agentscope-ai / agentscope-ai/QwenPaw

[Bug]: Environment variables not passed & Frontend config not synced

Ouverte
#6,055 5 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bug
Langage dominant
TypeScript
Étoiles
35k
Forks
3.1k
Merge moyen
1 j 13 h
PR mergées (30 j)
228

Description

Version: QwenPaw 1.1.12 (Docker)

Bug 1: Environment variables not passed to agents

After setting SUMMARIZE_WHEN_COMPACT=false via docker-compose environment, newly created agents still use the system default value true. The environment variable has no effect.

Bug 2: Frontend does not read local config

After modifying the model configuration in /home/ubuntu/copaw/secrets/providers, the frontend UI does not update and still displays the old model.

Bug 3: Attempting to upgrade to the untested v2.0 version directly caused a crash, making the service completely unavailable.

Steps to reproduce (Bug 1):

Add SUMMARIZE_WHEN_COMPACT=false to the environment section in docker-compose.yml.
Start the service and create a new agent.
Check the agent configuration – summarize_when_compact is still true.
Expected results:

Environment variables should override system defaults and apply to new agents.
The frontend UI should sync with the configuration file after a restart.
Version updates must be tested and must not break existing environments.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Start by reproducing Bug 1 using the environment section in docker-compose.yml, then trace how SUMMARIZE_WHEN_COMPACT reaches a newly created agent. Compare the frontend’s displayed model with the configuration under /home/ubuntu/copaw/secrets/providers, and test the reported upgrade path separately. Done means the environment override applies, the frontend reflects the local configuration after restart, and existing environments remain available during version updates.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
docker-compose, python
Domaine
backend, frontend, release
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
Plutôt claire
Accessibilité débutants
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.