We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
TGPy messages with errors look quite like random spam, and full error tracebacks are rarely useful.
I am proposing to show only the last line of the error and save the full error to a variable and/or logs.
Current behavior:
msg.something TGPy> Error occurred Traceback (most recent call last): File "/home/tmat/.local/pipx/venvs/tgpy/lib/python3.11/site-packages/tgpy/_core/meval.py", line 175, in _meval new_locs, ret = await getattr(py_module, 'tmp')(**kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "tgpy://message/-1001611149679/38326", line 1, in tmp msg.something AttributeError: 'Message' object has no attribute 'something'
Suggested behavior:
msg.something TGPy> AttributeError: 'Message' object has no attribute 'something'
The text was updated successfully, but these errors were encountered:
feat: truncate exceptions (#39)
3fa538f
739fbbc
Implemented in 739fbbc
Sorry, something went wrong.
tm-a-t
No branches or pull requests
TGPy messages with errors look quite like random spam, and full error tracebacks are rarely useful.
I am proposing to show only the last line of the error and save the full error to a variable and/or logs.
Example
Current behavior:
Suggested behavior:
The text was updated successfully, but these errors were encountered: