helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: kv-cache : fix M-RoPE checkpoints

fix #20002
cont https://github.com/ggml-org/llama.cpp/pull/16825#issuecomment-3460868350

Extend the KV cache save/load to handle the `llama_kv_cell_ext` data.

Changed files:
filename: src/llama-batch.cpp
patch: @@ -394,11 +394,13 @@ llama_ubatch llama_batch_allocr::ubatch_reserve(uint32_t n_seq_tokens, uint32_t
     clear();
     split_reset();
 
+    const int64_t n_pos_all = (int64_t) n_tokens*n_pos_per_embd;
+
     auto udata = std::make_shared<llama_ubatch::data_t>();
 
     udata->token     .resize(n_tokens);
     udata->embd      .clear();
-    udata->pos       .resize(n_tokens);
+    udata->pos       .resize(n_pos_all);
     udata->n_seq_id  .resize(n_tokens);
     udata->seq_id    .resize(n_tokens);
     udata->seq_id_unq.resize(0);

filename: src/llama-kv-cache.cpp
patch: @@ -1760,8 +1760,10 @@ void llama_kv_cache::state_write_meta(llama_io_write_i & io, const cell_ranges_t
             io.write(&pos,      sizeof(pos));
             io.write(&n_seq_id, sizeof(n_seq_id));
 
-            // TODO: we also need to save llama_kv_cell_ext when apply_ubatch() support loading it
-            //       see: https://github.com/ggml-org/llama.cpp/pull/16825#issuecomment-3460868350
+            if (hparams.n_pos_per_embd() > 1) {
+                const llama_kv_cell_ext ext = cells.ext_get(i);
+                io.write(&ext, sizeof(ext));
+            }
 
             for (const auto & seq_id : seq_ids) {
                 io.write(&seq_id, sizeof(seq_id));
@@ -1895,6 +1897,14 @@ bool llama_kv_cache::state_read_meta(llama_io_read_i & io, uint32_t strm, uint32
                 return false;
             }
 
+            if (hparams.n_pos_per_embd() > 1) {
+                llama_kv_cell_ext ext;
+                io.read_to(&ext, sizeof(ext));
+
+                ubatch.pos[i + ubatch.n_tokens]   = ext.y;
+                ubatch.pos[i + ubatch.n_tokens*2] = ext.x;
+            }
+
             // read the sequence id, but directly discard it - we will use dest_seq_id instead
             {
                 llama_seq_id seq_id;
Repository: facebook/react
Pull request: [eslint-plugin-react-hooks] move eslint plugin once again


Changed files:
filename: .github/workflows/runtime_commit_artifacts.yml
patch: @@ -170,7 +170,8 @@ jobs:
           # Copy eslint-plugin-react-hooks
           # NOTE: This is different from www, here we include the full package
           #       including package.json to include dependencies in fbsource.
-          cp -r build/oss-experimental/eslint-plugin-react-hooks $BASE_FOLDER/RKJSModules/vendor/react
+          mkdir "$BASE_FOLDER/tools"
+          cp -r build/oss-experimental/eslint-plugin-react-hooks "$BASE_FOLDER/tools"
 
           # Move React Native version file
           mv build/facebook-react-native/VERSION_NATIVE_FB ./compiled-rn/VERSION_NATIVE_FB
Repository: vercel/next.js
Pull request: ci: Fix retry comments in workflow files

The retry comments for e2e tests and deploy tests were off by one.

Changed files:
filename: .github/workflows/retry_deploy_test.yml
patch: @@ -15,7 +15,7 @@ permissions:
 jobs:
   retry-on-failure:
     name: retry failed jobs
-    # Retry the test-e2e-deploy-release workflow up to 2 times
+    # Retry the test-e2e-deploy-release workflow once
     if: >-
       ${{
         startsWith(github.event.workflow_run.display_title, 'test-e2e-deploy') &&

filename: .github/workflows/retry_test.yml
patch: @@ -18,7 +18,7 @@ permissions:
 jobs:
   retry-on-failure:
     name: retry failed jobs
-    # Retry the build-and-test workflow up to 3 times
+    # Retry the build-and-test workflow up to 2 times
     if: >-
       ${{ 
         github.event.workflow_run.conclusion == 'failure' &&
Repository: electron/electron
Pull request: build: fixup release notes generation

#### Description of Change
- Follow up to #49194.  That PR accidentally broke release notes generation and we did not catch that because we don't generate release notes for nightlies.

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd
- [ ] `npm test` passes
- [x] [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: <!-- 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: script/release/notes/notes.ts
patch: @@ -109,7 +109,8 @@ const runGit = async (dir: string, args: string[]) => {
   const response = spawnSync('git', args, {
     cwd: dir,
     encoding: 'utf8',
-    stdio: ['inherit', 'pipe', 'pipe']
+    stdio: ['inherit', 'pipe', 'pipe'],
+    maxBuffer: 100 * 1024 * 1024 // 100MB buffer to handle large git outputs
   });
   if (response.status !== 0) {
     console.error(`Git command failed: git ${args.join(' ')}`);
Repository: ollama/ollama
Pull request: Avoid sharing a buffer when multiple inputs are sent to generate embeddings via api/embed.

This sharing happens due to a race condition between the processing of each of the inputs.

Addtional details were added in the linked issue.

Fixes #8713 

Changed files:
filename: llama/llama.go
patch: @@ -199,21 +199,25 @@ func (c *Context) KvCacheDefrag() {
 
 // Get the embeddings for a sequence id
 func (c *Context) GetEmbeddingsSeq(seqId int) []float32 {
-	embeddings := unsafe.Pointer(C.llama_get_embeddings_seq(c.c, C.int(seqId)))
-	if embeddings == nil {
+	e := unsafe.Pointer(C.llama_get_embeddings_seq(c.c, C.int(seqId)))
+	if e == nil {
 		return nil
 	}
 
-	return unsafe.Slice((*float32)(embeddings), c.Model().NEmbd())
+	embeddings := make([]float32, c.Model().NEmbd())
+	_ = copy(embeddings, unsafe.Slice((*float32)(e), c.Model().NEmbd()))
+	return embeddings
 }
 
 func (c *Context) GetEmbeddingsIth(i int) []float32 {
-	embeddings := unsafe.Pointer(C.llama_get_embeddings_ith(c.c, C.int32_t(i)))
-	if embeddings == nil {
+	e := unsafe.Pointer(C.llama_get_embeddings_ith(c.c, C.int32_t(i)))
+	if e == nil {
 		return nil
 	}
 
-	return unsafe.Slice((*float32)(embeddings), c.Model().NEmbd())
+	embeddings := make([]float32, c.Model().NEmbd())
+	_ = copy(embeddings, unsafe.Slice((*float32)(e), c.Model().NEmbd()))
+	return embeddings
 }
 
 type ModelParams struct {
Repository: facebook/react
Pull request: [eslint-plugin-react-hooks] another CI update...

We currently created a nested directory, this should remove that.

See:
https://github.com/facebook/react/tree/builds/facebook-fbsource/compiled-rn/facebook-fbsource/xplat/js/RKJSModules/vendor/react/eslint-plugin-react-hooks/eslint-plugin-react-hooks

Changed files:
filename: .github/workflows/runtime_commit_artifacts.yml
patch: @@ -170,9 +170,7 @@ jobs:
           # Copy eslint-plugin-react-hooks
           # NOTE: This is different from www, here we include the full package
           #       including package.json to include dependencies in fbsource.
-          mkdir $BASE_FOLDER/RKJSModules/vendor/react/eslint-plugin-react-hooks
-          cp -r build/oss-experimental/eslint-plugin-react-hooks \
-            $BASE_FOLDER/RKJSModules/vendor/react/eslint-plugin-react-hooks
+          cp -r build/oss-experimental/eslint-plugin-react-hooks $BASE_FOLDER/RKJSModules/vendor/react
 
           # Move React Native version file
           mv build/facebook-react-native/VERSION_NATIVE_FB ./compiled-rn/VERSION_NATIVE_FB
Repository: vuejs/vue
Pull request: fix(types): add missing `listeners` type on RenderContext

<!--
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)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] 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 `dev` branch for v2.x (or to a previous version branch), _not_ the `master` 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
- [x] 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:**

Looks like `listeners` type is missing on the `RenderContext` of functional component render function. So I just add it.
https://vuejs.org/v2/guide/render-function.html#Functional-Components

Changed files:
filename: types/options.d.ts
patch: @@ -119,6 +119,7 @@ export interface RenderContext<Props=DefaultProps> {
   slots(): any;
   data: VNodeData;
   parent: Vue;
+  listeners: { [key: string]: Function | Function[] };
   injections: any
 }
 

filename: types/test/options-test.ts
patch: @@ -312,6 +312,7 @@ Vue.component('functional-component', {
     context.slots();
     context.data;
     context.parent;
+    context.listeners.click;
     return createElement("div", {}, context.children);
   }
 });
Repository: facebook/react
Pull request: [mcp] Fix unresolved imports


We need to explicitly import the modules so they'll be inlined correctly into the bundle.


Changed files:
filename: compiler/packages/react-mcp-server/src/tools/runtimePerf.ts
patch: @@ -1,5 +1,11 @@
 import * as babel from '@babel/core';
 import puppeteer from 'puppeteer';
+// @ts-ignore
+import * as babelPresetTypescript from '@babel/preset-typescript';
+// @ts-ignore
+import * as babelPresetEnv from '@babel/preset-env';
+// @ts-ignore
+import * as babelPresetReact from '@babel/preset-react';
 
 type PerformanceResults = {
   renderTime: number;
@@ -25,15 +31,11 @@ export async function measurePerformance(
   code: string,
   iterations: number,
 ): Promise<PerformanceResults> {
-  const babelOptions = {
+  const babelOptions: babel.TransformOptions = {
     filename: 'anonymous.tsx',
     configFile: false,
     babelrc: false,
-    presets: [
-      '@babel/preset-typescript',
-      '@babel/preset-env',
-      '@babel/preset-react',
-    ],
+    presets: [babelPresetTypescript, babelPresetEnv, babelPresetReact],
   };
 
   const parsed = await babel.parseAsync(code, babelOptions);
Repository: ollama/ollama
Pull request: Add MLflow Tracing as an observability integration in README

[MLflow Tracing](https://mlflow.org/docs/latest/llms/tracing/index.html) has an automatic integration with Ollama (see the [Ollama section in the docs](https://mlflow.org/docs/latest/llms/tracing/index.html#automatic-tracing)), which allows users to conveniently record the inputs, outputs, and other metadata of their interactions with the Ollama API.

We'd like to add a line in the README to mention this integration. Please let me know if there's anything else required, or if you'd like to change the content in any way!

Changed files:
filename: README.md
patch: @@ -545,3 +545,4 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [OpenLIT](https://github.com/openlit/openlit) is an OpenTelemetry-native tool for monitoring Ollama Applications & GPUs using traces and metrics.
 - [HoneyHive](https://docs.honeyhive.ai/integrations/ollama) is an AI observability and evaluation platform for AI agents. Use HoneyHive to evaluate agent performance, interrogate failures, and monitor quality in production.
 - [Langfuse](https://langfuse.com/docs/integrations/ollama) is an open source LLM observability platform that enables teams to collaboratively monitor, evaluate and debug AI applications.
+- [MLflow Tracing](https://mlflow.org/docs/latest/llms/tracing/index.html#automatic-tracing) is an open source LLM observability tool with a convenient API to log and visualize traces, making it easy to debug and evaluate GenAI applications.
Repository: huggingface/transformers
Pull request: Fix DocQA max_answer_len validation error message

Summary
This PR fixes a small typo in DocumentQuestionAnsweringPipeline._sanitize_parameters() where the ValueError raised for invalid max_answer_len was missing a closing parenthesis in the "(got ...)" portion of the message.

Changes
- Fix malformed ValueError message for max_answer_len validation in:
  - src/transformers/pipelines/document_question_answering.py
- Add a lightweight regression test (no model downloads) that asserts the error message is well-formed:
  - tests/pipelines/test_pipelines_document_question_answering.py

Testing
- python -m pytest tests/pipelines/test_pipelines_document_question_answering.py -k sanitize_parameters_max_answer_len_error_message -q

Changed files:
filename: src/transformers/pipelines/document_question_answering.py
patch: @@ -201,7 +201,7 @@ def _sanitize_parameters(
             postprocess_params["top_k"] = top_k
         if max_answer_len is not None:
             if max_answer_len < 1:
-                raise ValueError(f"max_answer_len parameter should be >= 1 (got {max_answer_len}")
+                raise ValueError(f"max_answer_len parameter should be >= 1 (got {max_answer_len})")
             postprocess_params["max_answer_len"] = max_answer_len
         if handle_impossible_answer is not None:
             postprocess_params["handle_impossible_answer"] = handle_impossible_answer

filename: src/transformers/pipelines/question_answering.py
patch: @@ -328,7 +328,7 @@ def _sanitize_parameters(
             postprocess_params["top_k"] = top_k
         if max_answer_len is not None:
             if max_answer_len < 1:
-                raise ValueError(f"max_answer_len parameter should be >= 1 (got {max_answer_len}")
+                raise ValueError(f"max_answer_len parameter should be >= 1 (got {max_answer_len})")
             postprocess_params["max_answer_len"] = max_answer_len
         if handle_impossible_answer is not None:
             postprocess_params["handle_impossible_answer"] = handle_impossible_answer
Repository: electron/electron
Pull request: build: fixup release notes generation

Backport of #49302

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: script/release/notes/notes.ts
patch: @@ -109,7 +109,8 @@ const runGit = async (dir: string, args: string[]) => {
   const response = spawnSync('git', args, {
     cwd: dir,
     encoding: 'utf8',
-    stdio: ['inherit', 'pipe', 'pipe']
+    stdio: ['inherit', 'pipe', 'pipe'],
+    maxBuffer: 100 * 1024 * 1024 // 100MB buffer to handle large git outputs
   });
   if (response.status !== 0) {
     console.error(`Git command failed: git ${args.join(' ')}`);
Repository: electron/electron
Pull request: ci: disallow non-maintainer changes to Yarn files

Backport of #49186

See that PR for details.


Notes: none <!-- 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 -->


Changed files:
filename: .github/workflows/non-maintainer-dependency-change.yml
patch: @@ -7,6 +7,8 @@ on:
       - 'spec/yarn.lock'
       - '.github/workflows/**'
       - '.github/actions/**'
+      - '.yarn/**'
+      - '.yarnrc.yml'
 
 permissions: {}
Repository: vuejs/vue
Pull request: fix(show): prevent transitions from starting on change truthy values

Closes #7523

<!--
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)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] 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 `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] 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:**


Changed files:
filename: src/platforms/web/runtime/directives/show.js
patch: @@ -27,7 +27,7 @@ export default {
 
   update (el: any, { value, oldValue }: VNodeDirective, vnode: VNodeWithData) {
     /* istanbul ignore if */
-    if (value === oldValue) return
+    if (!value === !oldValue) return
     vnode = locateNode(vnode)
     const transition = vnode.data && vnode.data.transition
     if (transition) {
Repository: facebook/react
Pull request: Add missing copyright header


This made the build fail since there was no file header comment.


Changed files:
filename: packages/eslint-plugin-react-hooks/npm/index.d.ts
patch: @@ -1 +1,8 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
 export * from './cjs/eslint-plugin-react-hooks';

filename: packages/eslint-plugin-react-hooks/npm/index.js
patch: @@ -1,3 +1,10 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
 'use strict';
 
 // TODO: this doesn't make sense for an ESLint rule.
Repository: ggml-org/llama.cpp
Pull request: ci : use ubuntu-latest for gguf-publish workflow

This commit changes the runner for the gguf-publish workflow from ubuntu-slim back to ubuntu-latest, which was updated in Commit 142cbe2ac68978e5dec3a2e19c1b64ef1c5740b1 ("ci : use new 1vCPU runner for lightweight jobs (#19107)").

The motivation for this is that the action used in the workflow depends on the docker daemon, which does not seem not available in the ubuntu-slim runner. This is currently causing an error in the workflow and preventing the gguf-publish workflow from running successfully. Today was the the first time since the original change (I think) that publish task has been run which may be why the issue was not noticed before.

Refs: https://github.com/ggml-org/llama.cpp/actions/runs/22481900566


Changed files:
filename: .github/workflows/gguf-publish.yml
patch: @@ -21,7 +21,7 @@ on:
 jobs:
   deploy:
 
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-latest
 
     steps:
     - uses: actions/checkout@v6
Repository: vuejs/vue
Pull request: fix(codegen): support filters with () in older browsers

Fix #7544
Make sure no extra , is added at the end of the call so it also work with older browsers

<!--
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)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] 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 `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] 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
- [x] 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:**


Changed files:
filename: src/compiler/parser/filter-parser.js
patch: @@ -92,6 +92,6 @@ function wrapFilter (exp: string, filter: string): string {
   } else {
     const name = filter.slice(0, i)
     const args = filter.slice(i + 1)
-    return `_f("${name}")(${exp},${args}`
+    return `_f("${name}")(${exp}${args !== ')' ? ',' + args : args}`
   }
 }

filename: test/unit/modules/compiler/codegen.spec.js
patch: @@ -44,6 +44,13 @@ describe('codegen', () => {
     )
   })
 
+  it('generate filters with no arguments', () => {
+    assertCodegen(
+      '<div>{{ d | e() }}</div>',
+      `with(this){return _c('div',[_v(_s(_f("e")(d)))])}`
+    )
+  })
+
   it('generate v-for directive', () => {
     assertCodegen(
       '<div><li v-for="item in items" :key="item.uid"></li></div>',
Repository: electron/electron
Pull request: ci: disallow non-maintainer changes to Yarn files

> [!IMPORTANT]
> Please note that code reviews and merges will be delayed during our [quiet period in December](https://www.electronjs.org/blog/dec-quiet-period-25) and might not happen until January.

#### Description of Change

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

Now that we have these files after the Yarn v4 migration, let's make sure they're covered by our disallowed non-maintainer changes workflow.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd

#### Release Notes

Notes: none <!-- 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 -->


Changed files:
filename: .github/workflows/non-maintainer-dependency-change.yml
patch: @@ -7,6 +7,8 @@ on:
       - 'spec/yarn.lock'
       - '.github/workflows/**'
       - '.github/actions/**'
+      - '.yarn/**'
+      - '.yarnrc.yml'
 
 permissions: {}