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

Tribler should gracefully handle "No space left on device" type of errors #7409

Open
kozlovsky opened this issue May 8, 2023 · 7 comments
Open

Comments

@kozlovsky
Copy link
Contributor

Tribler currently experiences crashes that result in exceptions. Ideally, it should close gracefully and display a clear, informative message for the user, detailing the cause of the issue rather than presenting a crash report.

The error can manifest itself in multiple places, so it may be challenging to fix the issue completely. Still, we can try to add corresponding error handlers in appropriate places.

Possible types of errors:

  • CommitException: OperationalError: database or disk is full
  • OSError: [Errno 28] No space left on device (in in cache_exitnodes_to_disk)

Related to #7368 (but happens after the Tribler core started)

@sentry-for-tribler
Copy link

Sentry issue: TRIBLER-16D

@sentry-for-tribler
Copy link

Sentry issue: TRIBLER-16H

@sentry-for-tribler
Copy link

Sentry issue: TRIBLER-16G

@xoriole
Copy link
Contributor

xoriole commented Jun 30, 2023

The case on the upgrade with no space left is addressed on #7496

Copy link

Sentry issue: TRIBLER-1EC

Copy link

Sentry issue: TRIBLER-1F9

@drew2a
Copy link
Contributor

drew2a commented Dec 15, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants