-
Notifications
You must be signed in to change notification settings - Fork 406
RGS Accepts Stale Data Without Error #1785
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
Milestone
Comments
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Dec 16, 2022
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Dec 16, 2022
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Feb 9, 2023
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Feb 9, 2023
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Feb 16, 2023
arik-so
added a commit
to arik-so/rust-lightning
that referenced
this issue
Feb 16, 2023
optout21
pushed a commit
to optout21/rust-lightning
that referenced
this issue
Jul 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of #1764, the RGS processor will now happily accept data that is >2 weeks old, which is an indication the server is busted and we should actually generate an error, see #1764 (comment). A straight partial-revert of 1764 is probably not the right solution - the errors are just not descriptive enough for us and we should fix that.
The text was updated successfully, but these errors were encountered: