This error is coming from the server, senpai doesn't validate configuration values.
Related to #40
I can't reproduce. JOIN messages for detached channels should be blocked by upstreamConn.produce here: https://git.sr.ht/~emersion/soju/tree/bc83d3a3ba81f3e8c010c83160832bbf6b6bffff/item/upstream.go#L1820
they shouldn't be, since they don't provide information to soju unless the ID is specified.
Also, SQLite considers NULL to be different from NULL  (postgresql also does ), so the receipts flood the DB with junk.
Right now protodump panics on malformed input, e.g. missing attributes, tags, etc. protodump should only print an error in such case.
To do: change error types from
src/dwarf.rsand provide context when returning errors.
Should protodump also not panic on unexpected type tags? From one side this is due to protodump not supporting all types (so a panic is justified), but malformed input could point a type attribute to a tag that is not a type (so protodump should return an error).
Maybe list all types from std and panic if the tag is one of them and isn't supported by protodump , otherwise return an error.