i don't know what the best solution for everybody is, but the super
silent treatment seems like the worst, but that's just me :-}
> Perhaps you're suggesting the agents should automatically catch all
> their own exceptions and then throw them to stderr. What if you want to
> handle them? For de
Raoul Duke wrote:
> apparently one has to manually write ones agents to log the exceptions
> out to stderr or stdout? i guess my personal principle of least
> surprise implementation would have been to at least spit out the first
> exception once.
The problem is where do you throw the exceptions?
> If any exceptions are thrown by an action function, no nested
> dispatches will occur, and the exception will be cached in the Agent
> itself. When an Agent has errors cached, any subsequent interactions
> will immediately throw an exception, until the agent's errors are
> cleared. Agent errors
If any exceptions are thrown by an action function, no nested
dispatches will occur, and the exception will be cached in the Agent
itself. When an Agent has errors cached, any subsequent interactions
will immediately throw an exception, until the agent's errors are
cleared. Agent errors can be exa
hello,
it seems like when i'm running agent stuff via load-file etc. in the
repl, exceptions in fns the agent runs don't appear to be logged
anywhere, they are seemingly silently swallowed. personally i find
that frustrating. is there some way to make them always verbose / spit
out to stdout? or
