`--network eravm` spawn `anvil-zksync` without closing them at the end of the process

[s3bc40]

OS: Ubuntu 24.04.1

I should look into this one day:

➜ ps
    PID TTY          TIME CMD
  16981 pts/6    00:00:01 zsh
  22748 pts/6    00:00:00 anvil-zksync
  26762 pts/6    00:00:00 anvil-zksync
  48272 pts/6    00:00:00 anvil-zksync
  49743 pts/6    00:00:00 anvil-zksync
  53086 pts/6    00:00:00 anvil-zksync
  56588 pts/6    00:00:00 anvil-zksync
  61013 pts/6    00:00:00 anvil-zksync
 143444 pts/6    00:00:00 ps

Running test or other CLI cmd with --network eravm tend to spawn anvil-zksync processes, but they are not shutting down.

I have to check this out, idk if it is specific to my OS...

I'll think about this, taking what I just did in my justfile:

deploy-anvil:
  anvil > /dev/null 2>&1 & ANVIL_PID=$!; mox run deploy; kill $ANVIL_PID

[s3bc40]

This could leverage an issue with testing with eravm.

If we manage to close every spawned anvil-zksync ps, then the RPC url will stay the same:

========================================
  Listening on 0.0.0.0:8011
========================================

We could use anvil-zksync as we use anvil in moccasin for testing with one fixed RPC url.

[PatrickAlphaC]

oo. Yeah we should fix this...

[s3bc40]

After quick investigation, I think it comes from node.py in titanoboa-zksync.

The __del__ method doesn't seem to be triggered. Maybe the AnvilZksync is not garbage collected while the zk env is running...

Also I saw that the port is dynamically chosen. We could change this to have the opportunity to get a constant RPC Url to add to Metamask, but maybe there's a reason to this choice.

[PatrickAlphaC]

@s3bc40 can you make an issue in that repo?

[s3bc40]

Yes I'll do and maybe work on this later 👍

[s3bc40]

vyperlang/titanoboa-zksync#45