AutoRegister | bytecode instrumentation , a gradle plug

I'm afraid I presented another case of skimming the docs instead of actually reading it.

So I moved the code around a bit and this is what ended up working for me.

index.html

I don't think the term 'workaround' means what you think it means. If there was a way to distinguish, that would just be 'the answer', not 'the workaround'. If you elaborate on WHY you need this, perhaps a different solution is available, that is NOT directly detecting 'full rebuild' versus 'incremental build', which nevertheless is sufficient for your needs. That'd be a workaround, but you'd have to explain why you need it in order for us to try to help you out.

Here's the most common reason I can think of for why you need this:

Let's say your AP will scan all source files, and distill some sort of list from it. For example, all classes that implement com.derteufelqwe.MyAwesomeInterface. Then, it writes this list someplace. Say, META-INF/services/com.derteufelqwe.MyAwesomeInterface. The problem is: During incremental builds, you only see a subset of all sources, therefore the list is incomplete, then you write it where ever it needs to be written and now you have a broken list (as it is incomplete).

The fix for this is that you can ask the Filer for a source file or class file; even if it is not part of the compilation run it is still on the source path or class path and you get a result. Thus, IF you can read the existing list, and you can extract, per entry, the source or class file that is responsible for it (which in our hypothetical case where you are creating a services file, is trivial: The very entry is itself a fully qualified class name you can ask the Filer to find) you can then query the filer if that resource is still around. If yes, keep it, if not, delete it. Now you can update (instead of regenenerate and replace) your list.

As of today, you need to use DNS proxies or forwarders to achieve your ask. It is documented here in the scenario table.

For scenario "Name resolution from App Service Web Apps to VMs in the same virtual network.", the solution is to "Customer-managed DNS servers forwarding queries between virtual networks for resolution by Azure (DNS proxy)."

On How to perform "Name resolution with your own DNS" check here, where your scenario is described.

spring.cloud.consul.discovery.enabled=false will disable the consul DiscoveryClient. There is no java/annotation way to do it.

Did you try to remove optional=false from AuthorizationPosition?

Sometimes, Hibernate doesn't manage to put things in the "correct" order.

Hibernate sometimes needs to store NULL in foreign keys, even though there is a theoretical way to avoid it. You have to remove not-null constraints in these cases. (I removed all my not-null constraints from foreign keys ...)

You could try to remove the cascade from AuthorizationPosition, it might be the cause of the ordering problem. But I guess it wouldn't change anything.

Async await doesn't work in the forEach loop. Convert your forEach to a for loop. Something like so:

The docs are indeed a bit misleading, but "default" is not a permission/scope, it just tells you want data you can get WITHOUT an additional permission. You can find the available permissions in the link of your question, if you just scroll to the top. Only that list is important, for the default fields there is a link "Default Public Profile Fields", but - again - no scope/permission is needed.

And yes, there is a big difference between scope and fields. For example, the email field can be used after authorizing with the email scope, but the birthday field requires authorization with the user_birthday permission. Fields can be found here, for example: https://developers.facebook.com/docs/graph-api/reference/v3.1/user

Resolved

In public_html

OneSignalSDKUpdaterWorker.js OneSignalSDKWorker.js manifest.json

I never could get this to work and based on my google research, many others have had the same problem. I also tried using System.Timers.Timer and it's Elapsed event would not raise either. Google research showed lots of others having this problem too. All my code was in a try/catch and no errors were ever raised by either. I unfortunately had to write my own file monitor code and while it is not pretty, it works. I'm posting it for any others who may have this problem and who may be looking for a custom solution.