You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An error occurred during code execution while being connected to wss://poseidon-terraform.compute.internal:7200/api/v1/runners/10-25237a45-751f-11ef-badf-fa163efe023e/websocket?executionID=61e88f26-dfa3-43c1-8701-1436c94e29c9.
On September 17th at 18:30 UTC, we got another the allocation stopped as expected occurrence (specific Sentry event). While this was initially tracked in #423, I thought it was resolved back then despite a follow-up issue in #487.
When checking the Poseidon log, I didn't notice something super specific. Hence, I just wanted to clarify what might have caused the issue.
When tracking the runner id (10-25237a45-751f-11ef-badf-fa163efe023e) and execution id (61e88f26-dfa3-43c1-8701-1436c94e29c9) in the logs, we come across the interesting log The client closed the connection. This means that CodeOcean has closed the WebSocket connection to the execution. In response, we cancel the execution and send the WebSocketOutputErrorThe allocation stopped as expected. As stated in #423, I still think it's nice to do so.
So, I would say, the question is: Why did CodeOcean still receive the error when it has closed the WebSocket connection? Why does CodeOcean throw an error when Poseidon notifies about the canceled execution?
Sentry Issue: CODEOCEAN-123
On September 17th at 18:30 UTC, we got another
the allocation stopped as expected
occurrence (specific Sentry event). While this was initially tracked in #423, I thought it was resolved back then despite a follow-up issue in #487.When checking the Poseidon log, I didn't notice something super specific. Hence, I just wanted to clarify what might have caused the issue.
Poseidon logs around that time
The text was updated successfully, but these errors were encountered: