helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: fix docker build-args

`env` context is not accessible from `job.*.strategy`. since it's in the environment, just tell Docker to use the environment variable

> You can also use the --build-arg flag without a value, in which case the daemon propagates the value from the local environment into the Docker container it's building

https://docs.docker.com/reference/cli/docker/buildx/build/#build-arg

Changed files:
filename: .github/workflows/release.yaml
patch: @@ -312,16 +312,18 @@ jobs:
           - flavor: 'latest=false'
             platforms: linux/amd64,linux/arm64
             build-args: |
-              CGO_CFLAGS=${{ env.CGO_CFLAGS }}
-              CGO_CXXFLAGS=${{ env.CGO_CXXFLAGS }}
-              GOFLAGS=${{ needs.setup-environment.outputs.GOFLAGS }}
+              CGO_CFLAGS
+              CGO_CXXFLAGS
+              GOFLAGS
           - flavor: 'latest=false,suffix=rocm'
             platforms: linux/amd64
             build-args: |
-              CGO_CFLAGS=${{ env.CGO_CFLAGS }}
-              CGO_CXXFLAGS=${{ env.CGO_CXXFLAGS }}
+              CGO_CFLAGS
+              CGO_CXXFLAGS
+              GOFLAGS
               FLAVOR=rocm
-              GOFLAGS=${{ needs.setup-environment.outputs.GOFLAGS }}
+    env:
+      GOFLAGS: ${{ needs.setup-environment.outputs.GOFLAGS }}
     runs-on: linux
     environment: release
     needs: setup-environment
Repository: electron/electron
Pull request: build: disallow non-maintainer changes to GitHub Actions workflows

Backport of #48038.

See that PR for details.

Notes: none

Changed files:
filename: .github/workflows/non-maintainer-dependency-change.yml
patch: @@ -1,16 +1,18 @@
-name: Check for Non-Maintainer Dependency Change
+name: Check for Disallowed Non-Maintainer Change
 
 on:
   pull_request_target:
     paths:
       - 'yarn.lock'
       - 'spec/yarn.lock'
+      - '.github/workflows/**'
+      - '.github/actions/**'
 
 permissions: {}
 
 jobs:
   check-for-non-maintainer-dependency-change:
-    name: Check for non-maintainer dependency change
+    name: Check for disallowed non-maintainer change
     if: ${{ !contains(fromJSON('["MEMBER", "OWNER"]'), github.event.pull_request.author_association) && github.event.pull_request.user.type != 'Bot' && !github.event.pull_request.draft }}
     permissions:
       contents: read
@@ -24,7 +26,7 @@ jobs:
           PR_URL: ${{ github.event.pull_request.html_url }}
         run: |
           set -eo pipefail
-          REVIEW_COUNT=$(gh pr view $PR_URL --json reviews | jq '[ .reviews[] | select(.author.login == "github-actions") | select(.body | startswith("<!-- no-dependency-change -->")) ] | length')
+          REVIEW_COUNT=$(gh pr view $PR_URL --json reviews | jq '[ .reviews[] | select(.author.login == "github-actions") | select(.body | startswith("<!-- disallowed-non-maintainer-change -->")) ] | length')
           if [[ $REVIEW_COUNT -eq 0 ]]; then
             echo "SHOULD_REVIEW=1" >> "$GITHUB_OUTPUT"
           fi
@@ -34,4 +36,4 @@ jobs:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           PR_URL: ${{ github.event.pull_request.html_url }}
         run: |
-          printf "<!-- no-dependency-change -->\n\nHello @${{ github.event.pull_request.user.login }}! It looks like this pull request touches one of our dependency files, and per [our contribution policy](https://github.com/electron/electron/blob/main/CONTRIBUTING.md#dependencies-upgrades-policy) we do not accept these types of changes in PRs." | gh pr review $PR_URL -r --body-file=-
+          printf "<!-- disallowed-non-maintainer-change -->\n\nHello @${{ github.event.pull_request.user.login }}! It looks like this pull request touches one of our dependency or CI files, and per [our contribution policy](https://github.com/electron/electron/blob/main/CONTRIBUTING.md#dependencies-upgrades-policy) we do not accept these types of changes in PRs." | gh pr review $PR_URL -r --body-file=-
Repository: vercel/next.js
Pull request: Tests: Reduce loglines from apply patch delay

