-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote-dev: LiveReloadConfig is not always properly initialized #12571
Comments
Sometimes I also see
which looks like the same lost app properties issue. |
I have not been able to reproduce this. It looks like the config is going missing somehow. #12931 helps with one of the reported stack traces. |
Just curious how were you testing this? I was using minikube. |
Ah, it looks like I can reproduce it only when editing the pom.xml in the IDE. Editing in a text editor doesn't seem cause this error. So it looks like it's related to the IDE copying/cleaning the resources dir. |
Yes, if I disable automatic build in the IDE I can't reproduce it. That makes sense. Didn't think of it originally. Not sure we can do much here. I am closing it for now. |
This IDE building issue is actually not limited to the POM, I guess. So it probably has to be a general recommendation to turn off automatic building for the remote-dev. |
There probably is something I can do here. Do you know what exactly is broken by the automatic build? |
All I can say atm is it looked like the application.properties was not always present. |
I guess in the output directory. If we always looked at the source dir instead in dev mode then we probably would avoid this issue. |
Then resource filtering wouldn't be applied. At least on the first build. |
After thinking about it a bit I guess there is not much we can do. |
Adding and removing
to the POM of a simple REST endpoint project running in remote-dev mode may sometimes fail with
FYI @stuartwdouglas
The text was updated successfully, but these errors were encountered: