wackazong
wackazong
`secp256k1-sys` is the only crate not compiling if I try to build `near-jsonrpc-client-rs` for `wasm32-unknown-unknown`. It would be great to have `near-jsonrpc-client-rs` available in the browser to use with Rust...
I can confirm the bug and the workaround by @uttarayan21 🙏
> I got `backoff` working with the following change, and using it in place of the `TokioSleeper` when using `wasm-bindgen`. > > ```rust > #[cfg(feature = "gloo-timers")] > #[cfg_attr(docsrs, doc(cfg(feature...
My use case would be to allow for the control of default values for keys and timestamps in different testing environments.
Yes, the first proposition would be great. The context would just need to be available in the builder, not in the final struct. I would like to set the context...
For me the most important would be to pass in the context at runtime and not at compile time.
https://github.com/near/near-cli/commit/8895ea7a45d5af192c938fa3718ca2ebc0460899#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L1331 For me it was rather useful in scripted deployments using bash process substitution and sourcing the key json from 1Password.
Storing the credentials unencrypted on disk is a security issue IMHO. I would prefer `--keyPath`. Or, even better, an env var that can be used to supply the private key.