6.0.0-alpha12
6/12/25

[#13119] time of auto_save_drafts is double for the first auto save
Summary time of auto_save_drafts is double for the first auto save
Queue IMP
Queue Version 6.1.7
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester lauffer (at) ph-freiburg (dot) de
Created 04/16/2014 (4075 days ago)
Due
Updated 12/30/2014 (3817 days ago)
Assigned 04/16/2014 (4075 days ago)
Resolved 12/30/2014 (3817 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/30/2014 06:28:03 PM Michael Slusarz State ⇒ Not A Bug
 
05/13/2014 06:34:51 AM Michael Slusarz State ⇒ Stalled
 
04/18/2014 06:10:29 AM Michael Slusarz Comment #4 Reply to this comment
Put a 'console.log(new Date());' entry inside of the auto-draft 
function (don't have access to the code right this second, so not sure 
of the official function name) in js/compose-dimp.js.

Do note that drafts will NOT be auto-saved unless something has 
actually changed in the timespan since the last update.  Maybe that's 
why you are not seeing consistent updates.
04/17/2014 09:50:12 AM lauffer (at) ph-freiburg (dot) de Comment #3 Reply to this comment
Can you give me a patch/info to monitor or so...?
I just watched several times with different auto_save settings (1min, 
5min) the draft folder on the imap server (watch -n 1 ls...) directly.
04/16/2014 08:51:27 PM Michael Slusarz Comment #2
State ⇒ Feedback
Reply to this comment
Can't reproduce.

Added console log to the code - logging when the periodical executor 
is defined, and then every time the save drafts it is run.  Used a 5 
second interval for testing.

// Initial definition
Date {Wed Apr 16 2014 14:44:29 GMT-0600 (Mountain Standard Time)}
compos...1884070 (line 685)
// First run (to init the hash values)
Date {Wed Apr 16 2014 14:44:29 GMT-0600 (Mountain Standard Time)}
compos...1884070 (line 705)
// Second run
Date {Wed Apr 16 2014 14:44:34 GMT-0600 (Mountain Standard Time)}
compos...1884070 (line 705)
// Third run
Date {Wed Apr 16 2014 14:44:39 GMT-0600 (Mountain Standard Time)}
compos...1884070 (line 705)
[etc...]

It's correctly being run every X seconds (X in the test = 5 seconds).
04/16/2014 03:39:27 PM lauffer (at) ph-freiburg (dot) de Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ time of auto_save_drafts is double for the first auto save
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
- tested with chrome and ff latest
- in dynamic view
- with "Compose message in a seperate window"

The preset time of auto_save_drafts is exactly the double for the 
first save. So the 5min auto save tasks will be done after now+10, 
now+15, now+20...

realy a minor bug... casually found...

Saved Queries