Skip to content
New issue

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

TG-side error handling #15

Open
Keyrxng opened this issue Oct 26, 2024 · 0 comments
Open

TG-side error handling #15

Keyrxng opened this issue Oct 26, 2024 · 0 comments

Comments

@Keyrxng
Copy link
Member

Keyrxng commented Oct 26, 2024

When interacting with the bot should all errors receive JSON.stringify treatment and posted in response to whatever the command invoked was?

  1. It may be possible that sensitive info is exposed in the error across all commands (private, group, etc...)
  2. It provides the quickest feedback otherwise you need to investigate the worker logs rn as-is
  3. We could create a storage location for errors and we reply instead with a link or details as to where the error was saved to? This is ideal as it's only accessible by the team/partner. Consider this separate from the old supabase error logging because this is moving into GitHub storage very soon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant