helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: [Flight] Use the Promise of the first await even if that is cut off

We need a "value" to represent the I/O that was loaded. We don't normally actually use the Promise at the callsite that started the I/O because that's usually deep inside internals. Instead we override the value of the I/O entry with the Promise that was first awaited in user space. This means that you could potentially have different values depending on if multiple things await the same I/O. We just take one of them. (Maybe we should actually just write the first user space awaited Promise as the I/O entry? This might instead have other implications like less deduping.)

When you pass a Promise forward, we may skip the awaits that happened in earlier components because they're not part of the currently rendering component. That's mainly for the stack and time stamps though. The value is still probably conceptually the best value because it represents the I/O value as far user space is concerned.

This writes the I/O early with the first await we find in user space even if we're not going to use that particular await for the stack.

Changed files:
filename: packages/react-server/src/ReactFlightServer.js
patch: @@ -2327,6 +2327,21 @@ function visitAsyncNode(
             // then this gets I/O ignored, which is what we want because it means it was likely
             // just part of a previous component's rendering.
             match = ioNode;
+            if (
+              node.stack !== null &&
+              isAwaitInUserspace(request, node.stack)
+            ) {
+              // This await happened earlier but it was done in user space. This is the first time
+              // that user space saw the value of the I/O. We know we'll emit the I/O eventually
+              // but if we do it now we can override the promise value of the I/O entry to the
+              // one observed by this await which will be a better value than the internals of
+              // the I/O entry. If it's still alive that is.
+              const promise =
+                awaited.promise === null ? undefined : awaited.promise.deref();
+              if (promise !== undefined) {
+                serializeIONode(request, ioNode, awaited.promise);
+              }
+            }
           } else {
             if (
               node.stack === null ||

filename: packages/react-server/src/__tests__/ReactFlightAsyncDebugInfo-test.js
patch: @@ -491,7 +491,7 @@ describe('ReactFlightAsyncDebugInfo', () => {
               ],
               "start": 0,
               "value": {
-                "status": "halted",
+                "value": undefined,
               },
             },
             "env": "Server",
Repository: ggml-org/llama.cpp
Pull request: kleidiai : fix MUL_MAT support for batched (3D) inputs

The supports_op() check incorrectly rejected MUL_MAT operations with 3D inputs (ne[2] > 1), but the actual compute_forward_qx() implementation handles batched inputs correctly via a loop over ne12.

This caused models with Q4_0/Q8_0 weights to crash during graph scheduling when n_seq_max > 1, because weights were placed in KLEIDIAI buffers during loading (tested with 2D inputs) but the runtime used 3D inputs.

~Also relax the buffer check to allow supports_op() to be called during weight loading when src[0]->buffer is NULL.~

Fixes #20608

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*

update: Ah, I just read the contributing guidelines above. I used an AI while tracking this down. I reviewed and tested the changes, and then pared it down to the minimal set of changes needed for the fix, but it would be "considered AI-generated" according to the contribution guidelines.

Feel free to close this PR if needed, but the root cause for the bug and this fix for it both work and make sense to me now. 


Changed files:
filename: ggml/src/ggml-cpu/kleidiai/kleidiai.cpp
patch: @@ -1461,7 +1461,7 @@ class extra_buffer_type : ggml::cpu::extra_buffer_type {
                 return false;
             }
             if ((op->src[1]->type == GGML_TYPE_F32 || op->src[1]->type == GGML_TYPE_I32) &&
-                ggml_ne(op->src[1], 2) == 1 && ggml_ne(op->src[1], 3) == 1) {
+                ggml_ne(op->src[1], 3) == 1) {
                 return true;
             }
         }
Repository: nodejs/node
Pull request: v8: add GCProfiler support for erm

Add GCProfiler support for explicit resource management

Changed files:
filename: doc/api/v8.md
patch: @@ -1471,6 +1471,7 @@ added:
 -->
 
 Create a new instance of the `v8.GCProfiler` class.
+This API supports `using` syntax.
 
 ### `profiler.start()`
 
@@ -1490,7 +1491,7 @@ added:
   - v18.15.0
 -->
 
-Stop collecting GC data and return an object.The content of object
+Stop collecting GC data and return an object. The content of object
 is as follows.
 
 ```json
@@ -1575,6 +1576,14 @@ setTimeout(() => {
 }, 1000);
 ```
 
+### `profiler[Symbol.dispose]()`
+
+<!-- YAML
+added: REPLACEME
+-->
+
+Stop collecting GC data, and discard the profile.
+
 ## Class: `SyncCPUProfileHandle`
 
 <!-- YAML

filename: lib/v8.js
patch: @@ -488,6 +488,10 @@ class GCProfiler {
       return JSONParse(data);
     }
   }
