nearlib sometimes sends 2 txns with the same nonce at once. 1 is guaranteed to fail. about near-api-js HOT 8 CLOSED

It seems to be triggered when the access key points to its own account. We've tried to repro with the studio app, but it doesn't reproduce correctly.

from near-api-js.

Can we prioritize the fix?
Currently the accessKey is always pulled from the node through RPC. It doesn't cache the key locally:
https://github.com/nearprotocol/nearlib/blob/8aadbdd93c255ff2fa3f01397f5fc11be3f9aea5/src.ts/account.ts#L91-L100

from near-api-js.

Background: Right now 2 of the apps I'm working on (ethrelay and metanear) can't send more than 1 transaction per second. So I have to implement queue for metanear and to reimplement sendTransaction on ethrelay

from near-api-js.

Getting cors error:
Access to fetch at 'https://rpc.nearprotocol.com/' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

const nearRpc = new providers.JsonRpcProvider("https://rpc.nearprotocol.com");
return await nearRpc.sendJsonRpc('tx', [txHash, accountId]);

txHash is encoded and accountId is also expected val

from near-api-js.

@evgenykuzyakov is nearcore executing OPTIONS requests as actual JSON-RPC? Not sure why would CORS error occur because of nonce error otherwise. Or is the problem that Access-Control-Allow-Origin isn't set on errors by nearcore?

from near-api-js.

Moved it to In Progress as I understand Vlad is working on this currently.

from near-api-js.

For now this is somewhat blocked by the fact that nearcore sometimes doesn't return error specific to duplicate nonce (Timeout is returned instead).

from near-api-js.

nearcore issue: near/nearcore#2039.

from near-api-js.