Terminal access to bot #61

Open
opened 2024-04-04 10:07:36 -04:00 by modulatingforce · 1 comment

Kinda a fun neat idea. In the py implementation of the bot, I wanted to have the terminal be simultaneously be active

I was just curious last night and found a related crate that might help us do just that

https://docs.rs/crossterm/latest/crossterm/event/struct.EventStream.html

https://github.com/crossterm-rs/crossterm/tree/master/examples

Pretty low priority, but could become a priority if we need to troubleshoot the responsiveness of the bot - for example in deadlock or otherwise where we're not sure if it's even running properly or not. We wanted this feature before because at times in the previous bot, it would stop responding after about a month (not from a deadlock though)

Kinda a fun neat idea. In the py implementation of the bot, I wanted to have the terminal be simultaneously be active I was just curious last night and found a related crate that might help us do just that https://docs.rs/crossterm/latest/crossterm/event/struct.EventStream.html https://github.com/crossterm-rs/crossterm/tree/master/examples Pretty low priority, but could become a priority if we need to troubleshoot the responsiveness of the bot - for example in deadlock or otherwise where we're not sure if it's even running properly or not. We wanted this feature before because at times in the previous bot, it would stop responding after about a month (not from a deadlock though)
modulatingforce self-assigned this 2024-04-04 10:09:37 -04:00
modulatingforce added this to the Rust Learning project 2024-04-04 10:09:40 -04:00
modulatingforce added
Complexity
Advanced
Ownership
Individual Lead
and removed
Ownership
Collab
labels 2024-04-04 10:10:34 -04:00
Owner

this might potentially be difficult if the bot is running as a systemd service as i have planned, just a heads up

this *might* potentially be difficult if the bot is running as a systemd service as i have planned, just a heads up
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: modulatingforce/forcebot_rs#61
No description provided.