You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might just be a display glitch, but sometimes when building Quarkus I can see something like: threads used/hidden/max: 8/0/7
This is on WSL2/Ubuntu 20.04.
In WSL1/Ubuntu 20.04 on my rather dated work laptop it even reaches threads used/hidden/max: 12/0/7.
When this happens the list of modules being built is actually that long (longer than it should be).
The text was updated successfully, but these errors were encountered:
I think logging statements may still be associated with a given project after it has been finished. The client should disassociate those if they are sent after the project's build is finished.
What do you mean with "disassociate"? - not show them at all in the threaded view?
Yes, they would be associated to the main log instead of the per project log.
The way the log are associated to projects is not 100% perfect, because of the lacking infrastructure in maven, so mvnd does its best. Also ordering of the messages may be wrong : if the project's finish message arrives before one of the log, the client will recreate the project and it will kept in the display forever.
This might just be a display glitch, but sometimes when building Quarkus I can see something like:
threads used/hidden/max: 8/0/7
This is on WSL2/Ubuntu 20.04.
In WSL1/Ubuntu 20.04 on my rather dated work laptop it even reaches
threads used/hidden/max: 12/0/7
.When this happens the list of modules being built is actually that long (longer than it should be).
The text was updated successfully, but these errors were encountered: