Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Open Settings Folder crashes without the process environment variable and uses the wrong portable path

Abierto Apto para principiantes
  • ¿Algo no está bien?
#696 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
visualbasic
Área
desktop

Línea de trabajo

Lee SettingsPage.xaml.vb y sigue cómo SettingsService selecciona DataFolder en SettingsService.vb, incluido el modo portátil en Application.xaml.vb. Empieza comparando la ruta del controlador del botón con la carpeta de datos activa del servicio y luego comprueba cómo se gestionan los errores al abrir la carpeta. La tarea estará terminada cuando el botón abra el directorio de configuración activo en ambos casos notificados y muestre un error gestionado si falla la apertura.

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

Descripción

Tested on official v4.0.0-beta.12, Windows 11 25H2 (26200.9711), ASUS Vivobook S 15 / Snapdragon X Elite X1E-78-100 / 16 GB RAM, .NET 10.0.13. Both the native ARM64 application and the official x64 application were tested directly on this ARM laptop. Additional component checks used unchanged libraries extracted from the x64 release, with the release's embedded manifest. No Intel/AMD PC was tested. Only disposable files were used. Most testing was automated with Codex, with human assistance identified where applicable. Related build request: #556.

The same button has two related problems.

A. Crash when the process has no IridiumIO environment variable

  1. Launch the application from a parent process that lacks IridiumIO.
  2. Open Settings and click Open Settings Folder.

The app exits with:

System.ArgumentNullException: Value cannot be null. (Parameter 'path1')
  at System.IO.Path.Combine(String path1, String path2)
  at CompactGUI.SettingsPage.Button_Click(Object sender, RoutedEventArgs e)

This happened at 01:48:53 and 01:50:27 BST on 21 October 2026. The second reproduction deliberately omitted the variable only from the launched child's environment; no global variable was removed. Application logs and Windows .NET Runtime 1026/Application Error 1000 records corroborate both crashes.

A fresh child given the existing user-scoped value did not crash.

B. Wrong folder in portable mode
With IridiumIO present and the executable in a directory named CompactGUI, active settings are in the adjacent .CompactGUIData directory. The button instead constructs %LOCALAPPDATA%\IridiumIO\CompactGUI. That path did not exist in this setup; Explorer opened Documents instead of the active data folder.

Expected in both cases: open the actual settings directory, with a handled error if opening fails.

Source explanation

Opening ISettingsService.DataFolder.FullName with error handling should address both failures.

x64 component comparison (21 October 2026)

Invoking the actual x64 release's SettingsPage.Button_Click handler with IridiumIO missing only from the test process reproduced the same exception:

System.ArgumentNullException: Value cannot be null. (Parameter 'path1')
  at System.IO.Path.Combine(String path1, String path2)
  at CompactGUI.SettingsPage.Button_Click(Object sender, RoutedEventArgs e)

The harness caught that exception. A subsequent direct GUI test independently confirmed the x64 app crash:

Direct x64 GUI follow-up (21 October 2026, BST)

A fresh official x64 application was launched with IridiumIO omitted only from that child's environment. Clicking Settings -> Open Settings Folder terminated the process at 18:22:52. Windows recorded:

.NET Runtime, event 1026: process terminated due to an unhandled exception
System.ArgumentNullException: Value cannot be null. (Parameter 'path1')
  at System.IO.Path.Combine(String path1, String path2)
  at CompactGUI.SettingsPage.Button_Click(Object sender, RoutedEventArgs e)
Application Error, event 1000: CompactGUI.exe; exception 0xe0434352

The event's executable path matched the isolated official x64 copy, and the process was confirmed exited. This was an actual button click and unhandled application crash, separate from the caught component test.

With the existing environment value present, the portable x64 button opened a new Explorer window titled Documents at about 18:11:38. Its active data directory was the adjacent .CompactGUIData folder, not Documents. Explorer's full address could not be independently read because access to that window was unavailable; the window title, active data directory and handler's constructed path were recorded. The portable misdirection was also directly observed in the earlier ARM64 test.

The existing user-scoped environment variable was left unchanged.

Lenguaje dominante
Visual Basic .NET
Estrellas
8.9k
Forks
343
Merge medio
3 d 18 h
PR fusionados (30 d)
7

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 IridiumIO/CompactGUI

Todos los issues de IridiumIO/CompactGUI

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.