Setting SNAPCRAFT_ENABLE_SENTRY= causes stacktrace (empty string value not truthy)
Metadata
Current evaluation
Fixed by removing the legacy Sentry error-reporting stack entirely; SNAPCRAFT_ENABLE_SENTRY is no longer parsed in snapcraft.
Resolution: closed resolved
Reason: The issue was resolved by removing the legacy Sentry integration that parsed SNAPCRAFT_ENABLE_SENTRY. Maintainer @mr-cal confirmed in a comment that SNAPCRAFT_ENABLE_SENTRY is no longer parsed, eliminating the strtobool ValueError on empty string values.
Evaluated by: mr-cal-bot
No scores available.
Issue body
$ SNAPCRAFT_ENABLE_SENTRY= snapcraft
Skipping pull dummy-part (already ran)
Preparing to build dummy-part
Building dummy-part
Error in sys.excepthook:
Traceback (most recent call last):
File "/home/rumo/dev/snapcraft/snapcraft/cli/_errors.py", line 76, in exception_handler
os.getenv('SNAPCRAFT_ENABLE_SENTRY', 'n')) == 1
File "/usr/lib/python3.5/distutils/util.py", line 317, in strtobool
raise ValueError("invalid truth value %r" % (val,))
ValueError: invalid truth value ''
The same happens with `SNAPCRAFT_SEND_ERROR_DATA=`.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | closed resolved | Fixed by removing the legacy Sentry error-reporting stack entirely; SNAPCRAFT_ENABLE_SENTRY is no longer parsed in snapcraft. | |
| stealth/space-bunny-alpha |
Impact:
15
Quick Win:
8
Complexity:
20
Confidence:
85
Actionability:
70
|
close stale | Setting SNAPCRAFT_ENABLE_SENTRY= (empty value) raised ValueError in sys.excepthook because strtobool rejects empty strings. The legacy sentry error-reporting stack this traceback points at has since been fully removed from snapcraft. | |
| qwen/qwen3.6-35b-a3b |
Impact:
10
Quick Win:
10
Complexity:
0
Confidence:
100
Actionability:
100
|
close resolved | SNAPCRAFT_ENABLE_SENTRY= (empty string) caused a ValueError from strtobool. The Sentry error reporting feature and all related code have been removed from the codebase. | |
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
8
Staleness:
92
Complexity:
15
Confidence:
70
Support Request:
10
|
close stale | Bug report from snapcraft 1.x era where setting SNAPCRAFT_ENABLE_SENTRY= (empty string) caused a ValueError in strtobool. The referenced code path (snapcraft/cli/_errors.py) no longer exists in the current codebase. 8+ years old, zero interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
10
Confidence:
80
Support Request:
5
|
close stale | Bug where setting SNAPCRAFT_ENABLE_SENTRY= or SNAPCRAFT_SEND_ERROR_DATA= to an empty string triggers a Python ValueError stacktrace. Untriaged and inactive for over 8 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
0
|
close stale | Bug report showing that setting SNAPCRAFT_ENABLE_SENTRY to an empty string causes a ValueError in strtobool. Issue is 8 years old, has no maintainer interaction, and references Python 3.5. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Setting SNAPCRAFT_ENABLE_SENTRY to an empty string causes a Python ValueError crash due to improper env var parsing. Untriaged and inactive for over 8 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1807492 Snapcraft should print the path of the stack trace file even when the error report is sent automatically | snapcraft (launchpad) | closed | Issue closed as stale because Sentry integration was removed entirely in snapcraft#5592 (commit 0a120c694). | |
| #2187 errors: enable sentry by default | snapcraft | merged | Merged PR #2187 in commit f77a6c10a, enabling Sentry error reporting by default and adding SNAPCRAFT_ENABLE_SILENT_REPORTS for prompt-free reports. |