-
Notifications
You must be signed in to change notification settings - Fork 271
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
build(deps): bump semver from 1.0.17 to 1.0.20 #2576
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [semver](https://github.com/dtolnay/semver) from 1.0.17 to 1.0.20. - [Release notes](https://github.com/dtolnay/semver/releases) - [Commits](dtolnay/semver@1.0.17...1.0.20) --- updated-dependencies: - dependency-name: semver dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
Pull requests that update a dependency file
rust
Pull requests that update Rust code
labels
Dec 20, 2023
olix0r
added a commit
to linkerd/linkerd2
that referenced
this pull request
Dec 27, 2023
When connecting to a control plane API, the API server can return an HTTP response long before it returns the first stream response. To bound this time, we now enforce timeouts so that failures may result in attempting to use an alternate controller instances. All controller response streams now use a generic gRPC middleware with initial, idle, and lifetime timeouts. When an initial timeout is encountered, a DeadlineExceeded grpc status is synthesized. When the other timeouts are encountered, the stream terminates gracefully. These timeouts are configurable by the proxy injector. Timeouts are not enabled without configuration: * LINKERD2_PROXY_CONTROL_STREAM_INITIAL_TIMEOUT * LINKERD2_PROXY_CONTROL_STREAM_IDLE_TIMEOUT * LINKERD2_PROXY_CONTROL_STREAM_LIFETIME Each of these parameters is optional. --- * build(deps): bump semver from 1.0.17 to 1.0.20 (linkerd/linkerd2-proxy#2576) * build(deps): bump memchr from 2.5.0 to 2.6.4 (linkerd/linkerd2-proxy#2577) * build(deps): bump arbitrary from 1.2.3 to 1.3.2 (linkerd/linkerd2-proxy#2578) * build(deps): bump data-encoding from 2.3.3 to 2.5.0 (linkerd/linkerd2-proxy#2579) * build(deps): bump tj-actions/changed-files from 40.2.3 to 41.0.1 (linkerd/linkerd2-proxy#2586) * build(deps): bump ahash from 0.8.5 to 0.8.6 (linkerd/linkerd2-proxy#2582) * build(deps): bump jemallocator from 0.5.0 to 0.5.4 (linkerd/linkerd2-proxy#2581) * build(deps): bump anyhow from 1.0.69 to 1.0.76 (linkerd/linkerd2-proxy#2583) * build(deps): bump symbolic-common from 12.6.0 to 12.8.0 (linkerd/linkerd2-proxy#2584) * build(deps): bump gimli from 0.28.0 to 0.28.1 (linkerd/linkerd2-proxy#2588) * build(deps): bump foreign-types-macros from 0.2.2 to 0.2.3 (linkerd/linkerd2-proxy#2590) * build(deps): bump symbolic-demangle from 12.6.0 to 12.8.0 (linkerd/linkerd2-proxy#2591) * control: Enforce timeouts on response stream (linkerd/linkerd2-proxy#2587) Signed-off-by: Oliver Gould <[email protected]>
olix0r
added a commit
to linkerd/linkerd2
that referenced
this pull request
Dec 27, 2023
When connecting to a control plane API, the API server can return an HTTP response long before it returns the first stream response. To bound this time, we now enforce timeouts so that failures may result in attempting to use an alternate controller instances. All controller response streams now use a generic gRPC middleware with initial, idle, and lifetime timeouts. When an initial timeout is encountered, a DeadlineExceeded grpc status is synthesized. When the other timeouts are encountered, the stream terminates gracefully. These timeouts are configurable by the proxy injector. Timeouts are not enabled without configuration: * LINKERD2_PROXY_CONTROL_STREAM_INITIAL_TIMEOUT * LINKERD2_PROXY_CONTROL_STREAM_IDLE_TIMEOUT * LINKERD2_PROXY_CONTROL_STREAM_LIFETIME Each of these parameters is optional. --- * build(deps): bump semver from 1.0.17 to 1.0.20 (linkerd/linkerd2-proxy#2576) * build(deps): bump memchr from 2.5.0 to 2.6.4 (linkerd/linkerd2-proxy#2577) * build(deps): bump arbitrary from 1.2.3 to 1.3.2 (linkerd/linkerd2-proxy#2578) * build(deps): bump data-encoding from 2.3.3 to 2.5.0 (linkerd/linkerd2-proxy#2579) * build(deps): bump tj-actions/changed-files from 40.2.3 to 41.0.1 (linkerd/linkerd2-proxy#2586) * build(deps): bump ahash from 0.8.5 to 0.8.6 (linkerd/linkerd2-proxy#2582) * build(deps): bump jemallocator from 0.5.0 to 0.5.4 (linkerd/linkerd2-proxy#2581) * build(deps): bump anyhow from 1.0.69 to 1.0.76 (linkerd/linkerd2-proxy#2583) * build(deps): bump symbolic-common from 12.6.0 to 12.8.0 (linkerd/linkerd2-proxy#2584) * build(deps): bump gimli from 0.28.0 to 0.28.1 (linkerd/linkerd2-proxy#2588) * build(deps): bump foreign-types-macros from 0.2.2 to 0.2.3 (linkerd/linkerd2-proxy#2590) * build(deps): bump symbolic-demangle from 12.6.0 to 12.8.0 (linkerd/linkerd2-proxy#2591) * control: Enforce timeouts on response stream (linkerd/linkerd2-proxy#2587) Signed-off-by: Oliver Gould <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps semver from 1.0.17 to 1.0.20.
Release notes
Sourced from semver's releases.
Commits
55fa2ca
Release 1.0.205feccc0
Merge pull request #305 from dtolnay/precedence83aaaf0
Add a method for precedence comparison of Versions83154ea
Test docs.rs documentation build in CI72a6b5a
Release 1.0.1983abc7f
Relocate comparator parse testing2d34e8f
Touch up PR 299 test cases5e09329
More comprehensible excessive version comparator test473209f
Merge pull request #299 from CXWorks/mastercb07901
Update actions/checkout@v3 -> v4Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)