ctrl-c not reliable on opam 2.0.2 during installation

[avsm]

with opam.2.0.2, I'm trying an opam install . and observing that several ctrl-c keypresses are ignored during the archive downloading phase, and then I get non-deterministic errors. For example:

[atdgen-runtime.2.0.0] found in cache
[base.v0.11.1] found in cache
[base64.2.3.0] found in cache
[bin_prot.v0.11.0] found in cache
[biniou.1.2.0] found in cache
[cmdliner.1.0.3] found in cache
[cohttp.1.2.0] found in cache
[cohttp-async.1.2.0] found in cache
[conduit.1.3.0] found in cache
[conduit-async.1.3.0] found in cache
[configurator.v0.11.0] found in cache
[core.v0.11.3] found in cache
[core_bench.v0.11.0] found in cache
[core_extended.v0.11.0] found in cache
[core_kernel.v0.11.1] found in cache
[cppo.1.6.5] found in cache
[cppo_ocamlbuild.1.6.0] found in cache
Fatal error:
Cannot remove /Users/avsm/.opam/foo/.opam-switch/sources/cryptokit.1.13 (error 255).

On other invocations of ctrl-c, I get a user interrupt error as expected:

[toplevel_expect_test.v0.11.0] found in cache
[typerep.v0.11.0] found in cache
[uchar.0.0.2] found in cache
[uri.2.1.0] found in cache
[uutf.1.0.1] found in cache
[variantslib.v0.11.0] found in cache
[yojson.1.4.1] found in cache
[zarith.1.7] found in cache
[ERROR] User interruption

[dra27]

I confirm this is still quite easy to do in a docker container with both 2.0.8 and 2.1.0

[dra27]

Another to check for triage: in the original example, all the downloads appear to be cached. It would be worth seeing if this is occurring as a result of un-tarring or downloading.