helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: test-new-tests: enable adapter in deploy flow

## Summary
- export `NEXT_ENABLE_ADAPTER=1` in the `test-new-tests-deploy` workflow job
- export `NEXT_ENABLE_ADAPTER=1` in the `test-new-tests-deploy-cache-components` workflow job

## Testing
- `git diff --check`

Changed files:
filename: .github/workflows/build_and_test.yml
patch: @@ -780,7 +780,9 @@ jobs:
 
     uses: ./.github/workflows/build_reusable.yml
     with:
+      # Keep Next.js related env variables in sync with additionalEnv in next-deploy.ts
       afterBuild: |
+        export NEXT_ENABLE_ADAPTER=1
         export NEXT_E2E_TEST_TIMEOUT=240000
         export __NEXT_EXPERIMENTAL_STRICT_ROUTE_TYPES=true
         node scripts/test-new-tests.mjs \
@@ -815,6 +817,7 @@ jobs:
         export __NEXT_CACHE_COMPONENTS=true
         export __NEXT_EXPERIMENTAL_CACHED_NAVIGATIONS=true
         export __NEXT_EXPERIMENTAL_APP_NEW_SCROLL_HANDLER=true
+        export NEXT_ENABLE_ADAPTER=1
         export NEXT_EXTERNAL_TESTS_FILTERS="test/deploy-tests-manifest.json,test/cache-components-tests-manifest.json"
         export NEXT_E2E_TEST_TIMEOUT=240000
         node scripts/test-new-tests.mjs \
Repository: huggingface/transformers
Pull request: Fix tensor indexing crash in serve generate_response KV cache continuation

## What does this PR do?

Fixes a crash in `transformers serve` when the `/v1/responses` streaming endpoint attempts to reuse a KV cache from a previous request in the same conversation session.

### The bug

In `generate_response`, `inputs` is assigned the raw `input_ids` tensor on lines 1310-1313:

```python
inputs = processor.apply_chat_template(
    inputs, add_generation_prompt=True, return_tensors="pt", return_dict=True
)["input_ids"]
inputs = inputs.to(model.device)
```

Later, the KV cache continuation check incorrectly tries to index `inputs` as a dict:

```python
if inputs["input_ids"].shape[-1] > seq_len:  # TypeError: tensor can't be indexed with a string
```

This raises a `TypeError` on the second request in a conversation, since `inputs` is already a tensor, not a dictionary.

### The fix

Change `inputs["input_ids"].shape[-1]` to `inputs.shape[-1]`, matching how `generate_response_non_streaming` handles the same check (line 1632).

Fixes #44734

## Before submitting

- [x] This PR fixes a bug (non-breaking change which fixes an issue).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#start-contributing-pull-requests)?
- [x] Did you make sure to update the documentation with your changes?
  N/A - one-line bugfix, no documentation impact.
- [x] Did you write any new necessary tests?
  The existing test suite covers the serve module. This is a one-line fix to match an already-correct pattern in the non-streaming variant.

Changed files:
filename: src/transformers/cli/serve.py
patch: @@ -1328,7 +1328,7 @@ def generate_response(self, req: dict) -> Generator[str, None, None]:
         last_kv_cache = None
         if self.is_continuation(req) and not must_discard_cache:
             seq_len = self.last_kv_cache.get_seq_length()
