all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 67945@debbugs.gnu.org, daniel@dpettersson.net
Subject: bug#67945: 30.0.50; Jsonrpc trouble dealing with nested synchronous requests
Date: Thu, 1 Feb 2024 23:40:59 -0800	[thread overview]
Message-ID: <CADwFkmmsx=p==psPci5HfTHSSHCzRZXHBOV+U0cGO0qG7Y-bxQ@mail.gmail.com> (raw)
In-Reply-To: <CALDnm517x1vGm_di6VxFDfz1AkCcL=YEQGr6TvX5jTTWu7-3KA@mail.gmail.com> ("João Távora"'s message of "Thu, 21 Dec 2023 01:01:44 +0000")

João Távora <joaotavora@gmail.com> writes:

> On Wed, Dec 20, 2023 at 11:31 PM João Távora <joaotavora@gmail.com> wrote:
>>
>> Hi,
>>
>> I've come across a rather complicated bug in jsonrpc.el that affects a
>> certain class of JSON-RPC applications.  Eglot, on of the more important
>> `jsonrpc.el` clients (perhaps the most) is not affected, as far as I
>> can tell.
>>
>> I already have a fix for this bug, but I am filing this report as a
>> reference for the commit message and to collect comments.
>
> I've now pushed the fix to jsonrpc.el and tagged version 1.0.21
> of the jsonrpc package.
>
> I'd like to push some tests using the `jbug.py` test server
> attached earlier.  Is here a good place to store such helper scripts
> in our test subtree?
>
> João

Thanks, should this bug be closed or is there more to do here?





  parent reply	other threads:[~2024-02-02  7:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 23:30 bug#67945: 30.0.50; Jsonrpc trouble dealing with nested synchronous requests João Távora
2023-12-21  1:01 ` João Távora
2023-12-21  7:51   ` Eli Zaretskii
2023-12-21  9:52     ` João Távora
2024-02-02  7:40   ` Stefan Kangas [this message]
2024-02-02  9:29     ` João Távora
2024-02-04 12:32       ` Daniel Pettersson
2024-07-25  7:12       ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmmsx=p==psPci5HfTHSSHCzRZXHBOV+U0cGO0qG7Y-bxQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=67945@debbugs.gnu.org \
    --cc=daniel@dpettersson.net \
    --cc=joaotavora@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.