antazoey

> Could be fixed by #1941 was it?

> hi all and apologies for late response. it seems to create another error log as follows : > > ```shell > File "/home/ubuntu/app/version-2-geospatial-pipelines/geospatial-pipelines/.venv/lib/python3.8/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 535, in _run_script > exec(code,...

are you using the eth-tester provider that comes with Ape? I haven't been able to reproduce this one, even after implementing the auto mine functionality.

> We haven't updated to a newer version of `eth-ape` because of #1933 workaround for #1933 https://github.com/ApeWorX/ape/issues/1933#issuecomment-2025623526 btw, this isn't a bug on 0.8 (which isn't released yet but is...

still unable to reproduce this.

please re-open , i dont think this is a problem!

How are you compiling + making changes the source code? Are the sources being changed mid test?

if there is any easy way to help reproduce this, it would be much appreciated!

I don't think Vyper is supported yet for programmatic Etherscan verification. For example, look at the part of the API docs: https://docs.etherscan.io/contract-verification/verifying-contracts-programmatically#id-4.-configuring-source-code-parameters It says the supported values for the `compilerversion`...

We should also support config driven versioning