helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: doc: add known issue to v24.11.0 release notes

Refs: https://github.com/nodejs/node/pull/60414#issuecomment-3457808776
Refs: https://github.com/nodejs/nodejs.org/pull/8280

<!--
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: doc/changelogs/CHANGELOG_V24.md
patch: @@ -70,6 +70,15 @@ the end of April 2028.
 Other than updating metadata, such as the `process.release` object, to reflect
 that the release is LTS, no further changes from Node.js 24.10.0 are included.
 
+### Known issue
+
+An issue has been identified in the Node.js 24.x line with `Buffer.allocUnsafe`
+unintentionally returning zero-filled buffers. This API is
+[documented to return uninitialized memory](https://nodejs.org/docs/latest-v24.x/api/buffer.html#static-method-bufferallocunsafesize).
+The documented behavior will be restored in the next Node.js 24.x LTS release to bring
+it back in line with previous releases. For more information, see
+[#60423](https://github.com/nodejs/node/issues/60423).
+
 <a id="24.10.0"></a>
 
 ## 2025-10-08, Version 24.10.0 (Current), @RafaelGSS
Repository: vercel/next.js
Pull request: fix: move conductor.json to repo root for proper detection

## What?

Moves `conductor.json` from `.conductor/conductor.json` to the repository root and updates script paths accordingly.

## Why?

Conductor searches for configuration files in a specific priority order:
1. Workspace root
2. Remote default branch
3. Repository root

The previous location at `.conductor/conductor.json` wasn't in the standard search path, which could cause Conductor to not detect the configuration properly. Moving to the repo root follows the [recommended pattern from Conductor's documentation](https://docs.conductor.build/core/conductor-json).

## How?

- Moved `conductor.json` to repository root
- Updated script paths from `./scripts/` to `./.conductor/scripts/`
- Scripts remain in `.conductor/scripts/` for organization

Changed files:
filename: conductor.json
patch: @@ -2,8 +2,8 @@
   "name": "next.js",
   "description": "Next.js framework development workspace",
   "scripts": {
-    "setup": "./scripts/setup.sh",
-    "run": "./scripts/run.sh"
+    "setup": "./.conductor/scripts/setup.sh",
+    "run": "./.conductor/scripts/run.sh"
   },
   "worktree": {
     "default_branch": "canary"
Repository: ollama/ollama
Pull request: ci: fix linux version

Pass through the version override so the makefiles use it

rc3 linux binaries are reporting a version string of `0.5.2-rc3-0-g581a4a5-dirty`

Changed files:
filename: Dockerfile
patch: @@ -66,6 +66,7 @@ COPY . .
 ARG OLLAMA_SKIP_CUDA_GENERATE
 ARG OLLAMA_SKIP_ROCM_GENERATE
 ARG OLLAMA_FAST_BUILD
+ARG VERSION
 RUN --mount=type=cache,target=/root/.ccache \
     if grep "^flags" /proc/cpuinfo|grep avx>/dev/null; then \
         make -j $(expr $(nproc) / 2 ) dist ; \
@@ -91,6 +92,7 @@ WORKDIR /go/src/github.com/ollama/ollama/
 COPY . .
 ARG CGO_CFLAGS
 ENV GOARCH arm64
+ARG VERSION
 RUN --mount=type=cache,target=/root/.ccache \
     make -j 5 dist_cuda_v11 \
         CUDA_ARCHITECTURES="72;87" \
@@ -109,6 +111,7 @@ WORKDIR /go/src/github.com/ollama/ollama/
 COPY . .
 ARG CGO_CFLAGS
 ENV GOARCH arm64
+ARG VERSION
 RUN --mount=type=cache,target=/root/.ccache \
     make -j 5 dist_cuda_v12 \
         CUDA_ARCHITECTURES="87" \
@@ -120,6 +123,7 @@ FROM --platform=linux/arm64 unified-builder-arm64 AS build-arm64
 COPY . .
 ARG OLLAMA_SKIP_CUDA_GENERATE
 ARG OLLAMA_FAST_BUILD
+ARG VERSION
 RUN --mount=type=cache,target=/root/.ccache \
     make -j 5 dist
 COPY --from=runners-jetpack5-arm64 /go/src/github.com/ollama/ollama/dist/ dist/
Repository: vuejs/vue
Pull request: fix #6931: Clean up target variables to avoid memory leaks

<!--
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:**
The development environment on Windows is flaky and crashes a lot. I'm also seeing intermittent failures that seem unrelated to my change (they also occur on the `dev` branch with no changes). Filing the PR now to get feedback and to see if CI has the same failures.

Changed files:
filename: src/core/instance/events.js
patch: @@ -19,7 +19,7 @@ export function initEvents (vm: Component) {
   }
 }
 
-let target: Component
+let target: any
 
 function add (event, fn, once) {
   if (once) {
@@ -40,6 +40,7 @@ export function updateComponentListeners (
 ) {
   target = vm
   updateListeners(listeners, oldListeners || {}, add, remove, vm)
+  target = undefined
 }
 
 export function eventsMixin (Vue: Class<Component>) {

filename: src/platforms/web/runtime/modules/events.js
patch: @@ -26,7 +26,7 @@ function normalizeEvents (on) {
   }
 }
 
-let target: HTMLElement
+let target: any
 
 function createOnceHandler (handler, event, capture) {
   const _target = target // save current target element in closure
@@ -78,6 +78,7 @@ function updateDOMListeners (oldVnode: VNodeWithData, vnode: VNodeWithData) {
   target = vnode.elm
   normalizeEvents(on)
   updateListeners(on, oldOn, add, remove, vnode.context)
+  target = undefined
 }
 
 export default {

filename: src/platforms/weex/runtime/modules/events.js
patch: @@ -46,6 +46,7 @@ function updateDOMListeners (oldVnode: VNodeWithData, vnode: VNodeWithData) {
   const oldOn = oldVnode.data.on || {}
   target = vnode.elm
   updateListeners(on, oldOn, add, remove, vnode.context)
+  target = undefined
 }
 
 export default {
Repository: ggml-org/llama.cpp
Pull request: fix(server): respect `load-on-startup` option in router mode

### Problem
When running `llama-server` in router mode with a custom model preset (`.ini` file), the `load-on-startup` option was being ignored. The server attempted to load **all** defined models at startup, regardless of whether `load-on-startup = false` was set for specific models.

This caused the server to fail initialization if the total number of models exceeded the `--models-max` limit, even if the user intended to load only a subset (or zero) of models initially.

**Example Error:**
```text
main: failed to initialize router models: number of models to load on startup (5) exceeds models_max (1)
```

In this scenario, the user set `load-on-startup = false` for 5 models, expecting none to load on startup, but the server counted them as 5 models to load.

### Solution
Modified `tools/server/server-models.cpp` to explicitly check the value of the `load-on-startup` option using `common_arg_utils::is_truthy(val)` before adding a model to the startup list.

Previously, the code simply pushed the model name if the option key existed:
```cpp
// Before
if (inst.meta.preset.get_option(COMMON_ARG_PRESET_LOAD_ON_STARTUP, val)) {
    models_to_load.push_back(name);
}
```

Now it validates the boolean value:
```cpp
// After
if (inst.meta.preset.get_option(COMMON_ARG_PRESET_LOAD_ON_STARTUP, val)) {
    if (common_arg_utils::is_truthy(val)) {
        models_to_load.push_back(name);
    }
}
```

### Testing
1. Created a test `.ini` file with multiple models, setting `load-on-startup = false` for all of them.
2. Launched the server with `--models-max 1`.
3. **Result:** The server starts successfully without attempting to load any models, ignoring the `models_max` limit for non-startup models.
4. Verified that models with `load-on-startup = true` are still correctly loaded.

### Related
This fix ensures that the `load-on-startup` parameter works as documented in the preset configuration, preventing initialization crashes for users managing large model pools with strict VRAM limits.

Changed files:
filename: tools/server/server-models.cpp
patch: @@ -291,7 +291,9 @@ void server_models::load_models() {
     for (const auto & [name, inst] : mapping) {
         std::string val;
         if (inst.meta.preset.get_option(COMMON_ARG_PRESET_LOAD_ON_STARTUP, val)) {
-            models_to_load.push_back(name);
+            if (common_arg_utils::is_truthy(val)) {
+                models_to_load.push_back(name);
+            }
         }
     }
     if ((int)models_to_load.size() > base_params.models_max) {
Repository: electron/electron
Pull request: fix: `systemPreferences.getAccentColor` inverted color

#### Description of Change

Closes https://github.com/electron/electron/issues/48506.

Fixes an issue where `systemPreferences.getAccentColor` inverted the color.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [x] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [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: Fixed an issue where `systemPreferences.getAccentColor` inverted the color.


Changed files:
filename: shell/browser/api/electron_api_system_preferences_win.cc
patch: @@ -16,6 +16,7 @@
 #include "base/win/wrapped_window_proc.h"
 #include "shell/common/color_util.h"
 #include "shell/common/process_util.h"
+#include "skia/ext/skia_utils_win.h"
 #include "ui/gfx/win/hwnd_util.h"
 #include "ui/gfx/win/singleton_hwnd.h"
 
@@ -88,7 +89,7 @@ std::string SystemPreferences::GetAccentColor() {
   if (!color.has_value())
     return "";
 
-  return hexColorDWORDToRGBA(color.value());
+  return ToRGBAHex(skia::COLORREFToSkColor(color.value()), false);
 }
 
 std::string SystemPreferences::GetColor(gin_helper::ErrorThrower thrower,

filename: spec/api-browser-window-spec.ts
patch: @@ -1,4 +1,4 @@
-import { app, BrowserWindow, BrowserView, dialog, ipcMain, OnBeforeSendHeadersListenerDetails, net, protocol, screen, webContents, webFrameMain, session, WebContents, WebFrameMain } from 'electron/main';
+import { app, BrowserWindow, BrowserView, dialog, ipcMain, OnBeforeSendHeadersListenerDetails, net, protocol, screen, webContents, webFrameMain, session, systemPreferences, WebContents, WebFrameMain } from 'electron/main';
 
 import { expect } from 'chai';
 
@@ -2590,6 +2590,14 @@ describe('BrowserWindow module', () => {
       expect(accentColor).to.match(/^#[0-9A-F]{6}$/i);
     });
 
+    it('matches the systemPreferences system color when true', () => {
+      const w = new BrowserWindow({ show: false });
+      w.setAccentColor(true);
+      const accentColor = w.getAccentColor() as string;
+      const systemColor = systemPreferences.getAccentColor().slice(0, 6);
+      expect(accentColor).to.equal(`#${systemColor}`);
+    });
+
     it('returns the correct accent color after multiple changes', () => {
       const w = new BrowserWindow({ show: false });
Repository: huggingface/transformers
Pull request: Rewrite for loop in get_image_features with torch ops for export

# What does this PR do?

Make Ministral 3, Llava, etc. torch exportable by rewriting for loop with torch ops.

## Who can review?

@molbap @yonigozlan @zucchini-nlp 

Changed files:
filename: src/transformers/models/llava/modeling_llava.py
patch: @@ -202,10 +202,11 @@ def get_image_features(
         image_features = self.multi_modal_projector(selected_image_feature)
 
         if "image_sizes" in kwargs:
-            split_sizes = [
-                (height // self.vision_tower.patch_size) * (width // self.vision_tower.patch_size)
-                for height, width in kwargs["image_sizes"]
-            ]
+            split_sizes = (
+                (torch.as_tensor(kwargs["image_sizes"], device=image_features.device) // self.vision_tower.patch_size)
+                .prod(dim=-1)
+                .tolist()
+            )
             image_features = torch.split(image_features.squeeze(0), split_sizes)
         else:
             image_features = list(image_features)

filename: src/transformers/models/mistral3/modeling_mistral3.py
patch: @@ -252,7 +252,9 @@ def get_image_features(
 
         image_features = self.multi_modal_projector(selected_image_feature.squeeze(0), image_sizes)
         downsample_ratio = self.vision_tower.patch_size * self.config.spatial_merge_size
-        split_sizes = [(height // downsample_ratio) * (width // downsample_ratio) for height, width in image_sizes]
+        split_sizes = (
+            (torch.as_tensor(image_sizes, device=image_features.device) // downsample_ratio).prod(dim=-1).tolist()
+        )
         image_features = torch.split(image_features.squeeze(0), split_sizes)
         return image_features
 

filename: src/transformers/models/mistral3/modular_mistral3.py
patch: @@ -157,7 +157,9 @@ def get_image_features(
 
         image_features = self.multi_modal_projector(selected_image_feature.squeeze(0), image_sizes)
         downsample_ratio = self.vision_tower.patch_size * self.config.spatial_merge_size
-        split_sizes = [(height // downsample_ratio) * (width // downsample_ratio) for height, width in image_sizes]
+        split_sizes = (
+            (torch.as_tensor(image_sizes, device=image_features.device) // downsample_ratio).prod(dim=-1).tolist()
+        )
         image_features = torch.split(image_features.squeeze(0), split_sizes)
         return image_features
Repository: ollama/ollama
Pull request: ci: fix artifact path prefix for missing windows payloads

upload-artifacts strips off leading common paths so when the ./build/ artifacts were removed, the ./dist/windows-amd64 prefix became common and was stripped, making the
later download-artifacts place them in the wrong location

Example intermediate artifact from before the build changes:
```
% unzip generate-windows-cuda-11.3.zip
Archive:  generate-windows-cuda-11.3.zip
  inflating: build/darwin/amd64/placeholder
  inflating: build/darwin/arm64/placeholder
  inflating: build/embed_darwin_amd64.go
  inflating: build/embed_darwin_arm64.go
  inflating: build/embed_linux.go
  inflating: build/embed_unused.go
  inflating: build/linux/amd64/placeholder
  inflating: build/linux/arm64/placeholder
  inflating: dist/windows-amd64/lib/ollama/cublas64_11.dll
  inflating: dist/windows-amd64/lib/ollama/cudart32_110.dll
  inflating: dist/windows-amd64/lib/ollama/cublasLt64_11.dll
  inflating: dist/windows-amd64/lib/ollama/cudart64_110.dll
  inflating: dist/windows-amd64/lib/ollama/ggml_cuda_v11.dll
  inflating: dist/windows-amd64/lib/ollama/runners/cuda_v11/ollama_llama_server.exe
```

Example artifact now:
```
% unzip generate-windows-cuda-11.3.zip
Archive:  generate-windows-cuda-11.3.zip
  inflating: lib/ollama/cublas64_11.dll
  inflating: lib/ollama/cublasLt64_11.dll
  inflating: lib/ollama/cudart64_110.dll
  inflating: lib/ollama/cudart32_110.dll
  inflating: lib/ollama/runners/cuda_v11_avx/ggml_cuda_v11.dll
  inflating: lib/ollama/runners/cuda_v11_avx/ollama_llama_server.exe
```

Changed files:
filename: .github/workflows/release.yaml
patch: @@ -447,15 +447,19 @@ jobs:
       - uses: actions/download-artifact@v4
         with:
           name: generate-windows-cpu
+          path: dist/windows-amd64/
       - uses: actions/download-artifact@v4
         with:
           name: generate-windows-cuda-11.3
+          path: dist/windows-amd64/
       - uses: actions/download-artifact@v4
         with:
           name: generate-windows-cuda-12.4
+          path: dist/windows-amd64/
       - uses: actions/download-artifact@v4
         with:
           name: generate-windows-rocm
+          path: dist/windows-amd64/
       - uses: actions/download-artifact@v4
         with:
           name: windows-arm64
Repository: vuejs/vue
Pull request: tweak: The value of this is always undefined

<!--
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
- [x] 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: src/core/util/options.js
patch: @@ -89,7 +89,7 @@ export function mergeDataOrFn (
         typeof parentVal === 'function' ? parentVal.call(this) : parentVal
       )
     }
-  } else if (parentVal || childVal) {
+  } else {
     return function mergedInstanceDataFn () {
       // instance merge
       const instanceData = typeof childVal === 'function'
@@ -123,7 +123,7 @@ strats.data = function (
 
       return parentVal
     }
-    return mergeDataOrFn.call(this, parentVal, childVal)
+    return mergeDataOrFn(parentVal, childVal)
   }
 
   return mergeDataOrFn(parentVal, childVal, vm)
Repository: facebook/react
Pull request: [ci] Only label on PR open


No reason to label it every update, only do it once when it's first opened.
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32936).
* __->__ #32936
* #32935

Changed files:
filename: .github/workflows/shared_label_core_team_prs.yml
patch: @@ -2,6 +2,7 @@ name: (Shared) Label Core Team PRs
 
 on:
   pull_request_target:
+    types: [opened]
 
 permissions: {}
Repository: electron/electron
Pull request: fix: `systemPreferences.getAccentColor` inverted color

Backport of #48511.

See that PR for details.

Notes: Fixed an issue where `systemPreferences.getAccentColor` inverted the color.

Changed files:
filename: shell/browser/api/electron_api_system_preferences_win.cc
patch: @@ -16,6 +16,7 @@
 #include "base/win/wrapped_window_proc.h"
 #include "shell/common/color_util.h"
 #include "shell/common/process_util.h"
+#include "skia/ext/skia_utils_win.h"
 #include "ui/gfx/color_utils.h"
 #include "ui/gfx/win/hwnd_util.h"
 
@@ -88,7 +89,7 @@ std::string SystemPreferences::GetAccentColor() {
   if (!color.has_value())
     return "";
 
-  return hexColorDWORDToRGBA(color.value());
+  return ToRGBAHex(skia::COLORREFToSkColor(color.value()), false);
 }
 
 std::string SystemPreferences::GetColor(gin_helper::ErrorThrower thrower,

filename: spec/api-browser-window-spec.ts
patch: @@ -1,4 +1,4 @@
-import { app, BrowserWindow, BrowserView, dialog, ipcMain, OnBeforeSendHeadersListenerDetails, net, protocol, screen, webContents, webFrameMain, session, WebContents, WebFrameMain } from 'electron/main';
+import { app, BrowserWindow, BrowserView, dialog, ipcMain, OnBeforeSendHeadersListenerDetails, net, protocol, screen, webContents, webFrameMain, session, systemPreferences, WebContents, WebFrameMain } from 'electron/main';
 
 import { expect } from 'chai';
 
@@ -2606,6 +2606,14 @@ describe('BrowserWindow module', () => {
       expect(accentColor).to.match(/^#[0-9A-F]{6}$/i);
     });
 
+    it('matches the systemPreferences system color when true', () => {
+      const w = new BrowserWindow({ show: false });
+      w.setAccentColor(true);
+      const accentColor = w.getAccentColor() as string;
+      const systemColor = systemPreferences.getAccentColor().slice(0, 6);
+      expect(accentColor).to.equal(`#${systemColor}`);
+    });
+
     it('returns the correct accent color after multiple changes', () => {
       const w = new BrowserWindow({ show: false });
Repository: ollama/ollama
Pull request: win: builtin arm runner

The new build embeds the arm runner in the
main binary, so there is no longer a lib/ollama

Changed files:
filename: app/ollama.iss
patch: @@ -97,7 +97,6 @@ Source: "..\dist\windows-amd64\lib\ollama\*"; DestDir: "{app}\lib\ollama\"; Chec
 Source: "..\dist\windows-arm64\vc_redist.arm64.exe"; DestDir: "{tmp}"; Check: IsArm64() and vc_redist_needed(); Flags: deleteafterinstall
 Source: "..\dist\windows-arm64-app.exe"; DestDir: "{app}"; DestName: "{#MyAppExeName}" ;Check: IsArm64();  Flags: ignoreversion 64bit
 Source: "..\dist\windows-arm64\ollama.exe"; DestDir: "{app}"; Check: IsArm64(); Flags: ignoreversion 64bit
-Source: "..\dist\windows-arm64\lib\ollama\*"; DestDir: "{app}\lib\ollama\"; Check: IsArm64(); Flags: ignoreversion 64bit recursesubdirs
 #endif
 
 Source: "..\dist\ollama_welcome.ps1"; DestDir: "{app}"; Flags: ignoreversion