Datasets:
sample_id string | source string | annotation_level string | split string | query string | query_context string | known_context_document_ids list | reference_answer string | answer_document_id string | silver_evidence_path list | evidence_issue_ids list | source_repo_name string | source_issue_id int64 | source_issue_number int64 | source_issue_url string | target_repo_name string | target_issue_id int64 | target_issue_number int64 | target_issue_url string | reference_anchor_document_id string | reference_answer_author string | reference_answer_author_association string | quality_score float64 | quality_details dict | issue_created_at timestamp[s] | valid_comment_count int64 | fragments list | human_reviewed bool |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
cross_issue_0003 | OpenDigger-GHArchive-Cross-Issue | silver | dev | [Epic] Horizontally scalable request layer (e.g. `pgwired`)? | At the moment, all communication from clients goes through `environmentd`, which maintains the catalog, performs optimization, sends requests to `clusterd`, and passes results back to the client. Both data and control are multiplexed on the same connection.
The result of this multiplexing is
* increased effort for `en... | [
"gh_issue_1358985263"
] | from @ georgewfraser (thanks!), lightly edited and shared with permission:
You can get most of Fivetran's commands if you set up postgres as a source (henceforth, "upstreamdb") and set up a new postgres database as a destination (henceforth, "downstreamdb"). Instrument downstreamdb with statement level logging and do ... | gh_comment_755764601 | [
"gh_comment_1242851542",
"gh_issue_778157642",
"gh_comment_755764601"
] | [
1358985263,
778157642
] | MaterializeInc/materialize | 1,358,985,263 | 14,568 | https://github.com/MaterializeInc/materialize/issues/14568 | MaterializeInc/materialize | 778,157,642 | 5,188 | https://github.com/MaterializeInc/materialize/issues/5188 | gh_comment_1242851542 | rjnn | MEMBER | 94.15 | {
"explicit_cross_issue_reference": true,
"resolution_cue": true,
"technical_cue": true,
"anchor_query_overlap": 0.0769,
"anchor_target_overlap": 0.2692,
"target_answer_overlap": 0.25
} | 2022-09-01T06:56:50 | 6 | [
{
"document_id": "gh_issue_1358985263",
"fragment_type": "issue_description",
"sequence": 0,
"text": "[Epic] Horizontally scalable request layer (e.g. `pgwired`)\nAt the moment, all communication from clients goes through `environmentd`, which maintains the catalog, performs optimization, sends requ... | false |
cross_issue_0020 | OpenDigger-GHArchive-Cross-Issue | silver | dev | External hostname is not updated if an ingress is added *after* relating a charm to Prometheus? | ### Bug Description
See title. If you first relate to Prometheus and then to Traefik, it all works as expected. The other way around, no cigar.
### To Reproduce
-
### Environment
-
### Relevant log output
shell
-
### Additional context
We could have used the ingress established/revoked events, but these are un... | [
"gh_issue_1381005452"
] | So basically, what I think would make sense here:
An optional argument, per consumer, to turn path-prefix-stripping on and off. It should take whatever path prefix it is using for that route and add it to the middleware's list of path's to strip. As an example:
- Jon is instantiating the traefik consumer in his `zinc... | gh_comment_1265451573 | [
"gh_comment_1277474331",
"gh_issue_1207565669",
"gh_comment_1265451573"
] | [
1381005452,
1207565669
] | canonical/prometheus-k8s-operator | 1,381,005,452 | 368 | https://github.com/canonical/prometheus-k8s-operator/issues/368 | canonical/traefik-k8s-operator | 1,207,565,669 | 45 | https://github.com/canonical/traefik-k8s-operator/issues/45 | gh_comment_1277474331 | simskij | MEMBER | 88 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.1351,
"anchor_target_overlap": 0.2273,
"target_answer_overlap": 0.1321
} | 2022-09-21T06:13:02 | 14 | [
{
"document_id": "gh_issue_1381005452",
"fragment_type": "issue_description",
"sequence": 0,
"text": "External hostname is not updated if an ingress is added *after* relating a charm to Prometheus\n### Bug Description\n\nSee title. If you first relate to Prometheus and then to Traefik, it all works ... | false |
cross_issue_0027 | OpenDigger-GHArchive-Cross-Issue | silver | dev | [Question] longhorn-conversion-webhook container not starting error, failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: eaccess /usr/local/sbin/longhorn-manager: permission denied: unknown? | **Question:**
I am open this as Question, because this is my first Longhorn storage installation on Kubernetes cluster (Multi Master HA setup), Feels like issue with some container permission while accessing /usr/local/sbin/longhorn-manager while provisioning container.
after applying the longhorn.yaml version v1.3.2,... | [
"gh_issue_1749022121"
] | You can manually hide the private information, or you can send the support bundle to longhorn-support-bundle@suse.com which is only accessible by Longhorn members. | gh_comment_2176532828 | [
"gh_comment_2176162185",
"gh_issue_2359706899",
"gh_comment_2176532828"
] | [
1749022121,
2359706899
] | longhorn/longhorn | 1,749,022,121 | 6,090 | https://github.com/longhorn/longhorn/issues/6090 | longhorn/longhorn | 2,359,706,899 | 8,780 | https://github.com/longhorn/longhorn/issues/8780 | gh_comment_2176162185 | derekbit | MEMBER | 94.85 | {
"explicit_cross_issue_reference": true,
"resolution_cue": true,
"technical_cue": true,
"anchor_query_overlap": 0.375,
"anchor_target_overlap": 0.375,
"target_answer_overlap": 0.0769
} | 2023-06-08T19:02:29 | 14 | [
{
"document_id": "gh_issue_1749022121",
"fragment_type": "issue_description",
"sequence": 0,
"text": "[Question] longhorn-conversion-webhook container not starting error, failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start cont... | false |
cross_issue_0036 | OpenDigger-GHArchive-Cross-Issue | silver | dev | error message using this step? | Hi,
I set this first step in our workflow:
- name: Cancel Previous Runs
uses: styfle/cancel-workflow-action@0.11.0
I did 2 pushes (first, and second) one after another to check how it works.
I see this message in the logs:
`Error while canceling workflow_id 5888667: Resource not accessible by integration`
Why did ... | [
"gh_issue_1528923107"
] | Makes sense, as long as we can provide examples for each of the `Advanced:` use cases in the readme.
Would you like to submit a PR? | gh_comment_1316300915 | [
"gh_comment_1379695924",
"gh_issue_1448551601",
"gh_comment_1316300915"
] | [
1528923107,
1448551601
] | styfle/cancel-workflow-action | 1,528,923,107 | 200 | https://github.com/styfle/cancel-workflow-action/issues/200 | styfle/cancel-workflow-action | 1,448,551,601 | 191 | https://github.com/styfle/cancel-workflow-action/issues/191 | gh_comment_1379695924 | styfle | OWNER | 82.09 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.1034,
"anchor_target_overlap": 0.087,
"target_answer_overlap": 0
} | 2023-01-11T04:08:12 | 7 | [
{
"document_id": "gh_issue_1528923107",
"fragment_type": "issue_description",
"sequence": 0,
"text": "error message using this step\nHi,\nI set this first step in our workflow:\n\n - name: Cancel Previous Runs\n uses: styfle/cancel-workflow-action@0.11.0\n\nI did 2 pushes (first, and second) one aft... | false |
cross_issue_0042 | OpenDigger-GHArchive-Cross-Issue | silver | dev | [image_picker] image_picker: ^1.0.7 image revert issue in IOS? | ### Steps to reproduce
1. get the image from library/gallery or capture it from camera(only front camera)
2. select and show it
3. all images are inverted like a mirror in IOS devices only are inverted
### Expected results
The image must be the same as placed in the gallery or captured by camera using the front came... | [
"gh_issue_2242954070"
] | When taking selfie in native camera at on Android devices, they are correcting the mirror effect, this is a useful feature to be baked into the `camera` package instead of modifing the image using `Transform` widget
Thanks for the issue! | gh_comment_789551119 | [
"gh_comment_2063059413",
"gh_issue_407865675",
"gh_comment_789551119"
] | [
2242954070,
407865675
] | flutter/flutter | 2,242,954,070 | 146,751 | https://github.com/flutter/flutter/issues/146751 | flutter/flutter | 407,865,675 | 27,650 | https://github.com/flutter/flutter/issues/27650 | gh_comment_2063059413 | TahaTesser | MEMBER | 88 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.2105,
"anchor_target_overlap": 0.1579,
"target_answer_overlap": 0.2667
} | 2024-04-14T23:46:19 | 72 | [
{
"document_id": "gh_issue_2242954070",
"fragment_type": "issue_description",
"sequence": 0,
"text": "[image_picker] image_picker: ^1.0.7 image revert issue in IOS\n### Steps to reproduce\n\n1. get the image from library/gallery or capture it from camera(only front camera)\n2. select and show it\n3.... | false |
cross_issue_0045 | OpenDigger-GHArchive-Cross-Issue | silver | dev | residual and capacity do not have the value returned by the API? | ### Mark
Peugeot
### Model
e208
### Year
2020
### Engine
Electric
### Remote service
E-remote control
### HomeAssistant version
last
### Integration version
last
### What happened?
Hi, I think there is a problem with the display of battery capacity and remaining values.
the percentage does not correspond... | [
"gh_issue_3333286707"
] | Unfortunally stellantis dont provide the specific type of hybrid.
The only way is to remove capacity and residual for all hybrids on next release. | gh_comment_3012288415 | [
"gh_comment_3207555401",
"gh_issue_3171387380",
"gh_comment_3012288415"
] | [
3333286707,
3171387380
] | andreadegiovine/homeassistant-stellantis-vehicles | 3,333,286,707 | 264 | https://github.com/andreadegiovine/homeassistant-stellantis-vehicles/issues/264 | andreadegiovine/homeassistant-stellantis-vehicles | 3,171,387,380 | 208 | https://github.com/andreadegiovine/homeassistant-stellantis-vehicles/issues/208 | gh_comment_3207555401 | andreadegiovine | OWNER | 88 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.1818,
"anchor_target_overlap": 0.1818,
"target_answer_overlap": 0.3125
} | 2025-08-18T23:42:58 | 8 | [
{
"document_id": "gh_issue_3333286707",
"fragment_type": "issue_description",
"sequence": 0,
"text": "residual and capacity do not have the value returned by the API\n### Mark\n\nPeugeot\n\n### Model\n\ne208\n\n### Year\n\n2020\n\n### Engine\n\nElectric\n\n### Remote service\n\nE-remote control\n\n#... | false |
cross_issue_0048 | OpenDigger-GHArchive-Cross-Issue | silver | dev | Receive from dashboard? | As a fast-follow for send, we need to design a way to handle "Send" & "Receive" as global action.
This issue is about the Receive part that is delivered separately.
AC:
- User is able to trigger receive from homepage
- User is able to choose or create new account for receiving
Designs: URL | [
"gh_issue_2770798238"
] | Missing Cardano Send feature is something that has to be handled here. And even if we unblock the ADA send and implemented, it will probably be available only on 2.8.7 FW and not older (since the ADA send flow has been changed in that version). URL | gh_comment_2603965598 | [
"gh_comment_2603958190",
"gh_issue_2801051938",
"gh_comment_2603965598"
] | [
2770798238,
2801051938
] | trezor/trezor-suite | 2,770,798,238 | 16,204 | https://github.com/trezor/trezor-suite/issues/16204 | trezor/trezor-suite | 2,801,051,938 | 16,484 | https://github.com/trezor/trezor-suite/issues/16484 | gh_comment_2603958190 | matejkriz | MEMBER | 88 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.625,
"anchor_target_overlap": 0.5,
"target_answer_overlap": 0.15
} | 2025-01-06T06:37:29 | 6 | [
{
"document_id": "gh_issue_2770798238",
"fragment_type": "issue_description",
"sequence": 0,
"text": "Receive from dashboard\nAs a fast-follow for send, we need to design a way to handle \"Send\" & \"Receive\" as global action.\nThis issue is about the Receive part that is delivered separately.\n\nA... | false |
cross_issue_0063 | OpenDigger-GHArchive-Cross-Issue | silver | dev | None or multiple MFA types potentially break login flow? | This needs investigation to replicate, but there is a possiblity that if:
A user has no MFA setup on their amazon account, they will be prompted to set it up after a successful login. Which breaks the flow.
A user has multiple forms of MFA setup on their amazon account, they might be presented with a different versio... | [
"gh_issue_2769061212"
] | @mmstano when you say you cleared cookies and history - I meant the ones the server application (the add-on) stores, not your browsers. Perhaps a misunderstanding there because I said cookies, because that's what I called one of the files it generates haha. Probably a poor choice of words on my part.
I'm not sure if H... | gh_comment_2587420635 | [
"gh_comment_2585955674",
"gh_issue_2769203934",
"gh_comment_2587420635"
] | [
2769061212,
2769203934
] | madmachinations/home-assistant-alexa-shopping-list | 2,769,061,212 | 37 | https://github.com/madmachinations/home-assistant-alexa-shopping-list/issues/37 | madmachinations/home-assistant-alexa-shopping-list | 2,769,203,934 | 39 | https://github.com/madmachinations/home-assistant-alexa-shopping-list/issues/39 | gh_comment_2585955674 | madmachinations | OWNER | 82.86 | {
"explicit_cross_issue_reference": true,
"resolution_cue": false,
"technical_cue": true,
"anchor_query_overlap": 0.0357,
"anchor_target_overlap": 0.2667,
"target_answer_overlap": 0.1625
} | 2025-01-04T16:55:20 | 20 | [
{
"document_id": "gh_issue_2769061212",
"fragment_type": "issue_description",
"sequence": 0,
"text": "None or multiple MFA types potentially break login flow\nThis needs investigation to replicate, but there is a possiblity that if:\n\nA user has no MFA setup on their amazon account, they will be pr... | false |
cross_issue_0066 | OpenDigger-GHArchive-Cross-Issue | silver | dev | Canonical URL not added with default configuration? | "With a new install of the Metatag 1.22.5 and default settings...\n\nUnder \"Advanced Tags\" for \"G(...TRUNCATED) | [
"gh_issue_1631050458"
] | "I checked metatag's handling of `#attached` and it looks like it already works correctly. There was(...TRUNCATED) | gh_comment_1773517917 | [
"gh_comment_1749924386",
"gh_issue_1929309320",
"gh_comment_1773517917"
] | [
1631050458,
1929309320
] | backdrop-contrib/metatag | 1,631,050,458 | 109 | https://github.com/backdrop-contrib/metatag/issues/109 | backdrop-contrib/metatag | 1,929,309,320 | 110 | https://github.com/backdrop-contrib/metatag/issues/110 | gh_comment_1749924386 | quicksketch | MEMBER | 96 | {"explicit_cross_issue_reference":true,"resolution_cue":true,"technical_cue":true,"anchor_query_over(...TRUNCATED) | 2023-03-19T09:54:24 | 12 | [{"document_id":"gh_issue_1631050458","fragment_type":"issue_description","sequence":0,"text":"Canon(...TRUNCATED) | false |
cross_issue_0068 | OpenDigger-GHArchive-Cross-Issue | silver | dev | SchemaOf returns undefined-able type for a required array? | "I need to verify that my schema match array of strings, so I use [`yup.SchemaOf `]( URL but when I (...TRUNCATED) | [
"gh_issue_1486753151"
] | Yes, strict nulls is a required typescript setting for types to work, as mentioned in the docs | gh_comment_1704320561 | [
"gh_comment_1419298740",
"gh_issue_916934899",
"gh_comment_1704320561"
] | [
1486753151,
916934899
] | jquense/yup | 1,486,753,151 | 1,853 | https://github.com/jquense/yup/issues/1853 | jquense/yup | 916,934,899 | 1,389 | https://github.com/jquense/yup/issues/1389 | gh_comment_1419298740 | jquense | OWNER | 88 | {"explicit_cross_issue_reference":true,"resolution_cue":false,"technical_cue":true,"anchor_query_ove(...TRUNCATED) | 2022-12-09T05:20:38 | 6 | [{"document_id":"gh_issue_1486753151","fragment_type":"issue_description","sequence":0,"text":"Schem(...TRUNCATED) | false |
End of preview. Expand in Data Studio
YAML Metadata Warning:The task_categories "information-retrieval" is not in the official list: text-classification, token-classification, table-question-answering, question-answering, zero-shot-classification, translation, summarization, feature-extraction, text-generation, fill-mask, sentence-similarity, text-to-speech, text-to-audio, automatic-speech-recognition, audio-to-audio, audio-classification, audio-text-to-text, voice-activity-detection, depth-estimation, image-classification, object-detection, image-segmentation, text-to-image, image-to-text, image-to-image, image-to-video, unconditional-image-generation, video-classification, reinforcement-learning, robotics, tabular-classification, tabular-regression, tabular-to-text, table-to-text, multiple-choice, text-ranking, text-retrieval, time-series-forecasting, text-to-video, image-text-to-text, image-text-to-image, image-text-to-video, visual-question-answering, document-question-answering, zero-shot-image-classification, graph-ml, mask-generation, zero-shot-object-detection, text-to-3d, image-to-3d, image-feature-extraction, video-text-to-text, keypoint-detection, visual-document-retrieval, any-to-any, video-to-video, other
MetaRAG Cross-Issue OSSQA
Dataset page: https://huggingface.co/datasets/MapleBi/MetaRAG_Cross-Issue_OSSQA
MetaRAG Cross-Issue OSSQA is an English open-source software issue question-answering and retrieval benchmark. Each example asks a question grounded in one GitHub issue and requires evidence from a related issue. The data contains explicit cross-issue references and a three-document silver evidence path.
Dataset configurations
| Configuration | Splits | Rows | Purpose |
|---|---|---|---|
default |
dev, test |
100 / 400 | Complete evaluation records, including embedded issue fragments and silver labels. |
queries |
dev, test |
100 / 400 | Retrieval and QA queries with answer and evidence-path supervision. |
corpus |
corpus |
9,536 | Deduplicated issue-description and issue-comment fragments for retrieval. This is a knowledge corpus, not a training split. |
Loading
from datasets import load_dataset
evaluation = load_dataset("MapleBi/MetaRAG_Cross-Issue_OSSQA")
queries = load_dataset("MapleBi/MetaRAG_Cross-Issue_OSSQA", "queries")
corpus = load_dataset("MapleBi/MetaRAG_Cross-Issue_OSSQA", "corpus", split="corpus")
Main fields
default includes the query, its known context, answer, source and target issue metadata, silver_evidence_path, quality signals, and the ordered fragments supporting each example. queries is the compact query-level representation. corpus contains one searchable fragment per document_id, plus issue, repository, author, timestamp, and cross-issue-link metadata.
The fields answer_document_id and silver_evidence_path refer to corpus.document_id. known_context_document_ids identifies documents supplied as query context; these are excluded from the gold evidence path. split is repository-disjoint between dev and test.
Data creation
The dataset was constructed from public GitHub event data via OpenDigger / GH Archive, from 2022-01-01 through 2025-12-31. It contains 500 qualified cross-issue samples from 468 repositories. The sampling procedure requires an explicit cross-issue reference, a path spanning at least two distinct issues, English-language filtering, deterministic diversity sampling, and repository-disjoint development/test partitions.
See dataset_statistics.json for the complete sampling settings, quality distribution, year distribution, and leakage audit result.
Labels and limitations
reference_answer and silver_evidence_path are heuristic silver annotations. They should not be treated as human-validated gold labels without additional review. Source text may contain stale links, personal identifiers visible in public GitHub content, inaccurate technical claims, or other artifacts of public issue discussions.
The data is intended for research and evaluation. Users are responsible for ensuring their use complies with the applicable GitHub Terms of Service, the source platforms' policies, and their own privacy, legal, and ethical requirements.
Provenance
- OpenDigger: https://github.com/X-lab2017/open-digger
- GH Archive: https://www.gharchive.org/
Repository integrity
MANIFEST.sha256 contains SHA-256 checksums for every data file and dataset_statistics.json in this package. To regenerate the package from the accompanying source files, remove this output directory and run python3 prepare_hf_dataset.py.
- Downloads last month
- 27