New `Refreshing AUR` stage failure cancels a repo’s package installation operation of pamac

Pamac --version

Pamac 10.3.0-4 - libpamac 11.2.0

Variant in use

CLI

Distribution

Manjaro (unstable branch of updates)

Desktop environment

KDE

What's not working

Package installation cancels by AUR refreshing stage failure.

How to reproduce?

In case of failure of the AUR refreshing, pamac install fails to install a repo package.

More information (optional)

New Refreshing AUR stage failure cancels a repo’s package installation operation of pamac ...and leads to more load of AUR file host server cause of further immediate retry(-ies) in order to get a Manjaro native repo package to be installed.

~/Desktop ❯ pamac install nodejs
Preparing...
Synchronizing package databases...
Refreshing AUR...                                                                                                                                                      
6.9 MB/9.4 MB                                                                                                                                                          
https://aur.archlinux.org/packages-meta-ext-v1.json.gz: Connection terminated unexpectedly

~/Desktop ❯ pamac install nodejs
Preparing...
Synchronizing package databases...
Refreshing AUR...                                                                                                                                                      
                                                                                                                                                                       
Choose optional dependencies for nodejs:
1:  npm: nodejs package manager

Enter a selection (default=none): 
...

According to https://forum.manjaro.org/t/refreshing-aur-stage-downloads-a-9-3-mib-file-and-eats-about-1-5-gib-of-ram-memory/100170 now pamac install operation eats that much amount of RAM during simple package installation.

pamac --version
Pamac 10.3.0-4  -  libpamac 11.2.0

pacman-mirrors -G
unstable

---

BTW If that libpamac 11.2.0 from pamac --version is insufficient info about that dependency, please add package build into into it as you did for the Pamac 10.3.0-4 in it: this simplifies user report and do not waste to other operations like:

 pamac info libpamac | grep 'Ver'   
Version               : 11.2.0-5

Please add it into full output of pamac --version if you need to know it's -3 / -4 / -5 build number. Otherwise at least it looks like inconsistent output: one item with build number, other one w/o it.

And prior to install nodejs I rebooted PC, so I have running 11.2.0-5 before to install the nodejs package.

Thank you!