Fix Systec error message lookup - #2081
Open
giri256 wants to merge 1 commit into
Open
Conversation
Contributor
|
Tick the box to add this pull request to the merge queue (same as
|
Signed-off-by: p1 <giridharpavan593@gmail.com>
giri256
force-pushed
the
fix/systec-error-code
branch
from
July 27, 2026 13:45
879d022 to
b0f2f90
Compare
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.
Fixes #2077.
The Systec backend passes a
ctypesreturn-code object into its exception class. Looking up that object directly in the error-message table raisesTypeErrorbecause it is not hashable, hiding the actual USB-CAN error.The lookup now uses the numeric
.value, while the original result object remains available on the exception. I also added a regression test and changelog entry.Tests:
pytest test/test_systec.py -q— 18 passed