thunderbird / thunderbird/appointment
Handle Google Scope Changed error
Open
Nobody has claimed this yet.
bug
sentry
- Dominant language
- Python
- Stars
- 552
- Forks
- 29
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 23
Description
It was mainly used to keep track of different permission states people could end up in, but we handle it on the UI-side by asking them to select everything (there's no optional permissions here!) So I think we can remove this spammy error message now.
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
Start by locating the handling for the Google Scope Changed error described in the linked Sentry issue and trace how the UI currently requests permissions. Confirm where the error message is emitted; done means the redundant error is no longer reported while the existing select-all permission flow remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100