+
+  [SymbolDispose]() {
+    this.stop();
+  }
 }
 
 module.exports = {

filename: test/parallel/test-v8-collect-gc-profile-using.js
patch: @@ -0,0 +1,26 @@
+'use strict';
+
+require('../common');
+const assert = require('assert');
+const { GCProfiler } = require('v8');
+
+{
+  const profiler = new GCProfiler();
+  profiler.start();
+
+  const result = profiler[Symbol.dispose]();
+
+  assert.strictEqual(result, undefined);
+  assert.strictEqual(profiler.stop(), undefined);
+}
+
+{
+  const profiler = new GCProfiler();
+  profiler.start();
+
+  profiler[Symbol.dispose]();
+  // Repeat invocations should not throw
+  profiler[Symbol.dispose]();
+
+  assert.strictEqual(profiler.stop(), undefined);
+}
Repository: vuejs/vue
Pull request: fix(security) upgrade lodash.template

This is for vue-server-renderer

https://github.com/lodash/lodash/pull/4336

<!--
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:**

- [ ] 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)
- [ ] 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: packages/vue-server-renderer/package.json
patch: @@ -22,7 +22,7 @@
     "chalk": "^1.1.3",
     "hash-sum": "^1.0.2",
     "he": "^1.1.0",
-    "lodash.template": "^4.4.0",
+    "lodash.template": "^4.5.0",
     "lodash.uniq": "^4.5.0",
     "resolve": "^1.2.0",
     "serialize-javascript": "^1.3.0",
Repository: ollama/ollama
Pull request: cmd: added support for escaping ~ in filepath

#10333
<img width="552" alt="Screenshot 2025-04-18 at 11 36 55 PM" src="https://github.com/user-attachments/assets/1e42e43a-b805-4ce1-8be8-35d4674c08f9" />


Changed files:
filename: cmd/interactive.go
patch: @@ -503,6 +503,7 @@ func normalizeFilePath(fp string) string {
 		"\\\\", "\\", // Escaped backslash
 		"\\*", "*", // Escaped asterisk
 		"\\?", "?", // Escaped question mark
+		"\\~", "~", // Escaped tilde
 	).Replace(fp)
 }
Repository: vuejs/vue
Pull request: [automated] Patreon sponsors update

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -208,6 +208,13 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
         </a>
       </td>
     </tr><tr></tr>
+    <tr>
+      <td align="center" valign="middle">
+        <a href="https://www.dailynow.co/" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/daily.png">
+        </a>
+      </td>
+    </tr><tr></tr>
   </tbody>
 </table>
 <!--gold end-->

filename: README.md
patch: @@ -213,6 +213,13 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
         </a>
       </td>
     </tr><tr></tr>
+    <tr>
+      <td align="center" valign="middle">
+        <a href="https://www.dailynow.co/" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/daily.png">
+        </a>
+      </td>
+    </tr><tr></tr>
   </tbody>
 </table>
 <!--gold end-->
