-
Notifications
You must be signed in to change notification settings - Fork 0
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
Upgrade to recipes 0.9.4, and use kerchunk to open inputs #5
base: main
Are you sure you want to change the base?
Conversation
/run citrace_tracer |
@jordanplanders the test errored because of a bug in the |
@cisaacstern Sounds good. I was surprised that it was still "in progress" this morning, but figured it might just be a lot of bytes to process. Thanks for your persistence! |
Actually still waiting for this bug fix to propagate up to Pangeo Forge Cloud, but going to make a few adjustments here in the meantime... I'll explain after committing. |
Two changes just made:
Now just waiting for the new version of the cloud application to build, after which I'll re-trigger the test here. |
Ok I think everything's fixed 🤞 so will re-run test now. |
/run citrace_tracer |
The test failed, but I'm sure we can find out why! Pangeo Forge maintainers are working diligently to provide public logs for contributors. |
@cisaacstern ah, the plot thickens! Let me know what I can probe. |
Thanks for the ping, @jordanplanders. I believe this is a versioning issue on the backend, which if I'm correct, should be solved by pangeo-forge/pangeo-forge-orchestrator#210. I'll re-trigger the test once that goes through. As noted in the comments in that PR thread, this is certainly helping to highlight the necessity of some broader infrastructure upgrades we're working on (which should hopefully prevent or greatly minimize this type of problem in the future). |
Ok I think this problem is solved... re-testing this recipe now. |
/run citrace_tracer |
Just going to get out ahead of the upcoming automated failure comment and say... this is going to fail! 😆 Hoping pangeo-forge/pangeo-forge-orchestrator#212 will fix the underlying issue (finally!). |
The test failed, but I'm sure we can find out why! Pangeo Forge maintainers are working diligently to provide public logs for contributors. |
/run citrace_tracer |
pangeo-forge/pangeo-forge-orchestrator#212 did not fix this 😮💨 🤦 ... going to try another approach. |
@cisaacstern Oh gracious! As always, if there is something I can do (investigate something about the files? I'm not sure how to contribute at this point 😬), let me know! 🤞 |
@jordanplanders thanks for asking. At this point this is totally on me to fix what has ended up being a far more tangled backend service issue than I'd anticipated. I'll keep truckin' on that and ping you again here when it's (actually!) fixed. |
@jordanplanders pangeo-forge/pangeo-forge-recipes#383 was merged this week, so upgrading this feedstock's required pangeo-forge-recipes version may likely resolve the root issue #3 we've been fighting all along. I'll run a test from this PR to see if that's the case. 🤞