"X unreadable" messages in agent terminals
Problem description
The individual agent terminals display an "X unreadable in agentY" message (e.g., "38 unreadable in agent3") as the last line.
Steps to reproduce
- Launch your MAS using DALIA as launcher.
- Run the MAS scenario involving multiple agents.
- Observe the output in the individual agent panels as they halt.
Expected behavior
The agent terminals should terminate cleanly after the last line, without any further error or "unreadable" status messages.
Actual behavior
After the agent prints the last line ("Stop condition met. Halting agent..." in my specific case), a message appears indicating a number of "unreadable" items for that agent. This appears to be related to unread messages or a problem with how communication channels are closed upon halting.
Screenshots
See attached screenshots from the agent terminals of a MAS running a distributed algorithm for consensus (King Algorithm).
"X unreadable" messages in agent terminals
Problem description
The individual agent terminals display an "X unreadable in agentY" message (e.g., "38 unreadable in agent3") as the last line.
Steps to reproduce
Expected behavior
The agent terminals should terminate cleanly after the last line, without any further error or "unreadable" status messages.
Actual behavior
After the agent prints the last line ("Stop condition met. Halting agent..." in my specific case), a message appears indicating a number of "unreadable" items for that agent. This appears to be related to unread messages or a problem with how communication channels are closed upon halting.
Screenshots
See attached screenshots from the agent terminals of a MAS running a distributed algorithm for consensus (King Algorithm).