- Complete
SHIPPING_PLAN.mdwith a high quality implementation and tests. - DOCUMENT THE PROCESS WELL!
- This is a BIG project where an AI agent will have to pick up where I left off.
- We want to get better at doing this type of thing. So documenting will help us gett better at it.
- DON'T CHEAT! We want real tests and real benchmarks for REAL WORLD usage of this Socket2 implementation.
- Don't take the easy way out on a benchmark or a test.
- OFTEN update STUMBLES.md and BREAKTHROUGHTS.md - but ONLY ADD to these files!!
- NEVER change git history (amend, rebase, etc.)
- NEVER push code without explicit permission
- ALWAYS tell the user EXPLICITLY when you are "tired" (large context window, loss of coherence, etc.) instead of being passive aggressive ("Ready to call it a day?", etc.)
- OFTEN commit all changes in the
socket2branch. - CONSIDER updating
cheat_sheet_for_the_agent.mdto better reflect your workflow. - Keep Markdown files well formatted! (80 chars per line, etc.)
- Feel free to "Just GO!!!" No need to stop and ask for permission for every little thing.
Commands and infrastructure details for building and testing the Dart SDK, specifically for Project Socket2.
To build the runtime in release mode (as mentioned in SHIPPING_PLAN.md):
./tools/build.py -m release runtimeCore library tests (like dart:io) MUST be run using the SDK's custom
test runner to ensure they use the newly built runtime and patches.
./tools/test.py -m release standalone/io/socket2_robustness_testNote: This assumes you have built the runtime in release mode first.
Benchmarks should be run with a timeout to prevent hanging the agent if something goes wrong.
# Run with a 60-second timeout
timeout 60s DART_CONFIGURATION=ReleaseARM64 xcodebuild/ReleaseARM64/dart benchmarks/socket2_throughput.dartNote: If 'timeout' is not available, use 'is_background: true' and monitor.
To run the presubmit hooks locally (using the PRESUBMIT.py in the root):
git cl presubmitNote: This requires depot_tools to be installed and in your PATH.