Giters
teremterem
/
botmerger
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
Watchers:
1
Issues:
16
Forks:
teremterem/botmerger Issues
Make sure cached bot responses are also written to chat history between bots
Updated
a year ago
How to maintain chat history if the same bot invokes another bot multiple times in parallel ?
Updated
a year ago
Ensure that bots are indeed capable of working in parallel
Updated
a year ago
If a bot calls itself recursively using the same original message as an input this will most likely produce a deadlock
Updated
a year ago
Rename `invisible_to_bots` to `hidden_from_history` ?
Closed
a year ago
Explicitly define `hidden_from_history` parameter in all the methods involved in creation of MergedMessage objects
Closed
a year ago
Make `alias` optional in `create_bot` decorator
Updated
a year ago
Upgrade Pydantic to "^2"
Updated
a year ago
Get rid of `MergedMessage.goes_after` field in favour of some kind of sequential id that could be used to sort messages chronologically ?
Updated
a year ago
Come up with some kind of pattern that would allow for creation of bots that "mitigate" exceptions in other bots
Updated
a year ago
Come up with a better segregation by modules compared to currently existing `base.py`, `core.py` and `models.py`
Updated
a year ago
Rename `indicate_typing_afterwards` to `still_thinking`
Closed
a year ago
Once an error happened inside an SequentialMergedBotWrapper based bot, the bot becomes unresponsive to further requests
Closed
a year ago
SequentialMergedBotWrapper makes it hard to debug the bots because the continuity of stack traces gets disrupted by async queues
Updated
a year ago
Comments count
1
Register fulfillment functions as manager object's state, not as bot object's state
Closed
a year ago
Turn all Pydantic models that have hidden state (PrivateAttr) into regular classes ?
Closed
a year ago