QuantConnect / QuantConnect/lean-cli

Standardize Handling of Conflicting Project Names to Local Platform Behavior

Open
#374 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
326
Forks
168
Avg merge
3d 50m
Merged PRs (30d)
3

Description

  • Project config corruption causes the CLI to lose track of the project cloud id and create a duplicate with project name 2

  • CLI Current Behavior:

    • on pull: Finds alternate name on conflict and pulls to the new directory. Also, updates the name in the cloud
    • on push: Renames locally on conflict/corruption and also renames in the cloud

  • Local Platform's current behavior

    • on pull: Fail and warn on conflict
    • on push: does not have any native logic for this case but maybe can be the same as pul i.e fail

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Trace the CLI's pull and push handling for conflicting or corrupted project names, then compare it with the stated Local Platform behavior. Clarify whether both operations should fail and warn, and treat the work as done when the chosen behavior is consistent and no duplicate or cloud rename occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.