Skip to content
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

Number of minutes is always reported as positive #2

Closed
jeremyfelt opened this issue May 12, 2012 · 2 comments
Closed

Number of minutes is always reported as positive #2

jeremyfelt opened this issue May 12, 2012 · 2 comments

Comments

@jeremyfelt
Copy link

@jeremyfelt jeremyfelt commented May 12, 2012

When a scheduled event does not fire and the associated timestamp is in the past, the human readable time still reports as positive.

@tollmanz
Copy link
Owner

@tollmanz tollmanz commented May 13, 2012

Do you remember if "Doing Cron" stated yes or no when this occurred?

@jeremyfelt
Copy link
Author

@jeremyfelt jeremyfelt commented May 13, 2012

I believe it said yes, but not certain.
On May 13, 2012 2:03 PM, "Zack Tollman" <
reply@reply.github.com>
wrote:

Do you remember if "Doing Cron" stated yes or no when this occurred?


Reply to this email directly or view it on GitHub:
#2 (comment)

tollmanz pushed a commit that referenced this issue Jul 1, 2012
When an events time is less than the current time, the human time diff gets the "ago" indicator. Additionally, if doing cron is "no" and the current time is greater than an event's time, the event is printed in red. This should allow for very easily seeing if a number of events have been missed.
@tollmanz tollmanz closed this Jul 1, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants