helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Assign name to hydration stream

This allows React DevTools to show a name for this which doesn't have a url like the fetches.

Also, don't set startTime for client resume fetch. The start time for this data didn't start on the server as an MPA nav. The start of the fetch actually is a waterfall and should be shown as such.

Changed files:
filename: packages/next/src/client/app-index.tsx
patch: @@ -163,6 +163,10 @@ const readable = new ReadableStream({
     nextServerDataRegisterWriter(controller)
   },
 })
+if (process.env.NODE_ENV !== 'production') {
+  // @ts-expect-error
+  readable.name = 'hydration'
+}
 
 let debugChannel:
   | { readable?: ReadableStream; writable?: WritableStream }
@@ -190,8 +194,6 @@ if (clientResumeFetch) {
       callServer,
       findSourceMapURL,
       debugChannel,
-      // @ts-expect-error This is not yet part of the React types
-      startTime: 0,
     })
   ).then(async (fallbackInitialRSCPayload) =>
     createInitialRSCPayloadFromFallbackPrerender(
Repository: nodejs/node
Pull request: doc,crypto: reorder ML-KEM in the asymmetric key types table

Order ML-KEM by security strength not by alphabetical order.

Changed files:
filename: doc/api/crypto.md
patch: @@ -87,9 +87,9 @@ The following table lists the asymmetric key types recognized by the [`KeyObject
 | `'ml-dsa-44'`[^openssl35]          | ML-DSA-44          | 2.16.840.1.101.3.4.3.17 |
 | `'ml-dsa-65'`[^openssl35]          | ML-DSA-65          | 2.16.840.1.101.3.4.3.18 |
 | `'ml-dsa-87'`[^openssl35]          | ML-DSA-87          | 2.16.840.1.101.3.4.3.19 |
-| `'ml-kem-1024'`[^openssl35]        | ML-KEM-1024        | 2.16.840.1.101.3.4.4.3  |
 | `'ml-kem-512'`[^openssl35]         | ML-KEM-512         | 2.16.840.1.101.3.4.4.1  |
 | `'ml-kem-768'`[^openssl35]         | ML-KEM-768         | 2.16.840.1.101.3.4.4.2  |
+| `'ml-kem-1024'`[^openssl35]        | ML-KEM-1024        | 2.16.840.1.101.3.4.4.3  |
 | `'rsa-pss'`                        | RSA PSS            | 1.2.840.113549.1.1.10   |
 | `'rsa'`                            | RSA                | 1.2.840.113549.1.1.1    |
 | `'slh-dsa-sha2-128f'`[^openssl35]  | SLH-DSA-SHA2-128f  | 2.16.840.1.101.3.4.3.21 |
Repository: ollama/ollama
Pull request: Add instructions to easily install specific versions on faq.md

This PR adds a new question to faq.md on how to install specific versions of ollama using `VER_PARAM` env variable. 

Might be useful when trying to install release candidates versions or switching between versions easily, and I could not find any info on how to do that in the current docs.

Changed files:
filename: docs/linux.md
patch: @@ -100,6 +100,16 @@ sudo curl -L https://ollama.com/download/ollama-linux-amd64 -o /usr/bin/ollama
 sudo chmod +x /usr/bin/ollama
 ```
 
+## Installing specific versions
+
+Use `OLLAMA_VERSION` environment variable with the install script to install a specific version of Ollama, including pre-releases. You can find the version numbers in the [releases page](https://github.com/ollama/ollama/releases). 
+
+For example:
+
+```
+curl -fsSL https://ollama.com/install.sh | OLLAMA_VERSION=0.1.32 sh
+```
+
 ## Viewing logs
 
 To view logs of Ollama running as a startup service, run:
Repository: facebook/react
Pull request: Add Bridge types for Fusebox

New types used by Fusebox https://github.com/facebookexperimental/rn-chrome-devtools-frontend/pull/117

Changed files:
filename: packages/react-devtools-fusebox/src/frontend.d.ts
patch: @@ -15,7 +15,9 @@ export type Wall = {
 };
 
 export type Bridge = {
-  shutdown: () => void,
+  addListener(event: string, listener: (params: unknown) => any): void;
+  removeListener(event: string, listener: Function): void;
+  shutdown: () => void;
 };
 export type Store = Object;
 export type BrowserTheme = 'dark' | 'light';
Repository: nodejs/node
Pull request: src: remove unused variables from report

This PR removes unused variables in `node_report.cc` detected by clang-tidy(`bugprone-unused-local-non-trivial-variable`).

Changed files:
filename: src/node_report.cc
patch: @@ -757,7 +757,6 @@ static void PrintSystemInformation(JSONWriter* writer) {
 
   writer->json_objectstart("userLimits");
   struct rlimit limit;
-  std::string soft, hard;
 
   for (size_t i = 0; i < arraysize(rlimit_strings); i++) {
     if (getrlimit(rlimit_strings[i].id, &limit) == 0) {
@@ -793,8 +792,6 @@ static void PrintLoadedLibraries(JSONWriter* writer) {
 
 // Obtain and report the node and subcomponent version strings.
 static void PrintComponentVersions(JSONWriter* writer) {
-  std::stringstream buf;
-
   writer->json_objectstart("componentVersions");
 
   for (const auto& version : per_process::metadata.versions.pairs()) {
Repository: ollama/ollama
Pull request: Error handling load_single_document() in ingest.py

load_single_document() handles
- corrupt files
- empty (zero byte) files
- unsupported file extensions

Changed files:
filename: examples/langchain-python-rag-privategpt/ingest.py
patch: @@ -77,13 +77,21 @@ def load(self) -> List[Document]:
 
 
 def load_single_document(file_path: str) -> List[Document]:
-    ext = "." + file_path.rsplit(".", 1)[-1]
-    if ext in LOADER_MAPPING:
-        loader_class, loader_args = LOADER_MAPPING[ext]
-        loader = loader_class(file_path, **loader_args)
-        return loader.load()
+    if os.path.getsize(file_path) != 0:
+        filename, ext = os.path.splitext(file_path)
+        if ext in LOADER_MAPPING:
+            loader_class, loader_args = LOADER_MAPPING[ext]
+            try:
+                loader = loader_class(file_path, **loader_args)
+                if loader:
+                    return loader.load()
+            except:
+                print(f"Corrupted file {file_path}. Ignoring it.")
+        else:
+            print(f"Unsupported file {file_path}. Ignoring it.")
+    else:
+        print(f"Empty file {file_path}. Ignoring it.")
 
-    raise ValueError(f"Unsupported file extension '{ext}'")
 
 def load_documents(source_dir: str, ignored_files: List[str] = []) -> List[Document]:
     """
@@ -100,7 +108,8 @@ def load_documents(source_dir: str, ignored_files: List[str] = []) -> List[Docum
         results = []
         with tqdm(total=len(filtered_files), desc='Loading new documents', ncols=80) as pbar:
             for i, docs in enumerate(pool.imap_unordered(load_single_document, filtered_files)):
-                results.extend(docs)
+                if docs:
+                    results.extend(docs)
                 pbar.update()
 
     return results
Repository: ollama/ollama
Pull request: added new community integration (headless-ollama)

ollama makes it wonderfully easy to build desktop apps that rely on local LLMs with its js and python libraries.

> however, the user's system needs to have ollama already installed for the desktop app to use the libraries and make calls to the LLMs. Making users install ollama client separately isn't good UX tbh. thus, "headless-ollama"

this repo has pre-run scripts which automatically utilises node runtime to check for the host OS and installs the ollama client and the models needed by the desktop app before the server starts.

this is really helpful while building desktop apps where you want everything to be local and self contained within the system.

Changed files:
filename: README.md
patch: @@ -382,6 +382,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [AI ST Completion](https://github.com/yaroslavyaroslav/OpenAI-sublime-text) (Sublime Text 4 AI assistant plugin with Ollama support)
 - [Discord-Ollama Chat Bot](https://github.com/kevinthedang/discord-ollama) (Generalized TypeScript Discord Bot w/ Tuning Documentation)
 - [Discord AI chat/moderation bot](https://github.com/rapmd73/Companion) Chat/moderation bot written in python. Uses Ollama to create personalities.
+- [Headless Ollama](https://github.com/nischalj10/headless-ollama) (Scripts to automatically install ollama client & models on any OS for apps that depends on ollama server)
 
 ### Supported backends
Repository: denoland/deno
Pull request: fix(ext/node): drain pending messages before emitting worker exit event

- Fixes a race condition in `worker_threads` where the `exit` event could fire before pending `message` events were delivered
- In Node.js, `message` is guaranteed to fire before `exit` — our implementation had two independent polling loops (`#pollControl` and `#pollMessages`) that raced against each other
- Fix: `await` the message loop promise in `#pollControl` before emitting `exit`, ensuring all pending messages are drained first

Fixes flaky `test-worker-sharedarraybuffer-from-worker-thread.js` node_compat test.

Changed files:
filename: ext/node/polyfills/worker_threads.ts
patch: @@ -208,6 +208,7 @@ class NodeWorker extends EventEmitter {
   #refed = true;
   #messagePromise = undefined;
   #controlPromise = undefined;
+  #messageLoopPromise = undefined;
   #workerOnline = false;
   #exited = false;
   // "RUNNING" | "CLOSED" | "TERMINATED"
@@ -497,7 +498,7 @@ class NodeWorker extends EventEmitter {
     }
 
     this.#pollControl();
-    this.#pollMessages();
+    this.#messageLoopPromise = this.#pollMessages();
     process.nextTick(() => process.emit("worker", this));
   }
 
@@ -573,6 +574,9 @@ class NodeWorker extends EventEmitter {
             err.stack = undefined;
             this.emit("error", err);
           }
+          // Drain pending messages before emitting exit so that
+          // all 'message' events fire before 'exit' (Node.js behavior).
+          await this.#messageLoopPromise;
           this.resourceLimits = {};
           if (!this.#exited) {
             this.#exited = true;
@@ -588,6 +592,9 @@ class NodeWorker extends EventEmitter {
           debugWT(`Host got "close" message from worker: ${this.#name}`);
           this.#status = "CLOSED";
           this.#closeStdio();
+          // Drain pending messages before emitting exit so that
+          // all 'message' events fire before 'exit' (Node.js behavior).
+          await this.#messageLoopPromise;
           this.resourceLimits = {};
           if (!this.#exited) {
             this.#exited = true;
Repository: vercel/next.js
Pull request: [upgrade] Version gate adding `--turbopack` flag

`--turbopack` flag is not needed for v16 upgrade.

Changed files:
filename: packages/next-codemod/bin/upgrade.ts
patch: @@ -188,7 +188,10 @@ export async function runUpgrade(
         `react@${targetNextPackageJson.peerDependencies['react']}`
       )
 
-  if (compareVersions(targetNextVersion, '15.0.0-canary') >= 0) {
+  if (
+    compareVersions(targetNextVersion, '15.0.0-canary') >= 0 &&
+    compareVersions(targetNextVersion, '16.0.0-canary') < 0
+  ) {
     await suggestTurbopack(appPackageJson, targetNextVersion)
   }
Repository: nodejs/node
Pull request: test: mark test-web-locks skip on IBM i

For the test-weblocks test it check the rss memory before and after but on IBM i this is always set to 0 from libuv

Reference:
https://github.com/nodejs/node/blob/d2ff9daf589af059cacd58972640c8dbc6c7ba88/src/node_process_methods.cc#L229-L233
https://github.com/libuv/libuv/commit/8813dca3883bb808e33e947c8784ffe16792ca94

So, this test case can be skipped for now

Changed files:
filename: test/parallel/parallel.status
patch: @@ -139,6 +139,7 @@ test-inspector-network-content-type: SKIP
 test-fetch:  SKIP
 test-without-async-context-frame: SKIP
 test-process-cpuUsage: PASS, FLAKY
+test-web-locks: SKIP
 
 
 [$asan==on]
Repository: facebook/react
Pull request: [DevTools] Fix React Compiler badging


In #31140 we switched over the uMC polyfill to use memo instead of state since memo would FastRefresh properly. However this busted devtools' badging of compiled components; this PR fixes it.

TODO: tests
Co-authored-by: Ruslan Lesiutin <rdlesyutin@gmail.com>


Changed files:
filename: packages/react-devtools-shared/src/backend/fiber/renderer.js
patch: @@ -599,6 +599,8 @@ export function getInternalReactConstants(version: string): {
       !shouldSkipForgetCheck &&
       // $FlowFixMe[incompatible-type] fiber.updateQueue is mixed
       (fiber.updateQueue?.memoCache != null ||
+        (Array.isArray(fiber.memoizedState?.memoizedState) &&
+          fiber.memoizedState.memoizedState[0]?.[REACT_MEMO_CACHE_SENTINEL]) ||
         fiber.memoizedState?.memoizedState?.[REACT_MEMO_CACHE_SENTINEL])
     ) {
       const displayNameWithoutForgetWrapper = getDisplayNameForFiber(
Repository: ollama/ollama
Pull request: llm: always add bos token to prompt

Carries https://github.com/ollama/ollama/pull/4399

Fixes issues with embeddings not working because `bos` tokens were omitted from the prompt

Thank you @deadbeef84 for finding and fixing this.

Fixes https://github.com/ollama/ollama/issues/4207
Fixes https://github.com/ollama/ollama/issues/3777

Changed files:
filename: llm/ext_server/server.cpp
patch: @@ -835,7 +835,7 @@ struct llama_server_context
         system_tokens.clear();
 
         if (!system_prompt.empty()) {
-            system_tokens = ::llama_tokenize(ctx, system_prompt, add_bos_token);
+            system_tokens = ::llama_tokenize(ctx, system_prompt, true);
 
             llama_batch_clear(batch);
 
@@ -1656,7 +1656,7 @@ struct llama_server_context
                     slot.t_start_process_prompt = ggml_time_us();
                     slot.t_start_genereration = 0;
 
-                    prompt_tokens = tokenize(slot.prompt, system_prompt.empty() && add_bos_token);  // add BOS if there isn't system prompt
+                    prompt_tokens = tokenize(slot.prompt, system_prompt.empty());  // add BOS if there isn't system prompt
 
                     slot.n_prompt_tokens = prompt_tokens.size();
Repository: denoland/deno
Pull request: fix(ext/node): fix BadResource error in FileHandle.readLines()

## Summary

- Fixes #32678
- `FileHandle.createReadStream()` now passes the FileHandle object (not numeric fd) to ReadStream/WriteStream, matching Node.js behavior
- Added `FileHandleOperations` wrapper in `importFd()` that bridges FileHandle's promise-based methods to the callback-based stream internals, enabling proper lifecycle coordination via ref-counting

## Test plan

- [x] Added unit test: close after `readLines()` should not throw
- [x] Added unit test: iterating `readLines()` returns correct lines
- [x] `./x test-node fs_test` passes
- [x] Manual verification of `createReadStream` with FileHandle

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Changed files:
filename: ext/node/polyfills/internal/fs/handle.ts
patch: @@ -318,7 +318,7 @@ export class FileHandle extends EventEmitter {
 
   readLines(options?: CreateReadStreamOptions): ReadlineInterface {
     return createInterface({
-      input: this.createReadStream({ ...options, autoClose: false }),
+      input: this.createReadStream(options),
       crlfDelay: Infinity,
     });
   }

filename: tests/unit_node/fs_test.ts
patch: @@ -1740,6 +1740,42 @@ Deno.test({
   },
 });
 
+Deno.test({
+  name:
+    "[node/fs/promises FileHandle.readLines] close after readLines should not throw",
+  async fn() {
+    const tempFile = Deno.makeTempFileSync();
+    Deno.writeTextFileSync(tempFile, "line one\nline two\nline three\n");
+    try {
+      const fd = await open(tempFile, "r");
+      fd.readLines();
+      await fd.close();
+    } finally {
+      Deno.removeSync(tempFile);
+    }
+  },
+});
+
+Deno.test({
+  name:
+    "[node/fs/promises FileHandle.readLines] should iterate lines correctly",
+  async fn() {
+    const tempFile = Deno.makeTempFileSync();
+    Deno.writeTextFileSync(tempFile, "line one\nline two\nline three\n");
+    try {
+      const fd = await open(tempFile, "r");
+      const lines: string[] = [];
+      for await (const line of fd.readLines()) {
+        lines.push(line);
+      }
+      assertEquals(lines, ["line one", "line two", "line three"]);
+      await fd.close();
+    } finally {
+      Deno.removeSync(tempFile);
+    }
+  },
+});
+
 Deno.test(
   "[node/fs Dir] Dir is disposable via Symbol.dispose",
   { permissions: { read: true } },
Repository: vercel/next.js
Pull request: Remove layout-router sticky/fixed debug warning

Fixes an issue that reproduces due to a combination of the log forwarding logic alongside logging out an explicit element. We can add this back in the future once our log forwarding library properly ignores non-enumerable properties. 

Changed files:
filename: packages/next/src/client/components/layout-router.tsx
patch: @@ -140,12 +140,6 @@ function shouldSkipElement(element: HTMLElement) {
   // and will result in a situation we bail on scroll because of something like a fixed nav,
   // even though the actual page content is offscreen
   if (['sticky', 'fixed'].includes(getComputedStyle(element).position)) {
-    if (process.env.NODE_ENV === 'development') {
-      console.warn(
-        'Skipping auto-scroll behavior due to `position: sticky` or `position: fixed` on element:',
-        element
-      )
-    }
     return true
   }
 

filename: test/e2e/app-dir/router-autoscroll/router-autoscroll.test.ts
patch: @@ -197,20 +197,6 @@ describe('router autoscrolling on navigation', () => {
         .click()
         .waitForElementByCss('#content-that-is-visible')
       await check(() => browser.eval('window.scrollY'), 0)
-
-      if (isNextDev) {
-        // Check that we've logged a warning
-        await check(async () => {
-          const logs = await browser.log()
-          return logs.some((log) =>
-            log.message.includes(
-              'Skipping auto-scroll behavior due to `position: sticky` or `position: fixed` on element:'
-            )
-          )
-            ? 'success'
-            : undefined
-        }, 'success')
-      }
     })
 
     it('Should scroll to the top of the layout when the first child is position sticky', async () => {
@@ -221,20 +207,6 @@ describe('router autoscrolling on navigation', () => {
         .click()
         .waitForElementByCss('#content-that-is-visible')
       await check(() => browser.eval('window.scrollY'), 0)
-
-      if (isNextDev) {
-        // Check that we've logged a warning
-        await check(async () => {
-          const logs = await browser.log()
-          return logs.some((log) =>
-            log.message.includes(
-              'Skipping auto-scroll behavior due to `position: sticky` or `position: fixed` on element:'
-            )
-          )
-            ? 'success'
-            : undefined
-        }, 'success')
-      }
     })
 
     it('Should apply scroll when loading.js is used', async () => {
Repository: electron/electron
Pull request: fix: allow importing from electron/utility at runtime

Backport of #47968

See that PR for details.


Notes: Fixed an issue where importing  from `electron/utility` threw a `ERR_MODULE_NOT_FOUND` error at runtime <!-- 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: lib/common/init.ts
patch: @@ -93,20 +93,23 @@ makeElectronModule('electron');
 makeElectronModule('electron/common');
 if (process.type === 'browser') {
   makeElectronModule('electron/main');
-}
-if (process.type === 'renderer') {
+} else if (process.type === 'renderer') {
   makeElectronModule('electron/renderer');
+} else if (process.type === 'utility') {
+  makeElectronModule('electron/utility');
 }
 
 const originalResolveFilename = Module._resolveFilename;
 
-// 'electron/main', 'electron/renderer' and 'electron/common' are module aliases
+// 'electron/{common,main,renderer,utility}' are module aliases
 // of the 'electron' module for TypeScript purposes, i.e., the types for
 // 'electron/main' consist of only main process modules, etc. It is intentional
 // that these can be `require()`-ed from both the main process as well as the
 // renderer process regardless of the names, they're superficial for TypeScript
 // only.
-const electronModuleNames = new Set(['electron', 'electron/main', 'electron/renderer', 'electron/common']);
+const electronModuleNames = new Set([
+  'electron', 'electron/main', 'electron/renderer', 'electron/common', 'electron/utility'
+]);
 Module._resolveFilename = function (request, parent, isMain, options) {
   if (electronModuleNames.has(request)) {
     return 'electron';

filename: lib/utility/api/net.ts
patch: @@ -1,8 +1,7 @@
 import { fetchWithSession } from '@electron/internal/browser/api/net-fetch';
 import { ClientRequest } from '@electron/internal/common/api/net-client-request';
 
-import { IncomingMessage } from 'electron/utility';
-import type { ClientRequestConstructorOptions } from 'electron/utility';
+import type { ClientRequestConstructorOptions, IncomingMessage } from 'electron/utility';
 
 const { isOnline, resolveHost } = process._linkedBinding('electron_common_net');
Repository: huggingface/transformers
Pull request: Move the Mi355 to regular docker

Currently, the Mi355 workflow depends on an old docker container `huggingface/testing-rocm7.0-preview`
With recent changes (#41792) the regular AMD docker should work on both Mi325 and Mi355. 
To avoid bugs, this PR changes the workflow to use the regular AMD docker. 

Changed files:
filename: .github/workflows/self-scheduled-amd-mi355-caller.yml
patch: @@ -21,7 +21,7 @@ jobs:
       job: run_models_gpu
       slack_report_channel: "#amd-hf-ci"
       runner_group: hfc-amd-mi355
-      docker: huggingface/testing-rocm7.0-preview
+      docker: huggingface/transformers-pytorch-amd-gpu
       ci_event: Scheduled CI (AMD) - mi355
       report_repo_id: hf-transformers-bot/transformers-ci-dummy
     secrets: inherit
@@ -33,7 +33,7 @@ jobs:
       job: run_pipelines_torch_gpu
       slack_report_channel: "#amd-hf-ci"
       runner_group: hfc-amd-mi355
-      docker: huggingface/testing-rocm7.0-preview
+      docker: huggingface/transformers-pytorch-amd-gpu
       ci_event: Scheduled CI (AMD) - mi355
       report_repo_id: hf-transformers-bot/transformers-ci-dummy
     secrets: inherit
@@ -45,7 +45,7 @@ jobs:
       job: run_examples_gpu
       slack_report_channel: "#amd-hf-ci"
       runner_group: hfc-amd-mi355
-      docker: huggingface/testing-rocm7.0-preview
+      docker: huggingface/transformers-pytorch-amd-gpu
       ci_event: Scheduled CI (AMD) - mi355
       report_repo_id: hf-transformers-bot/transformers-ci-dummy
     secrets: inherit

filename: docker/transformers-pytorch-amd-gpu/Dockerfile
patch: @@ -39,7 +39,7 @@ RUN python3 -m pip install --no-cache-dir "torchcodec==0.5"
 # Install flash attention from source. Tested with commit 6387433156558135a998d5568a9d74c1778666d8
 RUN git clone https://github.com/ROCm/flash-attention/ -b tridao && \
     cd flash-attention && \
-    GPU_ARCHS="gfx942;gfx950" python setup.py install  
-# GPU_ARCHS builds for MI300, MI325 and MI355
+    GPU_ARCHS="gfx942" python setup.py install  
+# GPU_ARCHS builds for MI300, MI325 but not MI355: we would need to add `;gfx950` but it takes too long to build.
 
 RUN python3 -m pip install --no-cache-dir einops