-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Reset scan node for each join #828
Conversation
Scan node will have completed and will be in a finished state
3e32509
to
b40b99a
Compare
Codecov Report
@@ Coverage Diff @@
## develop #828 +/- ##
===========================================
- Coverage 59.59% 59.57% -0.02%
===========================================
Files 155 155
Lines 17266 17271 +5
===========================================
+ Hits 10289 10290 +1
- Misses 6048 6051 +3
- Partials 929 930 +1
|
// bae-fd541c25-229e-5280-b44b-e5c2af3e374d | ||
`{ | ||
"name": "Painted House", | ||
"rating": 4.9 | ||
}`, | ||
// "bae-d3bc0f38-a2e1-5a26-9cc9-5b3fdb41c6db" | ||
`{ | ||
"name": "Go Guide for Rust developers", | ||
"rating": 5.0 |
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.
question: why not keep the 4 fields?
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.
They are irrelevant, and including them suggests relevance
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.
A little strict xD. It doesn't hinder understanding with them in, however it also doesn't add anything
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.
IMO it does, when tracking down the bug the first thing I did (and this was about 50% of the effort) was remove everything extra so I had a minimal failing case. Specificity matters a lot in tests IMO. Really cuts down the possible what-if cases when looking to see why it is failing
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.
fair 👍
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.
LGTM
Scan node will have completed and will be in a finished state
Relevant issue(s)
Resolves #827
Description
Resets scan node for each join. Scan node may have completed and will be in a finished state and will return nil for other items.
Specify the platform(s) on which this was tested: