helloadhavan/github_issues huggingface dataset:
Repository: vuejs/vue
Pull request: fix: correct the `has` implementation in the `_renderProxy`

It's feasible that someone might ask if something other than a string is
in the proxy such as a `Symbol` that lacks a `charAt` method.  This aligns
the implementation with the `getHandler`.

<!--
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:**

This issue was discovered when using `vue-test-utils` and the associated test helpers it provides.  Ref: https://github.com/vuejs/vue-test-utils/issues/452


Changed files:
filename: src/core/instance/proxy.js
patch: @@ -45,7 +45,7 @@ if (process.env.NODE_ENV !== 'production') {
   const hasHandler = {
     has (target, key) {
       const has = key in target
-      const isAllowed = allowedGlobals(key) || key.charAt(0) === '_'
+      const isAllowed = allowedGlobals(key) || (typeof key === 'string' && key.charAt(0) === '_')
       if (!has && !isAllowed) {
         warnNonPresent(target, key)
       }

filename: test/unit/features/instance/render-proxy.spec.js
patch: @@ -28,5 +28,22 @@ if (typeof Proxy !== 'undefined') {
       }).$mount()
       expect(`Property or method "a" is not defined`).not.toHaveBeenWarned()
     })
+
+    it('support symbols using the `in` operator in hand-written render functions', () => {
+      const sym = Symbol()
+
+      const vm = new Vue({
+        created () {
+          this[sym] = 'foo'
+        },
+        render (h) {
+          if (sym in this) {
+            return h('div', [this[sym]])
+          }
+        }
+      }).$mount()
+
+      expect(vm.$el.textContent).toBe('foo')
+    })
   })
 }
Repository: vercel/next.js
Pull request: Update Rspack production test manifest

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

Changed files:
filename: test/rspack-build-tests-manifest.json
patch: @@ -7308,9 +7308,9 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/static-shell-debugging/static-shell-debugging.test.ts": {
-    "passed": [],
+    "passed": ["static-shell-debugging should render the full page"],
     "failed": [],
-    "pending": ["static-shell-debugging should render the full page"],
+    "pending": [],
     "flakey": [],
     "runtimeError": false
   },
@@ -10615,7 +10615,10 @@
   "test/e2e/swc-plugins/index.test.ts": {
     "passed": ["swcPlugins supports swcPlugins basic case"],
     "failed": [],
-    "pending": ["swcPlugins invalid plugin name shows a redbox in dev"],
+    "pending": [
+      "swcPlugins incompatible plugin version shows a redbox in dev",
+      "swcPlugins invalid plugin name shows a redbox in dev"
+    ],
     "flakey": [],
     "runtimeError": false
   },
