-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: implemented submit chunking for RFD #0010 #737
Conversation
e6d0795
to
a11f303
Compare
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.
Missing some logic in the QuerySynthesizer, but the rest is looking good!
On the subject of versioning, I would do the following:
We can add RFD10 to On the next release, we will release new versions of the rust SDK and all plugins. |
This is not quite done yet, still working through a couple of things |
0ea199f
to
29eb6ad
Compare
29eb6ad
to
f2fe17e
Compare
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.
Some questions about changes to the logic. Either revert or prove parity with tests
f2fe17e
to
7e53387
Compare
d5d622e
to
c2e201b
Compare
just pushed to this branch again. It seems like there were some new |
Makes sense, Rust released 1.84.0 yesterday, which we pick up immediately in CI. New Rust versions usually mean new Clippy lints. |
- Added support for chunking Query submissions - Added test for submission chunking - Bumped hipcheck-common to 0.2.0 - Bumped hipcheck-sdk to 0.3.0 - Updated plugins to rely on hipcheck-sdk 0.3.0 - Bumped minor version of all plugins relying on hipcheck-sdk Signed-off-by: Patrick Casey <[email protected]>
c2e201b
to
9185e45
Compare
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 Patrick!
I just want to ensure that adding an enum variant to
QueryState
is not considered a breaking change. Also since this changeshipcheck-common
, does its version need be incremented or do we just handle that when it comes time to cut a release