-
Notifications
You must be signed in to change notification settings - Fork 0
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
Scylla Calypso #173
Scylla Calypso #173
Conversation
info!( | ||
"A cleanup batch uploaded: {:?}", | ||
data_service::add_many(&database, final_msgs).await | ||
); |
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.
what's this code doing?
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.
That code batch uploads all remaining batches before exiting, such that scylla will not exit until all batch uploads are complete.
basically I noticed I used a loop and the proper rust syntax is a while and it annoyed me so much I switched it in this PR even though this PR is unrelated. my b.
if calypso receives a short or emtpy protobuf command_data, it will fill the extra values with the default value specified in the YAML. so we should allow the client to specify blank which could end up meaning a "Reset to Default" button.
* basic proof of concept * misc improvements and cleanup of cursory processing * implement reids review suggestions * try and fix clippy * and again fix clippy * make data query optional to reset calypso to default if calypso receives a short or emtpy protobuf command_data, it will fill the extra values with the default value specified in the YAML. so we should allow the client to specify blank which could end up meaning a "Reset to Default" button. * clippy is trolling me * fixup error handling for plaintext error message * implement reid fixes * remove not prod error
* basic proof of concept * misc improvements and cleanup of cursory processing * implement reids review suggestions * try and fix clippy * and again fix clippy * make data query optional to reset calypso to default if calypso receives a short or emtpy protobuf command_data, it will fill the extra values with the default value specified in the YAML. so we should allow the client to specify blank which could end up meaning a "Reset to Default" button. * clippy is trolling me * fixup error handling for plaintext error message * implement reid fixes * remove not prod error
Changes
config/<key>?data=123&data=456
. For context, this sends a MQTT message in accordance with the specifications of this PR.Notes
Do yall have any recommendations on how error codes and whatnot should be handled in the web server side? Should an error message be returned in the body of the response, or should we just have error codes and a log of what happened internal to the server?
Test Cases
candump
ing a virtual can interfaceChecklist
It can be helpful to check the
Checks
andFiles changed
tabs.Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
package-lock.json
changes (unless dependencies have changed)