Rene Leonhardt

This has been fixed and released months ago (May 15): https://github.com/google/closure-compiler-npm/pull/314 But emscripten still uses a 18 months old release since 12 months ago 🤷 https://github.com/emscripten-core/emscripten/blob/main/package.json#L24 ```json "google-closure-compiler": "20240317.0.0", ```

Oh, I just implemented the fix, didn't see this pull request mentioned 😅 If my diff is helpful: ```diff diff --git a/src/modules/fossil_metrics.rs b/src/modules/fossil_metrics.rs index 6beb19e4..0d97bbfb 100644 --- a/src/modules/fossil_metrics.rs +++ b/src/modules/fossil_metrics.rs...

I'm not sure that the black workflow is such a good example, I found the bake-action much easier to work with. But in any case, as you can see in...

Is the review finished? @GokulrajKS thank you very much for your contribution! Can you remove the comment?

All your work is lost?

Is it possible to improve the documentation to show the fastest way for a fully local run? https://swe-agent.com/latest/usage/coding_challenges/ shows some bits and pieces, maybe there could be a dedicated guide...

@askender Can you allow maintainers to push to your branch?

Great to see that the stale workflow is working, instead of actually implementing this feature request since last year it now has been automatically closed as not planned and moved...

Sad that it takes a year to fix this problem 😞

Same here for `windows-latest` with major `8` or SemVer `8.0.412+8`. ``` Available versions: 22.0.1+8, 22.0.0+36, 21.0.3+9.0.LTS, 21.0.2+13.0.LTS, 21.0.1+12.0.LTS, 21.0.0+35.0.LTS, 20.0.2+9, 20.0.1+9, 20.0.0+36, 19.0.2+7, 19.0.1+10, 19.0.0+36, 18.0.2+101, 18.0.2+9, 18.0.1+10, 18.0.0+36, 17.0.11+9,...