helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: build: update on-create-command for siso

As in title. Otherwise:

```
2026-01-12 09:45:27.402Z: Cloning "depot_tools" into /home/builduser/.electron_build_tools/third_party/depot_tools
2026-01-12 09:45:30.860Z: Updating /home/builduser/.electron_build_tools/third_party/depot_tools
2026-01-12 09:45:30.862Z: Running "/home/builduser/.electron_build_tools/third_party/depot_tools/update_depot_tools"
2026-01-12 09:45:47.147Z: WARN We've made these temporary changes to your configuration:
 * migrated remoteBuild from unsupported 'reclient' to 'siso'
 * added gn arg "use_siso = ********" needed by remoteBuild siso
Run "e sanitize-config" to make these changes permanent.
```

Notes: none.

Changed files:
filename: .devcontainer/on-create-command.sh
patch: @@ -48,7 +48,8 @@ if [ ! -f $buildtools/configs/evm.testing.json ]; then
             \"gen\": {
                 \"args\": [
                     \"import(\\\"//electron/build/args/testing.gn\\\")\",
-                    \"use_remoteexec = true\"
+                    \"use_remoteexec = true\",
+                    \"use_siso=true\"
                 ],
                 \"out\": \"Testing\"
             },
@@ -58,7 +59,7 @@ if [ ! -f $buildtools/configs/evm.testing.json ]; then
             },
             \"\$schema\": \"file:///home/builduser/.electron_build_tools/evm-config.schema.json\",
             \"configValidationLevel\": \"strict\",
-            \"remoteBuild\": \"reclient\",
+            \"remoteBuild\": \"siso\",
             \"preserveSDK\": 5
         }
     " >$buildtools/configs/evm.testing.json
Repository: ollama/ollama
Pull request: openai: finish streaming tool calls as tool_calls

When a response contains tool_calls it finishes the chat, and we see this already happening in Ollama in non-chunk mode. This ensures that the chunk with tool calls contains the finish reason, not a following one, while any following ones are not sent - their choice with empty content will conflict with the tool call response. This follows how OpenAI API behaves as far as I can tell.

/cc @codefromthecrypt 

Changed files:
filename: openai/openai.go
patch: @@ -20,6 +20,8 @@ import (
 	"github.com/ollama/ollama/types/model"
 )
 
+var finishReasonToolCalls = "tool_calls"
+
 type Error struct {
 	Message string      `json:"message"`
 	Type    string      `json:"type"`
@@ -266,7 +268,7 @@ func toChatCompletion(id string, r api.ChatResponse) ChatCompletion {
 	}
 }
 
