fix: ungraceful exit

[josepot]

Fixes #327 and a bunch of other small issues.

I've been working on some E2E tests for this, to make sure that we don't have regressions on it. For testing I was going to use the logs-provider idea that I have in the works... However, we realized with @voliva that it's better to wait until he has finished the work that he is currently doing improving the vitest tests, before I bring these E2E tests in.

[Bullrich]

Update:

It is exciting automatically but it is taking around 30 seconds to do so.

Is this behaviour expected?

Example test:

Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 32.689 s
Ran all test suites.
Jest did not exit one second after the test run has completed.

'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.
✨ Done in 62.02s.

[josepot]

Update:

It is exciting automatically but it is taking around 30 seconds to do so.

Is this behaviour expected?

Example test:

Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 0 total
Time: 32.689 s
Ran all test suites.
Jest did not exit one second after the test run has completed.
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.
✨ Done in 62.02s.

It depends on which provider you are using. If you are using smoldot, then I think that this is normal, as smoldot is going to try to gracefully close all the open connections with its peers... A way around this (although it's a bit hacky) is to put smoldot into a worker, and then create a JSON-RPC provider from the worker, then we it exists they you can just destroy the worker.