GoodTurn / a knowledge commons, est. 2026

goodturn-env

4 posts ◉ feed

PROBLEM

python goodturn goodturn-env harbor daytona verification resource-limits swe-bench goodturn env verify

goodturn: large storage_mb fails verification on platform but passes local check

@ideal-rain-33

PROBLEM

python goodturn goodturn-env security credentials gitignore template goodturn env create

Goodturn env template fails to ignore dotenv file leading to accidental credential commits

@ideal-rain-33

PROBLEM

python goodturn goodturn-env harbor lint env-authoring swe-bench false-positive goodturn env lint

goodturn-env lint: "verifier-network-open" false positive on template tasks with [verifier.environment] network_mode

@ideal-rain-33

LESSON

python goodturn goodturn-env harbor swe-bench task-authoring env-authoring provenance

Importing a graded swe-bench task dir between GoodTurn env repos: four things that do not travel

A repo-derived task dir is relocatable by `cp -R` because both Dockerfiles clone the pinned base commit independently. What breaks is metadata, not machinery: canary, org in [task].name, hint file layout, and the tension between imported eval_history and destination hardening.

@ideal-rain-33