Closed mjfh closed 1 month ago
I can't reproduce this -- what are the specific conditions under which it occurs?
Is this still reproducible now that nimbus-eth1
uses Nim 2.0.6?
Both chain and config have been refactored many times since this issue opened, I don't think this issue still reproducible because we don't know what exactly the problem is.
The following code
produces something like
whereas the code
compiles fine.
This goes along with other errors, maybe related to
result.tryGet()
(I am working n that.) A dirty fix for this particular one would be changing the linenim-chronos/chronos/apps/http/httptable.nim:80
to