Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

lean live deploy skips the localhost host rewrite and symbol map mount for brokerage settings

Aperta
  • Qualcosa non va?
#690 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 7 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker, python
Ambito
cli

Direzione di ricerca

Start with lean/components/docker/lean_runner.py, reading get_basic_docker_config and _mount_common_directories to understand how the existing top-level settings are handled. Compare those paths with the selected environment settings used by lean live deploy; done means the environment's localhost host is rewritten and its symbol map file is mounted.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Expected Behavior

lean live deploy with the Terminal Link brokerage (renamed to Quant Bridge in #685) rewrites a localhost / 127.0.0.1 server host to host.docker.internal. It also mounts the symbol map file from data/symbol-properties. lean data download and lean backtest already do both.

Actual Behavior

For lean live deploy neither happens. The Lean container gets "terminal-link-server-host": "localhost", so it can't reach a server running on the user's machine. The symbol map file isn't mounted either, and terminal-link-symbol-map-file keeps its relative value.

LeanRunner only checks the top level of the Lean config (lean/components/docker/lean_runner.py: the server host loop in get_basic_docker_config and files_to_mount in _mount_common_directories). lean live deploy writes the brokerage and live data provider settings into lean_config["environments"][<environment>] instead, so the checks never find them.

Potential Solution

Apply the host rewrite and the file mounts to the selected environment's entries as well as the top-level ones.

Reproducing the Problem
  1. lean live deploy "<project>" --brokerage "Terminal Link" --data-provider-live "Terminal Link" --terminal-link-server-host localhost ... (with all the other required --terminal-link-* options)
  2. Look at the config passed to the container: environments["lean-cli"]["terminal-link-server-host"] is still localhost, and only config.json is mounted.
  3. For comparison, lean data download --data-provider-historical "Terminal Link" ... --terminal-link-server-host localhost passes host.docker.internal and mounts /Files/terminal-link-symbol-map-file.
System Information

lean-cli master (1873571).

Checklist
  • I have completely filled out this template
  • I have confirmed that this issue exists on the current master branch
  • I have confirmed that this is not a duplicate issue by searching issues
Lingua principale
Python
Stelle
329
Fork
169
Merge medio
5g 16h
PR unite (30g)
10

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QuantConnect/lean-cli

Tutte le issue di QuantConnect/lean-cli

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.