Initialize Mercurial Gauntlet on story skip #893
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Seeing errors in the logs about people attempting to access Mercurial Gauntlet without the required DbQuestWalls initialized. It seems the gap here is story skip - you skip past the MG story but without having the data initialized. Attempting to read the story after this will not send a request to the server. Will need to run a DB query after this to fix affected saves. Plus a usual bunch of misc refactoring and global query filter usage.
This gives a warning about using Take without an OrderBy, but the guard here against additional wall rows is unlikely to be worth it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Seeing errors in the logs about people attempting to access Mercurial Gauntlet without the required DbQuestWalls initialized. It seems the gap here is story skip - you skip past the MG story but without having the data initialized. Attempting to read the story after this will not send a request to the server.
Will need to run a DB query after this to fix affected saves.
Plus a usual bunch of misc refactoring and global query filter usage.