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.

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

When logging is disabled, queries should not go unanswered. #25

Closed
guusdk opened this issue Jan 17, 2019 · 2 comments

Comments

@guusdk
Copy link
Member

commented Jan 17, 2019

When logging is disabled, a request for log entries goes unexpectedly unanswered (an empty response, or an error, is expected).

The cause for this is a nullpointerexception, from referencing a 'null' collection of retrieved archived messages, instead of an empty one.

@guusdk

This comment has been minimized.

Copy link
Member Author

commented Jan 17, 2019

Sadly, the exception is not logged.

@guusdk guusdk changed the title When logging is disabled, queries go unanswered When logging is disabled, queries should not go unanswered. Jan 17, 2019

@guusdk

This comment has been minimized.

Copy link
Member Author

commented Jan 24, 2019

This will be fixed in release 1.7.1.

@guusdk guusdk closed this Jan 24, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.