Apply #83800 without merge conflicts.

Changed files:
filename: test/lib/next-modes/next-dev.ts
patch: @@ -150,7 +150,7 @@ export class NextDevInstance extends NextInstance {
       }
     }
 
-    console.log('running', shellQuote(startArgs))
+    require('console').log('running', shellQuote(startArgs))
     await new Promise<void>((resolve, reject) => {
       try {
         this.childProcess = spawn(startArgs[0], startArgs.slice(1), {
@@ -291,7 +291,7 @@ export class NextDevInstance extends NextInstance {
         }
 
         if (this.patchFileDelay > 0) {
-          console.warn(
+          require('console').warn(
             `Applying patch delay of ${this.patchFileDelay}ms. Note: Introducing artificial delays is generally discouraged, as it may affect test reliability. However, this delay is configurable on a per-test basis.`
           )
           await waitFor(this.patchFileDelay)
Repository: ollama/ollama
Pull request: build: set CFLAGS for cpu

`CPPFLAGS` doesn't get inserted into the right place and gets overwritten by the default `CFLAGS='-O2 -g'`. Set `CFLAGS` in the place it matters most in code and optionally configure it globally through `CGO_CFLAGS` and `CGO_CXXFLAGS` for release

Changed files:
filename: .github/workflows/release.yaml
patch: @@ -5,6 +5,10 @@ on:
     tags:
       - 'v*'
 
+env:
+  CGO_CFLAGS: '-O3'
+  CGO_CXXFLAGS: '-O3'
+
 jobs:
   setup-environment:
     runs-on: ubuntu-latest
@@ -291,7 +295,7 @@ jobs:
       - uses: docker/setup-buildx-action@v3
       - run: |
           apt-get update && apt-get install pigz
-          for TARGET in ${{ matrix.targets }}; do docker buildx build --platform $PLATFORM --target $TARGET --build-arg GOFLAGS --output type=local,dest=dist/$PLATFORM .; done
+          for TARGET in ${{ matrix.targets }}; do docker buildx build --platform $PLATFORM --target $TARGET --build-arg GOFLAGS --build-arg CGO_CFLAGS --build-args CGO_CXXFLAGS --output type=local,dest=dist/$PLATFORM .; done
           tar c -C dist/$PLATFORM . | pigz -9cv >dist/ollama-${PLATFORM//\//-}.tgz
         env:
           PLATFORM: ${{ matrix.os }}/${{ matrix.arch }}
@@ -308,12 +312,16 @@ jobs:
           - flavor: 'latest=false'
             platforms: linux/amd64,linux/arm64
             build-args: |
+              CGO_CFLAGS=${{ env.CGO_CFLAGS }}
+              CGO_CXXFLAGS=${{ env.CGO_CXXFLAGS }}
               GOFLAGS=${{ needs.setup-environment.outputs.GOFLAGS }}
           - flavor: 'latest=false,suffix=rocm'
             platforms: linux/amd64
             build-args: |
-              GOFLAGS=${{ needs.setup-environment.outputs.GOFLAGS }}
+              CGO_CFLAGS=${{ env.CGO_CFLAGS }}
+              CGO_CXXFLAGS=${{ env.CGO_CXXFLAGS }}
               FLAVOR=rocm
+              GOFLAGS=${{ needs.setup-environment.outputs.GOFLAGS }}
     runs-on: linux
     environment: release
     needs: setup-environment

filename: ml/backend/ggml/ggml/src/ggml-cpu/cpu.go
patch: @@ -1,6 +1,6 @@
 package cpu
 
-// #cgo CFLAGS: -Wno-implicit-function-declaration
+// #cgo CFLAGS: -O3 -Wno-implicit-function-declaration
 // #cgo CXXFLAGS: -std=c++17
 // #cgo CPPFLAGS: -I${SRCDIR}/amx -I${SRCDIR}/llamafile -I${SRCDIR}/.. -I${SRCDIR}/../../include
 // #cgo CPPFLAGS: -DGGML_USE_LLAMAFILE
Repository: ollama/ollama
Pull request: build: set goflags in linux release

GOFLAGS is set in the environment but need to tell docker to forward it to the build context

Changed files:
filename: .github/workflows/release.yaml
patch: @@ -291,7 +291,7 @@ jobs:
       - uses: docker/setup-buildx-action@v3
       - run: |
           apt-get update && apt-get install pigz
-          for TARGET in ${{ matrix.targets }}; do docker buildx build --platform $PLATFORM --target $TARGET --output type=local,dest=dist/$PLATFORM .; done
+          for TARGET in ${{ matrix.targets }}; do docker buildx build --platform $PLATFORM --target $TARGET --build-arg GOFLAGS --output type=local,dest=dist/$PLATFORM .; done
           tar c -C dist/$PLATFORM . | pigz -9cv >dist/ollama-${PLATFORM//\//-}.tgz
         env:
           PLATFORM: ${{ matrix.os }}/${{ matrix.arch }}
Repository: ollama/ollama
Pull request: discover: fix default LibOllamaPath value


Changed files:
filename: discover/path.go
patch: @@ -24,30 +24,34 @@ var LibOllamaPath string = func() string {
 		return ""
 	}
 
-	libPath := filepath.Dir(exe)
+	var libPath string
 	switch runtime.GOOS {
 	case "windows":
 		libPath = filepath.Join(filepath.Dir(exe), "lib", "ollama")
 	case "linux":
 		libPath = filepath.Join(filepath.Dir(exe), "..", "lib", "ollama")
+	case "darwin":
+		libPath = filepath.Dir(exe)
 	}
 
 	cwd, err := os.Getwd()
 	if err != nil {
 		return ""
 	}
 
-	// build paths for development
-	buildPaths := []string{
+	paths := []string{
+		libPath,
+
+		// build paths for development
 		filepath.Join(filepath.Dir(exe), "build", "lib", "ollama"),
 		filepath.Join(cwd, "build", "lib", "ollama"),
 	}
 
-	for _, p := range buildPaths {
+	for _, p := range paths {
 		if _, err := os.Stat(p); err == nil {
 			return p
 		}
 	}
 
-	return libPath
+	return filepath.Dir(exe)
 }()
Repository: vuejs/vue
Pull request: fix(refs): allow ref key to be zero (fix #7669)

prevents missing elements when :ref value is "0"

fix #7669

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**


Changed files:
filename: src/core/vdom/modules/ref.js
patch: @@ -1,6 +1,6 @@
 /* @flow */
 
-import { remove } from 'shared/util'
+import { remove, isDef } from 'shared/util'
 
 export default {
   create (_: any, vnode: VNodeWithData) {
@@ -19,7 +19,7 @@ export default {
 
 export function registerRef (vnode: VNodeWithData, isRemoval: ?boolean) {
   const key = vnode.data.ref
-  if (!key) return
+  if (!isDef(key)) return
 
   const vm = vnode.context
   const ref = vnode.componentInstance || vnode.elm

filename: test/unit/features/ref.spec.js
patch: @@ -9,6 +9,10 @@ describe('ref', () => {
     test2: {
       id: 'test2',
       template: '<div>test2</div>'
+    },
+    test3: {
+      id: 'test3',
+      template: '<div>test3</div>'
     }
   }
 
@@ -20,6 +24,7 @@ describe('ref', () => {
       template: `<div>
         <test ref="foo"></test>
         <test2 :ref="value"></test2>
+        <test3 :ref="0"></test3>
       </div>`,
       components
     })
@@ -28,6 +33,8 @@ describe('ref', () => {
     expect(vm.$refs.foo.$options.id).toBe('test')
     expect(vm.$refs.bar).toBeTruthy()
     expect(vm.$refs.bar.$options.id).toBe('test2')
+    expect(vm.$refs['0']).toBeTruthy()
+    expect(vm.$refs['0'].$options.id).toBe('test3')
   })
 
   it('should dynamically update refs', done => {
Repository: nodejs/node
Pull request: doc: add @avivkeller to collaborators

Fixes: #60937

(Re-open of #61113 with the correct branch. Sorry for my first mistake as a collaborator xD)

Changed files:
filename: README.md
patch: @@ -287,6 +287,8 @@ For information about the governance of the Node.js project, see
   **Yagiz Nizipli** <<yagiz@nizipli.com>> (he/him) - [Support me](https://github.com/sponsors/anonrig)
 * [atlowChemi](https://github.com/atlowChemi) -
   **Chemi Atlow** <<chemi@atlow.co.il>> (he/him)
+* [avivkeller](https://github.com/avivkeller) -
+  **Aviv Keller** <<me@aviv.sh>> (he/him) - [Support me](https://github.com/sponsors/avivkeller)
 * [Ayase-252](https://github.com/Ayase-252) -
   **Qingyu Deng** <<i@ayase-lab.com>>
 * [bengl](https://github.com/bengl) -
Repository: ollama/ollama
Pull request: parser: fix parsing Modelfiles with multiple FROM commands

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

Changed files:
filename: parser/parser.go
patch: @@ -62,7 +62,13 @@ func (f Modelfile) CreateRequest(relativeDir string) (*api.CreateRequest, error)
 				return nil, err
 			}
 
-			req.Files = digestMap
+			if req.Files == nil {
+				req.Files = digestMap
+			} else {
+				for k, v := range digestMap {
+					req.Files[k] = v
+				}
+			}
 		case "adapter":
 			path, err := expandPath(c.Args, relativeDir)
 			if err != nil {

filename: parser/parser_test.go
patch: @@ -793,15 +793,20 @@ func createBinFile(t *testing.T, kv map[string]any, ti []llm.Tensor) (string, st
 }
 
 func TestCreateRequestFiles(t *testing.T) {
-	name, digest := createBinFile(t, nil, nil)
+	n1, d1 := createBinFile(t, nil, nil)
+	n2, d2 := createBinFile(t, map[string]any{"foo": "bar"}, nil)
 
 	cases := []struct {
 		input    string
 		expected *api.CreateRequest
 	}{
 		{
-			fmt.Sprintf("FROM %s", name),
-			&api.CreateRequest{Files: map[string]string{name: digest}},
+			fmt.Sprintf("FROM %s", n1),
+			&api.CreateRequest{Files: map[string]string{n1: d1}},
+		},
+		{
+			fmt.Sprintf("FROM %s\nFROM %s", n1, n2),
+			&api.CreateRequest{Files: map[string]string{n1: d1, n2: d2}},
 		},
 	}
Repository: vercel/next.js
Pull request: Time logs: Show full millisecond instead of 1 decimal

## Fix: Remove unnecessary decimal place in millisecond duration formatting

### What

Fixed `durationToString` to display whole milliseconds (e.g., "193ms") instead of showing a redundant decimal place (e.g., "193.0ms").

### Why

The "Ready in X" message was displaying durations like "Ready in 193.0ms" which looks incorrect. The `.0` suffix provides no useful information and makes the output look like a bug.

### How

Changed `.toFixed(1)` to `.toFixed(0)` for millisecond formatting in `durationToString()`. This aligns with the behavior of the newer `durationToStringWithNanoseconds()` function which already uses `.toFixed(0)` for milliseconds.

**Before:** `✓ Ready in 193.0ms`  
**After:** `✓ Ready in 193ms`

Changed files:
filename: packages/next/src/build/duration-to-string.ts
patch: @@ -21,7 +21,7 @@ const MILLISECONDS_THRESHOLD_NANOSECONDS = 2_000_000 // 2 milliseconds in nanose
  * - >= 2 minutes: show in minutes with 1 decimal place (e.g., "2.5min")
  * - >= 40 seconds: show in whole seconds (e.g., "45s")
  * - >= 2 seconds: show in seconds with 1 decimal place (e.g., "3.2s")
- * - < 2 seconds: show in milliseconds with 1 decimal place (e.g., "1500.0ms")
+ * - < 2 seconds: show in whole milliseconds (e.g., "1500ms")
  *
  * @deprecated Use durationToStringWithNanoseconds instead, collect time in nanoseconds using process.hrtime.bigint().
  * @param compilerDuration - Duration in seconds as a number
@@ -35,7 +35,7 @@ export function durationToString(compilerDuration: number) {
   } else if (compilerDuration > SECONDS_THRESHOLD_LOW) {
     return `${compilerDuration.toFixed(1)}s`
   } else {
-    return `${(compilerDuration * MILLISECONDS_PER_SECOND).toFixed(1)}ms`
+    return `${(compilerDuration * MILLISECONDS_PER_SECOND).toFixed(0)}ms`
   }
 }
Repository: vuejs/vue
Pull request: test(types): update TS version and fix types test

<!--
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: Update tests

**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: package-lock.json
patch: @@ -9580,9 +9580,9 @@
       "dev": true
     },
     "typescript": {
-      "version": "2.6.2",
-      "resolved": "https://registry.npmjs.org/typescript/-/typescript-2.6.2.tgz",
-      "integrity": "sha1-PFtv1/beCRQmkCfwPAlGdY92c6Q=",
+      "version": "2.7.1",
+      "resolved": "https://registry.npmjs.org/typescript/-/typescript-2.7.1.tgz",
+      "integrity": "sha512-bqB1yS6o9TNA9ZC/MJxM0FZzPnZdtHj0xWK/IZ5khzVqdpGul/R/EIiHRgFXlwTD7PSIaYVnGKq1QgMCu2mnqw==",
       "dev": true
     },
     "uglify-js": {

filename: package.json
patch: @@ -134,7 +134,7 @@
     "selenium-server": "^2.53.1",
     "serialize-javascript": "^1.3.0",
     "shelljs": "^0.7.8",
-    "typescript": "^2.6.1",
+    "typescript": "^2.7.1",
     "uglify-js": "^3.0.15",
     "webpack": "^3.10.0",
     "weex-js-runtime": "^0.23.5",

filename: types/test/plugin-test.ts
patch: @@ -2,8 +2,8 @@ import Vue from "../index";
 import { PluginFunction, PluginObject } from "../index";
 
 class Option {
-  prefix: string;
-  suffix: string;
+  prefix: string = "";
+  suffix: string = "";
 }
 
 const plugin: PluginObject<Option> = {

filename: types/test/vue-test.ts
patch: @@ -2,7 +2,7 @@ import Vue, { VNode } from "../index";
 import { ComponentOptions } from "../options";
 
 class Test extends Vue {
-  a: number;
+  a: number = 0;
 
   testProperties() {
     this.$data;
@@ -19,7 +19,7 @@ class Test extends Vue {
   }
 
   // test property reification
-  $refs: {
+  $refs!: {
     vue: Vue,
     element: HTMLInputElement,
     vues: Vue[],
Repository: ollama/ollama
Pull request: readme: add AI Toolkit for VSCode to community integrations

Add [AI Toolkit for VSCode](https://marketplace.visualstudio.com/items?itemName=ms-windows-ai-studio.windows-ai-studio) to community integrations.

AI Toolkit for VSCode ollama support: https://aka.ms/ai-tooklit/ollama-docs

Changed files:
filename: README.md
patch: @@ -369,6 +369,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Minima](https://github.com/dmayboroda/minima) (RAG with on-premises or fully local workflow)
 - [aidful-ollama-model-delete](https://github.com/AidfulAI/aidful-ollama-model-delete) (User interface for simplified model cleanup)
 - [Perplexica](https://github.com/ItzCrazyKns/Perplexica) (An AI-powered search engine & an open-source alternative to Perplexity AI)
+- [AI Toolkit for Visual Studio Code](https://aka.ms/ai-tooklit/ollama-docs) (Microsoft-official VSCode extension to chat, test, evaluate models with Ollama support, and use them in your AI applications.)
 
 ### Cloud
Repository: ggml-org/llama.cpp
Pull request: hexagon: add llama-completion windows runner script

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*


Changed files:
filename: scripts/snapdragon/windows/run-cli.ps1
patch: @@ -46,8 +46,8 @@ if ($null -ne $env:NDEV) {
 
 $env:ADSP_LIBRARY_PATH="$basedir\lib"
 
-& "$basedir\bin\llama-completion.exe" `
-    --no-mmap -no-cnv -m $basedir\..\..\gguf\$model `
+& "$basedir\bin\llama-cli.exe" `
+    --no-mmap -m $basedir\..\..\gguf\$model `
     --poll 1000 -t 6 --cpu-mask 0xfc --cpu-strict 1 `
     --ctx-size 8192 --ubatch-size 128 -fa on `
     -ngl 99 --device $device $cli_opts

filename: scripts/snapdragon/windows/run-completion.ps1
patch: @@ -0,0 +1,53 @@
+
+#!/usr/bin/env pwsh
+
+# Basedir on device
+$basedir=".\pkg-snapdragon"
+
+$cli_opts=$args
+
+$model="Llama-3.2-3B-Instruct-Q4_0.gguf"
+if ($null -ne $env:M) {
+    $model=$env:M
+}
+
+$device="HTP0"
+if ($null -ne $env:D) {
+    $device=$env:D
+}
+
+if ($null -ne $env:V) {
+    $env:GGML_HEXAGON_VERBOSE=$env:V
+}
+
+if ($null -ne $env:E) {
+    $env:GGML_HEXAGON_EXPERIMENTAL=$env:E
+}
+
+if ($null -ne $env:SCHED) {
+    $env:GGML_SCHED_DEBUG=$env:SCHED; $cli_opts="$cli_opts -v"
+}
+
+if ($null -ne $env:PROF) {
+    $env:GGML_HEXAGON_PROFILE=$env:PROF; $env:GGML_HEXAGON_OPSYNC=1
+}
+
+if ($null -ne $env:OPMASK) {
+    $env:GGML_HEXAGON_OPMASK=$env:OPMASK
+}
+
+if ($null -ne $env:NHVX) {
+    $env:GGML_HEXAGON_NHVX=$env:NHVX
+}
+
+if ($null -ne $env:NDEV) {
+    $env:GGML_HEXAGON_NDEV=$env:NDEV
+}
+
+$env:ADSP_LIBRARY_PATH="$basedir\lib"
+
+& "$basedir\bin\llama-completion.exe" `
+    --no-mmap -m $basedir\..\..\gguf\$model `
+    --poll 1000 -t 6 --cpu-mask 0xfc --cpu-strict 1 `
+    --ctx-size 8192 --batch-size 128 -fa on `
+    -ngl 99 -no-cnv --device $device $cli_opts
Repository: ollama/ollama
Pull request: Readme - add LlmTornado to libraries

There is already [OllamaSharp](https://github.com/awaescher/OllamaSharp) for .NET, however, business applications often need to rely on a mixture of open-weights and commercial models, hence why I created [LlmTornado](https://github.com/lofcz/LlmTornado) about a year ago. We provide an Ollama demo in our readme and have Ollama inference tests in our test suite. OllamaSharp offers a rich Ollama-specific API, we merely use the OAI-compatibility, nevertheless, I believe this could be a useful addon to the list of libraries.

Changed files:
filename: README.md
patch: @@ -481,6 +481,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [GoLamify](https://github.com/prasad89/golamify)
 - [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)
 
 ### Mobile
Repository: ollama/ollama
Pull request: Remove reference to the deleted examples folder

The documentation links the reader to an examples folder which no longer exists.

Changed files:
filename: docs/modelfile.md
patch: @@ -67,8 +67,6 @@ To use this:
 3. `ollama run choose-a-model-name`
 4. Start using the model!
 
-More examples are available in the [examples directory](../examples).
-
 To view the Modelfile of a given model, use the `ollama show --modelfile` command.
 
   ```bash
Repository: ggml-org/llama.cpp
Pull request: tools : add missing clocale include in mtmd-cli

cont #17331

Fixes #20106

Changed files:
filename: tools/mtmd/mtmd-cli.cpp
patch: @@ -13,6 +13,7 @@
 #include <vector>
 #include <limits.h>
 #include <cinttypes>
+#include <clocale>
 
 #if defined (__unix__) || (defined (__APPLE__) && defined (__MACH__))
 #include <signal.h>