Repository: vuejs/vue
Pull request: [automated] Patreon backers update (Jul 2019

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -366,10 +366,9 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Alex Balashov
 - Konstantin Levinski
 - Blaise Laflamme
-- Dilettant
 - Sean Ferguson
 - Johnny Ray Austin
-- IdealCoders
+- Daniel
 <!--50 end-->
 
 <h2 align="center">Backers via Patreon</h2>
@@ -380,105 +379,92 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
 - Samuel Smith
 - donny
 - Sean Washington
-- Keisuke Kita
-- kazupon
 - Lars Andreas Ness
-- Simon East
+- Keisuke Kita
 - Benjamin Listwon
 - Kirk Lewis
-- Victor Tolbert
-- Stephen Michael Hartley
 - Wen-Tien Chang
+- Stephen Michael Hartley
+- Victor Tolbert
 - Phan An
-- Barbara Liau
 - James J. Ye
+- Barbara Liau
 - Luiz
 - Matsumoto Takamasa
-- Shinya Katayama
-- Niannian Modisette
-- Guy Gavergun
 - Matt Jones
 - Duncan Kenzie
+- Niannian Modisette
+- Guy Gavergun
 - Bernhard E. Reiter
 - Zoran Knezevic
-- Chengzhi Yin
-- Pierre Vanhulst
 - Jon Hobbs-Smith
-- Akiho Nagao
+- Pierre Vanhulst
 - Anthony Estebe
-- Haim Yulzari
 - Asaf Yishai
-- Jim Raden
+- Haim Yulzari
+- Akiho Nagao
 - Jeremy Tan
+- Jim Raden
 - IMGNRY
-- Tai Shi Ling
-- Yong Jun Thong
 - Tyler
-- Rafael Belvederese
-- Chih-Hsuan Fan
-- Jamie McElwain
-- Vivekanandhan Natarajan
 - Daniel Waghorn
 - Guilherme S L de Souza
-- Matias Verdier
 - Rob Yedlin
+- Rafael Belvederese
+- Vivekanandhan Natarajan
 - Mickaël Andrieu
-- Cliff Hess
 - Joe Gregory
 - Jordan Oroshiba
 - Marcos Moura
-- Richard Simpson
 - Jessie Hernandez
-- Ivan Sieder
-- Aparajita Fishman
 - Eric
+- Ivan Sieder
 - Christo Crampton
 - Romain Lienard
 - Bohdan Kokotko
-- Oskar Lindgren
-- Jere Sjöroos
-- David Ang
 - Alexander Weiher
+- Jere Sjöroos
 - Donald Fischer
 - Wakana Seki
-- Domenico Gaudioso
+- Oskar Lindgren
+- David Ang
 - David Kaplan
+- Domenico Gaudioso
 - Jaeyoung Lee
 - Ben Hong
 - Andy
-- Joe Cochran
 - Matt Sencenbaugh
-- Colt Borg
+- Joe Cochran
 - Juan Bermudez
-- Hannes Kochniß
 - Alberto T. Payero Mota
-- Elon Hung
-- Daniel Mattingley
-- Teon Ooi
+- Hannes Kochniß
 - Chris Calo
+- Daniel Mattingley
+- Elon Hung
 - Soichiro Isshiki
-- Marko Boskovic
+- Shapovalov Pavel
 - Garion Herman
 - Ed Linklater
-- Rob
 - Andrew Willis
 - Yusuke Kawabata
 - Princeyesuraj Edward
-- 龙腾道
-- Shapovalov Pavel
-- Peter Matkovsky
 - 极 蔡
+- Peter Matkovsky
 - Nick Dandakis
+- 龙腾道
+- Masato Miura
 - Fabien GuySake Ungerer
 - Fedor Indutny
-- Masato Miura
+- Kenneth Crawford
 - Bill Condo
-- David McGuigan
 - Nathan Mallison
-- Kevin Batdorf
-- Sheree Peña
 - Pierre Lebrun
 - John Thompson
+- panmenghan
+- Jan-Philipp Schmeißer
+- Martin Bastien
+- Ryan Brewer
+- Bichinger Software & Consulting
 <!--10 end-->
 
 <h2 align="center">Backers via OpenCollective</h2>
Repository: ggml-org/llama.cpp
Pull request: ci : disable AMX jobs

The AMX runner in the Azure cloud stopped running for some reason.

Changed files:
filename: .github/workflows/build-self-hosted.yml
patch: @@ -97,19 +97,21 @@ jobs:
           vulkaninfo --summary
           GG_BUILD_VULKAN=1 bash ./ci/run.sh ~/results/llama.cpp /mnt/llama.cpp
 
-  ggml-ci-cpu-amx:
-    runs-on: [self-hosted, Linux, CPU, AMX]
+  # TODO: provision AMX-compatible machine
+  #ggml-ci-cpu-amx:
+  #  runs-on: [self-hosted, Linux, CPU, AMX]
 
-    steps:
-      - name: Clone
-        id: checkout
-        uses: actions/checkout@v6
+  #  steps:
+  #    - name: Clone
+  #      id: checkout
+  #      uses: actions/checkout@v6
 
-      - name: Test
-        id: ggml-ci
-        run: |
-          bash ./ci/run.sh ~/results/llama.cpp /mnt/llama.cpp
+  #    - name: Test
+  #      id: ggml-ci
+  #      run: |
+  #        bash ./ci/run.sh ~/results/llama.cpp /mnt/llama.cpp
 
+  # TODO: provision AMD GPU machine
   # ggml-ci-amd-vulkan:
   #   runs-on: [self-hosted, Linux, AMD]
 
@@ -124,6 +126,7 @@ jobs:
   #         vulkaninfo --summary
   #         GG_BUILD_VULKAN=1 bash ./ci/run.sh ~/results/llama.cpp /mnt/llama.cpp
 
+  # TODO: provision AMD GPU machine
   # ggml-ci-amd-rocm:
   #   runs-on: [self-hosted, Linux, AMD]
Repository: ollama/ollama
Pull request: create tempdir in models directory

the models directory should have plenty of storage and also ensure there's no cross-device copy

Changed files:
filename: server/create.go
patch: @@ -225,7 +225,7 @@ func detectModelTypeFromFiles(files map[string]string) string {
 }
 
 func convertFromSafetensors(files map[string]string, baseLayers []*layerGGML, isAdapter bool, fn func(resp api.ProgressResponse)) ([]*layerGGML, error) {
-	tmpDir, err := os.MkdirTemp("", "ollama-safetensors")
+	tmpDir, err := os.MkdirTemp(envconfig.Models(), "ollama-safetensors")
 	if err != nil {
 		return nil, err
 	}
Repository: ollama/ollama
Pull request: server/internal/registry: make pull send errors with Error field

Previously, the pull handler would send an error message in the Status field, this prevented the client from using the message as a signal to stop. In the case of the "run" command, it would follow the pull with a "show" which would print a nearly identical "not found" message for unresolved models.

Fixes #10307

Changed files:
filename: server/internal/registry/server.go
patch: @@ -244,6 +244,7 @@ func (s *Local) handleDelete(_ http.ResponseWriter, r *http.Request) error {
 }
 
 type progressUpdateJSON struct {
+	Error     string      `json:"error,omitempty,omitzero"`
 	Status    string      `json:"status,omitempty,omitzero"`
 	Digest    blob.Digest `json:"digest,omitempty,omitzero"`
 	Total     int64       `json:"total,omitempty,omitzero"`
@@ -348,14 +349,15 @@ func (s *Local) handlePull(w http.ResponseWriter, r *http.Request) error {
 		case err := <-done:
 			flushProgress()
 			if err != nil {
-				var status string
 				if errors.Is(err, ollama.ErrModelNotFound) {
-					status = fmt.Sprintf("error: model %q not found", p.model())
+					return &serverError{
+						Status:  404,
+						Code:    "not_found",
+						Message: fmt.Sprintf("model %q not found", p.model()),
+					}
 				} else {
-					status = fmt.Sprintf("error: %v", err)
+					return err
 				}
-				enc.Encode(progressUpdateJSON{Status: status})
-				return nil
 			}
 
 			// Emulate old client pull progress (for now):

filename: server/internal/registry/server_test.go
patch: @@ -221,7 +221,7 @@ func TestServerPull(t *testing.T) {
 
 	got = s.send(t, "POST", "/api/pull", `{"model": "unknown"}`)
 	checkResponse(got, `
-		{"status":"error: model \"unknown\" not found"}
+		{"code":"not_found","error":"model \"unknown\" not found"}
 	`)
 
 	got = s.send(t, "DELETE", "/api/pull", `{"model": "smol"}`)
@@ -235,7 +235,7 @@ func TestServerPull(t *testing.T) {
 
 	got = s.send(t, "POST", "/api/pull", `{"model": "://"}`)
 	checkResponse(got, `
-		{"status":"error: invalid or missing name: \"\""}
+		{"code":"bad_request","error":"invalid or missing name: \"\""}
 	`)
 
 	// Non-streaming pulls
Repository: huggingface/transformers
Pull request: Update `SamHQModelIntegrationTest::test_inference_mask_generation_batched_points_batched_images` for `XPU`

…onTest::test_inference_mask_generation_batched_points_batched_images pass in xpu


 @ydshieh



Changed files:
filename: tests/models/sam_hq/test_modeling_sam_hq.py
patch: @@ -881,6 +881,7 @@ def test_inference_mask_generation_batched_points_batched_images(self):
             {
                 (None, None): [-40.2445, -37.4300, -38.1577],
                 ("cuda", 8): [-14.1195, -17.2663, -13.7805],
+                ("xpu", None): [-14.1195, -17.2663, -13.7805],
             }
         )
         EXPECTED_MASKS = torch.tensor(expectations.get_expectation()).to(torch_device)
Repository: vuejs/vue
Pull request: fix #9920: fix function expression regex

<!--
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/codegen/events.js
patch: @@ -1,6 +1,6 @@
 /* @flow */
 
-const fnExpRE = /^([\w$_]+|\([^)]*?\))\s*=>|^function\s*(?:[\w$]+)?\s*\(/
+const fnExpRE = /^([\w$_]+|\([^)]*?\))\s*=>|^function(?:\s+[\w$]+)?\s*\(/
 const fnInvokeRE = /\([^)]*?\);*$/
 const simplePathRE = /^[A-Za-z_$][\w$]*(?:\.[A-Za-z_$][\w$]*|\['[^']*?']|\["[^"]*?"]|\[\d+]|\[[A-Za-z_$][\w$]*])*$/
 

filename: test/unit/modules/compiler/codegen.spec.js
patch: @@ -345,6 +345,11 @@ describe('codegen', () => {
       `<input @input="onInput(');[\\'());');">`,
       `with(this){return _c('input',{on:{"input":function($event){onInput(');[\\'());');}}})}`
     )
+    // function name including a `function` part (#9920)
+    assertCodegen(
+      '<input @input="functionName()">',
+      `with(this){return _c('input',{on:{"input":function($event){return functionName()}}})}`
+    )
   })
 
   it('generate events with multiple statements', () => {
Repository: facebook/react
Pull request: fix: log renders from passive effects for only newly finished work

This fixes displaying incorrect component render entries on a timeline, when we are reconnecting passive effects.

### Before
<img width="2318" height="1127" alt="1" src="https://github.com/user-attachments/assets/9b6b2824-d2de-43a3-8615-2c45d67c3668" />

The cloned nodes will persist original `actualStartTime`, when these were first mounted. When we "replay", the end time will be "now" or whatever the actual start time of the sibling. Depending on when this is being recorded, the diff between end and start could be tens of seconds and doesn't represent what React was doing.

We shouldn't log these entries at all.

### After
We are only logging newly finished renders, but could potentially loose renders that never commit.


Changed files:
filename: packages/react-reconciler/src/ReactFiberCommitWork.js
patch: @@ -4155,6 +4155,7 @@ export function reconnectPassiveEffects(
   if (
     enableProfilerTimer &&
     enableComponentPerformanceTrack &&
+    includeWorkInProgressEffects &&
     (finishedWork.mode & ProfileMode) !== NoMode &&
     ((finishedWork.actualStartTime: any): number) > 0 &&
     (finishedWork.flags & PerformedWork) !== NoFlags
Repository: nodejs/node
Pull request: test: add implicit test for fs dispose handling with using

Add test for implicit fs calls with `await using` syntax

Changed files:
filename: test/parallel/test-fs-promises-file-handle-dispose.js
patch: @@ -22,5 +22,29 @@ async function explicitCall() {
   assert.throws(() => dhSync.readSync(), { code: 'ERR_DIR_CLOSED' });
 }
 
+async function implicitCall() {
+  let fh;
+  {
+    await using openHandle = await fs.open(__filename);
+    fh = openHandle;
+    fh.on('close', common.mustCall());
+  }
+  assert.strictEqual(fh.fd, -1);
+
+  let dh;
+  {
+    await using dirHandle = await fs.opendir(__dirname);
+    dh = dirHandle;
+  }
+  await assert.rejects(dh.read(), { code: 'ERR_DIR_CLOSED' });
+
+  let dhSync;
+  {
+    using dirHandleSync = opendirSync(__dirname);
+    dhSync = dirHandleSync;
+  }
+  assert.throws(() => dhSync.readSync(), { code: 'ERR_DIR_CLOSED' });
+}
+
 explicitCall().then(common.mustCall());
-// TODO(aduh95): add test for implicit calls, with `await using` syntax.
+implicitCall().then(common.mustCall());