Retry failed (404) requests (regionlock) on next session in TidalMultiSession
- Dominant language
- Python
- Stars
- 23
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
---
_This issue has been automatically created by [todo-actions](https://github.com/apps/todo-actions) based on a TODO comment found in [tidal_async/session.py:353](https://github.com/FUMR/tidal-async/blob/0a95543456aa14a3f2f55419fb0132c1633062be/tidal_async/session.py#L353). It will automatically be closed when the TODO comment is removed from master._
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at tidal_async/session.py:353, where the TODO identifies the missing behavior in TidalMultiSession. Trace how failed 404 regionlock requests and session state are handled, then verify that those requests are retried on the next session; the issue is complete when that behavior is implemented and covered by the project's existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100