Add array-record feedstock#30587
Conversation
|
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR () and found it was in an excellent condition. |
|
Hi! This is the staged-recipes linter and I found some lint. File-specific lints and/or hints:
|
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipes/array-record/meta.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/16471335616. Examine the logs at this URL for more detail. |
|
Hi @iindyk we need your comment to confirm you'll also be a maintainer of the stock. |
f1db543 to
b3c45ab
Compare
|
Hello, yes, I'm willing to be a maintainer of the stock. |
|
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
|
@conda-forge-admin, please ping team |
|
Hi! This is the friendly automated conda-forge-webservice. I was asked to ping @conda-forge/staged-recipes and so here I am doing that. |
|
To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks! |
|
@conda-forge/help-python |
| rsync -avm -L --include="*.so" --include="*_pb2.py" \ | ||
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | ||
| bazel-bin/cpp "${TMPDIR}/array_record" | ||
| rsync -avm -L --include="*.so" --include="*_pb2.py" \ | ||
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | ||
| bazel-bin/python "${TMPDIR}/array_record" |
There was a problem hiding this comment.
| rsync -avm -L --include="*.so" --include="*_pb2.py" \ | |
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | |
| bazel-bin/cpp "${TMPDIR}/array_record" | |
| rsync -avm -L --include="*.so" --include="*_pb2.py" \ | |
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | |
| bazel-bin/python "${TMPDIR}/array_record" | |
| rsync -avm -L --include="*${SHLIB_EXT}" --include="*_pb2.py" \ | |
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | |
| bazel-bin/cpp "${TMPDIR}/array_record" | |
| rsync -avm -L --include="*${SHLIB_EXT}" --include="*_pb2.py" \ | |
| --exclude="*.runfiles" --exclude="*_obj" --include="*/" --exclude="*" \ | |
| bazel-bin/python "${TMPDIR}/array_record" |
| read, write, and random access by record index. ArrayRecord builds on top of Riegeli | ||
| and supports the same compression algorithms. | ||
| license: Apache-2.0 | ||
| license_family: Apache |
There was a problem hiding this comment.
| license_family: Apache |
| number: 0 | ||
| skip: true # [py<310] | ||
| skip: true # [win] | ||
| skip: true # [osx] |
There was a problem hiding this comment.
| skip: true # [osx] |
Let's enable macOS and see what it takes for it to build. Given that this is a bazel build, I won't ask for us to try Windows until the feedstock exists.
There was a problem hiding this comment.
I would prefer to skip osx for now:
- Unfortunately
array-recorddoesn't support MacOS x86 so it won't even compile here. - For MacOS ARM it will only apply once we get a feedstock - so I want to work on it in a follow-up PR.
There was a problem hiding this comment.
Okay, bazel is a such a painful system to build with we can get by for now only Linux but let's make sure check into macOS arm64 afterward. The build failure you linked seems to be more of an issue with how highway-hash was built than something specific to macOS x86, but it's so difficult to debug bazel that I don't have any suggestions yet.
|
@conda-forge/help-python It's ready for another review! |
|
Thank you for making this work! |
|
Please also take a look at conda-forge/tensorflow-datasets-feedstock#23 and #29008, which could benefit downstream. |
|
@conda-forge/help-python It's ready for review! |
|
@conda-forge/help-python It's ready for review! |
|
Adequate reviewers should be at @conda-forge/help-c-cpp or @conda-forge/help-python-c. The tag you used is for pure Python. |
danielnachun
left a comment
There was a problem hiding this comment.
I think this is probably ready to merge (notwithstanding the question about using the alpha tag), but @mtsokol please be aware that our ability to support bazel packages in conda-forge is extremely limited because the design of bazel is entirely antithetical to what we do here.
| number: 0 | ||
| skip: true # [py<310] | ||
| skip: true # [win] | ||
| skip: true # [osx] |
There was a problem hiding this comment.
Okay, bazel is a such a painful system to build with we can get by for now only Linux but let's make sure check into macOS arm64 afterward. The build failure you linked seems to be more of an issue with how highway-hash was built than something specific to macOS x86, but it's so difficult to debug bazel that I don't have any suggestions yet.
| @@ -0,0 +1,73 @@ | |||
| {% set name = "array-record" %} | |||
| {% set version = "0.8.0a1" %} | |||
There was a problem hiding this comment.
Normally we don't allow alpha tags on here, but I'm somewhat inclined to grant an exception here because this a bazel project and we're lucky it even has tags at all. Any thoughts on this from the rest of @conda-forge/staged-recipes?
There was a problem hiding this comment.
we can get by for now only Linux
conda-forge/tensorflow-datasets-feedstock#23
array-record is a major bottleneck for tensorflow-datasets, where this is dependent on Linux, so having even just Linux will help a lot.
@danielnachun Sure, thanks! Once we have a feedstock the next thing I will work on is MacOS ARM support. This one is already build for PyPI, contrary to MacOS x86 which isn't build there. So I guess potential MacOS x86 support will first take to build it for pip, and then conda-forge feedstock in the future. |
Checklist
url) rather than a repo (e.g.git_url) is used in your recipe (see here for more details).