[OPIK-5628] [FE] Clear stale job state on sandbox disconnect#6091
[OPIK-5628] [FE] Clear stale job state on sandbox disconnect#6091
Conversation
When the SDK connection dropped and a new one was established, the previous session's results/errors were still displayed. Reset activeJobId on disconnect so each session starts clean.
|
🔄 Test environment deployment process has started Phase 1: Deploying base version You can monitor the progress here. |
|
✅ Test environment is now available! To configure additional Environment variables for your environment, run [Deploy Opik AdHoc Environment workflow] (https://github.com/comet-ml/comet-deployment/actions/workflows/deploy_opik_adhoc_env.yaml) Access Information
The deployment has completed successfully and the version has been verified. |
|
🌙 Nightly cleanup: The test environment for this PR ( |
|
🔄 Test environment deployment process has started Phase 1: Deploying base version You can monitor the progress here. |
|
✅ Test environment is now available! To configure additional Environment variables for your environment, run [Deploy Opik AdHoc Environment workflow] (https://github.com/comet-ml/comet-deployment/actions/workflows/deploy_opik_adhoc_env.yaml) Access Information
The deployment has completed successfully and the version has been verified. |
Details
When an SDK connection dropped and a new one was established in the Agent Sandbox, results/errors from the previous session were still displayed. This was because
activeJobIdwas never cleared on disconnect. The fix resets it in the existingisConnectedeffect so each new session starts clean.Change checklist
Issues
AI-WATERMARK
AI-WATERMARK: yes
Testing
npx tsc --noEmit— passesnpx eslint src/v2/pages/AgentRunnerPage/AgentRunnerContent.tsx— passesDocumentation
N/A