Skip to content

fix(cloud): use the resolved project for live portfolio state - #750

Open
pcbeingused333 wants to merge 1 commit into
QuantConnect:masterfrom
pcbeingused333:fix/cloud-live-local-portfolio
Open

pcbeingused333 wants to merge 1 commit into
QuantConnect:masterfrom
pcbeingused333:fix/cloud-live-local-portfolio

Conversation

@pcbeingused333

Copy link
Copy Markdown
Contributor

Fixes #743

Cloud live deploy passed the original CLI argument to the portfolio lookup even when the cloud project had resolved successfully. A project ID or a name changed during a push therefore pointed the lookup at the wrong directory. The local result reader could also select a result from a different project after comparing deployment times.

Both deployment modes now pass the local path returned during project resolution, including the path recorded by the push if it renamed the project. For a cloud-only lookup by ID or name, the CLI checks the matching local directory by cloud ID with a read-only config lookup. The result reader uses the most recent local deployment in that directory when it is newer than the cloud deployment.

The CLI regression test covers a cloud ID and a push-induced rename against a fake workspace. In both cases the cash offered must come from the resolved project even though another project's result file is newer.

This change was prepared with assistance from an AI coding tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cloud live deployment looks for local portfolio history using the unresolved project argument

1 participant