You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Huginn.jl has implemented the same workflow that is working in Sleipnir.jl to run the tests automatically after every commit to main. However, in Huginn this is not working, and the problem seems to be comming from PyCall. Observing both stacktraces, we observe that in Huginn it seems that the conda environmnet is not properly set:
This error does't not show in Sleipnir. The problem is probably coming from the fact that here Sleipnir is being installed and imported as a separate module. Here is something in the PyCall documentation that may help find the solution.
The text was updated successfully, but these errors were encountered:
Is this fixed now? I think we basically repeated the same workflow of Sleipnir inside Huginn in order to to pyimport to all necessary Python packages? Ideally, it would be nice to fix this and clean up this repetition.
To be seen if now that we do @reexport using Sleipnir this is fixed.
Currently
Huginn.jl
has implemented the same workflow that is working inSleipnir.jl
to run the tests automatically after every commit to main. However, in Huginn this is not working, and the problem seems to be comming fromPyCall
. Observing both stacktraces, we observe that in Huginn it seems that the conda environmnet is not properly set:This error does't not show in Sleipnir. The problem is probably coming from the fact that here Sleipnir is being installed and imported as a separate module. Here is something in the PyCall documentation that may help find the solution.
The text was updated successfully, but these errors were encountered: