2018-01-08 GnuCash IRC logs
00:15:27 *** kael has quit IRC
01:18:24 *** fell has quit IRC
01:19:27 *** fell has joined #gnucash
01:42:09 *** O01eg has quit IRC
02:01:47 *** O01eg has joined #gnucash
02:14:42 *** Mechtilde has joined #gnucash
02:29:21 *** fekepp has quit IRC
02:46:48 *** tuxd00d has joined #gnucash
02:51:04 *** chris has quit IRC
02:54:13 *** Mechtilde has quit IRC
03:11:52 *** crossan007 has quit IRC
03:13:24 *** crossan007 has joined #gnucash
03:22:34 *** fekepp has joined #gnucash
03:25:40 *** fekepp has quit IRC
03:28:17 *** fekepp has joined #gnucash
03:34:04 *** fekepp has quit IRC
03:34:05 *** fekepp has joined #gnucash
03:39:41 *** fekepp has quit IRC
03:41:43 *** fekepp has joined #gnucash
03:49:39 *** hoijui has joined #gnucash
04:08:25 *** fekepp1 has joined #gnucash
04:11:10 *** fekepp has quit IRC
04:11:11 *** fekepp1 is now known as fekepp
04:28:20 *** fabior has joined #gnucash
04:42:58 *** harshitaneja has joined #gnucash
04:43:40 *** harshitaneja has joined #gnucash
05:31:45 *** jotrago has quit IRC
05:34:27 *** fabior has quit IRC
05:49:55 *** chris has joined #gnucash
05:55:31 *** pilotauto has quit IRC
05:57:21 *** chris has quit IRC
06:11:29 *** jotrago has joined #gnucash
06:14:32 *** hoijui has quit IRC
06:15:43 *** chris has joined #gnucash
06:17:04 *** hoijui has joined #gnucash
06:24:38 <lmat> jralls: Ah, I see. It's nice that the code was previously explicit about this expected behavior so that the fix wasn't too difficult to discover. It looks like your test is backwards. If boost threw, I would expect fail to be true. I would expect boost to throw in the later versions rather than the earlier.
06:25:15 <chris> jralls lmat - so the current state of time64-ftw is that I'm reviewing commits one-by-one, and triple checking for any bugs during conversion. but the main check is mostly via running reports. I was hoping to be skilled enough to write unittests for all, but this is rather difficult and time-consuming. So if you guys prefer I can complete the manual checks and submit a PR, and we can have more eyes on the changes. For now I know ALL
06:25:16 <chris> reports run (except I can't make taxtxf-de.scm run), however I'm not going to be 100% sure on logic errors that may have come up.
06:26:12 <chris> well I'll push PR when I've verified manually
06:26:59 <chris> lmat there may be further cherry-picking ahead
06:33:36 *** hoijui has quit IRC
06:35:38 <lmat> chris: What's difficult about unit testing scheme? I have no exposure to it, but I have lofty dreams of it being simple: just write a function that calls another function and validate its output? I know it's never "that" simple.
06:36:52 <chris> lol true it's not that difficult, but most reports are written as large blobby functions with some inputs (eg options) and outputs (split-list or html)
06:37:17 <chris> imagine testing combinations of options and validating html output
06:40:33 <chris> html output is cosmetic
06:41:13 <chris> but errors in some inputs e.g. "startdate, enddate" will be disastrous.
06:43:41 <chris> I learned my lesson in PR #250
06:44:35 <lmat> chris: Oh yeah, output HTML is no good to test. I think you shouldn't test those "controller" functions, but rather the functions they calll...iff possible.
06:45:17 <lmat> chris: But maybe that's the difficult part...it may require refactoring "blobby" functions into something more manageable: pulling out anonymous functions that should be named for the sake of unit testing.
06:47:53 <chris> Hmm thinking of transaction.scm which I spent weeks on, would have 100s of these named functions.
06:48:42 <chris> I may actually need to recruit rgmerk (the original transaction.scm writer from 15-20 years ago!) whom I met 2 days ago and has offered his expertise on this
06:49:03 <chris> but the other reports haven't had any major scrutiny by myself
06:49:29 <chris> so perhaps the only conclusion I can offer today is to complete manual checking and create PR as is
07:02:27 *** chris has quit IRC
07:21:14 *** chris has joined #gnucash
07:48:17 *** User_ has joined #gnucash
07:49:43 *** harshitaneja has quit IRC
07:51:34 *** harshitaneja has joined #gnucash
07:58:37 *** User_ has quit IRC
07:59:30 *** oozer has joined #gnucash
08:01:18 *** oozer has quit IRC
08:16:42 *** oozer has joined #gnucash
09:11:25 *** harshitaneja has quit IRC
09:12:57 *** harshitaneja has joined #gnucash
09:24:34 *** hoijui has joined #gnucash
09:30:09 *** MoeD has joined #gnucash
09:32:16 *** MoeD has quit IRC
09:37:24 *** Mechtilde has joined #gnucash
09:45:59 *** harshitaneja has quit IRC
09:58:36 <HASM> One of Gnucash/Aqbanking dialogs offers to "save the password", when retrieving transactions from the bank. Some of my download attempts fail. I'd like to delete/reset those passwords, but can't find a way to do it.
10:01:50 <warlord> HASM: exit and restart
10:02:05 <warlord> I believe it only gets saved for the current gnucash session.
10:04:35 *** ArtGravity has joined #gnucash
10:07:00 <HASM> Thanks, that seems to do it. My home computer is up 24x7 and I only log off/reboot occasionaly (to update the kernel) and that's when I exit gnucash.
10:08:11 *** oozer has quit IRC
10:12:26 *** kael has joined #gnucash
10:13:17 <Mechtilde> HASM, you can exit gnucash without reboot
10:13:28 <Mechtilde> you should do it daily
10:13:48 <Mechtilde> then you get a backup daily
10:14:58 <warlord> Mechtilde: you get a new backup anytime you click Save.
10:16:55 <Mechtilde> if I use the mysql backend too?
10:17:09 <HASM> I understand that. I save after entering all transactions. I backup monthly (via CLI). I've replayed the log files on the occasions things crash.
10:24:16 <HASM> I used to "arrow down/up" through editing split entries or new transactions. When moving out of the changed transaction my edits would be saved. Starting a few versions back (maybe for a year or more) "arrowing" out clears and doesn't save any changes, only using the enter/return key seems to work.
10:24:25 <warlord> Mechtilde: mysql backend never makes a backup, AFAIK
10:24:46 <HASM> Was that done on purpose? I've lost several entries this way.
10:26:40 <warlord> HASM: this is the first I've heard of it, honestly.
10:29:12 <HASM> warlord: should I file a bug report? One problem would be that I can't pinpoint when the behavior changed.
10:32:13 <warlord> HASM: Yes, I think you should. Arrowing out of a transaction *should* commit -- or pop up a dialog
10:33:04 <HASM> warlord: will do
10:44:58 *** kael has quit IRC
10:56:12 *** hoijui has quit IRC
10:57:01 *** marusich has quit IRC
11:02:54 *** Mechtilde has quit IRC
11:04:19 *** oozer has joined #gnucash
11:07:38 *** fekepp has quit IRC
11:08:55 *** fekepp has joined #gnucash
11:13:09 *** gnomey has quit IRC
11:14:58 *** gnomey has joined #gnucash
11:33:23 *** chf has quit IRC
11:35:11 <lmat> Still slashing through timespec.
11:38:12 *** chf has joined #gnucash
11:48:26 *** chf has quit IRC
11:58:12 *** chf has joined #gnucash
11:59:50 *** HASM has quit IRC
12:01:20 *** chf has quit IRC
12:01:38 <lmat> @tell HASM I think this is a setting. You can arrow out, and gnucash will ask if you want to keep or discard changes, and whether you want gnucash to stop asking.
12:01:38 <gncbot> lmat: The operation succeeded.
12:04:50 *** chf has joined #gnucash
12:07:07 *** jralls has quit IRC
12:07:15 *** jralls has joined #gnucash
12:07:15 *** ChanServ sets mode: +o jralls
12:18:23 <jralls> lmat: It's your test, not mine. I just enabled the commented-out line with the if statement.
12:31:24 *** hoijui has joined #gnucash
12:38:48 * warlord is not happy about having to update ovirt in lieu of the Intel bugs.
12:49:50 *** fabior has joined #gnucash
13:02:55 *** Cuare has joined #gnucash
13:04:27 *** fekepp has quit IRC
13:11:28 *** fekepp has joined #gnucash
13:30:02 *** tuxd00d has quit IRC
13:30:12 *** tuxd00d has joined #gnucash
13:31:25 *** oozer has quit IRC
13:39:08 *** KaiForce has joined #gnucash
13:40:23 *** bertbob has quit IRC
13:40:33 *** bertbob has joined #gnucash
13:40:46 *** oozer has joined #gnucash
13:43:44 *** harshitaneja has joined #gnucash
13:47:52 *** hoijui has quit IRC
13:47:58 *** chf has quit IRC
13:48:06 *** hoijui has joined #gnucash
13:49:26 *** chf has joined #gnucash
13:49:50 *** harshitaneja has quit IRC
13:49:58 *** harshitaneja_ has joined #gnucash
13:51:44 *** harshitaneja_ is now known as harshitaneja
14:01:07 *** harshitaneja has quit IRC
14:03:12 *** Crof has joined #gnucash
14:05:48 *** harshitaneja has joined #gnucash
14:11:56 *** harshitaneja has quit IRC
14:15:47 *** harshitaneja has joined #gnucash
14:19:02 *** harshitaneja has quit IRC
14:22:08 *** fabior has quit IRC
14:24:43 *** frakturfreak has joined #gnucash
14:31:13 *** oozer has quit IRC
14:38:14 *** oozer has joined #gnucash
14:40:00 *** fabior has joined #gnucash
14:45:44 *** fabior has quit IRC
16:11:16 *** bob_ has joined #gnucash
16:35:15 *** pilotauto has joined #gnucash
16:45:44 *** frakturfreak has quit IRC
16:52:59 <chris> lmat good work!
16:53:25 <chris> lmat I may just ask you to rebase again to my branch to pick up some further commits
16:55:07 *** hasdf has joined #gnucash
16:56:55 <hasdf> I have multiple accounts per bank. And multiple banks. Should I add a GnuCash account for every account, every bank or just one? I'm new to gnucash.
17:07:14 <warlord> hasdf: yes
17:12:22 <lmat> chris: No sweat. Let me know when you're ready.
17:12:57 <hasdf> warlord, yes what? ;)
17:13:04 <lmat> hasdf: For sure. You can create sub accounts if it suits your fancy. Like an account called "Chase" with sub accounts "My Chequing" "Wife's Chequing", etc.
17:13:20 <lmat> hasdf: warlord meant one account per (bank) account ;-)
17:13:24 <warlord> yes, add a GnuCash account for every account
17:14:05 <hasdf> thanks. I'll play around a bit
17:40:23 *** KaiForce has quit IRC
18:04:09 <lmat> hasdf: Neglect not the user guide and tutorial. They're excellent resources for learning double entry rudiments as well as how to use gnucash. Welcome to gnucash!
18:14:42 *** oozer has quit IRC
18:39:47 *** tuxd00d has quit IRC
18:42:52 *** hoijui has quit IRC
18:43:46 *** hasdf has quit IRC
18:57:48 *** Simon has quit IRC
18:58:21 *** Simon has joined #gnucash
19:17:39 *** bob_ has quit IRC
19:51:50 *** jotrago1 has joined #gnucash
19:52:43 *** jotrago has quit IRC
19:52:44 *** jotrago1 is now known as jotrago
19:57:41 *** Crof has left #gnucash
19:57:58 *** Crof has joined #gnucash
20:20:08 *** Simon has quit IRC
20:22:14 *** Simon has joined #gnucash
20:25:31 *** oozer has joined #gnucash
20:32:53 *** Cuare has quit IRC
20:47:52 *** User_ has joined #gnucash
20:53:33 <chris> lmat i think my branch is safe. i don't know how to fix python bindings.
20:55:17 *** User_ has quit IRC
21:06:38 <chris> lmat I think it's a good strategy to plan commits around specific functions rather than per-file as I did
21:09:58 *** Heisenburg has joined #gnucash
21:12:48 <Crof> So I'm looking to get into helping out an open source project. I'd love to see myself make a bug fix and get it included in a project...is this one too complex as a first project to get involved in? My biggest problems will be I've never coded with others so the pull/commit/branch concept is going to be my worst problem at first (in any open source project)
21:14:55 <Crof> That and I love personal finance - so finding GNUcash has made me so happy that I'd love to help out if I can. Saw this page (https://wiki.gnucash.org/wiki/GnuCash#Getting_involved_in_the_GnuCash_project), but haven't started down the path of getting the source code yet.
21:20:13 *** Heisenburg has quit IRC
21:20:34 *** kus has joined #gnucash
21:38:17 *** ArtGravity has quit IRC
22:03:08 *** caxa has joined #gnucash
22:06:58 *** caxa has quit IRC
22:11:44 *** oozer has quit IRC
22:26:27 *** User has joined #gnucash
22:28:41 *** Crof has quit IRC
22:38:34 *** User has quit IRC
23:06:02 *** wget has quit IRC
23:06:27 *** wget has joined #gnucash
23:31:53 *** kus has quit IRC