-func toChunk(id string, r api.ChatResponse) ChatCompletionChunk {
+func toChunk(id string, r api.ChatResponse, toolCallSent bool) ChatCompletionChunk {
 	toolCalls := toToolCalls(r.Message.ToolCalls)
 	return ChatCompletionChunk{
 		Id:                id,
@@ -279,6 +281,9 @@ func toChunk(id string, r api.ChatResponse) ChatCompletionChunk {
 			Delta: Message{Role: "assistant", Content: r.Message.Content, ToolCalls: toolCalls},
 			FinishReason: func(reason string) *string {
 				if len(reason) > 0 {
+					if toolCallSent {
+						return &finishReasonToolCalls
+					}
 					return &reason
 				}
 				return nil
@@ -585,6 +590,7 @@ type ChatWriter struct {
 	stream        bool
 	streamOptions *StreamOptions
 	id            string
+	toolCallSent  bool
 	BaseWriter
 }
 
@@ -634,11 +640,14 @@ func (w *ChatWriter) writeResponse(data []byte) (int, error) {
 
 	// chat chunk
 	if w.stream {
-		c := toChunk(w.id, chatResponse)
+		c := toChunk(w.id, chatResponse, w.toolCallSent)
 		d, err := json.Marshal(c)
 		if err != nil {
 			return 0, err
 		}
+		if !w.toolCallSent && len(c.Choices) > 0 && len(c.Choices[0].Delta.ToolCalls) > 0 {
+			w.toolCallSent = true
+		}
 
 		w.ResponseWriter.Header().Set("Content-Type", "text/event-stream")
 		_, err = w.ResponseWriter.Write([]byte(fmt.Sprintf("data: %s\n\n", d)))
Repository: nodejs/node
Pull request: os: freeze signals constant

Remove the ability to mutate signals constant as doing so can lead to unexpected behavior, notably when spawning child process.

Fixes: https://github.com/nodejs/node/issues/44749

<!--
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: lib/os.js
patch: @@ -25,6 +25,7 @@ const {
   ArrayPrototypePush,
   Float64Array,
   ObjectDefineProperties,
+  ObjectFreeze,
   StringPrototypeSlice,
   SymbolToPrimitive,
 } = primordials;
@@ -330,6 +331,8 @@ module.exports = {
   machine: getMachine,
 };
 
+ObjectFreeze(constants.signals);
+
 ObjectDefineProperties(module.exports, {
   constants: {
     __proto__: null,

filename: test/parallel/test-os-constants-signals.js
patch: @@ -0,0 +1,11 @@
+'use strict';
+
+require('../common');
+const { test } = require('node:test');
+const assert = require('node:assert');
+const { constants } = require('node:os');
+
+
+test('Verify that signals constant is immutable', () => {
+  assert.throws(() => constants.signals.FOOBAR = 1337, TypeError);
+});
Repository: ollama/ollama
Pull request: Add Ollamazing to Community Integrations

Add [Ollamazing](https://github.com/buiducnhat/ollamazing), a web extension.

Changed files:
filename: README.md
patch: @@ -380,6 +380,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [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)
+- [Ollamazing](https://github.com/buiducnhat/ollamazing) (Web extension to run Ollama models)
 
 ### Cloud
Repository: vuejs/vue
Pull request: Reactive components count

<!--
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:**

Before:
<img width="285" alt="screen shot 2018-04-10 at 18 48 06" src="https://user-images.githubusercontent.com/9060043/38568400-374c1ed2-3cf1-11e8-95e4-e312812aa460.png">

Alter:
<img width="223" alt="screen shot 2018-04-10 at 18 47 46" src="https://user-images.githubusercontent.com/9060043/38568398-37271240-3cf1-11e8-8e7c-b100975912cf.png">



Changed files:
filename: benchmarks/reorder-list/index.html
patch: @@ -15,7 +15,7 @@
 
     <script type="text/x-template" id="t">
       <div>
-        <h1>{{ total }} Components</h1>
+        <h1>{{ items.length }} Components</h1>
         <p>{{ action }} took {{time}}ms.</p>
         <button @click="shuffle">shuffle</button>
         <button @click="add">add</button>
Repository: nodejs/node
Pull request: fix: custom inspect should not throw when called with wrong this

Fixes #46323

I see `Event` has a similar brand check (lib/internal/event_target.js:152) Should we also remove that one?

<!--
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: lib/internal/event_target.js
patch: @@ -867,8 +867,6 @@ class EventTarget {
     return new CustomEvent(type, { detail: nodeValue });
   }
   [customInspectSymbol](depth, options) {
-    if (!isEventTarget(this))
-      throw new ERR_INVALID_THIS('EventTarget');
     const name = this.constructor.name;
     if (depth < 0)
       return name;

filename: test/parallel/test-eventtarget-custom-inspect-does-not-throw.js
patch: @@ -0,0 +1,19 @@
+'use strict';
+
+require('../common');
+const assert = require('assert');
+const util = require('util');
+
+const symbol = util.inspect.custom;
+
+const eventTargetInspect = EventTarget.prototype[symbol];
+
+const fakeEventTarget = {
+  [symbol]: eventTargetInspect,
+  someOtherField: 42
+};
+
+// Should not throw when calling the custom inspect method
+const output = util.inspect(fakeEventTarget);
+
+assert.strictEqual(typeof output, 'string');
Repository: ollama/ollama
Pull request: Add H200 as supported device.

Fixes: #9031

Changed files:
filename: docs/gpu.md
patch: @@ -7,7 +7,7 @@ Check your compute compatibility to see if your card is supported:
 
 | Compute Capability | Family              | Cards                                                                                                       |
 | ------------------ | ------------------- | ----------------------------------------------------------------------------------------------------------- |
-| 9.0                | NVIDIA              | `H100`                                                                                                      |
+| 9.0                | NVIDIA              | `H200` `H100`                                                                                               |
 | 8.9                | GeForce RTX 40xx    | `RTX 4090` `RTX 4080 SUPER` `RTX 4080` `RTX 4070 Ti SUPER` `RTX 4070 Ti` `RTX 4070 SUPER` `RTX 4070` `RTX 4060 Ti` `RTX 4060`  |
 |                    | NVIDIA Professional | `L4` `L40` `RTX 6000`                                                                                       |
 | 8.6                | GeForce RTX 30xx    | `RTX 3090 Ti` `RTX 3090` `RTX 3080 Ti` `RTX 3080` `RTX 3070 Ti` `RTX 3070` `RTX 3060 Ti` `RTX 3060` `RTX 3050 Ti` `RTX 3050`   |
Repository: huggingface/transformers
Pull request: Silence pytest warnings due to sentencepiece version

# What does this PR do?

As per the title. Finally localized why they would pop up when running `pytest` on some envs

Changed files:
filename: pyproject.toml
patch: @@ -72,5 +72,11 @@ markers = [
 log_cli = 1
 log_cli_level = "WARNING"
 asyncio_default_fixture_loop_scope = "function"
-# The above pytest-asyncio rule emits unnessecary warnings when it's not installed, so skip it by regex here
-filterwarnings = ["ignore:Unknown config option.*asyncio_default_fixture_loop_scope"]
+filterwarnings = [
+    # The above pytest-asyncio rule emits unnessecary warnings when it's not installed, so skip it here
+    "ignore:Unknown config option.*asyncio_default_fixture_loop_scope",
+    # Latest sentencepiece (v0.2.1) triggers those warnings when installed due to its build with afflicted version of swig - skip them
+    "ignore:builtin type SwigPyPacked has no __module__ attribute:DeprecationWarning",
+    "ignore:builtin type SwigPyObject has no __module__ attribute:DeprecationWarning",
+    "ignore:builtin type swigvarlink has no __module__ attribute:DeprecationWarning",
+]
Repository: electron/electron
Pull request: build: update NMV to 145

#### 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
-->

Upstream PR: https://github.com/nodejs/node/pull/61291

Needs to be merged before cutting the `41-x-y` release branch.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included
- [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: none


Changed files:
filename: build/args/all.gn
patch: @@ -2,7 +2,7 @@ is_electron_build = true
 root_extra_deps = [ "//electron" ]
 
 # Registry of NMVs --> https://github.com/nodejs/node/blob/main/doc/abi_version_registry.json
-node_module_version = 143
+node_module_version = 145
 
 v8_promise_internal_field_count = 1
 v8_embedder_string = "-electron.0"
Repository: ollama/ollama
Pull request: readme: fix nix package link

Existing link is to the now deprecated 24.05 release, removing the channel tag from the url so it will always go to the current stable channel.

Changed files:
filename: README.md
patch: @@ -439,7 +439,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Gentoo](https://github.com/gentoo/guru/tree/master/app-misc/ollama)
 - [Helm Chart](https://artifacthub.io/packages/helm/ollama-helm/ollama)
 - [Guix channel](https://codeberg.org/tusharhero/ollama-guix)
-- [Nix package](https://search.nixos.org/packages?channel=24.05&show=ollama&from=0&size=50&sort=relevance&type=packages&query=ollama)
+- [Nix package](https://search.nixos.org/packages?show=ollama&from=0&size=50&sort=relevance&type=packages&query=ollama)
 - [Flox](https://flox.dev/blog/ollama-part-one)
 
 ### Libraries
Repository: vercel/next.js
Pull request: [test] Remove rogue debug log

Logging the work unit store caused the following runtime error under some circumstances:

```
TypeError: Cannot read private member #headersList from an object whose class did not declare it
```

Changed files:
filename: test/e2e/app-dir/segment-cache/prefetch-runtime/app/(default)/errors/sync-io-after-runtime-api/dynamic-params/[id]/page.tsx
patch: @@ -1,6 +1,5 @@
 import { Suspense } from 'react'
 import { DebugRenderKind } from '../../../../../shared'
-import { workUnitAsyncStorage } from 'next/dist/server/app-render/work-unit-async-storage.external'
 
 type Params = { id: string }
 
@@ -25,11 +24,6 @@ export default async function Page({ params }: { params: Promise<Params> }) {
 }
 
 async function RuntimePrefetchable({ params }: { params: Promise<Params> }) {
-  const res = await params
-  console.log(
-    'RuntimePrefetchable :: awaited params',
-    res,
-    workUnitAsyncStorage.getStore()
-  )
+  await params
   return <div id="timestamp">Timestamp: {Date.now()}</div>
 }
Repository: ggml-org/llama.cpp
Pull request: Revert to OAI-compatible args

Reverts the output of function arguments to OpenAI-compatible format. Supersedes #20202 

Changed files:
filename: common/chat.cpp
patch: @@ -129,7 +129,7 @@ json common_chat_msg::to_json_oaicompat(bool concat_typed_text) const {
                 {"type", "function"},
                 {"function", {
                     {"name", tool_call.name},
-                    {"arguments", json::parse(tool_call.arguments)},
+                    {"arguments", json(tool_call.arguments)},
                 }},
             };
             if (!tool_call.id.empty()) {
@@ -1353,6 +1353,8 @@ static common_chat_params common_chat_templates_apply_jinja(const struct common_
     params.add_bos = tmpls->add_bos;
     params.add_eos = tmpls->add_eos;
 
+    workaround::func_args_not_string(params.messages);
+
     if (!tmpl.original_caps().supports_system_role) {
         workaround::system_message_not_supported(params.messages);
     }

filename: tests/test-chat.cpp
patch: @@ -1434,9 +1434,7 @@ static void test_msgs_oaicompat_json_conversion() {
                               "        \"type\": \"function\",\n"
                               "        \"function\": {\n"
                               "          \"name\": \"python\",\n"
-                              "          \"arguments\": {\n"
-                              "            \"code\": \"print('hey')\"\n"
-                              "          }\n"
+                              "          \"arguments\": \"{\\\"code\\\":\\\"print('hey')\\\"}\"\n"
                               "        }\n"
                               "      }\n"
                               "    ]\n"
Repository: vuejs/vue
Pull request: fix(core): Use native bind function instead of own (fix #7408)

Simple refactor bind function for easy revert.
Custom bind implementation performance is lower than native. ( https://jsperf.com/vue-bind-perf )

issue link: https://github.com/vuejs/vue/issues/7408

<!--
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:**

- [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/shared/util.js
patch: @@ -174,22 +174,34 @@ export const hyphenate = cached((str: string): string => {
 })
 
 /**
- * Simple bind, faster than native
+ * Simple bind polyfill for environments that do not support it... e.g.
+ * PhantomJS 1.x. Technically we don't need this anymore since native bind is
+ * now more performant in most browsers, but removing it would be breaking for
+ * code that was able to run in PhantomJS 1.x, so this must be kept for
+ * backwards compatibility.
  */
-export function bind (fn: Function, ctx: Object): Function {
+function polyfillBind (fn: Function, ctx: Object): Function {
   function boundFn (a) {
-    const l: number = arguments.length
+    const l = arguments.length
     return l
       ? l > 1
         ? fn.apply(ctx, arguments)
         : fn.call(ctx, a)
       : fn.call(ctx)
   }
-  // record original fn length
+
   boundFn._length = fn.length
   return boundFn
 }
 
+function nativeBind (fn: Function, ctx: Object): Function {
+  return fn.bind(ctx)
+}
+
+export const bind = Function.prototype.bind
+  ? nativeBind
+  : polyfillBind
+
 /**
  * Convert an Array-like object to a real Array.
  */
Repository: ollama/ollama
Pull request: build: add `-DGGML_CUDA_NO_PEER_COPY=ON` for ROCm ggml builds on windows

Fixes https://github.com/ollama/ollama/issues/9048

Changed files:
filename: CMakeLists.txt
patch: @@ -104,6 +104,10 @@ if(CMAKE_HIP_COMPILER)
     if(AMDGPU_TARGETS)
         add_subdirectory(${CMAKE_CURRENT_SOURCE_DIR}/ml/backend/ggml/ggml/src/ggml-hip)
 
+        if (WIN32)
+            target_compile_definitions(ggml-hip PRIVATE GGML_CUDA_NO_PEER_COPY=1)
+        endif()
+
         set(OLLAMA_HIP_INSTALL_DIR ${OLLAMA_INSTALL_DIR}/rocm)
         install(TARGETS ggml-hip
             RUNTIME_DEPENDENCIES
Repository: ollama/ollama
Pull request: doc: fix link for Abso

Hi,
I've realized the link from my previous PR was not pointing to the Abso repo, so I've fixed that.

Changed files:
filename: README.md
patch: @@ -494,7 +494,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [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)
-- [Abso](https://github.com/lunary-ai/abso/blob/main/README.md#ollama) (OpenAI-compatible TypeScript SDK for any LLM provider)
+- [Abso](https://github.com/lunary-ai/abso) (OpenAI-compatible TypeScript SDK for any LLM provider)
 
 ### Mobile