Disable OpenTelemetry instrumentation and reduce state cache invalidations

[MrgSub]

READ CAREFULLY THEN REMOVE

Remove bullet points that are not relevant.

PLEASE REFRAIN FROM USING AI TO WRITE YOUR CODE AND PR DESCRIPTION. IF YOU DO USE AI TO WRITE YOUR CODE PLEASE PROVIDE A DESCRIPTION AND REVIEW IT CAREFULLY. MAKE SURE YOU UNDERSTAND THE CODE YOU ARE SUBMITTING USING AI.

• Pull requests that do not follow these guidelines will be closed without review or comment.
• If you use AI to write your PR description your pr will be close without review or comment.
• If you are unsure about anything, feel free to ask for clarification.

Description

Please provide a clear description of your changes.

---

Type of Change

Please delete options that are not relevant.

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature with breaking changes)
• 📝 Documentation update
• 🎨 UI/UX improvement
• 🔒 Security enhancement
• ⚡ Performance improvement

Areas Affected

Please check all that apply:

• Email Integration (Gmail, IMAP, etc.)
• User Interface/Experience
• Authentication/Authorization
• Data Storage/Management
• API Endpoints
• Documentation
• Testing Infrastructure
• Development Workflow
• Deployment/Infrastructure

Testing Done

Describe the tests you've done:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Security Considerations

For changes involving data or authentication:

• No sensitive data is exposed
• Authentication checks are in place
• Input validation is implemented
• Rate limiting is considered (if applicable)

Checklist

• I have read the CONTRIBUTING document
• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• My changes generate no new warnings
• I have added tests that prove my fix/feature works
• All tests pass locally
• Any dependent changes are merged and published

Additional Notes

Add any other context about the pull request here.

Screenshots/Recordings

Add screenshots or recordings here if applicable.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

---

Summary by cubic

Disabled OpenTelemetry instrumentation and reduced unnecessary state cache invalidations to improve server performance.

• Refactors
  • Commented out OpenTelemetry setup and usage in the server entrypoint.
  • Limited calls to invalidate and send state cache in thread and workflow logic.

Summary by CodeRabbit

• Chores
  • Disabled certain cache invalidation and state update operations in thread management and synchronization workflows.
  • Removed OpenTelemetry instrumentation integration from the server application.
  • Cleaned up formatting by removing unnecessary whitespace.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change disables OpenTelemetry instrumentation in the server entrypoint, comments out cache invalidation and sendDoState calls in both the thread synchronization workflow and server utilities, and performs minor whitespace cleanup. No exported or public entity declarations were altered.

Changes

Cohort / File(s)	Change Summary
OpenTelemetry Instrumentation Removal apps/server/src/main.ts	Commented out imports and usage of OpenTelemetry instrumentation; reverted to direct handler invocation in Entry.fetch.
Cache Invalidation & sendDoState Disabled apps/server/src/lib/server-utils.ts, apps/server/src/workflows/sync-threads-workflow.ts	Commented out calls to agent.invalidateDoStateCache() and sendDoState(connectionId); minor whitespace cleanup.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server

    Client->>Server: HTTP Request
    alt Before (with instrumentation)
        Server->>OpenTelemetry: Instrument request
        OpenTelemetry->>Server: Pass to handler
    end
    Server->>Server: Handle request directly (instrumentation disabled)
    Server-->>Client: Response

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• Optimize thread counting and add license headers to workflow files #1949: Both PRs involve disabling or modifying the use of sendDoState and cache invalidation, indicating a direct relationship in how thread state updates are managed.
• Refactor ZeroDriver to use SQLite database for thread and label management #1917: Both PRs modify modifyThreadLabelsInDB and related thread label logic, with this PR disabling cache invalidation and the other refactoring database schema and label management.

Suggested labels

design

Suggested reviewers

• ahmetskilinc

Poem

🚀
Instrumentation off, the code runs free,
Cache invalidation now history.
Threads sync quietly, no extra call,
Whitespace trimmed, that's nearly all.
Review this patch, let logic flow—
To Mars and back, we're good to go!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 496b600 and 416f93c.

📒 Files selected for processing (3)

• apps/server/src/lib/server-utils.ts (2 hunks)
• apps/server/src/main.ts (2 hunks)
• apps/server/src/workflows/sync-threads-workflow.ts (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ZERODisable_OpenTelemetry_instrumentation_and_reduce_state_cache_invalidations

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[MrgSub]

• Disable OpenTelemetry instrumentation and reduce state cache invalidations #1975 👈 (View in Graphite)
• staging

This stack of pull requests is managed by Graphite. Learn more about stacking.

[MrgSub]

Merge activity

• Aug 10, 5:24 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 10, 5:24 PM UTC: @MrgSub merged this pull request with Graphite.

[cubic-dev-ai]

cubic analysis

No issues found across 3 files. Review in cubic