ObserverOfTime
ObserverOfTime
Yet never submitted a pull request.
Does `tree-sitter parse --wasm` work? If it does then this is likely an issue somewhere in the Zed implementation.
You can replace `$HOME/Library/Caches/tree-sitter/lib/orgmode.so` with the one generated by Zed. Though I'm not sure either the `--wasm` flag or Zed _actually_ produce a Wasm library. 🤔
> `$HOME/Library/Caches/tree-sitter` doesn't exist on my machine It might be in `$HOME/.cache/tree-sitter` then.
OK so in Tree-sitter 0.25, `build --wasm` properly calls `emcc`, but `parse --wasm` calls `cc` instead. Zed and the upcoming Tree-sitter 0.26 release both use WASI SDK instead of Emscripten....
The tree-sitter-yaml release failed with the same error so I created a new token with read-write access to all of the organization's packages just to be safe but it still...
Nothing we can do about this here. It should be fixed in tree-sitter-cpp either by including the C query file, or by prepending it to the C++ one at build...
[fudiff](https://crates.io/crates/fudiff) seems promising and has no dependencies. Rejected alternatives: - [patcher](https://crates.io/crates/patcher): AI generated - [diff-match-patch-rs](https://crates.io/crates/diff-match-patch-rs): weird format
Failed jobs sometimes require fixes to the workflow (e.g. #5120) so it can't be rerun directly.
If we only use it for commits that fix broken workflows and call it from the release branch that won't be an issue.