helloadhavan/github_issues huggingface dataset:
Repository: denoland/deno
Pull request: test: add per-file timeout and reduce CI job timeout

## Summary
- Add a 2-minute per-file timeout wrapping the entire `runSingleTest` (including `generateBundle` fetch calls) using `Promise.race`, so the runner always moves on even if the WPT server becomes unresponsive
- Reduce WPT CI job timeout from 240 minutes to 30 minutes

## Test plan
- [ ] WPT CI job completes without hanging

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

Changed files:
filename: .github/workflows/ci.generate.ts
patch: @@ -1241,7 +1241,7 @@ const buildJobs = buildItems.map((rawBuildItem) => {
         name: jobNameForJob("wpt"),
         needs: [buildJob],
         runsOn: buildItem.testRunner ?? buildItem.runner,
-        timeoutMinutes: 240,
+        timeoutMinutes: 30,
         defaults,
         env,
         steps: step.if(isNotTag.and(buildItem.skip.not()))(

filename: .github/workflows/ci.yml
patch: @@ -3938,7 +3938,7 @@ jobs:
     needs:
       - build-release-linux-x86_64
     runs-on: ubuntu-24.04
-    timeout-minutes: 240
+    timeout-minutes: 30
     defaults:
       run:
         shell: bash

filename: tests/wpt/runner/runner.ts
patch: @@ -90,6 +90,31 @@ export async function runSingleTest(
   reporter: (result: TestCaseResult) => void,
   inspectBrk: boolean,
   timeouts: { long: number; default: number },
+  fileTimeout = 2 * 60_000,
+): Promise<TestResult> {
+  const result = await Promise.race([
+    runSingleTestInner(url, _options, reporter, inspectBrk, timeouts),
+    new Promise<TestResult>((resolve) =>
+      setTimeout(() => {
+        resolve({
+          cases: [],
+          harnessStatus: null,
+          duration: fileTimeout,
+          status: 1,
+          stderr: `test file timed out after ${fileTimeout / 1000}s\n`,
+        });
+      }, fileTimeout)
+    ),
+  ]);
+  return result;
+}
+
+async function runSingleTestInner(
+  url: URL,
+  _options: ManifestTestOptions,
+  reporter: (result: TestCaseResult) => void,
+  inspectBrk: boolean,
+  timeouts: { long: number; default: number },
 ): Promise<TestResult> {
   const timeout = _options.timeout === "long"
     ? timeouts.long
Repository: ollama/ollama
Pull request: Correct typos.

ASSSISTANT --> ASSISTANT 

Changed files:
filename: docs/api.md
patch: @@ -797,9 +797,9 @@ curl http://localhost:11434/api/show -d '{
 
 ```json
 {
-  "modelfile": "# Modelfile generated by \"ollama show\"\n# To build a new Modelfile based on this one, replace the FROM line with:\n# FROM llava:latest\n\nFROM /Users/matt/.ollama/models/blobs/sha256:200765e1283640ffbd013184bf496e261032fa75b99498a9613be4e94d63ad52\nTEMPLATE \"\"\"{{ .System }}\nUSER: {{ .Prompt }}\nASSSISTANT: \"\"\"\nPARAMETER num_ctx 4096\nPARAMETER stop \"\u003c/s\u003e\"\nPARAMETER stop \"USER:\"\nPARAMETER stop \"ASSSISTANT:\"",
-  "parameters": "num_ctx                        4096\nstop                           \u003c/s\u003e\nstop                           USER:\nstop                           ASSSISTANT:",
-  "template": "{{ .System }}\nUSER: {{ .Prompt }}\nASSSISTANT: ",
+  "modelfile": "# Modelfile generated by \"ollama show\"\n# To build a new Modelfile based on this one, replace the FROM line with:\n# FROM llava:latest\n\nFROM /Users/matt/.ollama/models/blobs/sha256:200765e1283640ffbd013184bf496e261032fa75b99498a9613be4e94d63ad52\nTEMPLATE \"\"\"{{ .System }}\nUSER: {{ .Prompt }}\nASSISTANT: \"\"\"\nPARAMETER num_ctx 4096\nPARAMETER stop \"\u003c/s\u003e\"\nPARAMETER stop \"USER:\"\nPARAMETER stop \"ASSISTANT:\"",
+  "parameters": "num_ctx                        4096\nstop                           \u003c/s\u003e\nstop                           USER:\nstop                           ASSISTANT:",
+  "template": "{{ .System }}\nUSER: {{ .Prompt }}\nASSISTANT: ",
   "details": {
     "format": "gguf",
     "family": "llama",
Repository: ollama/ollama
Pull request: fix `ollama create`'s usage string

Since `StringP()` automatically adds the initial value, the initial value description for Modelfile was duplicated.
I have fixed this by removing the redundant default value description from the usage.

Before:
```
$ ./ollama create -h
Create a model from a Modelfile

Usage:
  ollama create MODEL [flags]

Flags:
  -f, --file string       Name of the Modelfile (default "Modelfile") (default "Modelfile")
  -h, --help              help for create
  -q, --quantize string   Quantize model to this level (e.g. q4_0)

Environment Variables:
      OLLAMA_HOST        The host:port or base URL of the Ollama server (e.g. http://localhost:11434)
```

After:
```
$ ./ollama create -h
Create a model from a Modelfile

Usage:
  ollama create MODEL [flags]

Flags:
  -f, --file string       Name of the Modelfile (default "Modelfile")
  -h, --help              help for create
  -q, --quantize string   Quantize model to this level (e.g. q4_0)

Environment Variables:
      OLLAMA_HOST        The host:port or base URL of the Ollama server (e.g. http://localhost:11434)
```

Changed files:
filename: cmd/cmd.go
patch: @@ -1050,7 +1050,7 @@ func NewCLI() *cobra.Command {
 		RunE:    CreateHandler,
 	}
 
-	createCmd.Flags().StringP("file", "f", "Modelfile", "Name of the Modelfile (default \"Modelfile\")")
+	createCmd.Flags().StringP("file", "f", "Modelfile", "Name of the Modelfile")
 	createCmd.Flags().StringP("quantize", "q", "", "Quantize model to this level (e.g. q4_0)")
 
 	showCmd := &cobra.Command{
Repository: nodejs/node
Pull request: test: remove timeout in test-https-proxy-request-handshake-failure

The timeout is unnecessary since we are testing for certificate failure. It can cause flakes on very slow machines where the request cannot be finished in 1 second.

Fixes: https://github.com/nodejs/node/issues/59166

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/client-proxy/test-https-proxy-request-handshake-failure.mjs
patch: @@ -33,7 +33,6 @@ const requestUrl = `https://${serverHost}/test`;
 const { code, signal, stderr, stdout } = await runProxiedRequest({
   NODE_USE_ENV_PROXY: 1,
   REQUEST_URL: requestUrl,
-  REQUEST_TIMEOUT: 1000,
   HTTPS_PROXY: `http://localhost:${proxy.address().port}`,
 });
Repository: electron/electron
Pull request: build: extend Chromium options in bug report template

#### Description of Change

As predicted by @dsanders11 and others, we got a bunch of bug reports with clearly incorrect values for "does this issue also happen in Chromium?" because people didn't test or didn't know how to test.

This PR adds an "I don't know how to test" option.

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd
- [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: .github/ISSUE_TEMPLATE/bug_report.yml
patch: @@ -63,6 +63,7 @@ body:
     label: Does the issue also appear in Chromium / Google Chrome?
     description: If it does, please report the issue in the [Chromium issue tracker](https://issues.chromium.org/issues), not against Electron. Electron will inherit the fix once Chromium resolves the issue.
     options:
+      - I don't know how to test
       - "Yes"
       - "No"
   validations:
Repository: huggingface/transformers
Pull request: Bump AMD docker

This PR bumps the base version of the AMD docker to ROCm 7.0, which means it is compatible with MI355 which was not the case before. 
To avoid issues with detectron, the install is split from the rest of the pip install, and to support MI355 for flash attn, the gfx950 architecture was added to FA compilation.
I tested the docker for Mi325 and Mi355 on important models and there was no major new failures.

Changed files:
filename: docker/transformers-pytorch-amd-gpu/Dockerfile
patch: @@ -1,4 +1,4 @@
-FROM rocm/pytorch:rocm6.4.1_ubuntu24.04_py3.12_pytorch_release_2.7.1
+FROM rocm/pytorch:rocm7.0.2_ubuntu24.04_py3.12_pytorch_release_2.7.1
 LABEL maintainer="Hugging Face"
 
 ARG DEBIAN_FRONTEND=noninteractive
@@ -10,8 +10,8 @@ RUN apt update && \
 
 RUN git lfs install
 
-RUN python3 -m pip install --no-cache-dir --upgrade pip numpy
-RUN python3 -m pip install --no-cache-dir --upgrade importlib-metadata setuptools ninja git+https://github.com/facebookresearch/detectron2.git pytesseract "itsdangerous<2.1.0"
+RUN python3 -m pip install --no-cache-dir --upgrade pip numpy importlib-metadata setuptools wheel ninja pytesseract "itsdangerous<2.1.0"
+RUN python3 -m pip install --no-cache-dir --no-build-isolation git+https://github.com/facebookresearch/detectron2.git
 
 ARG REF=main
 WORKDIR /
@@ -39,6 +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" python setup.py install
+    GPU_ARCHS="gfx942;gfx950" python setup.py install  
+# GPU_ARCHS builds for MI300, MI325 and MI355
 
 RUN python3 -m pip install --no-cache-dir einops
Repository: vercel/next.js
Pull request: [dev] Fix Middleware and Proxy file conflict

Since the conflict check looked only at the file name 💀, when there's a `proxy` or `middleware` file inside the app, it also detected a conflict:

```
Unhandled Rejection: Error: Both "middleware" and "proxy" files are detected. Please use "proxy" instead.
```

CI: https://github.com/vercel/next.js/actions/runs/18568804746/job/52937138783?pr=84965#step:34:326

Therefore, check for the actual file path of the middleware/proxy file.

Changed files:
filename: packages/next/src/server/lib/router-utils/setup-dev-bundler.ts
patch: @@ -393,34 +393,38 @@ async function startWatcher(
 
       let hasMiddlewareFile = false
       let hasProxyFile = false
+
       for (const fileName of sortedKnownFiles) {
-        const { name } = path.parse(fileName)
-        if (name === MIDDLEWARE_FILENAME) {
+        if (
+          !files.includes(fileName) &&
+          !directories.some((d) => fileName.startsWith(d))
+        ) {
+          continue
+        }
+
+        const { name: fileBaseName, dir: fileDir } = path.parse(fileName)
+
+        const isAtConventionLevel =
+          fileDir === dir || fileDir === path.join(dir, 'src')
+
+        if (isAtConventionLevel && fileBaseName === MIDDLEWARE_FILENAME) {
           hasMiddlewareFile = true
         }
-        if (name === PROXY_FILENAME) {
+        if (isAtConventionLevel && fileBaseName === PROXY_FILENAME) {
           hasProxyFile = true
         }
-      }
 
-      if (hasMiddlewareFile) {
-        if (hasProxyFile) {
-          throw new Error(
-            `Both "${MIDDLEWARE_FILENAME}" and "${PROXY_FILENAME}" files are detected. Please use "${PROXY_FILENAME}" instead.`
+        if (hasMiddlewareFile) {
+          if (hasProxyFile) {
+            throw new Error(
+              `Both "${MIDDLEWARE_FILENAME}" and "${PROXY_FILENAME}" files are detected. Please use "${PROXY_FILENAME}" instead.`
+            )
+          }
+          Log.warnOnce(
+            `The "${MIDDLEWARE_FILENAME}" file convention is deprecated. Please use "${PROXY_FILENAME}" instead.`
           )
         }
-        Log.warnOnce(
-          `The "${MIDDLEWARE_FILENAME}" file convention is deprecated. Please use "${PROXY_FILENAME}" instead.`
-        )
-      }
 
-      for (const fileName of sortedKnownFiles) {
-        if (
-          !files.includes(fileName) &&
-          !directories.some((d) => fileName.startsWith(d))
-        ) {
-          continue
-        }
         const meta = knownFiles.get(fileName)
 
         const watchTime = fileWatchTimes.get(fileName)

filename: test/e2e/app-dir/app-middleware/app/middleware.js
patch: @@ -0,0 +1 @@
+// noop, this file should not picked up as Middleware file and throw error.

filename: test/e2e/app-dir/app-middleware/app/proxy.js
patch: @@ -0,0 +1 @@
+// noop, this file should not picked up as Proxy file and throw error.
Repository: ggml-org/llama.cpp
Pull request: CUDA: Blackwell features for non-native builds

This PR adds architectures to enable the recent Blackwell-specific MXFP4 optimizations for non-native builds. The problem with `120f-virtual` which we were using in the initial PR is that it doesn't match some regex that CMake was using to validate CUDA architectures. But the same regex seems to be compatible with `120a-real` and `121a-real` so I would suggest that we for now simply build those since there is no other hardware to cover. Newer CMake versions come with a bugfix for the regex so presumably this will be less problematic for us to handle in the future. @CISC is there a way to run the Windows CUDA release CI without merging a PR?

Changed files:
filename: ggml/src/ggml-cuda/CMakeLists.txt
patch: @@ -35,6 +35,20 @@ if (CUDAToolkit_FOUND)
             if (CUDAToolkit_VERSION VERSION_GREATER_EQUAL "11.8")
                 list(APPEND CMAKE_CUDA_ARCHITECTURES 89-real)
             endif()
+
+            if (CUDAToolkit_VERSION VERSION_GREATER_EQUAL "12.8")
+                # The CUDA architecture 120f-virtual would in principle work for Blackwell support
+                #     but the newly added "f" suffix conflicted with a preexising regex for validating CUDA architectures in CMake.
+                # So either a recent CMake version or one with the backported fix is needed.
+                # The following versions should work:
+                #   - CMake >= v3.31.8 && CMake < v4.0.0
+                #   - CMake >= v4.0.2
+                # This is NOT documented in the CMake release notes,
+                #     check Modules/Internal/CMakeCUDAArchitecturesValidate.cmake in the CMake git repository instead.
+                # However, the architectures 120a-real and 121a-real should work with basically any CMake version and
+                #     until the release of e.g. Rubin there is no benefit to shipping virtual architectures for Blackwell.
+                list(APPEND CMAKE_CUDA_ARCHITECTURES 120a-real 121a-real)
+            endif()
         endif()
     endif()
     message(STATUS "Using CUDA architectures: ${CMAKE_CUDA_ARCHITECTURES}")
@@ -62,7 +76,7 @@ if (CUDAToolkit_FOUND)
     else()
         foreach(ARCH ${CMAKE_CUDA_ARCHITECTURES})
             if(ARCH MATCHES "^12[0-9](-real|-virtual)?$")
-                message(FATAL_ERROR "Compute capability ${ARCH} used, use ${ARCH}a or ${ARCH}f for Blackwell specific optimizations")
+                message(FATAL_ERROR "Compute capability ${ARCH} used, use ${ARCH}a or ${ARCH}f for Blackwell-specific optimizations")
             endif()
         endforeach()
     endif()
Repository: ollama/ollama
Pull request: use post token


Changed files:
filename: app/lifecycle/updater.go
patch: @@ -56,13 +56,13 @@ func IsNewReleaseAvailable(ctx context.Context) (bool, UpdateResponse) {
 	query.Add("nonce", nonce)
 	requestURL.RawQuery = query.Encode()
 
-	data := []byte(fmt.Sprintf("%s,%s", http.MethodGet, requestURL.RequestURI()))
+	data := []byte(fmt.Sprintf("%s,%s", http.MethodPost, requestURL.RequestURI()))
 	signature, err := auth.Sign(ctx, data)
 	if err != nil {
 		return false, updateResp
 	}
 
-	req, err := http.NewRequestWithContext(ctx, http.MethodGet, requestURL.String(), nil)
+	req, err := http.NewRequestWithContext(ctx, http.MethodPost, requestURL.String(), nil)
 	if err != nil {
 		slog.Warn(fmt.Sprintf("failed to check for update: %s", err))
 		return false, updateResp

filename: server/auth.go
patch: @@ -57,7 +57,7 @@ func getAuthorizationToken(ctx context.Context, challenge registryChallenge) (st
 	}
 
 	sha256sum := sha256.Sum256(nil)
-	data := []byte(fmt.Sprintf("%s,%s,%s", http.MethodGet, redirectURL.String(), base64.StdEncoding.EncodeToString([]byte(hex.EncodeToString(sha256sum[:])))))
+	data := []byte(fmt.Sprintf("%s,%s,%s", http.MethodPost, redirectURL.String(), base64.StdEncoding.EncodeToString([]byte(hex.EncodeToString(sha256sum[:])))))
 
 	headers := make(http.Header)
 	signature, err := auth.Sign(ctx, data)
@@ -67,7 +67,7 @@ func getAuthorizationToken(ctx context.Context, challenge registryChallenge) (st
 
 	headers.Add("Authorization", signature)
 
-	response, err := makeRequest(ctx, http.MethodGet, redirectURL, headers, nil, nil)
+	response, err := makeRequest(ctx, http.MethodPost, redirectURL, headers, nil, nil)
 	if err != nil {
 		return "", err
 	}
Repository: denoland/deno
Pull request: fix: make flamegraph SVG fill full browser viewport

Fixes #32725

The flamegraph SVG had a fixed pixel `height` attribute, which combined
with the `viewBox` aspect ratio, caused the browser to constrain the
rendered width — leaving the right side of the viewport empty.

- Changed `height="{image_height}"` → `height="100%"` on the `<svg>` element
- Added `fg:content_height="{image_height}"` to `<g id="frames">` so the
  JS resize logic can still reference the original content height
- Updated `flamegraph.js` to read `orig_height` from the new attribute
- Added test assertions for the new attributes

Changed files:
filename: runtime/cpu_profiler/flamegraph.js
patch: @@ -28,7 +28,7 @@ function init(evt) {
       toggle_invert();
     });
   }
-  orig_height = parseFloat(svg.attributes.height.value);
+  orig_height = parseFloat(frames.getAttribute("fg:content_height"));
   // Fluid: fill viewport width and height
   svg.removeAttribute("width");
   update_for_resize = function () {

filename: runtime/cpu_profiler/flamegraph.rs
patch: @@ -121,7 +121,7 @@ pub(crate) fn generate_flamegraph_svg(
   svg.push_str(&format!(
     r##"<?xml version="1.0" standalone="no"?>
 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
-<svg version="1.1" width="100%" height="{image_height}" onload="init(evt)" viewBox="0 0 {image_width} {image_height}" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:fg="http://github.com/nicholasgasior/gofern" style="min-height:100vh">
+<svg version="1.1" width="100%" height="100%" onload="init(evt)" viewBox="0 0 {image_width} {image_height}" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:fg="http://github.com/nicholasgasior/gofern" style="min-height:100vh">
 <defs>
   <linearGradient id="background" y1="0" y2="1">
     <stop stop-color="#eeeeee" offset="5%"/>
@@ -162,7 +162,7 @@ pub(crate) fn generate_flamegraph_svg(
 <label style="font-family:Verdana,sans-serif;font-size:12px;cursor:pointer"><input type="checkbox" id="invert_cb" style="cursor:pointer"/> Invert</label>
 </body>
 </foreignObject>
-<g id="frames" total_samples="{total_samples}" width="{frames_width}" fg:max_depth="{max_depth}" fg:frame_height="{frame_height}" fg:y_pad_top="{y_pad_top}">
+<g id="frames" total_samples="{total_samples}" width="{frames_width}" fg:max_depth="{max_depth}" fg:frame_height="{frame_height}" fg:y_pad_top="{y_pad_top}" fg:content_height="{image_height}">
 "##,
     flamegraph_js = FLAMEGRAPH_JS,
     details_y = image_height - y_pad_bottom + 21,

filename: tests/specs/cpu_prof/flamegraph/verify.js
patch: @@ -24,4 +24,12 @@ if (!content.includes("function init(evt)")) {
   console.log("Missing interactive JavaScript");
   Deno.exit(1);
 }
+if (!content.includes('height="100%"')) {
+  console.log("SVG should use full viewport height");
+  Deno.exit(1);
+}
+if (!content.includes("fg:content_height=")) {
+  console.log("Missing content height data attribute");
+  Deno.exit(1);
+}
 console.log("Valid flamegraph");
Repository: vercel/next.js
Pull request: Turbopack: fix pageExtensions precedence

Webpack doesn't use the specified order, it's by length.

Closes PACK-5691

Changed files:
filename: crates/next-core/src/next_config.rs
patch: @@ -1388,7 +1388,12 @@ impl NextConfig {
 
     #[turbo_tasks::function]
     pub fn page_extensions(&self) -> Vc<Vec<RcStr>> {
-        Vc::cell(self.page_extensions.clone())
+        // Sort page extensions by length descending. This mirrors the Webpack behavior in Next.js,
+        // which just builds a regex alternative, which greedily matches the longest
+        // extension: https://github.com/vercel/next.js/blob/32476071fe331948d89a35c391eb578aed8de979/packages/next/src/build/entries.ts#L409
+        let mut extensions = self.page_extensions.clone();
+        extensions.sort_by_key(|ext| std::cmp::Reverse(ext.len()));
+        Vc::cell(extensions)
     }
 
     #[turbo_tasks::function]

filename: test/integration/custom-page-extension/next.config.js
patch: @@ -1,3 +1,5 @@
-module.exports = {
-  pageExtensions: ['page.js'],
-}
+module.exports = (phase, { defaultConfig }) => ({
+  // Append the custom extension to the default page extensions, to ensure that matching precedence
+  // is by length.
+  pageExtensions: [...defaultConfig.pageExtensions, 'page.js'],
+})