repo stringclasses 8
values | issue_number int64 13k 155k | issue_title stringlengths 3 139 | issue_body stringlengths 4 68.4k ⌀ | commit_sha stringlengths 40 40 | files listlengths 1 300 |
|---|---|---|---|---|---|
electron/electron | 50,696 | feat: register contextMenus and sidePanel extension permissions | Fixes #50331. This PR adds the missing 'contextMenus' and 'sidePanel' permissions to the Electron extension system, resolving the 'unknown permission' warnings and enabling the corresponding APIs. | 4e17ddd7b8a80a133ceab4d6bffbc23b2196c620 | [
{
"filename": "shell/common/extensions/api/_api_features.json",
"patch": "@@ -24,6 +24,14 @@\n \"action.setBadgeTextColor\": {\n \"channel\": \"stable\"\n },\n+ \"contextMenus\": {\n+ \"dependencies\": [\"permission:contextMenus\"],\n+ \"contexts\": [\"privileged_extension\"]\n+ },\n+ \"sid... |
huggingface/transformers | 45,248 | Fix tf32 issue: set `torch.backends.cudnn.conv.fp32_precision` explicitly. | # What does this PR do?
PR #42428 change the way to enable / disable torch's TF32 using torch new API. It turns out set
> torch.backends.fp32_precision = False
would still have
> torch.backends.cudnn.conv.fp32_precision = "tf32"
> torch.backends.cudnn.rnn.fp32_precision = "tf32"
It's not clear if it's a bug or a design in `torch`, I will talk to people at torch conference next week.
For now, this issue causes ~60 `test_batching_equivalence` failing. Set `torch.backends.cudnn.conv.fp32_precision = "ieee"` explicitly will have no such failing tests (on the commit of the linked PR).
I will merge this PR directly to move fast. If `torch` team says that it's a design instead of a bug, we could move the logic to our `enable_tf32`.
Keep in mind, even with this fix, there are still 37 failing `test_batching_equivalence`, which are caused by other issues introduced after #42428 , which should be fixed in separated PR(s).
Note: this PR bring the `vit` and `clip` CI back to ✅ | e70c3db53455c5b2eb78ee54cbf27d04a2f29fa9 | [
{
"filename": "conftest.py",
"patch": "@@ -153,7 +153,18 @@ def check_output(self, want, got, optionflags):\n # TODO: Considering move this to `enable_tf32`, or report a bug to `torch`.\n import torch\n \n- torch.backends.cudnn.conv.fp32_precision = \"ieee\"\n+ # In order to set `torch.backend... |
vercel/next.js | 92,325 | ci: fix stats action | We recently re-imaged the self-hosted Linux runners and it now hits `ERR_PNPM_EXDEV` when pnpm copies packages between its default store and the temp stats workspace. Keeping both under the same temp root avoids the cross-filesystem copy failure. | 037d60bfe1f8be7f556b1d83df923689518eeb1a | [
{
"filename": ".github/actions/next-stats-action/src/constants.js",
"patch": "@@ -3,7 +3,20 @@ const os = require('os')\n const fs = require('fs')\n \n const benchTitle = 'Page Load Tests'\n-const workDir = fs.mkdtempSync(path.join(os.tmpdir(), 'next-stats'))\n+\n+function getTempRoot() {\n+ const tempRoot... |
ollama/ollama | 15,312 | app: default app home view to new chat instead of launch | null | a91ece0b1d719dde01231e484c748afca08529d2 | [
{
"filename": "app/store/database.go",
"patch": "@@ -82,7 +82,7 @@ func (db *database) init() error {\n \t\twebsearch_enabled BOOLEAN NOT NULL DEFAULT 0,\n \t\tselected_model TEXT NOT NULL DEFAULT '',\n \t\tsidebar_open BOOLEAN NOT NULL DEFAULT 0,\n-\t\tlast_home_view TEXT NOT NULL DEFAULT 'launch',\n+\t\tl... |
nodejs/node | 62,570 | deps: bump Undici 8 and fix tests | <!--
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.
-->
| a976df664f536c326da5fb127035c960dc39f20f | [
{
"filename": "test/common/websocket-server.js",
"patch": "@@ -120,7 +120,7 @@ class WebSocketServer {\n this.customHandleUpgradeHeaders.map((header) => {\n const index = header.indexOf(':');\n return [header.slice(0, index).trim(), header.slice(index + 1).trim()];\n- })\n+ }... |
facebook/react | 36,204 | [Performance] Core reconciler and server streaming optimizations | This PR introduces several optimizations to the React core targeting high-frequency paths in the Reconciler, Concurrent Mode, and Server Streaming.
### Key Changes:
1. **Reconciler:** Optimized view-transition restoration traversal. By pre-calculating eligibility once per commit and utilizing subtree flags for early bailouts, complexity is reduced from O(N) to O(V).
2. **Concurrent Mode:** Implemented O(1) bailout for lane starvation checks. Tracks earliestPendingTime on the root to avoid 31 bitwise iterations on every yield.
3. **Micro-optimizations:** Replaced Array.map with manual for-loops in the commit phase and hook state cloning, eliminating closure allocations in hot paths.
4. **Server Streaming:** Aggressive GC for single-shot iterators. Nullifies buffer chunks immediately after streaming, significantly reducing peak heap pressure for large RSC payloads.
### Verification:
- Verified with packages/react-reconciler/src/__tests__/ReactHooks-test.internal.js
- Verified with packages/react-reconciler/src/__tests__/ReactExpiration-test.js
- Verified with packages/react-reconciler/src/__tests__/ViewTransitionReactServer-test.js
- Verified with packages/react-server/src/__tests__/ReactFlightServer-test.js | 7ce159d11b052461ad602a1644c60873c6197127 | [
{
"filename": "packages/react-reconciler/src/ReactFiberCommitWork.js",
"patch": "@@ -3503,12 +3503,17 @@ export function commitPassiveMountEffects(\n ): void {\n resetComponentEffectTimers();\n \n+ const isViewTransitionEligible =\n+ enableViewTransition &&\n+ includesOnlyViewTransitionEligibleLane... |
golang/go | 78,436 | encoding/hex: speed up Decode | This CL eliminates the remaining bounds check for index expressions on
Encode's src parameter within the function's loop.
Here are some benchmark results (no change to allocations):
goos: darwin
goarch: arm64
pkg: encoding/hex
cpu: Apple M4
│ old │ new │
│ sec/op │ sec/op vs base │
Decode/256-10 166.2n ± 0% 142.9n ± 0% -14.02% (n=180)
Decode/1024-10 626.9n ± 0% 532.7n ± 0% -15.03% (n=180)
Decode/4096-10 2.472µ ± 0% 2.079µ ± 0% -15.90% (n=180)
Decode/16384-10 9.843µ ± 0% 8.266µ ± 0% -16.02% (n=180)
geomean 1.262µ 1.069µ -15.25%
│ old │ new │
│ B/s │ B/s vs base │
Decode/256-10 1.434Gi ± 0% 1.669Gi ± 0% +16.32% (p=0.000 n=180)
Decode/1024-10 1.521Gi ± 0% 1.790Gi ± 0% +17.69% (p=0.000 n=180)
Decode/4096-10 1.543Gi ± 0% 1.834Gi ± 0% +18.87% (p=0.000 n=180)
Decode/16384-10 1.550Gi ± 0% 1.846Gi ± 0% +19.08% (p=0.000 n=180)
geomean 1.512Gi 1.783Gi +17.98%
| dcda1b6a81011649d08db5093f38b12d1ac52f7d | [
{
"filename": "src/encoding/hex/hex.go",
"patch": "@@ -85,10 +85,10 @@ func DecodedLen(x int) int { return x / 2 }\n // If the input is malformed, Decode returns the number\n // of bytes decoded before the error.\n func Decode(dst, src []byte) (int, error) {\n-\ti, j := 0, 1\n-\tfor ; j < len(src); j += 2 {... |
huggingface/transformers | 45,243 | Nvidia CI with `torch 2.11` | # What does this PR do?
Use torch 2.11 for our (daily) CI since it's released for 2 weeks already.
For CircleCI, we need to fix something regarding `torchvision.io.read_video`.
For daily CI, torch 2.11 doesn't cause issues (for those `torchvision.io.read_video`). | b65b67c4e1ea82ef9b50020e38ae716edf8758aa | [
{
"filename": "docker/transformers-all-latest-gpu/Dockerfile",
"patch": "@@ -9,12 +9,12 @@ SHELL [\"sh\", \"-lc\"]\n # The following `ARG` are mainly used to specify the versions explicitly & directly in this docker file, and not meant\n # to be used as arguments for docker build (so far).\n \n-ARG PYTORCH=... |
vercel/next.js | 92,324 | ci: remove deploy examples workflow from build-and-deploy | We don't need to deploy a single image component example every time `build_and_deploy` runs. If something about this example changes, it can be manually re-deployed. | b4f31566f5297a908d0a1fbb3d096c8694b8425a | [
{
"filename": ".github/workflows/build_and_deploy.yml",
"patch": "@@ -563,31 +563,6 @@ jobs:\n - name: Publish\n run: cargo xtask workspace --publish\n \n- deployExamples:\n- if: ${{ needs.deploy-target.outputs.value != 'automated-preview' }}\n- name: Deploy examples\n- runs-on: ubun... |
electron/electron | 50,695 | fix: defer Wrappable destruction in SecondWeakCallback to a posted task | Backport of #50688
See that PR for details.
Notes: Fixed an intermittent `Invoke in DisallowJavascriptExecutionScope` crash on application quit when a `WebContents` (or other JS-emitting native object) is garbage-collected during shutdown.
| 1c1384c8a72629f2b3ebd81de13ce18e2896c622 | [
{
"filename": "shell/common/gin_helper/wrappable.cc",
"patch": "@@ -4,6 +4,7 @@\n \n #include \"shell/common/gin_helper/wrappable.h\"\n \n+#include \"base/task/sequenced_task_runner.h\"\n #include \"gin/object_template_builder.h\"\n #include \"gin/public/isolate_holder.h\"\n #include \"shell/common/gin_help... |
rust-lang/rust | 154,832 | Rollup of 2 pull requests | Successful merges:
- rust-lang/rust#150129 (`BorrowedCursor`: make `init` a boolean)
- rust-lang/rust#154830 (miri subtree update)
<!-- homu-ignore:start -->
r? @ghost
[Create a similar rollup](https://bors.rust-lang.org/queue/rust?prs=150129,154830)
<!-- homu-ignore:end -->
| f359441c73e947a6a47d5393bb4cd29e2c828257 | [
{
"filename": "Cargo.lock",
"patch": "@@ -3422,9 +3422,9 @@ dependencies = [\n \n [[package]]\n name = \"rustc-build-sysroot\"\n-version = \"0.5.12\"\n+version = \"0.5.13\"\n source = \"registry+https://github.com/rust-lang/crates.io-index\"\n-checksum = \"eec3905e8201688412f6f4b1f6c86d38b3ee6578f59ba85f413... |
ollama/ollama | 15,311 | Revert "enable flash attention for gemma4 (#15296)" | This reverts commit c8e0878814b4d19200d65571d3d2d35b4b48fd3e.
Fixes a performance regression - Perf run comparison:
```
│ /tmp/0.20.0.log │ /tmp/0.20.1-flash.log │ /tmp/0.20.1-no-flash.log │
│ token/sec │ token/sec vs base │ token/sec vs base │
Model/name=gemma4:e2b/step=prefill 3.035k ± 1% 1.227k ± 2% -59.57% (p=0.002 n=6) 3.040k ± 1% ~ (p=0.310 n=6)
Model/name=gemma4:e2b/step=generate 144.92 ± 3% 95.09 ± 6% -34.39% (p=0.002 n=6) 146.20 ± 2% +0.89% (p=0.026 n=6)
Model/name=gemma4:e4b/step=prefill 1508.1 ± 5% 827.4 ± 3% -45.14% (p=0.002 n=6) 1533.3 ± 2% ~ (p=0.180 n=6)
Model/name=gemma4:e4b/step=generate 93.55 ± 1% 66.75 ± 5% -28.64% (p=0.002 n=6) 94.75 ± 2% +1.29% (p=0.026 n=6)
Model/name=gemma4:26b/step=prefill 1497.5 ± 1% 689.7 ± 1% -53.95% (p=0.002 n=6) 1556.9 ± 1% +3.97% (p=0.002 n=6)
Model/name=gemma4:26b/step=generate 86.95 ± 3% 70.63 ± 4% -18.77% (p=0.002 n=6) 88.78 ± 1% +2.09% (p=0.009 n=6)
geomean 447.9 260.7 -41.80% 455.4 +1.67%
``` | 9e725f32dec43afe8730a5a000dc4c4c60e99b93 | [
{
"filename": "fs/ggml/ggml.go",
"patch": "@@ -890,7 +890,6 @@ func (f GGML) FlashAttention() bool {\n \treturn slices.Contains([]string{\n \t\t\"bert\",\n \t\t\"gemma3\",\n-\t\t\"gemma4\",\n \t\t\"glm4moelite\",\n \t\t\"glmocr\",\n \t\t\"gptoss\", \"gpt-oss\",",
"additions": 0,
"deletions": 1
}
] |
facebook/react | 36,180 | Add Flight SSR benchmark fixture | This PR adds a benchmark fixture for measuring the performance overhead of the React Server Components (RSC) Flight rendering compared to plain Fizz server-side rendering.
### Motivation
Performance discussions around RSC (e.g. #36143, #35125) have highlighted the need for reproducible benchmarks that accurately measure the cost that Flight adds on top of Fizz. This fixture provides multiple benchmark modes that can be used to track performance improvements across commits, compare Node vs Edge (web streams) overhead, and identify bottlenecks in Flight serialization and deserialization.
### What it measures
The benchmark renders a dashboard app with ~25 components (16 client components), 200 product rows with nested data (~325KB Flight payload), and ~250 Suspense boundaries in the async variant. It compares 8 render variants: Fizz-only and Flight+Fizz, across Node and Edge stream APIs, with both synchronous and asynchronous apps.
### Benchmark modes
- **`yarn bench`** runs a sequential in-process benchmark with realistic Flight script injection (tee + `TransformStream`/`Transform` buffered injection), matching what real frameworks do when inlining the RSC payload into the HTML response for hydration.
- **`yarn bench:bare`** runs the same benchmark without script injection, isolating the React-internal rendering cost. This is best for tracking changes to Flight serialization or Fizz rendering.
- **`yarn bench:server`** starts an HTTP server and uses `autocannon` to measure real req/s at `c=1` and `c=10`. The `c=1` results provide a clean signal for tracking React-internal changes, while `c=10` reflects throughput under concurrent load.
- **`yarn bench:concurrent`** runs an in-process concurrent benchmark with 50 in-flight renders via `Promise.all`, measuring throughput without HTTP overhead.
- **`yarn bench:profile`** collects CPU profiles via the V8 inspector and reports the top functions by self-time along with GC pause data.
- **`yarn start`** starts the HTTP server for manual browser testing. Appending `.rsc` to any Flight URL serves the raw Flight payload.
### Key findings during development
On Node 22, the Flight+Fizz overhead compared to Fizz-only rendering is roughly:
- **Without script injection** (`bench:bare`): ~2.2x for sync, ~1.3x for async
- **With script injection** (`bench:server`, c=1): ~2.9x for sync, ~1.8x for async
- **Edge vs Node** adds another ~30% for sync and ~10% for async, driven by the stream plumbing for script injection (tee + `TransformStream` buffering)
The async variant better represents real-world applications where server components fetch data asynchronously. Its lower overhead reflects the fact that Flight serialization and Fizz rendering can overlap with I/O wait times, making the added Flight cost a smaller fraction of total request time.
The benchmark also revealed that the Edge vs Node gap is negligible for Fizz-only rendering (~1-2%) but grows to ~15% for Flight+Fizz sync even without script injection. With script injection (tee + `TransformStream` buffering), the gap roughly doubles to ~30% for sync. The async variants show smaller gaps (~5% without, ~10% with injection).
| 268ef5505c6bf8362b51b4580661e324154a08b7 | [
{
"filename": "fixtures/flight-ssr-bench/README.md",
"patch": "@@ -27,7 +27,6 @@ yarn install\n | `yarn bench:profile` | CPU profiling via V8 inspector. Saves `.cpuprofile` files to `build/profiles/`. |\n | `yarn bench:server` | HTTP server benchmark using autocannon. Measures real req/s with TCP overhead. ... |
nodejs/node | 62,566 | doc: document TransformStream transformer.cancel option | Add documentation for the `cancel` option of the `TransformStream` transformer, which allows users to specify a callback that will be called when the stream is canceled.
See: https://streams.spec.whatwg.org/#transformer-api
Fixes: https://github.com/nodejs/node/issues/62540
<!--
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.
-->
| 868db3134db042c1b0c91a65fa9a6bfc515b5d80 | [
{
"filename": "doc/api/webstreams.md",
"patch": "@@ -5,11 +5,6 @@\n <!-- YAML\n added: v16.5.0\n changes:\n- - version:\n- - v21.5.0\n- - v20.14.0\n- pr-url: https://github.com/nodejs/node/pull/50126\n- description: Supports the `cancel` transformer callback.\n - version:\n - v21.0.0\n ... |
huggingface/transformers | 45,241 | Update tiny model creation script | # What does this PR do?
After the series of fixes in other previous PRs, we can now update the tiny model creation script. This update makes the script running without any failure, just 10 warnings.
There are many # TODO, some of them may just be quick remarks only. I decide to push and merge without removing them, so we still have the context to further improve the script to be more robust and clean.
The workflow file is also changed, so it could run on a daily basis, for us to check if there is any issue with the more future PRs merged into main. It doesn't upload the tiny models to the hub at this moment, which is a task for me to work on in a separate PR. | 4992ead60e0ef0719d9bb45060ee987efcda3ba6 | [
{
"filename": ".github/workflows/check_tiny_models.yml",
"patch": "@@ -10,6 +10,7 @@ on:\n \r\n env:\r\n TOKEN: ${{ secrets.TRANSFORMERS_HUB_BOT_HF_TOKEN }}\r\n+ HF_TOKEN: ${{ secrets.HF_HUB_READ_TOKEN }}\r\n \r\n jobs:\r\n check_tiny_models:\r\n@@ -22,61 +23,35 @@ jobs:\n fetch-depth: 2\r\n ... |
electron/electron | 50,693 | fix: defer Wrappable destruction in SecondWeakCallback to a posted task | Backport of #50688
See that PR for details.
Notes: Fixed an intermittent `Invoke in DisallowJavascriptExecutionScope` crash on application quit when a `WebContents` (or other JS-emitting native object) is garbage-collected during shutdown.
| 562780086138c8e4be6a3ba0f2a21063883ed8a9 | [
{
"filename": "shell/common/gin_helper/wrappable.cc",
"patch": "@@ -4,6 +4,7 @@\n \n #include \"shell/common/gin_helper/wrappable.h\"\n \n+#include \"base/task/sequenced_task_runner.h\"\n #include \"gin/object_template_builder.h\"\n #include \"gin/public/isolate_holder.h\"\n #include \"shell/common/gin_help... |
golang/go | 78,398 | net: make SplitHostPort alloc-free in more cases | Because SplitHostPort is not inlineable, its error result cannot benefit
from mid-stack inlining and must be moved to the heap. However, callers
of SplitHostPort that only use its error result in nil checks are pretty
typical, and their performance needlessly suffers from the resulting
allocation.
Drawing inspiration from CL 734440, this CL refactors SplitHostPort to
an inlineable wrapper around a function that returns, not an error, but
the concrete type of SplitHostPort's error result. Consequently, that
error result can stay on the stack in cases where callers only use it in
nil checks, and SplitHostPort is now allocation-free for such callers.
To clarify: the goal of this CL is to make SplitHostPort
allocation-free, not simply in non-error cases, but also in error cases
in which the error result is only used in nil checks. | ca9b9c915e8d8f44f8153dfdc667bf7ea829a339 | [
{
"filename": "src/cmd/compile/internal/test/inl_test.go",
"patch": "@@ -185,6 +185,7 @@ func TestIntendedInlining(t *testing.T) {\n \t\t},\n \t\t\"net\": {\n \t\t\t\"(*UDPConn).ReadFromUDP\",\n+\t\t\t\"SplitHostPort\",\n \t\t},\n \t\t\"sync\": {\n \t\t\t// Both OnceFunc and its returned closure need to be ... |
rust-lang/rust | 154,830 | miri subtree update | Subtree update of `miri` to https://github.com/rust-lang/miri/commit/ce20bd38b1a5361dee26cac090e7f74fc0530d4b.
Created using https://github.com/rust-lang/josh-sync.
r? @ghost | 21256d86e49b50364337ba7285ffaa2d90ae9609 | [
{
"filename": "Cargo.lock",
"patch": "@@ -3422,9 +3422,9 @@ dependencies = [\n \n [[package]]\n name = \"rustc-build-sysroot\"\n-version = \"0.5.12\"\n+version = \"0.5.13\"\n source = \"registry+https://github.com/rust-lang/crates.io-index\"\n-checksum = \"eec3905e8201688412f6f4b1f6c86d38b3ee6578f59ba85f413... |
vercel/next.js | 92,323 | Add RTL text support to @vercel/og | ## What?
Added support for right-to-left (RTL) text rendering in the `@vercel/og` library. This includes:
1. **Font substitution improvements**: Added `contextSubstitutionFormat3` function to handle OpenType context substitution format 3, which is required for proper RTL text shaping in languages like Arabic and Hebrew.
2. **RTL text detection and positioning**: Implemented RTL detection using Unicode ranges for Arabic, Hebrew, and related scripts. When RTL text is detected, the text positioning and alignment logic is adjusted accordingly to properly render right-to-left content.
3. **Alignment handling for RTL**: Updated text alignment logic to correctly handle `right`, `end`, `center`, `left`, and `justify` alignments when rendering RTL text.
## Why?
The `@vercel/og` library previously did not properly support RTL languages, which are used by millions of people worldwide. This fix enables proper rendering of Arabic, Hebrew, and other RTL scripts in Open Graph images generated with Next.js.
## How?
- Updated both `index.edge.js` and `index.node.js` compiled files with RTL support
- Added RTL regex pattern to detect RTL Unicode characters
- Modified text positioning calculations to account for RTL layout
- Added proper handling of text alignment in RTL context
- Added test routes for both edge and node runtimes with Arabic text examples
- Added e2e tests to verify RTL rendering works correctly
## Test Plan
Added e2e tests in `test/e2e/og-api/index.test.ts`:
- Test for RTL Arabic text rendering in edge runtime
- Test for RTL Arabic text rendering in node runtime
Both tests verify that the image is generated successfully with proper content-type and non-zero size.
https://claude.ai/code/session_0192MAXgejpjkKBgChuyTFcd | 9dd2f2ff2f47edf3c51c681b417a0f443e842410 | [
{
"filename": "packages/next/src/compiled/@vercel/og/index.edge.js",
"patch": "@@ -9854,6 +9854,12 @@ function contextSubstitutionFormat3(contextParams, subtable) {\n if (substitution) {\n substitutions.push(substitution);\n }\n+ } else if (substitutionType === \"21\")... |
nodejs/node | 62,564 | src: restrict MaybeStackBuffer string helpers to text types | Limit MaybeStackBuffer::ToString() and ToStringView to textual element types so byte buffers do not instantiate std::basic_string[_view]<unsigned char> on libc++.
This avoids the macOS/Xcode deprecation warning for `char_traits<unsigned char>` while preserving existing string helper behavior for text buffers. `uint16_t` buffers are mapped to char16_t for these conversions so UTF-16 call sites continue to work. | 69be72f1d805fc60bb4293bd21f0f9d756bab640 | [
{
"filename": "src/util.h",
"patch": "@@ -390,6 +390,16 @@ constexpr size_t strsize(const T (&)[N]) {\n return N - 1;\n }\n \n+template <typename T>\n+inline constexpr bool kMaybeStackBufferHasStringType =\n+ std::is_same_v<T, char> || std::is_same_v<T, wchar_t> ||\n+ std::is_same_v<T, char8_t> || s... |
ollama/ollama | 15,306 | model/parsers: rework gemma4 tool call handling | Replace the custom Gemma4 argument normalizer with a stricter reference-style conversion: preserve Gemma-quoted strings, quote bare keys, and then unmarshal the result as JSON.
This keeps quoted scalars as strings, preserves typed unquoted values, and adds test coverage for malformed raw-quoted inputs that the reference implementation rejects. | c6b78c7984ae10e2dc609d916452e7bc834331d7 | [
{
"filename": "model/parsers/gemma4.go",
"patch": "@@ -4,6 +4,7 @@ import (\n \t\"encoding/json\"\n \t\"errors\"\n \t\"log/slog\"\n+\t\"regexp\"\n \t\"strings\"\n \t\"unicode\"\n \n@@ -25,6 +26,11 @@ const (\n \tgemma4ToolCallCloseTag = \"<tool_call|>\"\n )\n \n+var (\n+\tgemma4QuotedStringRe = regexp.MustC... |
huggingface/transformers | 45,238 | Update `get_test_info.py` (related to tiny model creation) | # What does this PR do?
We have introduced `CausalLMModelTest` for some time, but haven't update `get_test_info.py` accordingly, which causes some issues, in particularly for tiny model creation, regarding the part of the attribute `all_model_classes`. See code change for more details, which is itself clear. | 60da0c1892ce53b59526a7e284c0cb106d50cf88 | [
{
"filename": "utils/get_test_info.py",
"patch": "@@ -15,6 +15,7 @@\n import importlib\n import os\n import sys\n+import unittest\n \n \n # This is required to make the module import works (when the python process is running from the root of the repo)\n@@ -87,11 +88,19 @@ def get_test_classes(test_file):\n ... |
facebook/react | 36,179 | Test branch react fork | <!--
Thanks for submitting a pull request!
We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.
Before submitting a pull request, please make sure the following is done:
1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
2. Run `yarn` in the repository root.
3. If you've fixed a bug or added code that should be tested, add tests!
4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
10. If you haven't already, complete the CLA.
Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->
## Summary
<!--
Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->
## How did you test this change?
<!--
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
How exactly did you verify that your PR solves the issue you wanted to solve?
If you leave this empty, your PR will very likely be closed.
-->
| 1f6bd0a582afa8b37708b5b001e6582f126cfb53 | [
{
"filename": "README.md",
"patch": "@@ -73,7 +73,7 @@ Read our [contributing guide](https://legacy.reactjs.org/docs/how-to-contribute.\n \n To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/facebook/react/labels/good%2... |
electron/electron | 50,690 | fix: dangling raw_ptr MicrotasksRunner::isolate_ | Backport of #50676
See that PR for details.
Notes: none. | ce2b8187e543ac48a79a6ed4530427714c3bd9ed | [
{
"filename": "shell/browser/javascript_environment.cc",
"patch": "@@ -86,6 +86,7 @@ JavascriptEnvironment::~JavascriptEnvironment() {\n // Otherwise cppgc::internal::Sweeper::Start will try to request a task runner\n // from the NodePlatform with an already unregistered isolate.\n locker_.reset();\n+... |
golang/go | 78,348 | runtime: truncate trace strings before inserting into trace map | traceStringTable.put inserted the full user-supplied string into the
trace map, then only truncated it to MaxEventTrailerDataSize (1024
bytes) when writing to the trace buffer. If the string exceeded the
traceRegionAlloc block size (~64KB), this caused a fatal
"traceRegion: alloc too large" crash.
Move the truncation to the top of put, before the map insertion, so
that the map key, map entry, and written output are all consistent
and bounded.
The existing truncation in writeString is retained: the emit method
also calls writeString without going through the map, so writeString
still needs its own guard.
TestStartRegionLongString reproduces the crash before the fix.
Observed in production at CockroachDB: Stopper.RunTask passes
singleflight keys (up to ~450KB) as trace region names via
trace.StartRegion. See:
https://github.com/cockroachdb/cockroach/pull/166669 for context
on the trigger. | 3c53061685d5237f9f2fc4522fce6d774776fede | [
{
"filename": "src/runtime/trace/annotation_test.go",
"patch": "@@ -8,9 +8,22 @@ import (\n \t\"context\"\n \t\"io\"\n \t. \"runtime/trace\"\n+\t\"strings\"\n \t\"testing\"\n )\n \n+func TestStartRegionLongString(t *testing.T) {\n+\t// Regression test: a region name longer than the trace region\n+\t// alloc... |
vercel/next.js | 92,321 | Reapply "simplify session dependent tasks and add TTL support (#91729)" | <!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
| a88b102e3ecdc6f2c6fc2a72d5a1bd2cb0d92f70 | [
{
"filename": "turbopack/crates/turbo-tasks-fetch/src/client.rs",
"patch": "@@ -3,7 +3,7 @@ use std::{hash::Hash, sync::LazyLock};\n use anyhow::Result;\n use quick_cache::sync::Cache;\n use turbo_rcstr::RcStr;\n-use turbo_tasks::{ReadRef, Vc, duration_span, mark_session_dependent};\n+use turbo_tasks::{Comp... |
ollama/ollama | 15,305 | ggml: fix ROCm build for cublasGemmBatchedEx reserve wrapper | Add missing cublasGemmAlgo_t to hipblasGemmAlgo_t type mapping and cast away const qualifiers that hipblasGemmBatchedEx doesn't accept. | 5a767c3588c6e94be24b7ff8d1fc4ae889892384 | [
{
"filename": "llama/patches/0020-ggml-No-alloc-mode.patch",
"patch": "@@ -229,7 +229,7 @@ diff --git a/ggml/src/ggml-cuda/common.cuh b/ggml/src/ggml-cuda/common.cuh\n index 9fcb2f9fd..e800ee8f6 100644\n --- a/ggml/src/ggml-cuda/common.cuh\n +++ b/ggml/src/ggml-cuda/common.cuh\n-@@ -37,6 +37,62 @@\n+@@ -37,... |
rust-lang/rust | 154,824 | Rollup of 6 pull requests | Successful merges:
- rust-lang/rust#147552 ([Debugger Visualizers] Optimize lookup behavior)
- rust-lang/rust#154052 (float: Fix panic at max exponential precision)
- rust-lang/rust#154706 (fix compilation of time/hermit.rs)
- rust-lang/rust#154707 (Make `substr_range` and `subslice_range` return the new `Range` type)
- rust-lang/rust#154767 (triagebot: roll library reviewers for `{coretests,alloctests}`)
- rust-lang/rust#154797 (bootstrap: Include shorthand aliases in x completions)
<!-- homu-ignore:start -->
r? @ghost
[Create a similar rollup](https://bors.rust-lang.org/queue/rust?prs=147552,154052,154706,154707,154767,154797)
<!-- homu-ignore:end -->
| 9f07f8b41a240b26c7d93b9348632b9eb9ba9144 | [
{
"filename": "src/bootstrap/src/core/config/flags.rs",
"patch": "@@ -243,7 +243,7 @@ fn normalize_args(args: &[String]) -> Vec<String> {\n \n #[derive(Debug, Clone, clap::Subcommand)]\n pub enum Subcommand {\n- #[command(aliases = [\"b\"], long_about = \"\\n\n+ #[command(visible_aliases = [\"b\"], lo... |
nodejs/node | 62,555 | build: bump GCC requirement to 13.2 | V8 can no longer be compiled with GCC 12.
<!--
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.
-->
| 73bb965e6bd455abdfc2d7131776a6f4864b9a74 | [
{
"filename": "BUILDING.md",
"patch": "@@ -156,7 +156,7 @@ Depending on the host platform, the selection of toolchains may vary.\n \n | Operating System | Compiler Versions |\n | ---------------- | ------------------------------------------------------------... |
facebook/react | 36,171 | Fix typo in README | Drafted with AI assistance, reviewed and verified manually.
| e29efb06e5b80a0944d6f15019a701cd318aba63 | [
{
"filename": "README.md",
"patch": "@@ -63,7 +63,7 @@ The main purpose of this repository is to continue evolving React core, making i\n \n ### [Code of Conduct](https://code.fb.com/codeofconduct)\n \n-Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read [the... |
electron/electron | 50,688 | fix: defer Wrappable destruction in SecondWeakCallback to a posted task | ## Description of Change
V8's second-pass weak callbacks run inside a `DisallowJavascriptExecutionScope` — they may touch the V8 API but **must not invoke JavaScript**, directly or indirectly. Several Electron `gin_helper::Wrappable` subclasses (`WebContents` in particular) emit JS events from their destructors (`'will-destroy'` / `'destroyed'`), so when `SecondWeakCallback` synchronously `delete`s the C++ object inside that scope, the destructor's `Emit()` → `node::MakeCallback` → `v8::Function::Call` aborts with:
```
# Fatal error in ../../v8/src/execution/execution.cc, line 364
# Invoke in DisallowJavascriptExecutionScope
```
This was previously latent and timing-dependent — it required GC to collect the JS wrapper from a foreground GC task posted by V8's incremental marking finalizer, which only happened under specific heap-layout / allocation-timing conditions. It surfaced as #47420, #45416, podman-desktop/podman-desktop#12409, and intermittent flakes of `spec/fixtures/crash-cases/webcontentsview-create-leak-exit`.
### Fix
Both `WrappableBase::SecondWeakCallback` and `DeprecatedWrappableBase::SecondWeakCallback` now post the deletion via `base::SequencedTaskRunner::GetCurrentDefault()->{DeleteSoon,PostTask}` so the destructor (and any `Emit()` it does) runs once V8 has left the GC scope. Falls back to synchronous deletion when no task runner is bound (early/late process lifetime).
### Regression test
`spec/fixtures/crash-cases/wrappable-gc-weak-callback-emit/` reproduces the crash deterministically on `main` by setting `v8.setFlagsFromString('--stress-incremental-marking')` (which forces foreground GC tasks on every allocation step) and leaking three `WebContentsView` instances before `app.quit()`. Verified on a Linux testing build:
| | runs | crashes |
|---|---|---|
| Before fix | 5/5 | 5 |
| After fix | 10/10 | 0 |
All 23 existing crash-case fixtures continue to pass.
### Checklist
- [x] PR description has a clear explanation of the change
- [x] `npm run lint` passes
- [x] regression test added (`spec/fixtures/crash-cases/wrappable-gc-weak-callback-emit`)
- [x] all `spec/fixtures/crash-cases/*` pass
Fixes #47420
Fixes #45416
Notes: Fixed an intermittent `Invoke in DisallowJavascriptExecutionScope` crash on application quit when a `WebContents` (or other JS-emitting native object) is garbage-collected during shutdown.
| f89c8efc9d9f3e2644a26b637b89c17b82607da6 | [
{
"filename": "shell/common/gin_helper/wrappable.cc",
"patch": "@@ -4,6 +4,7 @@\n \n #include \"shell/common/gin_helper/wrappable.h\"\n \n+#include \"base/task/sequenced_task_runner.h\"\n #include \"gin/object_template_builder.h\"\n #include \"gin/public/isolate_holder.h\"\n #include \"shell/common/gin_help... |
ollama/ollama | 15,301 | ggml: skip cublasGemmBatchedEx during graph reservation | cublasGemmBatchedEx fails during graph capture when pool allocations return fake pointers. This is triggered when NUM_PARALLEL is greater than 1 for models like gemma4 that use batched matmuls. Skip it during reservation since the memory tracking is already handled by the pool allocations.
Fixes #15249 | 0cf2922e9308b0b3e07f9c74b38b59c7367b331d | [
{
"filename": "llama/patches/0020-ggml-No-alloc-mode.patch",
"patch": "@@ -11,9 +11,9 @@ must be recreated with no-alloc set to false before loading data.\n ggml/include/ggml-backend.h | 1 +\n ggml/src/ggml-backend-impl.h | 16 +++\n ggml/src/ggml-backend.cpp | 75 ++++++++++-\n- ggml/src/... |
golang/go | 78,344 | encoding/{base32,base64}: speed up Encode | This CL clarifies (*Encoding).Encode and speeds it up by reducing the
number of bounds checks in its loop.
Here are some benchmark results (no change to allocations):
goos: darwin
goarch: arm64
pkg: encoding/base32
cpu: Apple M4
│ old │ new │
│ sec/op │ sec/op vs base │
EncodeToString-10 7.310µ ± 0% 5.308µ ± 0% -27.39% (n=180)
Encode-10 5.651µ ± 0% 3.603µ ± 0% -36.25% (n=180)
geomean 6.427µ 4.373µ -31.96%
│ old │ new │
│ B/s │ B/s vs base │
EncodeToString-10 1.044Gi ± 0% 1.437Gi ± 0% +37.71% (p=0.000 n=180)
Encode-10 1.350Gi ± 0% 2.118Gi ± 0% +56.88% (p=0.000 n=180)
geomean 1.187Gi 1.745Gi +46.98%
pkg: encoding/base64
│ old │ new │
│ sec/op │ sec/op vs base │
EncodeToString-10 7.058µ ± 0% 6.034µ ± 0% -14.51% (n=180)
│ old │ new │
│ B/s │ B/s vs base │
EncodeToString-10 1.081Gi ± 0% 1.264Gi ± 0% +16.97% (p=0.000 n=180)
Updates #20206 | 1caac3d65532fefacbbed57f11a4a49273f173e2 | [
{
"filename": "src/encoding/base32/base32.go",
"patch": "@@ -127,61 +127,59 @@ func (enc *Encoding) Encode(dst, src []byte) {\n \t// outside of the loop to speed up the encoder.\n \t_ = enc.encode\n \n-\tdi, si := 0, 0\n-\tn := (len(src) / 5) * 5\n-\tfor si < n {\n+\tfor len(src) >= 5 {\n \t\t// Combining t... |
huggingface/transformers | 45,228 | More fix for tiny model creation | # What does this PR do?
All of this are trivial ... (maybe except "evolla") | c142f63cccd50ddc2eb012fb5afb720d71600dec | [
{
"filename": "src/transformers/models/videomt/modular_videomt.py",
"patch": "@@ -15,6 +15,7 @@\n from dataclasses import dataclass\n \n import torch\n+from huggingface_hub.dataclasses import strict\n from torch import nn\n \n from ...file_utils import ModelOutput\n@@ -37,6 +38,7 @@\n \n \n @auto_docstring(... |
vercel/next.js | 92,320 | Revert "simplify session dependent tasks and add TTL support (#91729)" | This is causing OOMs in some applications running with a persistent cache
See discussion: https://vercel.slack.com/archives/C03EWR7LGEN/p1775159630054759
The issue appears to be invalidating the chunk graph in an odd way that causes us to allocate an ~infinite number of error strings | 4a6d432aa34953347986ef91ce5b96026b651365 | [
{
"filename": "turbopack/crates/turbo-tasks-backend/src/backend/mod.rs",
"patch": "@@ -363,37 +363,6 @@ impl<B: BackingStorage> TurboTasksBackendInner<B> {\n self.options.dependency_tracking\n }\n \n- /// Sets the initial aggregation number for a newly created task. Root tasks get `u32::MAX`\... |
nodejs/node | 62,552 | tools: bump the eslint group in /tools/eslint with 2 updates | Bumps the eslint group in /tools/eslint with 2 updates: [@eslint/markdown](https://github.com/eslint/markdown) and [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc).
Updates `@eslint/markdown` from 7.5.1 to 8.0.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/eslint/markdown/releases"><code>@eslint/markdown</code>'s releases</a>.</em></p>
<blockquote>
<h2>v8.0.0</h2>
<h2><a href="https://github.com/eslint/markdown/compare/v7.5.1...v8.0.0">8.0.0</a> (2026-03-24)</h2>
<h3>⚠ BREAKING CHANGES</h3>
<ul>
<li>Require Node.js ^20.19.0 || ^22.13.0 || >=24 (<a href="https://redirect.github.com/eslint/markdown/issues/561">#561</a>)</li>
<li>remove <code>/types</code> export (<a href="https://redirect.github.com/eslint/markdown/issues/564">#564</a>)</li>
</ul>
<h3>Features</h3>
<ul>
<li>add fenced-code-meta rule (<a href="https://redirect.github.com/eslint/markdown/issues/512">#512</a>) (<a href="https://github.com/eslint/markdown/commit/f30e1c992d12165d2c88f6eec042eea84e2ff948">f30e1c9</a>)</li>
<li>add option to no-duplicate/unused-definitions rules (<a href="https://redirect.github.com/eslint/markdown/issues/616">#616</a>) (<a href="https://github.com/eslint/markdown/commit/d189c5e2c5ff8d03c3d7e16905a227d5c5e584ac">d189c5e</a>)</li>
<li>fix incorrect regex pattern in <code>no-multiple-h1</code> (<a href="https://redirect.github.com/eslint/markdown/issues/624">#624</a>) (<a href="https://github.com/eslint/markdown/commit/e57e39835f50ec1198f7fadb5e5cd600383fbc6c">e57e398</a>)</li>
<li>fix incorrect regex pattern in <code>require-alt-text</code> and <code>no-html</code> (<a href="https://redirect.github.com/eslint/markdown/issues/604">#604</a>) (<a href="https://github.com/eslint/markdown/commit/cd264d07d9b271608c6d59365c42a499a595a767">cd264d0</a>)</li>
<li>Require Node.js ^20.19.0 || ^22.13.0 || >=24 (<a href="https://redirect.github.com/eslint/markdown/issues/561">#561</a>) (<a href="https://github.com/eslint/markdown/commit/f6d2a22ae210bcdee9c6487c13bab11c5403eed2">f6d2a22</a>)</li>
<li>support Math (<a href="https://redirect.github.com/eslint/markdown/issues/617">#617</a>) (<a href="https://github.com/eslint/markdown/commit/cc03b5fae54337f5de012a41c5af438b281818a1">cc03b5f</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>false positive triggered by comments in <code>no-html</code> (<a href="https://github.com/eslint/markdown/commit/a2ccff86ba536894fddbcfc89cb8d56567a22ac4">a2ccff8</a>)</li>
<li>false positive triggered by HTML inside comments in <code>no-html</code> (<a href="https://redirect.github.com/eslint/markdown/issues/592">#592</a>) (<a href="https://github.com/eslint/markdown/commit/a2ccff86ba536894fddbcfc89cb8d56567a22ac4">a2ccff8</a>)</li>
<li>false positives for inline elements in <code>no-reversed-media-syntax</code> (<a href="https://redirect.github.com/eslint/markdown/issues/597">#597</a>) (<a href="https://github.com/eslint/markdown/commit/8538c109af89c1cb4e7131f1287fbb4e3267cc96">8538c10</a>)</li>
<li>recognize <code>Definition</code> node in <code>no-missing-link-fragments</code> (<a href="https://redirect.github.com/eslint/markdown/issues/603">#603</a>) (<a href="https://github.com/eslint/markdown/commit/9b58e36ee78fb327392a8fd4dcb2af69bea518b3">9b58e36</a>)</li>
<li>recognize HTML heading in <code>no-missing-link-fragments</code> (<a href="https://redirect.github.com/eslint/markdown/issues/583">#583</a>) (<a href="https://github.com/eslint/markdown/commit/bd9dfa38fb5af611c018f5ae8d163ff28e936c56">bd9dfa3</a>)</li>
<li>remove <code>/types</code> export (<a href="https://redirect.github.com/eslint/markdown/issues/564">#564</a>) (<a href="https://github.com/eslint/markdown/commit/28eecf6f178ecb31e47cc67dbe32c6286aae4dec">28eecf6</a>)</li>
<li>update dependency <code>@eslint/plugin-kit</code> to ^0.6.0 (<a href="https://redirect.github.com/eslint/markdown/issues/584">#584</a>) (<a href="https://github.com/eslint/markdown/commit/be16763a550574febaba2dfa4f7c3ad197c3b83c">be16763</a>)</li>
<li>update eslint (<a href="https://redirect.github.com/eslint/markdown/issues/629">#629</a>) (<a href="https://github.com/eslint/markdown/commit/4c75af059f27afd4f94ab5e42882bfcead5e0ba4">4c75af0</a>)</li>
<li>use types from <code>@eslint/plugin-kit</code> and update <code>@eslint/core</code> (<a href="https://redirect.github.com/eslint/markdown/issues/607">#607</a>) (<a href="https://github.com/eslint/markdown/commit/f5d4ce075e7285019a0be274342dfff769a3aa34">f5d4ce0</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/eslint/markdown/blob/main/CHANGELOG.md"><code>@eslint/markdown</code>'s changelog</a>.</em></p>
<blockquote>
<h2><a href="https://github.com/eslint/markdown/compare/v7.5.1...v8.0.0">8.0.0</a> (2026-03-24)</h2>
<h3>⚠ BREAKING CHANGES</h3>
<ul>
<li>Require Node.js ^20.19.0 || ^22.13.0 || >=24 (<a href="https://redirect.github.com/eslint/markdown/issues/561">#561</a>)</li>
<li>remove <code>/types</code> export (<a href="https://redirect.github.com/eslint/markdown/issues/564">#564</a>)</li>
</ul>
<h3>Features</h3>
<ul>
<li>add fenced-code-meta rule (<a href="https://redirect.github.com/eslint/markdown/issues/512">#512</a>) (<a href="https://github.com/eslint/markdown/commit/f30e1c992d12165d2c88f6eec042eea84e2ff948">f30e1c9</a>)</li>
<li>add option to no-duplicate/unused-definitions rules (<a href="https://redirect.github.com/eslint/markdown/issues/616">#616</a>) (<a href="https://github.com/eslint/markdown/commit/d189c5e2c5ff8d03c3d7e16905a227d5c5e584ac">d189c5e</a>)</li>
<li>fix incorrect regex pattern in <code>no-multiple-h1</code> (<a href="https://redirect.github.com/eslint/markdown/issues/624">#624</a>) (<a href="https://github.com/eslint/markdown/commit/e57e39835f50ec1198f7fadb5e5cd600383fbc6c">e57e398</a>)</li>
<li>fix incorrect regex pattern in <code>require-alt-text</code> and <code>no-html</code> (<a href="https://redirect.github.com/eslint/markdown/issues/604">#604</a>) (<a href="https://github.com/eslint/markdown/commit/cd264d07d9b271608c6d59365c42a499a595a767">cd264d0</a>)</li>
<li>Require Node.js ^20.19.0 || ^22.13.0 || >=24 (<a href="https://redirect.github.com/eslint/markdown/issues/561">#561</a>) (<a href="https://github.com/eslint/markdown/commit/f6d2a22ae210bcdee9c6487c13bab11c5403eed2">f6d2a22</a>)</li>
<li>support Math (<a href="https://redirect.github.com/eslint/markdown/issues/617">#617</a>) (<a href="https://github.com/eslint/markdown/commit/cc03b5fae54337f5de012a41c5af438b281818a1">cc03b5f</a>)</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>false positive triggered by comments in <code>no-html</code> (<a href="https://github.com/eslint/markdown/commit/a2ccff86ba536894fddbcfc89cb8d56567a22ac4">a2ccff8</a>)</li>
<li>false positive triggered by HTML inside comments in <code>no-html</code> (<a href="https://redirect.github.com/eslint/markdown/issues/592">#592</a>) (<a href="https://github.com/eslint/markdown/commit/a2ccff86ba536894fddbcfc89cb8d56567a22ac4">a2ccff8</a>)</li>
<li>false positives for inline elements in <code>no-reversed-media-syntax</code> (<a href="https://redirect.github.com/eslint/markdown/issues/597">#597</a>) (<a href="https://github.com/eslint/markdown/commit/8538c109af89c1cb4e7131f1287fbb4e3267cc96">8538c10</a>)</li>
<li>recognize <code>Definition</code> node in <code>no-missing-link-fragments</code> (<a href="https://redirect.github.com/eslint/markdown/issues/603">#603</a>) (<a href="https://github.com/eslint/markdown/commit/9b58e36ee78fb327392a8fd4dcb2af69bea518b3">9b58e36</a>)</li>
<li>recognize HTML heading in <code>no-missing-link-fragments</code> (<a href="https://redirect.github.com/eslint/markdown/issues/583">#583</a>) (<a href="https://github.com/eslint/markdown/commit/bd9dfa38fb5af611c018f5ae8d163ff28e936c56">bd9dfa3</a>)</li>
<li>remove <code>/types</code> export (<a href="https://redirect.github.com/eslint/markdown/issues/564">#564</a>) (<a href="https://github.com/eslint/markdown/commit/28eecf6f178ecb31e47cc67dbe32c6286aae4dec">28eecf6</a>)</li>
<li>update dependency <code>@eslint/plugin-kit</code> to ^0.6.0 (<a href="https://redirect.github.com/eslint/markdown/issues/584">#584</a>) (<a href="https://github.com/eslint/markdown/commit/be16763a550574febaba2dfa4f7c3ad197c3b83c">be16763</a>)</li>
<li>update eslint (<a href="https://redirect.github.com/eslint/markdown/issues/629">#629</a>) (<a href="https://github.com/eslint/markdown/commit/4c75af059f27afd4f94ab5e42882bfcead5e0ba4">4c75af0</a>)</li>
<li>use types from <code>@eslint/plugin-kit</code> and update <code>@eslint/core</code> (<a href="https://redirect.github.com/eslint/markdown/issues/607">#607</a>) (<a href="https://github.com/eslint/markdown/commit/f5d4ce075e7285019a0be274342dfff769a3aa34">f5d4ce0</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/eslint/markdown/commit/3cafcda73ee5ec9a614378101d689bc62f48ba18"><code>3cafcda</code></a> chore: release 8.0.0 🚀 (<a href="https://redirect.github.com/eslint/markdown/issues/594">#594</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/cc03b5fae54337f5de012a41c5af438b281818a1"><code>cc03b5f</code></a> feat: support Math (<a href="https://redirect.github.com/eslint/markdown/issues/617">#617</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/23dc0c6fa0b54412928dc145e9a1692cf01b0167"><code>23dc0c6</code></a> chore: simplify <code>package.json</code> import and add cjs import type test (<a href="https://redirect.github.com/eslint/markdown/issues/634">#634</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/493de5db26a997d6d7494e94bdaace1ebd32bec3"><code>493de5d</code></a> chore: update dependency knip to v6 (<a href="https://redirect.github.com/eslint/markdown/issues/636">#636</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/5b266ef5ac0d8c59631f5dff265a3e08e73cd29b"><code>5b266ef</code></a> chore: update dependency <code>@eslint/json</code> to ^1.2.0 (<a href="https://redirect.github.com/eslint/markdown/issues/635">#635</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/e57e39835f50ec1198f7fadb5e5cd600383fbc6c"><code>e57e398</code></a> feat: fix incorrect regex pattern in <code>no-multiple-h1</code> (<a href="https://redirect.github.com/eslint/markdown/issues/624">#624</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/bd9dfa38fb5af611c018f5ae8d163ff28e936c56"><code>bd9dfa3</code></a> fix: recognize HTML heading in <code>no-missing-link-fragments</code> (<a href="https://redirect.github.com/eslint/markdown/issues/583">#583</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/68046a73f3dc7d3ddf5141d9789c328135253c9d"><code>68046a7</code></a> chore: ignore <code>eslint-v9</code> for renovate (<a href="https://redirect.github.com/eslint/markdown/issues/632">#632</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/faadc59403a84d26932ce7f98a44751fae5e20cc"><code>faadc59</code></a> test: ensure <code>@eslint/markdown</code> works with both ESLint v9 and v10 (<a href="https://redirect.github.com/eslint/markdown/issues/593">#593</a>)</li>
<li><a href="https://github.com/eslint/markdown/commit/b80d942ad79f6ea66bcf6ad86d03c63c5ebc59b7"><code>b80d942</code></a> chore: update <code>eslint-plugin-eslint-plugin</code> to v7 (<a href="https://redirect.github.com/eslint/markdown/issues/631">#631</a>)</li>
<li>Additional commits viewable in <a href="https://github.com/eslint/markdown/compare/v7.5.1...v8.0.0">compare view</a></li>
</ul>
</details>
<br />
Updates `eslint-plugin-jsdoc` from 62.8.0 to 62.8.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/gajus/eslint-plugin-jsdoc/releases">eslint-plugin-jsdoc's releases</a>.</em></p>
<blockquote>
<h2>v62.8.1</h2>
<h2><a href="https://github.com/gajus/eslint-plugin-jsdoc/compare/v62.8.0...v62.8.1">62.8.1</a> (2026-03-25)</h2>
<h3>Bug Fixes</h3>
<ul>
<li><strong><code>valid-types</code>:</strong> allow required default names; fixes <a href="https://redirect.github.com/gajus/eslint-plugin-jsdoc/issues/1675">#1675</a> (<a href="https://github.com/gajus/eslint-plugin-jsdoc/commit/bca557be5a15cd0e4c8da8268d2e863019bc2333">bca557b</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/gajus/eslint-plugin-jsdoc/commit/bca557be5a15cd0e4c8da8268d2e863019bc2333"><code>bca557b</code></a> fix(<code>valid-types</code>): allow required default names; fixes <a href="https://redirect.github.com/gajus/eslint-plugin-jsdoc/issues/1675">#1675</a></li>
<li><a href="https://github.com/gajus/eslint-plugin-jsdoc/commit/78335ff9e7b66790446d2141328464666c011bb4"><code>78335ff</code></a> chore(deps): bump picomatch from 2.3.1 to 2.3.2</li>
<li><a href="https://github.com/gajus/eslint-plugin-jsdoc/commit/7bc2525fce14a74d695cffbc14a287423b645e63"><code>7bc2525</code></a> chore(deps): bump undici from 6.23.0 to 6.24.0</li>
<li>See full diff in <a href="https://github.com/gajus/eslint-plugin-jsdoc/compare/v62.8.0...v62.8.1">compare view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions
</details> | 4f44a1e3bbe1c94951c1c98a5225fc481ea63554 | [
{
"filename": "tools/eslint/package-lock.json",
"patch": "@@ -12,11 +12,11 @@\n \"@babel/eslint-parser\": \"^8.0.0-rc.3\",\n \"@babel/plugin-syntax-import-source\": \"^8.0.0-rc.3\",\n \"@eslint/js\": \"^10.0.1\",\n- \"@eslint/markdown\": \"^7.5.1\",\n+ \"@eslint/markdow... |
rust-lang/rust | 154,815 | Rollup of 8 pull requests | Successful merges:
- rust-lang/rust#149868 (rustc: Stop passing `--allow-undefined` on wasm targets)
- rust-lang/rust#153555 (Clarified docs in std::sync::RwLock + added test to ensure that max reader count is respected)
- rust-lang/rust#152851 (Fix SGX delayed host lookup via ToSocketAddr)
- rust-lang/rust#154051 (use libm for acosh and asinh)
- rust-lang/rust#154581 (More informative `Debug for vec::ExtractIf`)
- rust-lang/rust#154461 (Edit the docs new_in() and with_capacity_in())
- rust-lang/rust#154526 (Panic/return false on overflow in no_threads read/try_read impl)
- rust-lang/rust#154798 (rustdoc-search: match path components on words)
<!-- homu-ignore:start -->
r? @ghost
[Create a similar rollup](https://bors.rust-lang.org/queue/rust?prs=149868,153555,152851,154051,154581,154461,154526,154798)
<!-- homu-ignore:end -->
| 42108257e6d02616cc6015ccc5f1c86f7a9ccbdf | [
{
"filename": "src/librustdoc/html/static/js/search.js",
"patch": "@@ -2799,6 +2799,8 @@ class DocSearch {\n result_list.sort((aaa, bbb) => {\n const aai = aaa.item;\n const bbi = bbb.item;\n+ const ap = aai.modulePath !== undefined ... |
facebook/react | 36,163 | fix: potential null dereference in react compiler configuration (#32571) | Fixes #32571
<!--
Thanks for submitting a pull request!
We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.
Before submitting a pull request, please make sure the following is done:
1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
2. Run `yarn` in the repository root.
3. If you've fixed a bug or added code that should be tested, add tests!
4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
10. If you haven't already, complete the CLA.
Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->
## Summary
Fix potential null dereference in React Compiler configuration by adding a null check for the plugins array.
The babel.config-react-compiler.js file contains a hack comment about Zod spreading values in React Compiler's build artifact. If the baseConfig.plugins array is null or undefined, the assignment `plugins: baseConfig.plugins` will cause a runtime TypeError when the compiler tries to process the configuration. This could crash the build process or cause incorrect transpilation.
## How did you test this change?
- Modified the babel.config-react-compiler.js file to add a null check before assigning plugins
- Verified the change prevents TypeError when baseConfig.plugins is null or undefined
- Confirmed the build process continues to work correctly with valid plugin arrays
``` | 1d57229123c9337ca38401598f85aea4b2381768 | [
{
"filename": "babel.config-react-compiler.js",
"patch": "@@ -15,5 +15,5 @@\n const baseConfig = require('./babel.config-ts');\n \n module.exports = {\n- plugins: baseConfig.plugins,\n+ plugins: Array.isArray(baseConfig.plugins) ? baseConfig.plugins : [],\n };",
"additions": 1,
"deletions": 1
}
... |
ollama/ollama | 15,296 | gemma4: enable flash attention | ~~This patches additional code paths in the GGML CUDA backend for the memory prediction flow.~~
~~Fixes #15249~~
Enable flash attention for gemma4 | 67a4af39372555b7da2fddd1f17f22bd5d188cb0 | [
{
"filename": "fs/ggml/ggml.go",
"patch": "@@ -890,6 +890,7 @@ func (f GGML) FlashAttention() bool {\n \treturn slices.Contains([]string{\n \t\t\"bert\",\n \t\t\"gemma3\",\n+\t\t\"gemma4\",\n \t\t\"glm4moelite\",\n \t\t\"glmocr\",\n \t\t\"gptoss\", \"gpt-oss\",",
"additions": 1,
"deletions": 0
}
] |
electron/electron | 50,687 | fix: propagate requesting frame through sync permission checks | Backport of #50679
See that PR for details.
Notes: no-notes | a3e84658843935ebea06e326793da03ffad3147b | [
{
"filename": "shell/browser/api/electron_api_web_contents.cc",
"patch": "@@ -1739,7 +1739,8 @@ bool WebContents::CheckMediaAccessPermission(\n content::WebContents::FromRenderFrameHost(render_frame_host);\n auto* permission_helper =\n WebContentsPermissionHelper::FromWebContents(web_contents)... |
huggingface/transformers | 45,225 | fix: hf-doc-builder insallation was failing | # What does this PR do?
The `dev` extra now indirectly pulls hf-doc-builder so the install step failed.
We also need to update to current main for the latest features | f2d19afa2f7071e39740a223e03c4ecbeec1416f | [
{
"filename": "docker/transformers-doc-builder/Dockerfile",
"patch": "@@ -5,6 +5,10 @@ RUN apt update\n RUN git clone https://github.com/huggingface/transformers\n \n RUN python3 -m pip install --no-cache-dir --upgrade pip && python3 -m pip install --no-cache-dir ./transformers[dev]\n+\n+# We want to use th... |
nodejs/node | 62,551 | meta: bump cachix/install-nix-action from 31.9.1 to 31.10.3 | Bumps [cachix/install-nix-action](https://github.com/cachix/install-nix-action) from 31.9.1 to 31.10.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/cachix/install-nix-action/releases">cachix/install-nix-action's releases</a>.</em></p>
<blockquote>
<h2>v31.10.3</h2>
<h2>What's Changed</h2>
<ul>
<li>nix: 2.34.2 -> 2.34.4 by <a href="https://github.com/github-actions"><code>@github-actions</code></a>[bot] in <a href="https://redirect.github.com/cachix/install-nix-action/pull/271">cachix/install-nix-action#271</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/cachix/install-nix-action/compare/v31...v31.10.3">https://github.com/cachix/install-nix-action/compare/v31...v31.10.3</a></p>
<h2>v31.10.2</h2>
<h2>What's Changed</h2>
<ul>
<li>nix: 2.34.1 -> 2.34.2 by <a href="https://github.com/github-actions"><code>@github-actions</code></a>[bot] in <a href="https://redirect.github.com/cachix/install-nix-action/pull/270">cachix/install-nix-action#270</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/cachix/install-nix-action/compare/v31...v31.10.2">https://github.com/cachix/install-nix-action/compare/v31...v31.10.2</a></p>
<h2>v31.10.1</h2>
<h2>What's Changed</h2>
<ul>
<li>nix: 2.34.0 -> 2.34.1 by <a href="https://github.com/github-actions"><code>@github-actions</code></a>[bot] in <a href="https://redirect.github.com/cachix/install-nix-action/pull/269">cachix/install-nix-action#269</a>
Fixes a bug introduced in 2.34.0 that made the Nix daemon fail to load authentication keys configured by <code>cachix-action</code>.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/cachix/install-nix-action/compare/v31.10.0...v31.10.1">https://github.com/cachix/install-nix-action/compare/v31.10.0...v31.10.1</a></p>
<h2>v31.10.0</h2>
<h2>What's Changed</h2>
<ul>
<li>nix: 2.33.3 -> 2.34.0 by <a href="https://github.com/github-actions"><code>@github-actions</code></a>[bot] in <a href="https://redirect.github.com/cachix/install-nix-action/pull/267">cachix/install-nix-action#267</a>
Release notes: <a href="https://discourse.nixos.org/t/nix-2-34-0-released/75818">https://discourse.nixos.org/t/nix-2-34-0-released/75818</a></li>
</ul>
<p>⚠️ Nix 2.34.0 contains a regression that, under certain scenarios (a <code>trusted-user</code> + a client-side <code>netrc-file</code>), breaks authentication with private caches that rely on <code>netrc</code> files. This regression affects <code>cachix/cachix-action</code>.</p>
<p><strong>UPD: 2.34.1 has been released with a patch for the authentication issue</strong></p>
<p><strong>Full Changelog</strong>: <a href="https://github.com/cachix/install-nix-action/compare/v31.9.1...v31.10.0">https://github.com/cachix/install-nix-action/compare/v31.9.1...v31.10.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/cachix/install-nix-action/commit/96951a368ba55167b55f1c916f7d416bac6505fe"><code>96951a3</code></a> Merge pull request <a href="https://redirect.github.com/cachix/install-nix-action/issues/271">#271</a> from cachix/create-pull-request/patch</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/62811694457f97eeef0c40b184d0a791495b3825"><code>6281169</code></a> nix: 2.34.2 -> 2.34.4</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/51f3067b56fe8ae331890c77d4e454f6d60615ff"><code>51f3067</code></a> Revert "ci: use 25.11 for channel tests"</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/15118c17f94ae94b32a2a51839986d18c508f12f"><code>15118c1</code></a> ci: use 25.11 for channel tests</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/e1ac057965e5be579300ea6beb1f0e9a8a607344"><code>e1ac057</code></a> Merge pull request <a href="https://redirect.github.com/cachix/install-nix-action/issues/270">#270</a> from cachix/create-pull-request/patch</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/d181b9642fe3b3f85724b0337c37dca054cb4ef8"><code>d181b96</code></a> nix: 2.34.1 -> 2.34.2</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/1ca7d21a94afc7c957383a2d217460d980de4934"><code>1ca7d21</code></a> Merge pull request <a href="https://redirect.github.com/cachix/install-nix-action/issues/269">#269</a> from cachix/create-pull-request/patch</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/b6137343272cafad497671822066f2a10ded6fef"><code>b613734</code></a> nix: 2.34.0 -> 2.34.1</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/19effe9fe722874e6d46dd7182e4b8b7a43c4a99"><code>19effe9</code></a> Merge pull request <a href="https://redirect.github.com/cachix/install-nix-action/issues/267">#267</a> from cachix/create-pull-request/patch</li>
<li><a href="https://github.com/cachix/install-nix-action/commit/d3f3b99dd19236cb244609944767f2864ec646ee"><code>d3f3b99</code></a> nix: 2.33.3 -> 2.34.0</li>
<li>See full diff in <a href="https://github.com/cachix/install-nix-action/compare/2126ae7fc54c9df00dd18f7f18754393182c73cd...96951a368ba55167b55f1c916f7d416bac6505fe">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | d9829783687db9ccd7784403aca95547ed05654a | [
{
"filename": ".github/workflows/linters.yml",
"patch": "@@ -149,7 +149,7 @@ jobs:\n persist-credentials: false\n sparse-checkout: '*.nix'\n sparse-checkout-cone-mode: false\n- - uses: cachix/install-nix-action@2126ae7fc54c9df00dd18f7f18754393182c73cd # v31.9.1\n+ - ... |
golang/go | 78,302 | cmd/compile/internal/types2: avoid panic on recursive generic types | The typeWriter was panicking when encountering a cycle during type string
generation for generic instances. By providing a placeholder string
instead of panicking, we allow the compiler to complete the type
checking process safely.
Fixes #78296 | 0a7018ac98954ee6076367b4a77905db2469f31b | [
{
"filename": "doc/next/78137.md",
"patch": "@@ -0,0 +1,2 @@\n+net: UnixConn read methods now return io.EOF directly instead of\r\n+wrapping it in net.OpError when the underlying read returns EOF.\n\\ No newline at end of file",
"additions": 2,
"deletions": 0
},
{
"filename": "src/net/http/i... |
vercel/next.js | 92,317 | Improve existing dev server error message to suggest using it | <!-- CURSOR_AGENT_PR_BODY_BEGIN -->
### What?
Improves the error message shown when a user tries to start `next dev` while another dev server is already running in the same directory.
### Why?
Previously, the error message only suggested killing the existing process (`Run kill <pid> to stop it.`). This wasn't the best advice — often the user just wants to access the already-running dev server rather than kill it and start a new one.
### How?
Updated the error message in `packages/next/src/build/lockfile.ts` to present both options:
1. Access the existing server at its URL
2. Kill the process if they want to start a new one
**Before:**
```
✖ Another next dev server is already running.
- Local: http://localhost:3000
- PID: 61479
- Dir: /path/to/project
- Log: .next/dev/logs/next-development.log
Run kill 61479 to stop it.
```
**After:**
```
✖ Another next dev server is already running.
- Local: http://localhost:3000
- PID: 61479
- Dir: /path/to/project
- Log: .next/dev/logs/next-development.log
You can access the existing server at http://localhost:3000,
or run kill 61479 to stop it and start a new one.
```
Updated the lockfile test regex to match the new message format.
<!-- CURSOR_AGENT_PR_BODY_END -->
[Slack Thread](https://vercel.slack.com/archives/C046HAU4H7F/p1775173304387809?thread_ts=1775173304.387809&cid=C046HAU4H7F)
<div><a href="https://cursor.com/agents/bc-0bb3085b-1fd1-56c3-8617-cd8a32d8c376"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-0bb3085b-1fd1-56c3-8617-cd8a32d8c376"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div>
| beaa9b9617bec03f48e84d4475502c2192fd92a2 | [
{
"filename": "packages/next/src/build/lockfile.ts",
"patch": "@@ -240,36 +240,26 @@ export class Lockfile {\n *\n * If this is not called, the lock will be released by the operating system\n * when the file handle is closed during process exit.\n- *\n- * This method is idempotent — calling it ... |
rust-lang/rust | 154,809 | Clippy subtree update | r? Manishearth
2 days late due to some sync difficulties.
| b8ce22d75c67382fd9a9c3395b6695fea908feb8 | [
{
"filename": "clippy_lints/src/manual_is_ascii_check.rs",
"patch": "@@ -91,6 +91,13 @@ enum CharRange {\n \n impl<'tcx> LateLintPass<'tcx> for ManualIsAsciiCheck {\n fn check_expr(&mut self, cx: &LateContext<'tcx>, expr: &'tcx Expr<'_>) {\n+ if !matches!(\n+ expr.kind,\n+ E... |
facebook/react | 36,160 | [Fiber] Fix context propagation into Suspense fallbacks | ## Summary
When a context value changes above a Suspense boundary that is showing its fallback, context consumers inside the fallback do not re-render — they display stale values.
`propagateContextChanges`, upon encountering a suspended Suspense boundary, marks the boundary for retry but stops traversing into its children entirely (`nextFiber = null`). This skips both the hidden primary subtree (intentional — those fibers may not exist) and the visible fallback subtree (a bug — those fibers are committed and visible to the user).
The fix skips the primary OffscreenComponent and continues traversal into the FallbackFragment, so fallback context consumers are found and marked for re-render.
In practice this often goes unnoticed because it's uncommon to read context inside a Suspense fallback, and when some other update (like a prop change) flows into the fallback it sidesteps the propagation path entirely. React Compiler makes the bug more likely to surface since it memoizes more aggressively, reducing the chance of an incidental re-render masking the stale value.
## Test plan
- Added regression test `'context change propagates to Suspense fallback (memo boundary)'` in `ReactContextPropagation-test.js`
- Verified the test fails without the fix and passes with it
- All existing context propagation, Suspense, memo, and hooks tests pass | 20d7378eab7eeb289798bc2ce25620116e6dfe2a | [
{
"filename": "packages/react-reconciler/src/ReactFiberNewContext.js",
"patch": "@@ -323,12 +323,23 @@ function propagateContextChanges<T>(\n renderLanes,\n workInProgress,\n );\n- if (!forcePropagateEntireTree) {\n- // During lazy propagation, we can defer propagating chan... |
ollama/ollama | 15,256 | ggml-metal: fix tensor API probe and bf16/f16 type mismatch on M5 | ## Summary
- Fix tensor API probe tile sizes `(8,8)` → `(16,16)` to match upstream llama.cpp, preventing false `has_tensor=false` on M5+ hardware
- Remove mixed `bfloat`/`half` kernel instantiations (`kernel_mul_mm_bf16_f16`, `kernel_mul_mm_id_bf16_f16`) that trigger `static_assert` failures in Apple's MPP framework when tensor API is enabled
## Problem
On Apple M5 devices (MTLGPUFamilyMetal4), two cascading failures prevent GPU inference:
1. **Tensor probe failure**: The runtime `matmul2d_descriptor(8, 8, dynamic_extent)` test shader fails to compile, incorrectly setting `has_tensor=false`. Upstream llama.cpp fixed this by using `(16, 16)` tile sizes.
2. **Main library crash**: When the probe *does* pass (or with the tile fix applied), the embedded Metal library fails to compile because `kernel_mul_mm_bf16_f16` and `kernel_mul_mm_id_bf16_f16` mix `bfloat` and `half` operand types in `matmul2d::run()`. Apple's MPP headers enforce strict type matching via `static_assert`, causing a `SIGABRT` during model load.
## Changes
| File | Change |
|------|--------|
| `ggml-metal-device.m` | `matmul2d_descriptor(8,8)` → `(16,16)` in f16 and bf16 tensor probes |
| `ggml-metal.metal` | Remove `kernel_mul_mm_bf16_f16` and `kernel_mul_mm_id_bf16_f16` |
| `ggml-metal-embed.metal` | Same removal in embedded library source |
## References
- Upstream fix: [llama.cpp#18456](https://github.com/ggml-org/llama.cpp/pull/18456)
- Related PRs: #14604, #14996, #13701
- Fixes: #14432, #13460, #13867
## Test plan
- [ ] Build from source on Apple M5 Max (macOS 26)
- [ ] Verify `has tensor = true` in debug output
- [ ] Verify Metal library compiles without `static_assert` errors
- [ ] Run model inference (e.g. `ollama run gemma4:26b --verbose`)
- [ ] Verify GPU acceleration is active (not CPU fallback)
🤖 Generated with [Claude Code](https://claude.com/claude-code) | b2bec1f287f07a7b8d01903c65d93e0738070fe8 | [
{
"filename": "ml/backend/ggml/ggml/src/ggml-metal/ggml-metal-device.m",
"patch": "@@ -683,7 +683,7 @@ ggml_metal_device_t ggml_metal_device_init(void) {\n \" auto tB = B.slice((int)tgid.x, 0); \\n\"\n \" \\n\"\n \" matmul2d< \\n\"\n- ... |
huggingface/transformers | 45,224 | remove unnecessary entries in some auto model mappings | # What does this PR do?
Fix for tiny model | 5701dbd8e5b87b0ed0f9feab46c13725a7dc4c19 | [
{
"filename": "src/transformers/models/auto/modeling_auto.py",
"patch": "@@ -1009,7 +1009,6 @@ class _BaseModelWithGenerate(PreTrainedModel, GenerationMixin):\n (\"perception_lm\", \"PerceptionLMForConditionalGeneration\"),\n (\"pi0\", \"PI0ForConditionalGeneration\"),\n (\"pix2struc... |
golang/go | 78,265 | crypto/x509/pkix: avoid quadratic string concatenation in RDNSequence.String | RDNSequence.String builds its result using repeated s += ... inside
nested loops, leading to O(N²) time and memory complexity.
A certificate with many Subject or Issuer RDN entries can therefore
cause excessive CPU and memory usage when String is called.
Switch to strings.Builder to construct the output, reducing complexity
to O(N) without changing behavior.
This follows the same approach used to fix CVE-2025-61729
(HostnameError.Error), which addressed the same quadratic concatenation
pattern. | b0706c20655d1a263c3a989b76c0c25796c900df | [
{
"filename": "src/crypto/x509/pkix/pkix.go",
"patch": "@@ -11,6 +11,7 @@ import (\n \t\"encoding/hex\"\n \t\"fmt\"\n \t\"math/big\"\n+\t\"strings\"\n \t\"time\"\n )\n \n@@ -38,23 +39,25 @@ var attributeTypeNames = map[string]string{\n // String returns a string representation of the sequence r,\n // roughl... |
vercel/next.js | 92,316 | fix: add @deprecated annotation to experimental.useCache | ### What?
Add a `@deprecated` JSDoc annotation to `experimental.useCache` in `config-shared.ts`, pointing to `cacheComponents: true` as the successor.
### Why?
`experimental.cacheComponents` already has `@deprecated use top-level cacheComponents instead`, but `experimental.useCache` has no deprecation notice despite `cacheComponents: true` being the documented successor. This causes both developers and AI coding agents to use the old flag, since nothing in the type definitions signals it's deprecated. IDEs and agents rely on JSDoc annotations for guidance.
### How?
Replace the existing JSDoc comment on `experimental.useCache` with `@deprecated use top-level cacheComponents instead`, matching the existing pattern on `experimental.cacheComponents`.
## PR checklist (Fixing a bug)
- One-line JSDoc change, no tests needed
Made with [Cursor](https://cursor.com) | b61cdbe9b965b194a24565c939c15239d992bfa1 | [
{
"filename": "packages/next/src/server/config-shared.ts",
"patch": "@@ -939,6 +939,7 @@ export interface ExperimentalConfig {\n authInterrupts?: boolean\n \n /**\n+ * Enables the use of the `\"use cache\"` directive.\n * @deprecated use top-level `cacheComponents` instead\n */\n useCache?: bo... |
nodejs/node | 62,550 | meta: bump step-security/harden-runner from 2.15.0 to 2.16.1 | Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.15.0 to 2.16.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/step-security/harden-runner/releases">step-security/harden-runner's releases</a>.</em></p>
<blockquote>
<h2>v2.16.1</h2>
<h2>What's Changed</h2>
<p>Enterprise tier: Added support for direct IP addresses in the allow list
Community tier: Migrated Harden Runner telemetry to a new endpoint</p>
<p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.16.0...v2.16.1">https://github.com/step-security/harden-runner/compare/v2.16.0...v2.16.1</a></p>
<h2>v2.16.0</h2>
<h2>What's Changed</h2>
<ul>
<li>Updated action.yml to use node24</li>
<li>Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS over HTTPS (DoH) by proxying DNS queries through a permitted resolver, allowing data exfiltration even with a restrictive allowed-endpoints list. This issue only affects the Community Tier; the Enterprise Tier is not affected. See <a href="https://github.com/step-security/harden-runner/security/advisories/GHSA-46g3-37rh-v698">GHSA-46g3-37rh-v698</a> for details.</li>
<li>Security fix: Fixed a medium severity vulnerability where the egress block policy could be bypassed via DNS queries over TCP to external resolvers, allowing outbound network communication that evades configured network restrictions. This issue only affects the Community Tier; the Enterprise Tier is not affected. See <a href="https://github.com/step-security/harden-runner/security/advisories/GHSA-g699-3x6g-wm3g">GHSA-g699-3x6g-wm3g</a> for details.</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.15.1...v2.16.0">https://github.com/step-security/harden-runner/compare/v2.15.1...v2.16.0</a></p>
<h2>v2.15.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Fixes <a href="https://redirect.github.com/step-security/harden-runner/issues/642">step-security/harden-runner#642</a> bug due to which post step was failing on Windows ARM runners</li>
<li>Updates npm packages</li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/step-security/harden-runner/compare/v2.15.0...v2.15.1">https://github.com/step-security/harden-runner/compare/v2.15.0...v2.15.1</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/step-security/harden-runner/commit/fe104658747b27e96e4f7e80cd0a94068e53901d"><code>fe10465</code></a> v2.16.1 (<a href="https://redirect.github.com/step-security/harden-runner/issues/654">#654</a>)</li>
<li><a href="https://github.com/step-security/harden-runner/commit/fa2e9d605c4eeb9fcad4c99c224cee0c6c7f3594"><code>fa2e9d6</code></a> Release v2.16.0 (<a href="https://redirect.github.com/step-security/harden-runner/issues/646">#646</a>)</li>
<li><a href="https://github.com/step-security/harden-runner/commit/58077d3c7e43986b6b15fba718e8ea69e387dfcc"><code>58077d3</code></a> Release v2.15.1 (<a href="https://redirect.github.com/step-security/harden-runner/issues/641">#641</a>)</li>
<li>See full diff in <a href="https://github.com/step-security/harden-runner/compare/a90bcbc6539c36a85cdfeb73f7e2f433735f215b...fe104658747b27e96e4f7e80cd0a94068e53901d">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | 8640c2e7356240ce0ade30e1052168514a466786 | [
{
"filename": ".github/workflows/scorecard.yml",
"patch": "@@ -35,7 +35,7 @@ jobs:\n \n steps:\n - name: Harden Runner\n- uses: step-security/harden-runner@a90bcbc6539c36a85cdfeb73f7e2f433735f215b # v2.15.0\n+ uses: step-security/harden-runner@fe104658747b27e96e4f7e80cd0a94068e53901... |
rust-lang/rust | 154,802 | Rollup of 5 pull requests | Successful merges:
- rust-lang/rust#154376 (Remove more BuiltinLintDiag variants - part 4)
- rust-lang/rust#154731 (llvm: Fix array ABI test to not check equality implementation)
- rust-lang/rust#127534 (feat(core): impl Step for NonZero<u*>)
- rust-lang/rust#154703 (Fix trailing comma in lifetime suggestion for empty angle brackets)
- rust-lang/rust#154776 (Fix ICE in read_discriminant for enums with non-contiguous discriminants)
<!-- homu-ignore:start -->
r? @ghost
[Create a similar rollup](https://bors.rust-lang.org/queue/rust?prs=154376,154731,127534,154703,154776)
<!-- homu-ignore:end -->
| 7f18b253f8d0d3ff468ae16ed7d6f7a4847d6680 | [
{
"filename": "compiler/rustc_const_eval/src/interpret/discriminant.rs",
"patch": "@@ -121,20 +121,20 @@ impl<'tcx, M: Machine<'tcx>> InterpCx<'tcx, M> {\n // discriminants are int-like.\n let discr_val = self.int_to_int_or_float(&tag_val, discr_layout).unwrap();\n ... |
ollama/ollama | 15,255 | model/parsers/gemma4: fix tool call argument parsing with internal quotes | The Gemma 4 parser now correctly handles tool call arguments that contain internal quotes by properly escaping content within <|"|> quotes. This fixes a parsing error when tool calls included shell commands or other quoted strings.
Fixes #15241 | d928879a09f72d9180bf782011bfe693eb3c022a | [
{
"filename": "model/parsers/gemma4.go",
"patch": "@@ -1,6 +1,9 @@\n package parsers\n \n import (\n+\t\"strconv\"\n+\t\"regexp\"\n+\n \t\"encoding/json\"\n \t\"errors\"\n \t\"log/slog\"\n@@ -343,53 +346,27 @@ func parseGemma4ToolCall(content string) (api.ToolCall, error) {\n \t}, nil\n }\n \n+var (\n+\tgem... |
huggingface/transformers | 45,210 | Fix pypi release | # What does this PR do?
Commits that got in the release branch to allow pushing | 43fb8cf00e893ad12abe5fa57b908fe30e2f8994 | [
{
"filename": "setup.py",
"patch": "@@ -292,8 +292,10 @@ def finalize_options(self):\n pass\n \n def run(self):\n- if SUPPORTED_PYTHON_VERSIONS[0] != PYTHON_MINOR_VERSION:\n- print(f\"Table updated only when running 3.{SUPPORTED_PYTHON_VERSIONS[0]}.x\")\n+ if SUPPORTED_P... |
nodejs/node | 62,549 | meta: bump actions/download-artifact from 8.0.0 to 8.0.1 | Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 8.0.0 to 8.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/download-artifact/releases">actions/download-artifact's releases</a>.</em></p>
<blockquote>
<h2>v8.0.1</h2>
<h2>What's Changed</h2>
<ul>
<li>Support for CJK characters in the artifact name by <a href="https://github.com/danwkennedy"><code>@danwkennedy</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/471">actions/download-artifact#471</a></li>
<li>Add a regression test for artifact name + content-type mismatches by <a href="https://github.com/danwkennedy"><code>@danwkennedy</code></a> in <a href="https://redirect.github.com/actions/download-artifact/pull/472">actions/download-artifact#472</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/download-artifact/compare/v8...v8.0.1">https://github.com/actions/download-artifact/compare/v8...v8.0.1</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/download-artifact/commit/3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c"><code>3e5f45b</code></a> Add regression tests for CJK characters (<a href="https://redirect.github.com/actions/download-artifact/issues/471">#471</a>)</li>
<li><a href="https://github.com/actions/download-artifact/commit/e6d03f67377d4412c7aa56a8e2e4988e6ec479dd"><code>e6d03f6</code></a> Add a regression test for artifact name + content-type mismatches (<a href="https://redirect.github.com/actions/download-artifact/issues/472">#472</a>)</li>
<li>See full diff in <a href="https://github.com/actions/download-artifact/compare/70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3...3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | a88fdca7249a9edd737122303af4a7d11786347f | [
{
"filename": ".github/workflows/build-tarball.yml",
"patch": "@@ -127,7 +127,7 @@ jobs:\n - name: Environment Information\n run: npx envinfo\n - name: Download tarball\n- uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # v8.0.0\n+ uses: actions/do... |
rust-lang/rust | 154,798 | rustdoc-search: match path components on words | Since the length of a path is treated as sorting criteria, and every path that contains the query without exactly matching it must be longer, exact matches will always sort first if they exist.
Fixes rust-lang/rust#154733
| f1d240c040e4df7db2504938141e150e2c92a7d9 | [
{
"filename": "src/librustdoc/html/static/js/search.js",
"patch": "@@ -2799,6 +2799,8 @@ class DocSearch {\n result_list.sort((aaa, bbb) => {\n const aai = aaa.item;\n const bbi = bbb.item;\n+ const ap = aai.modulePath !== undefined ... |
vercel/next.js | 92,288 | Update Rust toolchain to nightly-2026-04-02 | ### What?
Bumps the Rust toolchain from \`nightly-2026-02-18\` to \`nightly-2026-04-02\` and cleans up all resulting compiler warnings.
Changes:
- \`rust-toolchain.toml\` and \`.devcontainer/rust/devcontainer-feature.json\` updated to \`nightly-2026-04-02\`
- 22 \`collapsible_match\` clippy violations fixed across \`next-custom-transforms\` (in \`server_actions\`, \`shake_exports\`, \`next_ssg\`, \`font_imports_generator\`, \`react_server_components\`, \`strip_page_exports\`)
- Additional clippy and \`rustfmt\` fixes in \`turbopack-core\`, \`turbopack-ecmascript\`, \`turbopack-resolve\`, \`turbopack-css\`, \`turbopack-dev-server\`, \`next-core\`, and \`next-api\`
- \`#![feature(...)]\` declarations removed for features that are **now stable** on this toolchain: \`iter_intersperse\`, \`future_join\`, \`type_alias_impl_trait\`, \`box_patterns\`, \`try_trait_v2\`, \`never_type\`, \`iter_advance_by\`, \`downcast_unchecked\`, \`int_roundings\`, \`thread_id_value\`, \`map_try_insert\`, \`hash_set_entry\`, \`iter_collect_into\`, \`associated_type_defaults\`, \`trait_alias\`, \`str_split_remainder\`, \`arbitrary_self_types\`
- \`#![feature(arbitrary_self_types_pointers)]\` and some \`#![feature(min_specialization)]\` declarations removed from files where they were **declared but unused** — these features are still nightly-only, but the code in those specific files did not use any syntax gated behind them
### Why?
Routine toolchain bump to stay current with Rust nightly. Keeping the toolchain up to date ensures we benefit from compiler improvements, performance gains, and newly stabilized features (allowing removal of \`#![feature(...)]\` gates).
### How?
- Updated the toolchain pin in \`rust-toolchain.toml\`
- Ran \`cargo clippy\` and \`cargo fmt\` to surface and fix warnings introduced by the new lints
- Removed \`#![feature(...)]\` declarations that are no longer needed because the features have been stabilized, or where the features are still nightly-only but unused in those specific crates | 58d271cbd3e9912da6c4330ccdabc12a757ab354 | [
{
"filename": ".config/eslintignore.mjs",
"patch": "@@ -47,6 +47,7 @@ export default globalIgnores([\n 'examples/with-typescript-graphql/lib/gql/',\n 'test/development/basic/hmr/components/parse-error.js',\n 'test/development/mcp-server/fixtures/default-template/app/build-error/page.tsx',\n+ 'test/de... |
ollama/ollama | 15,254 | model/parsers: fix gemma4 arg parsing when quoted strings contain " | Fixes: #15241 | 73a8e9d62c8cec6a32f363d92cdd43a06a5faf1c | [
{
"filename": "model/parsers/gemma4.go",
"patch": "@@ -389,13 +389,29 @@ func gemma4ArgsToJSON(s string) string {\n \t\t\tcase '\\\\':\n \t\t\t\tif i+1 < len(s) {\n \t\t\t\t\tnext := s[i+1]\n-\t\t\t\t\tswitch next {\n-\t\t\t\t\tcase '\"', '\\\\', '/':\n-\t\t\t\t\t\t// Preserve valid JSON escapes that are al... |
huggingface/transformers | 45,192 | casually dropping the most capable open weights on the planet | ---------
# What does this PR do?
model previously unable to use tools
## Code Agent Policy
The Transformers repo is currently being overwhelmed by a large number of PRs and issue comments written by
code agents. We are currently bottlenecked by our ability to review and respond to them. As a result,
**we ask that new users do not submit pure code agent PRs** at this time.
You may use code agents in drafting or to help you diagnose issues. We'd also ask autonomous "OpenClaw"-like agents
not to open any PRs or issues for the moment.
PRs that appear to be fully agent-written will probably be closed without review, and we may block users who do this
repeatedly or maliciously.
This is a rapidly-evolving situation that's causing significant shockwaves in the open-source community. As a result,
this policy is likely to be updated regularly in the near future. For more information, please read [`CONTRIBUTING.md`](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md).
- [x] I confirm that this is not a pure code agent PR.
## 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?
- [x] 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.
- [x] 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).
- [x] Did you write any new necessary tests?
## Who can review?
@ArthurZucker @Cyrilvallez @eustlb @zucchini-nlp @Rocketknight1
| 3feea4a7fc273e92843002e9e4db85f5afae0689 | [
{
"filename": "tests/models/gemma4/test_modeling_gemma4.py",
"patch": "@@ -419,6 +419,7 @@ def test_generate_from_random_inputs_embeds(self):\n pass\n \n \n+@unittest.skip(\"Integration Tests are not up-to-date yet! TODO Cyril: update me pretty pretty please!\")\n @slow\n @require_torch_accelerator\... |
golang/go | 78,194 | cmd/link: propagate Mach-O section alignment to symbol in loadmacho | The Mach-O object file loader reads the section alignment from the
section header into ldMachoSect.align, but never calls SetAlign on
the symbol builder when converting sections to linker symbols. This
causes all Mach-O .syso sections to fall back to Funcalign (16 bytes
on ARM64) regardless of the alignment declared in the section header.
For .syso files containing C-compiled code with ADRP instructions on
ARM64, the lack of page alignment (4096 bytes) leads to incorrect
PC-relative address computation and runtime crashes.
The ELF loader already correctly propagates section alignment via
sb.SetAlign (ldelf.go:543). Apply the same treatment to the Mach-O
loader. Note that Mach-O stores alignment as log2 (e.g. 12 for 4096),
so we use 1 << sect.align.
Fixes #78192 | 85aa42b59a663335b3ce72f7b60ffa240aadeff8 | [
{
"filename": "src/cmd/link/internal/loadmacho/ldmacho.go",
"patch": "@@ -570,6 +570,9 @@ func Load(l *loader.Loader, arch *sys.Arch, localSymVersion int, f *bio.Reader,\n \t\t\tbld.SetData(dat[sect.addr-c.seg.vmaddr:][:sect.size])\n \t\t}\n \t\tbld.SetSize(int64(len(bld.Data())))\n+\t\tif sect.align != 0 {... |
nodejs/node | 62,548 | meta: bump actions/setup-node from 6.2.0 to 6.3.0 | Bumps [actions/setup-node](https://github.com/actions/setup-node) from 6.2.0 to 6.3.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/setup-node/releases">actions/setup-node's releases</a>.</em></p>
<blockquote>
<h2>v6.3.0</h2>
<h2>What's Changed</h2>
<h3>Enhancements:</h3>
<ul>
<li>Support parsing <code>devEngines</code> field by <a href="https://github.com/susnux"><code>@susnux</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1283">actions/setup-node#1283</a></li>
</ul>
<blockquote>
<p>When using node-version-file: package.json, setup-node now prefers devEngines.runtime over engines.node.</p>
</blockquote>
<h3>Dependency updates:</h3>
<ul>
<li>Fix npm audit issues by <a href="https://github.com/gowridurgad"><code>@gowridurgad</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1491">actions/setup-node#1491</a></li>
<li>Replace uuid with crypto.randomUUID() by <a href="https://github.com/trivikr"><code>@trivikr</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1378">actions/setup-node#1378</a></li>
<li>Upgrade minimatch from 3.1.2 to 3.1.5 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1498">actions/setup-node#1498</a></li>
</ul>
<h3>Bug fixes:</h3>
<ul>
<li>Remove hardcoded bearer for mirror-url <a href="https://github.com/marco-ippolito"><code>@marco-ippolito</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1467">actions/setup-node#1467</a></li>
<li>Scope test lockfiles by package manager and update cache tests by <a href="https://github.com/gowridurgad"><code>@gowridurgad</code></a> in <a href="https://redirect.github.com/actions/setup-node/pull/1495">actions/setup-node#1495</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/susnux"><code>@susnux</code></a> made their first contribution in <a href="https://redirect.github.com/actions/setup-node/pull/1283">actions/setup-node#1283</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/setup-node/compare/v6...v6.3.0">https://github.com/actions/setup-node/compare/v6...v6.3.0</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/setup-node/commit/53b83947a5a98c8d113130e565377fae1a50d02f"><code>53b8394</code></a> Bump minimatch from 3.1.2 to 3.1.5 (<a href="https://redirect.github.com/actions/setup-node/issues/1498">#1498</a>)</li>
<li><a href="https://github.com/actions/setup-node/commit/54045abd5dcd3b0fee9ca02fa24c57545834c9cc"><code>54045ab</code></a> Scope test lockfiles by package manager and update cache tests (<a href="https://redirect.github.com/actions/setup-node/issues/1495">#1495</a>)</li>
<li><a href="https://github.com/actions/setup-node/commit/c882bffdbd4df51ace6b940023952e8669c9932a"><code>c882bff</code></a> Replace uuid with crypto.randomUUID() (<a href="https://redirect.github.com/actions/setup-node/issues/1378">#1378</a>)</li>
<li><a href="https://github.com/actions/setup-node/commit/774c1d62961e73038a114d59c8847023c003194d"><code>774c1d6</code></a> feat(node-version-file): support parsing <code>devEngines</code> field (<a href="https://redirect.github.com/actions/setup-node/issues/1283">#1283</a>)</li>
<li><a href="https://github.com/actions/setup-node/commit/efcb663fc60e97218a2b2d6d827f7830f164739e"><code>efcb663</code></a> fix: remove hardcoded bearer (<a href="https://redirect.github.com/actions/setup-node/issues/1467">#1467</a>)</li>
<li><a href="https://github.com/actions/setup-node/commit/d02c89dce7e1ba9ef629ce0680989b3a1cc72edb"><code>d02c89d</code></a> Fix npm audit issues (<a href="https://redirect.github.com/actions/setup-node/issues/1491">#1491</a>)</li>
<li>See full diff in <a href="https://github.com/actions/setup-node/compare/6044e13b5dc448c55e2357c09f80417699197238...53b83947a5a98c8d113130e565377fae1a50d02f">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | b34d168e7e0bd0c2e592df4e65d55086b71d5cdf | [
{
"filename": ".github/workflows/auto-start-ci.yml",
"patch": "@@ -46,7 +46,7 @@ jobs:\n runs-on: ubuntu-slim\n steps:\n - name: Install Node.js\n- uses: actions/setup-node@6044e13b5dc448c55e2357c09f80417699197238 # v6.2.0\n+ uses: actions/setup-node@53b83947a5a98c8d113130e56537... |
facebook/react | 36,159 | [compiler][playground] parse compiler configs using json5 |
Compiler config parsing is currently done with new Function(...) which is a XSS vulnerability. Replacing this with json parsing for safety reasons.
Almost all compiler options (except for moduleTypeProvider) are json compatible, so this isn't a big change to capabilities. Previously created playground URLs with non-default configs may not be compatible with this change, but we should be able to get the correct config manually (by reading the JS version)
| 91452c1b4b44bb5cf53d5e5ea4754e6c81946bae | [
{
"filename": "compiler/apps/playground/__tests__/e2e/__snapshots__/page.spec.ts/default-config.txt",
"patch": "@@ -1,5 +1,3 @@\n-import type { PluginOptions } from \n-'babel-plugin-react-compiler/dist';\n-({\n+{\n //compilationMode: \"all\"\n-} satisfies PluginOptions);\n\\ No newline at end of file\n+}\... |
vercel/next.js | 92,284 | Turbopack: Remove FileSystemPath::value_to_string in favor of ValueToStringRef::to_string_ref | `FileSystemPath::value_to_string` was just calling `ValueToString::to_string`.
But:
- It's better to call `ValueToStringRef::to_string_ref`
- We don't really get much value from this inherent method except for avoiding a few imports?
I suspect this is left over from when we used to always wrap `FileSystemPath` in `Vc`. | e43c6c2a7f65ac5da7be689aa9a7129e392c8032 | [
{
"filename": "crates/next-core/src/app_structure.rs",
"patch": "@@ -7,8 +7,8 @@ use rustc_hash::FxHashMap;\n use tracing::Instrument;\n use turbo_rcstr::{RcStr, rcstr};\n use turbo_tasks::{\n- FxIndexMap, FxIndexSet, NonLocalValue, ResolvedVc, TaskInput, TryJoinIterExt, ValueDefault, Vc,\n- debug::Va... |
rust-lang/rust | 154,797 | bootstrap: Include shorthand aliases in x completions | Previously, `x d --<tab>` wouldn't show any options.
<!-- homu-ignore:start -->
<!--
If this PR is related to an unstable feature or an otherwise tracked effort,
please link to the relevant tracking issue here. If you don't know of a related
tracking issue or there are none, feel free to ignore this.
This PR will get automatically assigned to a reviewer. In case you would like
a specific user to review your work, you can assign it to them by using
r? <reviewer name>
-->
<!-- homu-ignore:end -->
| 91e4524d9a8807b4962191138b23861cc028f550 | [
{
"filename": "src/bootstrap/src/core/config/flags.rs",
"patch": "@@ -243,7 +243,7 @@ fn normalize_args(args: &[String]) -> Vec<String> {\n \n #[derive(Debug, Clone, clap::Subcommand)]\n pub enum Subcommand {\n- #[command(aliases = [\"b\"], long_about = \"\\n\n+ #[command(visible_aliases = [\"b\"], lo... |
ollama/ollama | 15,232 | tokenizer: add byte fallback for SentencePiece BPE encoding | When BPE merging produces tokens not in the vocabulary, fall back to encoding each UTF-8 byte as <0xHH> byte tokens instead of silently dropping the character. Also teach Decode to convert <0xHH> tokens back to raw bytes.
Fixes #15229, fixes #15231 | 0d569d2a399c2098ca5137a2831916cf90746ede | [
{
"filename": "model/models/gemma4/tokenizer_reference_test.go",
"patch": "@@ -0,0 +1,341 @@\n+package gemma4\n+\n+// TestGemma4TokenizerMatchesReference verifies our BPE tokenizer matches\n+// the Rust tokenizers library (the reference implementation) for Gemma 4.\n+//\n+// The test loads vocabulary from a... |
huggingface/transformers | 45,188 | fix `test_register_result_handler` | # What does this PR do ?
This PR fixes the `test_register_result_handler`. Not sure how it passed in the past when i added it but since CB returns `generated_tokens` from the same list to avoid copy, len(results[i].generated_tokens) for i =0,1,2 will always be the same after the got all the results. I reworked a bit the test to properly test. | 5dc08d4f8f33f6efb9097cf5374b6a6afedd1df7 | [
{
"filename": "tests/generation/test_continuous_batching.py",
"patch": "@@ -847,27 +847,24 @@ def test_register_result_handler(self) -> None:\n inputs = get_generation_inputs(user_messages, tokenizer, for_continuous_batching=True)[0]\n \n async def collect_results():\n- results = ... |
electron/electron | 50,686 | fix: propagate requesting frame through sync permission checks | Backport of #50679
See that PR for details.
Notes: no-notes | b68b8bbed2123b154a4547abd63538859725e5ab | [
{
"filename": "shell/browser/api/electron_api_web_contents.cc",
"patch": "@@ -1767,7 +1767,8 @@ bool WebContents::CheckMediaAccessPermission(\n content::WebContents::FromRenderFrameHost(render_frame_host);\n auto* permission_helper =\n WebContentsPermissionHelper::FromWebContents(web_contents)... |
golang/go | 78,190 | doc: fix typo | This PR will be imported into Gerrit with the title and first
comment (this text) used to generate the subject and body of
the Gerrit change.
**Please ensure you adhere to every item in this list.**
More info can be found at https://github.com/golang/go/wiki/CommitMessage
+ The PR title is formatted as follows: `net/http: frob the quux before blarfing`
+ The package name goes before the colon
+ The part after the colon uses the verb tense + phrase that completes the blank in,
"This change modifies Go to ___________"
+ Lowercase verb after the colon
+ No trailing period
+ Keep the title as short as possible. ideally under 76 characters or shorter
+ No Markdown
+ The first PR comment (this one) is wrapped at 76 characters, unless it's
really needed (ASCII art, table, or long link)
+ If there is a corresponding issue, add either `Fixes #1234` or `Updates #1234`
(the latter if this is not a complete fix) to this comment
+ If referring to a repo other than `golang/go` you can use the
`owner/repo#issue_number` syntax: `Fixes golang/tools#1234`
+ We do not use Signed-off-by lines in Go. Please don't add them.
Our Gerrit server & GitHub bots enforce CLA compliance instead.
+ Delete these instructions once you have read and applied them
| 7fc836e0700aaebc77a536dcc7e1f1095fa636b4 | [
{
"filename": "doc/godebug.md",
"patch": "@@ -248,7 +248,7 @@ and so removed the [`runtimecontentionstacks` setting](/pkg/runtime#hdr-Environm\n Go 1.25 (starting with Go 1.25 RC 2) disabled build information stamping when\n multiple VCS are detected due to concerns around VCS injection attacks. This\n beha... |
nodejs/node | 62,547 | meta: bump github/codeql-action from 4.32.4 to 4.35.1 | Bumps [github/codeql-action](https://github.com/github/codeql-action) from 4.32.4 to 4.35.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/releases">github/codeql-action's releases</a>.</em></p>
<blockquote>
<h2>v4.35.1</h2>
<ul>
<li>Fix incorrect minimum required Git version for <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a>: it should have been 2.36.0, not 2.11.0. <a href="https://redirect.github.com/github/codeql-action/pull/3781">#3781</a></li>
</ul>
<h2>v4.35.0</h2>
<ul>
<li>Reduced the minimum Git version required for <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> from 2.38.0 to 2.11.0. <a href="https://redirect.github.com/github/codeql-action/pull/3767">#3767</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.25.1">2.25.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3773">#3773</a></li>
</ul>
<h2>v4.34.1</h2>
<ul>
<li>Downgrade default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3">2.24.3</a> due to issues with a small percentage of Actions and JavaScript analyses. <a href="https://redirect.github.com/github/codeql-action/pull/3762">#3762</a></li>
</ul>
<h2>v4.34.0</h2>
<ul>
<li>Added an experimental change which disables TRAP caching when <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3569">#3569</a></li>
<li>We are rolling out improved incremental analysis to C/C++ analyses that use build mode <code>none</code>. We expect this rollout to be complete by the end of April 2026. <a href="https://redirect.github.com/github/codeql-action/pull/3584">#3584</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.25.0">2.25.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3585">#3585</a></li>
</ul>
<h2>v4.33.0</h2>
<ul>
<li>
<p>Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. <a href="https://redirect.github.com/github/codeql-action/pull/3562">#3562</a></p>
<p>To opt out of this change:</p>
<ul>
<li><strong>Repositories owned by an organization:</strong> Create a custom repository property with the name <code>github-codeql-file-coverage-on-prs</code> and the type "True/false", then set this property to <code>true</code> in the repository's settings. For more information, see <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">Managing custom properties for repositories in your organization</a>. Alternatively, if you are using an advanced setup workflow, you can set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
<li><strong>User-owned repositories using default setup:</strong> Switch to an advanced setup workflow and set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
<li><strong>User-owned repositories using advanced setup:</strong> Set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
</ul>
</li>
<li>
<p>Fixed <a href="https://redirect.github.com/github/codeql-action/issues/3555">a bug</a> which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. <a href="https://redirect.github.com/github/codeql-action/pull/3557">#3557</a></p>
</li>
<li>
<p>The CodeQL Action now loads <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">custom repository properties</a> on GitHub Enterprise Server, enabling the customization of features such as <code>github-codeql-disable-overlay</code> that was previously only available on GitHub.com. <a href="https://redirect.github.com/github/codeql-action/pull/3559">#3559</a></p>
</li>
<li>
<p>Once <a href="https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries">private package registries</a> can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. <a href="https://redirect.github.com/github/codeql-action/pull/3563">#3563</a></p>
</li>
<li>
<p>Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". <a href="https://redirect.github.com/github/codeql-action/pull/3564">#3564</a></p>
</li>
<li>
<p>A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/3570">#3570</a></p>
</li>
</ul>
<h2>v4.32.6</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3">2.24.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3548">#3548</a></li>
</ul>
<h2>v4.32.5</h2>
<ul>
<li>Repositories owned by an organization can now set up the <code>github-codeql-disable-overlay</code> custom repository property to disable <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis for CodeQL</a>. First, create a custom repository property with the name <code>github-codeql-disable-overlay</code> and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to <code>true</code> to disable improved incremental analysis. For more information, see <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">Managing custom properties for repositories in your organization</a>. This feature is not yet available on GitHub Enterprise Server. <a href="https://redirect.github.com/github/codeql-action/pull/3507">#3507</a></li>
<li>Added an experimental change so that when <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3487">#3487</a></li>
<li>The minimum memory check for improved incremental analysis is now skipped for CodeQL 2.24.3 and later, which has reduced peak RAM usage. <a href="https://redirect.github.com/github/codeql-action/pull/3515">#3515</a></li>
<li>Reduced log levels for best-effort private package registry connection check failures to reduce noise from workflow annotations. <a href="https://redirect.github.com/github/codeql-action/pull/3516">#3516</a></li>
<li>Added an experimental change which lowers the minimum disk space requirement for <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a>, enabling it to run on standard GitHub Actions runners. We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3498">#3498</a></li>
<li>Added an experimental change which allows the <code>start-proxy</code> action to resolve the CodeQL CLI version from feature flags instead of using the linked CLI bundle version. We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3512">#3512</a></li>
<li>The previously experimental changes from versions 4.32.3, 4.32.4, 3.32.3 and 3.32.4 are now enabled by default. <a href="https://redirect.github.com/github/codeql-action/pull/3503">#3503</a>, <a href="https://redirect.github.com/github/codeql-action/pull/3504">#3504</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/github/codeql-action/blob/main/CHANGELOG.md">github/codeql-action's changelog</a>.</em></p>
<blockquote>
<h1>CodeQL Action Changelog</h1>
<p>See the <a href="https://github.com/github/codeql-action/releases">releases page</a> for the relevant changes to the CodeQL CLI and language packs.</p>
<h2>[UNRELEASED]</h2>
<ul>
<li>The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. <a href="https://redirect.github.com/github/codeql-action/pull/3789">#3789</a></li>
<li>Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. <a href="https://redirect.github.com/github/codeql-action/pull/3794">#3794</a></li>
</ul>
<h2>4.35.1 - 27 Mar 2026</h2>
<ul>
<li>Fix incorrect minimum required Git version for <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a>: it should have been 2.36.0, not 2.11.0. <a href="https://redirect.github.com/github/codeql-action/pull/3781">#3781</a></li>
</ul>
<h2>4.35.0 - 27 Mar 2026</h2>
<ul>
<li>Reduced the minimum Git version required for <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> from 2.38.0 to 2.11.0. <a href="https://redirect.github.com/github/codeql-action/pull/3767">#3767</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.25.1">2.25.1</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3773">#3773</a></li>
</ul>
<h2>4.34.1 - 20 Mar 2026</h2>
<ul>
<li>Downgrade default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3">2.24.3</a> due to issues with a small percentage of Actions and JavaScript analyses. <a href="https://redirect.github.com/github/codeql-action/pull/3762">#3762</a></li>
</ul>
<h2>4.34.0 - 20 Mar 2026</h2>
<ul>
<li>Added an experimental change which disables TRAP caching when <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3569">#3569</a></li>
<li>We are rolling out improved incremental analysis to C/C++ analyses that use build mode <code>none</code>. We expect this rollout to be complete by the end of April 2026. <a href="https://redirect.github.com/github/codeql-action/pull/3584">#3584</a></li>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.25.0">2.25.0</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3585">#3585</a></li>
</ul>
<h2>4.33.0 - 16 Mar 2026</h2>
<ul>
<li>
<p>Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. <a href="https://redirect.github.com/github/codeql-action/pull/3562">#3562</a></p>
<p>To opt out of this change:</p>
<ul>
<li><strong>Repositories owned by an organization:</strong> Create a custom repository property with the name <code>github-codeql-file-coverage-on-prs</code> and the type "True/false", then set this property to <code>true</code> in the repository's settings. For more information, see <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">Managing custom properties for repositories in your organization</a>. Alternatively, if you are using an advanced setup workflow, you can set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
<li><strong>User-owned repositories using default setup:</strong> Switch to an advanced setup workflow and set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
<li><strong>User-owned repositories using advanced setup:</strong> Set the <code>CODEQL_ACTION_FILE_COVERAGE_ON_PRS</code> environment variable to <code>true</code> in your workflow.</li>
</ul>
</li>
<li>
<p>Fixed <a href="https://redirect.github.com/github/codeql-action/issues/3555">a bug</a> which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. <a href="https://redirect.github.com/github/codeql-action/pull/3557">#3557</a></p>
</li>
<li>
<p>The CodeQL Action now loads <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">custom repository properties</a> on GitHub Enterprise Server, enabling the customization of features such as <code>github-codeql-disable-overlay</code> that was previously only available on GitHub.com. <a href="https://redirect.github.com/github/codeql-action/pull/3559">#3559</a></p>
</li>
<li>
<p>Once <a href="https://docs.github.com/en/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries">private package registries</a> can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. <a href="https://redirect.github.com/github/codeql-action/pull/3563">#3563</a></p>
</li>
<li>
<p>Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". <a href="https://redirect.github.com/github/codeql-action/pull/3564">#3564</a></p>
</li>
<li>
<p>A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. <a href="https://redirect.github.com/github/codeql-action/pull/3570">#3570</a></p>
</li>
</ul>
<h2>4.32.6 - 05 Mar 2026</h2>
<ul>
<li>Update default CodeQL bundle version to <a href="https://github.com/github/codeql-action/releases/tag/codeql-bundle-v2.24.3">2.24.3</a>. <a href="https://redirect.github.com/github/codeql-action/pull/3548">#3548</a></li>
</ul>
<h2>4.32.5 - 02 Mar 2026</h2>
<ul>
<li>Repositories owned by an organization can now set up the <code>github-codeql-disable-overlay</code> custom repository property to disable <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis for CodeQL</a>. First, create a custom repository property with the name <code>github-codeql-disable-overlay</code> and the type "True/false" in the organization's settings. Then in the repository's settings, set this property to <code>true</code> to disable improved incremental analysis. For more information, see <a href="https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization">Managing custom properties for repositories in your organization</a>. This feature is not yet available on GitHub Enterprise Server. <a href="https://redirect.github.com/github/codeql-action/pull/3507">#3507</a></li>
<li>Added an experimental change so that when <a href="https://redirect.github.com/github/roadmap/issues/1158">improved incremental analysis</a> fails on a runner — potentially due to insufficient disk space — the failure is recorded in the Actions cache so that subsequent runs will automatically skip improved incremental analysis until something changes (e.g. a larger runner is provisioned or a new CodeQL version is released). We expect to roll this change out to everyone in March. <a href="https://redirect.github.com/github/codeql-action/pull/3487">#3487</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/github/codeql-action/commit/c10b8064de6f491fea524254123dbe5e09572f13"><code>c10b806</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/3782">#3782</a> from github/update-v4.35.1-d6d1743b8</li>
<li><a href="https://github.com/github/codeql-action/commit/c5ffd0683786820677d054e3505e1c5bb4b8c227"><code>c5ffd06</code></a> Update changelog for v4.35.1</li>
<li><a href="https://github.com/github/codeql-action/commit/d6d1743b8ec7ecd94f78ad1ce4cb3d8d2ba58001"><code>d6d1743</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/3781">#3781</a> from github/henrymercer/update-git-minimum-version</li>
<li><a href="https://github.com/github/codeql-action/commit/65d2efa7333ad65f97cc54be40f4cd18630f884c"><code>65d2efa</code></a> Add changelog note</li>
<li><a href="https://github.com/github/codeql-action/commit/2437b20ab31021229573a66717323dd5c6ce9319"><code>2437b20</code></a> Update minimum git version for overlay to 2.36.0</li>
<li><a href="https://github.com/github/codeql-action/commit/ea5f71947c021286c99f61cc426a10d715fe4434"><code>ea5f719</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/3775">#3775</a> from github/dependabot/npm_and_yarn/node-forge-1.4.0</li>
<li><a href="https://github.com/github/codeql-action/commit/45ceeea896ba2293e10982f871198d1950ee13d6"><code>45ceeea</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/3777">#3777</a> from github/mergeback/v4.35.0-to-main-b8bb9f28</li>
<li><a href="https://github.com/github/codeql-action/commit/24448c98434f429f901d27db7ddae55eec5cc1c4"><code>24448c9</code></a> Rebuild</li>
<li><a href="https://github.com/github/codeql-action/commit/7c510606312e5c68ac8b27c009e5254f226f5dfa"><code>7c51060</code></a> Update changelog and version after v4.35.0</li>
<li><a href="https://github.com/github/codeql-action/commit/b8bb9f28b8d3f992092362369c57161b755dea45"><code>b8bb9f2</code></a> Merge pull request <a href="https://redirect.github.com/github/codeql-action/issues/3776">#3776</a> from github/update-v4.35.0-0078ad667</li>
<li>Additional commits viewable in <a href="https://github.com/github/codeql-action/compare/89a39a4e59826350b863aa6b6252a07ad50cf83e...c10b8064de6f491fea524254123dbe5e09572f13">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | 3844d3d5af696a3cd9755c08a28d2776460a46d1 | [
{
"filename": ".github/workflows/codeql.yml",
"patch": "@@ -27,15 +27,15 @@ jobs:\n \n # Initializes the CodeQL tools for scanning.\n - name: Initialize CodeQL\n- uses: github/codeql-action/init@89a39a4e59826350b863aa6b6252a07ad50cf83e # v4.32.4\n+ uses: github/codeql-action/init@... |
ollama/ollama | 15,221 | convert: support new Gemma4 audio_tower tensor naming | null | c97eacf49b9220cb3545923d83c0c31901f68aa5 | [
{
"filename": "convert/convert_gemma4.go",
"patch": "@@ -450,21 +450,31 @@ func (p *gemma4Model) Replacements() []string {\n \t\t\"model.audio_tower.subsample_conv_projection.conv_0.norm\", \"a.conv1d.0.norm\",\n \t\t\"model.audio_tower.subsample_conv_projection.conv_1.conv\", \"a.conv1d.1\",\n \t\t\"model.... |
vercel/next.js | 92,282 | Ensure app-page reports stale ISR revalidation errors via onRequestError | Note: the change is mostly whitespace. Recommend reviewing w/o whitespace [here](https://github.com/vercel/next.js/pull/92282/changes?w=1).
For App Router pages using time-based ISR, a stale cached response can be returned before background revalidation finishes. If that background revalidation later throws, the error does not bubble back through the normal top-level `app-page` request catch. Instead, the response cache has already resolved the request and later logs the failure internally.
When an error happens while rendering an app router page, and the entry is stale, we now explicitly await `routeModule.onRequestError(...)` before rethrowing.
This copies similar handling in pages router: https://github.com/vercel/next.js/blob/daca04d09bf9aaee9e1c63324166985b643e9844/packages/next/src/server/route-modules/pages/pages-handler.ts#L438-L460
and route handlers:
https://github.com/vercel/next.js/blob/daca04d09bf9aaee9e1c63324166985b643e9844/packages/next/src/build/templates/app-route.ts#L407-L409
| 30ea1254bbc8c62fac5045b7e13dbdd740f4cb2f | [
{
"filename": "packages/next/src/build/templates/app-page.ts",
"patch": "@@ -995,214 +995,317 @@ export async function handler(\n const isProduction = routeModule.isDev === false\n const didRespond = hasResolved || res.writableEnded\n \n- // skip on-demand revalidate if cache is not present... |
facebook/react | 36,157 | Update scheduler.production.min.js | <!--
Thanks for submitting a pull request!
We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.
Before submitting a pull request, please make sure the following is done:
1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
2. Run `yarn` in the repository root.
3. If you've fixed a bug or added code that should be tested, add tests!
4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
10. If you haven't already, complete the CLA.
Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->
## Summary
Added a try-catch block in the unstable_runWithPriority function in packages/scheduler/npm/umd/scheduler.production.min.js to catch the error - "Should not already be working" in Firefox after a breakpoint/alert #17355 and log a warning instead of throwing the error.
<!--
Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->
## How did you test this change?
Added a test case in packages/react-dom/src/__tests__/ReactComponentLifeCycle-test.js to verify that the error no longer occurs when setState is called in componentDidMount and a breakpoint is set in Firefox.
### Add This Code On Line No - 1574 in packages/react-dom/src/__tests__/ReactComponentLifeCycle-test.js
### Code :
it ('should not throw error "Should not already be working" in Firefox after a breakpoint/alert',
async () => {
class TestComponent extends React.Component {
state = { hasLaunched: false };
componentDidMount() {
this.setState({ hasLaunched: true });
}
render() {
return <div>{this.state.hasLaunched ? 'Launched' : 'Not Launched'}</div>;
}
}
const container = document.createElement('div');
const root = ReactDOMClient.createRoot(container);
await act(() => {
root.render(<TestComponent />);
});
expect(container.textContent).toBe('Launched');
});
<!--
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
How exactly did you verify that your PR solves the issue you wanted to solve?
If you leave this empty, your PR will very likely be closed.
-->
| 88abd73df06d48d83561059f6cb34f372f47d0de | [
{
"filename": ".eslintrc.js",
"patch": "@@ -566,6 +566,7 @@ module.exports = {\n CallSite: 'readonly',\n ConsoleTask: 'readonly', // TOOD: Figure out what the official name of this will be.\n ReturnType: 'readonly',\n+ AggregateError: 'readonly',\n AnimationFrameID: 'readonly',\n Weak... |
rust-lang/rust | 154,793 | Rollup of 10 pull requests | Successful merges:
- rust-lang/rust#154376 (Remove more BuiltinLintDiag variants - part 4)
- rust-lang/rust#127534 (feat(core): impl Step for NonZero<u*>)
- rust-lang/rust#153286 (various fixes for scalable vectors)
- rust-lang/rust#153592 (Add `min_adt_const_params` gate)
- rust-lang/rust#154675 (Improve shadowed private field diagnostics)
- rust-lang/rust#154703 (Fix trailing comma in lifetime suggestion for empty angle brackets)
- rust-lang/rust#154653 (Remove rustc_on_unimplemented's append_const_msg)
- rust-lang/rust#154743 (Remove an unused `StableHash` impl.)
- rust-lang/rust#154752 (Add comment to borrow-checker)
- rust-lang/rust#154764 (Add tests for three ICEs that have already been fixed)
<!-- homu-ignore:start -->
r? @ghost
[Create a similar rollup](https://bors.rust-lang.org/queue/rust?prs=154376,127534,153286,153592,154675,154703,154653,154743,154752,154764)
<!-- homu-ignore:end -->
| 7433eb6a1615fbec88b6f1fbbae350b0201e9b18 | [
{
"filename": "compiler/rustc_hir_typeck/src/method/suggest.rs",
"patch": "@@ -1214,6 +1214,13 @@ impl<'a, 'tcx> FnCtxt<'a, 'tcx> {\n unsatisfied_predicates,\n )\n };\n+ if let SelfSource::MethodCall(rcvr_expr) = source {\n+ self.err_ctxt().note_field_sh... |
huggingface/transformers | 45,185 | Generalize gemma vision mask to videos | # What does this PR do?
If we have videos, the token type ids will be `2` but the current fn checks only image token types. This PR generalizes it rely only on `vision_group_ids` instead of token types | 8d7904d68f0f90f0e6c687c3727a47f89006dde2 | [
{
"filename": "src/transformers/models/gemma3/modeling_gemma3.py",
"patch": "@@ -704,26 +704,26 @@ def forward(self, vision_outputs: torch.Tensor):\n return projected_vision_outputs.type_as(vision_outputs)\n \n \n-def token_type_ids_mask_function(vision_group_ids: torch.Tensor) -> Callable:\n+def to... |
golang/go | 78,109 | sync: modernize examples using newer ranged for loops | The examples in sync package currently use the traditional
for loop pattern.
These examples are modernized using the ranged for loops. | 4836c1604264900c82296a8576a46f11900937cb | [
{
"filename": "src/sync/example_test.go",
"patch": "@@ -66,13 +66,13 @@ func ExampleOnce() {\n \t\tfmt.Println(\"Only once\")\n \t}\n \tdone := make(chan bool)\n-\tfor i := 0; i < 10; i++ {\n+\tfor range 10 {\n \t\tgo func() {\n \t\t\tonce.Do(onceBody)\n \t\t\tdone <- true\n \t\t}()\n \t}\n-\tfor i := 0; i ... |
electron/electron | 50,679 | fix: propagate requesting frame through sync permission checks | ## Description of Change
`WebContentsPermissionHelper::CheckPermission` hardcoded `GetPrimaryMainFrame()` and used `web_contents_->GetLastCommittedURL()`, so the two synchronous checks routed through it — Web Serial and camera/microphone — always delivered the main frame's origin to `setPermissionCheckHandler`, along with wrong `details.isMainFrame` / `details.requestingUrl`, even when a cross-origin subframe triggered the check.
Thread the requesting `RenderFrameHost` through `CheckPermission` and its two callers so the permission manager receives the real frame. Other paths (HID/USB/FSA, `Permissions.query()`) already pass the iframe frame directly and are untouched.
## Checklist
- [x] PR description included and stakeholders cc'd
- [x] \`npm test\` passes
- [x] Relevant documentation changed
- [x] PR title follows semantic [commit guidelines](https://github.com/electron/electron/blob/main/docs/development/pull-requests.md#commit-message-guidelines)
- [x] PR release notes describe the change in a way relevant to app developers
## Release Notes
Notes: no-notes | d9a7e41c4adb5f4a389977a5a807350be79f8851 | [
{
"filename": "shell/browser/api/electron_api_web_contents.cc",
"patch": "@@ -1767,7 +1767,8 @@ bool WebContents::CheckMediaAccessPermission(\n content::WebContents::FromRenderFrameHost(render_frame_host);\n auto* permission_helper =\n WebContentsPermissionHelper::FromWebContents(web_contents)... |
nodejs/node | 62,545 | meta: bump codecov/codecov-action from 5.5.2 to 6.0.0 | Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 5.5.2 to 6.0.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/codecov/codecov-action/releases">codecov/codecov-action's releases</a>.</em></p>
<blockquote>
<h2>v6.0.0</h2>
<h2>⚠️ This version introduces support for node24 which make cause breaking changes for systems that do not currently support node24. ⚠️</h2>
<h2>What's Changed</h2>
<ul>
<li>Revert "Revert "build(deps): bump actions/github-script from 7.0.1 to 8.0.0"" by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1929">codecov/codecov-action#1929</a></li>
<li>Th/6.0.0 by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1928">codecov/codecov-action#1928</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.5.4...v6.0.0">https://github.com/codecov/codecov-action/compare/v5.5.4...v6.0.0</a></p>
<h2>v5.5.4</h2>
<p>This is a mirror of <code>v5.5.2</code>. <code>v6</code> will be released which requires <code>node24</code></p>
<h2>What's Changed</h2>
<ul>
<li>Revert "build(deps): bump actions/github-script from 7.0.1 to 8.0.0" by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1926">codecov/codecov-action#1926</a></li>
<li>chore(release): 5.5.4 by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1927">codecov/codecov-action#1927</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.5.3...v5.5.4">https://github.com/codecov/codecov-action/compare/v5.5.3...v5.5.4</a></p>
<h2>v5.5.3</h2>
<h2>What's Changed</h2>
<ul>
<li>build(deps): bump actions/github-script from 7.0.1 to 8.0.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/codecov/codecov-action/pull/1874">codecov/codecov-action#1874</a></li>
<li>chore(release): bump to 5.5.3 by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1922">codecov/codecov-action#1922</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.5.2...v5.5.3">https://github.com/codecov/codecov-action/compare/v5.5.2...v5.5.3</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md">codecov/codecov-action's changelog</a>.</em></p>
<blockquote>
<h2>v5.5.2</h2>
<h3>What's Changed</h3>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2">https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2</a></p>
<h2>v5.5.1</h2>
<h3>What's Changed</h3>
<ul>
<li>fix: overwrite pr number on fork by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1871">codecov/codecov-action#1871</a></li>
<li>build(deps): bump actions/checkout from 4.2.2 to 5.0.0 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1868">codecov/codecov-action#1868</a></li>
<li>build(deps): bump github/codeql-action from 3.29.9 to 3.29.11 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1867">codecov/codecov-action#1867</a></li>
<li>fix: update to use local app/ dir by <a href="https://github.com/thomasrockhu-codecov"><code>@thomasrockhu-codecov</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1872">codecov/codecov-action#1872</a></li>
<li>docs: fix typo in README by <a href="https://github.com/datalater"><code>@datalater</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1866">codecov/codecov-action#1866</a></li>
<li>Document a <code>codecov-cli</code> version reference example by <a href="https://github.com/webknjaz"><code>@webknjaz</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1774">codecov/codecov-action#1774</a></li>
<li>build(deps): bump github/codeql-action from 3.28.18 to 3.29.9 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1861">codecov/codecov-action#1861</a></li>
<li>build(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1833">codecov/codecov-action#1833</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1">https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1</a></p>
<h2>v5.5.0</h2>
<h3>What's Changed</h3>
<ul>
<li>feat: upgrade wrapper to 0.2.4 by <a href="https://github.com/jviall"><code>@jviall</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1864">codecov/codecov-action#1864</a></li>
<li>Pin actions/github-script by Git SHA by <a href="https://github.com/martincostello"><code>@martincostello</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1859">codecov/codecov-action#1859</a></li>
<li>fix: check reqs exist by <a href="https://github.com/joseph-sentry"><code>@joseph-sentry</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1835">codecov/codecov-action#1835</a></li>
<li>fix: Typo in README by <a href="https://github.com/spalmurray"><code>@spalmurray</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1838">codecov/codecov-action#1838</a></li>
<li>docs: Refine OIDC docs by <a href="https://github.com/spalmurray"><code>@spalmurray</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1837">codecov/codecov-action#1837</a></li>
<li>build(deps): bump github/codeql-action from 3.28.17 to 3.28.18 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1829">codecov/codecov-action#1829</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0">https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0</a></p>
<h2>v5.4.3</h2>
<h3>What's Changed</h3>
<ul>
<li>build(deps): bump github/codeql-action from 3.28.13 to 3.28.17 by <code>@app/dependabot</code> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1822">codecov/codecov-action#1822</a></li>
<li>fix: OIDC on forks by <a href="https://github.com/joseph-sentry"><code>@joseph-sentry</code></a> in <a href="https://redirect.github.com/codecov/codecov-action/pull/1823">codecov/codecov-action#1823</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/codecov/codecov-action/compare/v5.4.2..v5.4.3">https://github.com/codecov/codecov-action/compare/v5.4.2..v5.4.3</a></p>
<h2>v5.4.2</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/codecov/codecov-action/commit/57e3a136b779b570ffcdbf80b3bdc90e7fab3de2"><code>57e3a13</code></a> Th/6.0.0 (<a href="https://redirect.github.com/codecov/codecov-action/issues/1928">#1928</a>)</li>
<li><a href="https://github.com/codecov/codecov-action/commit/f67d33dda8a42b51c42a8318a1f66468119e898b"><code>f67d33d</code></a> Revert "Revert "build(deps): bump actions/github-script from 7.0.1 to 8.0.0""...</li>
<li><a href="https://github.com/codecov/codecov-action/commit/75cd11691c0faa626561e295848008c8a7dddffe"><code>75cd116</code></a> chore(release): 5.5.4 (<a href="https://redirect.github.com/codecov/codecov-action/issues/1927">#1927</a>)</li>
<li><a href="https://github.com/codecov/codecov-action/commit/87d39f4a2cec2673cf9505764fb20a38792ea722"><code>87d39f4</code></a> Revert "build(deps): bump actions/github-script from 7.0.1 to 8.0.0" (<a href="https://redirect.github.com/codecov/codecov-action/issues/1926">#1926</a>)</li>
<li><a href="https://github.com/codecov/codecov-action/commit/1af58845a975a7985b0beb0cbe6fbbb71a41dbad"><code>1af5884</code></a> chore(release): bump to 5.5.3 (<a href="https://redirect.github.com/codecov/codecov-action/issues/1922">#1922</a>)</li>
<li><a href="https://github.com/codecov/codecov-action/commit/c143300dea6c9a730986ff862c5bf4d458927ef8"><code>c143300</code></a> build(deps): bump actions/github-script from 7.0.1 to 8.0.0 (<a href="https://redirect.github.com/codecov/codecov-action/issues/1874">#1874</a>)</li>
<li>See full diff in <a href="https://github.com/codecov/codecov-action/compare/671740ac38dd9b0130fbe1cec585b89eea48d3de...57e3a136b779b570ffcdbf80b3bdc90e7fab3de2">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | 2515025fbb0b0a7afe9a17e89a5df759f2a90e88 | [
{
"filename": ".github/workflows/coverage-linux-without-intl.yml",
"patch": "@@ -87,6 +87,6 @@ jobs:\n - name: Clean tmp\n run: rm -rf coverage/tmp && rm -rf out\n - name: Upload\n- uses: codecov/codecov-action@671740ac38dd9b0130fbe1cec585b89eea48d3de # v5.5.2\n+ uses: cod... |
facebook/react | 36,156 | [Flight] Transport `AggregateErrors.errors` |
## Summary
Adds support to transporting `AggregateError.errors` (dev only).
## How did you test this change?
- [x] `yarn test ReactFlight-test`
| 9cd92e4373c3b345e35f516fe04c72e1929c5253 | [
{
"filename": "packages/react-client/src/ReactFlightClient.js",
"patch": "@@ -3537,18 +3537,40 @@ function resolveErrorDev(\n ),\n }\n : undefined;\n+ const isAggregateError =\n+ typeof AggregateError !== 'undefined' && 'errors' in errorInfo;\n+ const revivedErrors =\n+ // We... |
ollama/ollama | 15,214 | Add support for gemma4 | null | d356a27be9ba8b0b57cd6c22bfa4bce7bfd8cb8f | [
{
"filename": "cmd/audio.go",
"patch": "@@ -1,216 +0,0 @@\n-package cmd\n-\n-import (\n-\t\"encoding/binary\"\n-\t\"sync\"\n-\t\"time\"\n-)\n-\n-const (\n-\taudioSampleRate = 16000\n-\taudioChannels = 1\n-\taudioFrameSize = 1024 // samples per callback\n-)\n-\n-// AudioRecorder captures audio from the de... |
rust-lang/rust | 154,791 | Add regression test for #119316 (closure in const generic default ICE) | ## Summary
Adds a regression test for rust-lang/rust#119316.
Using a closure as a const generic default with `generic_const_exprs` used to ICE with "expected type of closure to be a closure". The compiler now correctly reports `E0308` (mismatched types: expected `usize`, found closure) and even suggests calling the closure.
## Test
`tests/ui/const-generics/generic_const_exprs/ice-closure-const-default-119316.rs`
Closes rust-lang/rust#119316 | 1a3daa646077b3f5bb80ec7afbf3ce84452e1d6e | [
{
"filename": "tests/ui/const-generics/generic_const_exprs/ice-closure-const-default-119316.rs",
"patch": "@@ -0,0 +1,12 @@\n+// Regression test for #119316\n+// This used to ICE with \"expected type of closure to be a closure\"\n+// when using a closure as a const generic default with generic_const_exprs.\... |
vercel/next.js | 92,272 | feat: add experimental.swcEnvOptions for SWC preset-env configuration | ### What?
Add `experimental.swcEnvOptions` to expose SWC's preset-env `env` configuration options — including `mode`, `coreJs`, `include`, `exclude`, `skip`, `shippedProposals`, `forceAllTransforms`, `debug`, and `loose`.
### Why?
Currently Next.js only passes `env.targets` (derived from browserslist) to SWC for **syntax downleveling**, but does not expose the polyfill injection capabilities that SWC already supports. This means:
- Users who need automatic core-js polyfills (e.g. `Array.prototype.at()`, `Promise.withResolvers()`, `Set` methods) have no built-in way to get them.
- The only workarounds are importing `core-js` globally (which bloats bundles significantly) or ejecting to Babel with `useBuiltIns: 'usage'` (which sacrifices SWC's performance benefits).
- In the Babel era, Next.js supported this via `@babel/preset-env`'s `useBuiltIns` (PR #10574). That capability was lost when Next.js migrated to SWC.
### How?
A new `experimental.swcEnvOptions` config is added. Its properties are spread into the `env` block that Next.js passes to SWC for client-side compilation, alongside the existing browserslist-derived `targets`. Server-side compilation is unaffected (always targets `node`).
The option surface mirrors [SWC's preset-env docs](https://swc.rs/docs/configuration/supported-browsers) 1:1, keeping it familiar and forward-compatible.
```js
// next.config.js
module.exports = {
experimental: {
swcEnvOptions: {
mode: 'usage',
coreJs: '3.38',
},
},
}
```
#### Changes:
config-shared.ts — type definition with JSDoc
config-schema.ts — zod validation
next-swc-loader.ts → swc/options.ts — plumb config into the SWC env block
Unit tests (6 cases) + e2e test (dev & production)
Related issues #66562, #63104, #74978
Related discussion #46724
| 2ef504b705011be4cf727f36cba3c85b05c9467b | [
{
"filename": "crates/next-core/src/next_client/context.rs",
"patch": "@@ -332,8 +332,9 @@ pub async fn get_client_module_options_context(\n \n let source_maps = *next_config.client_source_maps(mode).await?;\n \n- let preset_env_config = match &*next_config.experimental_swc_env_options().await? {\n- ... |
electron/electron | 50,676 | fix: dangling raw_ptr MicrotasksRunner::isolate_ | #### Description of Change
Fix a dangling `raw_ptr<v8::Isolate*> MicrotasksRunner::isolate_;` observed by running specs on a local build with dangling raw_ptr checks enabled.
The root cause was that `JavascriptEnvironment::DestroyMicrotasksRunner() ` didn't actually destroy the microtasks runner, which continued to survive after the isolate was freed.
```txt
[DanglingPtr](1/3) A raw_ptr/raw_ref is dangling.
[DanglingPtr](2/3) First, the memory was freed at:
Stack trace:
#0 0x55fcca536432 base::debug::CollectStackTrace() [../../base/debug/stack_trace_posix.cc:1050:7]
#1 0x55fcca51dc51 base::debug::StackTrace::StackTrace() [../../base/debug/stack_trace.cc:280:20]
#2 0x55fcca53da56 base::allocator::(anonymous namespace)::DanglingRawPtrDetected() [../../base/allocator/partition_alloc_support.cc:438:11]
#3 0x55fcca5f61b3 partition_alloc::PartitionRoot::FreeInUnknownRoot<>() [../../base/allocator/partition_allocator/src/partition_alloc/in_slot_metadata.h:389:5]
#4 0x55fccc969fed gin::IsolateHolder::~IsolateHolder() [../../gin/isolate_holder.cc:157:13]
#5 0x55fcc33ff804 electron::JavascriptEnvironment::~JavascriptEnvironment() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#6 0x55fcc33d3959 electron::ElectronBrowserMainParts::~ElectronBrowserMainParts() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#7 0x55fcc33d3a5e electron::ElectronBrowserMainParts::~ElectronBrowserMainParts() [../../electron/shell/browser/electron_browser_main_parts.cc:192:53]
#8 0x55fcc82caf58 content::BrowserMainLoop::~BrowserMainLoop() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#9 0x55fcc82cb19e content::BrowserMainLoop::~BrowserMainLoop() [../../content/browser/browser_main_loop.cc:496:37]
#10 0x55fcc82d0fac content::BrowserMainRunnerImpl::Shutdown() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#11 0x55fcc82ca881 content::BrowserMain() [../../content/browser/browser_main.cc:41:16]
#12 0x55fcc3a98ad9 content::RunBrowserProcessMain() [../../content/app/content_main_runner_impl.cc:701:10]
#13 0x55fcc3a9be57 content::ContentMainRunnerImpl::RunBrowser() [../../content/app/content_main_runner_impl.cc:1325:10]
#14 0x55fcc3a9b160 content::ContentMainRunnerImpl::Run() [../../content/app/content_main_runner_impl.cc:1155:12]
#15 0x55fcc3a97236 content::RunContentProcess() [../../content/app/content_main.cc:356:36]
#16 0x55fcc3a97470 content::ContentMain() [../../content/app/content_main.cc:369:10]
#17 0x55fcc3284555 main [../../electron/shell/app/electron_main_linux.cc:50:10]
#18 0x7ea81162a575 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x2a574)
#19 0x7ea81162a628 __libc_start_main
#20 0x55fcc326802a _start
[DanglingPtr](3/3) Later, the dangling raw_ptr was released at:
Stack trace:
#0 0x55fcca536432 base::debug::CollectStackTrace() [../../base/debug/stack_trace_posix.cc:1050:7]
#1 0x55fcca51dc51 base::debug::StackTrace::StackTrace() [../../base/debug/stack_trace.cc:280:20]
#2 0x55fcca53db3d base::allocator::(anonymous namespace)::DanglingRawPtrReleased<>() [../../base/allocator/partition_alloc_support.cc:600:21]
#3 0x55fcca57be39 base::internal::RawPtrBackupRefImpl<>::ReleaseInternal() [../../base/allocator/partition_allocator/src/partition_alloc/in_slot_metadata.h:211:7]
#4 0x55fcc34046ef electron::MicrotasksRunner::~MicrotasksRunner() [../../base/allocator/partition_allocator/src/partition_alloc/pointers/raw_ptr_backup_ref_impl.h:194:7]
#5 0x55fcc33ff838 electron::JavascriptEnvironment::~JavascriptEnvironment() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#6 0x55fcc33d3959 electron::ElectronBrowserMainParts::~ElectronBrowserMainParts() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#7 0x55fcc33d3a5e electron::ElectronBrowserMainParts::~ElectronBrowserMainParts() [../../electron/shell/browser/electron_browser_main_parts.cc:192:53]
#8 0x55fcc82caf58 content::BrowserMainLoop::~BrowserMainLoop() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#9 0x55fcc82cb19e content::BrowserMainLoop::~BrowserMainLoop() [../../content/browser/browser_main_loop.cc:496:37]
#10 0x55fcc82d0fac content::BrowserMainRunnerImpl::Shutdown() [../../third_party/libc++/src/include/__memory/unique_ptr.h:74:5]
#11 0x55fcc82ca881 content::BrowserMain() [../../content/browser/browser_main.cc:41:16]
#12 0x55fcc3a98ad9 content::RunBrowserProcessMain() [../../content/app/content_main_runner_impl.cc:701:10]
#13 0x55fcc3a9be57 content::ContentMainRunnerImpl::RunBrowser() [../../content/app/content_main_runner_impl.cc:1325:10]
#14 0x55fcc3a9b160 content::ContentMainRunnerImpl::Run() [../../content/app/content_main_runner_impl.cc:1155:12]
#15 0x55fcc3a97236 content::RunContentProcess() [../../content/app/content_main.cc:356:36]
#16 0x55fcc3a97470 content::ContentMain() [../../content/app/content_main.cc:369:10]
#17 0x55fcc3284555 main [../../electron/shell/app/electron_main_linux.cc:50:10]
#18 0x7ea81162a575 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x2a574)
#19 0x7ea81162a628 __libc_start_main
#20 0x55fcc326802a _start
```
Checks enabled by building with these flags:
```diff
diff --git a/build/args/all.gn b/build/args/all.gn
index 45939f456f..1934854c67 100644
--- a/build/args/all.gn
+++ b/build/args/all.gn
@@ -53,8 +53,11 @@ use_qt6 = false
# https://chromium.googlesource.com/chromium/src/+/main/docs/dangling_ptr.md
# TODO(vertedinde): hunt down dangling pointers on Linux
-enable_dangling_raw_ptr_checks = false
-enable_dangling_raw_ptr_feature_flag = false
+is_debug = true
+enable_dangling_raw_ptr_checks = true
+enable_dangling_raw_ptr_feature_flag = true
+enable_backup_ref_ptr_support = true
+enable_backup_ref_ptr_feature_flag = true
```
#### Checklist
- [x] PR description included
- [x] I have built and tested this PR
- [x] `npm test` passes
- [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. | e5c3b18791066a3fb82824f981a5dc8871668c5c | [
{
"filename": "shell/browser/javascript_environment.cc",
"patch": "@@ -86,6 +86,7 @@ JavascriptEnvironment::~JavascriptEnvironment() {\n // Otherwise cppgc::internal::Sweeper::Start will try to request a task runner\n // from the NodePlatform with an already unregistered isolate.\n locker_.reset();\n+... |
golang/go | 78,079 | archive/tar: document blocking factor of 1 | The Writer uses a blocking factor of 1 (512 bytes per record),
unlike most tar command-line tools which default to 20
(10240 bytes). This difference can cause confusion when
comparing archive sizes. Add a note to the package
documentation.
Fixes #78037 | ea4de36aaf08ad15a541f997bfd9b07e8683f170 | [
{
"filename": "src/archive/tar/common.go",
"patch": "@@ -8,6 +8,11 @@\n // can be read and written in a streaming manner.\n // This package aims to cover most variations of the format,\n // including those produced by GNU and BSD tar tools.\n+//\n+// The [Writer] uses a blocking factor of 1 (512 bytes per r... |
huggingface/transformers | 45,180 | 🔒 Pin GitHub Actions to commit SHAs | ## 🔒 Pin GitHub Actions to commit SHAs
This PR pins all GitHub Actions to their exact commit SHA instead of mutable tags or branch names.
**Why?**
Pinning to a SHA prevents supply chain attacks where a tag (e.g. `v4`) could be moved to point to malicious code.
### Changes
| Workflow | Action | Avant | Après | SHA |
|---|---|---|---|---|
| `add-model-like.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `add-model-like.yml` | `actions/cache` | `v4` | `v4` | `0057852bfaa8…` |
| `add-model-like.yml` | `actions/upload-artifact` | `v4` | `v4` | `ea165f8d65b6…` |
| `benchmark.yml` | `actions/checkout` | `v5` | `v6.0.2` | `de0fac2e4500…` |
| `extras-smoke-test.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `extras-smoke-test.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `extras-smoke-test.yml` | `actions/setup-python` | `v5` | `v5` | `a26af69be951…` |
| `extras-smoke-test.yml` | `actions/upload-artifact` | `v4` | `v4` | `ea165f8d65b6…` |
| `extras-smoke-test.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `extras-smoke-test.yml` | `actions/setup-python` | `v5` | `v5` | `a26af69be951…` |
| `extras-smoke-test.yml` | `actions/download-artifact` | `v4` | `v4` | `d3f86a106a0b…` |
| `circleci-failure-summary-comment.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `circleci-failure-summary-comment.yml` | `actions/setup-python` | `v5` | `v5` | `a26af69be951…` |
| `circleci-failure-summary-comment.yml` | `actions/github-script` | `v7` | `v7` | `f28e40c7f34b…` |
| `assign-reviewers.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `assign-reviewers.yml` | `actions/setup-python` | `v5` | `v5` | `a26af69be951…` |
| `release-conda.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `release-conda.yml` | `conda-incubator/setup-miniconda` | `v2` | `v2` | `9f54435e0e72…` |
| `build-ci-docker-images.yml` | `docker/setup-buildx-action` | `v3` | `v3` | `8d2750c68a42…` |
| `build-ci-docker-images.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `build-ci-docker-images.yml` | `docker/login-action` | `v3` | `v3` | `c94ce9fb4685…` |
| `build-ci-docker-images.yml` | `docker/build-push-action` | `v5` | `v5` | `ca052bb54ab0…` |
| `build-ci-docker-images.yml` | `huggingface/hf-workflows/.github/actions/post-slack` | `main` | `main` | `a88e7fa2eaee…` |
| `build_documentation.yml` | `huggingface/doc-builder/.github/workflows/build_main_documentation.yml` | `main` | `main` | `90b4ee2c10b8…` |
| `build_documentation.yml` | `huggingface/doc-builder/.github/workflows/build_main_documentation.yml` | `main` | `main` | `90b4ee2c10b8…` |
| `build_pr_documentation.yml` | `huggingface/doc-builder/.github/workflows/build_pr_documentation.yml` | `main` | `main` | `90b4ee2c10b8…` |
| `upload_pr_documentation.yml` | `huggingface/doc-builder/.github/workflows/upload_pr_documentation.yml` | `main` | `main` | `90b4ee2c10b8…` |
| `self-scheduled-amd-mi250-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi250-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi250-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi250-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi325-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled_arc_scale_set.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi325-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled_arc_scale_set.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi325-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled_arc_scale_set.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `self-scheduled-amd-mi325-caller.yml` | `huggingface/hf-workflows/.github/workflows/transformers_amd_ci_scheduled_arc_scale_set.yaml` | `main` | `main` | `a88e7fa2eaee…` |
| `codeql.yml` | `huggingface/security-workflows/.github/workflows/codeql-reusable.yml` | `main` | `main` | `1b6a139c28db…` |
| `check-workflow-permissions.yml` | `huggingface/security-workflows/.github/workflows/permissions-advisor-reusable.yml` | `main` | `main` | `1b6a139c28db…` |
| `ssh-runner.yml` | `huggingface/tailscale-action` | `main` | `main` | `7d53c9737e53…` |
| `model_jobs.yml` | `actions/upload-artifact` | `v4` | `v4` | `ea165f8d65b6…` |
| `model_jobs.yml` | `huggingface/transformers/.github/workflows/collated-reports.yml` | `main` | `main` | `6abd9725ee7d…` |
| `release.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `release.yml` | `actions/setup-python` | `v5` | `v5` | `a26af69be951…` |
| `release.yml` | `actions/upload-artifact` | `v4` | `v4` | `ea165f8d65b6…` |
| `release.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `release.yml` | `actions/download-artifact` | `v4` | `v4` | `d3f86a106a0b…` |
| `release.yml` | `pypa/gh-action-pypi-publish` | `release/v1` | `release/v1` | `ed0c53931b1d…` |
| `trufflehog.yml` | `actions/checkout` | `v4` | `v6.0.2` | `de0fac2e4500…` |
| `trufflehog.yml` | `trufflesecurity/trufflehog` | `main` | `main` | `6bd2d14f7a4b…` |
> 🤖 Generated by `/github-actions-audit` — [security/pin-actions-to-sha]
---
Closes #45182
Closes huggingface/tracking-issues#43 | b0e15ab8593ff0702f2ba0d5ff9a52d57dc1ac4a | [
{
"filename": ".github/workflows/trufflehog.yml",
"patch": "@@ -11,10 +11,10 @@ jobs:\n runs-on: ubuntu-latest\n steps:\n - name: Checkout code\n- uses: actions/checkout@v4\n+ uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2\n with:\n fe... |
ollama/ollama | 15,213 | Feature/bonsai q1 0 support | null | bdcec130865b5c9fbfb870ec0edd27333fa2c751 | [
{
"filename": "README.md",
"patch": "@@ -1,91 +1,104 @@\n-<p align=\"center\">\n- <a href=\"https://ollama.com\">\n- <img src=\"https://github.com/ollama/ollama/assets/3325447/0d0b44e2-8f4a-4e99-9b52-a5c1c741c8f7\" alt=\"ollama\" width=\"200\"/>\n- </a>\n-</p>\n+# Ollama + Bonsai Q1_0 Support\n \n-# Ol... |
nodejs/node | 62,544 | meta: bump cachix/cachix-action from 16 to 17 | Bumps [cachix/cachix-action](https://github.com/cachix/cachix-action) from 16 to 17.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/cachix/cachix-action/releases">cachix/cachix-action's releases</a>.</em></p>
<blockquote>
<h2>v17</h2>
<h2>What's Changed</h2>
<h3>Breaking changes</h3>
<ul>
<li>Upgrade action to use Node 24 by <a href="https://github.com/sandydoo"><code>@sandydoo</code></a> in <a href="https://redirect.github.com/cachix/cachix-action/pull/212">cachix/cachix-action#212</a>
<a href="https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/">https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/cachix/cachix-action/compare/v16...v17">https://github.com/cachix/cachix-action/compare/v16...v17</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/cachix/cachix-action/commit/1eb2ef646ac0255473d23a5907ad7b04ce94065c"><code>1eb2ef6</code></a> Merge pull request <a href="https://redirect.github.com/cachix/cachix-action/issues/212">#212</a> from cachix/upgrade-node-24</li>
<li><a href="https://github.com/cachix/cachix-action/commit/75ce400143912180b47fa504676215ca47e1634f"><code>75ce400</code></a> dist: re-build using esbuild targeting node24</li>
<li><a href="https://github.com/cachix/cachix-action/commit/2b33705a8232e51ac94414b3b8c203d0a5e42ca3"><code>2b33705</code></a> deps: update devenv inputs</li>
<li><a href="https://github.com/cachix/cachix-action/commit/04937db281cae63d98e660f990648ab4eef1cec1"><code>04937db</code></a> breaking: update action to Node 24</li>
<li><a href="https://github.com/cachix/cachix-action/commit/ca2e51995f0edefbb31bc858102abd109580c99c"><code>ca2e519</code></a> ci: use 25.11 for tests</li>
<li><a href="https://github.com/cachix/cachix-action/commit/e7c5c1add25228c774d40ae0adbd520ea7c919c0"><code>e7c5c1a</code></a> Merge pull request <a href="https://redirect.github.com/cachix/cachix-action/issues/208">#208</a> from cachix/dependabot/github_actions/actions/checkout-6</li>
<li><a href="https://github.com/cachix/cachix-action/commit/bea8a506457e59a062336709ee10a5677fd9a59e"><code>bea8a50</code></a> ci: allow running tests manually and with a custom nix version</li>
<li><a href="https://github.com/cachix/cachix-action/commit/2e35755955435b7976b76834528c38a0fcf725c0"><code>2e35755</code></a> chore(deps): bump actions/checkout from 5 to 6</li>
<li>See full diff in <a href="https://github.com/cachix/cachix-action/compare/3ba601ff5bbb07c7220846facfa2cd81eeee15a1...1eb2ef646ac0255473d23a5907ad7b04ce94065c">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | afdc523e29735608b79a6faaaabc5681d2c05bad | [
{
"filename": ".github/workflows/test-shared.yml",
"patch": "@@ -169,7 +169,7 @@ jobs:\n with:\n extra_nix_config: sandbox = true\n \n- - uses: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1 # v16\n+ - uses: cachix/cachix-action@1eb2ef646ac0255473d23a5907ad7b04ce9... |
facebook/react | 36,153 | [Compiler] Remove ObjectMethod HIR node, lower as FunctionExpression #36151 | The compiler memoizes `{ foo() {} }` and `{ foo: () => {} }` differently — method shorthand gets the whole object in one scope, function expressions get split into separate cache slots. Same semantics, different output.
The issue is in `AlignObjectMethodScopes` — it only looks at `ObjectMethod` instructions when deciding what to merge. This extends it to also pick up `FunctionExpression` values used as object properties.
Fixes #36151 | eab37c236ebeeb0b380ff95670f23057a63f3063 | [
{
"filename": "compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/bug-inconsistent-memoization-object-fn-expression.expect.md",
"patch": "@@ -0,0 +1,70 @@\n+\n+## Input\n+\n+```javascript\n+function Component({a, b}) {\n+ return {\n+ test1: () => {\n+ console.log(a);\n+ ... |
rust-lang/rust | 154,790 | Add regression test for #132055 (escaping bound vars ICE) | ## Summary
Adds a regression test for rust-lang/rust#132055.
Using `return_type_notation` with a trait that has a lifetime parameter but omitting the lifetime in the bound used to ICE with "assertion failed: !t.has_escaping_bound_vars()". The compiler now correctly reports `E0106` (missing lifetime specifier) without crashing.
## Test
`tests/ui/associated-type-bounds/ice-escaping-bound-vars-132055.rs`
Closes rust-lang/rust#132055 | d95a52802dc7ed8c30259903bb49351e33953660 | [
{
"filename": "tests/ui/associated-type-bounds/ice-escaping-bound-vars-132055.rs",
"patch": "@@ -0,0 +1,15 @@\n+// Regression test for #132055\n+// This used to ICE with \"assertion failed: !t.has_escaping_bound_vars()\"\n+// when using return_type_notation with a trait that has a lifetime parameter\n+// bu... |
vercel/next.js | 92,266 | Update debugging.mdx | <!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
| ce247771c6384e8c511f1539d5b3e5a9411a2939 | [
{
"filename": "docs/01-app/02-guides/debugging.mdx",
"patch": "@@ -96,10 +96,26 @@ For Firefox:\n \n In either browser, any time your client-side code reaches a [`debugger`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Statements/debugger) statement, code execution will pause and that file wi... |
golang/go | 78,078 | os: update examples to use errors.Is instead of deprecated helpers | The `os.IsExist` and `os.IsNotExist` functions predate `errors.Is` and their documentation recommends using `errors.Is(err, fs.ErrExist)` and `errors.Is(err, fs.ErrNotExist)` in new code.
Update `ExampleMkdir` and `ExampleUserConfigDir` to follow this recommendation.
Fixes #77643 | a99a8761d31d24bd639361e44599ae714879aa9b | [
{
"filename": "src/os/example_test.go",
"patch": "@@ -246,7 +246,7 @@ func ExampleWriteFile() {\n \n func ExampleMkdir() {\n \terr := os.Mkdir(\"testdir\", 0750)\n-\tif err != nil && !os.IsExist(err) {\n+\tif err != nil && !errors.Is(err, fs.ErrExist) {\n \t\tlog.Fatal(err)\n \t}\n \terr = os.WriteFile(\"te... |
electron/electron | 50,672 | fix: resolve getFileHandle concurrent stalling by queuing callbacks | Backport of #50597
See that PR for details.
Notes: Fixed an issue where concurrent `getFileHandle` requests on the same path could stall indefinitely. | 19c1dd1f372f1c1f0f485468c1f92e07def0a30f | [
{
"filename": "shell/browser/file_system_access/file_system_access_permission_context.cc",
"patch": "@@ -697,7 +697,11 @@ void FileSystemAccessPermissionContext::ConfirmSensitiveEntryAccess(\n content::GlobalRenderFrameHostId frame_id,\n base::OnceCallback<void(SensitiveEntryResult)> callback) {\n ... |
nodejs/node | 62,543 | meta: bump actions/cache from 5.0.3 to 5.0.4 | Bumps [actions/cache](https://github.com/actions/cache) from 5.0.3 to 5.0.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/actions/cache/releases">actions/cache's releases</a>.</em></p>
<blockquote>
<h2>v5.0.4</h2>
<h2>What's Changed</h2>
<ul>
<li>Add release instructions and update maintainer docs by <a href="https://github.com/Link"><code>@Link</code></a>- in <a href="https://redirect.github.com/actions/cache/pull/1696">actions/cache#1696</a></li>
<li>Potential fix for code scanning alert no. 52: Workflow does not contain permissions by <a href="https://github.com/Link"><code>@Link</code></a>- in <a href="https://redirect.github.com/actions/cache/pull/1697">actions/cache#1697</a></li>
<li>Fix workflow permissions and cleanup workflow names / formatting by <a href="https://github.com/Link"><code>@Link</code></a>- in <a href="https://redirect.github.com/actions/cache/pull/1699">actions/cache#1699</a></li>
<li>docs: Update examples to use the latest version by <a href="https://github.com/XZTDean"><code>@XZTDean</code></a> in <a href="https://redirect.github.com/actions/cache/pull/1690">actions/cache#1690</a></li>
<li>Fix proxy integration tests by <a href="https://github.com/Link"><code>@Link</code></a>- in <a href="https://redirect.github.com/actions/cache/pull/1701">actions/cache#1701</a></li>
<li>Fix cache key in examples.md for bun.lock by <a href="https://github.com/RyPeck"><code>@RyPeck</code></a> in <a href="https://redirect.github.com/actions/cache/pull/1722">actions/cache#1722</a></li>
<li>Update dependencies & patch security vulnerabilities by <a href="https://github.com/Link"><code>@Link</code></a>- in <a href="https://redirect.github.com/actions/cache/pull/1738">actions/cache#1738</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/XZTDean"><code>@XZTDean</code></a> made their first contribution in <a href="https://redirect.github.com/actions/cache/pull/1690">actions/cache#1690</a></li>
<li><a href="https://github.com/RyPeck"><code>@RyPeck</code></a> made their first contribution in <a href="https://redirect.github.com/actions/cache/pull/1722">actions/cache#1722</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/actions/cache/compare/v5...v5.0.4">https://github.com/actions/cache/compare/v5...v5.0.4</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/actions/cache/blob/main/RELEASES.md">actions/cache's changelog</a>.</em></p>
<blockquote>
<h1>Releases</h1>
<h2>How to prepare a release</h2>
<blockquote>
<p>[!NOTE]<br />
Relevant for maintainers with write access only.</p>
</blockquote>
<ol>
<li>Switch to a new branch from <code>main</code>.</li>
<li>Run <code>npm test</code> to ensure all tests are passing.</li>
<li>Update the version in <a href="https://github.com/actions/cache/blob/main/package.json"><code>https://github.com/actions/cache/blob/main/package.json</code></a>.</li>
<li>Run <code>npm run build</code> to update the compiled files.</li>
<li>Update this <a href="https://github.com/actions/cache/blob/main/RELEASES.md"><code>https://github.com/actions/cache/blob/main/RELEASES.md</code></a> with the new version and changes in the <code>## Changelog</code> section.</li>
<li>Run <code>licensed cache</code> to update the license report.</li>
<li>Run <code>licensed status</code> and resolve any warnings by updating the <a href="https://github.com/actions/cache/blob/main/.licensed.yml"><code>https://github.com/actions/cache/blob/main/.licensed.yml</code></a> file with the exceptions.</li>
<li>Commit your changes and push your branch upstream.</li>
<li>Open a pull request against <code>main</code> and get it reviewed and merged.</li>
<li>Draft a new release <a href="https://github.com/actions/cache/releases">https://github.com/actions/cache/releases</a> use the same version number used in <code>package.json</code>
<ol>
<li>Create a new tag with the version number.</li>
<li>Auto generate release notes and update them to match the changes you made in <code>RELEASES.md</code>.</li>
<li>Toggle the set as the latest release option.</li>
<li>Publish the release.</li>
</ol>
</li>
<li>Navigate to <a href="https://github.com/actions/cache/actions/workflows/release-new-action-version.yml">https://github.com/actions/cache/actions/workflows/release-new-action-version.yml</a>
<ol>
<li>There should be a workflow run queued with the same version number.</li>
<li>Approve the run to publish the new version and update the major tags for this action.</li>
</ol>
</li>
</ol>
<h2>Changelog</h2>
<h3>5.0.4</h3>
<ul>
<li>Bump <code>minimatch</code> to v3.1.5 (fixes ReDoS via globstar patterns)</li>
<li>Bump <code>undici</code> to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)</li>
<li>Bump <code>fast-xml-parser</code> to v5.5.6</li>
</ul>
<h3>5.0.3</h3>
<ul>
<li>Bump <code>@actions/cache</code> to v5.0.5 (Resolves: <a href="https://github.com/actions/cache/security/dependabot/33">https://github.com/actions/cache/security/dependabot/33</a>)</li>
<li>Bump <code>@actions/core</code> to v2.0.3</li>
</ul>
<h3>5.0.2</h3>
<ul>
<li>Bump <code>@actions/cache</code> to v5.0.3 <a href="https://redirect.github.com/actions/cache/pull/1692">#1692</a></li>
</ul>
<h3>5.0.1</h3>
<ul>
<li>Update <code>@azure/storage-blob</code> to <code>^12.29.1</code> via <code>@actions/cache@5.0.1</code> <a href="https://redirect.github.com/actions/cache/pull/1685">#1685</a></li>
</ul>
<h3>5.0.0</h3>
<blockquote>
<p>[!IMPORTANT]
<code>actions/cache@v5</code> runs on the Node.js 24 runtime and requires a minimum Actions Runner version of <code>2.327.1</code>.</p>
</blockquote>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/actions/cache/commit/668228422ae6a00e4ad889ee87cd7109ec5666a7"><code>6682284</code></a> Merge pull request <a href="https://redirect.github.com/actions/cache/issues/1738">#1738</a> from actions/prepare-v5.0.4</li>
<li><a href="https://github.com/actions/cache/commit/e34039626f957d3e3e50843d15c1b20547fc90e2"><code>e340396</code></a> Update RELEASES</li>
<li><a href="https://github.com/actions/cache/commit/8a671105293e81530f1af99863cdf94550aba1a6"><code>8a67110</code></a> Add licenses</li>
<li><a href="https://github.com/actions/cache/commit/1865903e1b0cb750dda9bc5c58be03424cc62830"><code>1865903</code></a> Update dependencies & patch security vulnerabilities</li>
<li><a href="https://github.com/actions/cache/commit/565629816435f6c0b50676926c9b05c254113c0c"><code>5656298</code></a> Merge pull request <a href="https://redirect.github.com/actions/cache/issues/1722">#1722</a> from RyPeck/patch-1</li>
<li><a href="https://github.com/actions/cache/commit/4e380d19e192ace8e86f23f32ca6fdec98a673c6"><code>4e380d1</code></a> Fix cache key in examples.md for bun.lock</li>
<li><a href="https://github.com/actions/cache/commit/b7e8d49f17405cc70c1c120101943203c98d3a4b"><code>b7e8d49</code></a> Merge pull request <a href="https://redirect.github.com/actions/cache/issues/1701">#1701</a> from actions/Link-/fix-proxy-integration-tests</li>
<li><a href="https://github.com/actions/cache/commit/984a21b1cb176a0936f4edafb42be88978f93ef1"><code>984a21b</code></a> Add traffic sanity check step</li>
<li><a href="https://github.com/actions/cache/commit/acf2f1f76affe1ef80eee8e56dfddd3b3e5f0fba"><code>acf2f1f</code></a> Fix resolution</li>
<li><a href="https://github.com/actions/cache/commit/95a07c51324af6001b4d6ab8dff29f4dfadc2531"><code>95a07c5</code></a> Add wait for proxy</li>
<li>Additional commits viewable in <a href="https://github.com/actions/cache/compare/cdf6c1fa76f9f475f3d7449005a359c84ca0f306...668228422ae6a00e4ad889ee87cd7109ec5666a7">compare view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details> | 1de92081b7b980275c3ac64a08d302f44bdb1e68 | [
{
"filename": ".github/workflows/update-v8.yml",
"patch": "@@ -20,7 +20,7 @@ jobs:\n with:\n persist-credentials: false\n - name: Cache node modules and update-v8\n- uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v5.0.3\n+ uses: actions/cache@668228422a... |
ollama/ollama | 15,207 | llm: add automatic MOE expert weight offloading | ## Summary
Adds automatic partial layer offloading for Mixture-of-Experts models on the new engine. When a MOE model doesn't fully fit in VRAM, expert weights (`ffn_gate_exps`, `ffn_up_exps`, `ffn_down_exps`) can be selectively placed on CPU while the layer's
attention, norms, and routing tensors remain on GPU.
This addresses #11772 and the feedback on #12333:
- Automatic based on available memory — no user configuration
- Works with the existing multi-GPU layer assignment framework
- Targets the new engine only (`ml/`, `runner/ollamarunner/`, `llm/`)
## How it works
1. The GGML backend now classifies expert tensors separately, tracking their memory in a new `DeviceMemory.ExpertWeights` field
2. After the standard layout assigns full layers to GPUs, remaining VRAM is greedily filled with additional layers at base-only size (expert weights on CPU)
3. `ExpertOffload` layer indices are threaded through `LoadRequest` → `BackendParams` → GGML backend, which routes expert tensors to CPU buffers for those layers
## Benchmarks
Tested with `qwen3:30b-a3b` (Q4_K_M, 19.3 GB) on an RTX 3060 (12 GB VRAM, 24 GB system RAM):
| Metric | Baseline (main) | MOE offload | Delta |
|--------|-----------------|-------------|-------|
| VRAM | 11.84 GB (61.4%) | 11.98 GB (62.2%) | +0.8% |
| Generate | 29.41 tok/s | 26.64 tok/s | -9.4% |
| Prefill | 1264.76 tok/s | 646.05 tok/s | -48.9% |
On this hardware the model already fits ~61% on GPU at full layer size, leaving little remaining VRAM for additional base-only layers. The few extra layers add cross-device transfer overhead that outweighs their benefit.
The feature should have more impact on systems where VRAM is significantly more constrained relative to model size — e.g., 6-8 GB GPUs running large MOE models where many more layers would benefit from partial offloading. **Looking for feedback from users
with more constrained setups.**
## Test plan
- [x] Existing `TestLLMServerFitGPU` passes
- [x] Dense models unaffected (pass 2 skipped when no expert weights detected)
- [x] MOE model loads and runs correctly with expert offloading active
- [ ] Testing on more VRAM-constrained hardware (6-8 GB GPU)
- [ ] Multi-GPU testing
| 388e3b2cbcd4e255dc364f6dda4096b242ab5bda | [
{
"filename": "llm/server.go",
"patch": "@@ -480,6 +480,7 @@ type LoadRequest struct {\n \tKvCacheType string\n \tNumThreads int\n \tGPULayers ml.GPULayersList\n+\tExpertOffload []int\n \tMultiUserCache bool\n \n \t// Legacy fields - not used with the Ollama engine\n@@ -502,15 +503,17 @@ func (... |
facebook/react | 36,147 | [Feature] Add useList hook with remove and removeAt functions | ### Overview
This PR adds a new `useList` hook to simplify list management in React components.
It provides a convenient way to remove items by condition or by index while automatically triggering re-renders.
### Motivation
Currently, developers need to manually use `filter` or `splice` to remove items from arrays in React, which is repetitive and error-prone.
`useList` offers a unified abstraction to simplify these operations.
### Features
- `remove(predicate)` — Removes items that match the given condition.
- `removeAt(index)` — Removes the item at the specified index.
- `setList(newList)` — Replaces the entire list.
- Safe handling for empty lists or invalid indices.
### Example Usage
```js
const { list, setList, remove, removeAt } = useList([1, 2, 3, 4]);
// Remove all even numbers
remove(x => x % 2 === 0); // list becomes [1, 3]
// Remove item at index 0
removeAt(0); // list becomes [3]
````
### Test Coverage
* Initializing list (with default or provided values)
* Updating list with `setList`
* `remove` for partial match, no match, and full match
* `removeAt` for valid index, invalid index, and empty list
Closes #36005 | 2151bf61f0f35c417ff3044bd90a6fd8b6ebb0b0 | [
{
"filename": "packages/react/src/__tests__/useList-test.js",
"patch": "@@ -21,7 +21,7 @@ describe('useList', () => {\n });\n \n function renderHook(hook) {\n- const result = { current: null };\n+ const result = {current: null};\n let rerender;\n function TestComponent() {\n const [,... |
rust-lang/rust | 154,789 | Add regression test for #138710 (interpret queries ICE) | ## Summary
Adds a regression test for rust-lang/rust#138710.
Using `min_generic_const_args` with associated types and consts in an async function returning a `dyn` trait used to ICE in `rustc_middle::mir::interpret::queries`. The compiler now correctly reports errors without crashing.
## Test
`tests/ui/consts/ice-interpret-queries-138710.rs`
Closes rust-lang/rust#138710 | d5b6e8dbdce088429bcb17fd5bda58bee505f261 | [
{
"filename": "tests/ui/consts/ice-interpret-queries-138710.rs",
"patch": "@@ -0,0 +1,25 @@\n+//@ edition: 2021\n+// Regression test for #138710\n+// This used to ICE in rustc_middle::mir::interpret::queries\n+// when using min_generic_const_args with associated types and consts\n+// in an async context. No... |
huggingface/transformers | 45,179 | [CB] Tweaks to update and minor fixes | ## Summary
This PR ads minor changes to `cache.update`, updates the memory handler with all new features and refactors a few parts of the code to make it more readable.
Cache indexing:
- Replace fancy indexing (cache[idx, :, :]) with explicit torch.index_select / index_copy_, which have cleaner behavior under torch.compile and require non-negative indices.
- Switch index storage tensors from int32 to int64 to match index_select/index_copy_ requirements, removing hidden .long() casts in the hot path.
- Introduce sentinel_index and trash_index, which are dedicated positions in the cache padding zone that were already used but now have a name. It also avoids passing negative values (like -1) to indexing functions.
Memory handler (cache.py)
- Collapse the three separate solving methods (compute_num_blocks_and_max_batch_tokens, compute_max_batch_tokens, compute_num_blocks) and verbose compute_memory_footprint into a single polynomial coefficient model. Each term maps to a tensor in _setup_static_tensors, making the memory model auditable and impossible to drift between solvers.
- Account for previously unmodeled tensors: block_table, logprobs output rows, and async double-buffering (when use_async_batching is on).
Benchmark (continuous_batching_overall.py)
- Store results in a timestamped directory instead of a single file, enabling comparison against any previous baseline.
Tests
- Add TestMemoryHandlerPrediction: allocates tensors matching the handler's polynomial model and validates predicted vs actual GPU memory across 5 configurations.
- Fix test_paged_attention: move cache params to ContinuousBatchingConfig, handle list-type eos_token_id, accept attention-impl-dependent output variants.
## Performance
Those changes add between 1 and 3% of performance (when not using the block table) depending on the workload. No regressions.
## Testing
All tests pass, expect `tests/generation/test_continuous_batching.py::ContinuousBatchingWithAcceleratorTest::test_prefix_sharing` which is fixed in https://github.com/huggingface/transformers/pull/45026 | b3486057d1df05604eadf63f1150bc13f4d6d327 | [
{
"filename": ".github/workflows/build_documentation.yml",
"patch": "@@ -28,7 +28,7 @@ jobs:\n commit_sha: ${{ github.sha }}\n package: transformers\n notebook_folder: transformers_doc\n- languages: ar de es fr hi it ja ko pt zh\n+ languages: ar de es fr hi it ja ko pt tr zh\n ... |
vercel/next.js | 92,265 | Update debugging.mdx | melhoria
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
| 3741333f76ae9b1b00877e199aaa1a5eb8bd848f | [
{
"filename": "docs/01-app/02-guides/debugging.mdx",
"patch": "@@ -1,4 +1,4 @@\n----\n+automated-humanized-floor-plan-generation-flow.ts---\n title: How to use debugging tools with Next.js\n nav_title: Debugging\n description: Learn how to debug your Next.js application with VS Code, Chrome DevTools, or Fir... |
electron/electron | 50,671 | fix: resolve getFileHandle concurrent stalling by queuing callbacks | Backport of #50597
See that PR for details.
Notes: Fixed an issue where concurrent `getFileHandle` requests on the same path could stall indefinitely. | 04b468afb18655885f3bfd6404c4c4b292b00664 | [
{
"filename": "shell/browser/file_system_access/file_system_access_permission_context.cc",
"patch": "@@ -697,7 +697,11 @@ void FileSystemAccessPermissionContext::ConfirmSensitiveEntryAccess(\n content::GlobalRenderFrameHostId frame_id,\n base::OnceCallback<void(SensitiveEntryResult)> callback) {\n ... |
ollama/ollama | 15,204 | app: use the same client for inference and other requests | Previously we were accidentally using different clients/UAs depending on whether it was an inference call or a different call. This change makes them consistent, other than the timeout being different. | 68ce1a48a9ce238e611971d111b9264a13a301bd | [
{
"filename": "app/ui/ui.go",
"patch": "@@ -342,8 +342,18 @@ func (t *userAgentTransport) RoundTrip(req *http.Request) (*http.Response, error\n \n // httpClient returns an HTTP client that automatically adds the User-Agent header\n func (s *Server) httpClient() *http.Client {\n+\treturn userAgentHTTPClient(... |
nodejs/node | 62,541 | http: add req.signal to IncomingMessage | Fixes: https://github.com/nodejs/node/issues/62481
## Summary
Adds a lazy `signal` getter to `IncomingMessage` that returns an
`AbortSignal` which aborts when the request is closed or aborted.
This mirrors the Web Fetch API's `Request.signal` and Deno's
`request.signal`.
## Motivation
Currently, cancelling async work (DB queries, fetch calls) when a
client disconnects requires manual boilerplate in every request handler:
```js
// before
server.on('request', async (req, res) => {
const ac = new AbortController();
req.on('close', () => ac.abort());
const data = await fetch('https://slow-api.com', { signal: ac.signal });
res.end(JSON.stringify(data));
});
```
With this change:
```js
// after
server.on('request', async (req, res) => {
const data = await fetch('https://slow-api.com', { signal: req.signal });
res.end(JSON.stringify(data));
});
```
## Design
**Lazy initialization** — `AbortController` is only created when
`req.signal` is first accessed. Zero overhead for handlers that
do not use it.
**Single listener** — listens on `this.once('close')` and
`this.once('abort')` rather than `socket.once('close')` directly,
since the request stream's `close` event fires in all teardown paths:
- socket close propagates through `_destroy()` to req `close`
- socketless `req.destroy()` fires req `close` directly
- client abort fires req `abort` directly
**Race condition** — if `.signal` is accessed after `req.destroy()`
has already fired, `this.destroyed` is checked and the signal is
aborted immediately rather than registering a listener that would
never fire.
**`configurable: true`** — allows frameworks (Express, Fastify, Koa)
to override the property on their own subclasses.
## Changes
- `lib/_http_incoming.js` — adds `signal` getter to `IncomingMessage`
- `test/parallel/test-http-request-signal.js` — adds tests
## Tests
- `req.signal` is an `AbortSignal` and not aborted initially
- signal aborts when `'abort'` event fires
- signal aborts when `'close'` event fires (client disconnect)
- signal is pre-aborted if accessed after `req.destroy()` (race condition)
- multiple accesses return the same signal instance (lazy init)
---
Fixes: https://github.com/nodejs/node/issues/62481 | 48d116f561b3f95518ad8d01ba7c285e441b6c76 | [
{
"filename": "doc/api/http.md",
"patch": "@@ -2989,6 +2989,51 @@ added: v0.5.9\n \n Calls `message.socket.setTimeout(msecs, callback)`.\n \n+### `message.signal`\n+\n+<!-- YAML\n+added: REPLACEME\n+-->\n+\n+* Type: {AbortSignal}\n+\n+An {AbortSignal} that is aborted when the underlying socket closes or the... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.