(wrong-type-argument number-or-marker-p nil) error at gnus startup

(wrong-type-argument number-or-marker-p nil) error at gnus startup

[Julien Cubizolles]

With gnus v5.13 from Emacs 28.0.50 build of 2021-05-26, reported in
emacs bug#48664

Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
  <=(nil 6)
  gnus-get-unread-articles(nil nil)
  gnus-setup-news(nil nil nil)
  #f(compiled-function () #<bytecode 0x99b4d45572e0bb9>)()
  gnus-1(nil nil nil)
  gnus(nil)
  funcall-interactively(gnus nil)
  call-interactively(gnus record nil)
  command-execute(gnus record)
  execute-extended-command(nil "gnus" "gnus")
  funcall-interactively(execute-extended-command nil "gnus" "gnus")
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)

-- 
Julien Cubizolles

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Pankaj Jangid]

Julien Cubizolles <j.cubizolles@free.fr> writes:

> With gnus v5.13 from Emacs 28.0.50 build of 2021-05-26, reported in
> emacs bug#48664
>
> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>   <=(nil 6)
>   gnus-get-unread-articles(nil nil)
>   gnus-setup-news(nil nil nil)
>   #f(compiled-function () #<bytecode 0x99b4d45572e0bb9>)()
>   gnus-1(nil nil nil)
> ...

It appears that this and the issue reported by ‘Hirotaka Honda’ are
same. And I have also started facing the issue very recently. Like last
4-5 days.

I had reported a bug - 48664.

But I still couldn’t find the root cause. I thought may be it is a local
issue because no one else had any comments.

But now it appears that this is related to some code change.

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Eric Abrahamsen]

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> With gnus v5.13 from Emacs 28.0.50 build of 2021-05-26, reported in
>> emacs bug#48664
>>
>> Debugger entered--Lisp error: (wrong-type-argument number-or-marker-p nil)
>>   <=(nil 6)
>>   gnus-get-unread-articles(nil nil)
>>   gnus-setup-news(nil nil nil)
>>   #f(compiled-function () #<bytecode 0x99b4d45572e0bb9>)()
>>   gnus-1(nil nil nil)
>> ...
>
> It appears that this and the issue reported by ‘Hirotaka Honda’ are
> same. And I have also started facing the issue very recently. Like last
> 4-5 days.
>
> I had reported a bug - 48664.
>
> But I still couldn’t find the root cause. I thought may be it is a local
> issue because no one else had any comments.
>
> But now it appears that this is related to some code change.

But Hirotaka Honda's error now looks like it's something to do with
`mail-extract-address-components', unless there's something really
bizarre going on...

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Hirotaka Honda]

Dear all

After I commented out gnus-registry as the following, any errors (or the same errors) happened again.

;; (gnus-registry-initialize)
;; (setq
;;  gnus-registry-split-strategy 'majority
;;  gnus-registry-ignored-groups '(
;; 								("nntp" t)
;; 								("nnrss" t)
;; 								("mail.spam" t)
;; 								("archive" t)
;; 								("Send-Mail" t))
;; gnus-registry-track-extra nil
;; gnus-registry-max-entries 500000)

;; (setq spam-log-to-registry t)

Hirotaka Honda

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> On 06/01/21 22:30 PM, Hirotaka Honda wrote:
>> Dear all
>>
>> I am not certian what is happening, though the most dubious mail has
>> the email header like this:
>>
>> X-From-Line: - Fri May 28 HH:MM:SS 2021 [I masked the time]
>> X-Mozilla-Status: 0001
>> X-Mozilla-Status2: 00000000
>> ...
>> From: =?iso-2022-jp?B?[mask]?= <[mask]@outlook.jp>
>> To: =?utf-8?B?[mask]?=
>> =?utf-8?B?[mask]?= <[mask]@[mask]>
>> Cc: =?iso-2022-jp?B?[mask]?=
>> =?iso-2022-jp?B?[mask]=?= <[mask]@[mask]>,
>> "[mask]@[mask]" <[mask]@[mask]>
>> ...
>> X-Mailer: JavaMail
>>
>> Does the Gnus expect that To field and Cc field are coded in different ways?
>
> That shouldn't be a problem, the decoding process is called once for
> each header, and each time it detects the coding over again.
>
> My only uncertainty is, should the headers somehow be already decoded at
> this point (during registry operation), and if so and we're just missing
> a decode call, why hasn't this become an issue in the past? I suspect we
> just need to add decoding to the process, but it still makes me suspicious.

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Eric Abrahamsen]

Hirotaka Honda <hirotaka@hondalaw.com> writes:

> Dear all
>
> After I commented out gnus-registry as the following, any errors (or the same errors) happened again.

Would you be willing to send me the full unsanitized message (or just
the headers) off-list so I can test?

Thanks,
Eric

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Julien Cubizolles]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:


> But Hirotaka Honda's error now looks like it's something to do with
> `mail-extract-address-components', unless there's something really
> bizarre going on...

I had the same error message, but it's gone in the last versions

GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.25, cairo version 1.16.0) of 2021-05-31
-- 
Julien Cubizolles

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Hirotaka Honda]

Dear all

What a cool typo it was. Correct is:
    never happened again.

Hirotaka

Hirotaka Honda <hirotaka@hondalaw.com> writes:

> Dear all
>
> After I commented out gnus-registry as the following, any errors (or the
> same errors) happened again.
>
> ;; (gnus-registry-initialize)
> ;; (setq
> ;;  gnus-registry-split-strategy 'majority
> ;;  gnus-registry-ignored-groups '(
> ;; 								("nntp" t)
> ;; 								("nnrss" t)
> ;; 								("mail.spam" t)
> ;; 								("archive" t)
> ;; 								("Send-Mail" t))
> ;; gnus-registry-track-extra nil
> ;; gnus-registry-max-entries 500000)
>
> ;; (setq spam-log-to-registry t)
>
> Hirotaka Honda
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> On 06/01/21 22:30 PM, Hirotaka Honda wrote:
>>> Dear all
>>>
>>> I am not certian what is happening, though the most dubious mail has
>>> the email header like this:
>>>
>>> X-From-Line: - Fri May 28 HH:MM:SS 2021 [I masked the time]
>>> X-Mozilla-Status: 0001
>>> X-Mozilla-Status2: 00000000
>>> ...
>>> From: =?iso-2022-jp?B?[mask]?= <[mask]@outlook.jp>
>>> To: =?utf-8?B?[mask]?=
>>> =?utf-8?B?[mask]?= <[mask]@[mask]>
>>> Cc: =?iso-2022-jp?B?[mask]?=
>>> =?iso-2022-jp?B?[mask]=?= <[mask]@[mask]>,
>>> "[mask]@[mask]" <[mask]@[mask]>
>>> ...
>>> X-Mailer: JavaMail
>>>
>>> Does the Gnus expect that To field and Cc field are coded in different ways?
>>
>> That shouldn't be a problem, the decoding process is called once for
>> each header, and each time it detects the coding over again.
>>
>> My only uncertainty is, should the headers somehow be already decoded at
>> this point (during registry operation), and if so and we're just missing
>> a decode call, why hasn't this become an issue in the past? I suspect we
>> just need to add decoding to the process, but it still makes me suspicious.

Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup

[Eric Abrahamsen]

Hirotaka Honda <hirotaka@hondalaw.com> writes:

> Dear all
>
> What a cool typo it was. Correct is:
>     never happened again.

So much can ride on a word! :)