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
What is the feature or improvement?
Right now, if s nonsecure port is used for connection, a KittehNagException is reported as a non-terminating exception (everything works, you just get the exception trace). I don't mind the nag, but it would be nice if there was a way to turn off the entire trace explicitly, especially for testing, as the exception is a giant swath of text that gets emitted EVERY TIME. If I know what I'm about, especially during testing, I should be able to forcibly suppress the information I expect and don't need.
The text was updated successfully, but these errors were encountered:
What is the feature or improvement?
Right now, if s nonsecure port is used for connection, a
KittehNagException
is reported as a non-terminating exception (everything works, you just get the exception trace). I don't mind the nag, but it would be nice if there was a way to turn off the entire trace explicitly, especially for testing, as the exception is a giant swath of text that gets emitted EVERY TIME. If I know what I'm about, especially during testing, I should be able to forcibly suppress the information I expect and don't need.The text was updated successfully, but these errors were encountered: