Skip to content

Track active users on shell via websocket#1930

Merged
KCarretto merged 1 commit intomainfrom
shell-active-users-1284810859092603002
Feb 27, 2026
Merged

Track active users on shell via websocket#1930
KCarretto merged 1 commit intomainfrom
shell-active-users-1284810859092603002

Conversation

@KCarretto
Copy link
Copy Markdown
Collaborator

Track active users on shell via websocket by adding them to the active_users edge of the Shell entity on connection, polling to maintain presence, and removing them on disconnection.


PR created automatically by Jules for task 1284810859092603002 started by @KCarretto

This commit updates the Shell WebSocket handler to track active users on
the shell. When a user connects to the shell via WebSocket, they are
added to the `active_users` edge of the Shell entity. A background
goroutine polls every 10 seconds to ensure the user remains in the list
(handling potential race conditions or external removals). When the
WebSocket connection closes, the user is removed from the list.

This ensures that the "Active Users" list in the UI accurately reflects
who is currently viewing/interacting with the shell, even across
multiple Tavern instances.

Changes:
- Modified `tavern/internal/http/shell/handler.go` to add `manageUserPresence` method.
- Added `TestShellActiveUsers` to `tavern/internal/http/shell/integration_test.go` to verify the behavior.

Co-authored-by: KCarretto <16250309+KCarretto@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Copy Markdown
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2700    ±0 2700    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1330 2700 2700 0 0 0 0 44.7s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2700 0 0 5.7s

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 5.7s 5.7s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.2s 5.2s
TestInteractiveShell 1 5.1s 5.1s
TestOtherStreamOutput 1 5.0s 5.0s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.7s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.7s
imix::bin/imix: install::tests::test_install_execution 3 1.6s 4.7s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

@KCarretto KCarretto marked this pull request as ready for review February 27, 2026 01:33
@KCarretto KCarretto merged commit 057ab14 into main Feb 27, 2026
8 checks passed
@KCarretto KCarretto deleted the shell-active-users-1284810859092603002 branch February 27, 2026 01:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant