-
Notifications
You must be signed in to change notification settings - Fork 215
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
[Merged by Bors] - Add new PoET config "poet-request-timeout" and use it instead of GracePeriod for timeouts #4996
Conversation
44eb577
to
cdf8cf9
Compare
Codecov Report
@@ Coverage Diff @@
## develop #4996 +/- ##
=======================================
Coverage 77.1% 77.1%
=======================================
Files 254 254
Lines 30296 30301 +5
=======================================
+ Hits 23363 23377 +14
+ Misses 5416 5404 -12
- Partials 1517 1520 +3
|
bors try |
bors try |
tryAlready running a review |
tryBuild succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
05e5f75
to
4eed88f
Compare
e2736c8
to
cab09ff
Compare
bors merge |
…ePeriod for timeouts (#4996) ## Motivation The NiPoST builder uses `GracePeriod` for two different (unrelated) things: one is a duration relative to a PoET round start. A node waits until then before it starts creating and submitting a challenge to PoET (so that it uses the highest possible ATX it sees until then). The other use is as a request timeout for requests to PoET. For this a new config parameter "poet-request-timeout" is added to the config. This allows to set much shorter timeouts (1 hour on mainnet is much too long). ## Changes - add new config parameter "poet-request-timeout" - the defaults are calculated from the maximum time a request can take based on the linear jitter backoff ## Test Plan existing tests pass ## TODO <!-- This section should be removed when all items are complete --> - [x] Explain motivation or link existing issue(s) - [x] Test changes and document test plan - [x] Update documentation as needed - [x] Update [changelog](../CHANGELOG.md) as needed
Build failed: |
bors merge |
…ePeriod for timeouts (#4996) ## Motivation The NiPoST builder uses `GracePeriod` for two different (unrelated) things: one is a duration relative to a PoET round start. A node waits until then before it starts creating and submitting a challenge to PoET (so that it uses the highest possible ATX it sees until then). The other use is as a request timeout for requests to PoET. For this a new config parameter "poet-request-timeout" is added to the config. This allows to set much shorter timeouts (1 hour on mainnet is much too long). ## Changes - add new config parameter "poet-request-timeout" - the defaults are calculated from the maximum time a request can take based on the linear jitter backoff ## Test Plan existing tests pass ## TODO <!-- This section should be removed when all items are complete --> - [x] Explain motivation or link existing issue(s) - [x] Test changes and document test plan - [x] Update documentation as needed - [x] Update [changelog](../CHANGELOG.md) as needed
Build failed: |
bors merge |
…ePeriod for timeouts (#4996) ## Motivation The NiPoST builder uses `GracePeriod` for two different (unrelated) things: one is a duration relative to a PoET round start. A node waits until then before it starts creating and submitting a challenge to PoET (so that it uses the highest possible ATX it sees until then). The other use is as a request timeout for requests to PoET. For this a new config parameter "poet-request-timeout" is added to the config. This allows to set much shorter timeouts (1 hour on mainnet is much too long). ## Changes - add new config parameter "poet-request-timeout" - the defaults are calculated from the maximum time a request can take based on the linear jitter backoff ## Test Plan existing tests pass ## TODO <!-- This section should be removed when all items are complete --> - [x] Explain motivation or link existing issue(s) - [x] Test changes and document test plan - [x] Update documentation as needed - [x] Update [changelog](../CHANGELOG.md) as needed
Pull request successfully merged into develop. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Motivation
The NiPoST builder uses
GracePeriod
for two different (unrelated) things: one is a duration relative to a PoET round start. A node waits until then before it starts creating and submitting a challenge to PoET (so that it uses the highest possible ATX it sees until then).The other use is as a request timeout for requests to PoET. For this a new config parameter "poet-request-timeout" is added to the config. This allows to set much shorter timeouts (1 hour on mainnet is much too long).
Changes
Test Plan
existing tests pass
TODO