helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: Delete suppressWarning in OSS

I'm pretty sure this is completely unnecessary even in www and RN because it's only useful if you use the mock scheduler which typically only we do in our own tests. But all our tests pass so unless www/RN does something with it, I don't think this is used.

Also remove unnecessary `__DEV__` check. If it gets pulled in prod, we'd want to know about it.

Changed files:
filename: packages/shared/consoleWithStackDev.js
patch: @@ -8,11 +8,8 @@
 import ReactSharedInternals from 'shared/ReactSharedInternals';
 import {enableOwnerStacks} from 'shared/ReactFeatureFlags';
 
-let suppressWarning = false;
 export function setSuppressWarning(newSuppressWarning) {
-  if (__DEV__) {
-    suppressWarning = newSuppressWarning;
-  }
+  // TODO: Noop. Delete.
 }
 
 // In DEV, calls to console.warn and console.error get replaced
@@ -22,19 +19,11 @@ export function setSuppressWarning(newSuppressWarning) {
 // they are left as they are instead.
 
 export function warn(format, ...args) {
-  if (__DEV__) {
-    if (!suppressWarning) {
-      printWarning('warn', format, args, new Error('react-stack-top-frame'));
-    }
-  }
+  printWarning('warn', format, args, new Error('react-stack-top-frame'));
 }
 
 export function error(format, ...args) {
-  if (__DEV__) {
-    if (!suppressWarning) {
-      printWarning('error', format, args, new Error('react-stack-top-frame'));
-    }
-  }
+  printWarning('error', format, args, new Error('react-stack-top-frame'));
 }
 
 // eslint-disable-next-line react-internal/no-production-logging
Repository: ollama/ollama
Pull request: Omit build date from gzip headers

See https://reproducible-builds.org/ for why this is good.

This patch was done while working on reproducible builds for openSUSE.

Changed files:
filename: llm/generate/gen_common.sh
patch: @@ -101,7 +101,7 @@ compress_libs() {
     pids=""
     rm -rf ${BUILD_DIR}/lib/*.${LIB_EXT}*.gz
     for lib in ${BUILD_DIR}/lib/*.${LIB_EXT}* ; do
-        gzip --best -f ${lib} &
+        gzip -n --best -f ${lib} &
         pids+=" $!"
     done
     echo
Repository: denoland/deno
Pull request: fix(ext/node): add `threadName` to worker_threads module

## Summary

Adds the `threadName` export and `Worker.threadName` getter to the worker_threads module for Node.js compatibility.

- `threadName` module export: returns the name of the current thread (empty string for main thread, worker's name inside a worker)
- `Worker.threadName` getter: returns the worker's name while running, `null` after the worker has exited

## Test plan

- [x] `cargo test --test node_compat parallel -- --filter test-worker-thread-name`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Changed files:
filename: ext/node/polyfills/worker_threads.ts
patch: @@ -237,6 +237,7 @@ class NodeWorker extends EventEmitter {
       workerData: options?.workerData,
       environmentData: environmentData,
       env: env_,
+      name: this.#name,
       isEval: !!options?.eval,
       isWorkerThread: true,
     }, options?.transferList ?? []);
@@ -481,6 +482,14 @@ class NodeWorker extends EventEmitter {
     return PromiseResolve({ user, system });
   }
 
+  // https://nodejs.org/api/worker_threads.html#workerthreadname
+  get threadName(): string | null {
+    if (this.#exited) {
+      return null;
+    }
+    return this.#name;
+  }
+
   readonly getHeapSnapshot = () =>
     notImplemented("Worker.prototype.getHeapSnapshot");
   // fake performance
@@ -489,6 +498,7 @@ class NodeWorker extends EventEmitter {
 
 export let isMainThread;
 export let resourceLimits;
+export let threadName: string = "";
 
 let threadId = 0;
 let workerData: unknown = null;
@@ -562,6 +572,7 @@ internals.__initWorkerThreads = (
       workerData = metadata.workerData;
       environmentData = metadata.environmentData;
       isWorkerThread = metadata.isWorkerThread;
+      threadName = metadata.name ?? "";
       const env = metadata.env;
       if (env) {
         process.env = env;
@@ -592,6 +603,7 @@ internals.__initWorkerThreads = (
     defaultExport.workerData = workerData;
     defaultExport.parentPort = parentPort;
     defaultExport.threadId = threadId;
+    defaultExport.threadName = threadName;
 
     patchMessagePortIfFound(workerData);
 
@@ -856,6 +868,7 @@ const defaultExport = {
   setEnvironmentData,
   SHARE_ENV,
   threadId,
+  threadName,
   workerData,
   resourceLimits,
   parentPort,

filename: tests/node_compat/config.jsonc
patch: @@ -1573,6 +1573,7 @@
     "parallel/test-worker-relative-path-double-dot.js": {},
     "parallel/test-worker-relative-path.js": {},
     "parallel/test-worker-terminate-unrefed.js": {},
+    "parallel/test-worker-thread-name.js": {},
     "parallel/test-worker.js": {},
     "parallel/test-worker.mjs": {},
     "parallel/test-zlib-brotli-16GB.js": {},
Repository: ggml-org/llama.cpp
Pull request: examples : add -kvu to batched usage example [no ci]

This commit adds the --kv-unified flag to the usage example in the README.md file for the batched example.

The motivation for this is that without this flag the example will fail with the following error:
```console
Hello my name is
split_equal: sequential split is not supported when there are coupled
sequences in the input batch (you may need to use the -kvu flag)
decode: failed to find a memory slot for batch of size 4
main: llama_decode() failed
```


Changed files:
filename: examples/batched/README.md
patch: @@ -3,7 +3,7 @@
 The example demonstrates batched generation from a given prompt
 
 ```bash
-./llama-batched -m ./models/llama-7b-v2/ggml-model-f16.gguf -p "Hello my name is" -np 4
+./llama-batched -m ./models/llama-7b-v2/ggml-model-f16.gguf -p "Hello my name is" -np 4 --kv-unified
 
 ...
Repository: ollama/ollama
Pull request: Fix embeddings load model behavior

Fixes https://github.com/ollama/ollama/issues/2810. Also cleans up the `embedding_only` API option which had no effect.

Changed files:
filename: api/types.go
patch: @@ -121,7 +121,6 @@ type Runner struct {
 	VocabOnly          bool    `json:"vocab_only,omitempty"`
 	UseMMap            bool    `json:"use_mmap,omitempty"`
 	UseMLock           bool    `json:"use_mlock,omitempty"`
-	EmbeddingOnly      bool    `json:"embedding_only,omitempty"`
 	RopeFrequencyBase  float32 `json:"rope_frequency_base,omitempty"`
 	RopeFrequencyScale float32 `json:"rope_frequency_scale,omitempty"`
 	NumThread          int     `json:"num_thread,omitempty"`
@@ -395,7 +394,6 @@ func DefaultOptions() Options {
 			UseMLock:           false,
 			UseMMap:            true,
 			UseNUMA:            false,
-			EmbeddingOnly:      true,
 		},
 	}
 }

filename: docs/api.md
patch: @@ -321,7 +321,6 @@ curl http://localhost:11434/api/generate -d '{
     "vocab_only": false,
     "use_mmap": true,
     "use_mlock": false,
-    "embedding_only": false,
     "rope_frequency_base": 1.1,
     "rope_frequency_scale": 0.8,
     "num_thread": 8

filename: server/routes.go
patch: @@ -385,7 +385,7 @@ func GenerateHandler(c *gin.Context) {
 	streamResponse(c, ch)
 }
 
-func EmbeddingHandler(c *gin.Context) {
+func EmbeddingsHandler(c *gin.Context) {
 	loaded.mu.Lock()
 	defer loaded.mu.Unlock()
 
@@ -438,8 +438,9 @@ func EmbeddingHandler(c *gin.Context) {
 		return
 	}
 
-	if !loaded.Options.EmbeddingOnly {
-		c.JSON(http.StatusBadRequest, gin.H{"error": "embedding option must be set to true"})
+	// an empty request loads the model
+	if req.Prompt == "" {
+		c.JSON(http.StatusOK, api.EmbeddingResponse{Embedding: []float64{}})
 		return
 	}
 
@@ -948,7 +949,7 @@ func (s *Server) GenerateRoutes() http.Handler {
 	r.POST("/api/pull", PullModelHandler)
 	r.POST("/api/generate", GenerateHandler)
 	r.POST("/api/chat", ChatHandler)
-	r.POST("/api/embeddings", EmbeddingHandler)
+	r.POST("/api/embeddings", EmbeddingsHandler)
 	r.POST("/api/create", CreateModelHandler)
 	r.POST("/api/push", PushModelHandler)
 	r.POST("/api/copy", CopyModelHandler)
Repository: facebook/react
Pull request: easy: add link to legacy context warning


Missed this when adding the link to other places of the same warning in https://github.com/facebook/react/commit/378b305958eb7259cacfce8ad0e66eec07e07074


Changed files:
filename: packages/react-server/src/ReactFizzServer.js
patch: @@ -1696,13 +1696,15 @@ function renderFunctionComponent(
         if (disableLegacyContext) {
           console.error(
             '%s uses the legacy contextTypes API which was removed in React 19. ' +
-              'Use React.createContext() with React.useContext() instead.',
+              'Use React.createContext() with React.useContext() instead. ' +
+              '(https://react.dev/link/legacy-context)',
             componentName,
           );
         } else {
           console.error(
             '%s uses the legacy contextTypes API which will be removed soon. ' +
-              'Use React.createContext() with React.useContext() instead.',
+              'Use React.createContext() with React.useContext() instead. ' +
+              '(https://react.dev/link/legacy-context)',
             componentName,
           );
         }
Repository: electron/electron
Pull request: fix: `backgroundMaterial` on initial activate (35-x-y)

Manually backport #46657 to 35-x-y. See that PR for details.

Notes: Fixed an issue where the `backgroundMaterial` feature did not work in a frameless window on initial window creation.

Changed files:
filename: patches/chromium/chore_modify_chromium_handling_of_mouse_events.patch
patch: @@ -61,7 +61,7 @@ index 932351e288f37fd09ae1a43f44e8b51fb0caa4b8..4a0616bc210d234e51e564daabdd2ebd
    // Overridden from WidgetObserver.
    void OnWidgetThemeChanged(Widget* widget) override;
 diff --git a/ui/views/win/hwnd_message_handler.cc b/ui/views/win/hwnd_message_handler.cc
-index c4d1d483454591031bd76dffced0c1d821800e13..e3bb491f218b2e5d96c424e40a071a618b345039 100644
+index 193e7c1bd76ce18abe6ac47848fc0fb02f2151dd..e985cd1017a54cf8d93875d642d846efb76b60e0 100644
 --- a/ui/views/win/hwnd_message_handler.cc
 +++ b/ui/views/win/hwnd_message_handler.cc
 @@ -3165,15 +3165,19 @@ LRESULT HWNDMessageHandler::HandleMouseEventInternal(UINT message,

filename: patches/chromium/fix_activate_background_material_on_windows.patch
patch: @@ -14,7 +14,7 @@ This patch likely can't be upstreamed as-is, as Chromium doesn't have
 this use case in mind currently.
 
 diff --git a/ui/views/win/hwnd_message_handler.cc b/ui/views/win/hwnd_message_handler.cc
-index 1bbc783c8606f28c93b6e3bf2c60fe8ea4e1fc01..1ed6a143f76c21e0cfd5c7b319171c6f38a5df19 100644
+index 1bbc783c8606f28c93b6e3bf2c60fe8ea4e1fc01..79807442326d2e57b62cf889267507ebd4c484a9 100644
 --- a/ui/views/win/hwnd_message_handler.cc
 +++ b/ui/views/win/hwnd_message_handler.cc
 @@ -932,13 +932,13 @@ void HWNDMessageHandler::FrameTypeChanged() {
@@ -33,6 +33,15 @@ index 1bbc783c8606f28c93b6e3bf2c60fe8ea4e1fc01..1ed6a143f76c21e0cfd5c7b319171c6f
  }
  
  void HWNDMessageHandler::SetWindowIcons(const gfx::ImageSkia& window_icon,
+@@ -1725,7 +1725,7 @@ void HWNDMessageHandler::OnActivateApp(BOOL active, DWORD thread_id) {
+   if (delegate_->HasNonClientView() && !active &&
+       thread_id != GetCurrentThreadId()) {
+     // Update the native frame if it is rendering the non-client area.
+-    if (HasSystemFrame()) {
++    if (is_translucent_ || HasSystemFrame()) {
+       DefWindowProcWithRedrawLock(WM_NCACTIVATE, FALSE, 0);
+     }
+   }
 @@ -2327,17 +2327,18 @@ LRESULT HWNDMessageHandler::OnNCActivate(UINT message,
      delegate_->SchedulePaint();
    }

filename: patches/chromium/fix_take_snapped_status_into_account_when_showing_a_window.patch
patch: @@ -19,7 +19,7 @@ would be removed from its snapped state when re-shown. This fixes that.
 Upstreamed at https://chromium-review.googlesource.com/c/chromium/src/+/6330848.
 
 diff --git a/ui/views/win/hwnd_message_handler.cc b/ui/views/win/hwnd_message_handler.cc
-index 1ed6a143f76c21e0cfd5c7b319171c6f38a5df19..c4d1d483454591031bd76dffced0c1d821800e13 100644
+index 79807442326d2e57b62cf889267507ebd4c484a9..193e7c1bd76ce18abe6ac47848fc0fb02f2151dd 100644
 --- a/ui/views/win/hwnd_message_handler.cc
 +++ b/ui/views/win/hwnd_message_handler.cc
 @@ -674,7 +674,8 @@ void HWNDMessageHandler::Show(ui::mojom::WindowShowState show_state,
Repository: facebook/react
Pull request: Override the getCurrentStack temporarily while printing uncaught errors

This is just a follow up to #30300.

I forgot the uncaught branch.


Changed files:
filename: packages/react-reconciler/src/ReactFiberErrorLogger.js
patch: @@ -46,27 +46,29 @@ export function defaultOnUncaughtError(
       'Consider adding an error boundary to your tree to customize error handling behavior.\n' +
       'Visit https://react.dev/link/error-boundaries to learn more about error boundaries.';
 
-    if (enableOwnerStacks) {
-      console.warn(
-        '%s\n\n%s\n',
-        componentNameMessage,
-        errorBoundaryMessage,
-        // We let our console.error wrapper add the component stack to the end.
-      );
-    } else {
+    const prevGetCurrentStack = ReactSharedInternals.getCurrentStack;
+    if (!enableOwnerStacks) {
       // The current Fiber is disconnected at this point which means that console printing
       // cannot add a component stack since it terminates at the deletion node. This is not
       // a problem for owner stacks which are not disconnected but for the parent component
       // stacks we need to use the snapshot we've previously extracted.
       const componentStack =
         errorInfo.componentStack != null ? errorInfo.componentStack : '';
-      // Don't transform to our wrapper
-      console['warn'](
-        '%s\n\n%s\n%s',
+      ReactSharedInternals.getCurrentStack = function () {
+        return componentStack;
+      };
+    }
+    try {
+      console.warn(
+        '%s\n\n%s\n',
         componentNameMessage,
         errorBoundaryMessage,
-        componentStack,
+        // We let our console.error wrapper add the component stack to the end.
       );
+    } finally {
+      if (!enableOwnerStacks) {
+        ReactSharedInternals.getCurrentStack = prevGetCurrentStack;
+      }
     }
   }
 }
Repository: ggml-org/llama.cpp
Pull request: common : skip model validation when --help is requested

This commit skips the model validation check when the user specifies the --help option.

The motivation for this is that currently and error is thrown before the --help could be processed. Now skips validation if params.usage is set, allowing help to display without requiring --model.

Resolves: https://github.com/ggml-org/llama.cpp/issues/17754

Changed files:
filename: common/arg.cpp
patch: @@ -427,7 +427,7 @@ static bool common_params_parse_ex(int argc, char ** argv, common_params_context
 
     // model is required (except for server)
     // TODO @ngxson : maybe show a list of available models in CLI in this case
-    if (params.model.path.empty() && ctx_arg.ex != LLAMA_EXAMPLE_SERVER) {
+    if (params.model.path.empty() && ctx_arg.ex != LLAMA_EXAMPLE_SERVER && !params.usage) {
         throw std::invalid_argument("error: --model is required\n");
     }
Repository: ollama/ollama
Pull request: Add ollama user to video group

On OpenSUSE, ollama needs to be a member of the video group to access the GPU

Fixes #2587 

Changed files:
filename: scripts/install.sh
patch: @@ -88,6 +88,10 @@ configure_systemd() {
         status "Adding ollama user to render group..."
         $SUDO usermod -a -G render ollama
     fi
+    if getent group video >/dev/null 2>&1; then
+        status "Adding ollama user to video group..."
+        $SUDO usermod -a -G video ollama
+    fi
 
     status "Adding current user to ollama group..."
     $SUDO usermod -a -G ollama $(whoami)
Repository: electron/electron
Pull request: fix: `backgroundMaterial` on initial activate

#### Description of Change

Closes https://github.com/electron/electron/issues/38466

Extends https://github.com/electron/electron/issues/39708 to fix an issue where the `backgroundMaterial` feature did not work in a frameless window on initial window creation. A repaint needed to be triggered first, by a resize or other similar action.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [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: Fixed an issue where the `backgroundMaterial` feature did not work in a frameless window on initial window creation.

Changed files:
filename: patches/chromium/fix_activate_background_material_on_windows.patch
patch: @@ -14,7 +14,7 @@ This patch likely can't be upstreamed as-is, as Chromium doesn't have
 this use case in mind currently.
 
 diff --git a/ui/views/win/hwnd_message_handler.cc b/ui/views/win/hwnd_message_handler.cc
-index 29829e282edfa8821bd366a9e9a3755d7f3f8643..9feff09aa83eb88460dce786ab2514f0a9b21c6e 100644
+index 29829e282edfa8821bd366a9e9a3755d7f3f8643..661864ab6aad78a721ac921ae778c40085cdc23e 100644
 --- a/ui/views/win/hwnd_message_handler.cc
 +++ b/ui/views/win/hwnd_message_handler.cc
 @@ -952,13 +952,13 @@ void HWNDMessageHandler::FrameTypeChanged() {
@@ -33,6 +33,15 @@ index 29829e282edfa8821bd366a9e9a3755d7f3f8643..9feff09aa83eb88460dce786ab2514f0
  }
  
  void HWNDMessageHandler::SetWindowIcons(const gfx::ImageSkia& window_icon,
+@@ -1755,7 +1755,7 @@ void HWNDMessageHandler::OnActivateApp(BOOL active, DWORD thread_id) {
+   if (delegate_->HasNonClientView() && !active &&
+       thread_id != GetCurrentThreadId()) {
+     // Update the native frame if it is rendering the non-client area.
+-    if (HasSystemFrame()) {
++    if (is_translucent_ || HasSystemFrame()) {
+       DefWindowProcWithRedrawLock(WM_NCACTIVATE, FALSE, 0);
+     }
+   }
 @@ -2356,17 +2356,18 @@ LRESULT HWNDMessageHandler::OnNCActivate(UINT message,
      delegate_->SchedulePaint();
    }
Repository: facebook/react
Pull request: Add RN fork of consoleWithStackDev so we can improve the mainline one

We're removing this wrapper from the mainline but RN is still using component stacks to filter out warnings.

This is unfortunate since it'll be hard to keep track of the interplay with these, DevTools and how you're supposed to implement error dialogs in userspace.

Changed files:
filename: packages/shared/forks/consoleWithStackDev.rn.js
patch: @@ -0,0 +1,59 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ */
+
+import ReactSharedInternals from 'shared/ReactSharedInternals';
+
+let suppressWarning = false;
+export function setSuppressWarning(newSuppressWarning) {
+  if (__DEV__) {
+    suppressWarning = newSuppressWarning;
+  }
+}
+
+// In DEV, calls to console.warn and console.error get replaced
+// by calls to these methods by a Babel plugin.
+//
+// In PROD (or in packages without access to React internals),
+// they are left as they are instead.
+
+export function warn(format, ...args) {
+  if (__DEV__) {
+    if (!suppressWarning) {
+      printWarning('warn', format, args, new Error('react-stack-top-frame'));
+    }
+  }
+}
+
+export function error(format, ...args) {
+  if (__DEV__) {
+    if (!suppressWarning) {
+      printWarning('error', format, args, new Error('react-stack-top-frame'));
+    }
+  }
+}
+
+export let isWritingAppendedStack = false;
+
+function printWarning(level, format, args, currentStack) {
+  if (__DEV__) {
+    if (ReactSharedInternals.getCurrentStack) {
+      const stack = ReactSharedInternals.getCurrentStack(currentStack);
+      if (stack !== '') {
+        isWritingAppendedStack = true;
+        format += '%s';
+        args = args.concat([stack]);
+      }
+    }
+
+    args.unshift(format);
+    // We intentionally don't use spread (or .apply) directly because it
+    // breaks IE9: https://github.com/facebook/react/issues/13610
+    // eslint-disable-next-line react-internal/no-production-logging
+    Function.prototype.apply.call(console[level], console, args);
+    isWritingAppendedStack = false;
+  }
+}

filename: scripts/rollup/forks.js
patch: @@ -209,6 +209,9 @@ const forks = Object.freeze({
     switch (bundleType) {
       case FB_WWW_DEV:
         return './packages/shared/forks/consoleWithStackDev.www.js';
+      case RN_OSS_DEV:
+      case RN_FB_DEV:
+        return './packages/shared/forks/consoleWithStackDev.rn.js';
       default:
         return null;
     }
Repository: ggml-org/llama.cpp
Pull request: fix: convert_hf_to_gguf - use existing local chat_template if mistral-format model has one.

Cont. https://github.com/ggml-org/llama.cpp/pull/17712

Some of the new [Ministral-3](https://huggingface.co/mistralai/Ministral-3-14B-Instruct-2512/blob/main/chat_template.jinja) Instruct variants have local chat templates, unlike previous Mistral models which required community intervention.

Beforehand, Ministral-3 models were converted and given an Unsloth `Devstral` chat template. This PR ensures Ministral-3 models converted with `--mistral-format` use their own provided chat templates instead.

It should also affect [Mistral-Large-3](https://huggingface.co/mistralai/Mistral-Large-3-675B-Instruct-2512/tree/main) as it has its own chat template too - I don't have the resources to test converting it.

Changed files:
filename: convert_hf_to_gguf.py
patch: @@ -2341,19 +2341,31 @@ def _set_vocab_mistral(self):
         self.gguf_writer.add_add_bos_token(True)
         self.gguf_writer.add_add_eos_token(False)
 
-        template_dir = Path(__file__).parent / "models/templates/"
+        local_template_file_path = self.dir_model / "chat_template.jinja"
+
+        if self.is_mistral_format and local_template_file_path.is_file():
+            # Ministral-3 and other new Mistral models come with chat templates.
+            # ref: https://huggingface.co/mistralai/Ministral-3-14B-Instruct-2512/tree/main
+            logger.info("Using an existing Mistral local chat template.")
+
+            with open(local_template_file_path, "r", encoding="utf-8") as f:
+                template = f.read()
+        elif not self.is_mistral_format or not self.disable_mistral_community_chat_template:
+            template_dir = Path(__file__).parent / "models/templates/"
 
-        if not self.is_mistral_format or not self.disable_mistral_community_chat_template:
             # Log only for Mistral format that the official tokenization and detokenization is via `mistral-common`.
             if self.is_mistral_format:
                 logger.info(
                     "Using a Mistral community chat template. These templates can be subject to errors in early days or weeks after a release. "
                     "Mistral recommends to use `mistral-common` to perform tokenization and detokenization."
                 )
             template = MistralModel.get_community_chat_template(vocab, template_dir, self.is_mistral_format)
-            self.gguf_writer.add_chat_template(template)
         else:
-            logger.info("Not using a Mistral community chat template. Ensure to perform the tokenization and detokenization via `mistral-common`.")
+            logger.info("Not using a Mistral local or community chat template. Ensure to perform the tokenization and detokenization via `mistral-common`.")
+            template = None
+
+        if template is not None:
+            self.gguf_writer.add_chat_template(template)
 
     def set_vocab(self):
         if self.is_mistral_format:
Repository: ollama/ollama
Pull request: Add env var so podman will map cuda GPUs

Without this env var, podman's GPU logic doesn't map the GPU through

Fixes #2716 

Changed files:
filename: Dockerfile
patch: @@ -132,6 +132,7 @@ ENV OLLAMA_HOST 0.0.0.0
 ENV PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 ENV LD_LIBRARY_PATH=/usr/local/nvidia/lib:/usr/local/nvidia/lib64
 ENV NVIDIA_DRIVER_CAPABILITIES=compute,utility
+ENV NVIDIA_VISIBLE_DEVICES=all
 
 ENTRYPOINT ["/bin/ollama"]
 CMD ["serve"]