@@ -20876,11 +20879,11 @@
     "runtimeError": false
   },
   "test/production/app-dir/metadata-streaming-config/metadata-streaming-config-customized.test.ts": {
-    "passed": [],
-    "failed": [],
-    "pending": [
+    "passed": [
       "app-dir - metadata-streaming-config-customized should have the customized streaming metadata config output in routes-manifest.json"
     ],
+    "failed": [],
+    "pending": [],
     "flakey": [],
     "runtimeError": false
   },
@@ -21676,9 +21679,9 @@
     "passed": [],
     "failed": [],
     "pending": [
-      "next-server-nft should not include .next directory in traces despite dynamic fs operations",
-      "next-server-nft should not trace too many files in next-minimal-server.js.nft.json",
-      "next-server-nft should not trace too many files in next-server.js.nft.json"
+      "next-server-nft default mode should not include .next directory in traces despite dynamic fs operations",
+      "next-server-nft default mode should not trace too many files in next-minimal-server.js.nft.json",
+      "next-server-nft with output:standalone should not trace too many files in next-server.js.nft.json"
     ],
     "flakey": [],
     "runtimeError": false
Repository: ollama/ollama
Pull request: Add "LocalLLM" Repo link


Changed files:
filename: README.md
patch: @@ -379,6 +379,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [MinimalNextOllamaChat](https://github.com/anilkay/MinimalNextOllamaChat) (Minimal Web UI for Chat and Model Control)
 - [Chipper](https://github.com/TilmanGriesel/chipper) AI interface for tinkerers (Ollama, Haystack RAG, Python)
 - [ChibiChat](https://github.com/CosmicEventHorizon/ChibiChat) (Kotlin-based Android app to chat with Ollama and Koboldcpp API endpoints)
+- [LocalLLM](https://github.com/qusaismael/localllm) (Minimal Web-App to run ollama models on it with a GUI)
 
 ### Cloud
Repository: ollama/ollama
Pull request: Add library in Zig.


Changed files:
filename: README.md
patch: @@ -492,6 +492,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Ollama for Haskell](https://github.com/tusharad/ollama-haskell)
 - [multi-llm-ts](https://github.com/nbonamy/multi-llm-ts) (A Typescript/JavaScript library allowing access to different LLM in unified API)
 - [LlmTornado](https://github.com/lofcz/llmtornado) (C# library providing a unified interface for major FOSS & Commercial inference APIs)
+- [Ollama for Zig](https://github.com/dravenk/ollama-zig)
 
 ### Mobile
Repository: vuejs/vue
Pull request: fix(ssr): add Fragment in RenderState typing

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `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/server/render-context.js
patch: @@ -6,7 +6,12 @@ type RenderState = {
   type: 'Element';
   rendered: number;
   total: number;
+  children: Array<VNode>;
   endTag: string;
+} | {
+  type: 'Fragment';
+  rendered: number;
+  total: number;
   children: Array<VNode>;
 } | {
   type: 'Component';
@@ -74,7 +79,7 @@ export class RenderContext {
           this.renderNode(children[rendered], false, this)
         } else {
           this.renderStates.pop()
-          if (lastState.endTag) {
+          if (lastState.type === 'Element') {
             this.write(lastState.endTag, this.next)
           } else {
             this.next()
Repository: electron/electron
Pull request: fix: drag regions in child windows (manual backport 40-x-y)

#### Description of Change

Manual backport of #49231. See that PR for details.

#### Release Notes

Notes: Fixed drag regions in child windows


Changed files:
filename: shell/browser/api/electron_api_web_contents.cc
patch: @@ -754,6 +754,10 @@ WebContents::WebContents(v8::Isolate* isolate,
   script_executor_ = std::make_unique<extensions::ScriptExecutor>(web_contents);
 #endif
 
+  // TODO: This works for main frames, but does not work for child frames.
+  // See: https://github.com/electron/electron/issues/49256
+  web_contents->SetSupportsDraggableRegions(true);
+
   session_ = Session::CreateFrom(isolate, GetBrowserContext());
 
   SetUserAgent(GetBrowserContext()->GetUserAgent());
@@ -1021,6 +1025,10 @@ void WebContents::InitWithWebContents(
   browser_context_ = browser_context;
   web_contents->SetDelegate(this);
 
+  // TODO: This works for main frames, but does not work for child frames.
+  // See: https://github.com/electron/electron/issues/49256
+  web_contents->SetSupportsDraggableRegions(true);
+
 #if BUILDFLAG(ENABLE_PRINTING)
   PrintViewManagerElectron::CreateForWebContents(web_contents.get());
   printing::CreateCompositeClientIfNeeded(web_contents.get(), GetUserAgent());
@@ -1777,8 +1785,6 @@ void WebContents::RenderFrameCreated(
     auto details = gin_helper::Dictionary::CreateEmpty(isolate);
     details.SetGetter("frame", render_frame_host);
     Emit("frame-created", details);
-    content::WebContents::FromRenderFrameHost(render_frame_host)
-        ->SetSupportsDraggableRegions(true);
   }
 }
Repository: nodejs/node
Pull request: test: make buffer sizes 32bit-aware in test-internal-util-construct-sab

Fixes: #61025
Refs: #60497

The range checks for bound SharedArrayBuffer construction weren't compatible with the maximum array buffer size on 32-bit architectures.

Changed files:
filename: test/parallel/test-internal-util-construct-sab.js
patch: @@ -3,16 +3,20 @@
 
 require('../common');
 const assert = require('assert');
+const { kMaxLength } = require('buffer');
 const { isSharedArrayBuffer } = require('util/types');
 const { constructSharedArrayBuffer } = require('internal/util');
 
 // We're testing that we can construct a SAB even when the global is not exposed.
 assert.strictEqual(typeof SharedArrayBuffer, 'undefined');
 
-for (const length of [undefined, 0, 1, 2 ** 32]) {
+for (const length of [undefined, 0, 1, 2 ** 16]) {
   assert(isSharedArrayBuffer(constructSharedArrayBuffer(length)));
 }
 
-for (const length of [-1, Number.MAX_SAFE_INTEGER + 1, 2 ** 64]) {
+// Specifically test the following cases:
+// - out-of-range allocation requests should not crash the process
+// - no int64 overflow
+for (const length of [-1, kMaxLength + 1, 2 ** 64]) {
   assert.throws(() => constructSharedArrayBuffer(length), RangeError);
 }
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: @@ -9379,9 +9379,9 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/static-shell-debugging/static-shell-debugging.test.ts": {
-    "passed": [],
+    "passed": ["static-shell-debugging should render the full page"],
     "failed": [],
-    "pending": ["static-shell-debugging should render the full page"],
+    "pending": [],
     "flakey": [],
     "runtimeError": false
   },
@@ -9735,11 +9735,10 @@
     "runtimeError": false
   },
   "test/e2e/app-dir/use-cache-without-experimental-flag/use-cache-without-experimental-flag.test.ts": {
-    "passed": [
-      "use-cache-without-experimental-flag should recover from the build error if useCache flag is set",
-      "use-cache-without-experimental-flag should show a build error"
+    "passed": ["use-cache-without-experimental-flag should show a build error"],
+    "failed": [
+      "use-cache-without-experimental-flag should recover from the build error if useCache flag is set"
     ],
-    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false
@@ -12630,6 +12629,7 @@
   },
   "test/e2e/swc-plugins/index.test.ts": {
     "passed": [
+      "swcPlugins incompatible plugin version shows a redbox in dev",
       "swcPlugins invalid plugin name shows a redbox in dev",
       "swcPlugins supports swcPlugins basic case"
     ],
Repository: facebook/react
Pull request: Add test for multiple form submissions

Test for #30041 and #33055

Changed files:
filename: packages/react-dom/src/__tests__/ReactDOMForm-test.js
patch: @@ -1670,6 +1670,37 @@ describe('ReactDOMForm', () => {
     expect(divRef.current.textContent).toEqual('Current username: acdlite');
   });
 
+  it('parallel form submissions do not throw', async () => {
+    const formRef = React.createRef();
+    let resolve = null;
+    function App() {
+      async function submitForm() {
+        Scheduler.log('Action');
+        if (!resolve) {
+          await new Promise(res => {
+            resolve = res;
+          });
+        }
+      }
+      return <form ref={formRef} action={submitForm} />;
+    }
+    const root = ReactDOMClient.createRoot(container);
+    await act(() => root.render(<App />));
+
+    // Start first form submission
+    await act(async () => {
+      formRef.current.requestSubmit();
+    });
+    assertLog(['Action']);
+
+    // Submit form again while first form action is still pending
+    await act(async () => {
+      formRef.current.requestSubmit();
+      resolve(); // Resolve the promise to allow the first form action to complete
+    });
+    assertLog(['Action']);
+  });
+
   it(
     'requestFormReset works with inputs that are not descendants ' +
       'of the form element',
Repository: ollama/ollama
Pull request: Update faq.md

add port number so people will fully understand the OLLAMA_HOST Env. variable, especially when port number is not the default 11434 port.

Changed files:
filename: docs/faq.md
patch: @@ -66,7 +66,7 @@ If Ollama is run as a macOS application, environment variables should be set usi
 1. For each environment variable, call `launchctl setenv`.
 
     ```bash
-    launchctl setenv OLLAMA_HOST "0.0.0.0"
+    launchctl setenv OLLAMA_HOST "0.0.0.0:11434"
     ```
 
 2. Restart Ollama application.
@@ -81,7 +81,7 @@ If Ollama is run as a systemd service, environment variables should be set using
 
     ```ini
     [Service]
-    Environment="OLLAMA_HOST=0.0.0.0"
+    Environment="OLLAMA_HOST=0.0.0.0:11434"
     ```
 
 3. Save and exit.
Repository: ollama/ollama
Pull request: Update the Documentation.

Deepseek model also added into the documentation section.
1. 671B
2. 70B
3. 1.5B

Changed files:
filename: README.md
patch: @@ -54,6 +54,8 @@ Here are some example models that can be downloaded:
 
 | Model              | Parameters | Size  | Download                         |
 | ------------------ | ---------- | ----- | -------------------------------- |
+| DeepSeek-R1        | 7B         | 4.7GB | `ollama run deepseek-r1`         |
+| DeepSeek-R1        | 671B       | 404GB | `ollama run deepseek-r1:671b`    |
 | Llama 3.3          | 70B        | 43GB  | `ollama run llama3.3`            |
 | Llama 3.2          | 3B         | 2.0GB | `ollama run llama3.2`            |
 | Llama 3.2          | 1B         | 1.3GB | `ollama run llama3.2:1b`         |
Repository: ollama/ollama
Pull request: add gfx instinct gpus

add exclusion rule for windows to omit these targets since windows rocm does not support these gpus. this behavior can be disabled by setting `WINDOWS_AMDGPU_TARGETS_EXCLUDE_REGEX` to an empty string (or some other regular expression) to force building for these targets on windows

Changed files:
filename: CMakeLists.txt
patch: @@ -85,13 +85,20 @@ if(CMAKE_CUDA_COMPILER)
     )
 endif()
 
+set(WINDOWS_AMDGPU_TARGETS_EXCLUDE_REGEX "^gfx(906|908|90a):xnack[+-]$"
+    CACHE STRING
+    "Regular expression describing AMDGPU_TARGETS not supported on Windows. Override to force building these targets. Default \"^gfx(906|908|90a):xnack[+-]$\"."
+)
+
 check_language(HIP)
 if(CMAKE_HIP_COMPILER)
     set(HIP_PLATFORM "amd")
 
     find_package(hip REQUIRED)
     if(NOT AMDGPU_TARGETS)
         list(FILTER AMDGPU_TARGETS INCLUDE REGEX "^gfx(900|94[012]|101[02]|1030|110[012])$")
+    elseif(WIN32 AND WINDOWS_AMDGPU_TARGETS_EXCLUDE_REGEX)
+        list(FILTER AMDGPU_TARGETS EXCLUDE REGEX ${WINDOWS_AMDGPU_TARGETS_EXCLUDE_REGEX})
     endif()
 
     if(AMDGPU_TARGETS)

filename: CMakePresets.json
patch: @@ -56,7 +56,7 @@
       "name": "ROCm 6",
       "inherits": [ "ROCm" ],
       "cacheVariables": {
-        "AMDGPU_TARGETS": "gfx900;gfx940;gfx941;gfx942;gfx1010;gfx1012;gfx1030;gfx1100;gfx1101;gfx1102"
+        "AMDGPU_TARGETS": "gfx900;gfx940;gfx941;gfx942;gfx1010;gfx1012;gfx1030;gfx1100;gfx1101;gfx1102;gfx906:xnack-;gfx908:xnack-;gfx90a:xnack+;gfx90a:xnack-"
       }
     }
   ],
Repository: ollama/ollama
Pull request: add React Native client Integrations

I saw there is no React Native client for now,and I build a React Native client for ollama,it I can add this repo link to Community Integrations

Changed files:
filename: README.md
patch: @@ -353,6 +353,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Web management](https://github.com/lemonit-eric-mao/ollama-web-management) (Web management page)
 - [Promptery](https://github.com/promptery/promptery) (desktop client for Ollama.)
 - [Ollama App](https://github.com/JHubi1/ollama-app) (Modern and easy-to-use multi-platform client for Ollama)
+- [chat-ollama](https://github.com/annilq/chat-ollama) (a React Native client for Ollama)
 - [SpaceLlama](https://github.com/tcsenpai/spacellama) (Firefox and Chrome extension to quickly summarize web pages with ollama in a sidebar)
 - [YouLama](https://github.com/tcsenpai/youlama) (Webapp to quickly summarize any YouTube video, supporting Invidious as well)
 - [DualMind](https://github.com/tcsenpai/dualmind) (Experimental app allowing two models to talk to each other in the terminal or in a web interface)
Repository: facebook/react
Pull request: [compiler][repro] Nested fbt test fixture


Ideally we should detect and bail out on this case to avoid babel build failures.


Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/fbt/error.todo-fbt-param-nested-fbt.expect.md
patch: @@ -0,0 +1,56 @@
+
+## Input
+
+```javascript
+import fbt from 'fbt';
+import {Stringify} from 'shared-runtime';
+
+/**
+ * MemoizeFbtAndMacroOperands needs to account for nested fbt calls.
+ * Expected fixture `fbt-param-call-arguments` to succeed but it failed with error:
+ *   /fbt-param-call-arguments.ts: Line 19 Column 11: fbt: unsupported babel node: Identifier
+ *   ---
+ *   t3
+ *   ---
+ */
+function Component({firstname, lastname}) {
+  'use memo';
+  return (
+    <Stringify>
+      {fbt(
+        [
+          'Name: ',
+          fbt.param('firstname', <Stringify key={0} name={firstname} />),
+          ', ',
+          fbt.param(
+            'lastname',
+            <Stringify key={0} name={lastname}>
+              {fbt('(inner fbt)', 'Inner fbt value')}
+            </Stringify>
+          ),
+        ],
+        'Name'
+      )}
+    </Stringify>
+  );
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Component,
+  params: [{firstname: 'first', lastname: 'last'}],
+  sequentialRenders: [{firstname: 'first', lastname: 'last'}],
+};
+
+```
+
+
+## Error
+
+```
+Line 19 Column 11: fbt: unsupported babel node: Identifier
+---
+t3
+---
+```
+          
+      
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/fbt/error.todo-fbt-param-nested-fbt.js
patch: @@ -0,0 +1,38 @@
+import fbt from 'fbt';
+import {Stringify} from 'shared-runtime';
+
+/**
+ * MemoizeFbtAndMacroOperands needs to account for nested fbt calls.
+ * Expected fixture `fbt-param-call-arguments` to succeed but it failed with error:
+ *   /fbt-param-call-arguments.ts: Line 19 Column 11: fbt: unsupported babel node: Identifier
+ *   ---
+ *   t3
+ *   ---
+ */
+function Component({firstname, lastname}) {
+  'use memo';
+  return (
+    <Stringify>
+      {fbt(
+        [
+          'Name: ',
+          fbt.param('firstname', <Stringify key={0} name={firstname} />),
+          ', ',
+          fbt.param(
+            'lastname',
+            <Stringify key={0} name={lastname}>
+              {fbt('(inner fbt)', 'Inner fbt value')}
+            </Stringify>
+          ),
+        ],
+        'Name'
+      )}
+    </Stringify>
+  );
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Component,
+  params: [{firstname: 'first', lastname: 'last'}],
+  sequentialRenders: [{firstname: 'first', lastname: 'last'}],
+};
Repository: nodejs/node
Pull request: test_runner: fix lazy `test.assert` accessor

The intention was for this to be a define-on-access lazy property, but the object passed to `Object.defineProperty` isn't a descriptor, so this never happens. As a result, the `assert` object is currently reconstructed on every access; `test.assert === test.assert` is false at present.

Changed to a conventional lazy getter, in alignment with the other `node:test` property accessors.

Changed files:
filename: lib/test.js
patch: @@ -62,14 +62,18 @@ ObjectDefineProperty(module.exports, 'snapshot', {
   },
 });
 
+let lazyAssert;
+
 ObjectDefineProperty(module.exports, 'assert', {
   __proto__: null,
   configurable: true,
   enumerable: true,
   get() {
-    const { register } = require('internal/test_runner/assert');
-    const assert = { __proto__: null, register };
-    ObjectDefineProperty(module.exports, 'assert', assert);
-    return assert;
+    if (lazyAssert === undefined) {
+      const { register } = require('internal/test_runner/assert');
+      lazyAssert = { __proto__: null, register };
+    }
+
+    return lazyAssert;
   },
 });