Opening a snapshot for a repository from unauthorized providers fails
Open
Nobody has claimed this yet.
feature: snapshots
meta: never-stale
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Describe the bug
For example, if you share a workspace snapshot for a GitHub repository, opening the snapshot from an account that has been authorized only with GitLab, but not with GitHub, it fails with the following error:
Error: User is unauthorized!
Please file an issue if you think this is a bug.
Steps to reproduce
User Alice:
- Create an account and authorize with GitHub.
- Start a workspace from a GitHub repository.
- Create a workspace snapshot.
- Copy the shared workspace snapshot URL.
User Bob:
- Create an account authorized only with GitLab.
- Try opening the URL for the shared workspace snapshot.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Reproduce the shared workspace snapshot flow with GitHub authorization on one account and GitLab-only authorization on another, then trace the snapshot-opening and provider-authorization entry points. Done means Bob can open the GitHub snapshot without the unauthorized-user error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100