runpod: fix a NameError in the provision path, and test for the whole class
The 150 GB warning's call site in _provision_one used a name that did not exist in that scope. The helper was unit-tested and passed; every pod test then failed in two seconds with "name 'entry' is not defined" before renting anything. A helper can be correct while the line that calls it is not. The entry is looked up the way the rest of the pool does it. And since pyflakes sees exactly this class of bug, a test now runs it over the modules a pod boot goes through, so an undefined name in that path fails the suite instead of the first real request. Co-Authored-By:Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY
Showing
Please
register
or
sign in
to comment