helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: fix arm linux build when HWCAP2_SVE2 undefined

It looks like our almalinux-8 base doesn't have this macro defined in the headers we're including.

This includes `sys/auxv.h`, which includes `bits/hwcap.h`.  On our base image, that header states:
```
/* The following must match the kernel's <asm/hwcap.h>.  */
#define HWCAP_FP                (1 << 0)
#define HWCAP_ASIMD             (1 << 1)
...
```
and does NOT include HWCAP2_SVE2, however, looking at `asm/hwcap.h` the macro is defined as
```
#define HWCAP2_SVE2             (1 << 1)
```


Confirmed with this patch our docker build works

Changed files:
filename: ml/backend/ggml/ggml/src/ggml-cpu/arch/arm/arm.go
patch: @@ -1,5 +1,5 @@
 package arm
 
 // #cgo CXXFLAGS: -std=c++17
-// #cgo CPPFLAGS: -I${SRCDIR}/../.. -I${SRCDIR}/../../.. -I${SRCDIR}/../../../../include
+// #cgo CPPFLAGS: -I${SRCDIR}/../.. -I${SRCDIR}/../../.. -I${SRCDIR}/../../../../include -DHWCAP2_SVE2="2"
 import "C"
Repository: vercel/next.js
Pull request: Turbopack: improve cell order lint rule

Addresses the comments on this PR: https://github.com/vercel/next.js/pull/88474#discussion_r2687626329

"Merge when ready" had striked again

This did actually find another violation

Changed files:
filename: .config/ast-grep/rules/no-map-async-cell.yml
patch: @@ -8,13 +8,16 @@ language: Rust
 rule:
   all:
     - any:
-        - pattern: $X.cell()
-        - pattern: $X.resolved_cell()
+        - pattern: $_X.cell()
+        - pattern: $_X.resolved_cell()
+        - pattern: ResolvedVc::cell($_X)
+        - pattern: Vc::cell($_X)
     - inside:
         stopBy: end
         all:
           - any:
               - pattern: 'async |$$$ARGS| $BODY'
+              - pattern: 'async move |$$$ARGS| $BODY'
               - pattern: '|$$$ARGS| async { $$$BODY }'
               - pattern: '|$$$ARGS| async move { $$$BODY }'
           - inside:

