fix: Only check for events queue on subscription request #1326
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant issue(s)
Resolves #1189
Description
Only checks for the events queue on subscription request. This makes the optional
WithUpdateEvents
database (constructor) option optional again (it would error without it for any kind of non-introspection request).Tested by running a few of the integration tests having hacked away the WithUpdateEvents db option in utils2.go, also checked that without the fix the hacks would result in an error.
As the integration test framework does not allow for db configuration atm, and we are planning on releasing today I am skimping on adding proper automated tests for this right now.