-
Notifications
You must be signed in to change notification settings - Fork 23
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
Again messages break processable command output #754
Labels
bug
Something isn't working
core
FileAccess, ProcessUtil, IdeContext, etc.
environment
EnvironmentCommandlet, env variables, path, etc.
logging
Milestone
Comments
hohwille
added
bug
Something isn't working
environment
EnvironmentCommandlet, env variables, path, etc.
logging
core
FileAccess, ProcessUtil, IdeContext, etc.
labels
Nov 12, 2024
hohwille
added a commit
to hohwille/IDEasy
that referenced
this issue
Nov 12, 2024
hohwille
added a commit
that referenced
this issue
Nov 15, 2024
was auto-closed by PR. But still a bullet-proof solution is needed. |
Still buggy after merging PR #755
Problem was this message:
This one is interesting since this message is also in |
hohwille
added a commit
to hohwille/IDEasy
that referenced
this issue
Nov 19, 2024
hohwille
added a commit
to hohwille/IDEasy
that referenced
this issue
Nov 19, 2024
hohwille
added a commit
that referenced
this issue
Nov 21, 2024
hohwille
added a commit
that referenced
this issue
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
core
FileAccess, ProcessUtil, IdeContext, etc.
environment
EnvironmentCommandlet, env variables, path, etc.
logging
See #627 and #531.
This error was introduce by me with PR #746
Adding a log warning to some reasonable place should not lead to this error.
It is not acceptable that before adding a log warning you always have to understand if that may be triggered during context initialization since this way this error will come back again and again.
We need to find a way to finally fix this problem once and forever!
The text was updated successfully, but these errors were encountered: