[BUG]: os.chdir() Changes the Process-Wide Working Directory During Repository Sync
Los mantenedores suelen responder en 1 día
@aadityachhipa80-oss ya está trabajando en esto.
Desde el 19/11/2026.
- #70 de @aadityachhipa80-oss — abierto
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 75/100
Línea de trabajo
Lee scripts/update_subtrees.py, centrándote en sync_all_subtrees() y la llamada os.chdir(bot_root). Sigue cómo se construyen las rutas y comprueba si la función o sus llamadores dependen del directorio de trabajo del proceso. El objetivo se cumple cuando la sincronización deja intacto el directorio de trabajo y las rutas relativas, como gap_log.json, siguen resolviéndose de forma coherente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Bug Description
The sync_all_subtrees() function in scripts/update_subtrees.py uses os.chdir(bot_root) to change the current working directory of the Python process during repository synchronization.
The os.chdir() function changes the working directory globally for the entire process, rather than only for the repository synchronization function.
This can cause unexpected behavior when SkillBot is launched from a directory other than its project root. Relative file paths used by other parts of the application may resolve to different locations after repository synchronization changes the working directory.
For example, a relative path such as gap_log.json may initially resolve relative to the directory from which SkillBot was launched. After os.chdir(bot_root) executes, the same relative path resolves relative to the SkillBot project directory.
As a result, files may be read from or written to unexpected locations, potentially causing missing or misplaced gap-log entries.
Root Cause:
sync_all_subtrees()callsos.chdir(bot_root)during repository synchronization.os.chdir()modifies the current working directory for the entire Python process.- Other application components that use relative file paths are affected by this global directory change.
- The working directory may change unexpectedly when SkillBot is launched from outside its project root.
- Repository synchronization does not need to change the process-wide working directory because the relevant paths are already constructed using
bot_root.
Expected Behavior:
Repository synchronization should operate using explicitly resolved paths without changing the process-wide working directory.
The application's current working directory should remain unchanged after repository synchronization, and relative file paths used by other components should continue resolving consistently.
Actual Behavior:
The call to os.chdir(bot_root) changes the working directory globally during repository synchronization. Consequently, relative paths used by other application components may resolve to different locations before and after synchronization.
Impact:
This can cause files to be accessed or created in unexpected directories when SkillBot is launched from a location other than its project root.
It may also result in gap-log entries being written to a different file location, making previously stored entries appear missing or causing the application to use an unintended gap log.
The issue primarily affects non-default launch scenarios where the initial working directory differs from the SkillBot project directory.
Steps to Reproduce
- Set up the SkillBot project with its required Python dependencies and environment configuration.
- Open a terminal and navigate to a directory outside the SkillBot project root.
- Start the SkillBot application using its script or entry point while keeping the terminal's current working directory unchanged.
- Before repository synchronization runs, record the application's current working directory using
os.getcwd(). - Check how a relative file path such as
gap_log.jsonresolves before synchronization. - Allow the repository synchronization process to execute
sync_all_subtrees()inscripts/update_subtrees.py. - Observe the execution of
os.chdir(bot_root)inside the synchronization workflow. - After synchronization, check the current working directory again using
os.getcwd(). - Resolve the same relative file path, such as
gap_log.json, again and compare its location with the location obtained before synchronization.
Expected Result:
- Repository synchronization should not modify the process-wide current working directory.
- The current working directory should remain unchanged before and after synchronization.
- Relative file paths should continue resolving to the same locations throughout the application's execution.
Actual Result:
The os.chdir(bot_root) call changes the process-wide working directory during repository synchronization. Relative file paths can consequently resolve to different locations after synchronization.
Additional Observation:
The repository synchronization code already constructs its relevant paths using bot_root as an absolute path. Therefore, changing the process-wide working directory is unnecessary for resolving those paths.
Logs and Screenshots
No response
Environment Details
Application: SkillBot (Discord Bot)
Operating System: Windows 11
Programming Language: Python 3.11.3
Affected File: scripts/update_subtrees.py
Affected Function: sync_all_subtrees()
Affected Operation: os.chdir(bot_root)
Related Component: Repository synchronization
Affected Resource: Process-wide current working directory
Related Application Behavior: Relative file path resolution
Example Affected File: gap_log.json
Impact
Medium - Feature works but has issues
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- Lenguaje dominante
- Python
- Estrellas
- 10
- Forks
- 11
- Merge medio
- 6 min
- PR fusionados (30 d)
- 4
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AOSSIE-Org/SkillBot
-
[BUG]: Issue-creation intent is missed when the article is omitted (create issue for this)Posiblemente ocupada @Ankitavasudev la tomó hace 8 días. Abiertobug enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
AOSSIE-Org/SkillBot#65 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: Non-Atomic Gap Log Writes Can Cause Data Loss After an Interrupted SaveQuizá libre de nuevo @SYED-IRTEZA-HUSSAIN-RIZVI la tomó hace 11 días y no hay ningún pull request abierto. Abiertobug enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
AOSSIE-Org/SkillBot#61 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: wait_for_ollama() Retries Indefinitely When Ollama Is UnavailableQuizá libre de nuevo @SYED-IRTEZA-HUSSAIN-RIZVI la tomó hace 11 días y no hay ningún pull request abierto. Abiertobug enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
AOSSIE-Org/SkillBot#56 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: Backlog Messages Are Re-processed on Discord ReconnectionQuizá libre de nuevo @SYED-IRTEZA-HUSSAIN-RIZVI la tomó hace 11 días y no hay ningún pull request abierto. Abiertobug enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
AOSSIE-Org/SkillBot#58 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[BUG]: _log_gap() Performs Blocking File I/O on the Async Event LoopPosiblemente ocupada @abu-tahir-0 la tomó hace 13 días. Abiertobug enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
AOSSIE-Org/SkillBot#57 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de AOSSIE-Org/SkillBot
Issues similares
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
gke-labs/kube-agents#6778 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Declare the CMS schema library in the optional recipients extraPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea:python in-progress
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
yhay81/pyropdf#1005 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
area/build-framework kind/enhancement priority/low
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
yugabyte/yugabyte-db#38826 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
sususweet/midea_auto_cloud#306 ·
Los mantenedores suelen responder en 9 días