-
Notifications
You must be signed in to change notification settings - Fork 190
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
nf-core list: Handle exception when HEAD is detached #297
Comments
|
Ups, sorry. I should have opened this issue at nf-core tools. I'll just leave this open here for now, but if you want me to I can reopen this at tools. |
No worries - GitHub has a new feature which allows you to transfer issues, so I've just moved this to tools. Relevant code: (problem is line 298) Lines 293 to 301 in 1855d34
Can you rerun with verbose logging please? Also, if you can go through all of your nf-core repos that have been pulled by nextflow and check their git statuses: cd ~/.nextflow/assets/nf-core/
cd rnaseq/
git status
# ..etc My guess is that one of these will give the same detached status. I'm not sure how this could have happened - we should add some code to the listing command to handle this exception type though. If you want to solve this, just reset the repo that has the detached head: git reset --hard HEAD Then I think everything should work fine again. Phil |
|
I only have MHCQuant on my machine. The debug log shows:
|
Removing
solved the issue. |
Is there anything to fix here? I’m a bit lost as to what the issue is that needs solving.. |
I accidentally reproduced it a month later or so, but it might just be an issue with my setup. No idea. |
Thinking about it more... I would guess that this happens when nextflow pulls a workflow to your home directory cache ( This has happened before and broken the website, which pulls the tools repo and others. That's why that update script now forces a hard git fetch && git reset --hard origin/master This shouldn't really happen, as |
Handle exceptions due to detached HEAD refs in the local pulls of remote workflows. Prints a helpful message about how to fix. Fixes nf-core#297
I guess there's an issue with a git branch?
The text was updated successfully, but these errors were encountered: