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

Include Make in builder-target-platform image #192

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

tsibley
Copy link
Member

@tsibley tsibley commented Nov 6, 2023

Required for building the Python isal package (for Augur) when there aren't wheels available (such as with recent version 1.5.2).

Checklist

  • Checks pass

Required for building the Python isal package (for Augur) when there
aren't wheels available (such as with recent version 1.5.2).
@tsibley tsibley requested a review from a team November 6, 2023 21:24
@tsibley tsibley merged commit a085532 into master Nov 6, 2023
33 checks passed
@tsibley tsibley deleted the trs/add-make-to-builder-target-platform branch November 6, 2023 21:25
@tsibley
Copy link
Member Author

tsibley commented Nov 6, 2023

Merging since this resolves build failures.

Copy link
Member

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?

Copy link
Contributor

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).

Copy link
Member Author

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 the pip 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.

Copy link
Member

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!

@tsibley
Copy link
Member Author

tsibley commented Nov 8, 2023

Two things to follow up on given discussion in pycompression/python-isal#158 (comment).

  1. We should test that the python-isal builds in our arm64 image actually function as expected, as the reason wheels weren't published for 1.5.2 is not due to build failures but test failures. We're not running isal's tests at install/build time, of course. (Gosh, I miss Perl and CPAN's whole ecosystem of testing sometimes.)

  2. We should expect to build python-isal going forward and not rely on wheels, at least for arm64, unless we can resolve the issues in the upstream CI which produces the wheels.

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

Successfully merging this pull request may close these issues.

3 participants