Datasets:
base_commit stringlengths 40 40 | created_at timestamp[s]date 2025-01-01 00:00:00 2025-01-01 00:00:00 | idx int64 735 5.45k | image_info stringlengths 126 217 | instance_id stringlengths 12 72 | modified_entity_summaries stringclasses 1
value | modified_files stringclasses 1
value | num_non_test_files int64 0 0 | num_non_test_func_methods int64 0 0 | num_non_test_lines int64 0 0 | passrate stringclasses 3
values | patch stringlengths 814 13.2M | problem_statement stringlengths 200 93k | repo_name stringlengths 7 67 | test_patch stringlengths 95 9.13M | docker_image stringlengths 48 108 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
39d25d222321e57c66e5dc22bc3fa741f0885760 | 2025-01-01T00:00:00 | 735 | {"remote_user": "root", "project_path": "/workspaces/poseidon", "script_folder": "/root", "remote_workspace_folder": "/workspaces/poseidon"} | openhpi__poseidon-566 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/configuration.example.yaml b/configuration.example.yaml
index 36144fc9..43e65b5c 100644
--- a/configuration.example.yaml
+++ b/configuration.example.yaml
@@ -65,6 +65,14 @@ nomad:
# namespace: poseidon
# Prefer local Docker images over pulling them from a registry. Images with the `latest` tag will a... | #Network access becomes unavailable
An execution environment providing network access first seems to work correctly. However, after some time (and some unknown events), the environment looses the network access. The allocation itself is still running on Nomad, but unfortunately without any possibility to reach the inte... | openHPI/poseidon | diff --git a/internal/environment/nomad_environment_test.go b/internal/environment/nomad_environment_test.go
index ae43d080..dd713197 100644
--- a/internal/environment/nomad_environment_test.go
+++ b/internal/environment/nomad_environment_test.go
@@ -4,6 +4,7 @@ import (
"context"
"fmt"
nomadApi "github.com/hashi... | ghcr.io/jzwilliams07/logics-swe-env:openhpi__poseidon-566 |
b4f017999ff4047f1ca18ed3d3a4aca54919f0f4 | 2025-01-01T00:00:00 | 736 | {"remote_user": "root", "project_path": "/workspaces/relayer", "script_folder": "/root", "remote_workspace_folder": "/workspaces/relayer"} | gonative-cc__relayer-251 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/.gitignore b/.gitignore
index fcddfba8..c03265d5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -29,3 +29,4 @@ contrib/bitcoind-data
contrib/fork-*
e2e-bitcoin-spv.yml
bitcoin-spv
+!cmd/bitcoin-spv/
diff --git a/bitcoinspv/block_events.go b/bitcoinspv/block_events.go
index 817d428e..928be2ca 100644
--- a/b... | #Support sending blocks to Walrus
<!-- markdownlint-disable MD041 -->
## Summary
As a part of the Bitcoin execution node implementation, we need to send Bitcoin blocks to Walrus.
- add a flag `--walrus` (with related values) to bitcoinspv relayer to enable sending full blocks to Walrus.
- implement walrus support.... | gonative-cc/relayer | diff --git a/bitcoinspv/relayer_test.go b/bitcoinspv/relayer_test.go
index ce0fa16a..3ff4d9b9 100644
--- a/bitcoinspv/relayer_test.go
+++ b/bitcoinspv/relayer_test.go
@@ -42,6 +42,7 @@ func setupTest(t *testing.T) (*Relayer, *mocks.MockBTCClient, *mocks.MockBitcoin
logger,
btcClient,
lcClient,
+ nil,
)
re... | ghcr.io/jzwilliams07/logics-swe-env:gonative-cc__relayer-251 |
fcb6a0d4cbc8ab4f1cd130340c96faf0a75d2086 | 2025-01-01T00:00:00 | 737 | {"remote_user": "root", "project_path": "/workspaces/terraform-provider-flexibleengine", "script_folder": "/root", "remote_workspace_folder": "/workspaces/terraform-provider-flexibleengine"} | flexibleenginecloud__terraform-provider-flexibleengine-640 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/docs/resources/mrs_job_v2.md b/docs/resources/mrs_job_v2.md
new file mode 100644
index 000000000..501852994
--- /dev/null
+++ b/docs/resources/mrs_job_v2.md
@@ -0,0 +1,101 @@
+---
+subcategory: "MRS Service (MRS)"
+---
+
+# flexibleengine_mrs_job_v2
+
+Manage a job resource within FlexibleEngine MRS.
+
+##... | #[MRS] Feature request: Terraform to provide Huawei Cloud MRS API v2 sparkSubmit method
Hi there,
### Terraform Version
0.12.20
### Affected Resource(s)
flexibleengine_mrs_cluster_v1
### Important Factoids
Do you have an estimate on when you could provide the sparkSubmit method from Huawei Cloud MRS API... | FlexibleEngineCloud/terraform-provider-flexibleengine | diff --git a/flexibleengine/resource_flexibleengine_mrs_job_v2_test.go b/flexibleengine/resource_flexibleengine_mrs_job_v2_test.go
new file mode 100644
index 000000000..eeaf426e9
--- /dev/null
+++ b/flexibleengine/resource_flexibleengine_mrs_job_v2_test.go
@@ -0,0 +1,152 @@
+package flexibleengine
+
+import (
+ "fmt"
+... | ghcr.io/jzwilliams07/logics-swe-env:flexibleenginecloud__terraform-provider-flexibleengine-640 |
5295e7f2738ea37ce7c8a2adfa08d2aa0c35f317 | 2025-01-01T00:00:00 | 738 | {"remote_user": "root", "project_path": "/workspaces/ts-json-schema-generator", "script_folder": "/root/", "remote_workspace_folder": "/workspaces/ts-json-schema-generator"} | vega__ts-json-schema-generator-1154 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/factory/formatter.ts b/factory/formatter.ts
index 11fb516c2..5bf8753c7 100644
--- a/factory/formatter.ts
+++ b/factory/formatter.ts
@@ -27,6 +27,7 @@ import { UnionTypeFormatter } from "../src/TypeFormatter/UnionTypeFormatter";
import { UnknownTypeFormatter } from "../src/TypeFormatter/UnknownTypeFormatte... | #Support the type "never"
Currently, ts-json-schema-generator doesn't produce anything for the type "never".
The use-case I have is for the type `Record<string, never>`, which is recommended by `typescript-eslint` for when an object has no properties.
Though in general, having support for never wouldn't hurt anyway... | vega/ts-json-schema-generator | diff --git a/test/valid-data-other.test.ts b/test/valid-data-other.test.ts
index 32b6e7ab4..833df917d 100644
--- a/test/valid-data-other.test.ts
+++ b/test/valid-data-other.test.ts
@@ -65,6 +65,9 @@ describe("valid-data-other", () => {
it("undefined-union", assertValidSchema("undefined-union", "MyType"));
it(... | ghcr.io/jzwilliams07/logics-swe-env:vega__ts-json-schema-generator-1154 |
4736fe7092126af436cb0f9edc7fa284b31aa14e | 2025-01-01T00:00:00 | 739 | {"remote_user": "root", "project_path": "/workspaces/magiclinksdev", "script_folder": "/root/", "remote_workspace_folder": "/workspaces/magiclinksdev"} | micahparks__magiclinksdev-5 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/cmd/migrate/main.go b/cmd/migrate/main.go
new file mode 100644
index 0000000..8361c3b
--- /dev/null
+++ b/cmd/migrate/main.go
@@ -0,0 +1,66 @@
+package main
+
+import (
+ "context"
+ "log"
+ "os"
+
+ jt "github.com/MicahParks/jsontype"
+ "go.uber.org/zap"
+
+ mld "github.com/MicahParks/magiclinksdev"
+ "gi... | #Allow API clients to choose which key type to sign JWTs with
Currently, JWTs are only signed with whatever the default key is in the database. Using the default configuration, this is the EdDSA key.
Add an option to all client requests to specify a signing key type for the JWT on a per-request basis. This supports ... | MicahParks/magiclinksdev | diff --git a/config.test.json b/config.test.json
index cca69a3..407a213 100644
--- a/config.test.json
+++ b/config.test.json
@@ -44,7 +44,6 @@
"maxIdle": "4m",
"minConns": 2,
"plaintextClaims": false,
- "plaintextJWK": false,
- "semver": "v0.0.1"
+ "plaintextJWK": false
}
}
diff --git a/magi... | ghcr.io/jzwilliams07/logics-swe-env:micahparks__magiclinksdev-5 |
5142b9da8816df4eb9e9a9b52f7ffbf01648dd6a | 2025-01-01T00:00:00 | 740 | {"remote_user": "root", "project_path": "/workspaces/diki", "script_folder": "/root/", "remote_workspace_folder": "/workspaces/diki"} | gardener__diki-366 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006.go b/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006.go
new file mode 100644
index 000000000..752bd3f61
--- /dev/null
+++ b/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006.go
@@ -0,0 +1,64 @@
+// SPDX-FileCopyrightText: ... | #☂ Implement `Garden` provider & `Security Hardened Shoot Cluster` ruleset
**What would you like to be added**:
A `Garden` provider that has access to the garden cluster can be implemented:
- [X] Add Garden provider https://github.com/gardener/diki/pull/305
A new ruleset should also be created for the `Garden` provide... | gardener/diki | diff --git a/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006_test.go b/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006_test.go
new file mode 100644
index 000000000..a34ad42a5
--- /dev/null
+++ b/pkg/provider/garden/ruleset/securityhardenedshoot/rules/2006_test.go
@@ -0,0 +1,105 @@
+// SPDX-Fil... | ghcr.io/jzwilliams07/logics-swe-env:gardener__diki-366 |
990b287873fb1fadad40959a06d3469dd690145e | 2025-01-01T00:00:00 | 741 | {"remote_user": "root", "project_path": "/workspaces/mcp-server", "script_folder": "/root", "remote_workspace_folder": "/workspaces/mcp-server"} | blockscout__mcp-server-23 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/.env.example b/.env.example
index ae7d238..270eabb 100644
--- a/.env.example
+++ b/.env.example
@@ -8,4 +8,7 @@ BLOCKSCOUT_BS_TIMEOUT=120.0
BLOCKSCOUT_BENS_TIMEOUT=30.0
BLOCKSCOUT_CHAINSCOUT_TIMEOUT=15.0
BLOCKSCOUT_CHAIN_CACHE_TTL_SECONDS=1800
-BLOCKSCOUT_PROGRESS_INTERVAL_SECONDS="15.0"
\ No newline at... | #Enhance `get_address_info` with Address Metadata from Metadata Service
### Description
The current `get_address_info` tool provides essential on-chain data for an address from the Blockscout API. However, it lacks valuable off-chain metadata, such as public tags (e.g., "Arbitrum: Outbox 4"), which are available throu... | blockscout/mcp-server | diff --git a/tests/integration/test_address_tools_integration.py b/tests/integration/test_address_tools_integration.py
index c633e29..fd37f41 100644
--- a/tests/integration/test_address_tools_integration.py
+++ b/tests/integration/test_address_tools_integration.py
@@ -2,6 +2,7 @@
import pytest
from blockscout_mcp_s... | ghcr.io/jzwilliams07/logics-swe-env:blockscout__mcp-server-23 |
a2cdaa2c50f32727a6937d434b8ac8e0d02661b1 | 2025-01-01T00:00:00 | 742 | {"remote_user": "root", "project_path": "/workspaces/griffonner", "script_folder": "/root", "remote_workspace_folder": "/workspaces/griffonner"} | will-langdale__griffonner-29 | [] | [] | 0 | 0 | 0 | 3/7 | diff --git a/src/griffonner/core.py b/src/griffonner/core.py
index 25b479d..e75de74 100644
--- a/src/griffonner/core.py
+++ b/src/griffonner/core.py
@@ -171,6 +171,7 @@ def copy_file_passthrough(
def generate_file(
source_file: Path,
+ source_dir: Path,
output_dir: Path,
template_dirs: Optional[Lis... | #Building to correct directories isn't working as expected
Output directory isn't structured as I'd expect.
In the below example, I'm looking for home.md to be built and passed to the root of `docs/output`. Instead it's being put in `docs/output/pages`.
In short, the root directory of source and target isn't being pr... | will-langdale/griffonner | diff --git a/test/plugins/test_plugins_integration.py b/test/plugins/test_plugins_integration.py
index 269bc0d..aa94461 100644
--- a/test/plugins/test_plugins_integration.py
+++ b/test/plugins/test_plugins_integration.py
@@ -104,6 +104,7 @@ def test_core_generation_with_processors(self, mock_load_griffe):
... | ghcr.io/jzwilliams07/logics-swe-env:will-langdale__griffonner-29 |
00c0fb1ce60001684538262251fee3ed55c05b38 | 2025-01-01T00:00:00 | 743 | "{\"remote_user\": \"root\", \"project_path\": \"/workspaces/metastore-lib-js\", \"script_folder\": (...TRUNCATED) | datopian__metastore-lib-js-12 | [] | [] | 0 | 0 | 0 | 3/7 | "diff --git a/README.md b/README.md\nindex 89b5b0b..b2eedbb 100644\n--- a/README.md\n+++ b/README.md(...TRUNCATED) | "#Generate LFS pointer files before metadata is uploaded to Github Backend\nLFS files (.gitattribute(...TRUNCATED) | datopian/metastore-lib-js | "diff --git a/test/backend/filesystem.js b/test/backend/filesystem.js\nindex afbe7d0..ce04359 100644(...TRUNCATED) | ghcr.io/jzwilliams07/logics-swe-env:datopian__metastore-lib-js-12 |
16eb10d1c5fdb372a669705b54e34bb222b2057b | 2025-01-01T00:00:00 | 744 | "{\"remote_user\": \"root\", \"project_path\": \"/workspaces/PyViCare\", \"script_folder\": \"/root\(...TRUNCATED) | openviess__pyvicare-334 | [] | [] | 0 | 0 | 0 | 3/7 | "diff --git a/PyViCare/PyViCareDeviceConfig.py b/PyViCare/PyViCareDeviceConfig.py\nindex 97a6339a..b(...TRUNCATED) | "#Read WiFi Signal Strength\nHey,\r\n\r\nI've been looking into the code and into the HomeAssistant (...TRUNCATED) | openviess/PyViCare | "diff --git a/tests/response/VitoconnectOpto1.json b/tests/response/VitoconnectOpto1.json\nnew file (...TRUNCATED) | ghcr.io/jzwilliams07/logics-swe-env:openviess__pyvicare-334 |
Logics-SWE-Env-2.5K
2,553 software engineering task instances · 1,771 repositories · 4 programming languages
🤗 Related model: Logics-SWE-Qwen3.6-27B
📄 Paper: One to More, More to One
Overview
What is this dataset?
Logics-SWE-Env-2.5K is a collection of repository-level software engineering tasks for research on coding agents and environment-based reinforcement learning. It contains 2,553 unique task instances from 1,771 GitHub repositories, spanning Go, Python, TypeScript, and JavaScript.
This release is a public subset of the training data used in One to More, More to One: Category-Aware Iterative Expert Training for Software Engineering Agents. It is released as part of the AgenticBigBang project, alongside research on category-aware expert training and multi-teacher on-policy distillation.
Each instance provides a problem statement, the target repository and base revision, a reference code patch, a test patch, and environment-image metadata. These fields support repository-level task setup and test-based verification when used with the corresponding execution environment and runner. This is task and environment data, not an agent-trajectory or SFT demonstration dataset.
Relationship to the paper
The paper One to More, More to One: Category-Aware Iterative Expert Training for Software Engineering Agents develops category experts through Refresh–Repair–Expand (RRE) and integrates them into a single student using multi-teacher on-policy distillation (MOPD). This dataset exposes a subset of the underlying training tasks; it does not contain the complete training corpus, training trajectories, or all stage-specific sampling and balancing decisions.
The related model is Logics-SWE-Qwen3.6-27B. Results reported for that model concern the paper's full training procedure and should not be interpreted as results from training exclusively on this 2.5K subset.
Data Distribution
Programming languages
| Task language | Instances | Share |
|---|---|---|
| Go | 1,377 | 53.94% |
| Python | 580 | 22.72% |
| TypeScript | 465 | 18.21% |
| JavaScript | 131 | 5.13% |
| Total | 2,553 | 100.00% |
Task language denotes the primary programming language modified by the task patch, rather than necessarily the primary language of the repository. Assignments use reference-patch file extensions for 2,546 instances, test-patch file extensions for 5 instances, and a verified repository-language fallback for 2 instances. Multi-language repositories may have different repository and task languages.
Repository coverage
| Statistic | Value |
|---|---|
| Unique repositories | 1,771 |
| Mean instances per repository | 1.44 |
| Median instances per repository | 1 |
| Repositories contributing one instance | 1,403 |
| Largest repository contribution | 24 instances (0.94%) |
| Top-10 repository share | 5.68% |
| Top-20 repository share | 8.81% |
The repository distribution is long-tailed: 79.22% of repositories contribute exactly one instance. This release is not balanced across programming languages or repositories.
Machine-readable summaries are available in language_distribution.csv, repository_distribution.csv, and summary.json.
Data Format
The data uses JSON Lines, with one task instance per record. All 2,553 records share the following 16 fields and JSON value types:
| Field | Type | Description |
|---|---|---|
instance_id |
string | Unique task identifier. |
repo_name |
string | Source repository in owner/repository form. |
base_commit |
string | Repository revision used as the task's starting point. |
problem_statement |
string | Task description presented to the agent. |
patch |
string | Reference code changes; not an agent input. |
test_patch |
string | Test changes associated with task verification. |
docker_image |
string | Task-environment container image reference hosted on GHCR (ghcr.io). |
image_info |
string | Additional environment-image metadata. |
modified_files |
string | Stored description of modified files. |
modified_entity_summaries |
string | Stored summaries of modified code entities. |
num_non_test_files |
number | Non-test file-change count. |
num_non_test_func_methods |
number | Non-test function/method-change count. |
num_non_test_lines |
number | Non-test line-change count. |
passrate |
string | Historical pass-rate metadata; not a model-independent difficulty score. |
created_at |
string | Source timestamp metadata. |
idx |
number | Source record index. |
The language statistics above are derived annotations; language is not a field in the source records. The source snapshot also does not provide complete per-instance A/B/C expert-category labels.
Quick Start
Load from Hugging Face
Install the Hugging Face datasets package, then load the dataset:
from datasets import load_dataset
tasks = load_dataset(
"Logics-MLLM/Logics-SWE-Env-2.5K",
split="train",
)
print(f"Number of tasks: {len(tasks)}")
task = tasks[0]
print(task["instance_id"])
print(task["repo_name"])
print(task["problem_statement"])
The train split contains all 2,553 released instances in data/train.jsonl; no held-out evaluation split is provided. Loading the records does not itself provision task environments or execute verification.
To load a downloaded copy instead, use load_dataset("json", data_files="train.jsonl", split="train").
Use with an agent runner
- Resolve the task's environment image and initialize the repository at
base_commit. - Give the agent the problem statement and the allowed repository context.
- Collect the agent's proposed code changes.
- Verify those changes using the task-specific tests and runner protocol in an isolated environment.
Keep reference patches, hidden test content, and derived solution summaries out of agent-visible inputs when measuring task-solving performance. Do not evaluate an agent in a workspace where the reference solution has already been applied.
Scope and Limitations
- Training subset, not a held-out benchmark. This release is drawn from the paper's training data. Performance on these tasks is not evidence of held-out generalization for models trained on them.
- Environment availability matters. Image metadata alone does not guarantee that an image is publicly retrievable or compatible with a particular runner. Use verified release image references and check runtime requirements before launching jobs.
- Historical pass rates are protocol-dependent. They depend on the model, sampling, and verification setup used to collect them, and should not be treated as scores of the released model.
- Coverage is uneven. Go accounts for over half of this subset; conclusions should account for its language and repository composition.
- Execute in isolation. Repository code and tests should run in appropriately isolated environments without access to host credentials or unrelated data.
License
The database is made available under the Open Data Commons Attribution License (ODC-BY) v1.0. Please attribute Logics-SWE-Env-2.5K and retain the applicable license notices when using or redistributing the database in accordance with its terms.
This license applies to rights in the database, not to all rights in its individual contents. Repository-derived code, reference patches, test patches, and other third-party materials remain subject to their applicable upstream licenses and notices. Container images and their dependencies may also carry separate licenses. ODC-BY does not replace those licenses or grant additional rights in third-party content.
Citation
If you use this dataset, please cite the associated work:
@misc{zhao2026onetomoremoretoone,
title = {One to More, More to One: Category-Aware Iterative Expert Training for Software Engineering Agents},
author = {Jie Zhao and Ziyu Jiang and Suhang Zheng and Minghui Shan and Xiaoxiao Xu and Lin Qu},
year = {2026},
eprint = {2609.23377},
archivePrefix = {arXiv},
primaryClass = {cs.SE},
url = {https://arxiv.org/abs/2609.23377}
}
Acknowledgements
We thank the authors and maintainers of the upstream repositories for their open-source contributions.
- Downloads last month
- 103
