-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--start-date argument not getting respected #318
Comments
Is this behavior consistent or intermittent? |
I'm pretty sure I saw it happen multiple times but sadly I deleted the Pushover notifications, but will definitely take another screenshot if I see it happening again. |
FWIW I ran through the following commands and each time the days returned increases by one as expected while respecting the lower bound:
Is it possible you had multiple camply searches with different windows running at the same time? I'm spitballing here but keep me posted on if you see the issue occur again |
Yeah, you were right. |
Thanks for the follow up here! |
Describe the bug
The
--start-date
argument was not working as intended. I provided 2024-04-19 as start date, but received a Pushover notification for a night from the 17th to the 18th.Original Camply Command
camply campsites --campground 232447 --campground 232449 --start-date 2024-04-19 --end-date 2024-04-21 --notifications pushover --search-forever
Expected behavior
I expected to not get a notification for any nights before the 19th.
Console Output (with
--debug
)No console output as I am running it in the background.
Additional context
This is a screenshot of the Pushover notification I received:
The text was updated successfully, but these errors were encountered: