-
Notifications
You must be signed in to change notification settings - Fork 173
Allow some grace period for BS PCB policy. #1990
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
Conversation
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.
We will patch SCIONLab with almost identical code, only the tolerance being different
Reviewed 1 of 1 files at r1.
Reviewable status:complete! all files reviewed, all discussions resolved
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.
Reviewed 1 of 1 files at r2.
Reviewable status:complete! all files reviewed, all discussions resolved
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.
Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Reviewable status:complete! all files reviewed, all discussions resolved
If a PCB arrives with a timestamp from the future (which is accepted due to the changes in scionproto#1990), it may result in a zero delay_time value. The delay_time value is used in a division in the fidelity computation, which will trigger an exception.
If a PCB arrives with a timestamp from the future (which is accepted due to the changes in scionproto#1990), it may result in a zero delay_time value. The delay_time value is used in a division in the fidelity computation, which will trigger an exception.
If a PCB arrives with a timestamp from the future (which is accepted due to the changes in #1990), it may result in a zero delay_time value. The delay_time value is used in a division in the fidelity computation, which will trigger an exception.
If a PCB arrives with a timestamp from the future (which is accepted due to the changes in scionproto#1990), it may result in a zero delay_time value. The delay_time value is used in a division in the fidelity computation, which will trigger an exception.
Antl had a problem with ARM 32: antlr/antlr4#1858 So picking the commit of antlr where the PR scionproto#1990 was merged. Also casting a constant to uint64 (see default type of an untyped constant https://golang.org/ref/spec#Constants ).
This change is