fix: pipeline with transactions causes unhandled warnings #884
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.
Pipeline#exec()
is a little tricky: it has an init process when called first time (indicated by whetherPipeline#nodeifiedPromise
is true).Transaction#exec()
is similar to that, it also has an init process that parse the result fromPipeline#exec()
before returning to users. However,#nodeifiedPromise
is not checked here, so it may fail which causes the unhandled warnings when retries.Closes: #883.
To be frank, it also take me a lot of time in order to understand the code, especially the complex relation between Pipeline & Transaction. We indeed need to do a refactor on this.