Vlad Frolov

Good call! Indeed, this `unsafe` is not playing well: https://github.com/near/borsh-rs/blob/b5104293d8e1f6641da1dc1c3c554390e34563b6/borsh/src/de/mod.rs#L274-L284 @ailisp It seems that you have some experience with this area (https://github.com/near/borsh/pull/41). Do you have the capacity to work on...

Nope, we still need to address it

Salford Systems is using Alpine for internal processes (testing and helpers). http://dots.org.ua/ is a local Ukrainian non-profit platform for programming contests (IOI, ACM, and training), and it is using Alpine...

I completely agree with @Alex-PK, both `.expect()` and `.context()` are misleading for me. `.chain()` is still a too broad term since you apply it to the Result which may be...

Given `#[fail(display)]` functionality has been moved into a separate crate `display_derive` in failure 1.x, I think this issue should be opened there: https://github.com/withoutboats/display_derive

@volovyk-s What is on your mind in terms of a different strategy? I feel near-api-js is the right abstraction layer to deal with the pool of RPC servers to enable...

@volovyk-s Ah, well, those are indeed two completely different efforts, but they came somewhat together, and we need both solutions: (1) extended RPC connection configuration, (2) failover configuration. This issue...

I want to mention that there is a similar issue #238

@amgando your solution implies that sh is available. Is it always the case for node environments on Windows? (Does near-shell work on Windows?)

@amgando I suggest we better use GitHub Actions. It is a new built-in CI with all three major platforms available.