Setting SNAPCRAFT_ENABLE_SENTRY= causes stacktrace (empty string value not truthy)
Metadata
Current evaluation
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.
Suggested action: close stale
Reason: The issue references snapcraft/cli/_errors.py line 76 using strtobool on SNAPCRAFT_ENABLE_SENTRY, but the current repo layout shows no snapcraft/cli/ directory — the old 1.x CLI architecture has been replaced by the craft-application based 7.x codebase. With 3049 days of inactivity, zero comments, and the affected code path removed, the issue is no longer applicable.
Impact:
10
Quick Win:
8.5
Staleness:
92
Complexity:
15
Confidence:
70
Support Request:
10
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.8-27b |
Impact:
10
Quick Win:
8.5
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
75
Support Request:
5
|
close stale | Empty string values for SNAPCRAFT_ENABLE_SENTRY and SNAPCRAFT_SEND_ERROR_DATA trigger a Python strtobool ValueError. The issue has been inactive for over 8 years with no maintainer response or labels. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.