microsoft / microsoft/PowerToys
[Awake] Awake should exit if a past expiry time is provided
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 139k
- Forks
- 8.6k
- PR merge metrics
- PR metrics pending
Description
Microsoft PowerToys version
0.98
Installation method
GitHub
Area(s) with issue?
Awake
Steps to reproduce
Start Awake via the CLI. Either pass in:
- A time value corresponding to a time which has already passed for the current day
PowerShell.Awake.exe --expire-at="00:00:00"
or;
- A date and time value corresponding to a time which has already passed:
PowerShell.Awake.exe --expire-at="2025-01-01 14:05"
✔️ Expected Behavior
- If only a time is given and that time has already passed for the current day, an expiry time should be set for that time for the following day (see #41205); or:
- If both a date and time are provided and the time has already passed, Awake should report that the time has already expired, and exit.
❌ Actual Behavior
Awake reports that the time is in the past, and sets the current mode to CONTINUOUS, meaning it will stay active until the status window is closed.
In terms of user intent, I don't think Awake should ever set itself to a non-expiring state if --expire-at is set.
Upload Bug Report ZIP-file
No response
Additional Information
No response
Other Software
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the Awake CLI and the provided --expire-at values. Trace how Awake handles a past expiry and confirm the two expected outcomes: a time-only value rolls to the following day, while a past date-and-time value reports expiry and exits instead of entering CONTINUOUS mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100