Yay: --devel produces a bunch of odd warnings

[rien333]

Affected Version

I've tried running yay-git, as well as the latest stable version (10.1.0-1)

$ yay -V
yay v10.1.0.r3.g7d080df - libalpm v12.0.2

Describe the bug
Whenever I run yay -Sy --devel, yay outputs a bunch -> signal: killed" messages, that seemingly do nothing, but I'm also really not sure where they're coming from (see output below). Sometimes the list of messages is prefixed with -> exit status 128. After these messages, I'm presented with the dialogue to upgrade -git packages, and everything works as expected.

To Reproduce
Not sure, this suddenly started to happen a week or two ago. It happens everytime I run yay -Sy --devel.

Expected behavior
yay doesn't output a bunch of seemingly meaningless/uninformative warnings/messages.

Output

$ yay -Syu --devel
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 custom is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
:: Checking development packages...
 -> spotify: ignoring package upgrade (1.0.98.78-2 => 1:1.1.42.622-2)
 -> exit status 128
 -> signal: killed
 -> signal: killed
 -> signal: killed
 -> signal: killed [x25]
 -> Flagged Out Of Date AUR Packages: ...
:: 5 Packages to upgrade.
...
# yay continues as normal

Let me know what other sort of info might be relevant.

[rien333]

I've also seen it happen that yay only outputs -> exit status 128 before the package selection dialogue thingy, instead of that message plus a bunch of -> signal: killed messages.

[ElArtista]

Same here

[IslandC0der]

Can also confirm on yay v10.1.1

[kureta]

My internet connection dropped and update was interrupted before this message. Maybe that is related.

[rien333]

My internet connection dropped and update was interrupted before this message. Maybe that is related.

My internet is sometimes unstable, but this happens so consistently that I expect this to be unrelated to internet connectivity (I've never seen it _not_ happen, iirc also on more stable networks).

[Jguer]

@rien333 can you share your gitconfig (blur out ids and signing keys if you prefer) but this error is generally connected to the command timing out (signal killed) or git unclean exit (128 due to auth issues or bad permissions from what I've seen, can happen if you have a command that turns all https to ssh on gitconfig)

EDIT: before yay would always hide this git output but for debugging purposes it is now visible

[rien333]

My ~/.gitconfig is not remarkable in any way:

  [user]
      email = ***@gmail.com
      name = rien333
  [color]
      ui = auto

[Qyriad]

Entirely removing the yay build directory got rid of these warnings for me, as a workaround, though obviously that's not ideal.

[DrasLorus]

Encountering the sames issue I have tested to remove the yay cache directory (rm -rf ~/.cache/yay/*) and it indeed removed the warnings. Maybe by comparing this directory with a clean one (generated using yay --gendb after being removed) may help find the source of the problem?

[smac89]

So far all I can find is that the error is from git, because the error message exactly corresponds to what is found here: https://github.com/gogs/gogs/issues/3294.

It also makes sense because this happens when yay is checking devel packages.

---

EDIT

So I decided to drop a fake git into the path and turns out that one of my packages required authentication for git 😕

This is the command yay was running:

git ls-remote https://git.mirko.pm/brombinmirko/xfce4-taskbar-plugin HEAD

Fortunately I don't use it anymore, so I just uninstalled it, and now the warning is gone