Jump to content


Photo

Bug: 'Time elapsed' overfills during synchronize


  • Please log in to reply
6 replies to this topic

#1 Aleksey Yablokov

Aleksey Yablokov

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationRussia, Saint-Petersburg

Posted 01 January 2013 - 06:12 AM

Hello! :)
If the error occurs the 'time elapsed' may be '15690d 15:23:11'.
How to repeat the error see on screenshots:
time.png

#2 Aleksey Yablokov

Aleksey Yablokov

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationRussia, Saint-Petersburg

Posted 03 January 2013 - 02:23 AM

Important: the bug occurs only with ToodleDo sync.
With 'Dut today' sync it hasn't repeated.

#3 Chris

Chris

    Administrator

  • Administrators
  • 337 posts
  • LocationUtah

Posted 04 January 2013 - 04:19 PM

I'll look into it. This was an issue in a previous version, so I thought it had been fixed. There are two possibilities that I can think of:
Did you ever turn the timer on in ToodleDo?
Are you using a version other than 2.0.10?

#4 Aleksey Yablokov

Aleksey Yablokov

    Member

  • Members
  • PipPip
  • 16 posts
  • LocationRussia, Saint-Petersburg

Posted 04 January 2013 - 05:00 PM

Due Today version was 2.0.10.156.
I have removed Due Today from my phone and PC. Many errors make work impossible.
Due Today is the most comfortable GTD organizer for me, but one contains too many bugs. I have tried to adapt......
:(

#5 Elenhil

Elenhil

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 11 September 2013 - 02:00 AM

I gather the bug is still there. Are there plans to fix it (or, at least, prevent it from happening by blocking sync while a timer is on)?



#6 Chris

Chris

    Administrator

  • Administrators
  • 337 posts
  • LocationUtah

Posted 11 September 2013 - 03:47 PM

I'm working specifically on this issue tonight. It looks like it's a problem with the way the time is encoded across the different platforms. I'll working on a solution to unify them.

#7 Elenhil

Elenhil

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 20 September 2013 - 04:30 AM

Looking forward to seeing this issue (and the one affecting filters) resolved!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users