DEBUG: capture mypy 2.1.0 INTERNAL ERROR traceback#457
Closed
jamesbraza wants to merge 2 commits into
Closed
Conversation
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Collaborator
Author
|
Closing scratch PR. Traceback captured (sqlite3.OperationalError: database is locked at mypy/metastore.py:174). This matches upstream issue python/mypy#13916 (canonical) / #21525 (recently-closed duplicate). Fix applied on PR #450 as require_serial: true on the mypy hook. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scratch PR to capture the
--show-tracebackoutput for the mypy 2.1.0 INTERNAL ERROR seen on PR #450.Do not merge. Closing once the traceback is captured.
Base is
mainso the diff against PR #450 is exactly this one line. CI's pre-commit hook will now print the real traceback instead of the bare INTERNAL ERROR notice.