compilation fix

[akshaydeo]

Summary

Briefly explain the purpose of this PR and the problem it solves.

Changes

• What was changed and why
• Any notable design decisions or trade-offs

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Describe the steps to validate this change. Include commands and expected outcomes.

# Core/Transports
go version
go test ./...

# UI
cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

If adding new configs or environment variables, document them here.

Screenshots/Recordings

If UI changes, add before/after screenshots or short clips.

Breaking changes

• Yes
• No

If yes, describe impact and migration instructions.

Related issues

Link related issues and discussions. Example: Closes #123

Security considerations

Note any security implications (auth, secrets, PII, sandboxing, etc.).

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

Warning

Rate limit exceeded

@akshaydeo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 8 minutes and 17 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fd55f66a-272d-4a4e-8746-8bab0c1b1798

📥 Commits

Reviewing files that changed from the base of the PR and between bf36f7e and 41aa15b.

📒 Files selected for processing (2)

• ui/app/_fallbacks/enterprise/components/access-profiles/managedVirtualKeyNotice.tsx
• ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx

📝 Walkthrough

Walkthrough

The PR removes managed profile editing capability from the virtual key details sheet. Import statements are updated, local state and data-fetching hooks are deleted, the "managed by profile" alert is converted from interactive dynamic content to static text, and the AccessProfileSheet component is removed entirely from the rendered output.

Changes

Simplify Managing Profile UI in Virtual Key Details

Layer / File(s)	Summary
Remove managing profile sheet and simplify alert ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx	Imports are updated, local showManagingProfile state and useGetAccessProfileQuery hook are removed, the "managed by profile" alert is simplified from a dynamic edit/open message to static explanatory text, and the AccessProfileSheet component is removed from the sheet footer.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• maximhq/bifrost#3665: Both PRs modify the same virtual key details sheet to rework managing-profile logic—this PR removes the managing profile sheet and query entirely while the related PR reworks how isManagedByProfile is derived.

Suggested reviewers

• danpiths

Poem

🐰 A profile once managed so tight,
Now rests as static text so light,
No sheets to open, no states to track—
The rabbit simplifies the stack! 🎉

🚥 Pre-merge checks | ❌ 5

❌ Failed checks (4 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is entirely a placeholder template with no actual content filled in; all sections remain unfilled with concrete information about the changes, testing, or related issues.	Complete the description by filling in the Summary, Changes, Type of change, Affected areas, testing steps, and Related issues sections with actual details about the compilation fix.
Linked Issues check	⚠️ Warning	The PR addresses a compilation fix in VirtualKeyDetailSheet (removing unused imports), but the linked issue #123 concerns Files API Support implementation, which is unrelated to the actual code changes made.	Either link the correct issue related to the compilation fix in VirtualKeyDetailSheet, or clarify the relationship between the UI component changes and the Files API Support feature.
Out of Scope Changes check	⚠️ Warning	The PR changes VirtualKeyDetailSheet by removing AccessProfileSheet imports and simplifying state management, but the linked issue #123 concerns Files API Support implementation, indicating a scope mismatch.	Ensure the linked issue accurately represents the work being done, or separate this compilation fix into a distinct PR with appropriate issue linkage.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'compilation fix' is vague and generic, providing no meaningful information about the specific compilation issue or the changes made to resolve it.	Replace with a descriptive title such as 'Remove unused AccessProfileSheet import from VirtualKeyDetailSheet' to clearly indicate the specific compilation fix being addressed.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 05-22-compilation_fix

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[akshaydeo]

• compilation fix #3683 👈 (View in Graphite)
• main

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

[greptile-apps]

Confidence Score: 5/5

Safe to merge — the change is a targeted compilation fix with no logic changes beyond swapping an enterprise alert for a no-op fallback stub.

The only functional change is replacing an enterprise-specific alert/popup (which couldn't compile in the OSS build) with a fallback that renders nothing. All remaining edits are pure formatting. No data flow, state, or API call changes are introduced.

No files require special attention.

Important Files Changed

Filename	Overview
ui/app/_fallbacks/enterprise/components/access-profiles/managedVirtualKeyNotice.tsx	New fallback stub component that accepts a managingProfile prop but renders null, standing in for the enterprise implementation to satisfy the compiler.
ui/app/workspace/virtual-keys/views/virtualKeyDetailsSheet.tsx	Replaces enterprise-only imports (AccessProfileSheet, useGetAccessProfileQuery) and inline alert with the new ManagedVirtualKeyNotice fallback; remaining changes are pure code reformatting.

_{Reviews (2): Last reviewed commit: "compilation fix" | Re-trigger Greptile}