Hi all, As of about a year ago capnp won't send a message if it thinks it would get rejected for size issues on the remote end. Our service is structured such that we send a very large request to open a remote object, then make a series of small queries against that. We naturally let those queries be pipelined, so don't call `.wait()` immediately on the initial query.
If the initial upload fails, it seems to happen pretty much silently. So where if we call `.wait()` immediately on the upload, we get the expected "Trying to send Cap'n proto message larger than single-message size limit." If we pipeline a second request, we instead get the cryptic "PromisedAnswer.questionId is not a current question." Is there a way to return a more interpretable error, possibly mentioning that somewhere along your pipelined requests a message wasn't sent? Thanks! -Alex -- 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 [email protected]. Visit this group at https://groups.google.com/group/capnproto.
