Alex

Results 71 issues of Alex

# Overview Using the type system, we can already determine all of the parameter and return types to put them in the blueprint.json. What we can't know, though, is the...

feature ➕
task ✔️

# Overview The crypto crates are small and quick to build and test. Creating a job for each one creates a lot of noise.

task ✔️
testing 🛠️

We need: - [ ] A way to query the operators for a service ID in solidity. - [ ] A registry of operators to `deviceId`s - [ ] A...

feature ➕

# Overview The CLI uses a mix of `tracing` logs and `println!()` making the output inconsistent.

optimization ⚙️
p3 🔵
task ✔️

# Overview Right now, the Ubuntu images for the VMs are downloaded to the same location. If the version is ever updated, the new images will overwrite the old one....

feature ➕
p3 🔵

# Overview If you spawn a local Tangle node with `cargo tangle blueprint deploy tangle --devnet`, and the node isn't using port 9944, then the commands it outputs, such as:...

p3 🔵
task ✔️

# Overview Right now, job results can be submitted an arbitrary order. There may be a use case for having the job results be submitted in the order that the...

feature ➕
p3 🔵
wishlist

# Overview `IntoJobDefinition` is implemented for functions that take *no* arguments: https://github.com/tangle-network/blueprint/blob/d52797640f63cb99587f5410449bf5a488c2567e/crates/tangle-extra/src/metadata/job_definition.rs#L83-L97 but in the case that a function takes, for example, a `Context`, this impl no long applies.

bug 🪲
p1 🟠

# Overview I'd like to do the following: ```toml sdk = { git = "https://github.com/tangle-network/blueprint", package = "blueprint-sdk" } ``` But the context derive macros assume that I am using...

feature ➕
task ✔️

# Overview We could add `#[debug_job(tangle)]` to add Tangle-specific suggestions to invalid jobs. Some common ones: * Using `TangleArg*` where T is not `Deserialize` * Using `TangleArg*` where T is...

feature ➕
p2 🟡
task ✔️