helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: build(dev-deps): drop unused @types/webpack dep

Backport of #47767

See that PR for details.


Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: package.json
patch: @@ -18,7 +18,6 @@
     "@types/semver": "^7.5.8",
     "@types/stream-json": "^1.7.7",
     "@types/temp": "^0.9.4",
-    "@types/webpack": "^5.28.5",
     "@types/webpack-env": "^1.18.5",
     "@typescript-eslint/eslint-plugin": "^8.32.1",
     "@typescript-eslint/parser": "^8.7.0",

filename: yarn.lock
patch: @@ -1061,15 +1061,6 @@
   resolved "https://registry.yarnpkg.com/@types/webpack-env/-/webpack-env-1.18.5.tgz#eccda0b04fe024bed505881e2e532f9c119169bf"
   integrity sha512-wz7kjjRRj8/Lty4B+Kr0LN6Ypc/3SymeCCGSbaXp2leH0ZVg/PriNiOwNj4bD4uphI7A8NXS4b6Gl373sfO5mA==
 
-"@types/webpack@^5.28.5":
-  version "5.28.5"
-  resolved "https://registry.yarnpkg.com/@types/webpack/-/webpack-5.28.5.tgz#0e9d9a15efa09bbda2cef41356ca4ac2031ea9a2"
-  integrity sha512-wR87cgvxj3p6D0Crt1r5avwqffqPXUkNlnQ1mjU93G7gCuFjufZR4I6j8cz5g1F1tTYpfOOFvly+cmIQwL9wvw==
-  dependencies:
-    "@types/node" "*"
-    tapable "^2.2.0"
-    webpack "^5"
-
 "@types/yauzl@^2.9.1":
   version "2.10.0"
   resolved "https://registry.yarnpkg.com/@types/yauzl/-/yauzl-2.10.0.tgz#b3248295276cf8c6f153ebe6a9aba0c988cb2599"
@@ -8041,7 +8032,7 @@ webpack-sources@^3.2.3:
   resolved "https://registry.yarnpkg.com/webpack-sources/-/webpack-sources-3.2.3.tgz#2d4daab8451fd4b240cc27055ff6a0c2ccea0cde"
   integrity sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==
 
-webpack@^5, webpack@^5.95.0:
+webpack@^5.95.0:
   version "5.95.0"
   resolved "https://registry.yarnpkg.com/webpack/-/webpack-5.95.0.tgz#8fd8c454fa60dad186fbe36c400a55848307b4c0"
   integrity sha512-2t3XstrKULz41MNMBF+cJ97TyHdyQ8HCt//pqErqDvNjU9YQBnZxIHa11VXsi7F3mb5/aO2tuDxdeTPdU7xu9Q==
Repository: ollama/ollama
Pull request: types/model: fix tag case

tag is case sensitive so it's incorrect to change it to lower case

resolves #4250

Changed files:
filename: types/model/name.go
patch: @@ -290,12 +290,14 @@ func (n Name) Filepath() string {
 	if !n.IsFullyQualified() {
 		panic("illegal attempt to get filepath of invalid name")
 	}
-	return strings.ToLower(filepath.Join(
-		n.Host,
-		n.Namespace,
-		n.Model,
+	return filepath.Join(
+		strings.ToLower(filepath.Join(
+			n.Host,
+			n.Namespace,
+			n.Model,
+		)),
 		n.Tag,
-	))
+	)
 }
 
 // LogValue returns a slog.Value that represents the name as a string.

