Fix deadlock in errors-must e2e test #874
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
emil14
changed the title
…ing compiler internals
…es now respects cases with `?` and `err`
…must to protect from fixed deadlock
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.
node -> ...with?error-guard operator - when callinggetFirstOutportNameto getnode:portsometimes we got:errwhich must've been skipped because of?)--emit-iradded forneva runcommand, that allows to emit IR in yaml while running the program to get the exact same IR that is actually executed (implementation and API needs to be refactored in the future)1.24golangci-lintupdated to 1.64 (still no support for Go 1.24?)src.Scope(with fixes)