Philip Sampaio
Philip Sampaio
I think this is now conflicting with my fix from https://github.com/pola-rs/polars/pull/18027 I'm also available to help if needed :) It seems that this fix would also fix the issue https://github.com/pola-rs/polars/issues/13163
I'm afraid this was not fixed yet. I could reproduce the error with the latest version from the main branch. Here is the backtrace: https://gist.github.com/philss/a81fab6f9cf85d23a0f1c364633e992b
I don't think we can build the metadata from outside the build of the module. But how do you change the config in a way that needs to rebuild the...
@mlwilkerson I think you can force the recompilation of the module with the following: ``` $ mix run -e "Kernel.ParallelCompiler.compile([(YourNativeModuleHere).module_info(:compile)[:source]])" ``` This will trigger the recompilation of that module, but...
I will hold this one until we decide to have a new minor (v0.9).
After talk with José, we saw that it's not possible to detect this since the error is directly from Erlang. So I'm closing.
> where is native code located at, something like `priv/polars.so`? Yes, it is stored in the `priv/native` path of each lib. > If so, if the native path contained target...
As @bvobart mentioned, we now have the `:has` pseudo-selector (from v0.38). I think you can work with a combination of `:has(y:fl-contains('hey'))` and `Floki.text()` with the `:deep` option set to `false`....
Makes sense to me. What do you think, @ypconstante ?
BTW, thank you for the report and the fix, @mellelieuwes !