helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: tools: show diff alongside the error in Nix linter

E.g. in https://github.com/nodejs/node/actions/runs/18593102650/job/53012480793, the GH web UI auto focuses on the error, so it'd be more useful to show the diff there to know how to fix the error.

<!--
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/linters.yml
patch: @@ -151,10 +151,10 @@ jobs:
           sparse-checkout-cone-mode: false
       - uses: cachix/install-nix-action@7be5dee1421f63d07e71ce6e0a9f8a4b07c2a487  # v31.6.1
       - name: Lint Nix files
-        run: nix-shell -I nixpkgs=./tools/nix/pkgs.nix -p 'nixfmt-tree' --run 'treefmt --quiet --fail-on-change'
-      - if: ${{ failure() }}
-        name: Show diff
-        run: git --no-pager diff
+        run: |
+          nix-shell -I nixpkgs=./tools/nix/pkgs.nix -p 'nixfmt-tree' --run '
+            treefmt --quiet --fail-on-change
+          ' || git --no-pager diff --exit-code
 
   lint-py:
     if: github.event.pull_request.draft == false
Repository: vercel/next.js
Pull request: Update Rspack development test manifest

This auto-generated PR updates the development integration test manifest used when testing Rspack.

Changed files:
filename: test/rspack-dev-tests-manifest.json
patch: @@ -600,6 +600,27 @@
     "flakey": [],
     "runtimeError": false
   },
