Access token might be inconsistent across threads
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 814
- Forks
- 209
- PR merge metrics
- No merged PRs in 30d
Description
In v2.0.x, access tokens are issued per thread. However, credentials are shared. This can lead to inconsistencies in access tokens between threads. Specific issues that can occur are as follows:
- Token refreshes occur as many times as the number of threads.
- Credentials are shared, so when multiple threads simultaneously refresh or read a token, it may become outdated.
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
No source file, test, or entry point is identified in the report. Trace how v2.0.x issues and stores access tokens and shares credentials across threads, then reproduce concurrent refresh and read scenarios. Done means token handling remains consistent across threads without redundant refreshes or stale credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, python
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100