Forward-merge branch-24.10 into branch-25.02 #508
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
![rapids-bot[bot]](https://avatars.githubusercontent.com/in/85914?s=60&v=4){kind=small}
`rapidsai/shared-action-workflows/get-pr-info` was deleted in favor of `nv-gha-runners/get-pr-info` rapidsai/shared-actions#11 Authors: - Christopher Harris (https://github.com/cwharris) - David Gardner (https://github.com/dagardner-nv) Approvers: - Michael Demoret (https://github.com/mdemoret-nv) URL: #500
|
FAILURE - Unable to forward-merge due to an error, manual merge is necessary. Do not use the IMPORTANT: When merging this PR, do not use the auto-merger (i.e. the |
dagardner-nv
approved these changes
Oct 22, 2024
This PR is replacing the `VAULT_HOST` variable with `AWS_ROLE_ARN`. This is required to use the new token service to get AWS credentials Authors: - Jordan Jacobelli (https://github.com/jjacobelli) Approvers: - David Gardner (https://github.com/dagardner-nv) URL: #506
Overview of new classes added in this PR:
- `DynamicRouterBase`
- Sink
- `WritableProvider`, `ReadableAcceptor`, `SinkChannelOwner`
- Source
- `MultiWritableAcceptor`, `MultiReadableProvider`, `MultiSourceChannelOwner`
- Runnable with ability to change number of outputs at runtime
- Cannot be added to a Segment
- Good backpressure support. Can still process requests if downstream blocks
- `LambdaDynamicRouter`
- Provide key function via lambda
- `DynamicRouterComponentBase`
- Sink
- `ForwardingWritableProvider`
- Source
- `MultiWritableAcceptor`, `MultiReadableProvider`, `MultiSourceChannelOwner`
- Non-Runnable with ability to change number of outputs at runtime
- Limited backpressure support. Will block if downstream blocks
- `LambdaDynamicRouterComponent`
- Provide key function via lambda
- `StaticRouterRunnableBase`
- Sink
- `WritableProvider`, `ReadableAcceptor`, `SinkChannelOwner`
- Source
- `MultiWritableAcceptor`, `MultiReadableProvider`, `MultiSourceChannelOwner`
- Runnable with fixed number of outputs
- Can be added to a Segment since it supports child outputs
- Good backpressure support. Can still process requests if downstream blocks
- `LambdaStaticRouterRunnable`
- Provide key function via lambda
- `StaticRouterComponentBase`
- Sink
- `ForwardingWritableProvider`
- Source
- `MultiWritableAcceptor`, `MultiReadableProvider`, `MultiSourceChannelOwner`
- Non-Runnable with fixed number of outputs
- Can be added to a Segment since it supports child outputs
- Limited backpressure support. Will block if downstream blocks
- `LambdaStaticRouterComponent`
- Provide key function via lambda
Closes #491
Authors:
- Michael Demoret (https://github.com/mdemoret-nv)
- David Gardner (https://github.com/dagardner-nv)
Approvers:
- David Gardner (https://github.com/dagardner-nv)
URL: #502
3 tasks
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.
Forward-merge triggered by push to branch-24.10 that creates a PR to keep branch-25.02 up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.