Skip to content
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.

Sign up for GitHub

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

Jump to bottom

BAD_WORK_UNIT (114) should be classed as Error in the log and not as a Warning #295

Open
muziqaz opened this issue Oct 12, 2024 · 1 comment
Open

BAD_WORK_UNIT (114) should be classed as Error in the log and not as a Warning #295

muziqaz opened this issue Oct 12, 2024 · 1 comment

Comments

@muziqaz
Copy link
Contributor

muziqaz commented Oct 12, 2024

error

When I filter to Warning in the logs, I see BAD_WORK_UNIT (114) listed. I believe this should be classed as Error. Unless Warning is classed as more severe as Error, but then the rest of the messages in my screenshot under Warning wouldn't make sense.
@muziqaz
Copy link
Contributor Author

muziqaz commented Oct 17, 2024

Hi, just to add, CORE_RESTART (98) seems to be classed as warning too. I believe this should be pushed as an Error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@muziqaz