From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#59883: Eglot gopls failed to connect Date: Sun, 10 Sep 2023 12:21:10 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32373"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= , 59883@debbugs.gnu.org To: Johann =?UTF-8?Q?H=C3=B6chtl?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Sep 10 21:22:17 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qfQ0e-000888-EB for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 10 Sep 2023 21:22:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qfQ0O-00049t-LU; Sun, 10 Sep 2023 15:22:00 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qfQ0N-00049Y-5h for bug-gnu-emacs@gnu.org; Sun, 10 Sep 2023 15:21:59 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qfQ0M-0008VU-Tu for bug-gnu-emacs@gnu.org; Sun, 10 Sep 2023 15:21:58 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qfQ0Q-0004Dj-Fn for bug-gnu-emacs@gnu.org; Sun, 10 Sep 2023 15:22:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 10 Sep 2023 19:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59883 X-GNU-PR-Package: emacs Original-Received: via spool by 59883-submit@debbugs.gnu.org id=B59883.169437368416161 (code B ref 59883); Sun, 10 Sep 2023 19:22:02 +0000 Original-Received: (at 59883) by debbugs.gnu.org; 10 Sep 2023 19:21:24 +0000 Original-Received: from localhost ([127.0.0.1]:51340 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qfPzn-0004Cb-Ga for submit@debbugs.gnu.org; Sun, 10 Sep 2023 15:21:23 -0400 Original-Received: from mail-lf1-x12f.google.com ([2a00:1450:4864:20::12f]:44385) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qfPzl-0004CO-76 for 59883@debbugs.gnu.org; Sun, 10 Sep 2023 15:21:21 -0400 Original-Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-502a4f33440so2942454e87.1 for <59883@debbugs.gnu.org>; Sun, 10 Sep 2023 12:21:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694373671; x=1694978471; darn=debbugs.gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date :message-id:reply-to; bh=LLoPYBL+kW2/NK1iOkErwJE5X9SHDz3WOrfSghjSs3k=; b=QqnaMN/OZi9ayuoN5bhPlE4MMgfh3p94P2/OEMF56PjiY9PA5CVR5awR46CJcRviyQ /gFFMrcys+VeBW+lV7wyTB6gvR/4QFpZ+zcplxQz6DzRCfl6V8ZfTzP1RwsBL0KNbVrx 1WJxxJWe1ZcAMARhHzkkE1yCx6tlC/jw6PKWdnuF52RrutTPf7ZeHGnuZN7KBXItK+cG yGpcwRVD0Fell4chpmQsrjFOS1g50SgjlScj8jptYv24HyoikRw9JbJOa/qhPb7EsriK qrt/HFDAvgPZ9ZtgbNJuPiRgra26ncwLvyC2oLbZ0uPdm8P4Jys0n2cRnNoEFjdjquX3 UBbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694373671; x=1694978471; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=LLoPYBL+kW2/NK1iOkErwJE5X9SHDz3WOrfSghjSs3k=; b=HfsYEActrniGNDhR+PH80bh4ilQn3Jyy7G6BcV5fKNwS6/5pvON+N3PQe8be4MCsfV mkcwTWnXNvqIiijKdQBKi/EtSoC1/leCdxpBkGYnXQ4WhtX2QqPiRXt5bW2WU9HeTd0m BrPuVVL7C8sYuOnhiFs5NpI/mzZQGqIaq/nkwBD38drFArZ3deTpp6Y1qkY/DfMjWpbG ofx9qI24CSKKo7etzEzDTdncIp3EttRQaMdi519Hl/H/XoyWRa5qdEDi2biZILzkAZrt 6HzHtcw9ZdrKTpWHYKIo7XE3OFE7gXsaOQuOQcVBt4Oe0ZUJp3L2JdXm/seajGJHtqoL ItUQ== X-Gm-Message-State: AOJu0Yz+CRnh2w+q7FXz0Z7kS3vj9IOeP4LG/nJw3Fj9PkAqSQLgl3Uw yr6/d+WFDb6ratldF4/9U+/TGy5sJdkZmbUg4oI= X-Google-Smtp-Source: AGHT+IFrLU6XwHcGLBcQBsE0FNvu4l9mXl7DYUSVc1qs1FnMn27SMbYKxbEdfBGdPUiC6HWTb9ubMvoi5HUeDr8ONKk= X-Received: by 2002:a19:8c1b:0:b0:500:761b:72ff with SMTP id o27-20020a198c1b000000b00500761b72ffmr4814942lfd.55.1694373671284; Sun, 10 Sep 2023 12:21:11 -0700 (PDT) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 10 Sep 2023 12:21:10 -0700 In-Reply-To: ("Johann =?UTF-8?Q?H=C3=B6chtl?="'s message of "Mon, 12 Dec 2022 08:13:42 +0100") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:269999 Archived-At: Johann H=C3=B6chtl writes: > Sorry, this bug has to be re-opened. I was confident that the described "= work-around" is > stable, yet it's not. Eglot was working consistently yesterday just to fi= nd it non-working today > with the same errors. Are you still seeing this? > Am So., 11. Dez. 2022 um 14:24 Uhr schrieb Johann H=C3=B6chtl : > > I found a solution. Quick: For some reason when opening a go file using = go-mode, > Emacs/eglot generates a "textDocument/didOpen" server message. Now the c= orrect > reaction of a LS upon such a message in a chase where the file actually = did not change > remains disputable: > > https://github.com/golang/go/issues/50267 > https://github.com/neovim/neovim/issues/16623 > > However, the gopls-team considered a "chatty" behavior of the language s= erver to be > better anyhow. To always send diagnostics is now the default, yet not re= leased as of > gopls 1.10.1 > > https://github.com/golang/tools/commit/ec743893cd01c9423aaae4513b092c4c4= c06f0f4 > > https://groups.google.com/g/golang-checkins/c/tt8Ig_UsKtE > > To use the yet unreleased feature from gopls@HEAD which works, follow > > https://github.com/golang/tools/blob/master/gopls/doc/advanced.md#unstab= le-versions > > > This bug report may be closed, reported for reference. > > Am So., 11. Dez. 2022 um 13:45 Uhr schrieb Johann H=C3=B6chtl > : > > I dug deeper into the problem: > > * When I open a very small golang-project, eglot interconnects correctly= with gopls > * When I open a larger golang-project, eglot fails to communicate with g= opls. In fact, it > fails to direct gopls to load the project as gopls stays at a very small= memory > footprint. > > When I uninstall go-mode OR find-file-literally *.go and later enable eg= lot, gopls is > correctly "directed" to load the project, because memory consumption is = much > higher. In this case it also reports back to eglot "loading packages" an= d "finished > loading packages". > > Sidenote: However I cannot interact any further with the LS as eglot doe= ns't consider > any buffer as managed: > > cl-no-applicable-method: No applicable method: eglot--managed-buffers, n= il > eldoc error: (jsonrpc-error No current JSON-RPC connection (jsonrpc-erro= r-code . > 32603) (jsonrpc-error-message . No current JSON-RPC connection)) > mouse-minibuffer-check: Minibuffer window is not active > > but I guess this is because the buffer has no mode eglot considers to be= supported. > > Sidenote2: If I enable go-mode for this buffer (thus triggering eglot-en= sure in .emacs) , > a second gopls process is spawned yet without communication between eglo= t and > gopls.