Skip to content

feat: capture user on scheduled tasks#2123

Draft
hulto wants to merge 2 commits intomainfrom
fix/capture-scheduled-task-user-6584457188345734185
Draft

feat: capture user on scheduled tasks#2123
hulto wants to merge 2 commits intomainfrom
fix/capture-scheduled-task-user-6584457188345734185

Conversation

@hulto
Copy link
Collaborator

@hulto hulto commented Mar 21, 2026

Updates scheduled tasks to capture the user that originally queued them. This ensures that any automated tasks (quests) spawned from a scheduled task can be traced back to the user who created it.


PR created automatically by Jules for task 6584457188345734185 started by @hulto

Added a `creator` edge to the `ScheduledTask` schema pointing to the `User` schema.
Updated the `CreateScheduledTask` mutation to automatically assign the authenticated user to the newly created scheduled task.
Modified the `handleTomeAutomation` logic in `api_claim_tasks.go` to capture the `creator` edge of the selected scheduled task and pass it along to any automated `Quest` instances it generates.

Co-authored-by: hulto <7121375+hulto@users.noreply.github.com>
@google-labs-jules
Copy link
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
Contributor

github-actions bot commented Mar 21, 2026

Summary

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

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1824 2833 2833 0 0 0 0 40.2s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2833 0 0 5.6s

Test Changes

0 test added, 0 removed

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 5.6s 5.6s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.1s 5.1s
TestInteractiveShell 1 5.0s 5.0s
TestOtherStreamOutput 1 5.0s 5.0s
TestDockerExecutor_Build_SimpleEcho 1 3.2s 3.2s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_output 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s

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

Github Test Reporter by CTRF 💚

🔄 This comment has been updated

Added a `creator` edge to the `ScheduledTask` schema pointing to the `User` schema.
Updated the `CreateScheduledTask` mutation to automatically assign the authenticated user to the newly created scheduled task.
Modified the `handleTomeAutomation` logic in `api_claim_tasks.go` to capture the `creator` edge of the selected scheduled task and pass it along to any automated `Quest` instances it generates.

Also updated `DropAllData` to correctly delete `ScheduledTasks` to prevent foreign key errors during environment resets.

Co-authored-by: hulto <7121375+hulto@users.noreply.github.com>
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