Skip to content
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

Get CI back running #102

Open
3 of 4 tasks
kmuehlbauer opened this issue Feb 20, 2024 · 3 comments
Open
3 of 4 tasks

Get CI back running #102

kmuehlbauer opened this issue Feb 20, 2024 · 3 comments

Comments

@kmuehlbauer
Copy link
Collaborator

kmuehlbauer commented Feb 20, 2024

tl;dr Pinning versions to those available in August 2022 and using older github-actions fixed the docker image and book build. This is not a longterm solution. This needs some discussion how to proceed here.

Fixed:

Issues:

@kmuehlbauer
Copy link
Collaborator Author

@mgrover1 #100, #101, #103 and #104 iteratively fixed the CI.

This just forced the CI, docker image etc back to versions around August 2022. That seemed to work, at least the rendered book contains the nicely rendered notebooks. See above this is no longterm solution.

@mike-dixon @leavesntwigs @DanielMichelson

If there is any movement forward on how to add lrose and baltrad to conda-forge this would really help for long-term maintenance of such repo here.

@kmuehlbauer
Copy link
Collaborator Author

I'll leave the issue open for a while just that everyone who gets directed to this repo immediately sees what's going on.

@mgrover1
Copy link
Collaborator

mgrover1 commented Mar 4, 2024

Thanks for all the work here @kmuehlbauer - I think this is a reasonable solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants