Datasets:
repo stringclasses 10
values | pr_number int64 7 155k | title stringlengths 4 137 | body stringlengths 0 68.4k | buggy_commit stringlengths 40 40 ⌀ | fix_commit stringlengths 40 40 | buggy_distance int64 1 30 ⌀ | confidence stringclasses 3
values | files listlengths 1 5 |
|---|---|---|---|---|---|---|---|---|
vercel/next.js | 92,354 | Handle edge runtime in places that import node:stream | ## What?
The codepath would cause checks to fail during deployment because it tries to import `node:stream` even when not used. This adds a specific path for edge runtime to avoid that. | ff7cd1bf2340ea56369c39d1aa74f1e273a7d233 | b6017fac6a98a2337ce8c173ab72ad527e2b556a | 19 | medium | [
{
"filename": "packages/next/errors.json",
"patch": "@@ -1145,5 +1145,8 @@\n \"1144\": \"Prefetch inlining is enabled but no hints were found for route \\\"%s\\\". This is a bug in the Next.js build pipeline — prefetch-hints.json should contain an entry for every route that produces segment data.\",\n \... |
nodejs/node | 62,002 | doc: include url.resolve() in DEP0169 application deprecation | Fixes: https://github.com/nodejs/node/issues/61816
Refs: https://github.com/nodejs/node/pull/61780 (supersedes)
## Situation
[DEP0169: Insecure url.parse()](https://nodejs.org/docs/latest/api/deprecations.html#DEP0169) lists an Application deprecation (non-node_modules code only) for `url.parse()` that was appli... | 27261b9391d755de208814dfae3f8f0923dc07b4 | d198813a6bf5af727552b816d36de7e84dbfa2c8 | 19 | medium | [
{
"filename": "doc/api/deprecations.md",
"patch": "@@ -2665,11 +2665,15 @@ future release.\n \n <!-- YAML\n changes:\n+ - version:\n+ - v24.0.0\n+ pr-url: https://github.com/nodejs/node/pull/55017\n+ description: DEP0169 covers also `url.format()` and `url.resolve()`.\n - version:\n - v1... |
huggingface/transformers | 45,261 | empty | # What this PR does
It's working, see https://github.com/huggingface/transformers/actions/runs/24025915210
(the failing job in this PR is because the workflow needs to be on `main` to be effective). | abc417a4b6cf05e474921449641f2ff0cc93d3dd | d3c7a19176496fc1ea246aa9df4f678f4fceb1cf | 26 | medium | [
{
"filename": ".github/workflows/circleci-failure-summary-comment.yml",
"patch": "@@ -95,20 +95,37 @@ jobs:\n \"https://circleci.com/api/v2/workflow/${workflow_id}/job\")\n \n # Step 5: Extract collection_job details\n- collection_job_number=$(echo \"$jobs\" | jq -r ... |
vercel/next.js | 92,292 | next-core: deduplicate output assets and detect content conflicts on emit | ### What?
Adds deduplication and conflict detection to the asset emission stage in `crates/next-core/src/emit.rs`, and a new `IssueStage::Emit` variant in `turbopack-core`.
Before emitting, assets are grouped by their output path. If multiple assets map to the same path:
- If their content is identical, one is silen... | f65b10a54d9abb2ceb3890bcadc22e372f635f88 | 81d5e070f4a84b34bb0efe2524c200584fed3215 | 2 | medium | [
{
"filename": "crates/next-core/src/emit.rs",
"patch": "@@ -1,9 +1,16 @@\n-use anyhow::Result;\n+use anyhow::{Ok, Result};\n+use futures::join;\n+use smallvec::{SmallVec, smallvec};\n use tracing::Instrument;\n-use turbo_tasks::{TryFlatJoinIterExt, ValueToStringRef, Vc};\n-use turbo_tasks_fs::{FileSystemPat... |
ollama/ollama | 15,022 | model/parsers: Close think block if tool block starts in Qwen3.5 | This change fixes https://github.com/ollama/ollama/issues/14745 when the model starts a `tool_call` block without closing the `think` block:
```
Thinking: I need to mock Valkey for tests. Let me check how the app initializes Valkey and update TESTING.md with this information.
<tool_call>
<function=bash>
<paramet... | null | 1cefa749aa7b0cd3e330a95f0b03e98dc0a914bd | null | low | [
{
"filename": "model/parsers/qwen35.go",
"patch": "@@ -21,6 +21,7 @@ const (\n const (\n \tqwen35ThinkingOpenTag = \"<think>\"\n \tqwen35ThinkingCloseTag = \"</think>\"\n+\tqwen35ToolCallOpenTag = \"<tool_call>\"\n )\n \n // Qwen35Parser handles qwen3.5 reasoning extraction and delegates post-thinking\n@@... |
rust-lang/rust | 154,292 | Don't use disk-cache for query `def_kind` | <!-- homu-ignore:start -->
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/pull/154292)*
<!-- homu-ignore:end -->
From what I can tell, the `def_kind` query has no local provider, and is always given its value via query feeding, usually from `TyCtxt::create_def`.
If that's the ... | null | 7e46c5f6fb87f8cf4353e058479cef15d1d952b4 | null | low | [
{
"filename": "compiler/rustc_middle/src/queries.rs",
"patch": "@@ -1436,8 +1436,10 @@ rustc_queries! {\n \n query def_kind(def_id: DefId) -> DefKind {\n desc { \"looking up definition kind of `{}`\", tcx.def_path_str(def_id) }\n- cache_on_disk\n separate_provide_extern\n+ ... |
electron/electron | 50,726 | ci: fetch clang-tidy package in fix-sync | Backport of #50704
See that PR for details.
Notes: none | null | 898e77a9ee80428f12d0819c0f565cef102ac3e4 | null | low | [
{
"filename": ".github/actions/fix-sync/action.yml",
"patch": "@@ -27,6 +27,7 @@ runs:\n python3 src/tools/clang/scripts/update.py\n # Refs https://chromium-review.googlesource.com/c/chromium/src/+/6667681\n python3 src/tools/clang/scripts/update.py --package objdump\n+ python... |
ollama/ollama | 15,312 | app: default app home view to new chat instead of launch | 5ab10d347a729ae84b480f93a502173e81831615 | 4589fa2cf5afd15fb19aca96c15b5fbf885d11cf | 11 | medium | [
{
"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... | |
facebook/react | 35,616 | Fix typos: occured->occurred, teh->the, accomodate->accommodate | Fixed spelling errors in comments and error messages:
- Fixed 'occured' -> 'occurred' in ReactAsyncActions-test.js
- Fixed 'teh' -> 'the' in ReactFiberConfigDOM.js
- Fixed 'occured' -> 'occurred' in ErrorBoundary.js
- Fixed 'accomodate' -> 'accommodate' in InferMutationAliasingEffects.ts
<!--
Thanks for submi... | null | 80b1cab397764f83efb9828563a259c8052ded0c | null | low | [
{
"filename": "packages/react-devtools-shared/src/devtools/views/ErrorBoundary/ErrorBoundary.js",
"patch": "@@ -156,7 +156,7 @@ export default class ErrorBoundary extends Component<Props, State> {\n <CaughtErrorView\n callStack={callStack}\n componentStack={componentStack}\... |
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/se... | c8e0878814b4d19200d65571d3d2d35b4b48fd3e | 4bc2728047b119984e5d36f290a09dcdb0a681eb | 3 | high | [
{
"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
}
] |
nodejs/node | 61,712 | deps: V8: cherry-pick 64b36b441179 | Cherry-picks V8 commit [`64b36b441179`](https://github.com/v8/v8/commit/64b36b44117949fe03df33d077117e7bd6257669) (ASCII fast path optimization in `WriteUtf8V2`).
This optimizes the `WriteUtf8V2` path for ASCII-only one-byte strings by using SIMD-accelerated validation (`simdutf::validate_ascii`) followed by a bulk `m... | null | 6682787d687c1fdeeb69740abcb4a25bb6628b66 | null | low | [
{
"filename": "deps/v8/src/strings/unicode-inl.h",
"patch": "@@ -206,6 +206,16 @@ bool Utf8::IsValidCharacter(uchar c) {\n c != kBadChar);\n }\n \n+template <>\n+bool Utf8::IsAsciiOneByteString<uint8_t>(const uint8_t* buffer, size_t size) {\n+ return simdutf::validate_ascii(reinterpret_cast<const... |
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 refer... | 036ed1b9b50558907789c66b407a6cd05d31cc20 | 49d5fd5a3e1a4b4ffc5c232621e98f2dd450fb99 | 4 | medium | [
{
"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... |
nodejs/node | 62,162 | inspector: return errors when CDP protocol event emission fails | Previously, there was no feedback when functions that emit events such as `Network.webSocketCreated` failed. This change modifies the behavior so that feedback can be obtained when such failures occur.
Since an event may be emitted to multiple sessions, instead of throwing an error directly, the errors are returned ... | d93935bf72a18ead8f35dc32f31746b96c4b970e | 4f08c6478d6ecd073c03536b8a6c473232e16c37 | 1 | medium | [
{
"filename": "src/inspector/dom_storage_agent.cc",
"patch": "@@ -17,18 +17,26 @@ using v8::Local;\n using v8::Object;\n using v8::Value;\n \n+static void ThrowEventError(v8::Isolate* isolate, const std::string& message) {\n+ isolate->ThrowException(v8::Exception::TypeError(\n+ v8::String::NewFromUtf8... |
huggingface/transformers | 42,428 | logic to select tf32 API as per Pytorch version | What does this PR do?
The ask is to use fp32_precision instead of allow_tf32 for
Pytorch version >= 2.9.0 for CUDA
as pointed out in this [doc](https://docs.pytorch.org/docs/main/notes/cuda.html#tensorfloat-32-tf32-on-ampere-and-later-devices) mentioned in the https://github.com/huggingface/transformers/issues/42371... | null | 7f5c20945a97ed960eb85d96b93c89f33772fd20 | null | low | [
{
"filename": "conftest.py",
"patch": "@@ -31,6 +31,7 @@\n patch_testing_methods_to_collect_info,\n patch_torch_compile_force_graph,\n )\n+from transformers.utils import enable_tf32\n \n \n NOT_DEVICE_TESTS = {\n@@ -137,11 +138,9 @@ def check_output(self, want, got, optionflags):\n doctest.DocTestPa... |
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. | bb0c58e13416574813361d27ddf4699bf24d3090 | 3cd2b03a5e81f39b132ccd95b8b250f158f97981 | 2 | medium | [
{
"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,660 | Avoid creating async return opaques for foreign async fns | Fixes https://github.com/rust-lang/rust/issues/146754
Previously, def collection created the desugared async return opaque for foreign `async fn` items, but AST lowering won't lower that opaque for foreign items. That left a `DefId` without a corresponding HIR owner, which later caused an ICE during analysis. | null | ce8a3e0a85c98020b199813305faf65e3922c86d | null | low | [
{
"filename": "compiler/rustc_resolve/src/def_collector.rs",
"patch": "@@ -209,12 +209,15 @@ impl<'a, 'ra, 'tcx> visit::Visitor<'a> for DefCollector<'a, 'ra, 'tcx> {\n fn visit_fn(&mut self, fn_kind: FnKind<'a>, _: &AttrVec, span: Span, _: NodeId) {\n match fn_kind {\n FnKind::Fn(\n-... |
electron/electron | 50,704 | ci: fetch clang-tidy package in fix-sync | `fix-sync` re-downloads `llvm-build` on macOS/Windows with the base `clang` and `objdump` packages, but not `clang-tidy`. A local `gclient sync` does pull `clang-tidy` (Electron's DEPS sets `checkout_clang_tidy: True`), so CI's `llvm-build` tree ends up missing a file that a local checkout has.
siso uploads the whole ... | null | 903e65e0486ee1506c9f55dfbd62bf10c96d877d | null | low | [
{
"filename": ".github/actions/fix-sync/action.yml",
"patch": "@@ -27,6 +27,7 @@ runs:\n python3 src/tools/clang/scripts/update.py\n # Refs https://chromium-review.googlesource.com/c/chromium/src/+/6667681\n python3 src/tools/clang/scripts/update.py --package objdump\n+ python... |
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 | 96b202d34b82d1755887bf4204e1f2e053720d4f | c8e0878814b4d19200d65571d3d2d35b4b48fd3e | 5 | medium | [
{
"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
}
] |
rust-lang/rust | 154,777 | `#[cfg]`: suggest alternative `target_` name when the value does not match | <!-- homu-ignore:start -->
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rust/pull/154777)*
<!-- homu-ignore:end -->
<!-- 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... | 65b88ea8ee499345aa8414f16d6cf018c6bdaed6 | cbe9c4deea5060e71d524dfdf310cac052bd8ad3 | 8 | medium | [
{
"filename": "compiler/rustc_lint/src/early/diagnostics/check_cfg.rs",
"patch": "@@ -316,9 +316,27 @@ pub(super) fn unexpected_cfg_value(\n let is_from_cargo = rustc_session::utils::was_invoked_from_cargo();\n let is_from_external_macro = name_span.in_external_macro(sess.source_map());\n \n- // ... |
vercel/next.js | 92,135 | Restart the `next dev` server if `.next` is deleted | This PR is AI generated.
If this directory is deleted while the dev server is running, we can't reasonably recover, so we should restart the process.
Addresses https://vercel.slack.com/archives/C03KAR5DCKC/p1774757692640999 | null | 35f26a2fac583b84baee785d680e4acf0a217b34 | null | low | [
{
"filename": "packages/next/src/server/lib/start-server.ts",
"patch": "@@ -524,32 +524,57 @@ export async function startServer(\n server.listen(port, hostname)\n })\n \n+ // Watch config files for changes and distDir ancestors for deletion.\n if (isDev) {\n- function watchConfigFiles(\n- d... |
huggingface/transformers | 45,252 | Fix unexpected TF32 being enabled in testing | # What does this PR do?
#43166 used `torch.set_float32_matmul_precision("high")` which causes (likely) TF32 being used
> “high”, float32 matrix multiplications either use the TensorFloat32 datatype (10 mantissa bits explicitly stored) or treat each float32 number as the sum of two bfloat16 numbers (approximately ... | null | 374d44d54adb1c5f52e68aff97d1675f56d657a8 | null | low | [
{
"filename": "tests/models/youtu/test_modeling_youtu.py",
"patch": "@@ -33,7 +33,7 @@\n if is_torch_available():\n import torch\n \n- torch.set_float32_matmul_precision(\"high\")\n+ torch.set_float32_matmul_precision(\"highest\")\n \n from transformers import (\n Cache,\n@@ -99,7 +99,... |
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 chi... | null | 9627b5a1caa64c1488643bffdf04495106fa3247 | null | low | [
{
"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... |
nodejs/node | 61,674 | async_hooks: add using scopes to AsyncLocalStorage | Adds support for `using scope = storage.withScope(data)` to do the equivalent of a `storage.run(data, fn)` with using syntax. This enables avoiding unnecessary closures.
cc @nodejs/diagnostics | null | 5b6091ce31068e1c86f863273cdd397ecb47e3b7 | null | low | [
{
"filename": "doc/api/async_context.md",
"patch": "@@ -386,6 +386,110 @@ try {\n }\n ```\n \n+### `asyncLocalStorage.withScope(store)`\n+\n+<!-- YAML\n+added: REPLACEME\n+-->\n+\n+> Stability: 1 - Experimental\n+\n+* `store` {any}\n+* Returns: {RunScope}\n+\n+Creates a disposable scope that enters the give... |
electron/electron | 50,725 | ci: fetch clang-tidy package in fix-sync | Backport of #50704
See that PR for details.
Notes: none | null | 0f4ae991d41e9466f1795b99c75931623a52b863 | null | low | [
{
"filename": ".github/actions/fix-sync/action.yml",
"patch": "@@ -27,6 +27,7 @@ runs:\n python3 src/tools/clang/scripts/update.py\n # Refs https://chromium-review.googlesource.com/c/chromium/src/+/6667681\n python3 src/tools/clang/scripts/update.py --package objdump\n+ python... |
facebook/react | 35,701 | Fix typos in comments | <!--
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 ... | c0d218f0f3e02ed581f74096e56baa947213135d | f944b4c5352be02623d2d7415c0806350f875114 | 6 | medium | [
{
"filename": "packages/react-dom-bindings/src/client/ReactFiberConfigDOM.js",
"patch": "@@ -4062,7 +4062,7 @@ export function registerSuspenseInstanceRetry(\n instance.data !== SUSPENSE_PENDING_START_DATA ||\n // The boundary is still in pending status but the document has finished loading\n //... |
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 | null | bb0c58e13416574813361d27ddf4699bf24d3090 | null | low | [
{
"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/... |
vercel/next.js | 91,693 | turbopack: move "compact database" tracing span to backend layer | ### What?
Move the `"compact database"` tracing span from `turbo-persistence` (`db.rs`) to the backend layer (`turbo-tasks-backend/src/backend/mod.rs`), make it a root span, group it with the sibling `"persist"` span under a shared `"background snapshot"` root, and emit one span per compaction session rather than one ... | 8e9f9514c494ef90fd6d453f4c95884aba287d15 | 47230b12d4b18c599a5955d925028383d0bad5bf | 7 | medium | [
{
"filename": "turbopack/crates/turbo-persistence/src/db.rs",
"patch": "@@ -574,7 +574,7 @@ impl<S: ParallelScheduler, const FAMILIES: usize> TurboPersistence<S, FAMILIES>\n \n new_meta_files.sort_unstable_by_key(|(seq, _)| *seq);\n \n- let sync_span = tracing::info_span!(\"sync new files\").... |
facebook/react | 35,621 | Fix typos: explicitlyu->explicitly, intialized->initialized | Fixed spelling errors:
- Fixed 'explicitlyu' -> 'explicitly' in compiler/CLAUDE.md
- Fixed 'intialized' -> 'initialized' in InferReactiveScopeVariables.ts (comment)
- Fixed 'intialized' -> 'initialized' in InferMutationAliasingEffects.ts (error message)
<!--
Thanks for submitting a pull request!
We apprecia... | ba833da405d44260e94bd47c13eec90816bf44f1 | 2233b7d7281fea5beec815cf5af9593d2b80f68d | 1 | medium | [
{
"filename": "compiler/CLAUDE.md",
"patch": "@@ -76,7 +76,7 @@ yarn snap minimize --update <path>\n \n ## Version Control\n \n-This repository uses Sapling (`sl`) for version control. Sapling is similar to Mercurial: there is not staging area, but new/deleted files must be explicitlyu added/removed.\n+This... |
ollama/ollama | 15,254 | model/parsers: fix gemma4 arg parsing when quoted strings contain " | Fixes: #15241 | 96b202d34b82d1755887bf4204e1f2e053720d4f | 036ed1b9b50558907789c66b407a6cd05d31cc20 | 3 | medium | [
{
"filename": "model/parsers/gemma4.go",
"patch": "@@ -345,27 +345,85 @@ func parseGemma4ToolCall(content string) (api.ToolCall, error) {\n \n // gemma4ArgsToJSON converts Gemma 4's custom argument format to valid JSON.\n func gemma4ArgsToJSON(s string) string {\n-\ts = strings.ReplaceAll(s, `<|\"|>`, `\"`)... |
vercel/next.js | 91,713 | turbo-persistence: remove Unmergeable mmap advice | ### What?
Remove the `MADV_UNMERGEABLE` (Unmergeable) mmap advice from `turbo-persistence`'s `advise_mmap_for_persistence` helper in `mmap_helper.rs`.
### Why?
The WSL (Windows Subsystem for Linux) kernel does not support `MADV_UNMERGEABLE` and returns an error when it is applied, causing turbo-persistence to fail o... | 8e9f9514c494ef90fd6d453f4c95884aba287d15 | df886d4a2d36b63717f8aa5eae1147811ad025f8 | 6 | medium | [
{
"filename": "turbopack/crates/turbo-persistence/src/mmap_helper.rs",
"patch": "@@ -2,15 +2,11 @@\n ///\n /// - `DontFork`: prevents mmap regions from being copied into child processes on `fork()`, avoiding\n /// unnecessary memory duplication and potential SIGBUS.\n-/// - `Unmergeable`: opts pages out o... |
nodejs/node | 62,460 | src: add contextify interceptor debug logs | Add debug logs to help investigate vm interceptor call order issues like
https://github.com/nodejs/node/pull/61898#issuecomment-4142811603
The format of the V8 values are conditional by the presence of
`NODE_DEBUG_NATIVE`. So these values are not always converted to c++
values by utilizing `per_process::Debug` de... | b411f904135bee50ddd1658719ede70db991579f | e7759896bc2d4ad5f91d184bf62f30c7302ba910 | 19 | medium | [
{
"filename": "src/debug_utils-inl.h",
"patch": "@@ -62,6 +62,25 @@ struct ToStringHelper {\n static std::string Convert(const std::string& value) { return value; }\n static std::string_view Convert(std::string_view value) { return value; }\n static std::string Convert(bool value) { return value ? \"t... |
End of preview. Expand in Data Studio
GitHub Issues + Fixes Dataset
A curated, high-signal dataset of GitHub issues collected from 25 popular open-source repositories.
Each example pairs a real GitHub issue with the exact code changes (diffs) that resolved it.
The dataset is designed for:
- Automated bug fixing
- LLM-based code agents
- Issue → patch generation
- Program repair research
How the data was extracted
The data was collected using the GitHub REST API and processed into a structured format.
To maintain quality and usefulness:
- Only closed issues were considered
- Each issue must have a clearly associated fix
- Fixes are stored as unified diffs extracted from the resolving commit
- Low-signal issues (questions, duplicates, discussions) were filtered out
- Issues without meaningful code changes were excluded
Each row represents one issue–fix pair.
Dataset structure
Each dataset entry has the following schema:
{
"repo": "owner/repository",
"issue_number": 12345,
"issue_title": "Short description of the problem",
"issue_body": "Full issue discussion and problem description",
"commit_sha": "abcdef123456...",
"files": [
{
"filename": "path/to/file.ext",
"patch": "unified diff showing the fix",
"additions": 10,
"deletions": 2
}
]
}
| Field | Description |
|---|---|
repo |
GitHub repository where the issue originated |
issue_number |
Original GitHub issue number |
issue_title |
Title of the issue |
issue_body |
Full issue description and context |
commit_sha |
Commit that fixed the issue |
files |
List of modified files |
files[].filename |
Path of the modified file |
files[].patch |
Unified diff representing the fix |
files[].additions |
Number of added lines |
files[].deletions |
Number of removed lines |
Supported languages
The dataset contains fixes across multiple programming languages, including (but not limited to):
- C / C++
- Python
- JavaScript / TypeScript
- Rust
- Go
- Java
- Assembly (very rare)
Language distribution varies by repository.
Intended use cases
This dataset is well-suited for:
- Training models to generate code patches from issue descriptions
- Evaluating LLM reasoning over real-world bug reports
- Building autonomous debugging or refactoring agents
- Research on program repair, code synthesis, and software maintenance
It is not intended for:
- Issue classification
- sentiment analysis
- Chatbot fine-tuning without code generation
Limitations
- The dataset reflects real-world noise from GitHub issues
- Issue descriptions vary widely in clarity and detail
- Some fixes involve refactoring or design changes rather than minimal patches
- No guarantee that all fixes are optimal or best practice
Warning: This dataset currently has the issues of 10/25 repos and 14k rows but is expected to have 50k rows and 2 GB in size
- Downloads last month
- 69