Skip to content

Conversation

@Yikun
Copy link
Member

@Yikun Yikun commented Sep 7, 2022

What changes were proposed in this pull request?

Change the spark ci image from "ghcr.io/$REPO_OWNER/spark/$IMG_NAME" to "ghcr.io/$REPO_OWNER/spark/$IMG_NAME".

Due to some reasons (docker/build-push-action#687), original base ci image has permission issue, this is a bug of ghcr. Let's frist recover CI first (old image has permission issue but new image not), I will contact github team and take a deep look later.

Related Github incidents:

Why are the changes needed?

#33 [auth] grundprinzip/apache-spark-ci-image:pull,push token for ghcr.io
#33 DONE 0.0s

#32 exporting to image
#32 exporting manifest sha256:d6a11f99d74b4198a6d35e6341bb94852584dd070f9e7909546ad13490645667 done
#32 exporting config sha256:e227ad580c837e04213fcd11672c618aa5ac7a3523ed454cf99900aff22d3c33 done
#32 pushing layers
#32 pushing layers 0.6s done
#32 ERROR: unexpected status: 403 Forbidden
------
 > exporting to image:
------
ERROR: failed to solve: unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: unexpected status: 403 Forbidden

Does this PR introduce any user-facing change?

No

How was this patch tested?

base image ci passed

@github-actions github-actions bot added the INFRA label Sep 7, 2022
Yikun referenced this pull request Sep 7, 2022
### What changes were proposed in this pull request?
Upgrade pandas to 1.4.4 in infra and doc gen

### Why are the changes needed?
https://pandas.pydata.org/docs/whatsnew/v1.4.4.html

Especially, fix bugs which mentioned in #36353:
- Fixed regression in DataFrame.fillna() not working on a DataFrame with a MultiIndex (GH47649)
- Fixed regression in DataFrame.eval() creating a copy when updating inplace (GH47449)

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
CI passed

Closes #37810 from Yikun/pandas-1.4.4.

Authored-by: Yikun Jiang <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
@Yikun
Copy link
Member Author

Yikun commented Sep 7, 2022

Let's wait pyspark, spark, lint ci passed (about 1 hour)

@Yikun
Copy link
Member Author

Yikun commented Sep 7, 2022

Related github incident: https://www.githubstatus.com/incidents/d181frs643d4

@Yikun Yikun marked this pull request as draft September 7, 2022 09:16
@Yikun
Copy link
Member Author

Yikun commented Sep 7, 2022

Looks like github resolved this issue:

image

we might don't need this workaround. @HyukjinKwon

works in my local (without this PR): https://github.com/Yikun/spark/runs/8224647901?check_suite_focus=true

@Yikun Yikun closed this Sep 7, 2022
@HyukjinKwon
Copy link
Member

Thanks for letting me know!

@Yikun
Copy link
Member Author

Yikun commented Sep 8, 2022

community/community#32184

According others reply, same issue happened again on github side....let me rebase and see does this workaround still avaiable or not.

@Yikun Yikun reopened this Sep 8, 2022
@Yikun Yikun force-pushed the FIX-image-namespace branch from 746609e to 890b944 Compare September 8, 2022 04:11
@Yikun
Copy link
Member Author

Yikun commented Sep 8, 2022

BTW, I also drafted a PR to reduce the potential impact in future.

#37828

@qindongliang
Copy link
Contributor

This helped me fix the same issue. Here are the complete steps:

  1. Go to your GitHub Profile → Packages (https://github.com/YOUR_USERNAME?tab=packages)
  2. Click on the package that failed to push (e.g., apache-spark-ci-image-docs)
  3. Go to "Package settings" (right side)
  4. Under "Manage Actions access", click "Add Repository"
  5. Select your repository (e.g., [spark])
  6. Set the Role to "Admin" or "Write"
  7. Repeat for any other packages that need access
  8. Re-run the failed GitHub Actions workflow
    After this, the permission_denied: write_package error is resolved and CI can push images successfully! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants