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

ganon build-custom prints an interactive message from seqan causing 'hanging' in non-interactive compute environments #292

Open
jfy133 opened this issue Nov 13, 2024 · 0 comments

Comments

@jfy133
Copy link

jfy133 commented Nov 13, 2024

I was just testing ganon custom-build (finally back to it after parental leave), and when running it on a HPC my job hung.

I later found out it was because it was waiting for a response to this question:


#######################################################################
   Automatic Update Notifications
#######################################################################

 This app can look for updates automatically in the background,
 do you want to do that?

    [a] Always perform version checks for this app (the default).
    [n] Never perform version checks for this app.
    [y] Yes, perform a version check now, and ask again tomorrow.
    [s] Skip the version check now, but ask again tomorrow.

 Please enter one of [a, n, y, s] and press [RETURN].

 For more information, see:
 https://docs.seqan.de/sharg/main_user/about_update_notifications.html

#######################################################################

n

I think that's from a upstream dependency, but this is not very nice when working in non-interacive contexts...

Apparently you can turn this off via a seqan command: as listed here: https://docs.seqan.de/sharg/main_user/about_update_notifications.html#autotoc_md7

I think it might be good to have that included in ganon if I understand this issue correctly

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

1 participant