-
Notifications
You must be signed in to change notification settings - Fork 731
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
CCQ: Testing #3424
Merged
Merged
CCQ: Testing #3424
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ae39d94
to
24dbcdb
Compare
2e24f36
to
8f10a69
Compare
8f10a69
to
aac0af3
Compare
6e07adc
to
5071a05
Compare
SEJeff
reviewed
Oct 11, 2023
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.
Questions
- Do you forsee a user having multiple api keys? If not, is the username for anything other than a description?
- Public facing code really needs better test coverage. Public facing == threat surface.
- Assuming its identity key is permissioned, does the query server need to run on a guardian?
Notes
- The all or nothing approach makes me uneasy for some reason. What if the user is ok with some of the queries failing? They just make 1 ccq for each query instead of batching them? This should be made obvious to integrators I think if it isn't blatantly obvious in the whitepaper and godoc comments.
- Try to avoid logging secrets as logs have a habit of being shared with the world sometimes on purpose and often by accident.
- Littering the key files all over the codebase is messy, it would be so awesome to just use interfaces so this code can be tested without requiring these. This is guaranteed 100% to result in extra immunefi bugs and nonsense from github code scanners that will waste our time.
- The guardianset is fetched on startup, but doesn't seem to be polled intermittently though there is a crasher error for the error when the gst might be wrong.
- This PR supercedes CCQ/Node: Guardian Changes #3423 because it includes the same commit.
c9337bc
to
93b59cf
Compare
ec08acb
to
295376f
Compare
aac0af3
to
cf88129
Compare
295376f
to
301601c
Compare
99de9aa
to
f7da688
Compare
301601c
to
b5d8ffe
Compare
f7da688
to
25dec86
Compare
evan-gray
approved these changes
Oct 12, 2023
SEJeff
approved these changes
Oct 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds tests for the CCQ feature. This PR is dependent on PR #3423.
For background on this feature see the whitepaper (PR #3418).