filename: types/model/name_test.go
patch: @@ -19,6 +19,16 @@ func TestParseNameParts(t *testing.T) {
 		wantFilepath    string
 		wantValidDigest bool
 	}{
+		{
+			in: "registry.ollama.ai/library/dolphin-mistral:7b-v2.6-dpo-laser-q6_K",
+			want: Name{
+				Host:      "registry.ollama.ai",
+				Namespace: "library",
+				Model:     "dolphin-mistral",
+				Tag:       "7b-v2.6-dpo-laser-q6_K",
+			},
+			wantFilepath: filepath.Join("registry.ollama.ai", "library", "dolphin-mistral", "7b-v2.6-dpo-laser-q6_K"),
+		},
 		{
 			in: "scheme://host:port/namespace/model:tag",
 			want: Name{
@@ -266,9 +276,9 @@ func TestFilepathAllocs(t *testing.T) {
 	allocs := testing.AllocsPerRun(1000, func() {
 		n.Filepath()
 	})
-	allowedAllocs := 2.0
+	var allowedAllocs float64 = 3
 	if runtime.GOOS == "windows" {
-		allowedAllocs = 4
+		allowedAllocs = 5
 	}
 	if allocs > allowedAllocs {
 		t.Errorf("allocs = %v; allowed %v", allocs, allowedAllocs)
Repository: huggingface/transformers
Pull request: Fix typo in LFM-VL

# What does this PR do?

As per title, the typo was reported by the authors, as they are planning another release soon. The configs one the hub were saved with an "underscore" 

Changed files:
filename: src/transformers/generation/utils.py
patch: @@ -1941,7 +1941,7 @@ def _supports_default_dynamic_cache(cls) -> bool:
                 "minimax",
                 "xlnet",
                 "lfm2",
-                "lfm2-vl",
+                "lfm2_vl",
             ]
         )
 

filename: src/transformers/models/lfm2_vl/configuration_lfm2_vl.py
patch: @@ -50,7 +50,7 @@ class Lfm2VlConfig(PreTrainedConfig):
             The downsample_factor factor of the vision backbone.
     """
 
-    model_type = "lfm2-vl"
+    model_type = "lfm2_vl"
     sub_configs = {"text_config": AutoConfig, "vision_config": AutoConfig}
 
     def __init__(
Repository: ggml-org/llama.cpp
Pull request: on opencl added note for pre SYCL Intel hardware

Specify that it's for pre sycl hardware

Changed files:
filename: docs/backend/OPENCL.md
patch: @@ -17,7 +17,7 @@ OpenCL (Open Computing Language) is an open, royalty-free standard for cross-pla
 
 ### Llama.cpp + OpenCL
 
-The llama.cpp OpenCL backend is designed to enable llama.cpp on **Qualcomm Adreno GPU** firstly via OpenCL. Thanks to the portabilty of OpenCL, the OpenCL backend can also run on certain Intel GPUs although the performance is not optimal.
+The llama.cpp OpenCL backend is designed to enable llama.cpp on **Qualcomm Adreno GPU** firstly via OpenCL. Thanks to the portabilty of OpenCL, the OpenCL backend can also run on certain Intel GPUs such as those that do not have [SYCL](/docs/backend/SYCL.md) support although the performance is not optimal.
 
 ## OS
Repository: electron/electron
Pull request: test: fix extensions console flake

Backport of #47750

See that PR for details.


Notes: none

Changed files:
filename: spec/extensions-spec.ts
patch: @@ -18,7 +18,7 @@ const uuid = require('uuid');
 const fixtures = path.join(__dirname, 'fixtures');
 
 describe('chrome extensions', () => {
-  const emptyPage = '<script>console.log("loaded")</script>';
+  const emptyPage = '<html><body><h1>EMPTY PAGE</h1></body></html>';
 
   // NB. extensions are only allowed on http://, https:// and ftp:// (!) urls by default.
   let server: http.Server;
Repository: huggingface/transformers
Pull request: Remove upper version bound of pandas

# What does this PR do?

Let's skip pandas 2.3.0 and allow users to install newer versions.


Changed files:
filename: setup.py
patch: @@ -128,7 +128,7 @@
     "opencv-python",
     "optimum-benchmark>=0.3.0",
     "optuna",
-    "pandas<2.3.0",  # `datasets` requires `pandas` while `pandas==2.3.0` has issues with CircleCI on 2025/06/05
+    "pandas!=2.3.0",  # `datasets` requires `pandas` while `pandas==2.3.0` has issues with CircleCI on 2025/06/05
     "packaging>=20.0",
     "parameterized>=0.9",  # older version of parameterized cause pytest collection to fail on .expand
     "phonemizer",

filename: src/transformers/dependency_versions_table.py
patch: @@ -38,7 +38,7 @@
     "opencv-python": "opencv-python",
     "optimum-benchmark": "optimum-benchmark>=0.3.0",
     "optuna": "optuna",
-    "pandas": "pandas<2.3.0",
+    "pandas": "pandas!=2.3.0",
     "packaging": "packaging>=20.0",
     "parameterized": "parameterized>=0.9",
     "phonemizer": "phonemizer",
Repository: ggml-org/llama.cpp
Pull request: ggml-cuda: fix regex for arch list

🎄 https://xkcd.com/1171/

Changed files:
filename: ggml/src/ggml-cuda/CMakeLists.txt
patch: @@ -44,8 +44,13 @@ if (CUDAToolkit_FOUND)
     # Replace any 12x-real architectures with 12x{a}-real. FP4 ptx instructions are not available in just 12x
     if (GGML_NATIVE)
         set(PROCESSED_ARCHITECTURES "")
-        foreach(ARCH ${CMAKE_CUDA_ARCHITECTURES_NATIVE})
-            if(ARCH MATCHES "^12[0-9]$")
+        if (CMAKE_CUDA_ARCHITECTURES_NATIVE)
+            set(ARCH_LIST ${CMAKE_CUDA_ARCHITECTURES_NATIVE})
+        else()
+            set(ARCH_LIST ${CMAKE_CUDA_ARCHITECTURES})
+        endif()
+        foreach(ARCH ${ARCH_LIST})
+            if (ARCH MATCHES "^12[0-9](-real|-virtual)?$")
                 string(REGEX REPLACE "^(12[0-9]).*$" "\\1" BASE_ARCH ${ARCH})
                 message(STATUS "Replacing ${ARCH} with ${BASE_ARCH}a-real")
                 list(APPEND PROCESSED_ARCHITECTURES "${BASE_ARCH}a-real")
Repository: ollama/ollama
Pull request: skip hidden files in list models handler

Hidden files on MacOS (ex: `.DS_Store`) cause the list command to file when not skipped:
```
❯ ollama ls
Error: unqualified name: 
```

Changed files:
filename: server/routes.go
patch: @@ -733,6 +733,12 @@ func (s *Server) ListModelsHandler(c *gin.Context) {
 				return err
 			}
 
+			if hidden, err := filepath.Match(".*", filepath.Base(rel)); err != nil {
+				return err
+			} else if hidden {
+				return nil
+			}
+
 			n := model.ParseNameFromFilepath(rel)
 			m, err := ParseNamedManifest(n)
 			if err != nil {
Repository: electron/electron
Pull request: test: fix extensions console flake

#### Description of Change

Fixes a race condition flake in extensions tests:

<img width="753" height="360" alt="Screenshot 2025-07-15 at 9 53 40 AM" src="https://github.com/user-attachments/assets/90a8badd-2058-4288-a604-10e9002abd42" />

Many of them depend on parsing console logs, and sometimes the empty page load from the server could interfere with what it was supposed to be parsing.

#### 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] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: none

Changed files:
filename: spec/extensions-spec.ts
patch: @@ -18,7 +18,7 @@ const uuid = require('uuid');
 const fixtures = path.join(__dirname, 'fixtures');
 
 describe('chrome extensions', () => {
-  const emptyPage = '<script>console.log("loaded")</script>';
+  const emptyPage = '<html><body><h1>EMPTY PAGE</h1></body></html>';
 
   // NB. extensions are only allowed on http://, https:// and ftp:// (!) urls by default.
   let server: http.Server;
Repository: facebook/react
Pull request: Enable lazy context propagation

Last I heard this was great so not sure there are any more blockers to just include it in 19?

Changed files:
filename: packages/shared/ReactFeatureFlags.js
patch: @@ -101,8 +101,7 @@ export const enableObjectFiber = false;
 
 export const enableTransitionTracing = false;
 
-// Shipped on FB, waiting for next stable release to roll out to OSS
-export const enableLazyContextPropagation = __EXPERIMENTAL__;
+export const enableLazyContextPropagation = true;
 
 // Expose unstable useContext for performance testing
 export const enableContextProfiling = false;
Repository: denoland/deno
Pull request: fix(ext/node): fix send() validation in child_process IPC

Two validation issues in the IPC send() function:

1. Used `new TypeError("ERR_MISSING_ARGS")` instead of the proper `ERR_MISSING_ARGS` error class, so the error had the code as its message instead of the correct message and code properties.

2. Missing type validation for the message argument. Sending a Symbol would hit the IPC serializer and throw an internal error instead of the expected ERR_INVALID_ARG_TYPE. Now validates that message is string, object, number, or boolean before attempting to send.


Changed files:
filename: ext/node/polyfills/internal/child_process.ts
patch: @@ -47,6 +47,7 @@ import {
   ERR_INVALID_SYNC_FORK_INPUT,
   ERR_IPC_CHANNEL_CLOSED,
   ERR_IPC_SYNC_FORK,
+  ERR_MISSING_ARGS,
   ERR_UNKNOWN_SIGNAL,
 } from "ext:deno_node/internal/errors.ts";
 import { Buffer } from "node:buffer";
@@ -1880,7 +1881,21 @@ export function setupChannel(
     options = { swallowErrors: false, ...options };
 
     if (message === undefined) {
-      throw new TypeError("ERR_MISSING_ARGS", "message");
+      throw new ERR_MISSING_ARGS("message");
+    }
+
+    if (
+      typeof message !== "string" &&
+      typeof message !== "object" &&
+      typeof message !== "number" &&
+      typeof message !== "boolean" &&
+      typeof message !== "bigint"
+    ) {
+      throw new ERR_INVALID_ARG_TYPE(
+        "message",
+        ["string", "object", "number", "boolean"],
+        message,
+      );
     }
 
     if (handle !== undefined) {

filename: tests/node_compat/config.jsonc
patch: @@ -222,6 +222,7 @@
     "parallel/test-child-process-execsync-maxbuf.js": {},
     "parallel/test-child-process-exit-code.js": {},
     "parallel/test-child-process-flush-stdio.js": {},
+    "parallel/test-child-process-fork.js": {},
     "parallel/test-child-process-fork-abort-signal.js": {},
     "parallel/test-child-process-fork-and-spawn.js": {},
     "parallel/test-child-process-fork-close.js": {},
Repository: facebook/react
Pull request: disable `enableSiblingPrerendering` in experimental channel

Disables `enableSiblingPrerendering` in the experimental builds until the feature is tested at Meta first.

Changed files:
filename: packages/react-devtools-shared/src/__tests__/TimelineProfiler-test.js
patch: @@ -21,10 +21,10 @@ import semver from 'semver';
 // TODO: This is how other DevTools tests access the version but we should find
 // a better solution for this
 const ReactVersionTestingAgainst = process.env.REACT_VERSION || ReactVersion;
-const enableSiblingPrerendering = semver.gte(
-  ReactVersionTestingAgainst,
-  '19.0.0',
-);
+// Disabling this while the flag is off in experimental. Leaving the logic so we can
+// restore the behavior when we turn the flag back on.
+const enableSiblingPrerendering =
+  false && semver.gte(ReactVersionTestingAgainst, '19.0.0');
 
 describe('Timeline profiler', () => {
   let React;

filename: packages/shared/ReactFeatureFlags.js
patch: @@ -148,7 +148,7 @@ export const enableOwnerStacks = __EXPERIMENTAL__;
 
 export const enableShallowPropDiffing = false;
 
-export const enableSiblingPrerendering = __EXPERIMENTAL__;
+export const enableSiblingPrerendering = false;
 
 /**
  * Enables an expiration time for retry lanes to avoid starvation.

filename: packages/shared/forks/ReactFeatureFlags.test-renderer.js
patch: @@ -80,7 +80,7 @@ export const enableAddPropertiesFastPath = false;
 
 export const renameElementSymbol = true;
 export const enableShallowPropDiffing = false;
-export const enableSiblingPrerendering = __EXPERIMENTAL__;
+export const enableSiblingPrerendering = false;
 
 // TODO: This must be in sync with the main ReactFeatureFlags file because
 // the Test Renderer's value must be the same as the one used by the
Repository: ollama/ollama
Pull request: Fix help string for stop parameter

Changed the help prompt for setting the stop parameters, and quotes or commas are otherwise included in the stop-token:

/set parameter stop "?", "!" # Invalid
/set parameter stop ? ! # Valid

Changed files:
filename: cmd/interactive.go
patch: @@ -162,7 +162,7 @@ func generateInteractive(cmd *cobra.Command, opts runOptions) error {
 		fmt.Fprintln(os.Stderr, "  /set parameter repeat_penalty <float> How strongly to penalize repetitions")
 		fmt.Fprintln(os.Stderr, "  /set parameter repeat_last_n <int>    Set how far back to look for repetitions")
 		fmt.Fprintln(os.Stderr, "  /set parameter num_gpu <int>          The number of layers to send to the GPU")
-		fmt.Fprintln(os.Stderr, "  /set parameter stop \"<string>\", ...   Set the stop parameters")
+		fmt.Fprintln(os.Stderr, "  /set parameter stop <string> <string> ...   Set the stop parameters")
 		fmt.Fprintln(os.Stderr, "")
 	}
Repository: denoland/deno
Pull request: perf(ext/napi): use threadpool for async work instead of spawning threads

## Summary

- Replace `std::thread::spawn` with `deno_core::unsync::spawn_blocking` (tokio's blocking threadpool) in `napi_queue_async_work`
- Threads are reused from a pool instead of creating a new OS thread per call, reducing overhead especially on Linux where `clone()` is expensive
- This is analogous to how Node.js uses libuv's `uv_queue_work` threadpool

## Context

PR #32560 fixed a deadlock bug by moving `execute` callbacks to worker threads via `std::thread::spawn`. This created a performance regression (#32773) because every async NAPI call spawns and tears down a fresh OS thread. The tokio blocking threadpool keeps threads alive for reuse (default 10s keep-alive), avoiding per-call thread creation overhead.

## Benchmark (macOS aarch64, napi-rs async add)

| Runtime | µs/call |
|---------|---------|
| Node.js | ~8.8 |
| Deno 2.7.5 (std::thread::spawn) | ~8.5-9 |
| Deno dev (spawn_blocking) | ~8.5 |

On macOS the steady-state is similar since thread creation is lightweight. On Linux (reporter's platform), `std::thread::spawn` is significantly more expensive due to `clone()` syscall cost — the reporter measured 62µs → 258µs regression.

## Test plan

- [x] `cargo test --test integration -- napi` — all NAPI tests pass (debug + release)
- [x] Benchmarked with napi-rs async functions — performance on par with Node.js

Closes #32773

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

Changed files:
filename: ext/napi/node_api.rs
patch: @@ -595,7 +595,9 @@ pub(crate) fn napi_queue_async_work(
   // Per NAPI spec, `execute` runs on a worker thread and `complete` runs on
   // the main thread. Previously both ran on the main thread which caused
   // deadlocks when `execute` called threadsafe functions.
-  std::thread::spawn(move || {
+  // Uses tokio's blocking threadpool to reuse threads instead of spawning a
+  // new OS thread per call (which has high overhead on Linux).
+  deno_core::unsync::spawn_blocking(move || {
     let work = work.take();
     let work = unsafe { &*work };
Repository: nodejs/node
Pull request: typings: remove unnecessary import of global TypedArray

The error is caused by the `typings/globals.d.ts` file declaring TypedArray as a global type. 

The line `import { TypedArray } from '../globals';` was added unnecessarily, which is causing the error.

To fix this, I will remove the import line from the `typings/internalBinding/zlib.d.ts` file.

<img width="328" height="24" alt="image" src="https://github.com/user-attachments/assets/498679cd-ba68-42be-aeeb-219fdbb179ad" />


Changed files:
filename: typings/internalBinding/zlib.d.ts
patch: @@ -1,5 +1,3 @@
-import { TypedArray } from '../globals';
-
 declare namespace InternalZlibBinding {
   class ZlibBase {
     // These attributes are not used by the C++ binding, but declared on JS side.
Repository: ggml-org/llama.cpp
Pull request: tools : use common_log_pause to fix fit-params output race

Replaced the `std::this_thread::sleep_for(10ms)` hack with `common_log_pause(common_log_main())` in `llama-fit-params`.

**Reasoning:**
The previous 10ms delay was intended to let the async logger drain its queue to `stderr` before the main thread printed the result to `stdout`. However, on high-performance or loaded systems, 10ms is not guaranteed to be enough, leading to interleaved output (see Issue #18085).

`common_log_pause` explicitly waits for the background worker to drain the log queue, ensuring deterministic separation between logs and the final result.

Fixes #18085

Changed files:
filename: tools/fit-params/fit-params.cpp
patch: @@ -35,7 +35,7 @@ int main(int argc, char ** argv) {
     }
 
     LOG_INF("%s: printing fitted CLI arguments to stdout...\n", __func__);
-    std::this_thread::sleep_for(10ms); // to avoid a race between stderr and stdout
+    common_log_flush(common_log_main());
     printf("-c %" PRIu32 " -ngl %" PRIu32, cparams.n_ctx, mparams.n_gpu_layers);
 
     size_t nd = llama_max_devices();
Repository: vercel/next.js
Pull request: fix(next-swc): Enable `ignoreDynamic` for auto_cjs

This PR enables `ignoreDynamic` for common js modules which is detected by `auto_cjs` pass.


Fixes https://github.com/vercel/next.js/issues/40231.


---

I verified that with this change the test reproduction does not fail with import error.

Changed files:
filename: packages/next-swc/crates/core/src/lib.rs
patch: @@ -33,13 +33,13 @@ DEALINGS IN THE SOFTWARE.
 use auto_cjs::contains_cjs;
 use either::Either;
 use fxhash::FxHashSet;
+
 use serde::Deserialize;
 use std::cell::RefCell;
 use std::rc::Rc;
 use std::{path::PathBuf, sync::Arc};
 
 use next_binding::swc::core::{
-    base::config::ModuleConfig,
     common::{chain, comments::Comments, pass::Optional, FileName, SourceFile, SourceMap},
     ecma::ast::EsVersion,
     ecma::parser::parse_file_as_module,
@@ -287,7 +287,9 @@ impl TransformOptions {
             };
 
         if should_enable_commonjs {
-            self.swc.config.module = Some(ModuleConfig::CommonJs(Default::default()));
+            self.swc.config.module = Some(
+                serde_json::from_str(r##"{ "type": "commonjs", "ignoreDynamic": true }"##).unwrap(),
+            );
         }
 
         self

filename: packages/next-swc/crates/core/tests/loader/issue-40231/input.js
patch: @@ -0,0 +1,5 @@
+function loadSomethingWithDynamicImport(param) {
+  return import(`something/${param}`).then(r => r.default)
+}
+
+module.exports = { loadSomethingWithDynamicImport }
\ No newline at end of file

filename: packages/next-swc/crates/core/tests/loader/issue-40231/output.js
patch: @@ -0,0 +1,9 @@
+"use strict";
+function loadSomethingWithDynamicImport(param) {
+    return import("something/".concat(param)).then(function(r) {
+        return r.default;
+    });
+}
+module.exports = {
+    loadSomethingWithDynamicImport: loadSomethingWithDynamicImport
+};
Repository: ggml-org/llama.cpp
Pull request: vulkan: fix command buffer corruption in ggml_backend_vk_event_wait

Fixes #18297.

The async download paths that I had been using to test events weren't hitting event_wait, and this bug slipped through.

Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -13718,6 +13718,7 @@ static void ggml_vk_graph_optimize(ggml_backend_t backend, struct ggml_cgraph *
 }
 
 static void ggml_backend_vk_event_record(ggml_backend_t backend, ggml_backend_event_t event) {
+    VK_LOG_DEBUG("ggml_backend_vk_event_record(backend=" << backend << ", event=" << event << ")");
     ggml_backend_vk_context * ctx = (ggml_backend_vk_context *)backend->context;
     vk_event *vkev = (vk_event *)event->context;
 
@@ -13747,6 +13748,7 @@ static void ggml_backend_vk_event_record(ggml_backend_t backend, ggml_backend_ev
 }
 
 static void ggml_backend_vk_event_wait(ggml_backend_t backend, ggml_backend_event_t event) {
+    VK_LOG_DEBUG("ggml_backend_vk_event_wait(backend=" << backend << ", event=" << event << ")");
     ggml_backend_vk_context * ctx = (ggml_backend_vk_context *)backend->context;
     vk_event *vkev = (vk_event *)event->context;
 
@@ -13762,6 +13764,8 @@ static void ggml_backend_vk_event_wait(ggml_backend_t backend, ggml_backend_even
     }
 
     ggml_vk_wait_events(transfer_ctx, {vkev->event});
+    ggml_vk_ctx_end(transfer_ctx);
+    ctx->transfer_ctx.reset();
 }
 
 // TODO: enable async and synchronize
@@ -14521,6 +14525,7 @@ static void ggml_backend_vk_device_event_free(ggml_backend_dev_t dev, ggml_backe
 }
 
 static void ggml_backend_vk_device_event_synchronize(ggml_backend_dev_t dev, ggml_backend_event_t event) {
+    VK_LOG_DEBUG("ggml_backend_vk_device_event_synchronize(backend=" << dev << ", event=" << event << ")");
     ggml_backend_vk_device_context * ctx = (ggml_backend_vk_device_context *)dev->context;
     auto device = ggml_vk_get_device(ctx->device);
     vk_event *vkev = (vk_event *)event->context;
Repository: ollama/ollama
Pull request: Update langchainpy.md

fixing pip code.

Changed files:
filename: docs/tutorials/langchainpy.md
patch: @@ -12,7 +12,7 @@ So let's figure out how we can use **LangChain** with Ollama to ask our question
 
 Let's start by asking a simple question that we can get an answer to from the **Llama2** model using **Ollama**. First, we need to install the **LangChain** package:
 
-`pip install langchain`
+`pip install langchain_community`
 
 Then we can create a model and ask the question: