One !ai worked and the next did not. AI answer seems generated, but not sent:
archy beta asking archy exp
Steps to Reproduce
Run !ai questions back and forth between archy nodes
Expected Behavior
Consistent reply
Actual Behavior
inconsistent reply
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
### Description
One !ai worked and the next did not. AI answer seems generated, but not sent:
archy beta asking archy exp
### Steps to Reproduce
Run !ai questions back and forth between archy nodes
### Expected Behavior
Consistent reply
### Actual Behavior
inconsistent reply
### Archipelago Version
1.7.99-alpha
### Hardware
x86_64 (Intel/AMD)
### Relevant Logs
_No response_
### Screenshots
_No response_
Closing as stale/addressed — your own update (“I do get an answer eventually now”) plus the v1.8.4 federation fix for the perpetual peer-joined “Invalid signature” storm (which silently dropped inter-node traffic) cover the likely cause. Please reopen with fresh logs if the generate-but-not-send case still occurs on a current version.
Closing as stale/addressed — your own update (“I do get an answer eventually now”) plus the v1.8.4 federation fix for the perpetual peer-joined “Invalid signature” storm (which silently dropped inter-node traffic) cover the likely cause. Please reopen with fresh logs if the generate-but-not-send case still occurs on a current version.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description
One !ai worked and the next did not. AI answer seems generated, but not sent:
archy beta asking archy exp
Steps to Reproduce
Run !ai questions back and forth between archy nodes
Expected Behavior
Consistent reply
Actual Behavior
inconsistent reply
Archipelago Version
1.7.99-alpha
Hardware
x86_64 (Intel/AMD)
Relevant Logs
No response
Screenshots
No response
I do get an answer eventually now
This may be related to general meshtastic issues including public messages showing up in PM windows.
Closing as stale/addressed — your own update (“I do get an answer eventually now”) plus the v1.8.4 federation fix for the perpetual peer-joined “Invalid signature” storm (which silently dropped inter-node traffic) cover the likely cause. Please reopen with fresh logs if the generate-but-not-send case still occurs on a current version.