Skip to content
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

[FEA]: Remove MultiMessage and sub-classes from Morpheus #1802

Closed
7 tasks done
yczhang-nv opened this issue Jul 8, 2024 · 0 comments · Fixed by #1886
Closed
7 tasks done

[FEA]: Remove MultiMessage and sub-classes from Morpheus #1802

yczhang-nv opened this issue Jul 8, 2024 · 0 comments · Fixed by #1886
Assignees
Labels
feature request New feature or request

Comments

@yczhang-nv
Copy link
Contributor

yczhang-nv commented Jul 8, 2024

Is this a new feature, an improvement, or a change to existing functionality?

Improvement

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

Completely removes MultiMessage and its sub-classes from the Morpheus repo.

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
@yczhang-nv yczhang-nv added the feature request New feature or request label Jul 8, 2024
@yczhang-nv yczhang-nv self-assigned this Jul 8, 2024
@yczhang-nv yczhang-nv changed the title [FEA]: Completely remove all use cases of MultiMessage [FEA]: Remove all use cases of MultiMessage from stages Jul 30, 2024
@yczhang-nv yczhang-nv changed the title [FEA]: Remove all use cases of MultiMessage from stages [FEA]: Remove MultiMessage and sub-classes from Morpheus Sep 9, 2024
@rapids-bot rapids-bot bot closed this as completed in 64482ee Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant