Hi Jens, Info-level logs are generally meant to be enabled only for debugging, so the idea here is you normally shouldn't see this log. All exceptions that are transmitted over RPC are info-logged but normally you would only want to log them in production if some actual operation you care about fails with this exception.
-Kenton On Tue, Jun 7, 2022 at 5:03 PM Jens Alfke <j...@mooseyard.com> wrote: > > > On Jun 7, 2022, at 9:53 AM, 'Kenton Varda' via Cap'n Proto < > capnproto@googlegroups.com> wrote: > > Ideally, you should set things up so that when the stack unwinds, all > Promise objects are destroyed before the EventLoop is destroyed. > > > Thanks! I actually figured this out shortly after posting, but forgot to > send a follow-up. I had to inspect some classes' member declarations > carefully to find the two that were in the wrong order; swapping them fixed > it. > > But maybe you can help me with a less-annoying warning that I’m still > getting. When either the client or the server connection closes, I always > get an Info-level log: > > *returning failure over rpc; exception = capnp/rpc.c++:3107: failed: > RpcSystem was destroyed.* > > It appears harmless, and no exception is actually thrown, but I’d rather > not be logging this. Any idea what I might still be doing wrong? > > —Jens > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/CAJouXQm%3DGZtuX5Jn_QYS1bj2LRJiqtBvFp_som0EkggbYvk0eA%40mail.gmail.com.
