agentscope-ai / agentscope-ai/QwenPaw

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

Offen
#6,055 5 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
TypeScript
Sterne
35k
Forks
3.1k
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
228

Beschreibung

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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
docker-compose, python
Bereich
backend, frontend, release
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.