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.
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
[BUG] use deep copy of bit arrays when getting array node state #5681
[BUG] use deep copy of bit arrays when getting array node state #5681
Changes from all commits
f896932
73155cd
6697ecd
dde7595
1a898f9
2a20e02
e3a5952
36d1288
1f94bfe
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 321 in flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go
Codecov / codecov/patch
flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go#L319-L321
Check warning on line 326 in flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go
Codecov / codecov/patch
flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go#L323-L326
Check warning on line 332 in flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go
Codecov / codecov/patch
flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go#L330-L332
Check warning on line 337 in flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go
Codecov / codecov/patch
flytepropeller/pkg/apis/flyteworkflow/v1alpha1/node_status.go#L335-L337
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
I understand the purpose of this now, thanks for the comment. We're adding a field to a central config object and assuming that such field will only be used in a particular situation. This feels hacky to me, but maybe there's a precedent and good reason to follow this pattern.
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.
yup - it definitely is hacky. Looking forward when/if we eventually re-work eventing in propeller
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Check warning on line 167 in flytepropeller/pkg/controller/nodes/node_state_manager.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/node_state_manager.go#L165-L167
Check warning on line 172 in flytepropeller/pkg/controller/nodes/node_state_manager.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/node_state_manager.go#L170-L172
Check warning on line 177 in flytepropeller/pkg/controller/nodes/node_state_manager.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/node_state_manager.go#L175-L177
Check warning on line 182 in flytepropeller/pkg/controller/nodes/node_state_manager.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/node_state_manager.go#L180-L182