API dies if querying after disconnect

Reproduce:

await api.disconnect()

await api.derive.staking.stakerRewards(`FPstA2NF8wH4d8Z3VWhmALLSpcMi8Tttsv8jsJNZvL1y7GA`, 581)
  .catch(console.error);
console.log("Should be reached");

“Should be reached” will never be called

[kushptlapigarage]

I found same issue with out implementation. Here are the steps I took

1. connect to remote Substrate Node using @polkadotjs/api . I used ApiPromise.create()
2. Do simple queries using api.query.* methods
3. Shutdown WiFi ( simulates remote disconnect ). API Node is disconnected
4. Do another request using api.query.* method . The request should return as Failed but it halts
5. Start WiFi . Make another req using api.query.* method . This req does not return i.e. no response

[jacogr]

Thanks for logging.

Did an initial look-though and it def seems like an issue. So subscriptions are handled in a way where they re-connect, i.e. it will continue where it left off and but single-shot items don’t quite get handled the same. It should either -

• like subs, retry on re-connect, or
• throw an exception (which will be caught)

Just need to think through consistency and “least surprise” here. (Since we actually have round-robin on providers now as well where it can swap from one to another, the first one may be useful)