helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: build: fix release, add newVersion for tagging

#### Description of Change

Fixes publish by passing in a new, needed variable to the ci-release-build script

#### 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: script/release/prepare-release.js
patch: @@ -14,7 +14,11 @@ const readline = require('node:readline');
 const releaseNotesGenerator = require('./notes/index.js');
 const { getCurrentBranch, ELECTRON_DIR } = require('../lib/utils.js');
 const bumpType = args._[0];
-const targetRepo = bumpType === 'nightly' ? 'nightlies' : 'electron';
+const targetRepo = getRepo();
+
+function getRepo () {
+  return bumpType === 'nightly' ? 'nightlies' : 'electron';
+}
 
 const octokit = new Octokit({
   auth: process.env.ELECTRON_GITHUB_TOKEN
@@ -138,9 +142,10 @@ async function pushRelease (branch) {
   }
 }
 
-async function runReleaseBuilds (branch) {
+async function runReleaseBuilds (branch, newVersion) {
   await ciReleaseBuild(branch, {
-    ghRelease: true
+    ghRelease: true,
+    newVersion
   });
 }
 
@@ -170,6 +175,8 @@ async function verifyNewVersion () {
     console.log(`${fail} Aborting release of ${newVersion}`);
     process.exit();
   }
+
+  return newVersion;
 }
 
 async function promptForVersion (version) {
@@ -205,10 +212,10 @@ async function prepareRelease (isBeta, notesOnly) {
     } else {
       const changes = await changesToRelease();
       if (changes) {
-        await verifyNewVersion();
+        const newVersion = await verifyNewVersion();
         await createRelease(currentBranch, isBeta);
         await pushRelease(currentBranch);
-        await runReleaseBuilds(currentBranch);
+        await runReleaseBuilds(currentBranch, newVersion);
       } else {
         console.log('There are no new changes to this branch since the last release, aborting release.');
         process.exit(1);
Repository: huggingface/transformers
Pull request: [`HybridCache`] disable automatic compilation

# What does this PR do?

Recently I've expanded auto compilation in `generate` from `StaticCache` only to all compilable caches, through a new `is_compileable` attribute.

This PR sets `HybridCache.is_compileable` to `False`, which stops automatic compilation. There have been reports of speed loss on models that use this cache -- disabling until the root cause is found.

Changed files:
filename: src/transformers/cache_utils.py
patch: @@ -1602,7 +1602,9 @@ class HybridCache(Cache):
         ```
     """
 
-    is_compileable = True
+    # TODO (joao): dive deeper into gemma2 and paligemma -- there are reports of speed loss with compilation. Revert
+    # ALL changes from the PR that commented the line below when reactivating it.
+    # is_compileable = True
 
     # TODO (joao): remove `=None` in non-optional arguments in v4.46. Remove from `OBJECTS_TO_IGNORE` as well.
     @deprecate_kwarg("layer_device_map", version="4.52.0")

filename: tests/generation/test_utils.py
patch: @@ -2118,6 +2118,9 @@ def test_generate_compile_model_forward(self):
         Tests that `.generate` is compatible with torch.compile without graph breaks, keeping the same results.
         ⚠️ Runs two sequential generations to ensure the cache doesn't get stuck after the first compiled run! ⚠️
         """
+        # Monkey-patching the HybridCache at test-time to continue testing compilation support
+        HybridCache.is_compileable = True
+
         for model_class in self.all_generative_model_classes:
             if not model_class._supports_static_cache:
                 self.skipTest("This model doesn't support static cache (= no expectations of compilation support)")
@@ -2214,6 +2217,9 @@ def test_generate_compilation_all_outputs(self):
         Tests that all optional outputs are behaving as expected when compilation is triggered.
         In essence, it's the same as `test_greedy_generate_dict_outputs`, but with automatic compilation triggered.
         """
+        # Monkey-patching the HybridCache at test-time to continue testing compilation support
+        HybridCache.is_compileable = True
+
         for model_class in self.all_generative_model_classes:
             if not model_class._supports_static_cache:
                 self.skipTest("This model doesn't support static cache (= no expectations of compilation support)")
Repository: nodejs/node
Pull request: meta: move one or more collaborators to emeritus

This PR was generated by the [`find-inactive-collaborators.yml` workflow](https://github.com/nodejs/node/blob/main/.github/workflows/find-inactive-collaborators.yml).

@nodejs/tsc Please follow up with the [offboarding tasks](https://github.com/nodejs/node/blob/main/doc/contributing/offboarding.md).

Changed files:
filename: README.md
patch: @@ -320,8 +320,6 @@ For information about the governance of the Node.js project, see
   **Kohei Ueno** <<kohei.ueno119@gmail.com>> (he/him)
 * [daeyeon](https://github.com/daeyeon) -
   **Daeyeon Jeong** <<daeyeon.dev@gmail.com>> (he/him)
-* [danielleadams](https://github.com/danielleadams) -
-  **Danielle Adams** <<adamzdanielle@gmail.com>> (she/her)
 * [debadree25](https://github.com/debadree25) -
   **Debadree Chatterjee** <<debadree333@gmail.com>> (he/him)
 * [deokjinkim](https://github.com/deokjinkim) -
@@ -502,6 +500,8 @@ For information about the governance of the Node.js project, see
   **Claudio Rodriguez** <<cjrodr@yahoo.com>>
 * [danbev](https://github.com/danbev) -
   **Daniel Bevenius** <<daniel.bevenius@gmail.com>> (he/him)
+* [danielleadams](https://github.com/danielleadams) -
+  **Danielle Adams** <<adamzdanielle@gmail.com>> (she/her)
 * [DavidCai1993](https://github.com/DavidCai1993) -
   **David Cai** <<davidcai1993@yahoo.com>> (he/him)
 * [davisjam](https://github.com/davisjam) -
Repository: facebook/react
Pull request: [React Native] Set allowConcurrentByDefault = true

## Overview

React Native needs this flag on for Relay tests.

Changed files:
filename: packages/shared/forks/ReactFeatureFlags.native-fb.js
patch: @@ -60,7 +60,7 @@ export const enableRecursiveCommitTraversal = false;
 export const disableSchedulerTimeoutInWorkLoop = false;
 export const enableLazyContextPropagation = false;
 export const enableSyncDefaultUpdates = false;
-export const allowConcurrentByDefault = false;
+export const allowConcurrentByDefault = true;
 
 // Flow magic to verify the exports of this file match the original version.
 // eslint-disable-next-line no-unused-vars

filename: packages/shared/forks/ReactFeatureFlags.test-renderer.native.js
patch: @@ -59,7 +59,7 @@ export const enableRecursiveCommitTraversal = false;
 export const disableSchedulerTimeoutInWorkLoop = false;
 export const enableLazyContextPropagation = false;
 export const enableSyncDefaultUpdates = false;
-export const allowConcurrentByDefault = false;
+export const allowConcurrentByDefault = true;
 
 // Flow magic to verify the exports of this file match the original version.
 // eslint-disable-next-line no-unused-vars
Repository: ggml-org/llama.cpp
Pull request: Server: Cache position calculation error(#12160)

Bug for cache reuse：When using the `llama_kv_cache_seq_rm` function, the positions of tokens after `head_c` are offset due to the `kv_shift`. If `head_c` is updated incorrectly or not properly adjusted after the shift, it may cause valid tokens to be removed in subsequent operations. Here's a clear explanation of the process:

1. **Initial KV Cache State**:
   ```
   Cache Tokens:   a b c d e f g h j
   Cell Positions: 0 1 2 3 4 5 6 7 8
   New Tokens: a b e f h j
               0 1 - - - -
   ```

2. **First Operation**:
   - `head_p` is set to 2, and `head_c` is also set to 2.
   - The token 'e' is found, so `head_c` is updated to 4, and `n_match` is set to 2.
   - `kv_shift` is set to -2.
   - Tokens from `head_p` to `head_c` (positions 2 to 4: tokens 'c', 'd') are removed.
       ```
     Cache Tokens:   a b c d e f g h j
     Cell Positions: 0 1 - - 4 5 6 7 8
     ```
   - The remaining tokens' positions are updated by adding `kv_shift` (-2):
     ```
     Cache Tokens:   a b c d e f g h j
     Cell Positions: 0 1 - - 2 3 4 5 6
     ```
   - `head_p` is updated to `head_p + n_match` (2 + 2 = 4).
   - `head_c` is updated to `head_c + n_match` (4 + 2 = 6).

3. **Second Operation**:
   - `head_p` is 4, and `head_c` is 6.
   - The token 'h' is found, so `head_c` is updated to 7.
   - Tokens from `head_p` to `head_c` (positions 4 to 7: tokens 'g', 'h', 'j') are removed.
     ```
     Cache Tokens:   a b c d e f g h j
     Cell Positions: 0 1 - - 2 3 - - -
     ```

   - After this operation, valid tokens('h', 'j') in the cache are removed because their positions have been shifted incorrectly.

This demonstrates how improper handling of `kv_shift` and `head_c` updates can lead to the unintended removal of valid tokens in the KV cache.

Changed files:
filename: examples/server/server.cpp
patch: @@ -3003,7 +3003,7 @@ struct server_context {
                                             const int64_t kv_shift = (int64_t) head_p - (int64_t) head_c;
 
                                             llama_kv_cache_seq_rm (ctx, slot.id, head_p, head_c);
-                                            llama_kv_cache_seq_add(ctx, slot.id, head_c, -1,     kv_shift);
+                                            llama_kv_cache_seq_add(ctx, slot.id, head_c, head_c + n_match, kv_shift);
 
                                             for (size_t i = 0; i < n_match; i++) {
                                                 slot.cache_tokens[head_p + i] = slot.cache_tokens[head_c + i];
Repository: denoland/deno
Pull request: fix: allow WPT to successfully exit using `--exit-zero`

I went with `--exit-zero`. Happy to change to `--no-exit` if feelings are strong.

Supercedes #23417

Changed files:
filename: .github/workflows/wpt_epoch.yml
patch: @@ -72,7 +72,7 @@ jobs:
           deno run --unstable --allow-write --allow-read --allow-net           \
             --allow-env --allow-run --lock=tools/deno.lock.json                \
             ./tests/wpt/wpt.ts run                                                 \                                                \
-            --binary=$(which deno) --quiet --release --no-ignore --json=wpt.json --wptreport=wptreport.json
+            --binary=$(which deno) --quiet --release --no-ignore --json=wpt.json --wptreport=wptreport.json --exit-zero
 
       - name: Upload wpt results to wpt.fyi
         env:

filename: tests/wpt/wpt.ts
patch: @@ -550,6 +550,12 @@ function reportFinal(
     }. ${finalPassedCount} passed; ${finalFailedCount} failed; ${finalExpectedFailedAndFailedCount} expected failure; total ${finalTotalCount} (${duration}ms)\n`,
   );
 
+  // We ignore the exit code of the test run because the CI job reports the
+  // results to WPT.fyi, and we still want to report failure.
+  if (Deno.args.includes("--exit-zero")) {
+    return 0;
+  }
+
   return failed ? 1 : 0;
 }
Repository: denoland/deno
Pull request: fix(ci): Fix bench job

Forgot to add the step to clone the new submodule added in #23395 😅.

Changed files:
filename: .github/workflows/ci.generate.ts
patch: @@ -457,6 +457,10 @@ const ci = {
           ...submoduleStep("./tests/node_compat/runner/suite"),
           if: "matrix.job == 'lint' && matrix.os == 'linux'",
         },
+        {
+          ...submoduleStep("./cli/bench/testdata/lsp_benchdata"),
+          if: "matrix.job == 'bench'",
+        },
         {
           name: "Create source tarballs (release, linux)",
           if: [

filename: .github/workflows/ci.yml
patch: @@ -160,6 +160,9 @@ jobs:
       - name: Clone submodule ./tests/node_compat/runner/suite
         run: git submodule update --init --recursive --depth=1 -- ./tests/node_compat/runner/suite
         if: '!(matrix.skip) && (matrix.job == ''lint'' && matrix.os == ''linux'')'
+      - name: Clone submodule ./cli/bench/testdata/lsp_benchdata
+        run: git submodule update --init --recursive --depth=1 -- ./cli/bench/testdata/lsp_benchdata
+        if: '!(matrix.skip) && (matrix.job == ''bench'')'
       - name: 'Create source tarballs (release, linux)'
         if: |-
           !(matrix.skip) && (matrix.os == 'linux' &&
Repository: vercel/next.js
Pull request: devlow-bench: wait for complete ready for server startup event

Previously, we marked the server startup whenever a local url was shown in stdio. Next.js shows this url as soon as it can to make it actionable sooner, before the server is truly ready.

This changes makes the event record the time until the “Ready in Nms” message is shown instead.

Test Plan: `./node_modules/.bin/devlow-bench ./scripts/devlow-bench.mjs` and validate server startup is recorded.


Closes PACK-4184

Changed files:
filename: scripts/devlow-bench.mjs
patch: @@ -8,6 +8,8 @@ import { command } from '@vercel/devlow-bench/shell'
 import { waitForFile } from '@vercel/devlow-bench/file'
 
 const REPO_ROOT = fileURLToPath(new URL('..', import.meta.url))
+const START_SERVER_REGEXP = /Ready in \d+/
+const URL_REGEXP = /Local:\s+(?<url>.+)\n/
 
 const GIT_SHA =
   process.env.GITHUB_SHA ??
@@ -101,10 +103,12 @@ const nextBuildWorkflow =
       cleanupTasks.push(killShell)
 
       // wait for server to be ready
-      const START_SERVER_REGEXP = /Local:\s+(?<url>.+)\n/
       const {
         groups: { url },
-      } = await shell.waitForOutput(START_SERVER_REGEXP)
+      } = await shell.waitForOutput(URL_REGEXP)
+
+      // wait for server to be ready
+      await shell.waitForOutput(START_SERVER_REGEXP)
       await measureTime('server startup', { props: { turbopack, page } })
       await shell.reportMemUsage('mem usage after startup', {
         props: { turbopack, page },
@@ -188,7 +192,7 @@ const nextBuildWorkflow =
       // wait for server to be ready
       const {
         groups: { url: url2 },
-      } = await shell.waitForOutput(START_SERVER_REGEXP)
+      } = await shell.waitForOutput(URL_REGEXP)
       await shell.reportMemUsage('mem usage after startup with cache')
 
       // open page
@@ -279,10 +283,12 @@ const nextDevWorkflow =
       cleanupTasks.push(killShell)
 
       // wait for server to be ready
-      const START_SERVER_REGEXP = /Local:\s+(?<url>.+)\n/
       const {
         groups: { url },
-      } = await shell.waitForOutput(START_SERVER_REGEXP)
+      } = await shell.waitForOutput(URL_REGEXP)
+
+      // wait for server to be ready
+      await shell.waitForOutput(START_SERVER_REGEXP)
       await measureTime('server startup', { props: { turbopack, page } })
       await shell.reportMemUsage('mem usage after startup', {
         props: { turbopack, page },
@@ -508,7 +514,7 @@ const nextDevWorkflow =
       // wait for server to be ready
       const {
         groups: { url: url2 },
-      } = await shell.waitForOutput(START_SERVER_REGEXP)
+      } = await shell.waitForOutput(URL_REGEXP)
       await shell.reportMemUsage('mem usage after startup with cache')
 
       // open page
Repository: huggingface/transformers
Pull request: Fix check for XPU. PyTorch >= 2.6 no longer needs ipex.

Update is_torch_xpu_available. Only check for ipex module if torch version is less than 2.6. Ipex is no longer necessary as of torch 2.6.

@Rocketknight1


Changed files:
filename: src/transformers/utils/import_utils.py
patch: @@ -896,17 +896,19 @@ def get_major_and_minor_from_version(full_version):
 @lru_cache
 def is_torch_xpu_available(check_device=False):
     """
-    Checks if XPU acceleration is available either via `intel_extension_for_pytorch` or
-    via stock PyTorch (>=2.4) and potentially if a XPU is in the environment
+    Checks if XPU acceleration is available either via native PyTorch (>=2.6),
+    `intel_extension_for_pytorch` or via stock PyTorch (>=2.4) and potentially
+    if a XPU is in the environment.
     """
     if not is_torch_available():
         return False
 
     torch_version = version.parse(_torch_version)
-    if is_ipex_available():
-        import intel_extension_for_pytorch  # noqa: F401
-    elif torch_version.major < 2 or (torch_version.major == 2 and torch_version.minor < 4):
-        return False
+    if torch_version.major < 2 or (torch_version.major == 2 and torch_version.minor < 6):
+        if is_ipex_available():
+            import intel_extension_for_pytorch  # noqa: F401
+        elif torch_version.major < 2 or (torch_version.major == 2 and torch_version.minor < 4):
+            return False
 
     import torch
Repository: ggml-org/llama.cpp
Pull request: `server`: fix response_format w/ json_schema.schema

Fixes #11988

(regression caused by embarrassing typo in https://github.com/ggml-org/llama.cpp/commit/63e489c025d61c7ca5ec06c5d10f36e2b76aaa1d ; added a missing server test case)

Changed files:
filename: examples/server/tests/unit/test_chat_completion.py
patch: @@ -144,6 +144,7 @@ def test_apply_chat_template():
 @pytest.mark.parametrize("response_format,n_predicted,re_content", [
     ({"type": "json_object", "schema": {"const": "42"}}, 6, "\"42\""),
     ({"type": "json_object", "schema": {"items": [{"type": "integer"}]}}, 10, "[ -3000 ]"),
+    ({"type": "json_schema", "json_schema": {"schema": {"const": "foooooo"}}}, 10, "\"foooooo\""),
     ({"type": "json_object"}, 10, "(\\{|John)+"),
     ({"type": "sound"}, 0, None),
     # invalid response format (expected to fail)

filename: examples/server/utils.hpp
patch: @@ -590,8 +590,8 @@ static json oaicompat_completion_params_parse(
         if (response_type == "json_object") {
             json_schema = json_value(response_format, "schema", json::object());
         } else if (response_type == "json_schema") {
-            json json_schema = json_value(response_format, "json_schema", json::object());
-            json_schema = json_value(json_schema, "schema", json::object());
+            auto schema_wrapper = json_value(response_format, "json_schema", json::object());
+            json_schema = json_value(schema_wrapper, "schema", json::object());
         } else if (!response_type.empty() && response_type != "text") {
             throw std::runtime_error("response_format type must be one of \"text\" or \"json_object\", but got: " + response_type);
         }
Repository: denoland/deno
Pull request: fix(ext/node): worker_threads.receiveMessageOnPort doesn't panic

Follow up to https://github.com/denoland/deno/pull/23386.
Instead of using async `recv()` method, it was replaced
with a poll based function that doesn't hold onto
RefCell borrow across await point.

Fixes https://github.com/denoland/deno/issues/23362

Changed files:
filename: ext/web/message_port.rs
patch: @@ -15,6 +15,7 @@ use deno_core::OpState;
 use deno_core::RcRef;
 use deno_core::Resource;
 use deno_core::ResourceId;
+use futures::future::poll_fn;
 use serde::Deserialize;
 use serde::Serialize;
 use tokio::sync::mpsc::error::TryRecvError;
@@ -52,16 +53,19 @@ impl MessagePort {
     Ok(())
   }
 
-  #[allow(clippy::await_holding_refcell_ref)] // TODO(ry) remove!
   pub async fn recv(
     &self,
     state: Rc<RefCell<OpState>>,
   ) -> Result<Option<JsMessageData>, AnyError> {
-    let mut rx = self
-      .rx
-      .try_borrow_mut()
-      .map_err(|_| type_error("Port receiver is already borrowed"))?;
-    if let Some((data, transferables)) = rx.recv().await {
+    let rx = &self.rx;
+
+    let maybe_data = poll_fn(|cx| {
+      let mut rx = rx.borrow_mut();
+      rx.poll_recv(cx)
+    })
+    .await;
+
+    if let Some((data, transferables)) = maybe_data {
       let js_transferables =
         serialize_transferables(&mut state.borrow_mut(), transferables);
       return Ok(Some(JsMessageData {

filename: tests/unit_node/worker_threads_test.ts
patch: @@ -418,21 +418,45 @@ Deno.test({
 // Regression test for https://github.com/denoland/deno/issues/23362
 Deno.test("[node/worker_threads] receiveMessageOnPort works if there's pending read", function () {
   const { port1, port2 } = new workerThreads.MessageChannel();
+  const { port1: port3, port2: port4 } = new workerThreads.MessageChannel();
+  const { port1: port5, port2: port6 } = new workerThreads.MessageChannel();
 
   const message1 = { hello: "world" };
   const message2 = { foo: "bar" };
 
   assertEquals(workerThreads.receiveMessageOnPort(port2), undefined);
   port2.start();
+  port4.start();
+  port6.start();
 
   port1.postMessage(message1);
   port1.postMessage(message2);
+  port3.postMessage(message1);
+  port3.postMessage(message2);
+  port5.postMessage(message1);
+  port5.postMessage(message2);
   assertEquals(workerThreads.receiveMessageOnPort(port2), {
     message: message1,
   });
   assertEquals(workerThreads.receiveMessageOnPort(port2), {
     message: message2,
   });
+  assertEquals(workerThreads.receiveMessageOnPort(port4), {
+    message: message1,
+  });
+  assertEquals(workerThreads.receiveMessageOnPort(port4), {
+    message: message2,
+  });
+  assertEquals(workerThreads.receiveMessageOnPort(port6), {
+    message: message1,
+  });
+  assertEquals(workerThreads.receiveMessageOnPort(port6), {
+    message: message2,
+  });
   port1.close();
   port2.close();
+  port3.close();
+  port4.close();
+  port5.close();
+  port6.close();
 });
Repository: facebook/react
Pull request: Renamed function in error log issue #21446

<!--
  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 `master`.
  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

<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->

## Test Plan

<!-- Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. -->


Changed files:
filename: packages/shared/getComponentNameFromType.js
patch: @@ -53,7 +53,7 @@ export default function getComponentNameFromType(type: mixed): string | null {
   if (__DEV__) {
     if (typeof (type: any).tag === 'number') {
       console.error(
-        'Received an unexpected object in getComponentName(). ' +
+        'Received an unexpected object in getComponentNameFromType(). ' +
           'This is likely a bug in React. Please file an issue.',
       );
     }