starred/pvetui

Fork 0

mirror of https://github.com/devnullvoid/pvetui.git synced 2026-04-25 05:15:51 +03:00

[GH-ISSUE #69] bug: Configuration wizard fails to save on Windows after default config creation #14

New issue

Closed

opened 2026-02-26 18:43:12 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 18:43:12 +03:00

Owner

Originally created by @unclesp1d3r on GitHub (Dec 24, 2025).
Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/69

Originally assigned to: @devnullvoid on GitHub.

Configuration wizard fails to save on Windows after default config creation

I’ve run into a reproducible issue on Windows that prevents the configuration wizard from ever saving successfully when starting from a freshly created default config.

When running pvetui 1.0.15 on Windows, if you accept the initial prompts to (1) create a default configuration file and then (2) launch the interactive configuration wizard, the wizard fails validation on save. The error indicates that no authentication method was provided, even though valid credentials were entered.

It appears the wizard is validating against the initially generated default config content rather than the values entered in the interactive editor.

Steps to reproduce

Install pvetui 1.0.15 on Windows using Scoop.
Open PowerShell and run pvetui with no parameters.
At the prompt “Would you like to create a default configuration file?”, select Y.
At the prompt “Would you like to edit the new config in the interactive editor?”, select Y.
In the configuration form, provide either:
- a password, or
- a token_id and token_secret.
Select Save.
Observe the error dialog:

“You must provide either a password or a token for authentication.”

Expected behavior

The configuration wizard should accept valid authentication input and successfully save the configuration.

Actual behavior

The wizard always fails validation with the authentication error, making it impossible to save the config through the interactive editor.

Environment

OS: Windows 11 25H2
Installation method: Scoop
Version: pvetui 1.0.15

Let me know if you’d like me to test a patch or provide additional logs.

Originally created by @unclesp1d3r on GitHub (Dec 24, 2025). Original GitHub issue: https://github.com/devnullvoid/pvetui/issues/69 Originally assigned to: @devnullvoid on GitHub. ### Configuration wizard fails to save on Windows after default config creation I’ve run into a reproducible issue on Windows that prevents the configuration wizard from ever saving successfully when starting from a freshly created default config. When running **pvetui 1.0.15 on Windows**, if you accept the initial prompts to (1) create a default configuration file and then (2) launch the interactive configuration wizard, the wizard fails validation on save. The error indicates that no authentication method was provided, even though valid credentials were entered. It appears the wizard is validating against the initially generated default config content rather than the values entered in the interactive editor. ### Steps to reproduce 1. Install `pvetui` 1.0.15 on Windows using Scoop. 2. Open PowerShell and run `pvetui` with no parameters. 3. At the prompt **“Would you like to create a default configuration file?”**, select `Y`. 4. At the prompt **“Would you like to edit the new config in the interactive editor?”**, select `Y`. 5. In the configuration form, provide **either**: - a password, **or** - a `token_id` and `token_secret`. 6. Select **Save**. 7. Observe the error dialog: > “You must provide either a password or a token for authentication.” ### Expected behavior The configuration wizard should accept valid authentication input and successfully save the configuration. ### Actual behavior The wizard always fails validation with the authentication error, making it impossible to save the config through the interactive editor. ### Environment - OS: Windows 11 25H2 - Installation method: Scoop - Version: pvetui 1.0.15 Let me know if you’d like me to test a patch or provide additional logs.

kerem

2026-02-26 18:43:12 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 18:43:12 +03:00

Author

Owner

@devnullvoid commented on GitHub (Dec 24, 2025):

Interesting! I thought I fixed this in a recent release. Or at least it was something very similar. Nevertheless, thank you for the report. I'll get it fixed.

@devnullvoid commented on GitHub (Dec 24, 2025): Interesting! I thought I fixed this in a recent release. Or at least it was something very similar. Nevertheless, thank you for the report. I'll get it fixed.

kerem commented

2026-02-26 18:43:12 +03:00

Author

Owner

@centopw commented on GitHub (Dec 30, 2025):

Have the same problem on MacOS 15.6.1, install using homebrew and pvetui 1.0.15

@centopw commented on GitHub (Dec 30, 2025): Have the same problem on MacOS 15.6.1, install using homebrew and pvetui 1.0.15

kerem commented

2026-02-26 18:43:12 +03:00

Author

Owner

@srozb commented on GitHub (Dec 30, 2025):

I experienced the same issue on macOS. I was able to work around it by populating the API ID and Token directly in the configuration file.

@srozb commented on GitHub (Dec 30, 2025): I experienced the same issue on macOS. I was able to work around it by populating the API ID and Token directly in the configuration file.

kerem commented

2026-02-26 18:43:12 +03:00

Author

Owner

@devnullvoid commented on GitHub (Jan 1, 2026):

Fix is on develop and verified (Windows + Linux); macOS/homebrew reports should be resolved too. Config wizard now validates live form values (no stale auth) and rejects partial token input. Release pending.

@devnullvoid commented on GitHub (Jan 1, 2026): Fix is on develop and verified (Windows + Linux); macOS/homebrew reports should be resolved too. Config wizard now validates live form values (no stale auth) and rejects partial token input. Release pending.

kerem referenced this issue

2026-02-26 18:43:17 +03:00

[PR #14] [MERGED] Add common linters #30

kerem referenced this issue

2026-02-27 12:38:23 +03:00

[PR #14] Add common linters #106