Firepup650/FireBot
2
0
Fork 1
Code Issues 5 Pull requests Activity Actions

Allow communication between bot instances #4

New issue
Open
opened 2024-04-19 18:11:52 +00:00 by Firepup650 · 2 comments
Firepup650 commented 2024-04-19 18:11:52 +00:00
Owner
Copy link

This has been something I've wanted to do for a while, but I'm not sure exactly how to go about it.

The complications to this with my current approach is that each bot instance is a completely unique python process, and so I can't just relay between threads, AFAIK.

I want to be able to do this so I can have a bot instance request that a different instance shut down, which is better than having to manually ssh to my pi and kill the process.

This has been something I've wanted to do for a while, but I'm not sure exactly how to go about it. The complications to this with my current approach is that each bot instance is a completely unique python process, and so I can't just relay between threads, AFAIK. I want to be able to do this so I can have a bot instance request that a different instance shut down, which is better than having to manually ssh to my pi and kill the process.
Firepup650 added the
Kind/Feature
Priority
High
 labels 2024-04-19 18:11:52 +00:00
Firepup650 added
Priority
Critical
 and removed
Priority
High
 labels 2024-05-18 02:09:19 +00:00
Firepup650 commented 2024-05-18 02:10:41 +00:00
Author
Owner
Copy link

Raising the priority on this, since I need a way to force kill other bot instances without having to restart core. This is especially important when my public IP changes and FireBot no longer recognizes me.

Raising the priority on this, since I need a way to force kill other bot instances without having to restart core. This is especially important when my public IP changes and FireBot no longer recognizes me.
Firepup650 commented 2024-05-18 14:16:21 +00:00
Author
Owner
Copy link

Further usefulness to this would be cross-instance banning of users, which would be nice.

Further usefulness to this would be cross-instance banning of users, which would be nice.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Priority
Zero
There is no priority on this change

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Zero
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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: Firepup650/FireBot#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?