build(deps): bump tj-actions/changed-files from 40.2.3 to 41.0.1 #2586
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 40.2.3 to 41.0.1. - [Release notes](https://github.com/tj-actions/changed-files/releases) - [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md) - [Commits](tj-actions/changed-files@56284d8...716b1e1) --- updated-dependencies: - dependency-name: tj-actions/changed-files dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
olix0r
deleted the
dependabot/github_actions/tj-actions/changed-files-41.0.1
branch
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
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 tj-actions/changed-files from 40.2.3 to 41.0.1.
Release notes
Sourced from tj-actions/changed-files's releases.
... (truncated)
Changelog
Sourced from tj-actions/changed-files's changelog.
... (truncated)
Commits
716b1e1fix: update characters escaped by safe output (#1815)7aaf10dchore(deps): update dependency eslint-plugin-prettier to v5.1.2cc08e17Upgraded to v41 (#1811)6e79d6eUpdate README.mdd13ac19Update README.mdbb89f97Update README.md1864078Updated README.md (#1810)f495a03chore(deps): lock file maintenance47371c5Update README.md (#1808)4f573feRevert "chore(deps): update actions/download-artifact action to v4" (#1806)Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)