Vadim Kantorov

the only torch which works for pip version of flash_attn is `2.6.0+cu124`. In cu124 version ```bash nm ~/.local/lib/python3.10/site-packages/flash_attn_2_cuda.cpython-310-x86_64-linux-gnu.so | grep _ZN3c105ErrorC2ENS_14SourceLocationESs U _ZN3c105ErrorC2ENS_14SourceLocationESs nm ~/.local/lib/python3.10/site-packages/torch/lib/libc10.so | grep _ZN3c105ErrorC2ENS_14SourceLocationESs # 000000000008e120...

@tridao as advised by @malfet, the issue is PyTorch updated its C++ ABI in 2.6.0cu126, and it stayed this way in 2.7.0cu128: - https://github.com/pytorch/pytorch/issues/152790#issuecomment-2851107741 so probably a new push of...

I don't know how to try this. I did `nm ~/.local/lib/python3.10/site-packages/flash_attn_2_cuda.cpython-310-x86_64-linux-gnu.so`: [flash_attn_2_cuda.cpython-310-x86_64-linux-gnu.so.txt](https://github.com/user-attachments/files/20039059/flash_attn_2_cuda.cpython-310-x86_64-linux-gnu.so.txt) Maybe you can cross-reference the `c10` symbols manually against the recent symbols of `libc10_cuda.so` in 2.7.0? Some of...

For me, for now sth like this fixed the issue (make sure to adjust cp310) - seems to be working with torch2.7 even if this was build for torch2.6: ```...

This will be great: - https://github.com/Dao-AILab/flash-attention/issues/1696#issuecomment-2966762278

@KalleOlaviNiemitalo Yes, there are quite a few third-party solutions like csi command (https://visualstudiomagazine.com/articles/2021/06/14/csharp-scripting.aspx, https://github.com/dotnet/roslyn/issues/17666), https://github.com/dotnet-script/dotnet-script and plenty of others. IMO this fragmentation is an indicator it's time to add a...

IMO such a basic command should come in core / be supported officially and not require a third-party install...

Is this now released https://x.com/davidfowl/status/1925348132113817735 ? @davidfowl

Does it have a story for providing search paths for .so files / .dll files? At least it should be able to use the current directory for this

Really hope proper support for explicitly specifying search paths (for native .so libs and for managed .dll) gets implemented This is important for testing out DllImport bindings