helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: types/model: remove MarshalText/UnmarshalText from Digest


Changed files:
filename: types/model/digest.go
patch: @@ -38,20 +38,6 @@ func (d Digest) String() string { return d.s }
 // ParseName(name).Digest().
 func (d Digest) IsValid() bool { return d.s != "" }
 
-// MarshalText implements encoding.TextMarshaler.
-func (d Digest) MarshalText() ([]byte, error) {
-	return []byte(d.String()), nil
-}
-
-// UnmarshalText implements encoding.TextUnmarshaler.
-func (d *Digest) UnmarshalText(text []byte) error {
-	if d.IsValid() {
-		return errors.New("model.Digest: illegal UnmarshalText on valid Digest")
-	}
-	*d = ParseDigest(string(text))
-	return nil
-}
-
 // LogValue implements slog.Value.
 func (d Digest) LogValue() slog.Value {
 	return slog.StringValue(d.String())
Repository: nodejs/node
Pull request: benchmark: reduce readfile-permission-enabled config

**benchmark: reduce readfile-permission-enabled config**
```
There's no need to test all readfile config as
permission model won't impact based on size.
```

Part of https://github.com/nodejs/performance/issues/186


Changed files:
filename: benchmark/fs/readfile-permission-enabled.js
patch: @@ -12,8 +12,8 @@ const filename = tmpdir.resolve(`.removeme-benchmark-garbage-${process.pid}`);
 
 const bench = common.createBenchmark(main, {
   duration: [5],
-  encoding: ['', 'utf-8'],
-  len: [1024, 16 * 1024 * 1024],
+  encoding: ['utf-8'],
+  len: [1024],
   concurrent: [1, 10],
 }, {
   flags: [
Repository: denoland/deno
Pull request: fix(ci): fix ordering of platforms in ecosystem_compat_slack

Results for macOS and linux were swapped

Changed files:
filename: tools/ecosystem_compat_slack.ts
patch: @@ -135,7 +135,7 @@ function createMessage(ecosystemReports: Record<string, EcosystemReport>) {
       },
     ];
 
-    for (const os of ["darwin", "linux", "windows"]) {
+    for (const os of ["linux", "darwin", "windows"]) {
       const report = ecosystemReports[os][program] satisfies PmResult;
 
       const text = `${
Repository: facebook/react
Pull request: [DevTools] Enable pointEvents while scrolling

[`react-window` disables `pointerEvents` while scrolling meaning you can't click anything while scrolling.](https://github.com/bvaughn/react-window/issues/128).

This means that the first click when you stop the scroll with inertial scrolling doesn't get registered. This is suuuper annoying. This might make sense when you click to stop on a more intentional UI but it doesn't makes sense in a list like this because we eagerly click things even on mousedown.

This PR just override that to re-enable pointer events.

Supposedly this is done for performance but that might be outdated knowledge. I haven't observed any difference so far.

If we discover that it's a perf problem, there's another technique we can use where we call `ownerDocument.elementFromPoint(e.pageX, e.pageY)` and then dispatch the event against that element. But let's try the simplest approach first?

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/Components/Tree.js
patch: @@ -586,7 +586,10 @@ function InnerElementType({children, style}) {
   // A lot of options were considered; this seemed the one that requires the least code.
   // See https://github.com/bvaughn/react-devtools-experimental/issues/9
   return (
-    <div className={styles.InnerElementType} ref={divRef} style={style}>
+    <div
+      className={styles.InnerElementType}
+      ref={divRef}
+      style={{...style, pointerEvents: null}}>
       <SelectedTreeHighlight />
       {children}
     </div>
Repository: huggingface/transformers
Pull request: Update hqq.md

Fixed a typo in documentation of hqq, quantization method


Documentation: @stevhliu




Changed files:
filename: docs/source/en/quantization/hqq.md
patch: @@ -38,7 +38,7 @@ import torch
 from transformers import AutoModelForCausalLM, AutoTokenizer, HqqConfig
 
 quant_config = HqqConfig(nbits=8, group_size=64)
-model = transformers.AutoModelForCausalLM.from_pretrained(
+model = AutoModelForCausalLM.from_pretrained(
     "meta-llama/Llama-3.1-8B", 
     dtype=torch.float16, 
     device_map="auto",
Repository: vercel/next.js
Pull request: Turbopack: Only benchmark file IO on `next dev`

I added this in https://github.com/vercel/next.js/pull/66057

It's too noisy and not useful on CI. CI machines are often multi-tenant and/or running many other processes during initialization.

We could check for `process.env.CI`, but I think just having the check in `next dev` is enough.

https://vercel.slack.com/archives/C01A2M9R8RZ/p1759349240395449

Changed files:
filename: crates/napi/src/next_api/project.rs
patch: @@ -455,34 +455,40 @@ pub fn project_new(
             }
 
             let options: ProjectOptions = options.into();
+            let is_dev = options.dev;
             let container = turbo_tasks
                 .run(async move {
-                    let project = ProjectContainer::new(rcstr!("next.js"), options.dev);
+                    let project = ProjectContainer::new(rcstr!("next.js"), is_dev);
                     let project = project.to_resolved().await?;
                     project.initialize(options).await?;
                     Ok(project)
                 })
                 .or_else(|e| turbopack_ctx.throw_turbopack_internal_result(&e.into()))
                 .await?;
 
-            Handle::current().spawn({
-                let tt = turbo_tasks.clone();
-                async move {
-                    let result = tt
-                        .clone()
-                        .run(async move {
-                            benchmark_file_io(tt, container.project().node_root().owned().await?)
+            if is_dev {
+                Handle::current().spawn({
+                    let tt = turbo_tasks.clone();
+                    async move {
+                        let result = tt
+                            .clone()
+                            .run(async move {
+                                benchmark_file_io(
+                                    tt,
+                                    container.project().node_root().owned().await?,
+                                )
                                 .await
-                        })
-                        .await;
-                    if let Err(err) = result {
-                        // TODO Not ideal to print directly to stdout.
-                        // We should use a compilation event instead to report async errors.
-                        println!("Failed to benchmark file I/O: {err}");
+                            })
+                            .await;
+                        if let Err(err) = result {
+                            // TODO Not ideal to print directly to stdout.
+                            // We should use a compilation event instead to report async errors.
+                            println!("Failed to benchmark file I/O: {err}");
+                        }
                     }
-                }
-                .instrument(tracing::info_span!("benchmark file I/O"))
-            });
+                    .instrument(tracing::info_span!("benchmark file I/O"))
+                });
+            }
 
             Ok(External::new(ProjectInstance {
                 turbopack_ctx,
Repository: ollama/ollama
Pull request: server: provide helpful workaround hint when stalling on pull

This is a quick fix to help users who are stuck on the "pull" step at 99%.

In the near future we're introducing a new registry client that should/will hopefully be smarter. In the meantime, this should unblock the users hitting issue #1736.

Changed files:
filename: server/download.go
patch: @@ -247,7 +247,8 @@ func (b *blobDownload) downloadChunk(ctx context.Context, requestURL *url.URL, w
 				}
 
 				if !part.lastUpdated.IsZero() && time.Since(part.lastUpdated) > 5*time.Second {
-					slog.Info(fmt.Sprintf("%s part %d stalled; retrying", b.Digest[7:19], part.N))
+					const msg = "%s part %d stalled; retrying. If this persists, press ctrl-c to exit, then 'ollama pull' to find a faster connection."
+					slog.Info(fmt.Sprintf(msg, b.Digest[7:19], part.N))
 					// reset last updated
 					part.lastUpdated = time.Time{}
 					return errPartStalled
Repository: huggingface/transformers
Pull request: Remove Python 3.9 classifier

# What does this PR do?

Follows recent clean-up.

Changed files:
filename: setup.py
patch: @@ -434,7 +434,7 @@ def run(self):
             "transformers=transformers.commands.transformers_cli:main",
         ]
     },
-    python_requires=">=3.9.0",
+    python_requires=">=3.10.0",
     install_requires=list(install_requires),
     classifiers=[
         "Development Status :: 5 - Production/Stable",
@@ -444,7 +444,6 @@ def run(self):
         "License :: OSI Approved :: Apache Software License",
         "Operating System :: OS Independent",
         "Programming Language :: Python :: 3",
-        "Programming Language :: Python :: 3.9",
         "Programming Language :: Python :: 3.10",
         "Programming Language :: Python :: 3.11",
         "Programming Language :: Python :: 3.12",
Repository: vercel/next.js
Pull request: telemetry track mcp server usage

* Track the `experimental.mcpServer` usage through telemetry
* Set the default mcpServer as `undefined` unless you enable through env var

Changed files:
filename: packages/next/src/server/config-shared.ts
patch: @@ -1512,7 +1512,6 @@ export const defaultConfig = Object.freeze({
     browserDebugInfoInTerminal: false,
     isolatedDevBuild:
       process.env.__NEXT_EXPERIMENTAL_ISOLATED_DEV_BUILD === 'true',
-    mcpServer: !!process.env.__NEXT_EXPERIMENTAL_MCP_SERVER,
   },
   htmlLimitedBots: undefined,
   bundlePagesRouterDependencies: false,

filename: packages/next/src/server/config.ts
patch: @@ -1116,6 +1116,13 @@ function assignDefaultsAndValidate(
     result.htmlLimitedBots = HTML_LIMITED_BOT_UA_RE_STRING
   }
 
+  if (
+    typeof result.experimental.mcpServer === 'undefined' &&
+    process.env.__NEXT_EXPERIMENTAL_MCP_SERVER === 'true'
+  ) {
+    result.experimental.mcpServer = true
+  }
+
   // "use cache" was originally implicitly enabled with the cacheComponents flag, so
   // we transfer the value for cacheComponents to the explicit useCache flag to ensure
   // backwards compatibility.

filename: packages/next/src/telemetry/events/version.ts
patch: @@ -40,6 +40,7 @@ type EventCliSessionStarted = {
   reactCompiler: boolean
   reactCompilerCompilationMode: string | null
   reactCompilerPanicThreshold: string | null
+  mcpServer: boolean | null
 }
 
 export function eventCliSession(
@@ -74,6 +75,7 @@ export function eventCliSession(
     | 'reactCompiler'
     | 'reactCompilerCompilationMode'
     | 'reactCompilerPanicThreshold'
+    | 'mcpServer'
     | 'isRspack'
   >
 ): { eventName: string; payload: EventCliSessionStarted }[] {
@@ -132,6 +134,10 @@ export function eventCliSession(
       typeof nextConfig.reactCompiler !== 'boolean'
         ? (nextConfig.reactCompiler?.panicThreshold ?? null)
         : null,
+    mcpServer:
+      typeof nextConfig.experimental.mcpServer === 'boolean'
+        ? nextConfig.experimental.mcpServer
+        : null,
   }
   return [{ eventName: EVENT_VERSION, payload }]
 }
Repository: nodejs/node
Pull request: benchmark: calibrate length of util.diff

**benchmark: calibrate length of util.diff**
```
500 + 1000 already covers the curve. 2000 doesn’t add new qualitative insight — it just extends the same curve further down (another ~3–4× slowdown).

According to https://github.com/nodejs/performance/issues/186 this benchmark takes one minute to conclude a single run. This should fix it.
```

Changed files:
filename: benchmark/util/diff.js
patch: @@ -5,7 +5,7 @@ const common = require('../common');
 
 const bench = common.createBenchmark(main, {
   n: [1e3],
-  length: [1e3, 2e3],
+  length: [500, 1000],
   scenario: ['identical', 'small-diff', 'medium-diff', 'large-diff'],
 });
Repository: ollama/ollama
Pull request: fix ci


Changed files:
filename: .github/workflows/test.yaml
patch: @@ -5,7 +5,6 @@ on:
     paths:
       - '**/*'
       - '!docs/**'
-      - '!examples/**'
       - '!README.md'
 
 jobs:

filename: app/tray/tray.go
patch: @@ -24,10 +24,5 @@ func NewTray() (commontray.OllamaTray, error) {
 		return nil, fmt.Errorf("failed to load icon %s: %w", iconName, err)
 	}
 
-	tray, err := InitPlatformTray(icon, updateIcon)
-	if err != nil {
-		return nil, err
-	}
-
-	return tray, nil
+	return InitPlatformTray(icon, updateIcon)
 }

filename: examples/go-generate-streaming/main.go
patch: @@ -5,7 +5,7 @@ import (
 	"fmt"
 	"log"
 
-	"github.com/jmorganca/ollama/api"
+	"github.com/ollama/ollama/api"
 )
 
 func main() {

filename: examples/go-generate/main.go
patch: @@ -5,7 +5,7 @@ import (
 	"fmt"
 	"log"
 
-	"github.com/jmorganca/ollama/api"
+	"github.com/ollama/ollama/api"
 )
 
 func main() {
Repository: denoland/deno
Pull request: fix(ext/node): make fsPromises.watch() a proper AsyncIterable with close()

## Summary
- The watcher returned by `node:fs/promises` `watch()` was a plain object with only `[Symbol.asyncIterator]`, missing `next()` and `return()` methods
- The returned object now properly implements the `AsyncIterator` protocol, making it directly usable with `for await...of` and cleanly stoppable via `break` or `AbortSignal`
- Improved abort signal handling (respects already-aborted signals, uses `{ once: true }`)

Fixes #23562

## Test plan
- [x] Verified `for await (const event of watcher)` works correctly
- [x] Verified `watcher.next()` and `watcher.return()` are available
- [x] Verified `Symbol.asyncIterator` is present on the returned object
- [x] Existing test `node [fs/promises] watch should return async iterable` covers this behavior

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

Changed files:
filename: ext/node/polyfills/_fs/_fs_watch.ts
patch: @@ -171,26 +171,44 @@ export function watchPromise(
   });
 
   if (options?.signal) {
-    options?.signal.addEventListener("abort", () => watcher.close());
+    if (options.signal.aborted) {
+      watcher.close();
+    } else {
+      options.signal.addEventListener(
+        "abort",
+        () => watcher.close(),
+        { once: true },
+      );
+    }
   }
 
   const fsIterable = watcher[Symbol.asyncIterator]();
-  const iterable = {
-    async next() {
-      const result = await fsIterable.next();
-      if (result.done) return result;
-
-      const eventType = convertDenoFsEventToNodeFsEvent(result.value.kind);
+  const result = {
+    async next(): Promise<
+      IteratorResult<{ eventType: string; filename: string | Buffer | null }>
+    > {
+      const iterResult = await fsIterable.next();
+      if (iterResult.done) return iterResult;
+
+      const eventType = convertDenoFsEventToNodeFsEvent(
+        iterResult.value.kind,
+      );
       return {
-        value: { eventType, filename: basename(result.value.paths[0]) },
-        done: result.done,
+        value: { eventType, filename: basename(iterResult.value.paths[0]) },
+        done: false,
       };
     },
+    // deno-lint-ignore no-explicit-any
+    return(value?: any): Promise<IteratorResult<any>> {
+      watcher.close();
+      return Promise.resolve({ value, done: true });
+    },
+    [Symbol.asyncIterator]() {
+      return this;
+    },
   };
 
-  return {
-    [Symbol.asyncIterator]: () => iterable,
-  };
+  return result;
 }
 
 type WatchFileListener = (curr: Stats, prev: Stats) => void;
Repository: electron/electron
Pull request: build: combine dependent libc patch

Backport of #47491

See that PR for details.


Notes: none

Changed files:
filename: patches/chromium/.patches
patch: @@ -138,7 +138,6 @@ ignore_parse_errors_for_resolveshortcutproperties.patch
 feat_add_signals_when_embedder_cleanup_callbacks_run_for.patch
 feat_separate_content_settings_callback_for_sync_and_async_clipboard.patch
 fix_win32_synchronous_spellcheck.patch
-fix_enable_wrap_iter_in_string_view_and_array.patch
 fix_linter_error.patch
 chore_grandfather_in_electron_views_and_delegates.patch
 refactor_patch_electron_permissiontypes_into_blink.patch

filename: patches/chromium/build_make_libcxx_abi_unstable_false_for_electron.patch
patch: @@ -5,16 +5,20 @@ Subject: build: make libcxx_abi_unstable false for electron
 
 https://nornagon.medium.com/a-libc-odyssey-973e51649063
 
+See also https://github.com/electron/electron/issues/45810#issuecomment-2691417213.
+
 diff --git a/buildtools/third_party/libc++/__config_site b/buildtools/third_party/libc++/__config_site
-index 67075bd8b4d42e6e6d651cb0988d64eccb64cc23..e240ff6fff94a6cebf8662996712fe7eb22e5fff 100644
+index 67075bd8b4d42e6e6d651cb0988d64eccb64cc23..ddf1693002aa171b3d91aa4ef08f5b360e4adddc 100644
 --- a/buildtools/third_party/libc++/__config_site
 +++ b/buildtools/third_party/libc++/__config_site
-@@ -18,7 +18,7 @@
+@@ -18,7 +18,9 @@
  //    _LIBCPP_ABI_NAMESPACE to a shorter value.
  #define _LIBCPP_ABI_NAMESPACE __Cr
  
 -#define _LIBCPP_ABI_VERSION 2
 +#define _LIBCPP_ABI_VERSION 1
++#define _LIBCPP_ABI_USE_WRAP_ITER_IN_STD_ARRAY
++#define _LIBCPP_ABI_USE_WRAP_ITER_IN_STD_STRING_VIEW
  
  #define _LIBCPP_ABI_FORCE_ITANIUM 0
  #define _LIBCPP_ABI_FORCE_MICROSOFT 0

filename: patches/chromium/fix_enable_wrap_iter_in_string_view_and_array.patch
patch: @@ -1,22 +0,0 @@
-From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
-From: deepak1556 <hop2deep@gmail.com>
-Date: Sat, 1 Mar 2025 05:11:41 +0900
-Subject: fix: enable __wrap_iter in string_view and array
-
-Refs https://github.com/electron/electron/issues/45810#issuecomment-2691417213
-
-Patch can be removed when build_make_libcxx_abi_unstable_false_for_electron.patch is removed.
-
-diff --git a/buildtools/third_party/libc++/__config_site b/buildtools/third_party/libc++/__config_site
-index e240ff6fff94a6cebf8662996712fe7eb22e5fff..ddf1693002aa171b3d91aa4ef08f5b360e4adddc 100644
---- a/buildtools/third_party/libc++/__config_site
-+++ b/buildtools/third_party/libc++/__config_site
-@@ -19,6 +19,8 @@
- #define _LIBCPP_ABI_NAMESPACE __Cr
- 
- #define _LIBCPP_ABI_VERSION 1
-+#define _LIBCPP_ABI_USE_WRAP_ITER_IN_STD_ARRAY
-+#define _LIBCPP_ABI_USE_WRAP_ITER_IN_STD_STRING_VIEW
- 
- #define _LIBCPP_ABI_FORCE_ITANIUM 0
- #define _LIBCPP_ABI_FORCE_MICROSOFT 0
Repository: facebook/react
Pull request: feat(compiler): Ignore `TSInterfaceDeclaration`

## Summary

The following was not supported:
```ts
function A() {
  interface C {
    id: number;
  }
  return 0;
}
```

Message:
> Todo: (BuildHIR::lowerStatement) Handle TSInterfaceDeclaration statements (2:4)

Playground:
https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAggBQCURwAOsUXpjgjGgIaJEDC1dR-DACbIimKAFsARiwDcfIgF95MBDljEADHMwKQCoA

This PR fixes that.

## How did you test this change?
Added a test.

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/BuildHIR.ts
patch: @@ -1332,6 +1332,7 @@ function lowerStatement(
       return;
     }
     case "TypeAlias":
+    case "TSInterfaceDeclaration":
     case "TSTypeAliasDeclaration": {
       // We do not preserve type annotations/syntax through transformation
       return;
@@ -1358,7 +1359,6 @@ function lowerStatement(
     case "TSEnumDeclaration":
     case "TSExportAssignment":
     case "TSImportEqualsDeclaration":
-    case "TSInterfaceDeclaration":
     case "TSModuleDeclaration":
     case "TSNamespaceExportDeclaration":
     case "WithStatement": {

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/ignore-inner-interface-types.expect.md
patch: @@ -0,0 +1,35 @@
+
+## Input
+
+```javascript
+function Foo() {
+  type X = number;
+  interface Bar {
+    baz: number;
+  }
+  return 0;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
+
+```
+
+## Code
+
+```javascript
+function Foo() {
+  return 0;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
+
+```
+      
+### Eval output
+(kind: ok) 0
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/ignore-inner-interface-types.ts
patch: @@ -0,0 +1,12 @@
+function Foo() {
+  type X = number;
+  interface Bar {
+    baz: number;
+  }
+  return 0;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
Repository: ollama/ollama
Pull request: examples: start adding Go examples using api/

We can have the same examples as e.g. https://github.com/ollama/ollama-python/tree/main/examples here. Using consistent naming and renaming the existing example to have -http- since it uses direct HTTP requests rather than api/

Updates #2840

Changed files:
filename: examples/go-generate-streaming/main.go
patch: @@ -0,0 +1,40 @@
+package main
+
+import (
+	"context"
+	"fmt"
+	"log"
+
+	"github.com/jmorganca/ollama/api"
+)
+
+func main() {
+	client, err := api.ClientFromEnvironment()
+	if err != nil {
+		log.Fatal(err)
+	}
+
+	// By default, GenerateRequest is streaming.
+	req := &api.GenerateRequest{
+		Model:  "gemma",
+		Prompt: "how many planets are there?",
+	}
+
+	ctx := context.Background()
+	respFunc := func(resp api.GenerateResponse) error {
+		// Only print the response here; GenerateResponse has a number of other
+		// interesting fields you want to examine.
+
+		// In streaming mode, responses are partial so we call fmt.Print (and not
+		// Println) in order to avoid spurious newlines being introduced. The
+		// model will insert its own newlines if it wants.
+		fmt.Print(resp.Response)
+		return nil
+	}
+
+	err = client.Generate(ctx, req, respFunc)
+	if err != nil {
+		log.Fatal(err)
+	}
+	fmt.Println()
+}

filename: examples/go-generate/main.go
patch: @@ -0,0 +1,37 @@
+package main
+
+import (
+	"context"
+	"fmt"
+	"log"
+
+	"github.com/jmorganca/ollama/api"
+)
+
+func main() {
+	client, err := api.ClientFromEnvironment()
+	if err != nil {
+		log.Fatal(err)
+	}
+
+	req := &api.GenerateRequest{
+		Model:  "gemma",
+		Prompt: "how many planets are there?",
+
+		// set streaming to false
+		Stream: new(bool),
+	}
+
+	ctx := context.Background()
+	respFunc := func(resp api.GenerateResponse) error {
+		// Only print the response here; GenerateResponse has a number of other
+		// interesting fields you want to examine.
+		fmt.Println(resp.Response)
+		return nil
+	}
+
+	err = client.Generate(ctx, req, respFunc)
+	if err != nil {
+		log.Fatal(err)
+	}
+}
Repository: ggml-org/llama.cpp
Pull request: cmake: link ws2_32 for MinGW/w64devkit builds in cpp-httplib

Small linker fix to allow the procedure described in [build.md](https://github.com/ggml-org/llama.cpp/blob/master/docs/build.md) to work correctly using w64devkit.

Missing link found with Claude and corrected with Gemini.

Changed files:
filename: vendor/cpp-httplib/CMakeLists.txt
patch: @@ -9,6 +9,10 @@ if (NOT MSVC)
 endif()
 
 target_link_libraries  (${TARGET} PRIVATE Threads::Threads)
+
+if (WIN32 AND NOT MSVC)
+    target_link_libraries(${TARGET} PUBLIC ws2_32)
+endif()
 target_compile_features(${TARGET} PRIVATE cxx_std_17)
 
 target_compile_definitions(${TARGET} PRIVATE