ensure multi-tenant contextvar is passed

[evan-onyx]

Description

fixes issue in multitenant where heartbeats weren't being sent

How Has This Been Tested?

n/a, pretty important fix but 0 impact if it doesn't work

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

---

Summary by cubic

Propagates the multi-tenant context to the heartbeat thread so heartbeats are sent reliably during indexing in multi-tenant runs. Fixes missed heartbeats caused by contextvars not being passed to the background thread.

• Bug Fixes
  • Run heartbeat_loop inside contextvars.copy_context().run(...) to preserve tenant context.
  • Remove extra debug logging from the loop.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
internal-search	Ready	Preview	Comment	Aug 22, 2025 1:35am

[greptile-apps]

Greptile Summary

This PR fixes a critical multi-tenant context propagation issue in the heartbeat functionality. The problem was that background heartbeat threads were not inheriting context variables from their parent thread, specifically the CURRENT_TENANT_ID_CONTEXTVAR which is essential for proper tenant identification in multi-tenant deployments.

The core fix involves using Python's standard context variable propagation pattern for threads. Instead of directly passing the heartbeat_loop function to threading.Thread, the code now:

1. Captures the current context using contextvars.copy_context()
2. Uses context.run() to execute the heartbeat function within that captured context

This ensures that when get_session_with_current_tenant() is called within the heartbeat thread (line 21), the get_current_tenant_id() function can successfully retrieve the tenant ID from CURRENT_TENANT_ID_CONTEXTVAR. Without this fix, heartbeat threads would either fail with a RuntimeError in multi-tenant mode or potentially access the wrong tenant's data.

The change also removes a debug log statement that was likely adding unnecessary noise to the logs. This fix is crucial for proper multi-tenant isolation and ensures that background processes maintain the correct tenant context.

Confidence score: 4/5

• This PR addresses a well-defined issue with a standard Python solution for context variable propagation
• The fix follows established patterns for maintaining context across threads and aligns with the codebase's multi-tenant architecture
• Pay close attention to the threading context propagation logic and ensure it works correctly across different deployment scenarios

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[cubic-dev-ai]

No issues found across 1 file