-            if inputs["input_ids"].shape[-1] > seq_len:
+            if inputs.shape[-1] > seq_len:
                 last_kv_cache = self.last_kv_cache
 
         generation_kwargs = {
Repository: rust-lang/rust
Pull request: update zulip link in `std` documentation

#docs doesn't seem to exist anymore, so point people to `t-libs`. Also include direct link to topic since Zulip is world-viewable now.

Changed files:
filename: library/std/src/lib.rs
patch: @@ -94,8 +94,8 @@
 //! pull-requests for your suggested changes.
 //!
 //! Contributions are appreciated! If you see a part of the docs that can be
-//! improved, submit a PR, or chat with us first on [Zulip][rust-zulip]
-//! #docs.
+//! improved, submit a PR, or chat with us first on [Zulip][t-libs-zulip]
+//! #t-libs.
 //!
 //! # A Tour of The Rust Standard Library
 //!
@@ -209,7 +209,7 @@
 //! [multithreading]: thread
 //! [other]: #what-is-in-the-standard-library-documentation
 //! [primitive types]: ../book/ch03-02-data-types.html
-//! [rust-zulip]: https://rust-lang.zulipchat.com/
+//! [t-libs-zulip]: https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/
 //! [array]: prim@array
 //! [slice]: prim@slice
Repository: facebook/react
Pull request: Update changelog with latest releases


Changed files:
filename: CHANGELOG.md
patch: @@ -1,3 +1,9 @@
+## 19.2.1 (Dec 3, 2025)
+
+### React Server Components
+
+- Bring React Server Component fixes to Server Actions (@sebmarkbage [#35277](https://github.com/facebook/react/pull/35277))
+
 ## 19.2.0 (October 1st, 2025)
 
 Below is a list of all new features, APIs, and bug fixes.
@@ -71,6 +77,12 @@ Read the [React 19.2 release post](https://react.dev/blog/2025/10/01/react-19-2)
 
 - [createContainer](https://github.com/facebook/react/blob/v19.2.0/packages/react-reconciler/src/ReactFiberReconciler.js#L255-L261) and [createHydrationContainer](https://github.com/facebook/react/blob/v19.2.0/packages/react-reconciler/src/ReactFiberReconciler.js#L305-L312) had their parameter order adjusted after `on*` handlers to account for upcoming experimental APIs
 
+## 19.1.2 (Dec 3, 2025)
+
+### React Server Components
+
+- Bring React Server Component fixes to Server Actions (@sebmarkbage [#35277](https://github.com/facebook/react/pull/35277))
+
 ## 19.1.1 (July 28, 2025)
 
 ### React
@@ -123,6 +135,12 @@ An Owner Stack is a string representing the components that are directly respons
 * Exposed `registerServerReference` in client builds to handle server references in different environments. [#32534](https://github.com/facebook/react/pull/32534)
 * Added react-server-dom-parcel package which integrates Server Components with the [Parcel bundler](https://parceljs.org/) [#31725](https://github.com/facebook/react/pull/31725), [#32132](https://github.com/facebook/react/pull/32132), [#31799](https://github.com/facebook/react/pull/31799), [#32294](https://github.com/facebook/react/pull/32294), [#31741](https://github.com/facebook/react/pull/31741)
 
+## 19.0.1 (Dec 3, 2025)
+
+### React Server Components
+
+- Bring React Server Component fixes to Server Actions (@sebmarkbage [#35277](https://github.com/facebook/react/pull/35277))
+
 ## 19.0.0 (December 5, 2024)
 
 Below is a list of all new features, APIs, deprecations, and breaking changes. Read [React 19 release post](https://react.dev/blog/2024/04/25/react-19) and [React 19 upgrade guide](https://react.dev/blog/2024/04/25/react-19-upgrade-guide) for more information.
Repository: vercel/next.js
Pull request: Revert "Exclude partial fallback for deploy mode"

Reverts vercel/next.js#91163

Flag is re-landed for test teams

Changed files:
filename: test/deploy-tests-manifest.json
patch: @@ -98,7 +98,6 @@
   "rules": {
     "include": ["test/e2e/**/*.test.{t,j}s{,x}"],
     "exclude": [
-      "test/e2e/app-dir/partial-fallback-shell-upgrade/partial-fallback-shell-upgrade.test.ts",
       "test/e2e/cancel-request/stream-cancel.test.ts",
       "test/e2e/new-link-behavior/material-ui.test.ts",
       "test/e2e/react-dnd-compile/react-dnd-compile.test.ts",

filename: test/e2e/app-dir/partial-fallback-shell-upgrade/partial-fallback-shell-upgrade.test.ts
patch: @@ -1,9 +1,14 @@
 import { nextTestSetup } from 'e2e-utils'
 import { retry } from 'next-test-utils'
 
+const isAdapterTest = Boolean(process.env.NEXT_ENABLE_ADAPTER)
+
 describe('partial-fallback-shell-upgrade', () => {
   const { next, isNextDev } = nextTestSetup({
     files: __dirname,
+    // The latest changes to support this behavior on deployed infra are available in the adapter,
+    // and are not being backported to the CLI
+    skipDeployment: !isAdapterTest,
   })
 
   if (isNextDev) {
Repository: nodejs/node
Pull request: events: don't call resume after close (fix readline regression)

Fixes: https://github.com/nodejs/node/issues/60507
Regression from: https://github.com/nodejs/node/pull/58283

Since https://github.com/nodejs/node/pull/58283, readline is not compatible with `EventEmitter.on` (and readline own async iterator)
It throws on attempting to `.resume` the stream after it was closed, which was what `EventEmitter.on` was doing

Another option is to make `.resume` a noop in closed state instead of throwing

Changed files:
filename: lib/events.js
patch: @@ -1074,7 +1074,7 @@ function on(emitter, event, options = kEmptyObject) {
         const value = unconsumedEvents.shift();
         size--;
         if (paused && size < lowWatermark) {
-          emitter.resume();
+          emitter.resume(); // Can not be finished yet
           paused = false;
         }
         return PromiseResolve(createIterResult(value, false));
@@ -1191,6 +1191,7 @@ function on(emitter, event, options = kEmptyObject) {
     abortListenerDisposable?.[SymbolDispose]();
     removeAll();
     finished = true;
+    paused = false;
     const doneResult = createIterResult(undefined, true);
     while (!unconsumedPromises.isEmpty()) {
       unconsumedPromises.shift().resolve(doneResult);

filename: test/parallel/test-readline-async-iterators.js
patch: @@ -17,6 +17,7 @@ const testContents = [
   'line 1',
   'line 1\nline 2 南越国是前203年至前111年存在于岭南地区的一个国家\nline 3\ntrailing',
   'line 1\nline 2\nline 3 ends with newline\n',
+  Array(1e4).fill(0).map((_, i) => i).join('\n'), // More that 2 * highWaterMark
 ];
 
 async function testSimple() {
@@ -43,6 +44,29 @@ async function testSimple() {
   }
 }
 
+// Same as testSimple, but with Readable.from() instead of fs.createReadStream
+async function testReadableFrom() {
+  for (const fileContent of testContents) {
+    const readable = Readable.from([fileContent]);
+    const rli = readline.createInterface({
+      input: readable,
+      crlfDelay: Infinity
+    });
+
+    const iteratedLines = [];
+    for await (const k of rli) {
+      iteratedLines.push(k);
+    }
+
+    const expectedLines = fileContent.split('\n');
+    if (expectedLines[expectedLines.length - 1] === '') {
+      expectedLines.pop();
+    }
+    assert.deepStrictEqual(iteratedLines, expectedLines);
+    assert.strictEqual(iteratedLines.join(''), fileContent.replace(/\n/g, ''));
+  }
+}
+
 async function testMutual() {
   for (const fileContent of testContents) {
     fs.writeFileSync(filename, fileContent);
@@ -115,6 +139,7 @@ async function testSlowStreamForLeaks() {
 }
 
 testSimple()
+  .then(testReadableFrom)
   .then(testMutual)
   .then(testSlowStreamForLeaks)
   .then(common.mustCall());
Repository: rust-lang/rust
Pull request: Add regression test for recursive lazy type alias normalization ICE

Regression test for rust-lang/rust#152633.

The normalization ICE with recursive lazy_type_alias + min_generic_const_args was fixed by rust-lang/rust#152040 but didn't get a test. Compiler now reports E0275 instead of crashing.

Closes rust-lang/rust#152633

Changed files:
filename: tests/ui/type-alias/recursive-lazy-type-alias-ice-152633.rs
patch: @@ -0,0 +1,14 @@
+//! Ensure a self-referencing lazy type alias with `min_generic_const_args`
+//! doesn't ICE during normalization.
+//!
+//! Regression test for <https://github.com/rust-lang/rust/issues/152633>.
+
+#![feature(lazy_type_alias)]
+#![feature(min_generic_const_args)]
+
+trait Trait {
+    type const ASSOC: ();
+}
+type Arr2 = [usize; <Arr2 as Trait>::ASSOC]; //~ ERROR E0275
+
+fn main() {}

filename: tests/ui/type-alias/recursive-lazy-type-alias-ice-152633.stderr
patch: @@ -0,0 +1,11 @@
+error[E0275]: overflow normalizing the type alias `Arr2`
+  --> $DIR/recursive-lazy-type-alias-ice-152633.rs:12:1
+   |
+LL | type Arr2 = [usize; <Arr2 as Trait>::ASSOC];
+   | ^^^^^^^^^
+   |
+   = note: in case this is a recursive type alias, consider using a struct, enum, or union instead
+
+error: aborting due to 1 previous error
+
+For more information about this error, try `rustc --explain E0275`.
Repository: nodejs/node
Pull request: build: fix misplaced comma in ldflags

During my build of Node.js, the linker (lld) threw the following error:

```
error: unsupported linker arg: /root/node-v24.12.0/out/Release/obj.target/deps/openssl/libopenssl.a
```

After investigation, I found that a comma was misplaced inside the quotes. It should be outside the string to correctly separate the list elements. This PR corrects the syntax.

Changed files:
filename: node.gypi
patch: @@ -412,7 +412,7 @@
               'conditions': [
                 ['OS in "linux freebsd openharmony" and node_shared=="false"', {
                   'ldflags': [
-                    '-Wl,--whole-archive,'
+                    '-Wl,--whole-archive',
                       '<(obj_dir)/deps/openssl/<(openssl_product)',
                     '-Wl,--no-whole-archive',
                   ],
Repository: ollama/ollama
Pull request: scripts: fix macOS auto-update signature verification failure

Add --norsrc flag to ditto commands when creating Ollama-darwin.zip to exclude AppleDouble resource fork files (._* files) from the archive.

The mlx.metallib file has extended attributes, which causes ditto to include a ._mlx.metallib AppleDouble file in the zip. Since this file is not part of the code signature seal, macOS rejects the bundle during auto-update verification with:

  "a sealed resource is missing or invalid"
  "file added: .../._mlx.metallib"

The --norsrc flag prevents ditto from preserving resource forks and extended attributes, ensuring only signed files are included in the release archive.

Changed files:
filename: scripts/build_darwin.sh
patch: @@ -179,15 +179,15 @@ _build_macapp() {
     fi
 
     rm -f dist/Ollama-darwin.zip
-    ditto -c -k --keepParent dist/Ollama.app dist/Ollama-darwin.zip
+    ditto -c -k --norsrc --keepParent dist/Ollama.app dist/Ollama-darwin.zip
     (cd dist/Ollama.app/Contents/Resources/; tar -cf - ollama ollama-mlx *.so *.dylib *.metallib 2>/dev/null) | gzip -9vc > dist/ollama-darwin.tgz
 
     # Notarize and Staple
     if [ -n "$APPLE_IDENTITY" ]; then
         $(xcrun -f notarytool) submit dist/Ollama-darwin.zip --wait --timeout 20m --apple-id "$APPLE_ID" --password "$APPLE_PASSWORD" --team-id "$APPLE_TEAM_ID"
         rm -f dist/Ollama-darwin.zip
         $(xcrun -f stapler) staple dist/Ollama.app
-        ditto -c -k --keepParent dist/Ollama.app dist/Ollama-darwin.zip
+        ditto -c -k --norsrc --keepParent dist/Ollama.app dist/Ollama-darwin.zip
 
         rm -f dist/Ollama.dmg
Repository: facebook/react
Pull request: [eprh] Allow compiler rules to be opted-in but not in the preset


Follow up to #34649. This adds the compiler rules back so they can be opted-in 6.1.0, but aren't included in the presets as that would be a breaking change.


Changed files:
filename: packages/eslint-plugin-react-hooks/src/index.ts
patch: @@ -7,12 +7,16 @@
 import type {Linter, Rule} from 'eslint';
 
 import ExhaustiveDeps from './rules/ExhaustiveDeps';
+import {allRules} from './shared/ReactCompiler';
 import RulesOfHooks from './rules/RulesOfHooks';
 
 // All rules
 const rules = {
   'exhaustive-deps': ExhaustiveDeps,
   'rules-of-hooks': RulesOfHooks,
+  ...Object.fromEntries(
+    Object.entries(allRules).map(([name, config]) => [name, config.rule]),
+  ),
 } satisfies Record<string, Rule.RuleModule>;
 
 // Config rules
Repository: rust-lang/rust
Pull request: Fix ambiguous parsing in bootstrap.py

Noticed this while trying to produce rustdoc-json for std and saw JSON output from the bootstrap.py build of bootstrap's Rust code. This is technically a breaking change, but I think the fix should be simple and arguably an improvement in future compatibility if/when the flag set changes.

Changed files:
filename: src/bootstrap/bootstrap.py
patch: @@ -1259,7 +1259,12 @@ def check_vendored_status(self):
 
 def parse_args(args):
     """Parse the command line arguments that the python script needs."""
-    parser = argparse.ArgumentParser(add_help=False)
+
+    # Pass allow_abbrev=False to remove support for inexact matches (e.g.,
+    # `--json` turning on `--json-output`). The argument list here is partial,
+    # most flags are matched in the Rust bootstrap code. This prevents the the
+    # default ambiguity checks in argparse from functioning correctly.
+    parser = argparse.ArgumentParser(add_help=False, allow_abbrev=False)
     parser.add_argument("-h", "--help", action="store_true")
     parser.add_argument("--config")
     parser.add_argument("--build-dir")

filename: src/bootstrap/src/utils/change_tracker.rs
patch: @@ -616,4 +616,9 @@ pub const CONFIG_CHANGE_HISTORY: &[ChangeInfo] = &[
         severity: ChangeSeverity::Warning,
         summary: "`x.py test --no-doc` is renamed to `--all-targets`. Additionally `--tests` is added which only executes unit and integration tests.",
     },
+    ChangeInfo {
+        change_id: 154508,
+        severity: ChangeSeverity::Info,
+        summary: "`x.py` stopped accepting partial argument names. Use full names to avoid errors.",
+    },
 ];
Repository: ollama/ollama
Pull request: Revert "Documentation edits made through Mintlify web editor"

This reverts commit c6d4c0c7f2d38f4bca684db40de3716f39aa8fcc.

Merge after 0.14.0 ships for the updated Linux documentation.

Changed files:
filename: docs/linux.mdx
patch: @@ -1,5 +1,5 @@
 ---
-title: "Linux"
+title: Linux
 ---
 
 ## Install
@@ -13,14 +13,15 @@ curl -fsSL https://ollama.com/install.sh | sh
 ## Manual install
 
 <Note>
-  If you are upgrading from a prior version, you should remove the old libraries with `sudo rm -rf /usr/lib/ollama` first.
+  If you are upgrading from a prior version, you should remove the old libraries
+  with `sudo rm -rf /usr/lib/ollama` first.
 </Note>
 
 Download and extract the package:
 
 ```shell
-curl -fsSL https://ollama.com/download/ollama-linux-amd64.tgz \
-    | sudo tar zx -C /usr
+curl -fsSL https://ollama.com/download/ollama-linux-amd64.tar.zst \
+    | sudo tar x -C /usr
 ```
 
 Start Ollama:
@@ -40,17 +41,17 @@ ollama -v
 If you have an AMD GPU, also download and extract the additional ROCm package:
 
 ```shell
-curl -fsSL https://ollama.com/download/ollama-linux-amd64-rocm.tgz \
-    | sudo tar zx -C /usr
+curl -fsSL https://ollama.com/download/ollama-linux-amd64-rocm.tar.zst \
+    | sudo tar x -C /usr
 ```
 
 ### ARM64 install
 
 Download and extract the ARM64-specific package:
 
 ```shell
-curl -fsSL https://ollama.com/download/ollama-linux-arm64.tgz \
-    | sudo tar zx -C /usr
+curl -fsSL https://ollama.com/download/ollama-linux-arm64.tar.zst \
+    | sudo tar x -C /usr
 ```
 
 ### Adding Ollama as a startup service (recommended)
@@ -112,7 +113,11 @@ sudo systemctl status ollama
 ```
 
 <Note>
-  While AMD has contributed the `amdgpu` driver upstream to the official linux kernel source, the version is older and may not support all ROCm features. We recommend you install the latest driver from https://www.amd.com/en/support/linux-drivers for best support of your Radeon GPU.
+  While AMD has contributed the `amdgpu` driver upstream to the official linux
+  kernel source, the version is older and may not support all ROCm features. We
+  recommend you install the latest driver from
+  https://www.amd.com/en/support/linux-drivers for best support of your Radeon
+  GPU.
 </Note>
 
 ## Customizing
@@ -141,8 +146,8 @@ curl -fsSL https://ollama.com/install.sh | sh
 Or by re-downloading Ollama:
 
 ```shell
-curl -fsSL https://ollama.com/download/ollama-linux-amd64.tgz \
-    | sudo tar zx -C /usr
+curl -fsSL https://ollama.com/download/ollama-linux-amd64.tar.zst \
+    | sudo tar x -C /usr
 ```
 
 ## Installing specific versions
@@ -191,4 +196,4 @@ Remove the downloaded models and Ollama service user and group:
 sudo userdel ollama
 sudo groupdel ollama
 sudo rm -r /usr/share/ollama
-```
\ No newline at end of file
+```
Repository: nodejs/node
Pull request: doc: clarify that any truthy value of `shell` is part of DEP0190

The current wording makes it sound like passing a string would not be a problem, remove the mention of `true` in the title and add an example with a string

<!--
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: doc/api/deprecations.md
patch: @@ -4175,7 +4175,7 @@ Type: Documentation-only
 `process.features.tls_alpn`, `process.features.tls_ocsp`, and `process.features.tls_sni` are
 deprecated, as their values are guaranteed to be identical to that of `process.features.tls`.
 
-### DEP0190: Passing `args` to `node:child_process` `execFile`/`spawn` with `shell` option `true`
+### DEP0190: Passing `args` to `node:child_process` `execFile`/`spawn` with `shell` option
 
 <!-- YAML
 changes:
@@ -4192,7 +4192,8 @@ changes:
 Type: Runtime
 
 When an `args` array is passed to [`child_process.execFile`][] or [`child_process.spawn`][] with the option
-`{ shell: true }`, the values are not escaped, only space-separated, which can lead to shell injection.
+`{ shell: true }` or `{ shell: '/path/to/shell' }`, the values are not escaped, only space-separated,
+which can lead to shell injection.
 
 ### DEP0191: `repl.builtinModules`
Repository: ollama/ollama
Pull request: mlx: bundle openblas dependency

This should fix the error:
```
    imagegen_test.go:64: failed to generate image: unexpected status code 500: {"error":{"message":"image runner failed: /tmp/daniel_ollama_test/bin/ollama-mlx: error while loading shared libraries: libopenblas.so.0: cannot open shared object file: No such file or directory (exit: exit status 127)"}}
--- FAIL: TestImageGeneration (5.77s)
    --- FAIL: TestImageGeneration/jmorgan/z-image-turbo->llama3.2-vision (5.77s)
```

Changed files:
filename: CMakeLists.txt
patch: @@ -190,7 +190,7 @@ if(MLX_ENGINE)
     install(TARGETS mlx mlxc
         RUNTIME_DEPENDENCIES
             DIRECTORIES ${CUDAToolkit_BIN_DIR} ${CUDAToolkit_BIN_DIR}/x64 ${CUDAToolkit_LIBRARY_DIR}
-            PRE_INCLUDE_REGEXES cublas cublasLt cudart nvrtc cudnn nccl
+            PRE_INCLUDE_REGEXES cublas cublasLt cudart nvrtc nvrtc-builtins cudnn nccl openblas gfortran
             PRE_EXCLUDE_REGEXES ".*"
         RUNTIME DESTINATION ${OLLAMA_INSTALL_DIR} COMPONENT MLX
         LIBRARY DESTINATION ${OLLAMA_INSTALL_DIR} COMPONENT MLX