-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
settings: add network.connection_timeout
and network.cloud_api.skip_board_detection_calls
#2770
settings: add network.connection_timeout
and network.cloud_api.skip_board_detection_calls
#2770
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2770 +/- ##
==========================================
+ Coverage 67.52% 67.55% +0.02%
==========================================
Files 237 237
Lines 22362 22373 +11
==========================================
+ Hits 15101 15115 +14
+ Misses 6068 6066 -2
+ Partials 1193 1192 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
4b44476
to
665d54d
Compare
665d54d
to
2278bbc
Compare
The latest Buf updates on your PR. Results from workflow Check Protocol Buffers / check (pull_request).
|
2d4aee1
to
6df6b17
Compare
6df6b17
to
ab8c357
Compare
6d1db1e
to
ff3735f
Compare
connection_timeout
network.connection_timeout
and network.cloud_api.skip_board_detection_calls
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Introduces:
connection_timeout
setting, which our HTTP client will use as a timeout durationcloud_api.skip_board_detection_calls
boolean setting that (iftrue
) will skip the API call required to identify the board (if no installed platforms match the board).What is the current behavior?
The current behavior uses the default timeout which is 0. It means that it will wait indefinitely.
What is the new behavior?
The new behavior will respect user settings for the connection timeout. The default will be the same, but in case the user provides the
network.connection_timeout: 5
it means that the HTTP client will exit with an error if the connection is taking longer than 5 seconds.There is also a new configuration value to disable querying the Cloud API to identify a board.
Does this PR introduce a breaking change, and is titled accordingly?
Other information