janedegtiareva

Code smell: changing return true; to true in check_access causes a test failure

1

This is supposed to not affect any actual execution result. There might be an underlying issue.

This creates a huge drain on productivity right now * Restarting builds on PRs * publish on near-api-js with np takes >1/2 day due to having to re-run the tests

Add a capability to return a signature to the client rather than signing and sending the txn as a combo

2

Requirements: * The goal is sign transaction in the wallet UI and then return it back to the client code (which holds it as a signed transaction) * It's necessary...

This is a very easy change that would improve dev ex a lot.

can't publish near-shell from a cloud VM

1

steps to repro: * make a google cloud VM and install node, yarn, np, etc follow the app layer release process, specifically NODE_ENV=ci np --no-yarn get the following error: yarn...

This option does not apply to all the commands, and can cause confusion in some cases.

'options.stdout' must be specified error happens sometime after starting new proj

2

To Repro (happens occasionally) - open NEARStudio - new project from template. I used counter template, but this probably happens with any template - click run. - Error details: [info]:...

To reproduce: - fork an old fiddle, e.g. https://studio.nearprotocol.com/?f=c41iy5w79 - get error output in the console [info]: Task build is running... [error]: Task build failed: nearUtils.generateBindings is not a function...