helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: Windows ARM build

Skip cmake, and note it's unused in the developer docs.

Changed files:
filename: docs/development.md
patch: @@ -69,7 +69,7 @@ go run . serve
 
 ## Windows (ARM)
 
-Windows ARM does not support additional acceleration libraries at this time.
+Windows ARM does not support additional acceleration libraries at this time.  Do not use cmake, simply `go run` or `go build`.
 
 ## Linux
 

filename: scripts/build_windows.ps1
patch: @@ -26,9 +26,6 @@ function checkEnv() {
         $MSVC_INSTALL=(Get-CimInstance MSFT_VSInstance -Namespace root/cimv2/vs)[0].InstallLocation
         $env:VCToolsRedistDir=(get-item "${MSVC_INSTALL}\VC\Redist\MSVC\*")[0]
     }
-    if (-Not (get-command -ErrorAction silent ninja)) {
-        $script:NINJA_DIR=(gci -path (Get-CimInstance MSFT_VSInstance -Namespace root/cimv2/vs)[0].InstallLocation -r -fi ninja.exe) | split-path -parent
-    }
     # Locate CUDA versions
     # Note: this assumes every version found will be built
     $cudaList=(get-item "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v*\bin\" -ea 'silentlycontinue')
@@ -83,7 +80,7 @@ function checkEnv() {
 
 
 function buildOllama() {
-    if ($null -eq ${env:OLLAMA_SKIP_GENERATE}) {
+    if ($script:ARCH -ne "arm64") {
         Remove-Item -ea 0 -recurse -force -path "${script:SRC_DIR}\dist\windows-${script:ARCH}"
         New-Item "${script:SRC_DIR}\dist\windows-${script:ARCH}\lib\ollama\" -ItemType Directory -ea 0
 
@@ -122,8 +119,9 @@ function buildOllama() {
         }
         if ($env:HIP_PATH) {
             write-host "Building ROCm backend libraries"
-            if ($null -ne $script:NINJA_DIR) {
-                $env:PATH="$script:NINJA_DIR;$env:PATH"
+            if (-Not (get-command -ErrorAction silent ninja)) {
+                $NINJA_DIR=(gci -path (Get-CimInstance MSFT_VSInstance -Namespace root/cimv2/vs)[0].InstallLocation -r -fi ninja.exe) | split-path -parent
+                $env:PATH="$NINJA_DIR;$env:PATH"
             }
             $env:HIPCXX="${env:HIP_PATH}\bin\clang++.exe"
             $env:HIP_PLATFORM="amd"
@@ -138,8 +136,6 @@ function buildOllama() {
             & cmake --install build --component "HIP" --strip
             if ($LASTEXITCODE -ne 0) { exit($LASTEXITCODE)}
         }
-    } else {
-        write-host "Skipping generate step with OLLAMA_SKIP_GENERATE set"
     }
     write-host "Building ollama CLI"
     & go build -trimpath -ldflags "-s -w -X=github.com/ollama/ollama/version.Version=$script:VERSION -X=github.com/ollama/ollama/server.mode=release" .
Repository: vuejs/vue
Pull request: fix #8832: duplicate keys detected not warned

<!--
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/patch.js
patch: @@ -550,6 +550,9 @@ export function createPatchFunction (backend) {
       if (isDef(oldCh) && isDef(ch)) {
         if (oldCh !== ch) updateChildren(elm, oldCh, ch, insertedVnodeQueue, removeOnly)
       } else if (isDef(ch)) {
+        if (process.env.NODE_ENV !== 'production') {
+          checkDuplicateKeys(ch)
+        }
         if (isDef(oldVnode.text)) nodeOps.setTextContent(elm, '')
         addVnodes(elm, null, ch, 0, ch.length - 1, insertedVnodeQueue)
       } else if (isDef(oldCh)) {

filename: test/unit/modules/vdom/patch/children.spec.js
patch: @@ -530,4 +530,16 @@ describe('vdom patch: children', () => {
     patch(vnode2, vnode3)
     expect(`Duplicate keys detected: 'b'`).toHaveBeenWarned()
   })
+
+  it('should warn with duplicate keys: patchVnode with empty oldVnode', () => {
+    function makeNode (key) {
+      return new VNode('li', { key: key })
+    }
+
+    const vnode1 = new VNode('div')
+    const vnode2 = new VNode('div', undefined, ['1', '2', '3', '4', '4'].map(makeNode))
+
+    patch(vnode1, vnode2)
+    expect(`Duplicate keys detected: '4'`).toHaveBeenWarned()
+  })
 })
Repository: ollama/ollama
Pull request: .github/workflows: swap order of go test and golangci-lint

The linter is secondary to the tests, so it should run after the tests, exposing test failures faster.

Changed files:
filename: .github/workflows/test.yaml
patch: @@ -190,28 +190,27 @@ jobs:
 
           go-version-file: go.mod
 
-      # TODO(bmizerany): replace this heavy tool with just the
-      # tools/checks/binaries we want and then make them all run in parallel
-      # across jobs, not on a single tiny vm on Github Actions.
-      - uses: golangci/golangci-lint-action@v6
-        with:
-          args: --timeout 10m0s -v
-
-      - name: go test
-        # Do not skip tests in the face of linter errors, or 'go mod tidy'
-        # checks, which are secondary to the tests. Tests trump linters.
-        if: always()
-        run: go test -count=1 -benchtime=1x ./...
-
       # It is tempting to run this in a platform independent way, but the past
       # shows this codebase will see introductions of platform specific code
       # generation, and so we need to check this per platform to ensure we
       # don't abuse go generate on specific platforms.
       - name: check that 'go generate' is clean
+        if: always()
         run: |
           go generate ./...
           git diff --name-only --exit-code || (echo "Please run 'go generate ./...'." && exit 1)
 
+      - name: go test
+        if: always()
+        run: go test -count=1 -benchtime=1x ./...
+
+      # TODO(bmizerany): replace this heavy tool with just the
+      # tools/checks/binaries we want and then make them all run in parallel
+      # across jobs, not on a single tiny vm on Github Actions.
+      - uses: golangci/golangci-lint-action@v6
+        with:
+          args: --timeout 10m0s -v
+
       - name: cache save
         # Always save the cache, even if the job fails. The artifacts produced
         # during the building of test binaries are not all for naught. They can
Repository: facebook/react
Pull request: enableViewTransition in www


Changed files:
filename: packages/shared/forks/ReactFeatureFlags.test-renderer.www.js
patch: @@ -78,7 +78,7 @@ export const enableHydrationLaneScheduling = true;
 export const enableYieldingBeforePassive = false;
 
 export const enableThrottledScheduling = false;
-export const enableViewTransition = false;
+export const enableViewTransition = true;
 export const enableGestureTransition = false;
 export const enableFastAddPropertiesInDiffing = false;
 export const enableLazyPublicInstanceInFabric = false;

filename: packages/shared/forks/ReactFeatureFlags.www-dynamic.js
patch: @@ -36,7 +36,6 @@ export const enableInfiniteRenderLoopDetection = __VARIANT__;
 
 export const enableFastAddPropertiesInDiffing = __VARIANT__;
 export const enableLazyPublicInstanceInFabric = false;
-export const enableViewTransition = __VARIANT__;
 export const enableComponentPerformanceTrack = __VARIANT__;
 export const enableScrollEndPolyfill = __VARIANT__;
 export const enableFragmentRefs = __VARIANT__;

filename: packages/shared/forks/ReactFeatureFlags.www.js
patch: @@ -34,7 +34,6 @@ export const {
   syncLaneExpirationMs,
   transitionLaneExpirationMs,
   enableFastAddPropertiesInDiffing,
-  enableViewTransition,
   enableComponentPerformanceTrack,
   enableScrollEndPolyfill,
   enableFragmentRefs,
@@ -118,6 +117,7 @@ export const enableFizzBlockingRender = true;
 export const enableSrcObject = false;
 export const enableHydrationChangeEvent = false;
 export const enableDefaultTransitionIndicator = false;
+export const enableViewTransition = true;
 
 export const ownerStackLimit = 1e4;
Repository: ggml-org/llama.cpp
Pull request: ci: disable coopmat on ubuntu-24-cmake-vulkan job

There's some issue with the new barrier in the coopmat llvmpipe driver. But coopmat support in llvmpipe isn't really needed for it and wasn't around when the CI was set up anyways, so disable it to work around the problem.

Changed files:
filename: .github/workflows/build.yml
patch: @@ -469,6 +469,7 @@ jobs:
           cd build
           export GGML_VK_VISIBLE_DEVICES=0
           export GGML_VK_DISABLE_F16=1
+          export GGML_VK_DISABLE_COOPMAT=1
           # This is using llvmpipe and runs slower than other backends
           ctest -L main --verbose --timeout 4800
Repository: nodejs/node
Pull request: doc: note corepack package removal in distribution doc

## Situation

The Node.js Technical Steering Committee completed a [vote](https://github.com/nodejs/TSC/pull/1697#issuecomment-2737093616) on Mar 19, 2025 which resulted in the strategy decision:

> Phase out later: stop distributing Corepack (i.e. the distribution will no longer contain a corepack executable) on future (i.e. 25+) release lines of Node.js – existing release lines as well as the very next (i.e. 24.x) will keep it as experimental.

This is reflected in https://nodejs.org/docs/latest-v24.x/api/corepack.html, which states

> Corepack will no longer be distributed starting with Node.js v25.

This distribution strategy change is however not yet mentioned in the [Node.js Distribution Policy document](https://github.com/nodejs/node/blob/main/doc/contributing/distribution.md).

## Change

Add a corresponding comment to [Node.js Distribution Policy document](https://github.com/nodejs/node/blob/main/doc/contributing/distribution.md) about the removal of the [corepack](https://github.com/nodejs/corepack) module starting with Node.js v25.


Changed files:
filename: doc/contributing/distribution.md
patch: @@ -25,3 +25,7 @@ only as a semver-major change, unless the related feature or project is
 documented as experimental. In addition, Node.js includes external projects as
 internal dependencies. These may be replaced or removed at any time, provided
 that doing so is not a breaking change.
+
+## History
+
+* [corepack](https://github.com/nodejs/corepack) was added in Node.js v14.9.0 and v16.9.0. It is no longer distributed as of Node.js v25.0.0.
Repository: vercel/next.js
Pull request: fix: make RedirectType constant properties literal types

### What?

Fixed TypeScript error where `RedirectType.replace` and `RedirectType.push` were typed as `string` instead of literal types, causing compilation errors when used with `redirect()`.

### Why?

`RedirectType` constant properties weren't properly typed as literal types, causing TypeScript to see them as generic `string` values instead of the expected `'push' | 'replace'` union.

### How?

- Added `as const` to `RedirectType` properties in `packages/next/src/client/components/navigation.react-server.ts`.

Fixes #88627

Changed files:
filename: packages/next/src/client/components/navigation.react-server.ts
patch: @@ -16,4 +16,4 @@ export { ReadonlyURLSearchParams }
 export const RedirectType = {
   push: 'push',
   replace: 'replace',
-}
+} as const

filename: test/integration/app-types/src/app/type-checks/redirect/page.tsx
patch: @@ -1,4 +1,4 @@
-import { redirect, permanentRedirect } from 'next/navigation'
+import { redirect, permanentRedirect, RedirectType } from 'next/navigation'
 import type { Route } from 'next'
 
 export default function Page() {
@@ -21,6 +21,11 @@ export default function Page() {
     permanentRedirect('/blog/a/b')
     permanentRedirect(`/dashboard/${'123'}`)
     permanentRedirect('/external' as Route)
+
+    // RedirectType should be correctly typed as literal types:
+    redirect('/dashboard/another', RedirectType.replace)
+    redirect('/about', RedirectType.push)
+    permanentRedirect('/dashboard/user', RedirectType.replace)
   }
 
   return <div onClick={testRedirect} />
Repository: ollama/ollama
Pull request: Update README.md - add Nichey

Hello– releasing Nichey today, which integrates with Ollama. I also wrote an [example](https://github.com/goodreasonai/nichey/blob/main/docs/examples/ollama.py) in my repo on how to use Ollama with the project.

Changed files:
filename: README.md
patch: @@ -502,6 +502,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [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) (OpenAI-compatible TypeScript SDK for any LLM provider)
+- [Nichey](https://github.com/goodreasonai/nichey) is a Python package for generating custom wikis for your research topic
 
 ### Mobile
Repository: vuejs/vue
Pull request: fix(#8730): Improve error reporting

<!--
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
- [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:**
We can find this error at compile time.


Changed files:
filename: src/compiler/parser/index.js
patch: @@ -331,8 +331,20 @@ export function processElement (element: ASTElement, options: CompilerOptions) {
 function processKey (el) {
   const exp = getBindingAttr(el, 'key')
   if (exp) {
-    if (process.env.NODE_ENV !== 'production' && el.tag === 'template') {
-      warn(`<template> cannot be keyed. Place the key on real elements instead.`)
+    if (process.env.NODE_ENV !== 'production') {
+      if (el.tag === 'template') {
+        warn(`<template> cannot be keyed. Place the key on real elements instead.`)
+      }
+      if (el.for) {
+        const iterator = el.iterator2 || el.iterator1
+        const parent = el.parent
+        if (iterator && iterator === exp && parent && parent.tag === 'transition-group') {
+          warn(
+            `Do not use v-for index as key on <transtion-group> children, ` +
+            `this is the same as not using keys.`
+          )
+        }
+      }
     }
     el.key = exp
   }

filename: test/unit/modules/compiler/parser.spec.js
patch: @@ -242,6 +242,17 @@ describe('parser', () => {
     expect('<template> cannot be keyed').toHaveBeenWarned()
   })
 
+  it('warn the child of the <transition-group> component has sequential index', () => {
+    parse(`
+      <div>
+        <transition-group>
+          <i v-for="(o, i) of arr" :key="i"></i>
+        </transition-group>
+      </div>
+    `, baseOptions)
+    expect('Do not use v-for index as key on <transtion-group> children').toHaveBeenWarned()
+  })
+
   it('v-pre directive', () => {
     const ast = parse('<div v-pre id="message1"><p>{{msg}}</p></div>', baseOptions)
     expect(ast.pre).toBe(true)
Repository: ollama/ollama
Pull request: Add cuda Blackwell architecture for v12


Changed files:
filename: CMakePresets.json
patch: @@ -21,14 +21,14 @@
       "name": "CUDA 11",
       "inherits": [ "CUDA" ],
       "cacheVariables": {
-        "CMAKE_CUDA_ARCHITECTURES": "50;52;53;60;61;62;70;72;75;80;86"
+        "CMAKE_CUDA_ARCHITECTURES": "50;52;53;60;61;70;75;80;86"
       }
     },
     {
       "name": "CUDA 12",
       "inherits": [ "CUDA" ],
       "cacheVariables": {
-        "CMAKE_CUDA_ARCHITECTURES": "50;52;53;60;61;62;70;72;75;80;86;87;89;90;90a"
+        "CMAKE_CUDA_ARCHITECTURES": "50;60;61;70;75;80;86;87;89;90;90a;100"
       }
     },
     {

filename: scripts/build_windows.ps1
patch: @@ -222,13 +222,26 @@ function buildInstaller() {
 
 function distZip() {
     if (Test-Path -Path "${script:SRC_DIR}\dist\windows-amd64") {
+        if (Test-Path -Path "${script:SRC_DIR}\dist\windows-amd64\lib\ollama\rocm") {
+            write-host "Generating stand-alone distribution zip file ${script:SRC_DIR}\dist\ollama-windows-amd64-rocm.zip"
+            # Temporarily adjust paths so we can retain the same directory structure
+            Remove-Item -ea 0 -r "${script:SRC_DIR}\dist\windows-amd64-rocm"
+            mkdir -Force -path "${script:SRC_DIR}\dist\windows-amd64-rocm\lib\ollama"
+            Write-Output "Extract this ROCm zip file to the same location where you extracted ollama-windows-amd64.zip" > "${script:SRC_DIR}\dist\windows-amd64-rocm\README.txt"
+            Move-Item -path "${script:SRC_DIR}\dist\windows-amd64\lib\ollama\rocm" -destination "${script:SRC_DIR}\dist\windows-amd64-rocm\lib\ollama"
+            Compress-Archive -CompressionLevel Optimal -Path "${script:SRC_DIR}\dist\windows-amd64-rocm\*" -DestinationPath "${script:SRC_DIR}\dist\ollama-windows-amd64-rocm.zip" -Force
+        }
+
         write-host "Generating stand-alone distribution zip file ${script:SRC_DIR}\dist\ollama-windows-amd64.zip"
-        Compress-Archive -Path "${script:SRC_DIR}\dist\windows-amd64\*" -DestinationPath "${script:SRC_DIR}\dist\ollama-windows-amd64.zip" -Force
+        Compress-Archive -CompressionLevel Optimal -Path "${script:SRC_DIR}\dist\windows-amd64\*" -DestinationPath "${script:SRC_DIR}\dist\ollama-windows-amd64.zip" -Force
+        if (Test-Path -Path "${script:SRC_DIR}\dist\windows-amd64-rocm") {
+            Move-Item -destination "${script:SRC_DIR}\dist\windows-amd64\lib\ollama\rocm" -path "${script:SRC_DIR}\dist\windows-amd64-rocm\lib\ollama"
+        }
     }
 
     if (Test-Path -Path "${script:SRC_DIR}\dist\windows-arm64") {
         write-host "Generating stand-alone distribution zip file ${script:SRC_DIR}\dist\ollama-windows-arm64.zip"
-        Compress-Archive -Path "${script:SRC_DIR}\dist\windows-arm64\*" -DestinationPath "${script:SRC_DIR}\dist\ollama-windows-arm64.zip" -Force
+        Compress-Archive -CompressionLevel Optimal -Path "${script:SRC_DIR}\dist\windows-arm64\*" -DestinationPath "${script:SRC_DIR}\dist\ollama-windows-arm64.zip" -Force
     }
 }
Repository: nodejs/node
Pull request: doc: document timeout option for tls.connect()

Fixes #61075

This PR documents the `timeout` option supported by `tls.connect()` since
v11.8.0 / v10.16.0 and fixes misleading wording suggesting it comes from
`socket.connect()`. The option is inherited from `net.createConnection()`
and is equivalent to calling `socket.setTimeout()`.


Changed files:
filename: doc/api/tls.md
patch: @@ -1730,6 +1730,9 @@ changes:
     **Default:** `1024`.
   * `highWaterMark` {number} Consistent with the readable stream `highWaterMark` parameter.
     **Default:** `16 * 1024`.
+  * `timeout`: {number} If set and if a socket is created internally, will call
+    [`socket.setTimeout(timeout)`][] after the socket is created, but before it
+    starts the connection.
   * `secureContext`: TLS context object created with
     [`tls.createSecureContext()`][]. If a `secureContext` is _not_ provided, one
     will be created by passing the entire `options` object to
@@ -2479,6 +2482,7 @@ added: v0.11.3
 [`server.listen()`]: net.md#serverlisten
 [`server.setTicketKeys()`]: #serversetticketkeyskeys
 [`socket.connect()`]: net.md#socketconnectoptions-connectlistener
+[`socket.setTimeout(timeout)`]: net.md#socketsettimeouttimeout-callback
 [`tls.DEFAULT_ECDH_CURVE`]: #tlsdefault_ecdh_curve
 [`tls.DEFAULT_MAX_VERSION`]: #tlsdefault_max_version
 [`tls.DEFAULT_MIN_VERSION`]: #tlsdefault_min_version
Repository: vercel/next.js
Pull request: Turbopack: use bugs.nextjs.org for Turbopack panic error reports

Update the bug report link to use the new bugs.nextjs.org service instead of the direct GitHub discussions URL. Also shares more code when handling terminals that don't support links.

Test Plan: Added a deliberate panic to a turbotask, verified the link.


Changed files:
filename: crates/napi/src/next_api/turbopack_ctx.rs
patch: @@ -359,27 +359,22 @@ pub fn log_internal_error_and_inform(internal_error: &anyhow::Error) {
         env!("VERGEN_GIT_DESCRIBE"),
         env!("NEXTJS_VERSION")
     );
-    let new_discussion_url = if supports_hyperlinks::supports_hyperlinks() {
-        "clicking here.".hyperlink(
-            format!(
-                "https://github.com/vercel/next.js/discussions/new?category=turbopack-error-report&title={}&body={}&labels=Turbopack,Turbopack%20Panic%20Backtrace",
-                &urlencoding::encode(&title),
-                &urlencoding::encode(&format!("{}\n\nError message:\n```\n{}\n```", &version_str, &internal_error_str))
-            )
-        )
+    let bug_report_url = format!(
+        "https://bugs.nextjs.org/search?category=turbopack-error-report&title={}&body={}&labels=Turbopack,Turbopack%20Panic%20Backtrace",
+        &urlencoding::encode(&title),
+        &urlencoding::encode(&format!("{}\n\nError message:\n```\n{}\n```", &version_str, &internal_error_str))
+    );
+    let bug_report_message = if supports_hyperlinks::supports_hyperlinks() {
+        "clicking here.".hyperlink(&bug_report_url)
     } else {
-        format!(
-            "clicking here: https://github.com/vercel/next.js/discussions/new?category=turbopack-error-report&title={}&body={}&labels=Turbopack,Turbopack%20Panic%20Backtrace",
-            &urlencoding::encode(&title),
-            &urlencoding::encode(&format!("{}\n\nError message:\n```\n{}\n```", &version_str, &title))
-        )
+        format!("clicking here: {}", bug_report_url)
     };
 
     eprintln!(
         "\n-----\n{}: An unexpected Turbopack error occurred. A panic log has been written to \
          {}.\n\nTo help make Turbopack better, report this error by {}\n-----\n",
         "FATAL".red().bold(),
         PANIC_LOG.to_string_lossy(),
-        &new_discussion_url
+        &bug_report_message
     );
 }