Miraculous Owonubi
Miraculous Owonubi
Kubo permits the use of `peerid-base` as a parameter when making a call to `/api/v0/id`. This crate should too. In my tests, Kubo doesn't seem to respect the `format` parameter....
Linked: https://github.com/ferristseng/rust-multipart-rfc7578/pull/33 I noticed a weird trait restriction that makes it so only streams implementing `Sync` are permitted to the upload API. Even though the download API doesn't abide by...
Would be great if there was a modular interface to this that other applications could depend on. The CLI interface provided here, therefore being the first.
https://github.com/feross/simple-get/blob/e7a74115ca9dd28720f186275c5a67df81985426/index.js#L74-L77 This calls `abort` on the request, and fires the callback. So you'd expect `simpleGet` to have relinquished all execution back to the caller. But in a super simple example...
What do you think about setting up a log subscriber for the binary, `near-jsonrpc-client`, for example uses `log` internally, and I would like to be able to see those reports...
Just noticed some weird behaviour, not sure if it's been reported already, I tried searching but I'm not sure how to classify it this: ```rust pub/* (crate) */ trait MyTrait...
The ABI spec allows arbitrary metadata; ```rust /// Other arbitrary metadata. #[serde(default, flatten, skip_serializing_if = "HashMap::is_empty")] pub other: HashMap, ``` I was thinking `cargo-near` could provide a way for users...
When building with `--embed-abi`, `cargo-near` should probably check that the `__contract_abi` method is actually exported.
Opening this for visibility. Been seeing this issue come up again and again in the macOS CI runs. And it doesn't happen in the Linux runs. ![CleanShot 2022-08-27 at 18...