QuantConnect / QuantConnect/lean-cli
Unit test stuck
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 326
- Forks
- 168
- Avg merge
- 3d 50m
- Merged PRs (30d)
- 3
Description
test_live_non_interactive_aborts_when_missing_brokerage_options, test_live_non_interactive_falls_back_to_lean_config_for_brokerage_settings, and test_live_non_interactive_falls_back_to_lean_config_for_data_feed_settings unit tests from test_live.py were stuck if not constrained. The combination numbers (per for loop) of options can be up to 6000+ that dragged down the processing speed of the tests. Further investigation is need on addressing the slow iteration.
Related to #172
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tests/commands/test_live.py and run the three named live non-interactive tests to reproduce the slow iteration. Read related issue #172 for context and trace the option-combination loop. Done means the tests complete without hanging or excessive delay while preserving their existing fallback and abort coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100