Hi Guys, I’ve been looking into the <conda feedsto...
# daft-dev
g
Hi Guys, I’ve been looking into the conda feedstock for the package which is not publishing the package, the issues are: 1. daft version 2.33 introduces the use of Simd::load_or_default which is a nightly feature found since rust 1.79, rust 1.79 nightly is not found in conda, the only nightly rust compiler found in conda since 1.79 is 1.81. 2. daft version 0.2.33 locks the time crate to 0.3.29, which is incompatible with rust 1.81. what do you suggest?
meanwhile I am trying to release the rust nightly version which was used to build this daft version to conda through the rust feedstock
j
I think we might need @Sammy Sidhu’s input here, but my 2c: • `the only nightly rust compiler found in conda since 1.79 is 1.81`: I think we can probably bump our version to 1.81? • We can also bump our
time
crate
c
In our next release we will be upgrading to a newer version of nightly (compiled on August 1), which includes time being bumped to 0.3.36. Would this fix your problem?
g
This will solve this issue, but I think that if there is a conda package publishing, there needs to be a conda build test, because for version 0.2.33, there is currently no conda build for rust that is compatible
published the necessary rust toolchain to conda-forge. I am updating the getdaft feedstock
somehow the getdaft feedstock does not mange to install the correct rust version, can someone take a look?
👀 1
j
I’m not familiar at all with conda unfortunately, but seems like your build did publish the right files to conda-forge? https://anaconda.org/conda-forge/rust/files
g
as far as I understand conda builds, the channel sources should do the trick, the issue is that when I specify version 1.79 of the rust compiler it cannot use the correct rust compiler build due to strict channel priority, that my guess is happening due to the conda-build command. I am wondering wether there is someone who has experience building a conda package from the rust nightly, which is from the rust dev conda channel
j
Hmm, that’s perhaps a good question for the folks on https://github.com/conda-forge/rust-feedstock?
Also I was reading some other repos, seems like any package that uses pyo3 likely has to use unstable features in Rust as well. We can maybe take a look at how other Rust/Python projects do their setup
Here’s the feature for pyo3 that requires it: https://pyo3.rs/v0.14.5/features.html#nightly
g
I will take a look later next week. Thanks 🙂
🙌 1
j
Thanks for taking a stab at this!
g
Sure 🙂
@jay, last mile issues to link with clang on osx, are you familiar with that? https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1005207&v[…]dfe-b752375c22e3&t=71f60cc9-1e13-5dcf-5627-3ead6dfd2a23&l=2201 I think the right people have noticed, so we just have to wait :/
j
Not familiar with that unfortunately 😧 let’s see what they say!
s
I haven't seen the linker segfault before! That's a new one