anongit / mytracks

Automatically exported from code.google.com/p/mytracks
0 stars 0 forks source link

Several fixes to the service with regard to the stability bugs #199

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Mercurial clone with changes to be reviewed:
http://code.google.com/r/bartn-mytracks/source/list

Revisions to be pulled from that clone (or "all"):
all

Purpose of code changes on the clone:
Fix a few stability bugs.  Clean up code.

NOTE:
I will have more fixes coming up, including a fix to prevent from killing the 
service (startForeground).  This set of changes addresses most of the bugs I 
own (I will update each of them separately).

Original issue reported on code.google.com by ba...@google.com on 24 Oct 2010 at 9:21

GoogleCodeExporter commented 9 years ago
Added a few more fixes, including setting the service into foreground which 
should finally resolve all complaints about stopping the service.

I've noticed a few more minor bugs (e.g. after starting a new track, the 
selected track is not properly updated).  I will fix it later.

Original comment by ba...@google.com on 25 Oct 2010 at 4:30

GoogleCodeExporter commented 9 years ago

Original comment by sandordo...@google.com on 27 Oct 2010 at 5:04

GoogleCodeExporter commented 9 years ago
Just quick status update from my side (outstanding TODOs):
1) Add more sophisticated unit tests for the new interface I added (Sandor's 
comment)
2) Fix the selected track bug (some people also believe this is a bug, so I 
want to make it consistent)
3) DB locking fix

I believe other changes are ready to merge, unless you have more comments.  
I've been dogfooding this version of MyTracks for several days and I haven't 
found any single flaw yet (except all known issues).

Original comment by ba...@google.com on 27 Oct 2010 at 5:17

GoogleCodeExporter commented 9 years ago
One more update:
I've discovered a flaw this morning that needs to be fixed before my changes 
can be merged.  I will try to send a fix tonight.

Original comment by ba...@google.com on 28 Oct 2010 at 10:01

GoogleCodeExporter commented 9 years ago
PTAL.  I also believe all changes from my branch (except the one I marked -1) 
are ready for merging with head.  These changes span for about 2 weeks and now 
is hard to avoid conflicts.

1) and 3) remain at this point (2) was fixed.

Original comment by ba...@google.com on 29 Oct 2010 at 6:03

GoogleCodeExporter commented 9 years ago
I believe all changes have been addressed and merged with head.

Original comment by ba...@google.com on 5 Nov 2010 at 8:11