helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: server : disable speculative decoding for SWA models

ref https://github.com/ggml-org/llama.cpp/issues/13963

To properly support his, we first need to fix this TODO:

https://github.com/ggml-org/llama.cpp/blob/272df3f94b42d53a9b779270cdc0b9d5c16ff56a/src/llama-kv-cache-unified-iswa.cpp#L98-L106

Changed files:
filename: tools/server/server.cpp
patch: @@ -2016,6 +2016,11 @@ struct server_context {
                 params_base.n_cache_reuse = 0;
                 SRV_WRN("%s\n", "cache_reuse is not supported by this context, it will be disabled");
             }
+
+            if (!params_base.speculative.model.path.empty()) {
+                SRV_ERR("%s\n", "err: speculative decode is not supported by this context");
+                return false;
+            }
         }
 
         return true;
@@ -3203,9 +3208,7 @@ struct server_context {
                                 }
                             } else {
                                 // if we don't cache the prompt, we have to remove the entire KV cache
-                                llama_kv_self_seq_rm(ctx, slot.id, 0, -1);
                                 slot.n_past = 0;
-                                slot.cache_tokens.clear(); // TODO: not needed, will be cleared later via "keep_first()"
                             }
 
                             if (slot.n_past > 0 && slot.n_past < (int) slot.cache_tokens.size()) {
@@ -3220,7 +3223,6 @@ struct server_context {
                                     SLT_WRN(slot, "n_past = %d, cache_tokens.size() = %d, seq_id = %d, pos_min = %d, n_swa = %d\n", slot.n_past, (int) slot.cache_tokens.size(), slot.id, pos_min, n_swa);
                                     SLT_WRN(slot, "forcing full prompt re-processing due to lack of cache data (likely due to SWA, see %s)\n",
                                             "https://github.com/ggml-org/llama.cpp/pull/13194#issuecomment-2868343055");
-                                    llama_kv_self_seq_rm(ctx, slot.id, 0, -1);
                                     slot.n_past = 0;
                                 }
                             }
Repository: electron/electron
Pull request: ci: write test logging to console on Windows

Backport of #43990

See that PR for details.


Notes: <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->none


Changed files:
filename: appveyor-woa.yml
patch: @@ -327,4 +327,3 @@ for:
     on_finish:
       # Uncomment these lines to enable RDP
       # - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
-      - if exist electron\electron.log ( appveyor-retry appveyor PushArtifact electron\electron.log )

filename: appveyor.yml
patch: @@ -308,7 +308,7 @@ for:
           if ($env:TARGET_ARCH -eq 'ia32') {
             $env:npm_config_arch = "ia32"
           }
-      - echo Running main test suite & node script/yarn test -- --trace-uncaught --runners=main --enable-logging=file --log-file=%cd%\electron.log
+      - echo Running main test suite & node script/yarn test -- --trace-uncaught --runners=main --enable-logging
       - cd ..
       - echo Verifying non proprietary ffmpeg & python electron\script\verify-ffmpeg.py --build-dir out\Default --source-root %cd% --ffmpeg-path out\ffmpeg
       - echo "About to verify mksnapshot"
@@ -320,4 +320,3 @@ for:
     on_finish:
       # Uncomment these lines to enable RDP
       # - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
-      - if exist electron\electron.log ( appveyor-retry appveyor PushArtifact electron\electron.log )
Repository: denoland/deno
Pull request: fix(ext/fetch): fix lowercase http_proxy classified as https

While investigating something else, I noticed this typo which treated `http_proxy` as `Filter::Https`.

