From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 36903@debbugs.gnu.org, 36903-done@debbugs.gnu.org,
Michael Albinus <michael.albinus@gmx.de>,
37590-done@debbugs.gnu.org
Subject: bug#37590: bug#36903: 27.0.50; gnus registry vs. debbugs
Date: Tue, 08 Oct 2019 10:52:58 +0200 [thread overview]
Message-ID: <87imozty8l.fsf@web.de> (raw)
In-Reply-To: <87y2xziesu.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 05 Oct 2019 07:59:13 -0400")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Great! I'm closing this and a related report.
Hmm - same recipe as always, today I'm getting this:
Debugger entered--Lisp error: (cl-no-applicable-method registry-lookup nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..."))
signal(cl-no-applicable-method (registry-lookup nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+...")))
cl-no-applicable-method(#s(cl--generic :name registry-lookup :dispatches ((1 #s(cl--generic-generalizer :name cl--generic-t-generalizer :priority 0 :tagcode-function #f(compiled-function (name &rest _) #<bytecode 0x1fe70a31de9d>) :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1fe70a31de8d>))) (0 #s(cl--generic-generalizer :name eieio--generic-generalizer :priority 50 :tagcode-function cl--generic-struct-tag :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1578a5722cb9>)) #s(cl--generic-generalizer :name cl--generic-t-generalizer :priority 0 :tagcode-function #f(compiled-function (name &rest _) #<bytecode 0x1fe70a31de9d>) :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1fe70a31de8d>)))) :method-table (#s(cl--generic-method :specializers (registry-db t) :qualifiers nil :uses-cnm nil :function #f(compiled-function (db keys) #<bytecode 0x1578a7918569>))) :options nil) nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..."))
apply(cl-no-applicable-method #s(cl--generic :name registry-lookup :dispatches ((1 #s(cl--generic-generalizer :name cl--generic-t-generalizer :priority 0 :tagcode-function #f(compiled-function (name &rest _) #<bytecode 0x1fe70a31de9d>) :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1fe70a31de8d>))) (0 #s(cl--generic-generalizer :name eieio--generic-generalizer :priority 50 :tagcode-function cl--generic-struct-tag :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1578a5722cb9>)) #s(cl--generic-generalizer :name cl--generic-t-generalizer :priority 0 :tagcode-function #f(compiled-function (name &rest _) #<bytecode 0x1fe70a31de9d>) :specializers-function #f(compiled-function (tag &rest _) #<bytecode 0x1fe70a31de8d>)))) :method-table (#s(cl--generic-method :specializers (registry-db t) :qualifiers nil :uses-cnm nil :function #f(compiled-function (db keys) #<bytecode 0x1578a7918569>))) :options nil) (nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+...")))
#f(compiled-function (&rest args) #<bytecode 0x1578a6935d31>)(nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..."))
apply(#f(compiled-function (&rest args) #<bytecode 0x1578a6935d31>) nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..."))
registry-lookup(nil ("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..."))
gnus-registry-get-or-make-entry("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+...")
gnus-registry-get-id-key("<CABczVwdfiSF3DpZ0QprBYH_o14PDpDT6nvip__g8K_F1Eyn+..." gnorb-ids)
gnorb-gnus-hint-relevant-message()
run-hooks(gnus-select-article-hook)
apply(run-hooks gnus-select-article-hook)
gnus-run-hooks(gnus-select-article-hook)
gnus-summary-display-article(18 nil)
gnus-summary-select-article(nil nil pseudo)
gnus-summary-scroll-up(1)
funcall-interactively(gnus-summary-scroll-up 1)
call-interactively(gnus-summary-scroll-up nil nil)
command-execute(gnus-summary-scroll-up)
so the issue reappeared (because of Gnorb?).
Regards,
Michael.
next prev parent reply other threads:[~2019-10-08 8:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 7:11 bug#36903: 27.0.50; gnus registry vs. debbugs Michael Heerdegen
2019-08-03 15:38 ` Eric Abrahamsen
2019-08-03 23:47 ` Michael Heerdegen
2019-08-04 0:16 ` Eric Abrahamsen
2019-08-04 0:27 ` Eric Abrahamsen
2019-08-04 0:44 ` Noam Postavsky
2019-08-04 1:41 ` Eric Abrahamsen
2019-08-04 1:09 ` Michael Heerdegen
2019-08-04 2:10 ` Eric Abrahamsen
2019-08-04 2:35 ` Eric Abrahamsen
2019-08-07 17:59 ` Lars Ingebrigtsen
2019-08-07 20:22 ` Eric Abrahamsen
2019-08-11 23:34 ` Lars Ingebrigtsen
2019-08-12 15:24 ` Eric Abrahamsen
2019-09-14 15:04 ` Lars Ingebrigtsen
2019-09-15 0:27 ` Eric Abrahamsen
2019-09-15 12:20 ` Lars Ingebrigtsen
2019-09-15 23:31 ` Eric Abrahamsen
2019-09-16 13:24 ` Lars Ingebrigtsen
2019-09-16 22:37 ` Eric Abrahamsen
2019-09-19 17:39 ` Eric Abrahamsen
2019-09-21 8:40 ` Michael Albinus
2019-09-21 21:31 ` Eric Abrahamsen
2019-09-22 1:04 ` Michael Heerdegen
2019-09-22 2:36 ` Eric Abrahamsen
2019-09-22 8:02 ` Michael Albinus
2019-09-25 9:39 ` Michael Heerdegen
2019-09-25 16:30 ` Eric Abrahamsen
2019-10-01 23:27 ` Eric Abrahamsen
2019-10-02 12:36 ` Michael Albinus
2019-10-03 23:22 ` Eric Abrahamsen
2019-10-04 8:24 ` Michael Albinus
2019-10-04 16:59 ` Eric Abrahamsen
2019-10-05 7:53 ` Michael Albinus
2019-10-05 11:59 ` Eric Abrahamsen
2019-10-08 8:52 ` Michael Heerdegen [this message]
2019-10-08 18:40 ` bug#36903: bug#37590: " Eric Abrahamsen
2019-10-09 14:37 ` Michael Heerdegen
2019-08-12 15:36 ` Eric Abrahamsen
2019-08-12 18:30 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imozty8l.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=36903-done@debbugs.gnu.org \
--cc=36903@debbugs.gnu.org \
--cc=37590-done@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=michael.albinus@gmx.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).