Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PANIC: Failed to check for updates: ReleaseNotFound #1491

Open
mmrrnn opened this issue Feb 7, 2025 · 0 comments · May be fixed by #1492
Open

PANIC: Failed to check for updates: ReleaseNotFound #1491

mmrrnn opened this issue Feb 7, 2025 · 0 comments · May be fixed by #1492
Assignees

Comments

@mmrrnn
Copy link
Collaborator

mmrrnn commented Feb 7, 2025

Describe the bug
Sometimes we do alpha pre-release channel releases where not all downloads are available yet. Often Mac and Windows are ready but linux files are not.

It seems like on Linux machines in this case the auto updater knows that there is a new version but panics when fetching it as there is no file to fetch.

We should not panic, and i don't see any reason to report the issue to sentry.

Additional context
Sentry Issue: [TARI-UNIVERSE-3AB]

panic: Failed to check for updates: ReleaseNotFound
  File "panicking.rs", line 665, in rust_begin_unwind
  File "updates_manager.rs", line 146, in tari_universe::updates_manager::UpdatesManager::check_for_update::{{closure}}
  File "updates_manager.rs", line 105, in tari_universe::updates_manager::UpdatesManager::try_update::{{closure}}
  File "updates_manager.rs", line 90, in tari_universe::updates_manager::UpdatesManager::init_periodic_updates::{{closure}}::{{closure}}
  File "pthread_interpose.rs", line 150, in set_alt_signal_stack_and_start
...
(63 additional frame(s) were not displayed)
@mmrrnn mmrrnn self-assigned this Feb 7, 2025
@mmrrnn mmrrnn linked a pull request Feb 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant