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

WormBase upstream having issues; use bypass and revert when ready #338

Open
kltm opened this issue Sep 25, 2023 · 6 comments
Open

WormBase upstream having issues; use bypass and revert when ready #338

kltm opened this issue Sep 25, 2023 · 6 comments

Comments

@kltm
Copy link
Member

kltm commented Sep 25, 2023

Currently, there are issues with the WB file at its usual location.

As an interim workaround, we will have @vanaukenk send us the best version of the file and will use it "manually" until the upstream is fixed. Once the upstream is fixed, we will revert.

Tagging @vanaukenk and @pgaudet

@pgaudet
Copy link
Contributor

pgaudet commented Nov 17, 2023

@vanaukenk just checking the status on this one

@kltm
Copy link
Member Author

kltm commented Jan 4, 2024

Note that we lost this file with #350 ; I found it again in an email from @vanaukenk on 2023-09-25.
Tagging @sierra-moxon

@kltm
Copy link
Member Author

kltm commented Jan 22, 2024

@vanaukenk Will this be out with the next WB release? Is there a timeline for that?

@vanaukenk
Copy link

@kltm @pgaudet
It looks like the latest WB release has the correct reference format, so we can go back to using the WB ftp URL for file retrieval.
@kltm do you want me to update the WB yaml?

@kltm
Copy link
Member Author

kltm commented Jan 22, 2024

@vanaukenk Please: that would be great!

@kltm
Copy link
Member Author

kltm commented Jan 22, 2024

Should propagate out. As file changed and confirmed to exist, I'll move this to done until something comes up.

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

No branches or pull requests

3 participants