-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-40366][INFRA] Add spark namespace to spark ci image
#37815
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
Conversation
### 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]>
|
Let's wait pyspark, spark, lint ci passed (about 1 hour) |
|
Related github incident: https://www.githubstatus.com/incidents/d181frs643d4 |
|
Looks like github resolved this issue: 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 |
|
Thanks for letting me know! |
|
According others reply, same issue happened again on github side....let me rebase and see does this workaround still avaiable or not. |
746609e to
890b944
Compare
|
BTW, I also drafted a PR to reduce the potential impact in future. |
|
This helped me fix the same issue. Here are the complete steps:
|

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?
Does this PR introduce any user-facing change?
No
How was this patch tested?
base image ci passed