Charles Cooper

> @charles-cooper are you now on board with [this](https://github.com/vyperlang/titanoboa/issues/82#issuecomment-2141415648) solution? no i don't think so -- false cache miss is OK, but false cache hit can be catastrophic

@saurabhnanda the atomicity of transaction blocks is guaranteed. `postgresql-simple` only guarantees that if exceptions are thrown in a `withTransaction` block that the transaction will be rolled back. However, multiple threads...

I ended up wrapping the Connection in an MVar. Another option is to use withResource from https://hackage.haskell.org/package/resource-pool-0.2.3.2/docs/Data-Pool.html.

@lpsmith I more or less agree with you that supporting a higher level of thread safety on `withTransaction` is complicated. Not least of which, after implementing a locking mechanism, the...

Hmm. I quite like name shadowing but in the case that somebody chooses not to name shadow, doesn't that open up a not-very-subtle possibility of deadlocking? E.g. ``` withTransaction c...

note as of yesterday or so i am no longer seeing the issue. i noticed a new image in the logs -- ``` 2024-04-09T20:26:08.1175581Z Current runner version: '2.315.0' 2024-04-09T20:26:08.1199165Z ##[group]Operating...

superseded by https://github.com/vyperlang/vyper/pull/4090

this is more or less ready for review, @cyberthirst to add more tests

> the output should be the same, right? > > ``` > (venv) custom[feat/archives*] % vyper tmp.zip -f archive | vyper /dev/stdin > 0x346100325761000c610024565b6100286100366038396100286038f35b604051600255565b5f60405261003061001c565b565b5f80fd5f3560e01c6361bc221a811861002057346100245760015460405260206040f35b5f5ffd5b5f80fd8418288000a1657679706572830004000012 > (venv) custom[feat/archives*] % vyper tmp.zip...

> ``` > (venv) custom[feat/archives*] % vyper test4.vy > Error compiling: test4.vy > vyper.exceptions.ModuleNotFound: ethereum.ercs.erc20 > > contract "test4.vy:3", line 3:0 > 2 > ---> 3 from ethereum.ercs import erc20...