-Si not working for some AUR package(s)

[drws]

Affected Version

yay v12.3.5 - libalpm v14.0.0

Describe the bug

yay -Si errors out in a special case where a valid AUR package name (arduino) is queried. If any other AUR packages are queried alongside, Yay even errors out in a special way where it doesn't output anything useful, not even for valid packages from the query.

Reproduction Steps

1. Querying the package in question:

$ yay -Si arduino
error: package 'arduino' was not found
 -> exit status 1

2. Querying the package in question alongside main repo package:

$ yay -Si arduino pacman
error: package 'arduino' was not found
Repository      : core
Name            : pacman
Version         : 6.1.0-3
Description     : A library-based package manager with dependency support
Architecture    : x86_64
URL             : https://www.archlinux.org/pacman/
Licenses        : GPL-2.0-or-later
Groups          : None
Provides        : libalpm.so=14-64
Depends On      : bash  glibc  libarchive  curl  gpgme  pacman-mirrorlist  gettext  gawk  coreutils  gnupg  grep
Optional Deps   : perl-locale-gettext: translation support in makepkg-template
Conflicts With  : None
Replaces        : None
Download Size   : 936.01 KiB
Installed Size  : 4897.90 KiB
Packager        : Morten Linderud <[email protected]>
Build Date      : Fri 15 Mar 2024 18:46:11 CET
Validated By    : MD5 Sum  SHA-256 Sum  Signature

 -> exit status 1

3. Querying the package in question alongside AUR package:

$ yay -Si yay arduino
error: package 'arduino' was not found
 -> exit status 1

This was tested in two different systems. Also, it doesn't matter whether the arduino package is installed in the system or not (which it shouldn't with -S, so not an issue).

Expected behavior

There might be some peculiarities or errors in the PKGBUILD that trigger this behavior, but Yay should still be able to display arduino package information. yay -Si arduino should output info as expected and possibly also a warning or an error message for what is triggering the current behavior.

If a valid package data somehow couldn't be obtained after all, this should be caught too and a relevant error displayed.

Furthermore, there is something strange going on when the error is question is triggered as yay -Si is prevented from outputting data for other packages, which is an inconsistent behavior and is potentially a separate issue to consider.