Changed files:
filename: ext/fetch/proxy.rs
patch: @@ -97,7 +97,7 @@ pub(crate) fn from_env() -> Proxies {
   if env::var_os("REQUEST_METHOD").is_none() {
     if let Some(proxy) = parse_env_var("HTTP_PROXY", Filter::Http) {
       intercepts.push(proxy);
-    } else if let Some(proxy) = parse_env_var("http_proxy", Filter::Https) {
+    } else if let Some(proxy) = parse_env_var("http_proxy", Filter::Http) {
       intercepts.push(proxy);
     }
   }
Repository: huggingface/transformers
Pull request: [Bug Fix] Renamed loss to losses to suppress UnboundLocalError

# What does this PR do?

Fixes # (issue)

I use the keywords of `eval_accumulation_steps` and `UnboundLocalError ` but none of the issues are found. So I just decide to make a PR (because this is a quick fix)

## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?

## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.


 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.
- trainer: @muellerzr and @SunMarc



Changed files:
filename: src/transformers/trainer.py
patch: @@ -3791,16 +3791,16 @@ def evaluation_loop(
                     batch_size = observed_batch_size
 
             # Prediction step
-            loss, logits, labels = self.prediction_step(model, inputs, prediction_loss_only, ignore_keys=ignore_keys)
+            losses, logits, labels = self.prediction_step(model, inputs, prediction_loss_only, ignore_keys=ignore_keys)
             main_input_name = getattr(self.model, "main_input_name", "input_ids")
             inputs_decode = self._prepare_input(inputs[main_input_name]) if args.include_inputs_for_metrics else None
 
             if is_torch_xla_available():
                 xm.mark_step()
 
             # Update containers
-            if loss is not None:
-                losses = self.gather_function((loss.repeat(batch_size)))
+            if losses is not None:
+                losses = self.gather_function((losses.repeat(batch_size)))
                 all_losses.add(losses)
             if inputs_decode is not None:
                 inputs_decode = self.accelerator.pad_across_processes(inputs_decode, dim=1, pad_index=-100)
Repository: facebook/react
Pull request: Add missing createServerContext for experimental shared subset

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

Add missing `createServerContext` export in experimental share subset build

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

## How did you test this change?

The [PR on next.js side](https://github.com/vercel/next.js/pull/39721) is trying to opt-in the shared subset for server components if possible

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->


Changed files:
filename: packages/react/src/ReactSharedSubset.experimental.js
patch: @@ -19,6 +19,7 @@ export {
   createElement,
   createMutableSource as unstable_createMutableSource,
   createRef,
+  createServerContext,
   forwardRef,
   isValidElement,
   lazy,
Repository: vercel/next.js
Pull request: Rust: restore toolchain 2025-05-12

This restores #79117.

https://github.com/rust-lang/rust/issues/71520 broke Windows on arm64 when using rust-lld, so this disables that for now.

Test Plan: `pnpm --filter=@next/swc run build-native-no-plugin-release --target aarch64-pc-windows-msvc` on Windows on arm64.

Closes PACK-4590

Changed files:
filename: .cargo/config.toml
patch: @@ -34,9 +34,6 @@ rustflags = [
   "target-feature=+crt-static"
 ]
 
-[target.aarch64-pc-windows-msvc]
-linker = "rust-lld"
-
 [target.'cfg(target_os = "macos")']
 linker = "rust-lld"
 

filename: rust-toolchain.toml
patch: @@ -1,4 +1,4 @@
 [toolchain]
-channel = "nightly-2025-04-14"
+channel = "nightly-2025-05-12"
 components = ["rustfmt", "clippy", "rust-analyzer"]
 profile = "minimal"
Repository: huggingface/transformers
Pull request: Fix linalg.norm for CovnNextV2

# What does this PR do?

Bug introduced in 
 - https://github.com/huggingface/transformers/pull/37041

While we are normalizing on multiple dimensions
1.  `torch.linlag.norm` much slower than `torch.norm`
2. `torch.linlag.norm` **is not equivalent** to `torch.norm`

Instead, `torch.linlag.vector_norm` should be used

Fixes: https://github.com/huggingface/transformers/issues/37748

cc @Rocketknight1 

Changed files:
filename: src/transformers/models/convnextv2/modeling_convnextv2.py
patch: @@ -83,7 +83,7 @@ def __init__(self, dim: int):
 
     def forward(self, hidden_states: torch.FloatTensor) -> torch.FloatTensor:
         # Compute and normalize global spatial feature maps
-        global_features = torch.linalg.norm(hidden_states, ord=2, dim=(1, 2), keepdim=True)
+        global_features = torch.linalg.vector_norm(hidden_states, ord=2, dim=(1, 2), keepdim=True)
         norm_features = global_features / (global_features.mean(dim=-1, keepdim=True) + 1e-6)
         hidden_states = self.weight * (hidden_states * norm_features) + self.bias + hidden_states
Repository: nodejs/node
Pull request: tools: fix tools-deps-update

This extends PR https://github.com/nodejs/node/pull/52957 to our other automated updates.

@targos [suggested that this might be more robust](https://github.com/nodejs/node/pull/56663#issuecomment-2602910065).


Changed files:
filename: .github/workflows/tools.yml
patch: @@ -284,6 +284,10 @@ jobs:
               tail -n1 temp-output | grep "NEW_VERSION=" >> "$GITHUB_ENV" || true
               rm temp-output
     steps:
+      - name: Setup Git config
+        run: |
+           git config --global user.name "Node.js GitHub Bot"
+           git config --global user.email "github-bot@iojs.org"
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4.2.2
         if: github.event_name == 'schedule' || inputs.id == 'all' || inputs.id == matrix.id
         with:
@@ -301,17 +305,15 @@ jobs:
         if: env.COMMIT_MSG == '' && (github.event_name == 'schedule' || inputs.id == 'all' || inputs.id == matrix.id)
         run: |
           echo "COMMIT_MSG=${{ matrix.subsystem }}: update ${{ matrix.id }} to ${{ env.NEW_VERSION }}" >> "$GITHUB_ENV"
-      - uses: gr2m/create-or-update-pull-request-action@86ec1766034c8173518f61d2075cc2a173fb8c97  # v1.9.4
+      - uses: peter-evans/create-pull-request@5e914681df9dc83aa4e4905692ca88beb2f9e91f  # v7.0.5
         if: github.event_name == 'schedule' || inputs.id == 'all' || inputs.id == matrix.id
         # Creates a PR or update the Action's existing PR, or
         # no-op if the base branch is already up-to-date.
-        env:
-          GITHUB_TOKEN: ${{ secrets.GH_USER_TOKEN }}
         with:
-          author: Node.js GitHub Bot <github-bot@iojs.org>
-          body: This is an automated update of ${{ matrix.id }} to ${{ env.NEW_VERSION }}.
+          token: ${{ secrets.GH_USER_TOKEN }}
           branch: actions/tools-update-${{ matrix.id }}  # Custom branch *just* for this Action.
+          delete-branch: true
           commit-message: ${{ env.COMMIT_MSG }}
           labels: ${{ matrix.label }}
           title: '${{ matrix.subsystem }}: update ${{ matrix.id }} to ${{ env.NEW_VERSION }}'
-          update-pull-request-title-and-body: true
+          body: This is an automated update of ${{ matrix.id }} to ${{ env.NEW_VERSION }}.
Repository: huggingface/transformers
Pull request: Re-Enable `Trigger CircleCI via GitHub Actions when "ready for review" (#37885)`

# What does this PR do?

With `CircleCI-Public/trigger-circleci-pipeline-action@v1.2.0`, we could specify `target-branch` 🎉 

Changed files:
filename: .github/workflows/trigger_circleci.yml
patch: @@ -0,0 +1,20 @@
+name: Trigger CircleCI
+
+
+on:
+  pull_request_target:
+    types: [ready_for_review]
+
+
+jobs:
+  trigger-circleci:
+    runs-on: ubuntu-22.04
+    steps:
+      - name: trigger CircleCI pipeline via GitHub Actions
+        uses: CircleCI-Public/trigger-circleci-pipeline-action@v1.2.0
+        with:
+          GHA_Meta: "Trigger via GitHub Actions"
+          target-slug: "github/huggingface/transformers"
+          target-branch: "pull/${{ github.event.number }}/head"
+        env:
+          CCI_TOKEN: ${{ secrets.CIRCLECI_PAT }}
Repository: nodejs/node
Pull request: doc: fix inconsistencies in `WeakSet` and `WeakMap` comparison details

This PR fixes the inconsistencies in the comparison example added in #56648.

Part of #56640  

Changed files:
filename: doc/api/assert.md
patch: @@ -909,11 +909,12 @@ weakSet2.add(obj);
 
 // Comparing different instances fails, even with same contents
 assert.deepStrictEqual(weakSet1, weakSet2);
-// AssertionError: Expected inputs to be strictly deep-equal:
+// AssertionError: Values have same structure but are not reference-equal:
 // + actual - expected
 //
-// + WeakSet { <items unknown> }
-// - WeakSet { <items unknown> }
+// WeakSet {
+//   <items unknown>
+// }
 
 // Comparing the same instance to itself succeeds
 assert.deepStrictEqual(weakSet1, weakSet1);
@@ -1018,11 +1019,12 @@ weakSet2.add(obj);
 
 // Comparing different instances fails, even with same contents
 assert.deepStrictEqual(weakSet1, weakSet2);
-// AssertionError: Expected inputs to be strictly deep-equal:
+// AssertionError: Values have same structure but are not reference-equal:
 // + actual - expected
 //
-// + WeakSet { <items unknown> }
-// - WeakSet { <items unknown> }
+// WeakSet {
+//   <items unknown>
+// }
 
 // Comparing the same instance to itself succeeds
 assert.deepStrictEqual(weakSet1, weakSet1);
Repository: denoland/deno
Pull request: fix(ext/node): don't throw error for unsupported signal binding on windows

This PR changes the handling of unsupported signals on windows. Currently it throws an error if `process.on` is called with unsupported signal (ex. SIGHUP) on windows. That causes #25675 for example.

This PR changes it to not throw the error instead let it only print the warning messages.

closes #25675

Changed files:
filename: ext/node/polyfills/process.ts
patch: @@ -517,6 +517,12 @@ Process.prototype.on = function (
       // Ignores SIGBREAK if the platform is not windows.
     } else if (event === "SIGTERM" && Deno.build.os === "windows") {
       // Ignores SIGTERM on windows.
+    } else if (
+      event !== "SIGBREAK" && event !== "SIGINT" && Deno.build.os === "windows"
+    ) {
+      // Ignores all signals except SIGBREAK and SIGINT on windows.
+      // deno-lint-ignore no-console
+      console.warn(`Ignoring signal "${event}" on Windows`);
     } else {
       EventEmitter.prototype.on.call(this, event, listener);
       Deno.addSignalListener(event as Deno.Signal, listener);
@@ -541,8 +547,10 @@ Process.prototype.off = function (
   } else if (event.startsWith("SIG")) {
     if (event === "SIGBREAK" && Deno.build.os !== "windows") {
       // Ignores SIGBREAK if the platform is not windows.
-    } else if (event === "SIGTERM" && Deno.build.os === "windows") {
-      // Ignores SIGTERM on windows.
+    } else if (
+      event !== "SIGBREAK" && event !== "SIGINT" && Deno.build.os === "windows"
+    ) {
+      // Ignores all signals except SIGBREAK and SIGINT on windows.
     } else {
       EventEmitter.prototype.off.call(this, event, listener);
       Deno.removeSignalListener(event as Deno.Signal, listener);

filename: tests/unit_node/process_test.ts
patch: @@ -25,6 +25,7 @@ import {
   assertThrows,
   fail,
 } from "@std/assert";
+import { assertSpyCall, assertSpyCalls, spy } from "@std/testing/mock";
 import { stripAnsiCode } from "@std/fmt/colors";
 import * as path from "@std/path";
 import { delay } from "@std/async/delay";
@@ -238,6 +239,33 @@ Deno.test({
   },
 });
 
+Deno.test({
+  name: "process.on - ignored signals on windows",
+  ignore: Deno.build.os !== "windows",
+  fn() {
+    const ignoredSignals = ["SIGHUP", "SIGUSR1", "SIGUSR2"];
+
+    for (const signal of ignoredSignals) {
+      using consoleSpy = spy(console, "warn");
+      const handler = () => {};
+      process.on(signal, handler);
+      process.off(signal, handler);
+      assertSpyCall(consoleSpy, 0, {
+        args: [`Ignoring signal "${signal}" on Windows`],
+      });
+    }
+
+    {
+      using consoleSpy = spy(console, "warn");
+      const handler = () => {};
+      process.on("SIGTERM", handler);
+      process.off("SIGTERM", handler);
+      // No warning is made for SIGTERM
+      assertSpyCalls(consoleSpy, 0);
+    }
+  },
+});
+
 Deno.test(
   { permissions: { run: true, read: true } },
   async function processKill() {
Repository: denoland/deno
Pull request: ci: bump fetch depth to unblock canary uploads

Current mac arm canaries are failing to upload because the existing latest commit hash
is more that 5 commits behind and it's not in the git history.

Changed files:
filename: .github/workflows/ci.generate.ts
patch: @@ -158,7 +158,7 @@ const cloneRepoStep = [{
     // Use depth > 1, because sometimes we need to rebuild main and if
     // other commits have landed it will become impossible to rebuild if
     // the checkout is too shallow.
-    "fetch-depth": 5,
+    "fetch-depth": 50,
     submodules: false,
   },
 }];

filename: .github/workflows/ci.yml
patch: @@ -33,7 +33,7 @@ jobs:
       - name: Clone repository
         uses: actions/checkout@v4
         with:
-          fetch-depth: 5
+          fetch-depth: 50
           submodules: false
         if: github.event.pull_request.draft == true
       - id: check
@@ -148,7 +148,7 @@ jobs:
       - name: Clone repository
         uses: actions/checkout@v4
         with:
-          fetch-depth: 5
+          fetch-depth: 50
           submodules: false
         if: '!(matrix.skip)'
       - name: Clone submodule ./tests/util/std
Repository: facebook/react
Pull request: [easy] Clarify folders in react devtools readme

## Summary

Clarify the folder from which we run various commands in the relay-devtools readme

## How did you test this change?

:eyes:

Changed files:
filename: packages/react-devtools/README.md
patch: @@ -129,7 +129,7 @@ To use the latest build from CI, run the following command from the root of the
 You can test the standalone DevTools by running the following:
 
 * **First, complete the prerequisite steps above! If you don't do it, none of the steps below will work.**
-* Then, run `yarn start:backend` and `yarn start:standalone` in `../react-devtools-core`
-* Run `yarn start` in this folder
+* Then, run `yarn start:backend` and `yarn start:standalone` in `packages/react-devtools-core`
+* Run `yarn start` in `packages/react-devtools`
 * Refresh the app after it has recompiled a change
 * For React Native, copy `react-devtools-core` to its `node_modules` to test your changes.
Repository: electron/electron
Pull request: build: use Node 20 in Appveyor images

#### Description of Change

Upgrades our Appveyor base images to use Node 20 instead of Node 18.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [ ] PR description included and stakeholders cc'd
- [ ] `npm test` passes
- [ ] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [ ] relevant documentation, tutorials, templates and examples are changed or added
- [ ] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: none


Changed files:
filename: appveyor-woa.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-130.0.6695.0
+image: e-130.0.6695.0-node-20
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default

filename: appveyor.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-130.0.6695.0
+image: e-130.0.6695.0-node-20
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default

filename: script/setup-win-for-dev.bat
patch: @@ -56,11 +56,14 @@ REM Install Windows SDK
 choco install windows-sdk-11-version-22h2-all
 
 REM Install nodejs python git and yarn needed dependencies
-choco install -y --force nodejs --version=18.12.1
+choco install -y --force nodejs --version=20.9.0
 choco install -y python2 git yarn
 choco install python --version 3.7.9
 call C:\ProgramData\chocolatey\bin\RefreshEnv.cmd
 SET PATH=C:\Python27\;C:\Python27\Scripts;C:\Python39\;C:\Python39\Scripts;%PATH%
+if not exist "C:\Users\appveyor\AppData\Roaming\npm" (
+  mkdir "C:\Users\appveyor\AppData\Roaming\npm"
+)
 
 REM Setup Depot Tools
 git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git C:\depot_tools
Repository: denoland/deno
Pull request: v2.0.0-rc.3


Changed files:
filename: Cargo.lock
patch: @@ -1146,7 +1146,7 @@ dependencies = [
 
 [[package]]
 name = "deno"
-version = "2.0.0-rc.2"
+version = "2.0.0-rc.3"
 dependencies = [
  "anstream",
  "async-trait",

filename: cli/Cargo.toml
patch: @@ -2,7 +2,7 @@
 
 [package]
 name = "deno"
-version = "2.0.0-rc.2"
+version = "2.0.0-rc.3"
 authors.workspace = true
 default-run = "deno"
 edition.workspace = true