Fix the issue where the ReportTree component remains in a loading state when the result exceeds MAX_QUERY_SIZE #4747
+1
−1
Conversation
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
…te when the result exceeds MAX_QUERY_SIZE The MAX_QUERY_SIZE constant is defined in the report_server.thrift file as const i64 MAX_QUERY_SIZE = 500. After being compiled into a JavaScript package, Thrift i64 constants are not of type number in JavaScript and therefore cannot be used directly.
bruntib
approved these changes
Jan 22, 2026
Contributor
|
Thanks for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The MAX_QUERY_SIZE constant is defined in the report_server.thrift file as const i64 MAX_QUERY_SIZE = 500. After being compiled into a JavaScript package, Thrift i64 constants are not of type number in JavaScript and therefore cannot be used directly.