Skip to content

refactor(server): drop unused permission helpers - #687

Closed
staging-devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1789820821-drop-dead-permission-helpers
Closed

staging-devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1789820821-drop-dead-permission-helpers

Conversation

@staging-devin-ai-integration

@staging-devin-ai-integration staging-devin-ai-integration Bot commented Sep 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • PermissionsConfig::get_default had no callers at all, and can_accept_oneshot was never consulted at runtime — oneshot concurrency is enforced by the tower ConcurrencyLimitLayer built from max_concurrent_oneshots in server/mod.rs. Both were kept alive only by rationale-free #[allow(dead_code)].
  • Removed them (and can_accept_oneshot's unit test, which gave false confidence that production consults the helper). Keeping a lookalike of the actively used can_accept_session invites a future change to the helper that silently never takes effect.
  • No behavior change: max_concurrent_oneshots is still enforced exactly as before by the tower layer.

Review & Validation

  • Confirm no remaining references: rg 'can_accept_oneshot|get_default' apps/skit/src
  • cargo test -p streamkit-server --lib permissions and just lint-skit

Link to Devin session: https://staging.itsdev.in/sessions/f69e65121de248df9cc95587ea8f4361
Open in Devin Desktop: https://staging.itsdev.in/desktop/session/f69e65121de248df9cc95587ea8f4361?variant=devin-insiders
Requested by: @streamer45


Devin Review

Status Commit
🟢 Reviewed fd1ec6a

Devin Review (Staging)

get_default had no callers and can_accept_oneshot was never consulted; the
oneshot limit is enforced by the tower ConcurrencyLimitLayer.

Signed-off-by: streamkit-devin <devin@streamkit.dev>
@staging-devin-ai-integration

Copy link
Copy Markdown
Contributor Author

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@staging-devin-ai-integration staging-devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review (Staging)

Debug

Playground

@streamer45 streamer45 closed this Sep 19, 2026
@codecov

codecov Bot commented Sep 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.28%. Comparing base (64dcfda) to head (fd1ec6a).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #687      +/-   ##
==========================================
+ Coverage   85.26%   85.28%   +0.01%     
==========================================
  Files         251      251              
  Lines       76246    76232      -14     
  Branches     2485     2485              
==========================================
+ Hits        65014    65017       +3     
+ Misses      11226    11209      -17     
  Partials        6        6              
Flag Coverage Δ
backend 85.38% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
core 85.79% <ø> (ø)
engine 83.76% <ø> (ø)
api 91.14% <ø> (ø)
nodes 85.00% <ø> (+0.04%) ⬆️
server 85.27% <ø> (+<0.01%) ⬆️
plugin-native 84.79% <ø> (ø)
plugin-wasm 95.41% <ø> (ø)
ui-services 86.29% <ø> (ø)
ui-components 68.94% <ø> (ø)
Files with missing lines Coverage Δ
apps/skit/src/permissions.rs 98.70% <ø> (+0.95%) ⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

2 participants