fix(ibkr): keep dry-run Gateway sessions read-only - #515
Merged
Merged
Conversation
Dry-run still called the live connect_ib helper, so what-if permission probes ran after hours and logged Error 201 on small accounts. Wire dry-run to read-only connect, and treat margin probe rejections as write-access proof. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
connect_ib, which ran the live what-if write probe and loggedError 201on U159 (~$390 ELV).read_only=Trueand skips the permission probe.INITIAL MARGIN/EQUITY WITH LOAN VALUE) count as write-access proof, not missing trading permission.Test plan
Made with Cursor