dora-rs/dora - dora - 开源协同云脑生态支撑系统

Commit Graph

Author	SHA1	Message	Date
Xavier Tao	44a7c16c21	Add Python Node API metadata (#101 ) * Add a `dora-python-operator` crate to hold utils functions for dora python * Remove python serialisation and deserialisation from `dora-runtime` * Update `python` documentation	3 years ago
Philipp Oppermann	e8c17a864e	Adjust C and python node apis for new input/output API	3 years ago
Philipp Oppermann	0df06fce86	Send metadata in messages encoded with capnproto Changes the message format from raw data bytes to a higher-level `Message` struct serialized with capnproto. In addition to the raw data, which is sent as a byte array as before, the `Message` struct features `metadata` field. This metadata field can be used to pass open telemetry contexts, deadlines, etc.	3 years ago
Philipp Oppermann	f473c856c1	Fix clippy warnings across whole projects	3 years ago
Philipp Oppermann	de2481d2cb	Update python node API to work with synchronous Rust node API	3 years ago
Philipp Oppermann	03348c5be8	Redesign communication layer to be synchronous and add support for iceoryx	3 years ago
Philipp Oppermann	dbf189e239	Resolve clippy warnings	4 years ago
haixuanTao	4ff9a59ad7	Use `PyBytes` as it is faster than Vec<u8>	4 years ago
haixuanTao	6b2b082e71	Renaming `PyDoraNode` to `Node`	4 years ago
haixuanTao	d69776a85f	Adding `eyre` Error handling derived into `PyErr`	4 years ago
haixuanTao	9000e68111	Adding `__iter__` function	4 years ago
haixuanTao	1903c636cb	Refactoring `python-node-api`	4 years ago
haixuanTao	128bf6ca43	Adding `next`, `send_output` for Python node API Adding `next` and `send_output` requires an async threadpool as the communication Layer defined by the Middleware Layer returns an async Future stream. I solve this issue by adding a tokio runtime on a separater thread that is connected with two channels. One for sending data and one for receiving data. Those channel are then exposed synchronously to Python. This should not be cause for concern as channel are really fast. Looking at Zenoh Python client, they are heavily using `pyo3-asyncio` implementation of futures to pass Rust futures into Python. This can be a solution as well, but, from previous experiment, I'm concerned about performance on such solution. I have experienced that putting futures from Rust into the `asyncio` queue to be slow. I'm concerned also by mixing `async` and `sync` code in Python, as it might be blocking. This might requires 2 threadpool in Python. This might seem as heavy overhead for some operations.	4 years ago
haixuanTao	f7d288ba69	init `dora-node-api-python`	4 years ago

1 2

64 Commits (685b01e8fe3bbabf6fa2ab1ab667c9dacf388d21)