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

New repo URL breaks existing workflows #70

Closed
jaimergp opened this issue Sep 14, 2020 · 15 comments
Closed

New repo URL breaks existing workflows #70

jaimergp opened this issue Sep 14, 2020 · 15 comments
Labels
type:bug Something isn't working

Comments

@jaimergp
Copy link
Member

jaimergp commented Sep 14, 2020

I would have expected runners to follow redirections for actions that have changed location, but they don't...

https://github.com/openforcefield/openforcefield/runs/1114396909?check_suite_focus=true

Thanks to @mattwthompson for the report!

@goanpeca
Copy link
Member

Hi @jaimergp, yes I was expecting the redirects to last longer :-|

@mattwthompson
Copy link

It does seem to be working as expected after manually updating it: https://github.com/openforcefield/openforcefield/actions/runs/254560374

@goanpeca
Copy link
Member

Thanks for the report @mattwthompson, leaving open as this will probably bite more people :-|

@jaimergp
Copy link
Member Author

Are all users expected to manually migrate though? Maybe you can post the last version to your goanpeca namespace too, but adding a warning that it's changing locations and that the repo won't receive any more updates?

@goanpeca
Copy link
Member

Are all users expected to manually migrate though? Maybe you can post the last version to your goanpeca namespace too, but adding a warning that it's changing locations and that the repo won't receive any more updates?

Yep that would have been a better path 😆

I do not have time to do this at the moment so I will just create a fork and add a warning later when time clears a bit.

Thanks for the suggestion.

@goanpeca
Copy link
Member

Created this fork, so I guess this should bring it back to life ?

https://github.com/goanpeca/setup-miniconda

@jaimergp
Copy link
Member Author

Thank you so much for the fast response! That will do in the meantime, yes!

@jaimergp
Copy link
Member Author

I also raised this through their Twitter support and they are looking into it:

https://twitter.com/jaime_rgp/status/1305620040595763204

@jaimergp
Copy link
Member Author

jaimergp commented Sep 23, 2020

Github support has theoretically addressed this: https://twitter.com/mscccc/status/1306002367175823360

I don't know what we should do now, though:

a) Remove the fork and hope the redirection works
b) Keep the fork but add a deprecation warning pointing to the new URL

@goanpeca
Copy link
Member

goanpeca commented Sep 23, 2020

I would favor b :-)

That would be the nice thing to do.

Thoughts @conda-incubator/setup-miniconda-team ?

Now for how long would redirects work?

@jaimergp
Copy link
Member Author

I would favor b :-)

Agreed!

Now for how long would redirects work?

As far as I know, they shouldn't expire? source

@goanpeca
Copy link
Member

Let's keep the fork for now while we add the new things.

@bollwyvl
Copy link
Contributor

bollwyvl commented Nov 9, 2020

On account of #84, you'll probably want to upgrade to v2 anyhow...

@goanpeca
Copy link
Member

goanpeca commented Nov 12, 2022

Just made release 2.2.0, and updated the fork as well. We should be safe now to close the fork and close this issue @jaimergp, @jezdez ?

See https://github.com/search?q=goanpeca%2Fsetup-miniconda&type=code for users still using the old repo

@goanpeca
Copy link
Member

goanpeca commented Nov 15, 2022

I believe this is safe to close, updated release instructions (82400b0) to include an update to the fork and gave @jaimergp and @jezdez access to https://github.com/goanpeca/setup-miniconda just in case :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants