Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: RUN-917: Fix composite query freezing threshold
- Loading branch information
1 parent
3b6e32a
commit 888f0ac
Showing
3 changed files
with
74 additions
and
171 deletions.
There are no files selected for viewing
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
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
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
888f0ac
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dfinity-berestovskyy how does moving the check of the freezing threshold from the
run
to theexecute_query
method fixes composite queries?888f0ac
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Luca,
As I mentioned before, usually we provide more information in the merge commits. Seems it does not work well with your workflow of reviewing individual commits. I'll raise this question with the team maintaining the repo, there should be some options to make it more comfortable for you...
888f0ac
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @Luca8991,
I spoke with a few teams internally. We're in the process of full GitHub migration. This issue will be taken into account while adapting our tools for GitHub.
As a result, the Release Notes (and hence the proposals) will be pointing to the merge commits with detailed descriptions. Meanwhile, unfortunately, we should keep searching for those merge commits manually.
JFYI, for each commit to review, there is almost always a corresponding merge commit with more details.
Here is the corresponding merge commit: 0dacbbb
888f0ac
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the clarification @dfinity-berestovskyy! It now makes sense looking at the related MR