dora-rs
/
dora
Not watched
1
0
Fork 0
Code
Releases 124 Wiki evaluate Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain HPC
You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.
892 Commits
57 Branches
16 MB
7670 Download
Tree: f2fb2ffab6
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'f2fb2ffab6'
${ noResults }
dora/apis/python/node/Cargo.toml

Cargo.toml 570 B
Raw Normal View History

init `dora-node-api-python`
3 years ago
Release dora-rs version 0.1.3
3 years ago
init `dora-node-api-python`
3 years ago
​
Refactoring `python-node-api`
3 years ago
init `dora-node-api-python`
3 years ago
​
​
Remove code duplicate for tracing subscriber and use env variable to manage log level. The intent of this commit is to remove the quantity of log that is being pushed to user. This commit removes the redeclaration of a set up tracing methods to centralise the tokio-tracing subscriber within the extension crate. It also add the feature to filter information based on Environment variable. This makes it possible to define the log level for tokio tracing like this: ``` RUST_LOG=debug dora-daemon --run-dataflow dataflow.yml ``` I have also unified the feature flag to make it easier to manage tracing features among the workspace. I did not change the default behaviour of tracing in our crates and therefore by using the command above you should get the same tracing log as before. fix merge conflict generated
2 years ago
​
​
​
init `dora-node-api-python`
3 years ago
Remove static path from workspace dependency Removing those path make it easier to move package, reduce path management reduce complexity and make it easier to export crates to `crates.io`
2 years ago
​
Add `dora-node-api-python` package publication on pypi to release workflow (#92) * add `pip` release in release workflow * add blank space * Reduce Python verion to 3.7 for default conda support * Split CI workflows to avoid name collusions There is a name collusion issue within cargo. See: https://github.com/rust-lang/cargo/issues/6313 That make it impossible to build at the same time the `dora` cli binary, and the `dora` python shared library. To avoid the collusion, this commit split the two workflows: - `main` workflows consists of default-members and is tested on `ci.yml` - `python` workflow is on `ci-python.yaml` which is only run when python file changed. * add root example package * add python version * Fix Minor pypi release issue - Name is `dora-rs` and not `dora` - maturin 0.13 does not have `extension-module` features built in. * Use `--all` to check build of `dora` As the cli name was changed to `dora-cli`, we don't have name collusion anymore and can use `--all` flags for building and testing `dora`
3 years ago
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.
3 years ago
​
Update python node API to work with synchronous Rust node API
3 years ago
Remove static path from workspace dependency Removing those path make it easier to move package, reduce path management reduce complexity and make it easier to export crates to `crates.io`
2 years ago
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.
3 years ago
​
​
​
 123456789101112131415161718192021222324 
  1. [package]

  2. version.workspace = true

  3. name = "dora-node-api-python"

  4. edition = "2021"

  5. license = "Apache-2.0"

  6. 

  7. # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

  8. 

  9. [features]

  10. default = ["tracing"]

  11. tracing = ["dora-node-api/tracing"]

  12. 

  13. [dependencies]

  14. dora-node-api = { workspace = true }

  15. dora-operator-api-python = { workspace = true }

  16. pyo3 = { version = "0.16", features = ["eyre", "abi3-py37"] }

  17. eyre = "0.6"

  18. serde_yaml = "0.8.23"

  19. flume = "0.10.14"

  20. dora-runtime = { workspace = true }

  21. 

  22. [lib]

  23. name = "dora"

  24. crate-type = ["cdylib"]

DORA (Dataflow-Oriented Robotic Architecture) is middleware designed to streamline and simplify the creation of AI-based robotic applications. It offers low latency, composable, and distributed datafl