helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: build: use `windows-2025` runner

GitHub is transitioning `windows-latest` to it.

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: .github/workflows/coverage-windows.yml
patch: @@ -43,7 +43,7 @@ permissions:
 jobs:
   coverage-windows:
     if: github.event.pull_request.draft == false
-    runs-on: windows-2022
+    runs-on: windows-2025
     steps:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4.2.2
         with:
Repository: ollama/ollama
Pull request: Report errors on server lookup instead of path lookup failure

This should help identify more details on the failure mode for #3738 

Changed files:
filename: llm/server.go
patch: @@ -208,6 +208,12 @@ func NewLlamaServer(gpus gpu.GpuInfoList, model string, ggml *GGML, adapters, pr
 
 	for i := 0; i < len(servers); i++ {
 		dir := availableServers[servers[i]]
+		if dir == "" {
+			// Shouldn't happen
+			finalErr = fmt.Errorf("[%d] server %s not listed in available servers %v", i, servers[i], availableServers)
+			slog.Error("sever list inconsistent", "error", finalErr)
+			continue
+		}
 
 		// Find an availableServers  port, retry on each iterration in case the failure was a port conflict race
 		port := 0
Repository: facebook/react
Pull request: Unit Test for `findNodeHandle` Error Behavior

## Summary

As promised on https://github.com/facebook/react/pull/29627, this creates a unit test for the `findNodeHandle` error that prevents developers from calling it within render methods.

## How did you test this change?

```
$ yarn test ReactFabric-test.internal.js
```


Changed files:
filename: packages/react-native-renderer/src/__tests__/ReactFabric-test.internal.js
patch: @@ -1306,6 +1306,40 @@ describe('ReactFabric', () => {
     );
   });
 
+  it('findNodeHandle errors when called from render', async () => {
+    class TestComponent extends React.Component {
+      render() {
+        ReactFabric.findNodeHandle(this);
+        return null;
+      }
+    }
+    await expect(async () => {
+      await act(() => {
+        ReactFabric.render(<TestComponent />, 11, null, true);
+      });
+    }).toErrorDev([
+      'TestComponent is accessing findNodeHandle inside its render(). ' +
+        'render() should be a pure function of props and state. It should ' +
+        'never access something that requires stale data from the previous ' +
+        'render, such as refs. Move this logic to componentDidMount and ' +
+        'componentDidUpdate instead.',
+    ]);
+  });
+
+  it("findNodeHandle doesn't error when called outside render", async () => {
+    class TestComponent extends React.Component {
+      render() {
+        return null;
+      }
+      componentDidMount() {
+        ReactFabric.findNodeHandle(this);
+      }
+    }
+    await act(() => {
+      ReactFabric.render(<TestComponent />, 11, null, true);
+    });
+  });
+
   it('should no-op if calling sendAccessibilityEvent on unmounted refs', async () => {
     const View = createReactNativeComponentClass('RCTView', () => ({
       validAttributes: {foo: true},
Repository: vercel/next.js
Pull request: Turbopack: Remove workaround in hyper for rustc miscompilation bug on macos intel

Reverts https://github.com/vercel/next.js/pull/81950

This bug was fixed a few months ago upstream in rustc with https://github.com/rust-lang/rust/pull/143126

We worked around this by patching the hyper crate since updating rustc was too risky to do in a patch release. We've since upgraded our toolchain.

Closes PACK-5641

Changed files:
filename: Cargo.lock
patch: @@ -2831,19 +2831,22 @@ dependencies = [
 
 [[package]]
 name = "hyper"
-version = "1.6.0"
-source = "git+https://github.com/bgw/hyper-rs.git?branch=v1.6.0-with-macos-intel-miscompilation-workaround#ab3544930722e6c270c16d3239dbb1d58f713393"
+version = "1.7.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "eb3aa54a13a0dfe7fbe3a59e0c76093041720fdc77b110cc0fc260fafb4dc51e"
 dependencies = [
+ "atomic-waker",
  "bytes",
  "futures-channel",
- "futures-util",
+ "futures-core",
  "h2 0.4.7",
  "http 1.1.0",
  "http-body 1.0.1",
  "httparse",
  "httpdate",
  "itoa",
  "pin-project-lite",
+ "pin-utils",
  "smallvec",
  "tokio",
  "want",
@@ -2856,7 +2859,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "e3c93eb611681b207e1fe55d5a71ecf91572ec8a6705cdb6857f7d8d5242cf58"
 dependencies = [
  "http 1.1.0",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-util",
  "rustls",
  "rustls-native-certs",
@@ -2873,7 +2876,7 @@ version = "0.5.2"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "2b90d566bffbce6a75bd8b09a05aa8c2cb1fabb6cb348f8840c9e4c90a0d83b0"
 dependencies = [
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-util",
  "pin-project-lite",
  "tokio",
@@ -2901,7 +2904,7 @@ checksum = "70206fc6890eaca9fde8a0bf71caa2ddfc9fe045ac9e5c70df101a7dbde866e0"
 dependencies = [
  "bytes",
  "http-body-util",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-util",
  "native-tls",
  "tokio",
@@ -2935,7 +2938,7 @@ dependencies = [
  "futures-util",
  "http 1.1.0",
  "http-body 1.0.1",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "ipnet",
  "libc",
  "percent-encoding",
@@ -4073,7 +4076,7 @@ dependencies = [
  "http 1.1.0",
  "http-body 1.0.1",
  "http-body-util",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-util",
  "log",
  "rand 0.9.0",
@@ -5903,7 +5906,7 @@ dependencies = [
  "http 1.1.0",
  "http-body 1.0.1",
  "http-body-util",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-rustls",
  "hyper-tls 0.6.0",
  "hyper-util",
@@ -8853,7 +8856,7 @@ dependencies = [
  "http 1.1.0",
  "http-body 1.0.1",
  "http-body-util",
- "hyper 1.6.0",
+ "hyper 1.7.0",
  "hyper-timeout",
  "hyper-util",
  "percent-encoding",

filename: Cargo.toml
patch: @@ -450,5 +450,4 @@ webbrowser = "0.8.7"
 inventory = "0.3.21"
 
 [patch.crates-io]
-hyper = { git = "https://github.com/bgw/hyper-rs.git", branch = "v1.6.0-with-macos-intel-miscompilation-workaround" }
 mdxjs = { git = "https://github.com/mischnic/mdxjs-rs.git", branch = "swc-core-32" }
Repository: denoland/deno
Pull request: ci: maybe fix spec test timeout

This is what claude came up with.

Changed files:
filename: tests/util/lib/builders.rs
patch: @@ -385,9 +385,16 @@ impl TestContext {
 
 fn kill_process(pid: u32) {
   #[cfg(unix)]
-  // SAFETY: We're sending SIGKILL to a process we spawned.
-  unsafe {
-    libc::kill(pid as i32, libc::SIGKILL);
+  {
+    // kill the process tree by first killing children via
+    // pkill, then the process itself
+    let _ = std::process::Command::new("pkill")
+      .args(["-9", "-P", &pid.to_string()])
+      .output();
+    // SAFETY: We're sending SIGKILL to a process we spawned.
+    unsafe {
+      libc::kill(pid as i32, libc::SIGKILL);
+    }
   }
   #[cfg(not(unix))]
   {
Repository: huggingface/transformers
Pull request: Bump to hfh 1.0.0.rc5 to fix test

Should be the current failing CI. 

See https://github.com/huggingface/huggingface_hub/pull/3433 for info.

(related to [internal slack thread](https://huggingface.slack.com/archives/C01NE71C4F7/p1760022191957959))

Changed files:
filename: setup.py
patch: @@ -114,7 +114,7 @@
     "GitPython<3.1.19",
     "hf-doc-builder>=0.3.0",
     "hf_xet",
-    "huggingface-hub==1.0.0.rc4",
+    "huggingface-hub==1.0.0.rc5",
     "importlib_metadata",
     "ipadic>=1.0.0,<2.0",
     "jinja2>=3.1.0",

filename: src/transformers/dependency_versions_table.py
patch: @@ -23,7 +23,7 @@
     "GitPython": "GitPython<3.1.19",
     "hf-doc-builder": "hf-doc-builder>=0.3.0",
     "hf_xet": "hf_xet",
-    "huggingface-hub": "huggingface-hub==1.0.0.rc4",
+    "huggingface-hub": "huggingface-hub==1.0.0.rc5",
     "importlib_metadata": "importlib_metadata",
     "ipadic": "ipadic>=1.0.0,<2.0",
     "jinja2": "jinja2>=3.1.0",
Repository: nodejs/node
Pull request: doc: mark `path.matchesGlob` as stable

All other glob features were marked stable in https://github.com/nodejs/node/pull/57513, and this function stopped emitting experimental warnings in https://github.com/nodejs/node/pull/58236.

However, `path.matchesGlob` was never explicitly marked stable.

Changed files:
filename: doc/api/path.md
patch: @@ -289,10 +289,12 @@ path.format({
 added:
   - v22.5.0
   - v20.17.0
+changes:
+  - version: REPLACEME
+    pr-url: https://github.com/nodejs/node/pull/59572
+    description: Marking the API stable.
 -->
 
-> Stability: 1 - Experimental
-
 * `path` {string} The path to glob-match against.
 * `pattern` {string} The glob to check the path against.
 * Returns: {boolean} Whether or not the `path` matched the `pattern`.
Repository: electron/electron
Pull request: build: write abi version to published npm package

This adds a helper file that makes it easier for tools like `node-abi` to determine the ABI version of an otherwise unknown package. `node-abi` is a pretty massive source of annoyance for folks, even for seasoned Electron App developers it's an annoying thing you need to keep ensuring you update. Package managers don't make it easy, so instead to mitigate this as much as possible I'm proposing we write this file to disk, and then in `node-abi` if we are resolving a version we **don't recognize** we try to find this file on disk for a matching electron version. If it matches, and it exists, we can serve it and app developers don't need to do any package manager shenanigans.

Notes: Added `abi_version` file to the npm package

Changed files:
filename: script/release/bin/publish-to-npm.ts
patch: @@ -136,6 +136,20 @@ new Promise<string>((resolve, reject) => {
 
     return release;
   })
+  .then(async (release) => {
+    const gnArgs = await fs.promises.readFile(path.resolve(ELECTRON_DIR, 'build/args/all.gn'), 'utf8');
+
+    const abiVersionLine = gnArgs.split('\n').find((line) => line.startsWith('node_module_version = '));
+    const abiVersion = abiVersionLine ? abiVersionLine.split('=')[1].trim() : null;
+    if (!abiVersion) {
+      throw new Error('Could not find node_module_version in GN args');
+    }
+
+    const abiVersionFile = path.join(tempDir, 'abi_version');
+    await fs.promises.writeFile(abiVersionFile, abiVersion);
+
+    return release;
+  })
   .then(async (release) => {
     const currentBranch = await getCurrentBranch();
Repository: ollama/ollama
Pull request: fix: rope

Some models set RopeFrequencyBase and RopeFrequencyScale. Removing these fields makes those models unusable

Changed files:
filename: api/types.go
patch: @@ -122,6 +122,11 @@ type Runner struct {
 	UseMMap   bool `json:"use_mmap,omitempty"`
 	UseMLock  bool `json:"use_mlock,omitempty"`
 	NumThread int  `json:"num_thread,omitempty"`
+
+	// Unused: RopeFrequencyBase is ignored. Instead the value in the model will be used
+	RopeFrequencyBase float32 `json:"rope_frequency_base,omitempty"`
+	// Unused: RopeFrequencyScale is ignored. Instead the value in the model will be used
+	RopeFrequencyScale float32 `json:"rope_frequency_scale,omitempty"`
 }
 
 type EmbeddingRequest struct {
Repository: ggml-org/llama.cpp
Pull request: model-conversion : use CONVERTED_EMBEDDING_MODEL for embedding_verify_logits

This commit updates the embedding model verification script to use the CONVERTED_EMBEDDING_MODEL environment variable instead of using the EMBEDDING_MODEL_PATH (the original embedding model path) as the basis for the converted model file name.

The motivation for this that currently if the converted embedding model file name differs from the original embedding model directory/name the verification script will look for the wrong .bin files that were generating when running the models.


Changed files:
filename: examples/model-conversion/scripts/embedding/compare-embeddings-logits.sh
patch: @@ -34,8 +34,11 @@ done
 MODEL_PATH="${MODEL_PATH:-"$EMBEDDING_MODEL_PATH"}"
 MODEL_NAME="${MODEL_NAME:-$(basename "$MODEL_PATH")}"
 
+CONVERTED_MODEL_PATH="${CONVERTED_EMBEDDING_PATH:-"$CONVERTED_EMBEDDING_MODEL"}"
+CONVERTED_MODEL_NAME="${CONVERTED_MODEL_NAME:-$(basename "$CONVERTED_MODEL_PATH" .gguf)}"
+
 if [ -t 0 ]; then
-    CPP_EMBEDDINGS="data/llamacpp-${MODEL_NAME}-embeddings.bin"
+    CPP_EMBEDDINGS="data/llamacpp-${CONVERTED_MODEL_NAME}-embeddings.bin"
 else
     # Process piped JSON data and convert to binary (matching logits.cpp format)
     TEMP_FILE=$(mktemp /tmp/tmp.XXXXXX.binn)
Repository: huggingface/transformers
Pull request: More trainer cleaning 

# What does this PR do?

This PR removes 2 unused args : `_n_gpu` and `mp_parameters`

Changed files:
filename: src/transformers/training_args.py
patch: @@ -1272,12 +1272,6 @@ class TrainingArguments:
             "help": "Whether to recursively concat inputs/losses/labels/predictions across batches. If `False`, will instead store them as lists, with each batch kept separate."
         },
     )
-    _n_gpu: int = field(init=False, repr=False, default=-1)
-    mp_parameters: str = field(
-        default="",
-        metadata={"help": "Used by the SageMaker launcher to send mp-specific args. Ignored in Trainer"},
-    )
-
     auto_find_batch_size: bool = field(
         default=False,
         metadata={
Repository: facebook/react
Pull request: [compiler] Publish to latest tag

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #30666

> [!NOTE]
> The `latest` tag is published by default if no tag is specified, which
> is what we had done since the first release of the compiler

In my last PR to auto publish compiler releases I had added the
experimental tag to be used in publishing. However because we had
already previously published to the latest tag (which is non-removable)
this means that the `latest` tag is pinned to an old version. That makes
untagged installs of the compiler default to that old version instead of
whatever is the latest.

This changes the behavior back to what it was before. Since we are still
in the experimental release of the compiler anyway it seems fine to use
the latest tag. When we reach stable, we can update this to only push to
latest for stable releases.

Changed files:
filename: compiler/scripts/release/publish.js
patch: @@ -162,7 +162,9 @@ async function main() {
             'publish',
             ...opts,
             '--registry=https://registry.npmjs.org',
-            '--tag=experimental',
+            // For now, since the compiler is experimental only, to simplify installation we push
+            // to the `latest` tag
+            '--tag=latest',
           ],
           {
             cwd: pkgDir,
Repository: ollama/ollama
Pull request: add OLLAMA_KEEP_ALIVE env variable to FAQ


Changed files:
filename: docs/faq.md
patch: @@ -228,3 +228,7 @@ To unload the model and free up memory use:
 ```shell
 curl http://localhost:11434/api/generate -d '{"model": "llama2", "keep_alive": 0}'
 ```
+
+Alternatively, you can change the amount of time all models are loaded into memory by setting the `OLLAMA_KEEP_ALIVE` environment variable when starting the Ollama server. The `OLLAMA_KEEP_ALIVE` variable uses the same parameter types as the `keep_alive` parameter types mentioned above. Refer to section explaining [how to configure the Ollama server](#how-do-i-configure-ollama-server) to correctly set the environment variable.
+
+If you wish to override the `OLLAMA_KEEP_ALIVE` setting, use the `keep_alive` API parameter with the `/api/generate` or `/api/chat` API endpoints.
Repository: nodejs/node
Pull request: wasi: fix `clean` target in `test/wasi/Makefile`

Refs: https://www.gnu.org/software/make/manual/make.html#Cleanup
Refs: https://www.gnu.org/software/make/manual/make.html#Parallel-Disable

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/wasi/Makefile
patch: @@ -12,5 +12,7 @@ wasm/pthread.wasm : c/pthread.c
 wasm/%.wasm : c/%.c
 	$(CC) $< $(CFLAGS) --target=$(TARGET) --sysroot=$(SYSROOT) -s -o $@
 
-.PHONY clean:
+.PHONY: clean
+.NOTPARALLEL: clean
+clean:
 	rm -f $(OBJ)
Repository: vercel/next.js
Pull request: Add middleware to routes order doc

This adds `middleware` in the routes order to clarify where it comes in priority. 

Changed files:
filename: docs/01-app/03-api-reference/05-config/01-next-config-js/rewrites.mdx
patch: @@ -90,10 +90,11 @@ The order Next.js routes are checked is:
 
 1. [headers](/docs/app/api-reference/config/next-config-js/headers) are checked/applied
 2. [redirects](/docs/app/api-reference/config/next-config-js/redirects) are checked/applied
-3. `beforeFiles` rewrites are checked/applied
-4. static files from the [public directory](/docs/app/api-reference/file-conventions/public-folder), `_next/static` files, and non-dynamic pages are checked/served
-5. `afterFiles` rewrites are checked/applied, if one of these rewrites is matched we check dynamic routes/static files after each match
-6. `fallback` rewrites are checked/applied, these are applied before rendering the 404 page and after dynamic routes/all static assets have been checked. If you use [fallback: true/'blocking'](/docs/pages/api-reference/functions/get-static-paths#fallback-true) in `getStaticPaths`, the fallback `rewrites` defined in your `next.config.js` will _not_ be run.
+3. [middleware](/docs/app/api-reference/file-conventions/middleware)
+4. `beforeFiles` rewrites are checked/applied
+5. static files from the [public directory](/docs/app/api-reference/file-conventions/public-folder), `_next/static` files, and non-dynamic pages are checked/served
+6. `afterFiles` rewrites are checked/applied, if one of these rewrites is matched we check dynamic routes/static files after each match
+7. `fallback` rewrites are checked/applied, these are applied before rendering the 404 page and after dynamic routes/all static assets have been checked. If you use [fallback: true/'blocking'](/docs/pages/api-reference/functions/get-static-paths#fallback-true) in `getStaticPaths`, the fallback `rewrites` defined in your `next.config.js` will _not_ be run.
 
 </AppOnly>
Repository: electron/electron
Pull request: fix: Reland "[accessibility] Platform node lifetime cleanups"

Backport of #47590

See that PR for details.


Notes: none.

Changed files:
filename: shell/browser/ui/webui/accessibility_ui.cc
patch: @@ -265,7 +265,8 @@ std::string RecursiveDumpAXPlatformNodeAsString(
     return "";
   }
   std::string str(2 * indent, '+');
-  std::string line = node->GetDelegate()->GetData().ToString();
+  ui::AXPlatformNodeDelegate* const node_delegate = node->GetDelegate();
+  std::string line = node_delegate->GetData().ToString();
   std::vector<std::string> attributes = base::SplitString(
       line, " ", base::KEEP_WHITESPACE, base::SPLIT_WANT_NONEMPTY);
   for (const std::string& attribute : attributes) {
@@ -275,8 +276,9 @@ std::string RecursiveDumpAXPlatformNodeAsString(
     }
   }
   str += "\n";
-  for (size_t i = 0; i < node->GetDelegate()->GetChildCount(); i++) {
-    gfx::NativeViewAccessible child = node->GetDelegate()->ChildAtIndex(i);
+  for (size_t i = 0, child_count = node_delegate->GetChildCount();
+       i < child_count; i++) {
+    gfx::NativeViewAccessible child = node_delegate->ChildAtIndex(i);
     ui::AXPlatformNode* child_node =
         ui::AXPlatformNode::FromNativeViewAccessible(child);
     str += RecursiveDumpAXPlatformNodeAsString(child_node, indent + 1,