Kay Zheng wrote: > Now I have these logs captured using ch_logfile(...): > > https://gist.github.com/anonymous/d9b00634422a69b7ea3729ca6ac21b40 > > The first received message failed but the second succeeded. I verified > both messages, concatenated the fragments manually and parsed them > with some trivial Python code. they're all legit JSON strings, and > they are actually the same except the message IDs. > > Having these info, I think the root cause lies in the channel (or > JSON?) implementation inside Vim. > > I will keep looking into it, but I would be grateful if there's > someone familiar with the channel implementation that can help me out.
I suppose this will be hard to reproduce in a debugger, because of timing. In the channel logfile you may not see enough to pinpoint the problem. You can add some more ch_logs() calls in channel_read, where it is calling sock_read() or fd_read(). E.g. bylogging the number of bytes received. With the timestamp and other log messages you may be able to guess what goes wrong. -- Veni, Vidi, Video -- I came, I saw, I taped what I saw. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
