2014-12-24 GnuCash IRC logs
01:28:35 *** fell has joined #gnucash
01:28:35 *** gncbot sets mode: +o fell
01:41:20 *** StuM has quit IRC
01:49:37 *** ErKa has joined #gnucash
02:10:40 *** MechtiIde has joined #gnucash
02:18:57 *** ErKa has quit IRC
02:27:06 *** gjanssens has joined #gnucash
02:27:06 *** gncbot sets mode: +o gjanssens
02:29:28 *** O01eg has quit IRC
03:06:11 *** gour has joined #gnucash
03:24:54 *** StuM has joined #gnucash
03:33:39 *** cartsoftware has joined #gnucash
03:42:37 *** gour has quit IRC
03:43:20 *** gour has joined #gnucash
03:51:57 *** cartsoftware has quit IRC
04:02:10 *** wol has joined #gnucash
04:08:49 *** fell has quit IRC
04:09:43 *** MechtiIde has quit IRC
04:15:49 *** wol has quit IRC
04:23:40 *** GabrieleV_ has joined #gnucash
04:23:43 *** GabrieleV has quit IRC
04:23:44 *** GabrieleV_ is now known as GabrieleV
04:40:07 *** wol has joined #gnucash
05:06:14 *** GabrieleV_ has joined #gnucash
05:06:25 *** GabrieleV has quit IRC
05:06:26 *** GabrieleV_ is now known as GabrieleV
05:22:17 *** pppp2 has quit IRC
05:51:13 *** wol has quit IRC
05:51:13 *** GabrieleV_ has joined #gnucash
05:51:23 *** GabrieleV has quit IRC
05:51:23 *** GabrieleV_ is now known as GabrieleV
05:55:26 *** wol has joined #gnucash
06:06:01 *** pppp2 has joined #gnucash
06:27:40 *** rubdos has joined #gnucash
07:11:46 *** StuM has quit IRC
07:15:28 *** wol has quit IRC
07:21:33 *** himaxx has joined #gnucash
07:24:28 *** aqua___ has joined #gnucash
07:28:56 *** himaxx has quit IRC
07:31:07 *** StuM has joined #gnucash
07:33:42 *** rickoehn has joined #gnucash
07:58:54 *** agaric has quit IRC
08:13:24 *** andy has quit IRC
08:23:00 *** andy has joined #gnucash
08:55:06 *** Jimraehl1 has left #gnucash
08:55:10 *** pppp2 has quit IRC
09:08:50 *** Jimraehl1 has joined #gnucash
09:57:04 *** himaxx has joined #gnucash
09:57:28 *** himaxx has quit IRC
10:31:09 *** aqua___ has quit IRC
10:52:03 *** O01eg has joined #gnucash
10:54:34 *** mlncn has joined #gnucash
11:11:01 *** fell has joined #gnucash
11:11:01 *** gncbot sets mode: +o fell
11:12:35 *** StuM has quit IRC
11:15:12 *** cartsoftware has joined #gnucash
11:18:09 *** MechtiIde has joined #gnucash
11:38:58 *** gjanssens has quit IRC
11:40:34 *** gour has left #gnucash
11:51:18 *** ErKa has joined #gnucash
12:06:27 *** fell_ has joined #gnucash
12:06:28 *** gncbot sets mode: +o fell_
12:09:08 *** GabrieleV_ has joined #gnucash
12:09:45 *** GabrieleV has quit IRC
12:09:46 *** GabrieleV_ is now known as GabrieleV
12:11:38 *** fell has quit IRC
12:19:57 *** gour has joined #gnucash
12:23:40 *** aqua___ has joined #gnucash
12:32:08 *** puck has quit IRC
12:35:13 *** puck has joined #gnucash
13:18:58 *** mlncn has quit IRC
13:23:45 *** aqua___ has quit IRC
13:24:58 *** aqua___ has joined #gnucash
13:29:53 *** aqua___ has quit IRC
13:32:11 *** mlncn has joined #gnucash
13:46:17 *** MechtiIde has quit IRC
13:54:04 <warlord> jralls: w.r.t. bug 741948 , any idea how the user generated the txn with duplicate GUID?
14:06:54 <jralls> warlord: No. It was from the thread starting at http://lists.gnucash.org/pipermail/gnucash-user/2014-May/054453.html. The user had two transactions from 2010 that were exact duplicates, including entry times and all GUIDs. One masked the other in the GUI so he wasn't able to reconcile. The duplication occurred, and the user made a compensating entry, some 2 months after the transactions were originally entered, but it took
14:06:54 <jralls> him 4 years to be sufficiently irritated to ask about it on the mailing list.
14:07:39 <jralls> You won't see all of that in the list archive, as some of it was revealed in private mail after he sent me his file.
14:13:32 <warlord> How did the duplicate transaction occur?
14:13:39 <warlord> Log Replay?
14:15:37 <jralls> The user didn't know, it's probably been too long to remember. Log replay is an interesting hypothesis, though.
14:15:55 *** himaxx has joined #gnucash
14:17:25 *** himaxx has quit IRC
14:17:40 <warlord> That's the only way I can think to have an exact duplicate of a transaction, including GUID.
14:18:18 <warlord> The chance of a duplicate GUID randomly is like 1 in 1^128. That's not going to happen in our lifetime.
14:20:22 <jralls> Well, 2^128. If it was 1^128 we'd only have one GUID for everything. ;-) But no matter how small the likelihood it can still happen, even twice in one session. That's the way randomness works.
14:21:32 <jralls> You're also assuming that the root cause was two transaction objects in memory rather than one transaction object written twice.
14:21:36 <warlord> yes, but the *chance* of that happening in very very small. Yes, it *could* happen, but you're more likely to win MegaMillions every week for the rest of your life than see duplicate GUIDs randomly occur.
14:22:22 <warlord> Yes, I am, but the write code is very well tested, so I really doubt it would write the same txn twice. More likely it was input twice.
14:22:38 <warlord> (or somehow otherwise duplicate in core)
14:26:46 <jralls> Correct, except for the MegaMillions part: Since I never buy a ticket, the likelihood of my winning even once is 0. But "not likely" isn't "not", so while I'm not likely to see a duplicated GUID due to randomness I might anyway. I don't think I did, I'm just being pedantic.
14:29:53 <jralls> Anyway, the object creation code is also well exercised. I agree that log replay is the most likely cause for a duplication, so it should be checking the Collection as well before adding an object.
14:31:09 <warlord> right.
14:32:23 *** Krzysiek_K has joined #gnucash
14:32:36 <warlord> I really don't think we ought to check for duplicates on every data load.
14:33:28 <warlord> Honestly, it would be nice if there were a "written-by-version" field at the top of the data file so that we could ignore checking certain "known errors" if we know the writing version is "new enough"
14:34:59 <jralls> There is, now. You added it about 18 months ago.
14:37:05 <warlord> clearly we should use it. For example, it would mean we don't need to check all strings if we know that the data file was written from a version of gnucash that properly checked the data. ;)
14:37:28 <jralls> But in this case we should be getting an error back from the collection's hash function that we're trying to insert a duplicate. We just need to handle the error by creating a new GUID.
14:39:11 <jralls> Or in the case of log replay, dropping the object on the floor, since it's already in memory.
14:40:58 <jralls> Hmm. The version id is a schema version, not a GnuCash version. Keeping track of which version fixed which bug and incorporating that into the Scrub would be a chore.
14:44:00 <warlord> It'll be easier once we move completely the SQLite ;)
15:30:44 *** gour has quit IRC
16:01:15 *** aqua___ has joined #gnucash
16:24:06 *** aqua___ has quit IRC
16:50:20 *** rickoehn has quit IRC
16:58:05 *** ErKa has quit IRC
17:01:30 *** Krzysiek_K has left #gnucash
17:54:40 *** lmat has joined #gnucash
18:36:34 *** mlncn has quit IRC
18:47:55 *** StuM has joined #gnucash
18:56:21 *** mlncn has joined #gnucash
19:12:33 *** aqua___ has joined #gnucash
19:26:40 *** mlncn has quit IRC
19:27:28 *** aqua___ has quit IRC
19:32:13 *** rubdos has quit IRC
20:03:28 *** kanly has joined #gnucash
20:13:47 *** aqua___ has joined #gnucash
20:20:54 <kanly> Hey, newbie to gnucash here, just started using it and love it. Got all my banking, credit, and loan info imported, now I am having issues with stocks and other investments =/ I get stock grants from my company, so they are essentially a gift, does that mean I should list the price in transactions as 0?
20:32:10 <warlord> kanly: are they real stock grants, or are they options? if a real stock grant than they are income. If it's an option...... gnucash doesn't have a good way to represent it because it's only a promise of an asset, not a real asset.
20:49:20 <kanly> I believe these are real stock grants. They are vested over 4 years and they just appear in my account. I don't have to do anything. Every couple of months I get a few here and there. Thanks for the help warlord!
20:53:46 <jralls> kanly: If the company is publicly traded, you should price them at the close of the day they were issued. If not, talk to the HR or finance folks at your company to find out how to price them. This will be reportable income of some sort, so find out what kind, how it's going to be reported to the IRS, and how it affects your W4 and FICA withholding. You don't want a nasty surprise come April!
20:54:54 <warlord> kanly: what jralls said!
22:36:21 *** lmat has quit IRC
23:19:13 *** StuM has quit IRC