Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this! Where is this isal dependency even from? I don't get it when installing Augur with pip locally.
This fragility is unfortunate, and I wouldn't be surprised if other indirect dependencies cause breakage like this in the future. Would it be worthwhile to provide a standalone installer for Augur for cases like this, where flexibility in dependency versions defined by setup.py is not necessary and even undesirable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a requirement of xopen for Linux systems only. (I was curious so I tracked it down with pipdeptree in a nextstrain shell).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think a standalone installer for Augur is necessary for this Docker image. It'd be a bit of work for too narrow of a gain, I think, and there are other ways about it. For example, we could take additional measures in the Dockerfile to reduce this sort of breakage by using
--prefer-binary
to thepip install
of Augur. That would have gotten us the isal 1.5.1 wheels instead of trying to build isal 1.5.2 from source. We could also maintain a constraints file and pass that in with--constraint
if we wanted to pin things more tightly for this Docker image.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tsibley that makes sense. Good to know those alternatives!