Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

The elapsed_time is sometimes negative #9

Closed
kalbasit opened this issue Oct 30, 2011 · 1 comment
Closed

The elapsed_time is sometimes negative #9

kalbasit opened this issue Oct 30, 2011 · 1 comment
Labels
Backend BUG
Milestone
0.0.1

Comments

@kalbasit
Copy link
Owner

If the modification time of a new time entry is behind the last one, this happens after a git revert for example, the elapsed_time is all wrong and most of the time it goes under 0
@kalbasit
Copy link
Owner Author

If you were a victim of this issue, you can recalculate the elapsed time of
all projects and all their files by visiting
http://localhost:9282/rehash, but please
keep in mind that this can take a long time to process.

kalbasit added a commit that referenced this issue Oct 30, 2011
@kalbasit
Readme: Add a space after #9 so github parses it.
d70ad70
kalbasit added a commit that referenced this issue Oct 30, 2011
@kalbasit
Merge branch 'release/0.0.2' into stable
1819e27 
* release/0.0.2:
  WatchTower: Bump to version 0.0.2, the description was just not clear on rubygems.
  Gemspec: The summary was too long to fit in a tweet.
  Gemspec: The description is just too long.
  Readme: Seems like Github doesn't parse issues in the README, hardcode the link.
  Readme: Add a space after #9 so github parses it.
  Readme: Fix a typo.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Backend BUG
Projects
None yet
Milestone
0.0.1
Development

No branches or pull requests
1 participant
@kalbasit