+  "test/development/app-dir/cache-components-reused-promise/cache-components-reused-promise.test.ts": {
+    "passed": [
+      "cache-components-dev-warmup - reused promise aborts dynamic promises when restarting the render"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
+  "test/development/app-dir/cache-components-tasks/cache-components-tasks.test.ts": {
+    "passed": [
+      "cache-components-tasks - with runtime prefetch configs initial load setImmediate resolves between tasks",
+      "cache-components-tasks - with runtime prefetch configs navigation setImmediate resolves between tasks",
+      "cache-components-tasks - without runtime prefetch configs initial load setImmediate resolves between tasks",
+      "cache-components-tasks - without runtime prefetch configs navigation setImmediate resolves between tasks"
+    ],
+    "failed": [],
+    "pending": [],
+    "flakey": [],
+    "runtimeError": false
+  },
   "test/development/app-dir/cache-components-warnings/cache-components.warnings.test.ts": {
     "passed": [],
     "failed": [],
@@ -1189,14 +1210,13 @@
   },
   "test/development/app-hmr/hmr.test.ts": {
     "passed": [
+      "app-dir-hmr filesystem changes can navigate cleanly to a page that requires a change in the Webpack runtime",
       "app-dir-hmr filesystem changes should have no unexpected action error for hmr",
       "app-dir-hmr filesystem changes should not break when renaming a folder",
       "app-dir-hmr filesystem changes should not continously poll when hitting a not found page",
       "app-dir-hmr filesystem changes should update server components after navigating to a page with a different runtime"
     ],
-    "failed": [
-      "app-dir-hmr filesystem changes can navigate cleanly to a page that requires a change in the Webpack runtime"
-    ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
Repository: ollama/ollama
Pull request: server: allow vscode-webview origins


Changed files:
filename: envconfig/config.go
patch: @@ -72,6 +72,7 @@ func Origins() (origins []string) {
 		"app://*",
 		"file://*",
 		"tauri://*",
+		"vscode-webview://*",
 	)
 
 	return origins

filename: envconfig/config_test.go
patch: @@ -68,6 +68,7 @@ func TestOrigins(t *testing.T) {
 			"app://*",
 			"file://*",
 			"tauri://*",
+			"vscode-webview://*",
 		}},
 		{"http://10.0.0.1", []string{
 			"http://10.0.0.1",
@@ -86,6 +87,7 @@ func TestOrigins(t *testing.T) {
 			"app://*",
 			"file://*",
 			"tauri://*",
+			"vscode-webview://*",
 		}},
 		{"http://172.16.0.1,https://192.168.0.1", []string{
 			"http://172.16.0.1",
@@ -105,6 +107,7 @@ func TestOrigins(t *testing.T) {
 			"app://*",
 			"file://*",
 			"tauri://*",
+			"vscode-webview://*",
 		}},
 		{"http://totally.safe,http://definitely.legit", []string{
 			"http://totally.safe",
@@ -124,6 +127,7 @@ func TestOrigins(t *testing.T) {
 			"app://*",
 			"file://*",
 			"tauri://*",
+			"vscode-webview://*",
 		}},
 	}
 	for _, tt := range cases {
Repository: vuejs/vue
Pull request: Avoid double-decoding on attribute value

Chained `replace`s here may cause problems if the order isn't carefully arranged.Currently we get `"` after decoding `&amp;quot;` while `&quot;` is expected.

For a quick fix, I could move the `replace` which replaces `&amp;`s to the last.However, I prefer one single `replace` so that we don't bother with chaining order.



Changed files:
filename: src/compiler/parser/html-parser.js
patch: @@ -49,21 +49,19 @@ let IS_REGEX_CAPTURING_BROKEN = false
 const isScriptOrStyle = makeMap('script,style', true)
 const reCache = {}
 
-const ltRE = /&lt;/g
-const gtRE = /&gt;/g
-const nlRE = /&#10;/g
-const ampRE = /&amp;/g
-const quoteRE = /&quot;/g
+const decodingMap = {
+  '&lt;': '<',
+  '&gt;': '>',
+  '&quot;': '"',
+  '&amp;': '&',
+  '&#10;': '\n'
+}
+const encodedAttr = /&(lt|gt|quot|amp);/g
+const encodedAttrWithNewLines = /&(lt|gt|quot|amp|#10);/g
 
 function decodeAttr (value, shouldDecodeNewlines) {
-  if (shouldDecodeNewlines) {
-    value = value.replace(nlRE, '\n')
-  }
-  return value
-    .replace(ltRE, '<')
-    .replace(gtRE, '>')
-    .replace(ampRE, '&')
-    .replace(quoteRE, '"')
+  const re = shouldDecodeNewlines ? encodedAttrWithNewLines : encodedAttr
+  return value.replace(re, match => decodingMap[match])
 }
 
 export function parseHTML (html, options) {
Repository: electron/electron
Pull request: fix: release mouse buttons on focus loss on Wayland

Backport of #48752

See that PR for details.

Notes: Fixed an issue on Wayland (Linux) where right-clicking in the titlebar could  break mouse interactions.

Changed files:
filename: patches/chromium/.patches
patch: @@ -147,3 +147,4 @@ band-aid_over_an_issue_with_using_deprecated_nsopenpanel_api.patch
 disable_nsautofillheuristiccontroller_on_macos_26.patch
 expose_referrerscriptinfo_hostdefinedoptionsindex.patch
 inspectorpageagent_provisional_frame_speculative_fix.patch
+fix_release_mouse_buttons_on_focus_loss_on_wayland.patch

filename: patches/chromium/fix_release_mouse_buttons_on_focus_loss_on_wayland.patch
patch: @@ -0,0 +1,34 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Mitchell COhen <mitch.cohen@me.com>
+Date: Sun, 2 Nov 2025 15:30:56 -0500
+Subject: fix: release mouse buttons on focus loss on Wayland
+
+Fixes an issue where the mouse flags would get stuck if you right-click
+the CSD titlebar in Wayland.
+
+Bug: 455147429
+Change-Id: I9f5a9f395b3c1d85094a40a92d40691a897dbd05
+Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7091872
+Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
+Reviewed-by: Kramer Ge <fangzhoug@chromium.org>
+Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
+Cr-Commit-Position: refs/heads/main@{#1538048}
+
+diff --git a/ui/ozone/platform/wayland/host/wayland_event_source.cc b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+index 3ef7ad3369d458d56eb4e4702533005bc2de6261..44339caac5a2d818eb999786cd5093167c55a992 100644
+--- a/ui/ozone/platform/wayland/host/wayland_event_source.cc
++++ b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+@@ -334,6 +334,13 @@ void WaylandEventSource::OnPointerFocusChanged(
+     // Save new pointer location.
+     pointer_location_ = location;
+     window_manager_->SetPointerFocusedWindow(window);
++  } else {
++    // The compositor may swallow the release event for any buttons that are
++    // pressed when the window loses focus, e.g. when right-clicking the
++    // titlebar to open the system menu on GNOME.
++    if (!connection_->IsDragInProgress()) {
++      ReleasePressedPointerButtons(window, ui::EventTimeForNow());
++    }
+   }
+ 
+   auto closure = focused ? base::NullCallback()
Repository: ggml-org/llama.cpp
Pull request: CUDA: Do not mutate cgraph for fused ADDs

1. We should try to minimize in-place changes to the incoming ggml_cgraph where possible (those should happen in a backends' `graph_optimize` function)
2. Modifying in-place leads to an additional, unnecessary graph capture step as we store the properties before modifying the graph in-place in the cuda-backend: We hit `ggml_cuda_graph_node_set_properties` via `ggml_cuda_graph_update_required` before entering `ggml_cuda_graph_evaluate_and_capture`. 

Isolated from #19521


Changed files:
filename: ggml/src/ggml-cuda/ggml-cuda.cu
patch: @@ -3640,11 +3640,13 @@ static void ggml_cuda_graph_evaluate_and_capture(ggml_backend_cuda_context * cud
                         n_fuse++;
 
                         if (n_fuse > 1) {
+                            ggml_tensor fused_add_node;
+                            memcpy(&fused_add_node, node, sizeof(ggml_tensor));
                             for (int j = 0; j < n_fuse - 1; ++j) {
-                                node->src[j + 2] = cgraph->nodes[i + j + 1]->src[1];
+                                fused_add_node.src[j + 2] = cgraph->nodes[i + j + 1]->src[1];
                             }
-                            cgraph->nodes[i + n_fuse - 1]->data = node->data;
-                            ggml_cuda_op_fused_add(*cuda_ctx, node, n_fuse);
+                            fused_add_node.data = cgraph->nodes[i + n_fuse - 1]->data;
+                            ggml_cuda_op_fused_add(*cuda_ctx, &fused_add_node, n_fuse);
                             i += n_fuse - 1;
 
                             continue;
Repository: vuejs/vue
Pull request: Fix when functional component render method retrun null (fix #5536)

<!--
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) -->

issue: https://github.com/vuejs/vue/issues/5536

Originally I wanted to use `isDef` but the flow was a bit of a problem

**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:**

Changed files:
filename: src/core/vdom/create-element.js
patch: @@ -99,7 +99,7 @@ export function _createElement (
     // direct component options / constructor
     vnode = createComponent(tag, data, context, children)
   }
-  if (vnode !== undefined) {
+  if (isDef(vnode)) {
     if (ns) applyNS(vnode, ns)
     return vnode
   } else {

filename: test/unit/features/options/functional.spec.js
patch: @@ -1,4 +1,5 @@
 import Vue from 'vue'
+import { createEmptyVNode } from 'core/vdom/vnode'
 
 describe('Options functional', () => {
   it('should work', done => {
@@ -167,4 +168,21 @@ describe('Options functional', () => {
       vm.$destroy()
     }).then(done)
   })
+
+  it('create empty vnode when render return null', () => {
+    const child = {
+      functional: true,
+      render () {
+        return null
+      }
+    }
+    const vm = new Vue({
+      components: {
+        child
+      }
+    })
+    const h = vm.$createElement
+    const vnode = h('child')
+    expect(vnode).toEqual(createEmptyVNode())
+  })
 })
Repository: ollama/ollama
Pull request: Adding 'Ollama App' as community integrations

A little while back, I created an app to interact with Ollama from your phone called 'Ollama App'. I know, very creative, but the name stuck. I'd be very happy if it could be added to the integrations list.

At the moment, I only recommend using the mobile version, it's the most stable one, and the only one with a stable build, but I am cooking around a few other platforms (Flutter really is fabulous with multiplatform), like Desktop and maybe Web. When I'd decide to remove the experimental tag, where should I put them? Should I copy the entry and put it into multiple categories?

Thank you

Changed files:
filename: README.md
patch: @@ -330,6 +330,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [LLMChat](https://github.com/trendy-design/llmchat) (Privacy focused, 100% local, intuitive all-in-one chat interface)
 - [ARGO](https://github.com/xark-argo/argo) (Locally download and run Ollama and Huggingface models with RAG on Mac/Windows/Linux)
 - [G1](https://github.com/bklieger-groq/g1) (Prototype of using prompting strategies to improve the LLM's reasoning through o1-like reasoning chains.)
+- [Ollama App](https://github.com/JHubi1/ollama-app) (Modern and easy-to-use multi-platform client for Ollama)
 
 ### Terminal
 
@@ -416,6 +417,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 
 - [Enchanted](https://github.com/AugustDev/enchanted)
 - [Maid](https://github.com/Mobile-Artificial-Intelligence/maid)
+- [Ollama App](https://github.com/JHubi1/ollama-app) (Modern and easy-to-use multi-platform client for Ollama)
 - [ConfiChat](https://github.com/1runeberg/confichat) (Lightweight, standalone, multi-platform, and privacy focused LLM chat interface with optional encryption)
 
 ### Extensions & Plugins
Repository: facebook/react
Pull request: [playground] Wait for Monaco to fully load


I'm not sure what exactly is causing the flakiness in the playground e2e tests but I suspect it's some kind of timing issue.

Let's try waiting for Monaco to be fully initialized before running tests.
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32584).
* __->__ #32584
* #32583

Changed files:
filename: compiler/apps/playground/__tests__/e2e/page.spec.ts
patch: @@ -105,6 +105,9 @@ function nonReactFn() {
 
 test('editor should open successfully', async ({page}) => {
   await page.goto(`/`, {waitUntil: 'networkidle'});
+  await page.waitForFunction(
+    () => typeof window['MonacoEnvironment'] !== 'undefined',
+  );
   await page.screenshot({
     fullPage: true,
     path: 'test-results/00-fresh-page.png',
@@ -120,6 +123,9 @@ test('editor should compile from hash successfully', async ({page}) => {
   };
   const hash = encodeStore(store);
   await page.goto(`/#${hash}`, {waitUntil: 'networkidle'});
+  await page.waitForFunction(
+    () => typeof window['MonacoEnvironment'] !== 'undefined',
+  );
 
   // User input from hash compiles
   await page.screenshot({
@@ -143,6 +149,9 @@ test('reset button works', async ({page}) => {
   };
   const hash = encodeStore(store);
   await page.goto(`/#${hash}`, {waitUntil: 'networkidle'});
+  await page.waitForFunction(
+    () => typeof window['MonacoEnvironment'] !== 'undefined',
+  );
 
   // Reset button works
   page.on('dialog', dialog => dialog.accept());
@@ -166,6 +175,9 @@ TEST_CASE_INPUTS.forEach((t, idx) =>
     };
     const hash = encodeStore(store);
     await page.goto(`/#${hash}`, {waitUntil: 'networkidle'});
+    await page.waitForFunction(
+      () => typeof window['MonacoEnvironment'] !== 'undefined',
+    );
     await page.screenshot({
       fullPage: true,
       path: `test-results/03-0${idx}-${t.name}.png`,
Repository: vuejs/vue
Pull request: tweak type definition layouting

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [x] 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
- [ ] 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/env.js
patch: @@ -171,8 +171,8 @@ if (typeof Set !== 'undefined' && isNative(Set)) {
 }
 
 interface ISet {
-  has(key: string| number): boolean;
-  add(key: string| number): mixed;
+  has(key: string | number): boolean;
+  add(key: string | number): mixed;
   clear(): void;
 }
Repository: vuejs/vue
Pull request: [vue-server-renderer] ensure assets are unique

Hello. During upgrade process of Nuxt.js to vue 2.3.x (nuxt/nuxt.js#633) we encounter strange behavior which adds duplicate entries to `initial` section of client manifest json file. This PR fixes this issue and also ensures every section's items are unique to prevent such kind of problem in future. This PR also prevents an unexpected exception when detecting and ignoring duplicated chunks.

```js
{
  "publicPath": "/_nuxt/",
  "all": [
    "0.nuxt.bundle.309097aded56ffb03943.js",
    "1.nuxt.bundle.38d034e2ba6054b908d2.js",
    "nuxt.bundle.83400ec2bd4f29e215ba.js",
    "vendor.bundle.5953dc67058e339c4b85.js",
    "manifest.5953dc67058e339c4b85.js",
    "index.html"
  ],
  "initial": [
    "manifest.5953dc67058e339c4b85.js",
    "vendor.bundle.5953dc67058e339c4b85.js",
    "nuxt.bundle.83400ec2bd4f29e215ba.js",
    "manifest.5953dc67058e339c4b85.js",
    "vendor.bundle.5953dc67058e339c4b85.js"
  ],
  "async": [
    "0.nuxt.bundle.309097aded56ffb03943.js",
    "1.nuxt.bundle.38d034e2ba6054b908d2.js"
  ],
}
```

-------------------
Type: **Bug Fix**
Breaking: **No**

Changed files:
filename: package.json
patch: @@ -96,6 +96,7 @@
     "karma-webpack": "^2.0.1",
     "lodash": "^4.17.1",
     "lodash.template": "^4.4.0",
+    "lodash.uniq": "^4.5.0",
     "lru-cache": "^4.0.2",
     "nightwatch": "^0.9.9",
     "nightwatch-helpers": "^1.2.0",

filename: packages/vue-server-renderer/package.json
patch: @@ -22,6 +22,7 @@
     "hash-sum": "^1.0.2",
     "he": "^1.1.0",
     "lodash.template": "^4.4.0",
+    "lodash.uniq": "^4.5.0",
     "resolve": "^1.2.0",
     "source-map": "0.5.6",
     "serialize-javascript": "^1.3.0"

filename: src/server/webpack-plugin/client.js
patch: @@ -1,4 +1,5 @@
 const hash = require('hash-sum')
+const uniq = require('lodash.uniq')
 import { isJS } from './util'
 
 export default class VueSSRClientPlugin {
@@ -12,13 +13,13 @@ export default class VueSSRClientPlugin {
     compiler.plugin('emit', (compilation, cb) => {
       const stats = compilation.getStats().toJson()
 
-      const allFiles = stats.assets
-        .map(a => a.name)
+      const allFiles = uniq(stats.assets
+        .map(a => a.name))
 
-      const initialFiles = Object.keys(stats.entrypoints)
+      const initialFiles = uniq(Object.keys(stats.entrypoints)
         .map(name => stats.entrypoints[name].assets)
         .reduce((assets, all) => all.concat(assets), [])
-        .filter(isJS)
+        .filter(isJS))
 
       const asyncFiles = allFiles
         .filter(isJS)
@@ -39,6 +40,9 @@ export default class VueSSRClientPlugin {
         if (m.chunks.length === 1) {
           const cid = m.chunks[0]
           const chunk = stats.chunks.find(c => c.id === cid)
+          if (!chunk || !chunk.files) {
+            return
+          }
           const files = manifest.modules[hash(m.identifier)] = chunk.files.map(fileToIndex)
           // find all asset modules associated with the same chunk
           assetModules.forEach(m => {