helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: build: add patch conflict resolution workflow with CI artifacts

Backport of #50235

See that PR for details.


Notes: none

Changed files:
filename: .github/workflows/apply-patches.yml
patch: @@ -71,3 +71,10 @@ jobs:
       uses: ./src/electron/.github/actions/checkout
       with:
         target-platform: linux
+    - name: Upload Patch Conflict Fix
+      if: ${{ failure() }}
+      uses: actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f # v7.0.0
+      with:
+        name: update-patches
+        path: patches/update-patches.patch
+        if-no-files-found: ignore

filename: CLAUDE.md
patch: @@ -127,6 +127,22 @@ patches/{target}/*.patch  →  [e sync --3]  →  target repo commits
 2. Create a git commit
 3. Run `e patches <target>` to export
 
+**Fixing patch conflicts on an existing PR:**
+
+If asked to fix a patch conflict on a branch that already has an open PR, check the PR's failed **Apply Patches** CI run for an `update-patches` artifact before running `e sync` locally. CI has already performed the 3-way merge and exported the resolved patch diff — applying it is much faster than a full local sync.
+
+```bash
+# Find the failed Apply Patches run for the PR and download the artifact
+gh run list --repo electron/electron --branch <pr-branch> --workflow "Apply Patches" --limit 1
+gh run download <run-id> --repo electron/electron --name update-patches
+
+# Apply the CI-generated fix, then push
+git am update-patches.patch
+git push
+```
+
+If no artifact exists (e.g. the 3-way merge itself failed), fall back to `e sync --3` and resolve manually.
+
 ## Testing
 
 **Test location:** `spec/` directory
Repository: facebook/react
Pull request: [DevTools] Adjust the rects size by one pixel smaller

This ensures that the outline of a previous rectangle lines up on the same pixel as the next rectangle so that they appear consecutive.

<img width="244" height="51" alt="Screenshot 2025-10-16 at 11 35 32 AM" src="https://github.com/user-attachments/assets/75ffde6f-8cc6-49c1-8855-3953569546b4" />

I don't love this implementation. There's probably a smarter way. Was trying to avoid adding another element.


Changed files:
filename: packages/react-devtools-shared/src/devtools/views/SuspenseTab/SuspenseRects.js
patch: @@ -36,12 +36,14 @@ function ScaledRect({
   rect,
   visible,
   suspended,
+  adjust,
   ...props
 }: {
   className: string,
   rect: Rect,
   visible: boolean,
   suspended: boolean,
+  adjust?: boolean,
   ...
 }): React$Node {
   const viewBox = useContext(ViewBox);
@@ -57,8 +59,9 @@ function ScaledRect({
       data-visible={visible}
       data-suspended={suspended}
       style={{
-        width,
-        height,
+        // Shrink one pixel so that the bottom outline will line up with the top outline of the next one.
+        width: adjust ? 'calc(' + width + ' - 1px)' : width,
+        height: adjust ? 'calc(' + height + ' - 1px)' : height,
         top: y,
         left: x,
       }}
@@ -160,6 +163,7 @@ function SuspenseRects({
                 className={styles.SuspenseRectsRect}
                 rect={rect}
                 data-highlighted={selected}
+                adjust={true}
                 onClick={handleClick}
                 onDoubleClick={handleDoubleClick}
                 onPointerOver={handlePointerOver}
Repository: facebook/react
Pull request: [DevTools] Remove steps title from scrubber

The hover now has a reach tooltip for the "environment" instead.

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/SuspenseTab/SuspenseTimeline.js
patch: @@ -160,9 +160,7 @@ function SuspenseTimelineInput() {
         onClick={skipForward}>
         <ButtonIcon type={'skip-next'} />
       </Button>
-      <div
-        className={styles.SuspenseTimelineInput}
-        title={timelineIndex + '/' + max}>
+      <div className={styles.SuspenseTimelineInput}>
         <SuspenseScrubber
           min={min}
           max={max}
Repository: huggingface/transformers
Pull request: Fix failing `DepthProModelIntegrationTest`

# What does this PR do?
Fixes this failing [DepthProModelIntegrationTest](https://github.com/huggingface/transformers/actions/runs/22606636929/job/65500453624#step:14:4893).

<img width="2231" height="99" alt="image" src="https://github.com/user-attachments/assets/455f0a76-c40d-43d8-b8f0-1817632afa64" />


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?
@Rocketknight1 @vasqu

Changed files:
filename: tests/models/depth_pro/test_modeling_depth_pro.py
patch: @@ -311,7 +311,7 @@ class DepthProModelIntegrationTest(unittest.TestCase):
     def test_inference_depth_estimation(self):
         model_path = "apple/DepthPro-hf"
         image_processor = DepthProImageProcessor.from_pretrained(model_path)
-        model = DepthProForDepthEstimation.from_pretrained(model_path).to(torch_device)
+        model = DepthProForDepthEstimation.from_pretrained(model_path, dtype=torch.float32).to(torch_device)
         config = model.config
 
         image = prepare_img()
Repository: ollama/ollama
Pull request: Fix incorrect header for community integrations


Changed files:
filename: README.md
patch: @@ -640,5 +640,5 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Langfuse](https://langfuse.com/docs/integrations/ollama) is an open source LLM observability platform that enables teams to collaboratively monitor, evaluate and debug AI applications.
 - [MLflow Tracing](https://mlflow.org/docs/latest/llms/tracing/index.html#automatic-tracing) is an open source LLM observability tool with a convenient API to log and visualize traces, making it easy to debug and evaluate GenAI applications.
 
-## Security
+### Security
 - [Ollama Fortress](https://github.com/ParisNeo/ollama_proxy_server)
Repository: ollama/ollama
Pull request: ci: fix win vulkan


Changed files:
filename: .github/workflows/release.yaml
patch: @@ -192,7 +192,7 @@ jobs:
           Enter-VsDevShell -VsInstallPath 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise' -SkipAutomaticLocation  -DevCmdArguments '-arch=x64 -no_logo'
           cmake --preset "${{ matrix.preset }}" ${{ matrix.flags }} --install-prefix "$((pwd).Path)\dist\${{ matrix.os }}-${{ matrix.arch }}"
           cmake --build --parallel ([Environment]::ProcessorCount) --preset "${{ matrix.preset }}"
-          cmake --install build --component "${{ startsWith(matrix.preset, 'CUDA ') && 'CUDA' || startsWith(matrix.preset, 'ROCm ') && 'HIP' || 'CPU' }}" --strip
+          cmake --install build --component "${{ startsWith(matrix.preset, 'CUDA ') && 'CUDA' || startsWith(matrix.preset, 'ROCm ') && 'HIP' || startsWith(matrix.preset, 'Vulkan') && 'Vulkan' || 'CPU' }}" --strip
           Remove-Item -Path dist\lib\ollama\rocm\rocblas\library\*gfx906* -ErrorAction SilentlyContinue
         env:
           CMAKE_GENERATOR: Ninja
Repository: vercel/next.js
Pull request: [turbopack] Don't schedule idle snapshots when we are in a short session

In a few `next build` commands i saw multiple snapshots due to this.  Idle callbacks were firing near the end of the build.

```
  Creating an optimized production build ...
WARNING: The git repository is dirty, but File System Cache is still enabled. Manual removal of the filesystem cache database might be required.
✓ Finished writing to filesystem cache because: idle timeout in 6.1s
✓ Compiled successfully in 69s
✓ Collecting page data using 13 workers in 85ms
  Build ran with "compile" mode, to finalize the build run either "generate" or "generate-env" mode as well
✓ Finalizing page optimization in 32ms
Route (app)
...ommitted route table...
✓ Finished writing to filesystem cache because: stop in 3.5s
```

This is a bit wasteful since it is more efficient to write everything in a single batch at the end.

The solution is just to not schedule snapshotting operations in 'short sessions' (aka `next build`)

Changed files:
filename: crates/next-napi-bindings/src/next_api/turbopack_ctx.rs
patch: @@ -223,7 +223,7 @@ pub fn create_turbo_tasks(
             BackendOptions {
                 storage_mode: Some(if std::env::var("TURBO_ENGINE_READ_ONLY").is_ok() {
                     turbo_tasks_backend::StorageMode::ReadOnly
-                } else if is_ci {
+                } else if is_ci || is_short_session {
                     turbo_tasks_backend::StorageMode::ReadWriteOnShutdown
                 } else {
                     turbo_tasks_backend::StorageMode::ReadWrite
Repository: rust-lang/rust
Pull request: [libcore] Disable `doc(auto_cfg)` for integers trait impls

Fixes rust-lang/rust#153655.

Thanks to https://github.com/rust-lang/rust/pull/153964, `doc(auto_cfg)` finally works as expected on impls. So now this fix works:

<img width="1000" height="806" alt="image" src="https://github.com/user-attachments/assets/f37da375-c2eb-4a7b-abf2-1fdd3a73e2bb" />

cc @eggyal 

Changed files:
filename: library/core/src/fmt/num.rs
patch: @@ -594,13 +594,15 @@ impl_Debug! {
 // Include wasm32 in here since it doesn't reflect the native pointer size, and
 // often cares strongly about getting a smaller code size.
 #[cfg(any(target_pointer_width = "64", target_arch = "wasm32"))]
+#[doc(auto_cfg = false)]
 mod imp {
     use super::*;
     impl_Display!(i8, u8, i16, u16, i32, u32, i64, u64, isize, usize; as u64 into display_u64);
     impl_Exp!(i8, u8, i16, u16, i32, u32, i64, u64, isize, usize; as u64 into exp_u64);
 }
 
 #[cfg(not(any(target_pointer_width = "64", target_arch = "wasm32")))]
+#[doc(auto_cfg = false)]
 mod imp {
     use super::*;
     impl_Display!(i8, u8, i16, u16, i32, u32, isize, usize; as u32 into display_u32);
Repository: nodejs/node
Pull request: src: use validate_ascii_with_errors for buffer.isAscii

Tracking: #61041 

Don't expect `buffer.isAscii` common-case to be ASCII, as that's exposed as a public API for checks.
The error version has better performance on non-ascii  as it returns early, which could easily be e.g. >10x.

Refs: https://github.com/nodejs/node/pull/46271#discussion_r1081798237,

But somehow the `_errors` version is also faster on ASCII, which was supposed to be a common case for `validate_ascii`?
I'm not sure what's up, might be a simdutf bug?  cc @lemire 

On another note: v8 is also likely using `validate_ascii` incorrectly

`buffer.isAscii` perf:

main:
| Test | Size | Throughput | Mean Time |
|------|------|------------|-----------|
| Latin lipsum (ASCII) | 84.902 KiB | 105.08 GiB/s | 0.001 ms |
| Arabic lipsum | 79.771 KiB | 103.88 GiB/s | 0.001 ms |
| Chinese lipsum | 68.203 KiB | 101.78 GiB/s | 0.001 ms |

PR
| Test | Size | Throughput | Mean Time |
|------|------|------------|-----------|
| Latin lipsum (ASCII) | 84.902 KiB | 117.97 GiB/s | 0.001 ms |
| Arabic lipsum | 79.771 KiB | 1836.47 GiB/s | 0.000 ms |
| Chinese lipsum | 68.203 KiB | 1564.76 GiB/s | 0.000 ms |



Changed files:
filename: src/node_buffer.cc
patch: @@ -1252,7 +1252,8 @@ static void IsAscii(const FunctionCallbackInfo<Value>& args) {
         env, "Cannot validate on a detached buffer");
   }
 
-  args.GetReturnValue().Set(simdutf::validate_ascii(abv.data(), abv.length()));
+  args.GetReturnValue().Set(
+      !simdutf::validate_ascii_with_errors(abv.data(), abv.length()).error);
 }
 
 void SetBufferPrototype(const FunctionCallbackInfo<Value>& args) {
Repository: facebook/react
Pull request: [DevTools] Don't pluralize if already plural

In a demo today, `cookies()` showed up as `cookieses`. While adorable, is wrong.

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/utils.js
patch: @@ -205,6 +205,27 @@ export function pluralize(word: string): string {
     return word;
   }
 
+  // Bail out if it's already plural.
+  switch (word) {
+    case 'men':
+    case 'women':
+    case 'children':
+    case 'feet':
+    case 'teeth':
+    case 'mice':
+    case 'people':
+      return word;
+  }
+
+  if (
+    /(ches|shes|ses|xes|zes)$/i.test(word) ||
+    /[^s]ies$/i.test(word) ||
+    /ves$/i.test(word) ||
+    /[^s]s$/i.test(word)
+  ) {
+    return word;
+  }
+
   switch (word) {
     case 'man':
       return 'men';
Repository: ollama/ollama
Pull request: Rename api-reference.md back to api.md since redirect stopped working


Changed files:
filename: docs/docs.json
patch: @@ -63,6 +63,10 @@
     {
       "source": "/api/openai",
       "destination": "/api/openai-compatibility"
+    },
+    {
+      "source": "/api",
+      "destination": "/api/introduction"
     }
   ],
   "navigation": {
@@ -130,7 +134,7 @@
           {
             "group": "API Reference",
             "pages": [
-              "/api/index",
+              "/api/introduction",
               "/api/authentication",
               "/api/streaming",
               "/api/usage",
Repository: vercel/next.js
Pull request: Stub adapterPath with experimental.runtimeServerDeploymentId

`required-server-files.json` contains the `adapterPath` which might be nondeterministic across builds depending on where the adapter was installed.

Changed files:
filename: packages/next/src/server/config-shared.ts
patch: @@ -1863,7 +1863,10 @@ export function getNextConfigRuntime(
         authInterrupts: ex.authInterrupts,
         clientTraceMetadata: ex.clientTraceMetadata,
         clientParamParsingOrigins: ex.clientParamParsingOrigins,
-        adapterPath: ex.adapterPath,
+        // The full adapterPath might be non-deterministic across builds and doesn't actually matter
+        // at runtime, as it's only used to determine whether the adapter was used or not, not to
+        // execute it again. So replace it with a placeholder if it's set.
+        adapterPath: ex.adapterPath ? '<ommited but set>' : undefined,
         allowedRevalidateHeaderKeys: ex.allowedRevalidateHeaderKeys,
         fetchCacheKeyPrefix: ex.fetchCacheKeyPrefix,
         isrFlushToDisk: ex.isrFlushToDisk,
Repository: huggingface/transformers
Pull request: trigger tensor parallel utils test in the CI


Changed files:
filename: utils/tests_fetcher.py
patch: @@ -1069,7 +1069,7 @@ def parse_commit_message(commit_message: str) -> dict[str, bool]:
     "tests_hub": r"tests/.*",
     "tests_non_model": r"tests/[^/]*?/test_.*\.py",
     "tests_training_ci": r"tests/models/.*/test_modeling_.*",
