Modernize WatchServiceFileSystemWatcher and watch .env for dev mode #41317
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #41282
I can't say I'm a big fan of the fix but we will have to live with this for now.
@stuartwdouglas while working on this, I stumbled upon a small issue: if we are filtering tests, the counter of run tests (
All 5 tests are passing (0 skipped)
) is not updated when we add filters (even when we force a re-run).My understanding is that we actually don't clear the test results but only push diffs to the test results (in
TestState
). I wonder if when we fully rerun the tests, we should actually clear the status but I'm not entirely sure, that's what you wanted?The reproducer here is quite useful: https://github.com/flyinfish/quarkus--continuous-testing-dotenv . Run dev mode, then uncomment the filters in
src/main/resources/application.properties
and you should see the problem.@radcortez at some point, we should probably think of a way to achieve this in a fully supported manner as this thing is quite brittle :). Not sure it's high priority though.