Repository navigation
test: raise user list query ceiling for core's asset revision header - #64
Merged
Merged
Conversation
Core 2.0.1 stamps every API response with X-Flarum-Assets-Revision, which reads asset_revisions once per request.
This file contains hidden or 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
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.
Changes proposed in this pull request:
Core 2.0.1 added
X-Flarum-Assets-Revisionto every API response, which costs oneasset_revisionsread per request. That takesListUsersQueryCountTestfrom 11 to 12 queries and turns CI red on every PR. The ceiling and budget now include it; the count is still constant regardless of list size.Reviewers should focus on:
Screenshot
Necessity
Confirmed
yarn testinjs/).composer test).Required changes: