Skip to content

feat: use built triton-windows fork to fix long-path issue#29

Merged
philpax merged 1 commit intowp-1.5from
use-patched-triton-windows
Mar 9, 2026
Merged

feat: use built triton-windows fork to fix long-path issue#29
philpax merged 1 commit intowp-1.5from
use-patched-triton-windows

Conversation

@philpax
Copy link

@philpax philpax commented Mar 9, 2026

Temporary fix for #27 (does not close the issue out). Uses our triton-windows fork with a partial longpath fix.

@philpax philpax requested a review from lapp0 March 9, 2026 17:46
@lapp0
Copy link
Collaborator

lapp0 commented Mar 9, 2026

LGTM, I haven't tested. This impacts windows, the platform for which you are the primary downstream consumer. Ready to merge for convenience with wp-1.5 integration if you're ready.

Will be we able to target the official triton-windows in the coming days?

@philpax
Copy link
Author

philpax commented Mar 9, 2026

I've tested this and it works, but it might not cover all scenarios; the upstream fix (which has already been merged) should, so the plan is to update to that when possible. I've let them know that we'd appreciate a release being cut, so fingers crossed that I should be able to switch us over in the next few days. Feel free to merge 🙂

@philpax philpax merged commit c076f88 into wp-1.5 Mar 9, 2026
@philpax philpax deleted the use-patched-triton-windows branch March 9, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants