mirror of
https://github.com/IAmTomShaw/f1-race-replay.git
synced 2026-05-09 08:25:56 +02:00
[PR #249] fix: handle DataNotLoadedError and session load failures gracefully (… #251
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/f1-race-replay#251
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/IAmTomShaw/f1-race-replay/pull/249
Author: @nirvik34
Created: 3/11/2026
Status: 🔄 Open
Base:
main← Head:fix/245-data-not-loaded-error📝 Commits (5)
dd0ef90fix: handle DataNotLoadedError and session load failures gracefully (#245)7b0af3eMerge branch 'IAmTomShaw:main' into fix/245-data-not-loaded-error542e9e5fix(exceptions): refine session loading based on feedbackb053fb3Refactor: Implement specific error handling & worker resilience2610ba8Merge pull request #1 from IAmTomShaw/main📊 Changes
2 files changed (+220 additions, -140 deletions)
View changed files
📝
main.py(+17 -7)📝
src/f1_data.py(+203 -133)📄 Description
Closes #245
Problem
When session data fails to load, the app crashes with a raw FastF1
traceback — confusing for users who don't know what
DataNotLoadedErrormeans.Changes
src/f1_data.pyload_session()helperDataNotLoadedError→ session may not exist yet or still processingConnectionError→ tells user to check networkmain.pyexit_on_failure=Falseflag for secondary qualifying data loadBefore vs After
Before:
After:
Testing
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.