condition fail throws ERROR in log #6
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If a respackopts condition fail, it will throw an error in the log, causes lag and isn't good for debug. It should be throw a warning in the log.
For example, the attached log file has about 2000 lines are thrown by respackopts in a few clicks.
There is no fundamental difference between errors and warnings, for all intents and purposes the only thing that changes is whether "warning" or "error" is inserted before the message, so printing a warning instead would change pretty much nothing about the performance of the code.
Additionally, I believe the circumstance of an incorrect pack more closely matches the definition of an error than that of a warning as per the SLF4J docs, which is why I chose that level in the first place. Marking these issues as a warning instead merely downplays their severity, which is counterproductive.
If I have misunderstood your argument (which is almost certain), please clarify what you mean, possibly by providing an example.
I'm closing this since you didn't respond.
If you have new information or a new idea on how to word your issue to help me understand it, you can reopen it or create a new one.