-
Notifications
You must be signed in to change notification settings - Fork 137
Add NoOpReplayLog for optional replay protection #75
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
base: master
Are you sure you want to change the base?
Conversation
Add NoOpReplayLog, a ReplayLog implementation that performs no replay protection. This allows using the Router without replay protection when it is not needed, such as for onion messaging.
Rename the parameter to be more generic since it is passed to the ReplayLog and can store any auxiliary data, not just CLTV values. Update godoc to explain usage with and without replay protection.
Summary of ChangesHello @gijswijs, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the flexibility of the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Pull Request Test Coverage Report for Build 20823897384Details
💛 - Coveralls |
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.
Code Review
This pull request introduces a NoOpReplayLog for scenarios where replay protection is not needed, and refactors ProcessOnionPacket to use a more generic replayData parameter. The changes are logical and well-tested. My review focuses on ensuring adherence to the repository's style guide, particularly regarding comment formatting, line length, and the use of the require library in tests. I've provided specific suggestions to align the new code with these standards.
Roasbeef
left a comment
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 🥽
Failing linter howwever.
|
@gijswijs, remember to re-request review from reviewers when ready |
Summary
NoOpReplayLog, aReplayLogimplementation that performs no replay protection, allowing theRouterto be used without replay protection when it is not needed (e.g., for onion messaging)incomingCltvparameter toreplayDatainProcessOnionPacketto reflect its generic natureTest plan
NoOpReplayLoginreplaylog_test.go