-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ffsync: Update syncstorage-rs to v0.18.2 #6406
Conversation
@hgy59, I don't know if you can assist with this but I've merged three PRs today and published two updates without issue. When trying to publish this one I keep getting the below errors from GitHub:
I don't know if this is a transient error or something with this package. It doesn't seem to be a build error but rather an error publishing. If this is the case though I can't understand why the other packages didn't have this issue. Full details in: https://github.com/mreid-tt/spksrc/actions/runs/12951166615/ |
Error log with some more context (before
I guess this error is new and may affect all python dependent packages (kopia and jellyfin do not depend on python). This error is a hint that instead of package upload it is processing some other tasks first:
May be the build of python wheels is triggered again. |
I can confirm that this is realted to python packages. I reproduced the publish error with ffsync, bazarr and python311 packages. But I guess it is not (only) related to #6389. This PR updated only mk/*.mk files (exchept download.sh for github workflow). So it might be caused by #6282 @th0ma7 published python310 on 10.01.2025 and that was just about 3 minutes after #6282 was merged (if the timestamp in github and sc repo are the same timezone). |
@th0ma7 just found that the publish for python310 is still working |
I did not yet had a chance to respond but this is really odd as the difference between 310 and 311's makefiles are marginal? I'll be over probably be over tomorrow with my pr that fixes builds issues, perhaps this will be magically addressed by it? Still, what i don't get is why my pr do run properly then? Could it be a caching issue? |
@th0ma7 just found the root cause The publish target uses while publishing, python the variable otherwise the call of
with python311:
with python310:
So we must ensure that python3 on the host is used to publish packages with http. |
Building always succeeded, only publish is broken. |
Description
This PR includes the following:
Fixes #
Checklist
all-supported
completed successfullyType of change