Charles Cooper

bumping this -- @banteg looks like there are some merge conflicts now as well as some test failures

how are you running vyper-serve and what is the version (output of `vyper-serve --version`)?

wow, interesting! can you give the code or a repro which is producing the error?

:thinking: is this a bug? Or is the vyper compiler correct in trying to calculate a very very large number.

I don't think infrastructure providers need us to prevent DoS for them, since that is their job and they are presumably much better at it than we are, and some...

we can fix this by adding a sanity check that `right` is not too large here: https://github.com/vyperlang/vyper/blob/aac0be8db89981c4ae27bc606fc411c531c44a80/vyper/ast/nodes.py#L1000-L1004

@Saw-mon-and-Natalie what is the best distribution channel for these? we already have continuous docker builds and wondering if that works for this use case - https://hub.docker.com/r/vyperlang/vyper. or do we need...

we could have a special release tagged "pre-release" which we automatically update every commit to `master`.

> we could have a special release tagged "pre-release" which we automatically update every commit to `master`. i created https://github.com/vyperlang/vyper/releases/tag/pre-release, maybe we can auto-update it every commit to master

i deleted the release because, unfortunately, it breaks brownie:  i did not test hardhat or ape, i'm curious how we can publish this pre-release version without...