fix: stop discovered sandbox containers#22
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
sandbox down localstack-awsdiscover and stop timestamped LocalStack containers created by fallback startupnullstate sandbox down localstack-20260510103849Verification
python -m unittest tests.test_sandbox.SandboxTests.test_localstack_down_plan_accepts_discovered_container_names tests.test_sandbox.SandboxTests.test_sandbox_down_discovers_backend_containers tests.test_sandbox.SandboxTests.test_sandbox_down_accepts_explicit_localstack_container_name -vpython -m nullstate sandbox down localstack-aws --dry-runpython -m nullstate sandbox down localstack-20260510103849 --dry-runpython -m unittest tests.test_sandbox -vpython -m ruff check src\nullstate\cli.py src\nullstate\sandbox.py tests\test_sandbox.pypython -m mypy src