Ian Bull

Thanks @kitsonk. However, if I set my `DENO_DIR` to something below my current working directory (or even `export DENO_DIR=$PWD`) it still complains that I need `--allow-read`.

I have reproduced this same error, but not with the size of the data, but by reaching the `idleTimeout` and having the server close the connection. I've opened https://github.com/denoland/deno/issues/15091 to...

I'm not sure I'd feel confident if the errors just went away. This is clearly some timing / size issue in the underlying rust code / network layer. That happens,...

I can reproduce this websocket panic with Deno 1.15.1. I setup an echo server and a (reconnecting) client that pumps messages to the server. Right before the `ws.send`, I set...

Also, on occasion I get this backtrace. Similar, but not exactly the same: ``` thread 'main' panicked at 'Error 'IO error: Broken pipe (os error 32)' contains boxed error of...

And if we flip it around, and the server sends the messages to the client, while setting a short timer to close the connection, then you get the boxed error...

The third case `Protocol(SendAfterClosing)` is actually just the reverse. Client connects to the server, and the client echo's its responses, and the server sends sends requests followed by `close`. ```...

Same with the `Io` error. I added a matcher for that too. These seem like errors that _can_ be thrown according to https://docs.rs/tungstenite/0.15.0/tungstenite/error/enum.Error.html, so specific handling may be required. After...

Unless things have changed, Orion does have _server side_ but it runs on your client (if that makes sense). That is, you can self host your server. The client is...

I had a bit of time this evening so I thought I'd take a look, and you're right this is pretty complex. The `feature_checker` does have the right flags set,...