Closed avriiil closed 3 years ago
Hi @rrpelgrim, thanks for your patience. A fix for this is in progress, and we should be able to deploy it soon
Excellent, that would be a huge help! Do you think that will be in the next few days? Just trying to see whether I should go ahead and process the data locally (with loooong processing times) or wait until I can use my coiled cluster. thanks again!
-- Richard Pelgrim +31 (0)6 374 807 31
On Wed, Apr 7, 2021 at 8:32 AM Ian Rose @.***> wrote:
Hi @rrpelgrim https://github.com/rrpelgrim, thanks for your patience. A fix for this is in progress, and we should be able to deploy it soon
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/coiled/feedback/issues/140#issuecomment-815011130, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQLWMSXN5GYDVEXKV4MAHVTTHR3KNANCNFSM42JTK7TA .
We're expecting to roll this out to production in the next couple of days, yep :-)
On Wed, Apr 7, 2021 at 3:17 PM Richard Pelgrim @.***> wrote:
Excellent, that would be a huge help! Do you think that will be in the next few days? Just trying to see whether I should go ahead and process the data locally (with loooong processing times) or wait until I can use my coiled cluster. thanks again!
-- Richard Pelgrim +31 (0)6 374 807 31
On Wed, Apr 7, 2021 at 8:32 AM Ian Rose @.***> wrote:
Hi @rrpelgrim https://github.com/rrpelgrim, thanks for your patience. A fix for this is in progress, and we should be able to deploy it soon
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/coiled/feedback/issues/140#issuecomment-815011130, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AQLWMSXN5GYDVEXKV4MAHVTTHR3KNANCNFSM42JTK7TA
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/coiled/feedback/issues/140#issuecomment-815162027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADQPYMIXXNXR7A5EASZPTLTHSVURANCNFSM42JTK7TA .
-- Rami Chowdhury coiled.io "A mind all logic is like a knife all blade -- it makes the hand bleed that uses it." -- Rabindranath Tagore
Hi @necaris @ian-r-rose, just wondering if there's any update on this issue?
Hi @rrpelgrim, sorry for the slow reply. This fix should be deployed now: I was just able to create a new software environment with
import coiled
cloud = coiled.Cloud()
cloud.create_software_environment("pip-build-env", pip=["camel-kenlm"])
Please let us know if you run into any more problems around this!
Fantastic, thanks!
Closing, but if you run into any more troubles, feel free to ping here and reopen!
Just confirming that this is now working on my end as well. Thanks again!
When building a software environment using a .yml file containing the pip package
camel-tools
, the Jupyter Notebook cell completes but the software environment isn't actually built because of the error (partially) copied below. On Slack channel @necaris suggests that this is becausecamel-tools
requirescamel-kenlm
and the latter doesn't have binary wheels. Note thatcamel-tools
is only available throughpip
and not supported byconda
.The issue is two-fold:
Partial error message including the relevant mentions of
camel-tools
andcamel-kenlm
copied below: