Execution stalls after second encoding request

[alex-ketch]

To reproduce:
Open GSuita
Create an new "R" node
Run and insert into document
Update code and re-run
Request will never terminate

[alex-ketch]

Edit, this might just be an Executa issue after all as I was able to reproduce it with Basha too.

I see five messages in total in the browser inspector:

1. ⬆️: method: "execute"
2. ⬇️: result
3. ⬆️: method: "encode"
4. ⬇️: result
5. ⬆️: method: "execute"
6. 🦗: Silence…

There are four corresponding messages in the Executa CLI logs

1. Delegating job "jo14f03457f63sC54Xig3ymcNVrZYKnR" to peer "io14f03051a6jiJH5K5vDnFBSqf7c6hz"
2. Received result for job "jo14f03457f63sC54Xig3ymcNVrZYKnR"
3. Delegating job "jo14f0347202bqFU9THJh5tt082mxgnL" to peer "io14f03051a656mi3asxXxjJUo59THEL"
4. Received result for job "jo14f0347202bqFU9THJh5tt082mxgnL"

---

🖼 I do think I've isolated the reproduction to the size of the RPNG being encoded though!

Running and encoding ls -la to your heart's content doesn't cause any issues.
However running and encoding cat /home/guest/package-lock.json reliably stalls after the first encoding method.

---

Looking into playing around with the maxPayload setting in the WebSocket settings

[nokome]

Thanks @alex-ketch that is very useful. Might be useful to add a test e.g. to src/ws/WebSocketClientServer.test.ts (or in another file) that sends WS payloads of increasing sizes and see if that is indeed the issue.

[stencila-ci]

🎉 This issue has been resolved in version 1.11.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release
• v1.11.6

Your semantic-release bot 📦🚀

[alex-ketch]

Sadly still seeing this issue with:

• Server: https://hub.docker.com/layers/stencila/executa-midi/latest/images/sha256-b8ed0bd5049a0e4b1183c8b7e3fdbc3106589cb45ed160c111e7c2b396338dcd?context=explore
• Client: v1.11.6

[nokome]

Can not replicate error with master (1.11.7) locally (npm run cli:dev -- serve --ws --http) and Firefox:

Will try with latest Docker image now.

[nokome]

Can replicate stalling when using latest stencila/executa-midi

nokome@pluto ~/s/s/executa (master) [1]> docker pull stencila/executa-midi
Using default tag: latest
latest: Pulling from stencila/executa-midi
cbdc015de259: Pull complete 
35f8707632bb: Pull complete 
6b786d087f83: Pull complete 
31fb3cd05fdd: Pull complete 
03e41e2e43fb: Pull complete 
f3d9c2390c2f: Pull complete 
c644a6919971: Pull complete 
2cb077204b1d: Pull complete 
0a33cd7f8118: Pull complete 
200b9e2f690e: Pull complete 
94542fd3846f: Pull complete 
422ada9d0ba7: Pull complete 
7b16431d9115: Pull complete 
69a6c76ae0ec: Pull complete 
6c5fa772083c: Pull complete 
174d7d96e989: Pull complete 
c2105085e6d2: Pull complete 
4bb6e19859f9: Pull complete 
65f1c5e8a03e: Pull complete 
859b5e88c230: Pull complete 
15568bba7075: Pull complete 
80adbddd3754: Pull complete 
a18b70ccf25d: Pull complete 
436ac7686ea6: Pull complete 
e88ee0269662: Pull complete 
3ad7006b8fcb: Pull complete 
15a415509f5e: Pull complete 
Digest: sha256:b8ed0bd5049a0e4b1183c8b7e3fdbc3106589cb45ed160c111e7c2b396338dcd
Status: Downloaded newer image for stencila/executa-midi:latest
nokome@pluto ~/s/s/executa (master)> npm run docker:run-image stencila/executa-midi:latest

> @stencila/executa@1.11.7 docker:run-image /home/nokome/stencila/source/executa
> docker run -it --init --rm --cap-add=SYS_ADMIN -p 9000:9000 "stencila/executa-midi:latest"

I believe that this is because building of the image failed i.e. latest does not include the fix to this issue:

https://dev.azure.com/stencila/stencila/_build/results?buildId=2286&view=logs&j=1b7bf37f-59a6-5457-eae3-62ce29cb19a4&t=9d3843fb-f716-59bf-683b-829e70871150&l=3869