You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How would you describe the priority of this documentation request
Critical (currently preventing usage)
Describe the future/missing documentation
PR #1233 introduces new breaking API changes. We need to document the new compute_schema functionality, and update existing documentation broken by the change.
…1341)
* Update developer documentation to reflect new `compute_schema` changes.
* Cherry-pick `--run_milvus` flag from `fea-sherlock` (unrelated I just needed to quickly run the rest of the tests)
* Fix long-standing bug in `examples/developer_guide/3_simple_cpp_stage/pass_thru.py`, where the Python impl can support messages of any type, but the C++ impl only supports `MultiMessage`
* Copy code snippets from `docs/source/developer_guide/guides/7_python_modules.md` into `examples/developer_guide/7_python_modules/` allowing them to be tested & validated. Add a simple end-to-end test for the modules & stages (part of #993)
* Update the compound module snippet to operate on `MessageMeta` rather than `int` making it easier to run in a Morpheus pipeline.
Closes#1252
## By Submitting this PR I confirm:
- I am familiar with the [Contributing Guidelines](https://github.com/nv-morpheus/Morpheus/blob/main/docs/source/developer_guide/contributing.md).
- When the PR is ready for review, new or existing tests cover these changes.
- When the PR is ready for review, the documentation is up to date with these changes.
Authors:
- David Gardner (https://github.com/dagardner-nv)
Approvers:
- Devin Robison (https://github.com/drobison00)
URL: #1341
How would you describe the priority of this documentation request
Critical (currently preventing usage)
Describe the future/missing documentation
PR #1233 introduces new breaking API changes. We need to document the new compute_schema functionality, and update existing documentation broken by the change.
Where have you looked?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: