Creating gists fails with exception from (kill-new nil)

[eklitzke]

I get the following error when I try to call gist-buffer interactively. I get the same error with other commands like gist-region, and can't create any gists at all:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("\\`-+\\'" nil)
  menu-bar-update-yank-menu(nil nil)
  kill-new(nil)
  gist-created-callback(#<gh-gist-gist gh-gist-gist>)
  #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)(--cb-- --profile-- #<gh-gist-gist gh-gist-gist>)
  apply(#f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>) --cb-- --profile-- #<gh-gist-gist gh-gist-gist>)
  (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--))(#<gh-gist-gist gh-gist-gist>)
  #f(compiled-function (resp) #<bytecode 0x28a3829>)(#<gh-api-paged-response gh-api-paged-response>)
  apply(#f(compiled-function (resp) #<bytecode 0x28a3829>) #<gh-api-paged-response gh-api-paged-response>)
  #f(compiled-function (cl-cnm resp) #<bytecode 0x28a3dc5>)(#f(compiled-function (&rest cnm-args) #<bytecode 0x43a45ad>) #<gh-api-paged-response gh-api-paged-response>)
  apply(#f(compiled-function (cl-cnm resp) #<bytecode 0x28a3dc5>) #f(compiled-function (&rest cnm-args) #<bytecode 0x43a45ad>) #<gh-api-paged-response gh-api-paged-response>)
  #f(compiled-function (&rest args) #<bytecode 0x1555241>)(#<gh-api-paged-response gh-api-paged-response>)
  apply(#f(compiled-function (&rest args) #<bytecode 0x1555241>) #<gh-api-paged-response gh-api-paged-response> nil)
  gh-url-response-run-callbacks(#<gh-api-paged-response gh-api-paged-response>)
  #f(compiled-function (resp callback) #<bytecode 0x28a3849>)(#<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--)))
  apply(#f(compiled-function (resp callback) #<bytecode 0x28a3849>) (#<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--))))
  #f(compiled-function (cl-cnm resp callback) #<bytecode 0x28a41e1>)(#f(compiled-function (&rest cnm-args) #<bytecode 0x43a4559>) #<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--)))
  apply(#f(compiled-function (cl-cnm resp callback) #<bytecode 0x28a41e1>) #f(compiled-function (&rest cnm-args) #<bytecode 0x43a4559>) (#<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--))))
  #f(compiled-function (&rest args) #<bytecode 0x15552f9>)(#<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--)))
  apply(#f(compiled-function (&rest args) #<bytecode 0x15552f9>) #<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--)))
  gh-url-add-response-callback(#<gh-api-paged-response gh-api-paged-response> (lambda (&rest --cl-rest--) (apply (function #f(compiled-function (G1 G2 gist) #<bytecode 0x27bff7d>)) '--cb-- '--profile-- --cl-rest--)))
  gist-internal-new((#<gh-gist-gist-file gh-gist-gist-file>) nil nil nil)
  gist-region(1 657 nil)
  gist-buffer(nil)
  funcall-interactively(gist-buffer nil)
  call-interactively(gist-buffer record nil)
  command-execute(gist-buffer record)
  helm-M-x(nil #("gist-buffer" 0 11 (match-part "gist-buffer")))
  funcall-interactively(helm-M-x nil #("gist-buffer" 0 11 (match-part "gist-buffer")))
  call-interactively(helm-M-x nil nil)
  command-execute(helm-M-x)

[mfiano]

I can confirm the same problem which started happening recently.

[mfiano]

This is still an issue with Emacs stable (26.2) but not with HEAD.