v0.2.126 - #130
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b8e9118. Configure here.
| instance.instance.load() | ||
| # Resources load lazily on first `db()`/`browser()`/`resources()` access via | ||
| # `_load_resources()`. Skipping the eager preload avoids fail-fast 502s while | ||
| # the container is still warming up. |
There was a problem hiding this comment.
Removing load() breaks db() and browser() calls
High Severity
The instance.instance.load() call was removed with a comment claiming resources load lazily on first db()/browser()/resources() access via _load_resources(). However, InstanceClient.db() and InstanceClient.browser() (and their async counterparts) do not call _load_resources() — only resources() does. Since _resources_state is initialized with empty dicts, calling db() or browser() after make() or get() will now raise a KeyError, breaking the SDK's primary workflow.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit b8e9118. Configure here.


No description provided.