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

Abierto
  • ¿Algo no está bien?
#690 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

@pcbeingused333 ya está trabajando en esto.

Desde el 31/10/2026.

  • #691 de @pcbeingused333 — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, python
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Python
Estrellas
329
Forks
169
Merge medio
4 d 18 h
PR fusionados (30 d)
9

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QuantConnect/lean-cli

Todos los issues de QuantConnect/lean-cli

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.