Conversation:
Notices
-
Looks like NoResultException derives from the ServerException and the reason that they don't log centrally from ServerException is that it gets spammy with NoResultException in there.
This seems like something to fix in the descendant class rather than making all other errors opaque as fuck, though, if you ask me!
-
Well, next step then is getting NoResultException in with the ServerException code and coding it in such a way as we cut down on the spam caused by that. I will probably make NoResultException at LOG_DEBUG severity, not LOG_ERR.
-
Okay, added a $severity variable to the constructor of the ServerException class, if it is LOG_DEBUG it uses common_debug to write the line, otherwise it uses common_log, and got NoResultException in there using that to pass those things into LOG_DEBUG, not LOG_ERR. You can use the logfilter plugin to parse out LOG_DEBUG severity - which is what I do unless something's acting up.
-
Okay got the NoUserResultException thing in there easy enough and that seems to work so should be easy enough to get the rest in there.
maiyannah
All Hacker Poesy content and data are available under the