-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performing a sync operation gives an error #1682
Comments
It may be an AUR API outage. If you look at https://github.com/Jguer/yay#readme, the icons are all red. |
The AUR api seems to be working fine. Looks like yay calls:
Which returns a 404 not found. Going by the wiki and calling:
Without the .php works fine and returns a json. No idea what the difference between them is. I only see .php mentioned in some forum posts. |
I am having the same error. I do not thing it is the AUR. Pikaur and other tools are still working. |
i can confirm confirm
|
Seeing same error:
If the AUR is in fact down, the error should note as much instead of just bailing because it tried to decode a response that wasn't actually there at all. |
same error when searching for conky
success when using pacman |
Could it be that the AUR used to respond to the .php extension to the |
PHEW I thought I'd be alone on this one when I went digging through threads |
lol, I runs out of memory while installing (compiling) something with yay and so my system hangs up. I need to hard reset my system. After that I face the same issue. I expect it's related to the hard reboot. Now I read this. |
They updated aruweb repo a few hours ago: Maybe the just upgraded the version in the server. |
I am unable to compile yay right now, but the only reference I found to "rpc.php" is in Line 30 in 19d42ae
|
Yeah I'm getting this issue as well so it's a problem for every yay user |
I just had this error and I'm 99% this is the "bug" ... they obviously changed the endpoint. |
I can verify that removing the extension fixes this particular issue. diff --git i/pkg/settings/args.go w/pkg/settings/args.go
index 2ac583b..20698a6 100644
--- i/pkg/settings/args.go
+++ w/pkg/settings/args.go
@@ -27,7 +27,7 @@ func (c *Configuration) extractYayOptions(a *parser.Arguments) {
}
}
- c.Runtime.AURClient.BaseURL = strings.TrimRight(c.AURURL, "/") + "/rpc.php?"
+ c.Runtime.AURClient.BaseURL = strings.TrimRight(c.AURURL, "/") + "/rpc?"
c.AURURL = strings.TrimRight(c.AURURL, "/")
} |
Please see #1684 |
Confirmed: @pmarreck's guess was right. This workaround works for me too. |
Glad I guessed it right! Note that /src is ignored via .gitignore in |
@pmarreck I use they/them, not she or he |
@DivergentClouds My bad! Edited it. Thanks for your efforts |
If anyone is wanting to use yay while waiting for the updated release, you can pass in a bit of a dodgy AUR url to get it to work:
|
This didn't work for me, it looks like it updated some packages, but when I try to search or install a specific package I get the error "no query was executed" and "response decoding failed... etc" |
I have compiled yay without that |
LOL! I'm in China. I wait for this bug to be fixed from morning to night |
中文翻译: |
Thank to everyone for all the posts and getting to the bottom of this issue. I just remade yay 11.1.0-1 (+1655 42.74) and it solved the problem. Thanks again. |
It is so sad. I am also in China, but it is still not working on my computer. |
working now!! |
Looks like the aur guys patched it for us, and the patch is scheduled to be removed a month from now: Patch here: https://gitlab.archlinux.org/archlinux/aurweb/-/commit/101de8e7b18916dd84ae52d39fb853924ea63a42 |
Wish you good luck. Try |
中文翻译: |
API 已更改,不再支持 /rpc.php。有一个拉取请求来解决这个问题,但是对这个文件的支持已经恢复了一个月,以便有时间更新这个项目。届时,它将被删除。请确保您在下个月保持最新状态,以避免将来出现问题。 很抱歉给您带来麻烦。 |
|
translate to English: |
English: Thank you! And I'm looking forward to update my yay~ |
rebuilt yay, working great now, thanks for the fix! |
I also rebuild it ,but it is still not working. I don't know why 😭 |
Hello. I'm the person responsible for this issue, and I'd like to clarify some things here. We've ported the AUR over to Python from PHP, which required a complete rewrite of the website. We had just a couple of people doing this over the past half a year or so. During the port, we had followed https://aur.archlinux.org/rpc documentation spec; we found, after releasing, that the Do note that the Arch Wiki is primarily user-driven, and so this is not an authoritative source of truth when it comes to the AUR. While the majority of it is on point, and the AUR guidelines should be followed, the usage of The issue here was multi-faceted on release:
(1) will be supported for the
With a complete rewrite of the website, we missed some things, including this issue. That being said, the majority of AUR helpers are already using So, anyway, tl;dr - it was my fault that this happened, and I apologize for the inconvenience. I did try to get this resolved from our side as quick as possible. PS: Thanks to everybody here who was so quick to action and bring this thread up. We immediately got wind of it, and it was a large part of the reason it even got resolved that next morning. You are all great! |
同等 |
Closing this issue as fixed on Fixed by #1685 |
I have been getting this error for 3 hours now. edit: not a bug, server is down. #2217 (comment) |
This seems to be happening again today! |
Just for completeness if somebody else gets directed here for the same problem. yay! ;) |
Affected Version
yay v11.1.0 - libalpm v13.0.1
Describe the bug
When performing an action with sync (
-S
), the following message occurs:Doing a different action, such as
-Q
, completes normally.Reproduction Steps
yay -Syu
Expected behavior
yay
doesn't crash.Output
The text was updated successfully, but these errors were encountered: