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

Add /getcontext command for debugging #8

Merged
merged 4 commits into from
Dec 27, 2023
Merged

Conversation

ShrirajHegde
Copy link
Contributor

@ShrirajHegde ShrirajHegde commented Dec 26, 2023

  • Add /getcontext command for debugging
  • Enable simultaneous prompts
  • Catch all errors in handle_message
  • Reply to prompt message

@ruecat
Copy link
Owner

ruecat commented Dec 27, 2023

Thanks for the PR!
I created new branch for debugging and testing: dev.
/getcontext will be moved there.

@ruecat ruecat merged commit 6cf9716 into ruecat:main Dec 27, 2023
@ShrirajHegde
Copy link
Contributor Author

Debugging can also be useful while in regular use, not just development. Because it's not very obvious of what the chat context is just by seeing the chat history on telegram.

@ShrirajHegde
Copy link
Contributor Author

0376c52 also has the changes for response as reply to the message.

I don't think maintaining branches like this will be practical. Instead, you should use python logging module and use the logging levels along with an environmental variable like LOG_LEVEL. This way it can be easily set in env file.

Two different branches diverge unexpectedly and create a merge conflict very soon, which will be a huge problem. Dev branch is not for dev purposes like this, instead it is the changes 'in development'.

@ShrirajHegde ShrirajHegde mentioned this pull request Dec 31, 2023
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

Successfully merging this pull request may close these issues.

2 participants