all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jose A. Ortega Ruiz" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 71683@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: bug#71683: 30.0.50; Ellipsis buttons in compilation buffers can only be activated with the mouse
Date: Thu, 20 Jun 2024 23:41:01 +0000	[thread overview]
Message-ID: <87ed8rji7r.fsf@mail.jao.io> (raw)
In-Reply-To: <87r0crjwnm.fsf@mail.jao.io>

On Thu, Jun 20 2024, jao via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:

> I can reproduce the problem with this recipe, at least with my
> configuration (haven't been able to try with emacs -Q yet):
>
> - M-x compile
> - Enter as compile command:
>
> echo "21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message \"An unexpected internal error occurred\", :info \"channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)\", :trace (\"com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)\" \"com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:427)\" \"com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:421)\" \"com.rabbitmq.client.impl.recovery.RecoveryAwareChannelN.basicAck(RecoveryAwareChannelN.java:93)\" \"com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicAck(AutorecoveringChannel.java:439)\" \"langohr.basic$ack.invokeStatic(basic.clj:205)\" \"langohr.basic$ack.invokePrim(basic.clj)\" \"wintermute.message.mailbox.rabbitmq_core$ack.invokeStatic(rabbitmq_core.clj:81)\" \"wintermute.message.mailbox.rabbitmq_core$ack.invoke(rabbitmq_core.clj:80)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$ack__19911.invoke(rabbitmq_core.clj:89)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$fn__19923$fn__19924.invoke(rabbitmq_core.clj:93)\" \"wintermute.delete.server$processor.invokeStatic(server.clj:229)\" \"wintermute.delete.server$processor.invoke(server.clj:221)\" \"clojure.core$partial$fn__5912.invoke(core.clj:2656)\" \"wintermute.message.mailbox.rabbitmq_core$consumer$fn__19923.invoke(rabbitmq_core.clj:93)\" \"langohr.consumers$create_default$fn__19833.invoke(consumers.clj:83)\" \"langohr.consumers.proxy$com.rabbitmq.client.DefaultConsumer$ff19274a.handleDelivery(Unknown Source)\" \"com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:149)\" \"com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable.run(ConsumerWorkService.java:104)\" \"java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)\" \"java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)\" \"java.base/java.lang.Thread.run(Thread.java:829)\")}"
>
> That produces a compilation buffer which ends in:
>
> 21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message "An unexpected internal error occurred", :info "channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)", :trace ("com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:427)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQChannel.java:421)" "com.rabbitmq.client.impl.recovery.RecoveryAwareChannelN.basicAck(RecoveryAwareChannelN.java:93)" "com.rabbitmq.client.impl.recovery.AutorecoveringChannel.basicAck(AutorecoveringChannel.java:439)" "langohr.basic.invokeStatic(basic.clj:205)" "langohr.basic.invokePrim(basic.clj)" "wintermute.message.mailbox.rabbitmq_core.invokeStatic(rabbitmq_core.clj:81)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:80)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:89)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:93)" "wintermute.delete.server.invokeStatic(server.clj:229)" "wintermute.delete.server.invoke(server.clj:221)" "clojure.core.invoke(core.clj:2656)" "wintermute.message.mailbox.rabbitmq_core.invoke(rabbitmq_core.clj:93)" "langohr.consumers.invoke(consumers.clj:83)" "langohr.consumers.proxy.rabbitmq.client.DefaultConsumer.handleDelivery(Unknown Source)" "com.rabbitmq.client.impl.ConsumerDispatcher.run(ConsumerDispatcher.java:149)" "com.rabbitmq.client.impl.ConsumerWorkService.run(ConsumerWorkService.java:104)" "java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)" "java.base/java.util.concurrent.ThreadPoolExecutor.run(ThreadPoolExecutor.java:628)" "java.base/java.lang.Thread.run(Thread.java:829)")}

Sorry, emacs tricked me and inserted the full message again. The
compilation buffer looks in fact like this:

21:27:16.195 ERROR wintermute.message.mailbox.rabbitmq-core -  -- ALARM -- Failure ack-ing {:error :exception, :code -20, :message "An unexpected internal error occurred", :info "channel is already closed due to clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=OK, class-id=0, method-id=0)", :trace ("com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannjava:258)" "com.rabbitmq.client.impl.AMQChannel.transmit(AMQCha[…]







  parent reply	other threads:[~2024-06-20 23:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 18:29 bug#71683: 30.0.50; Ellipsis buttons in compilation buffers can only be activated with the mouse Jose A. Ortega Ruiz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 18:46 ` Eli Zaretskii
2024-06-20 20:41   ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-20 23:41 ` Jose A. Ortega Ruiz via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-22  9:37   ` Eli Zaretskii
     [not found]     ` <875xu1jo5a.fsf@mail.jao.io>
2024-06-22 10:42       ` Eli Zaretskii
2024-06-26  1:52         ` jao via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-26 11:20           ` Eli Zaretskii

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=87ed8rji7r.fsf@mail.jao.io \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71683@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mail@jao.io \
    /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.