Skip to content

Add logging on background redeemer#3545

Merged
JustArchi merged 1 commit into
JustArchiNET:mainfrom
Knight1:addLoggingOnBGR
Feb 5, 2026
Merged

Add logging on background redeemer#3545
JustArchi merged 1 commit into
JustArchiNET:mainfrom
Knight1:addLoggingOnBGR

Conversation

@Knight1
Copy link
Copy Markdown
Contributor

@Knight1 Knight1 commented Feb 5, 2026

Checklist

  • I read and understood the Contributing Guidelines.
  • This is not a duplicate of an existing merge request.
  • I believe this falls into the scope of the project and should be part of the built-in functionality.
  • My code follows the code style of this project.
  • I have added tests to cover my changes, wherever they are necessary.
  • All new and existing tests pass.

Changes

Added logging for background redeemer if no keys are found in a pasted .keys file or if the file was empty.

New functionality

2026-02-05 03:47:54|ArchiSteamFarm-96380|WARN|Bot-X|ImportKeysToRedeem() No valid keys were found in your .keys file for redemption. Please ensure your keys are in the correct format.
2026-02-05 03:48:37|ArchiSteamFarm-96380|ERROR|Bot-X|ImportKeysToRedeem() config/Bot-kn16htbot.keys is empty!

Additional info

Right now an empty .keys file or a file with the wrong formatting is silently discarded. (example: KEY TAB GAMENAME)

@JustArchi JustArchi added the ✨ Enhancement Issues marked with this label indicate further enhancements to the program, such as new features. label Feb 5, 2026
@JustArchi
Copy link
Copy Markdown
Member

LGTM, thanks! 🏆

@JustArchi JustArchi merged commit 355f053 into JustArchiNET:main Feb 5, 2026
26 checks passed
JustArchi added a commit that referenced this pull request Feb 5, 2026
This is follow-up to #3545

It's assumed that if user drops keys file into ASF's config directory, their intention is to make use of that file in order to add something into ASF. While we filter it out and accept the fact that the file may not represent 1:1 ASF's required input, there should be at least one valid entry to assume that user knows what they're doing.

Therefore, deleting the file outright is probably not a good idea, now that we have logging, it's better to leave file as-is and allow user to correct it. Of course, one could also argue that such correction is impossible if 1+ valid entries are found, but that's no longer our concern, user is expected to drop valid file there to begin with, and we're only adding logic for the most obvious kind of mistake, not all mistakes possible.
@Knight1 Knight1 deleted the addLoggingOnBGR branch February 5, 2026 05:16
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Apr 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

✨ Enhancement Issues marked with this label indicate further enhancements to the program, such as new features.

Development

Successfully merging this pull request may close these issues.

2 participants