Repository navigation
fix(realtime): enforce the Files capability on workspace document rooms - #9580
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
[Medium impact] The PR appears safe to merge, with no new actionable issues. SummaryWorkspace document rooms now check
|
Collaborator
Author
Collaborator
Author
|
@cubic-dev-ai review this PR |
Contributor
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hideFilesTab) was refused by every HTTP file operation but could still join a workspace file's collaborative document room over the socket, receive the file's content as the seed, and write edits that persist to the file. Room authorization checked only the workspace role and neverfiles.use.POST /api/internal/file-doc/access, returnsauthorizeRoomplus thefiles.usecapability.200body decision, not an HTTP status. While the app and relay roll out separately, an app without the route answers404. The relay treats that as an outage: the join error is retryable, writes are held, and nobody is evicted. It does not read it as "file deleted".workspace-file-docauthority, and admission and revalidation both dispatch on it through oneauthorizeRoomAccess.userIdattributes the last editor of a shared doc, so gating it would block co-editors' saves.Type of Change
Testing
apps/sim/lib/collab-doc/access.integration.ts(real Postgres; new):files.read_metadatarefuses.401without the secret, refusal returned in the body, otherwise the role.apps/realtime/src/handlers/file-doc-capabilities.integration.ts(Socket.IO + Redis + Postgres; new checks):tscfor realtime and realtime-protocol.check:boundaries,check:api-validation:strict,check:permission-group-enforcement,check:utils,check:comment-hygiene,check:test-patterns,check:explicit-any,check:file-names,check:source-conventions, and biome on changed files.check:audits, and rootbun run test. CI covers them.Checklist
test-auditauthoring gate)