-    "tests_tensor_parallel_ci": r"tests/models/.*/test_modeling_.*",
+    "tests_tensor_parallel_ci": r"(tests/models/.*/test_modeling_.*|tests/tensor_parallel/test_tensor_parallel\.py)",
 }
Repository: facebook/react
Pull request: [DevTools] Don't try to load anonymous or empty urls

This triggers unnecessary fetches.

Changed files:
filename: packages/react-devtools-shared/src/hooks/parseHookNames/loadSourceAndMetadata.js
patch: @@ -475,23 +475,25 @@ function loadSourceFiles(
 
     const fetchPromise =
       dedupedFetchPromises.get(runtimeSourceURL) ||
-      fetchFileFunction(runtimeSourceURL).then(runtimeSourceCode => {
-        // TODO (named hooks) Re-think this; the main case where it matters is when there's no source-maps,
-        // because then we need to parse the full source file as an AST.
-        if (runtimeSourceCode.length > MAX_SOURCE_LENGTH) {
-          throw Error('Source code too large to parse');
-        }
+      (runtimeSourceURL && !runtimeSourceURL.startsWith('<anonymous')
+        ? fetchFileFunction(runtimeSourceURL).then(runtimeSourceCode => {
+            // TODO (named hooks) Re-think this; the main case where it matters is when there's no source-maps,
+            // because then we need to parse the full source file as an AST.
+            if (runtimeSourceCode.length > MAX_SOURCE_LENGTH) {
+              throw Error('Source code too large to parse');
+            }
 
-        if (__DEBUG__) {
-          console.groupCollapsed(
-            `loadSourceFiles() runtimeSourceURL "${runtimeSourceURL}"`,
-          );
-          console.log(runtimeSourceCode);
-          console.groupEnd();
-        }
+            if (__DEBUG__) {
+              console.groupCollapsed(
+                `loadSourceFiles() runtimeSourceURL "${runtimeSourceURL}"`,
+              );
+              console.log(runtimeSourceCode);
+              console.groupEnd();
+            }
 
-        return runtimeSourceCode;
-      });
+            return runtimeSourceCode;
+          })
+        : Promise.reject(new Error('Empty url')));
     dedupedFetchPromises.set(runtimeSourceURL, fetchPromise);
 
     setterPromises.push(

filename: packages/react-devtools-shared/src/symbolicateSource.js
patch: @@ -52,6 +52,9 @@ export async function symbolicateSource(
   lineNumber: number, // 1-based
   columnNumber: number, // 1-based
 ): Promise<SourceMappedLocation | null> {
+  if (!sourceURL || sourceURL.startsWith('<anonymous')) {
+    return null;
+  }
   const resource = await fetchFileWithCaching(sourceURL).catch(() => null);
   if (resource == null) {
     return null;
Repository: ollama/ollama
Pull request: app/ui: do not send thinking to prevent  errors with cloud provider

When chatting with non-thinking models through cloud providers, the app was sending `"think": false` in every request. Cloud providers convert this to `"reasoning_effort": "none"`, but non-thinking models reject `reasoning_effort` parameter (including "none"), causing `500 Internal Server Error: unmarshal: invalid character 'I'` errors.

This fix only includes the `think` parameter when actually requesting thinking (true or "high"/"medium"/"low"), and omits it entirely when false or "none". This prevents the parameter from being sent to providers that would reject it, and adds early validation with clear error messages when users try to enable thinking on non-reasoning models.

Changed files:
filename: app/ui/app/src/api.ts
patch: @@ -205,6 +205,13 @@ export async function* sendMessage(
     data: uint8ArrayToBase64(att.data),
   }));
 
+  // Only send think parameter when actually requesting thinking
+  // Don't send false as it causes issues with some providers
+  const shouldSendThink =
+    think !== undefined &&
+    ((typeof think === "boolean" && think) ||
+      (typeof think === "string" && think !== ""));
+
   const response = await fetch(`${API_BASE}/api/v1/chat/${chatId}`, {
     method: "POST",
     headers: {
@@ -222,7 +229,7 @@ export async function* sendMessage(
         web_search: webSearch ?? false,
         file_tools: fileTools ?? false,
         ...(forceUpdate !== undefined ? { forceUpdate } : {}),
-        ...(think !== undefined ? { think } : {}),
+        ...(shouldSendThink ? { think } : {}),
       }),
     ),
     signal,

filename: app/ui/ui.go
patch: @@ -1794,13 +1794,14 @@ func (s *Server) buildChatRequest(chat *store.Chat, model string, think any, ava
 
 	var thinkValue *api.ThinkValue
 	if think != nil {
+		// Only set Think if it's actually requesting thinking
 		if boolValue, ok := think.(bool); ok {
-			thinkValue = &api.ThinkValue{
-				Value: boolValue,
+			if boolValue {
+				thinkValue = &api.ThinkValue{Value: boolValue}
 			}
 		} else if stringValue, ok := think.(string); ok {
-			thinkValue = &api.ThinkValue{
-				Value: stringValue,
+			if stringValue != "" && stringValue != "none" {
+				thinkValue = &api.ThinkValue{Value: stringValue}
 			}
 		}
 	}
Repository: vercel/next.js
Pull request: exempt data URL CSS from Pages Router global CSS restriction

### What?

Skip the Pages Router global CSS restriction for `data:` URL imports (similar to app router and mixed app/pages router)

### Why?

`data:text/css` should work the same no matter if pages router, app router or mixed router usage

### How?

the validation in `crates/next-api/src/module_graph.rs` already had a carve-out for `node_modules`. This adds the same for data URL modules.

fixes #89900

- [x] Related issues linked using `fixes #89900`
- [x] Tests added

Changed files:
filename: crates/next-api/src/module_graph.rs
patch: @@ -846,9 +846,12 @@ async fn validate_pages_css_imports_individual(
     candidates
         .into_iter()
         .map(async |issue| {
+            let path = issue.module.ident().path().await?;
             // We allow imports of global CSS files which are inside of `node_modules`.
+            // We also allow data URL CSS imports (e.g. `data:text/css,...`) since they
+            // are mostly tooling-generated and co-located with the importing components
             Ok(
-                if !issue.module.ident().path().await?.is_in_node_modules() {
+                if !path.is_in_node_modules() && !path.file_name().starts_with("data:") {
                     Some(issue)
                 } else {
                     None
@@ -868,8 +871,9 @@ async fn validate_pages_css_imports_individual(
 /// Validates that the global CSS/SCSS/SASS imports are only valid imports with the following
 /// rules:
 /// * The import is made from a `node_modules` package
+/// * The imported CSS is a `data:` URL module
 /// * The import is made from a `.module.css` file
-/// * The import is made from the `pages/_app.js`, or equivalent file.
+/// * The import is made from the `pages/_app.js`, or equivalent file
 #[turbo_tasks::function]
 pub async fn validate_pages_css_imports(
     graph: Vc<ModuleGraph>,

filename: test/e2e/css-data-url-global-pages/css-data-url-global-pages.test.ts
patch: @@ -0,0 +1,21 @@
+import { nextTestSetup } from 'e2e-utils'
+
+// CSS data urls are only supported in Turbopack
+;(process.env.IS_TURBOPACK_TEST ? describe : describe.skip)(
+  'css-data-url-global-pages',
+  () => {
+    const { next } = nextTestSetup({
+      files: __dirname,
+    })
+
+    it('should apply styles from data url correctly', async () => {
+      const browser = await next.browser('/')
+
+      const fontWeight = await browser
+        .elementByCss('#styled')
+        .getComputedCss('font-weight')
+
+      expect(fontWeight).toBe('700')
+    })
+  }
+)

filename: test/e2e/css-data-url-global-pages/next.config.ts
patch: @@ -0,0 +1,7 @@
+import type { NextConfig } from 'next'
+
+const nextConfig: NextConfig = {
+  /* config options here */
+}
+
+export default nextConfig

filename: test/e2e/css-data-url-global-pages/pages/index.tsx
patch: @@ -0,0 +1,5 @@
+import 'data:text/css,#styled{font-weight:700}'
+
+export default function Home() {
+  return <div id="styled">This text should be bold</div>
+}