When the boundary client establishes a connection to the websocket usedto communicate with a worker, it was configured with a max websocketmessage size of 32KiB. This was the default behavior for v1.8.7 ofnhooyr/websocket. However, there are cases where the worker can sendmessages to the client that are larger than 32KiB. When this happens theclient returns an error and terminates the connection.Notably this seems to only currently impact sessions made to SSHTargets, although it could theoretically impact any target typedepending on the details of how the worker performs the writing of themessages. The issue can be reproduced by attempting to scp a largeenough file from an SSH Target to the client. In this case theconnection gets terminated and results in a partial transfer of thefile.This message size limit appears to be unnecessary, and the defaultbehavior is changing in v1.8.8 of nhooyr/websocket to make the messagesize unlimited. Since this version is not yet released, this commitswitches the dependency to a fork with a version that is v1.8.7 plus thepatch to disable the limit. Once v1.8.8 is release this dependency canbe set back.See:coder/websocket#254coder/websocket#256

When the boundary client establishes a connection to the websocket usedto communicate with a worker, it was configured with a max websocketmessage size of 32KiB. This was the default behavior for v1.8.7 ofnhooyr/websocket. However, there are cases where the worker can sendmessages to the client that are larger than 32KiB. When this happens theclient returns an error and terminates the connection.Notably this seems to only currently impact sessions made to SSHTargets, although it could theoretically impact any target typedepending on the details of how the worker performs the writing of themessages. The issue can be reproduced by attempting to scp a largeenough file from an SSH Target to the client. In this case theconnection gets terminated and results in a partial transfer of thefile.This message size limit appears to be unnecessary, and the defaultbehavior is changing in v1.8.8 of nhooyr/websocket to make the messagesize unlimited. Since this version is not yet released, this commitswitches the dependency to a fork with a version that is v1.8.7 plus thepatch to disable the limit. Once v1.8.8 is release this dependency canbe set back.See:coder/websocket#254coder/websocket#256

When the boundary client establishes a connection to the websocket usedto communicate with a worker, it was configured with a max websocketmessage size of 32KiB. This was the default behavior for v1.8.7 ofnhooyr/websocket. However, there are cases where the worker can sendmessages to the client that are larger than 32KiB. When this happens theclient returns an error and terminates the connection.Notably this seems to only currently impact sessions made to SSHTargets, although it could theoretically impact any target typedepending on the details of how the worker performs the writing of themessages. The issue can be reproduced by attempting to scp a largeenough file from an SSH Target to the client. In this case theconnection gets terminated and results in a partial transfer of thefile.This message size limit appears to be unnecessary, and the defaultbehavior is changing in v1.8.8 of nhooyr/websocket to make the messagesize unlimited. Since this version is not yet released, this commitswitches the dependency to a fork with a version that is v1.8.7 plus thepatch to disable the limit. Once v1.8.8 is release this dependency canbe set back.See:coder/websocket#254coder/websocket#256

When the boundary client establishes a connection to the websocket usedto communicate with a worker, it was configured with a max websocketmessage size of 32KiB. This was the default behavior for v1.8.7 ofnhooyr/websocket. However, there are cases where the worker can sendmessages to the client that are larger than 32KiB. When this happens theclient returns an error and terminates the connection.Notably this seems to only currently impact sessions made to SSHTargets, although it could theoretically impact any target typedepending on the details of how the worker performs the writing of themessages. The issue can be reproduced by attempting to scp a largeenough file from an SSH Target to the client. In this case theconnection gets terminated and results in a partial transfer of thefile.This message size limit appears to be unnecessary, and the defaultbehavior is changing in v1.8.8 of nhooyr/websocket to make the messagesize unlimited. Since this version is not yet released, this commitswitches the dependency to a fork with a version that is v1.8.7 plus thepatch to disable the limit. Once v1.8.8 is release this dependency canbe set back.See:coder/websocket#254coder/websocket#256(cherry picked from commit88bb253)

Whoops, updates#254 andcloses#410