filename: turbopack/crates/turbopack-browser/src/ecmascript/list/content.rs
patch: @@ -116,14 +116,11 @@ impl EcmascriptDevChunkListContent {
 
         let by_merger = by_merger
             .into_iter()
-            .map(|(merger, contents)| async move {
+            .map(|(merger, contents)| (merger, Vc::cell(contents)))
+            .map(async |(merger, contents)| {
                 Ok((
                     merger.to_resolved().await?,
-                    merger
-                        .merge(Vc::cell(contents))
-                        .version()
-                        .into_trait_ref()
-                        .await?,
+                    merger.merge(contents).version().into_trait_ref().await?,
                 ))
             })
             .try_join()
Repository: nodejs/node
Pull request: tools: use ubuntu-slim runner in GHA

Those were missed in https://github.com/nodejs/node/pull/61734.
<!--
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/codeql.yml
patch: @@ -10,7 +10,7 @@ permissions:
 jobs:
   analyze:
     name: Analyze
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-slim
     permissions:
       actions: read
       contents: read

filename: .github/workflows/daily-wpt-fyi.yml
patch: @@ -21,7 +21,7 @@ permissions:
 jobs:
   collect-versions:
     if: github.repository == 'nodejs/node' || github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-slim
     outputs:
       matrix: ${{ steps.query.outputs.matrix }}
     steps:
Repository: huggingface/transformers
Pull request: Fix TypeError in dot_natural_key when state_dict keys have mixed types at same position

## What does this PR do?

Fixes #43867

When a model has sub-models with different naming conventions (e.g. `model.layers.26.self_attn.o_proj.weight` vs `desc_model.roberta.encoder.layers.7.norm1.weight`), `dot_natural_key` can produce lists where the same index contains an `int` in one key and a `str` in another. Python 3 cannot compare `int` and `str`, so `sorted()` raises:

```
TypeError: '<' not supported between instances of 'str' and 'int'
```

### Fix

Each segment is now returned as a `(type_rank, int_value, str_value)` tuple:
- Digit segments: `(0, int(p), p)` 
- String segments: `(1, 0, p)`

This ensures:
- All comparisons are between same-typed tuples (no `TypeError`)
- Natural numeric ordering is preserved within digit segments  
- Digit segments sort before string segments at the same position

### Test

```python
from transformers.core_model_loading import dot_natural_key

# Previously raised TypeError
keys = [
    'model.layers.26.self_attn.o_proj.weight',
    'desc_model.roberta.encoder.layers.7.norm1.weight',
]
sorted(keys, key=dot_natural_key)  # now works

# Natural numeric sort still works
keys = ['model.layers.10.w', 'model.layers.2.w', 'model.layers.1.w']
sorted(keys, key=dot_natural_key)
# => ['model.layers.1.w', 'model.layers.2.w', 'model.layers.10.w']
```


Changed files:
filename: src/transformers/core_model_loading.py
patch: @@ -812,12 +812,17 @@ def _job():
 
 
 def dot_natural_key(s: str):
-    parts = s.split(".")
-    for i, p in enumerate(parts):
-        # whole-segment digits -> int; otherwise leave as str
+    """Sort key for state-dict names: split on ``"."`` and sort digits numerically
+    and strings alphabetically. We emit a tuple at each point to sort ints
+    first and strings second to avoid int-string comparison failures.
+    """
+    result = []
+    for p in s.split("."):
         if p.isdigit():
-            parts[i] = int(p)
-    return parts
+            result.append((0, int(p)))
+        else:
+            result.append((1, p))
+    return result
 
 
 @contextmanager
Repository: ggml-org/llama.cpp
Pull request: [SYCL] Enhance build script to use half cores to build, avoid OS hang

After FA is supported, the number of source files become more.
When build the source code by SYCL default build script with all CPU cores on PC with small memory (like 16GB), it will lead to the memory exhausted。
Enhance build script to use half cores to build, avoid OS hang.

Changed files:
filename: examples/sycl/build.sh
patch: @@ -20,4 +20,4 @@ cmake .. -DGGML_SYCL=ON -DCMAKE_C_COMPILER=icx -DCMAKE_CXX_COMPILER=icpx -DLLAMA
 #cmake --build . --config Release --target llama-bench
 
 #build all binary
-cmake --build . --config Release -j -v
+cmake --build . --config Release -j$((($(nproc)+1)/2)) -v

filename: examples/sycl/run-llama2.sh
patch: @@ -23,9 +23,9 @@ if [ $# -gt 0 ]; then
     GGML_SYCL_DEVICE=$1
     echo "use $GGML_SYCL_DEVICE as main GPU"
     #use signle GPU only
-    ZES_ENABLE_SYSMAN=1 ./build/bin/llama-completion -m ${MODEL_FILE} -no-cnv -p "${INPUT_PROMPT}" -n 400 -e -ngl ${NGL} -s 0 -c ${CONTEXT} -mg $GGML_SYCL_DEVICE -sm none ${LOAD_MODE}
+    ZES_ENABLE_SYSMAN=1 ./build/bin/llama-completion -m ${MODEL_FILE} -no-cnv -p "${INPUT_PROMPT}" -n 200 -e -ngl ${NGL} -s 0 -c ${CONTEXT} -mg $GGML_SYCL_DEVICE -sm none ${LOAD_MODE}
 
 else
     #use multiple GPUs with same max compute units
-    ZES_ENABLE_SYSMAN=1 ./build/bin/llama-completion -m ${MODEL_FILE} -no-cnv -p "${INPUT_PROMPT}" -n 400 -e -ngl ${NGL} -s 0 -c ${CONTEXT} ${LOAD_MODE}
+    ZES_ENABLE_SYSMAN=1 ./build/bin/llama-completion -m ${MODEL_FILE} -no-cnv -p "${INPUT_PROMPT}" -n 200 -e -ngl ${NGL} -s 0 -c ${CONTEXT} ${LOAD_MODE}
 fi
Repository: ggml-org/llama.cpp
Pull request: llama: public llama_n_head


- [x] I have read the [contributing guidelines](https://github.com/ggerganov/llama.cpp/blob/master/CONTRIBUTING.md)
- Self-reported review complexity:
  - [x] Low
  - [ ] Medium
  - [ ] High

I'd like to request that `llama_n_head` method be added to the public interface.

Changed files:
filename: include/llama.h
patch: @@ -441,6 +441,7 @@ extern "C" {
     LLAMA_API int32_t llama_n_ctx_train(const struct llama_model * model);
     LLAMA_API int32_t llama_n_embd     (const struct llama_model * model);
     LLAMA_API int32_t llama_n_layer    (const struct llama_model * model);
+    LLAMA_API int32_t llama_n_head     (const struct llama_model * model);
 
     LLAMA_API const struct llama_model * llama_get_model(const struct llama_context * ctx);
 

filename: src/llama.cpp
patch: @@ -19047,6 +19047,10 @@ int32_t llama_n_layer(const struct llama_model * model) {
     return model->hparams.n_layer;
 }
 
+int32_t llama_n_head(const struct llama_model * model) {
+    return model->hparams.n_head();
+}
+
 const struct llama_model * llama_get_model(const struct llama_context * ctx) {
     return &ctx->model;
 }
Repository: ollama/ollama
Pull request: doc: clarify both rocm and main bundle necessary

Some users expect the rocm bundles to be self-sufficient, but are designed to be additive.

Fixes #11843

Changed files:
filename: docs/linux.md
patch: @@ -34,7 +34,11 @@ ollama -v
 
 ### AMD GPU install
 
-If you have an AMD GPU, also download and extract the additional ROCm package:
+If you have an AMD GPU, **also** download and extract the additional ROCm package:
+
+> [!IMPORTANT]
+> The ROCm tgz contains only AMD dependent libraries.  You must extract **both** `ollama-linux-amd64.tgz` and `ollama-linux-amd64-rocm.tgz` into the same location.
+
 
 ```shell
 curl -L https://ollama.com/download/ollama-linux-amd64-rocm.tgz -o ollama-linux-amd64-rocm.tgz

filename: docs/windows.md
patch: @@ -68,9 +68,9 @@ If you'd like to install or integrate Ollama as a service, a standalone
 `ollama-windows-amd64.zip` zip file is available containing only the Ollama CLI
 and GPU library dependencies for Nvidia.  If you have an AMD GPU, also download
 and extract the additional ROCm package `ollama-windows-amd64-rocm.zip` into the
-same directory.  This allows for embedding Ollama in existing applications, or
-running it as a system service via `ollama serve` with tools such as
-[NSSM](https://nssm.cc/). 
+same directory.  Both zip files are necessary for a complete AMD installation.
+This allows for embedding Ollama in existing applications, or running it as a
+system service via `ollama serve` with tools such as [NSSM](https://nssm.cc/). 
 
 > [!NOTE]  
 > If you are upgrading from a prior version, you should remove the old directories first.
Repository: vuejs/vue
Pull request: Update README.md (browser compatibility reference)

Updated Browser Compatibility reference. The previous currently returns HTTP 404.

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `main` branch for v2.x (or to a previous version branch)
- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [ ] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**

Updated browser compatibility reference for ES5. The previous currently returns HTTP 404.

Changed files:
filename: README.md
patch: @@ -45,7 +45,7 @@ Vue (pronounced `/vjuː/`, like view) is a **progressive framework** for buildin
 
 #### Browser Compatibility
 
-Vue.js supports all browsers that are [ES5-compliant](https://kangax.github.io/compat-table/es5/) (IE8 and below are not supported).
+Vue.js supports all browsers that are [ES5-compliant](https://compat-table.github.io/compat-table/es5/) (IE8 and below are not supported).
 
 ## Ecosystem
Repository: facebook/react
Pull request: [DevTools] Minify backend

When we disabled minification for the backend in https://github.com/facebook/react/pull/19369, we didn't have sourcemaps. As of https://github.com/facebook/react/issues/28730 we do so we can minify it again.

Minification isn't just about reducing parsed size but also about reducing runtime overhead via various compiler optimizations. We only use Terser at the moment but should use Closure in the future.

Changed files:
filename: packages/react-devtools-extensions/webpack.backend.js
patch: @@ -2,6 +2,7 @@
 
 const {resolve, isAbsolute, relative} = require('path');
 const Webpack = require('webpack');
+const TerserPlugin = require('terser-webpack-plugin');
 
 const {resolveFeatureFlags} = require('react-devtools-shared/buildUtils');
 const SourceMapIgnoreListPlugin = require('react-devtools-shared/SourceMapIgnoreListPlugin');
@@ -56,16 +57,32 @@ module.exports = {
     },
   },
   optimization: {
-    minimize: false,
+    minimize: !__DEV__,
+    minimizer: [
+      new TerserPlugin({
+        terserOptions: {
+          compress: {
+            unused: true,
+            dead_code: true,
+          },
+          mangle: {
+            keep_fnames: true,
+          },
+          format: {
+            comments: false,
+          },
+        },
+        extractComments: false,
+      }),
+    ],
   },
   plugins: [
     new Webpack.ProvidePlugin({
       process: 'process/browser',
     }),
     new Webpack.DefinePlugin({
-      __DEV__: true,
+      __DEV__,
       __PROFILE__: false,
-      __DEV____DEV__: true,
       // By importing `shared/` we may import ReactFeatureFlags
       __EXPERIMENTAL__: true,
       'process.env.DEVTOOLS_PACKAGE': `"react-devtools-extensions"`,
Repository: ollama/ollama
Pull request: test: add valid responses

some of the new models need a few more valid responses to pass

qwen in particular needed a few more.

Changed files:
filename: integration/utils_test.go
patch: @@ -574,8 +574,8 @@ func GenerateRequests() ([]api.GenerateRequest, [][]string) {
 			},
 		},
 		[][]string{
-			{"sunlight"},
-			{"soil", "organic", "earth", "black", "tan"},
+			{"sunlight", "scattering", "interact"},
+			{"soil", "organic", "earth", "black", "tan", "chemical", "processes", "pigments", "particles"},
 			{"england", "english", "massachusetts", "pilgrims", "british"},
 			{"fourth", "july", "declaration", "independence"},
 			{"nitrogen", "oxygen", "carbon", "dioxide"},
Repository: facebook/react
Pull request: [DevTools] Only check if we previously removed IO if its removal failed

Resolves https://github.com/facebook/react/pull/34495#discussion_r2352839101


Changed files:
filename: packages/react-devtools-shared/src/backend/fiber/renderer.js
patch: @@ -2902,29 +2902,32 @@ export function attach(
           // Let's remove it from the parent SuspenseNode.
           const ioInfo = asyncInfo.awaited;
           const suspendedBySet = parentSuspenseNode.suspendedBy.get(ioInfo);
-          // A boundary can await the same IO multiple times.
-          // We still want to error if we're trying to remove IO that isn't present on
-          // this boundary so we need to check if we've already removed it.
-          // We're assuming previousSuspendedBy is a small array so this should be faster
-          // than allocating and maintaining a Set.
-          let alreadyRemovedIO = false;
-          for (let j = 0; j < i; j++) {
-            const removedIOInfo = previousSuspendedBy[j].awaited;
-            if (removedIOInfo === ioInfo) {
-              alreadyRemovedIO = true;
-              break;
-            }
-          }
+
           if (
             suspendedBySet === undefined ||
-            (!alreadyRemovedIO && !suspendedBySet.delete(instance))
+            !suspendedBySet.delete(instance)
           ) {
-            throw new Error(
-              'We are cleaning up async info that was not on the parent Suspense boundary. ' +
-                'This is a bug in React.',
-            );
+            // A boundary can await the same IO multiple times.
+            // We still want to error if we're trying to remove IO that isn't present on
+            // this boundary so we need to check if we've already removed it.
+            // We're assuming previousSuspendedBy is a small array so this should be faster
+            // than allocating and maintaining a Set.
+            let alreadyRemovedIO = false;
+            for (let j = 0; j < i; j++) {
+              const removedIOInfo = previousSuspendedBy[j].awaited;
+              if (removedIOInfo === ioInfo) {
+                alreadyRemovedIO = true;
+                break;
+              }
+            }
+            if (!alreadyRemovedIO) {
+              throw new Error(
+                'We are cleaning up async info that was not on the parent Suspense boundary. ' +
+                  'This is a bug in React.',
+              );
+            }
           }
-          if (suspendedBySet.size === 0) {
+          if (suspendedBySet !== undefined && suspendedBySet.size === 0) {
             parentSuspenseNode.suspendedBy.delete(asyncInfo.awaited);
           }
           if (
Repository: facebook/react
Pull request: [DevTools] Don't keep stale root instances we never mounted around

Stacked on https://github.com/facebook/react/pull/34495
Follow-up to https://github.com/facebook/react/pull/34467

We can't reference a Fiber instance that we never fully mounted since we use these Fiber root instances to get the previous Fiber to reconcile against.

Fixes "There should always be an Offscreen Fiber child in a hydrated Suspense boundary." due to  attempting to unmount a Fiber that we didn't actually mount and "There should always be a SuspenseNode parent on a mounted instance." because we attempted to update a Fiber instance that never actually went through `mountFiberRecursively` because it didn't have any child when we first encountered it.

Changed files:
filename: packages/react-devtools-shared/src/backend/fiber/renderer.js
patch: @@ -1516,7 +1516,7 @@ export function attach(
       currentRoot = rootInstance;
       unmountInstanceRecursively(rootInstance);
       rootToFiberInstanceMap.delete(root);
-      flushPendingEvents(root);
+      flushPendingEvents();
       currentRoot = (null: any);
     });
 
@@ -1541,7 +1541,7 @@ export function attach(
       currentRoot = newRoot;
       setRootPseudoKey(currentRoot.id, root.current);
       mountFiberRecursively(root.current, false);
-      flushPendingEvents(root);
+      flushPendingEvents();
       currentRoot = (null: any);
     });
 
@@ -2099,7 +2099,7 @@ export function attach(
     }
   }
 
-  function flushPendingEvents(root: Object): void {
+  function flushPendingEvents(): void {
     if (shouldBailoutWithPendingOperations()) {
       // If we aren't profiling, we can just bail out here.
       // No use sending an empty update over the bridge.
@@ -5349,7 +5349,7 @@ export function attach(
 
         mountFiberRecursively(root.current, false);
 
-        flushPendingEvents(root);
+        flushPendingEvents();
 
         needsToFlushComponentLogs = false;
         currentRoot = (null: any);
@@ -5452,6 +5452,9 @@ export function attach(
       unmountInstanceRecursively(rootInstance);
       removeRootPseudoKey(currentRoot.id);
       rootToFiberInstanceMap.delete(root);
+    } else if (!prevWasMounted && !nextIsMounted) {
+      // We don't need this root anymore.
+      rootToFiberInstanceMap.delete(root);
     }
 
     if (isProfiling && isProfilingSupported) {
@@ -5475,7 +5478,7 @@ export function attach(
     }
 
     // We're done here.
-    flushPendingEvents(root);
+    flushPendingEvents();
 
     needsToFlushComponentLogs = false;
Repository: ggml-org/llama.cpp
Pull request: feat: remove a sampler from a chain

This PR makes it possible to remove a sampler from a chain.
This is useful for removing a sampler from before freeing the chain, to keep an existing state of a specific sampler.

- [x] I have read the [contributing guidelines](https://github.com/ggerganov/llama.cpp/blob/master/CONTRIBUTING.md)
- Self-reported review complexity:
  - [x] Low
  - [ ] Medium
  - [ ] High


Changed files:
filename: include/llama.h
patch: @@ -1056,6 +1056,9 @@ extern "C" {
     LLAMA_API struct llama_sampler * llama_sampler_chain_get(const struct llama_sampler * chain, int32_t i);
     LLAMA_API int                    llama_sampler_chain_n  (const struct llama_sampler * chain);
 
+    // after removing a sampler, the chain will no longer own it, and it will not be freed when the chain is freed
+    LLAMA_API struct llama_sampler * llama_sampler_chain_remove(   struct llama_sampler * chain, int32_t i);
+
     // available samplers:
 
     LLAMA_API struct llama_sampler * llama_sampler_init_greedy     (void);

filename: src/llama-sampling.cpp
patch: @@ -349,13 +349,26 @@ void llama_sampler_chain_add(struct llama_sampler * chain, struct llama_sampler
 struct llama_sampler * llama_sampler_chain_get(const struct llama_sampler * chain, int32_t i) {
     const auto * p = (const llama_sampler_chain *) chain->ctx;
 
-    if (i < 0 || i >= (int32_t) p->samplers.size()) {
+    if (i < 0 || (size_t) i >= p->samplers.size()) {
         return nullptr;
     }
 
     return p->samplers[i];
 }
 
+struct llama_sampler * llama_sampler_chain_remove(struct llama_sampler * chain, int32_t i) {
+    auto * p = (llama_sampler_chain *) chain->ctx;
+
+    if (i < 0 || (size_t) i >= p->samplers.size()) {
+        return nullptr;
+    }
+
+    auto * result = p->samplers[i];
+    p->samplers.erase(p->samplers.begin() + i);
+
+    return result;
+}
+
 int llama_sampler_chain_n(const struct llama_sampler * chain) {
     const auto * p = (const llama_sampler_chain *) chain->ctx;