Testing

[Derek Atkins]

Testing email to devel list.

-derek
Sent using my mobile device. Please excuse any typos.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] alpha-testing budgets in 5.x

[Christopher Lam]

On Tue, 4 Jan 2022 at 22:21, Adrien Monteleone <
adrien.montele...@lusfiber.net> wrote:

> On 1/4/22 10:40 AM, Christopher Lam wrote:
> > Experienced Users,
> >
> > The upcoming 5.x series (master branch) currently has a one-time fix for
> > budgets to ensure they're internally stored as unreversed numbers.
> > Currently (up to 4.x) budgeting $1000 income into $600 expense and $400
> > liability repayment are stored as +1000, +600, +400. They should be
> stored
> > internally as -1000, +600, +400 amounts, as per usual accounting
> equation.
>
> I would nit-pick the assertion of 'usual accounting equation'. I've only
> seen one form of it, in any reference, and short of any further
> 'factoring' it looks like this:
>

(snip)

The internal representation for *all* GnuCash transactional data has always
(IIUC) followed the convention "asset + liability + equity + income +
expense == 0". This is what I meant by the GnuCash accounting equation.
This dictates the amounts and signs saved in the XML/SQL. This also applies
to budget amounts, except budget income amounts. This will be modified in
5.x.

Any sign reversal *for display* aims to follow the global pref "Reverse
Balanced Accounts". This is stored in
https://wiki.gnucash.org/wiki/Configuration_Locations#GSettings -- on
Windows it'll be the systemwide registry
Computer\HKEY_CURRENT_USER\SOFTWARE\GSettings\org\gnucash\GnuCash\general

HTH, C
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] alpha-testing budgets in 5.x

[Adrien Monteleone]

Thanks, that will save some time.

Regards,
Adrien

On 1/4/22 11:54 AM, john wrote:

Linux users can also get a flatpak nightly from 
https://code.gnucash.org/builds/flatpak/master 
.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] alpha-testing budgets in 5.x

[Adrien Monteleone]

On 1/4/22 10:40 AM, Christopher Lam wrote:

Experienced Users,

The upcoming 5.x series (master branch) currently has a one-time fix for
budgets to ensure they're internally stored as unreversed numbers.
Currently (up to 4.x) budgeting $1000 income into $600 expense and $400
liability repayment are stored as +1000, +600, +400. They should be stored
internally as -1000, +600, +400 amounts, as per usual accounting equation.


I would nit-pick the assertion of 'usual accounting equation'. I've only 
seen one form of it, in any reference, and short of any further 
'factoring' it looks like this:


Assets = Liabilities + (Income - Expenses) + Equity

ALL of those terms are positive and a single operand is negative.


But somewhere along the way, someone decided to implement this instead:

Assets + (-Liabilities) + (-Income) + Expenses + (-Equity) = 0

Where the credit accounts are moved to the left and preference signed.

There would be no need for this conundrum with the budget or other parts 
of the UI, if the real equation were to be implemented.


But I digress, because I know that won't be changed.


The internal numbers assume the reversal pref is "Credit Accounts". This
means the budgets are currently functioning well *only* if reversal
preference is set to credit-accounts

A obligatory one-time fix is suggested and applied on the master branch,
applying some heuristics and negating the numbers, and will render the
datafile unreadable on GnuCash prior to 3.7. It is *not* an option to make
the one-time fix optional, because this will mean maintaining two code
paths in perpetuity. However I'm not sure if it is debugged enough.

I'd like to ask experienced users to test from the master branch, either as
win32 nightlies https://code.gnucash.org/builds/win32/master/ (4-jan-2022
onwards) or building on linux, and report back of the new budget is *less*
buggy than in 4.x maint series. Please do NOT test master on your
production datafile.

If there are unsolvable bugs, then I'll suggest that the one-time fix
change must be undone, and someone else may decide to try again.


What's the time frame?

I'm about to finish my 2022 budget, I can compare 4.9 to 5.x

Regards,
Adrien

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] alpha-testing budgets in 5.x

[john]

> On Jan 4, 2022, at 8:40 AM, Christopher Lam  wrote:
> 
> Experienced Users,
> 
> The upcoming 5.x series (master branch) currently has a one-time fix for
> budgets to ensure they're internally stored as unreversed numbers.
> Currently (up to 4.x) budgeting $1000 income into $600 expense and $400
> liability repayment are stored as +1000, +600, +400. They should be stored
> internally as -1000, +600, +400 amounts, as per usual accounting equation.
> The internal numbers assume the reversal pref is "Credit Accounts". This
> means the budgets are currently functioning well *only* if reversal
> preference is set to credit-accounts
> 
> A obligatory one-time fix is suggested and applied on the master branch,
> applying some heuristics and negating the numbers, and will render the
> datafile unreadable on GnuCash prior to 3.7. It is *not* an option to make
> the one-time fix optional, because this will mean maintaining two code
> paths in perpetuity. However I'm not sure if it is debugged enough.
> 
> I'd like to ask experienced users to test from the master branch, either as
> win32 nightlies https://code.gnucash.org/builds/win32/master/ (4-jan-2022
> onwards) or building on linux, and report back of the new budget is *less*
> buggy than in 4.x maint series. Please do NOT test master on your
> production datafile.
> 
> If there are unsolvable bugs, then I'll suggest that the one-time fix
> change must be undone, and someone else may decide to try again.

Linux users can also get a flatpak nightly from 
https://code.gnucash.org/builds/flatpak/master 
.

Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] alpha-testing budgets in 5.x

[Christopher Lam]

Experienced Users,

The upcoming 5.x series (master branch) currently has a one-time fix for
budgets to ensure they're internally stored as unreversed numbers.
Currently (up to 4.x) budgeting $1000 income into $600 expense and $400
liability repayment are stored as +1000, +600, +400. They should be stored
internally as -1000, +600, +400 amounts, as per usual accounting equation.
The internal numbers assume the reversal pref is "Credit Accounts". This
means the budgets are currently functioning well *only* if reversal
preference is set to credit-accounts

A obligatory one-time fix is suggested and applied on the master branch,
applying some heuristics and negating the numbers, and will render the
datafile unreadable on GnuCash prior to 3.7. It is *not* an option to make
the one-time fix optional, because this will mean maintaining two code
paths in perpetuity. However I'm not sure if it is debugged enough.

I'd like to ask experienced users to test from the master branch, either as
win32 nightlies https://code.gnucash.org/builds/win32/master/ (4-jan-2022
onwards) or building on linux, and report back of the new budget is *less*
buggy than in 4.x maint series. Please do NOT test master on your
production datafile.

If there are unsolvable bugs, then I'll suggest that the one-time fix
change must be undone, and someone else may decide to try again.

C
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[andygoblins]

On April 26, 2020 6:21:52 PM UTC, Geert Janssens  
wrote:
>Did you uninstall the result of "ninja install" before running the
>second test ?

No, silly me. If I uninstall first, I get the same error. The binaries must be 
looking in the install directory instead of the build directory.

I guess I could just test from the install directory, but it bothers me that 
the python tests work fine in the build directory without an install.

I'm sure I'm just missing something really obvious now.

>
>Also did you follow Rob Gowin's suggestion about using a space instead
>of a semicolon when 
>setting GNC_UNINSTALLED=1 ?
>

Yeah, I ran "export" on all my variables, and got the same result.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Geert Janssens]

Op zondag 26 april 2020 16:57:49 CEST schreef Andy Goblins:
> Mark, I do not get any of the errors you get when running with '--debug
> --test' - the python test stuff runs fine for me: it says, "Hello from
> python!" and then prints a bunch of tests. 
> So I did some more playing, and discovered:
> 1. If I run 'ninja install' the installed version loads the libraries
> correctly.
> 2. If I re-build gnucash with a build location of
> /gnucash-git/build instead of /some/other/place/build the libraries load
> correctly.

Did you uninstall the result of "ninja install" before running the second test ?

Also did you follow Rob Gowin's suggestion about using a space instead of a 
semicolon when 
setting GNC_UNINSTALLED=1 ?

> I'm guessing that most people keep their 'build' directory in the root of
> the git repository rather than in a different folder, and there must be
> some hard-coded references to this that messes up builds in alternative
> directories.

I always build outside of the git repository. But to be honest I haven't tried 
the python bindings 
in a while. I'll try myself in the next few days and see what happens.

Regards,

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Mark]

Great. Glad that you managed to figure it out.
I tried a few times to see if I could find what is causing my error
messages and try to fix it, but never got anywhere. Just seemed to get
entangled in an ever-expanding maze of conflicting libs and versions...
Finally I just gave up and stopped worrying about it since my gnucash
always works without problem even showing those warnings.

cheers,

*Mark*


*episte...@gmail.com *
*(613) 447-5385*



On Sun, Apr 26, 2020 at 10:57 AM Andy Goblins  wrote:

> Mark, I do not get any of the errors you get when running with '--debug
> --test' - the python test stuff runs fine for me: it says, "Hello from
> python!" and then prints a bunch of tests.
>
> So I did some more playing, and discovered:
> 1. If I run 'ninja install' the installed version loads the libraries
> correctly.
> 2. If I re-build gnucash with a build location of /gnucash-git/build
> instead of /some/other/place/build the libraries load correctly.
>
> I'm guessing that most people keep their 'build' directory in the root of
> the git repository rather than in a different folder, and there must be
> some hard-coded references to this that messes up builds in alternative
> directories.
>
>
> *Sent:* Saturday, April 25, 2020 at 5:17 PM
> *From:* "Mark" 
> *To:* "andygoblins" 
> *Cc:* "Geert Janssens" , "gnucash-devel" <
> gnucash-devel@gnucash.org>
> *Subject:* Re: [GNC-dev] Fwd: Testing python
> Unfortunately, we are beyond where I can help you with the build details,
> but I can at least give my experience for comparison. I had never tried it
> before, but I went to my most recent build directory and ran the gnucash
> binary directly from there. It ran fine for me, in the sense that it didn't
> give any different errors than when I run the installed binary. And I find
> that, whatever these warnings may mean about the build, they DO NOT prevent
> gnucash from opening and DO NOT seem to cause any problems in the
> functioning at all that I ever notice. This is my output, for information:
>
> 2012 > bin/gnucash --version
> GnuCash 3.10
> Build ID: 3.10+(2020-04-11)
> 2013 > bin/gnucash --debug --extra
> Traceback (most recent call last):
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
> line 14, in swig_import_helper
> return importlib.import_module(mname)
>   File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1030, in _gcd_import
>   File "", line 1007, in _find_and_load
>   File "", line 986, in
> _find_and_load_unlocked
>   File "", line 666, in _load_unlocked
>   File "", line 565, in module_from_spec
>   File "", line 1108, in
> create_module
>   File "", line 228, in
> _call_with_frames_removed
> ImportError:
> /newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/_gnucash_core_c.so:
> undefined symbol: forkpty
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/share/gnucash/python/init.py",
> line 2, in 
> import gnucash._sw_app_utils as _sw_app_utils
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/__init__.py",
> line 6, in 
> from gnucash.gnucash_core import *
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core.py",
> line 31, in 
> import gnucash.gnucash_core_c as gnucash_core_c
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
> line 17, in 
> _gnucash_core_c = swig_import_helper()
>   File
> "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
> line 16, in swig_import_helper
> return importlib.import_module('_gnucash_core_c')
>   File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> ModuleNotFoundError: No module named '_gnucash_core_c'
> Found Finance::Quote version 1.49.
>
>
> *Mark*
>
>
> *episte...@gmail.com *
> *(613) 447-5385*
>
>
>
> On Sat, Apr 25, 2020 at 2:54 

Re: [GNC-dev] Fwd: Testing python

[Andy Goblins]

   Mark, I do not get any of the errors you get when running with '--debug
   --test' - the python test stuff runs fine for me: it says, "Hello from
   python!" and then prints a bunch of tests.

   So I did some more playing, and discovered:
   1. If I run 'ninja install' the installed version loads the libraries
   correctly.
   2. If I re-build gnucash with a build location of /gnucash-git/build
   instead of /some/other/place/build the libraries load correctly.

   I'm guessing that most people keep their 'build' directory in the root
   of the git repository rather than in a different folder, and there must
   be some hard-coded references to this that messes up builds in
   alternative directories.


   Sent: Saturday, April 25, 2020 at 5:17 PM
   From: "Mark" 
   To: "andygoblins" 
   Cc: "Geert Janssens" , "gnucash-devel"
   
   Subject: Re: [GNC-dev] Fwd: Testing python
   Unfortunately, we are beyond where I can help you with the build
   details, but I can at least give my experience for comparison. I had
   never tried it before, but I went to my most recent build directory and
   ran the gnucash binary directly from there. It ran fine for me, in the
   sense that it didn't give any different errors than when I run the
   installed binary. And I find that, whatever these warnings may mean
   about the build, they DO NOT prevent gnucash from opening and DO NOT
   seem to cause any problems in the functioning at all that I ever
   notice. This is my output, for information:

   2012 > bin/gnucash --version
   GnuCash 3.10
   Build ID: 3.10+(2020-04-11)
   2013 > bin/gnucash --debug --extra
   Traceback (most recent call last):
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/lib/python3.9/site-packages/gnucash/gnucash_core_c.py", line 14, in
   swig_import_helper
   return importlib.import_module(mname)
 File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
   import_module
   return _bootstrap._gcd_import(name[level:], package, level)
 File "", line 1030, in _gcd_import
 File "", line 1007, in _find_and_load
 File "", line 986, in
   _find_and_load_unlocked
 File "", line 666, in _load_unlocked
 File "", line 565, in module_from_spec
 File "", line 1108, in
   create_module
 File "", line 228, in
   _call_with_frames_removed
   ImportError:
   /newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12
   /lib/python3.9/site-packages/gnucash/_gnucash_core_c.so: undefined
   symbol: forkpty
   During handling of the above exception, another exception occurred:
   Traceback (most recent call last):
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/share/gnucash/python/init.py", line 2, in 
   import gnucash._sw_app_utils as _sw_app_utils
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/lib/python3.9/site-packages/gnucash/__init__.py", line 6, in 
   from gnucash.gnucash_core import *
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/lib/python3.9/site-packages/gnucash/gnucash_core.py", line 31, in
   
   import gnucash.gnucash_core_c as gnucash_core_c
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/lib/python3.9/site-packages/gnucash/gnucash_core_c.py", line 17, in
   
   _gnucash_core_c = swig_import_helper()
 File
   "/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-1
   2/lib/python3.9/site-packages/gnucash/gnucash_core_c.py", line 16, in
   swig_import_helper
   return importlib.import_module('_gnucash_core_c')
 File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
   import_module
   return _bootstrap._gcd_import(name[level:], package, level)
   ModuleNotFoundError: No module named '_gnucash_core_c'
   Found Finance::Quote version 1.49.

   Mark

   [1]episte...@gmail.com
   (613) 447-5385



   On Sat, Apr 25, 2020 at 2:54 PM andygoblins <[2]andygobl...@gmx.com>
   wrote:

   I get the same issue when running the gnucash binary out of the build
   directory. Do I need to set a different environment variable so gnucash
   loads the correct .so files?

   On April 24, 2020 12:16:22 PM UTC, Geert Janssens
   <[3]geert.gnuc...@kobaltwit.be> wrote:

 Ok, so it looks like an issue with how gnucash finds its libraries
 from within the build directory, rather than from the installation
 directory.


 Can you run gnucash itself properly from the build directory ?


 Regards,


 Geert


 Op vrijdag 24 april 2020 00:37:37 CEST schreef andygoblins:

 > I'm building from git master. I just run "ninja build" without

Re: [GNC-dev] Fwd: Testing python

[Mark]

Unfortunately, we are beyond where I can help you with the build details,
but I can at least give my experience for comparison. I had never tried it
before, but I went to my most recent build directory and ran the gnucash
binary directly from there. It ran fine for me, in the sense that it didn't
give any different errors than when I run the installed binary. And I find
that, whatever these warnings may mean about the build, they DO NOT prevent
gnucash from opening and DO NOT seem to cause any problems in the
functioning at all that I ever notice. This is my output, for information:

2012 > bin/gnucash --version
GnuCash 3.10
Build ID: 3.10+(2020-04-11)
2013 > bin/gnucash --debug --extra
Traceback (most recent call last):
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
line 14, in swig_import_helper
return importlib.import_module(mname)
  File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 666, in _load_unlocked
  File "", line 565, in module_from_spec
  File "", line 1108, in create_module
  File "", line 228, in
_call_with_frames_removed
ImportError:
/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/_gnucash_core_c.so:
undefined symbol: forkpty

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/share/gnucash/python/init.py",
line 2, in 
import gnucash._sw_app_utils as _sw_app_utils
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/__init__.py",
line 6, in 
from gnucash.gnucash_core import *
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core.py",
line 31, in 
import gnucash.gnucash_core_c as gnucash_core_c
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
line 17, in 
_gnucash_core_c = swig_import_helper()
  File
"/newdata/dev/Gnucash/RELEASES/gnucash-3.10/build_with-python_2020-04-12/lib/python3.9/site-packages/gnucash/gnucash_core_c.py",
line 16, in swig_import_helper
return importlib.import_module('_gnucash_core_c')
  File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_gnucash_core_c'
Found Finance::Quote version 1.49.

*Mark*


*episte...@gmail.com *
*(613) 447-5385*



On Sat, Apr 25, 2020 at 2:54 PM andygoblins  wrote:

> I get the same issue when running the gnucash binary out of the build
> directory. Do I need to set a different environment variable so gnucash
> loads the correct .so files?
>
> On April 24, 2020 12:16:22 PM UTC, Geert Janssens <
> geert.gnuc...@kobaltwit.be> wrote:
>>
>> Ok, so it looks like an issue with how gnucash finds its libraries from
>> within the build directory, rather than from the installation directory.
>>
>>
>>
>> Can you run gnucash itself properly from the build directory ?
>>
>>
>>
>> Regards,
>>
>>
>>
>> Geert
>>
>>
>>
>> Op vrijdag 24 april 2020 00:37:37 CEST schreef andygoblins:
>>
>> > I'm building from git master. I just run "ninja build" without an
>> install
>>
>> > and do my testing straight from the build directory.
>>
>> >
>>
>> > The last commit in my copy of master was on April 14. Does the master
>> branch
>>
>> > include the 3.10 build fix?
>>
>> > On April 21, 2020 8:23:40 PM UTC, Mark  wrote:
>>
>> > >Yea, I ran 'sudo ninja install'.
>>
>> > >Andy, from your initial email, can't tell for sure but possibly you
>>
>> > >built a
>>
>> > >venv right after your ninja build without doing an install?
>>
>> > >
>>
>> > >*Mark*
>>
>> > >
>>
>> > >
>>
>> > >*episte...@gmail.com *
>>
>> > >*(613) 447-5385*
>>
>> > >
>>
>> > >
>>
>> > >
>>
>> > >On Tue, Apr 21, 2020 at 10:18 AM Geert Janssens
>>
>> >

Re: [GNC-dev] Fwd: Testing python

[andygoblins]

I get the same issue when running the gnucash binary out of the build 
directory. Do I need to set a different environment variable so gnucash loads 
the correct .so files?

On April 24, 2020 12:16:22 PM UTC, Geert Janssens  
wrote:
>Ok, so it looks like an issue with how gnucash finds its libraries from
>within the build directory, 
>rather than from the installation directory.
>
>Can you run gnucash itself properly from the build directory ?
>
>Regards,
>
>Geert
>
>Op vrijdag 24 april 2020 00:37:37 CEST schreef andygoblins:
>> I'm building from git master. I just run "ninja build" without an
>install
>> and do my testing straight from the build directory.
>> 
>> The last commit in my copy of master was on April 14. Does the master
>branch
>> include the 3.10 build fix?
>> On April 21, 2020 8:23:40 PM UTC, Mark  wrote:
>> >Yea, I ran 'sudo ninja install'.
>> >Andy, from your initial email, can't tell for sure but possibly you
>> >built a
>> >venv right after your ninja build without doing an install?
>> >
>> >*Mark*
>> >
>> >
>> >*episte...@gmail.com *
>> >*(613) 447-5385*
>> >
>> >
>> >
>> >On Tue, Apr 21, 2020 at 10:18 AM Geert Janssens
>> >
>> >
>> >wrote:
>> >> Op dinsdag 21 april 2020 15:01:33 CEST schreef Mark:
>> >> > My bindings are built from the git source code for the 3.10
>release
>> >> > 
>> >> > (gnucash-3.10.tar.bz2):
>> >> > 
>> >> > 
>> >> > 
>> >> > /opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash
>4.4.20
>> >> > 
>> >> > 2013 > ./gnucash --version
>> >> > 
>> >> > GnuCash 3.10
>> >> > 
>> >> > Build ID: 3.10+(2020-04-11)
>> >> > 
>> >> > 
>> >> > 
>> >> > So maybe I have a slightly later version of 3.10 where this bug
>was
>> >> 
>> >> already
>> >> 
>> >> > fixed?
>> >> 
>> >> No, I don't think so. The fix was only included on 2020-04-12 and
>is
>> >
>> >not
>> >
>> >> part of the release tarball.
>> >> 
>> >> 
>> >> 
>> >> But there are several factors at play. Do you run "make install" ?
>If
>> >
>> >so,
>> >
>> >> the python bindings would properly find the libraries in the
>> >
>> >installation
>> >
>> >> directory. If not, they should be found in the build directory,
>but I
>> >> expect that to fail without the aforementioned patch.
>> >> 
>> >> 
>> >> 
>> >> Regards,
>> >> 
>> >> 
>> >> 
>> >> Geert

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Geert Janssens]

Ok, so it looks like an issue with how gnucash finds its libraries from within 
the build directory, 
rather than from the installation directory.

Can you run gnucash itself properly from the build directory ?

Regards,

Geert

Op vrijdag 24 april 2020 00:37:37 CEST schreef andygoblins:
> I'm building from git master. I just run "ninja build" without an install
> and do my testing straight from the build directory.
> 
> The last commit in my copy of master was on April 14. Does the master branch
> include the 3.10 build fix?
> On April 21, 2020 8:23:40 PM UTC, Mark  wrote:
> >Yea, I ran 'sudo ninja install'.
> >Andy, from your initial email, can't tell for sure but possibly you
> >built a
> >venv right after your ninja build without doing an install?
> >
> >*Mark*
> >
> >
> >*episte...@gmail.com *
> >*(613) 447-5385*
> >
> >
> >
> >On Tue, Apr 21, 2020 at 10:18 AM Geert Janssens
> >
> >
> >wrote:
> >> Op dinsdag 21 april 2020 15:01:33 CEST schreef Mark:
> >> > My bindings are built from the git source code for the 3.10 release
> >> > 
> >> > (gnucash-3.10.tar.bz2):
> >> > 
> >> > 
> >> > 
> >> > /opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash 4.4.20
> >> > 
> >> > 2013 > ./gnucash --version
> >> > 
> >> > GnuCash 3.10
> >> > 
> >> > Build ID: 3.10+(2020-04-11)
> >> > 
> >> > 
> >> > 
> >> > So maybe I have a slightly later version of 3.10 where this bug was
> >> 
> >> already
> >> 
> >> > fixed?
> >> 
> >> No, I don't think so. The fix was only included on 2020-04-12 and is
> >
> >not
> >
> >> part of the release tarball.
> >> 
> >> 
> >> 
> >> But there are several factors at play. Do you run "make install" ? If
> >
> >so,
> >
> >> the python bindings would properly find the libraries in the
> >
> >installation
> >
> >> directory. If not, they should be found in the build directory, but I
> >> expect that to fail without the aforementioned patch.
> >> 
> >> 
> >> 
> >> Regards,
> >> 
> >> 
> >> 
> >> Geert


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Testing python

[Rob Gowin]

On Sun, Apr 19, 2020 at 2:19 PM Andy Goblins  wrote:

>I also tried skipping the virtual environment and just running
>"GNC_UNINSTALLED=1;GNC_BUILDDIR=dir>;PYTHONPATH=$GNC_BUILDDIR/lib/python3.8/site-packages:$GNC_BUILDDIR
>/lib/gnucash python" just like the cmake tests use, but I get the same
>result; it's not finding the libgncmod-backend stuff in
>build/lib/gnucash.
>

You almost had it. :-) The semicolons in the above command line make it
such that, for example, "GNC_UNINSTALLED=1" is its own (no-op) command that
does not affect the python command.

Try this in your virtual environment:

(gnucash-build) robg@kubuntu01:~/gnucash-build$ GNC_UNINSTALLED=1
GNC_BUILDDIR=`pwd` python3

Python 3.6.9 (default, Apr 18 2020, 01:56:04)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import gnucash
* 23:52:18  WARN  no preferences backend loaded, or the
backend doesn't define register_cb, returning 0
* 23:52:18  WARN  no preferences backend loaded, or the
backend doesn't define register_cb, returning 0
* 23:52:18  WARN  no preferences backend loaded, or the
backend doesn't define register_cb, returning 0
* 23:52:18  WARN  no preferences backend loaded, or the
backend doesn't define register_cb, returning 0
* 23:52:18  WARN  no preferences backend loaded, or the
backend doesn't define register_cb, returning 0
>>> import gnucash.gnucash_core_c
>>> print(gnucash.gnucash_core_c.CREC)
c

I don't know what the deal with the preference backend stuff is, but maybe
it won't affect your testing.

Rob
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[andygoblins]

I'm building from git master. I just run "ninja build" without an install and 
do my testing straight from the build directory.

The last commit in my copy of master was on April 14. Does the master branch 
include the 3.10 build fix?

On April 21, 2020 8:23:40 PM UTC, Mark  wrote:
>Yea, I ran 'sudo ninja install'.
>Andy, from your initial email, can't tell for sure but possibly you
>built a
>venv right after your ninja build without doing an install?
>
>*Mark*
>
>
>*episte...@gmail.com *
>*(613) 447-5385*
>
>
>
>On Tue, Apr 21, 2020 at 10:18 AM Geert Janssens
>
>wrote:
>
>> Op dinsdag 21 april 2020 15:01:33 CEST schreef Mark:
>>
>> > My bindings are built from the git source code for the 3.10 release
>>
>> > (gnucash-3.10.tar.bz2):
>>
>> >
>>
>> > /opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash 4.4.20
>>
>> > 2013 > ./gnucash --version
>>
>> > GnuCash 3.10
>>
>> > Build ID: 3.10+(2020-04-11)
>>
>> >
>>
>> > So maybe I have a slightly later version of 3.10 where this bug was
>> already
>>
>> > fixed?
>>
>>
>>
>> No, I don't think so. The fix was only included on 2020-04-12 and is
>not
>> part of the release tarball.
>>
>>
>>
>> But there are several factors at play. Do you run "make install" ? If
>so,
>> the python bindings would properly find the libraries in the
>installation
>> directory. If not, they should be found in the build directory, but I
>> expect that to fail without the aforementioned patch.
>>
>>
>>
>> Regards,
>>
>>
>>
>> Geert
>>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Mark]

Yea, I ran 'sudo ninja install'.
Andy, from your initial email, can't tell for sure but possibly you built a
venv right after your ninja build without doing an install?

*Mark*


*episte...@gmail.com *
*(613) 447-5385*



On Tue, Apr 21, 2020 at 10:18 AM Geert Janssens 
wrote:

> Op dinsdag 21 april 2020 15:01:33 CEST schreef Mark:
>
> > My bindings are built from the git source code for the 3.10 release
>
> > (gnucash-3.10.tar.bz2):
>
> >
>
> > /opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash 4.4.20
>
> > 2013 > ./gnucash --version
>
> > GnuCash 3.10
>
> > Build ID: 3.10+(2020-04-11)
>
> >
>
> > So maybe I have a slightly later version of 3.10 where this bug was
> already
>
> > fixed?
>
>
>
> No, I don't think so. The fix was only included on 2020-04-12 and is not
> part of the release tarball.
>
>
>
> But there are several factors at play. Do you run "make install" ? If so,
> the python bindings would properly find the libraries in the installation
> directory. If not, they should be found in the build directory, but I
> expect that to fail without the aforementioned patch.
>
>
>
> Regards,
>
>
>
> Geert
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Geert Janssens]

Op dinsdag 21 april 2020 15:01:33 CEST schreef Mark:
> My bindings are built from the git source code for the 3.10 release
> (gnucash-3.10.tar.bz2):
> 
> /opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash 4.4.20
> 2013 > ./gnucash --version
> GnuCash 3.10
> Build ID: 3.10+(2020-04-11)
> 
> So maybe I have a slightly later version of 3.10 where this bug was already
> fixed?

No, I don't think so. The fix was only included on 2020-04-12 and is not part 
of the release 
tarball.

But there are several factors at play. Do you run "make install" ? If so, the 
python bindings 
would properly find the libraries in the installation directory. If not, they 
should be found in the 
build directory, but I expect that to fail without the aforementioned patch.

Regards,

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Mark]

My bindings are built from the git source code for the 3.10 release
(gnucash-3.10.tar.bz2):

/opt/bin | Tue Apr 21 08:55:25 | marksa@Ares-A717-72G | bash 4.4.20
2013 > ./gnucash --version
GnuCash 3.10
Build ID: 3.10+(2020-04-11)

So maybe I have a slightly later version of 3.10 where this bug was already
fixed?


*Mark*
*episte...@gmail.com *
*(613) 447-5385*



On Tue, Apr 21, 2020 at 8:33 AM Geert Janssens 
wrote:

> Hi,
>
>
>
> I presume you are building from git. What commit are you building from ?
> There was an issue with detecting uninstalled builds that got fix right
> after the 3.10 release. So you'd need a very recent checkout to have this
> fix. This bug may be causing the symptoms you experience.
>
>
>
> Regards,
>
>
>
> Geert
>
>
>
> Op dinsdag 21 april 2020 05:15:53 CEST schreef Andy Goblins:
>
> > My environment seems much the same as yours. But for some reason, it
>
> > can't find the gncmod-backend-* files, which are compiled into the
>
> > build/lib/gnucash directory:
>
> >
>
> > Python 3.8.2 (default, Apr 8 2020, 14:31:25)
>
> > [GCC 9.3.0] on linux
>
> > Type "help", "copyright", "credits" or "license" for more information.
>
> >
>
> > >>> import sys
>
> > >>> print(sys.path)
>
> >
>
> > ['', '/usr/lib/python38.zip', '/usr/lib/python3.8',
>
> > '/usr/lib/python3.8/lib-dynload',
>
> > '/home/andy/hack/gnucash/build/lib/python3.8/site-packages',
>
> > '/home/andy/.local/lib/python3.8/site-packages',
>
> > '/usr/lib/python3.8/site-packages']
>
> >
>
> > >>> import gnucash
>
> >
>
> > * 22:04:55 WARN  failed to load gncmod-backend-dbi from
>
> > relative path
>
> > * 22:04:55 ERROR  required library gncmod-backend-dbi not
>
> > found.
>
> > * 22:04:55 WARN  failed to load gncmod-backend-xml from
>
> > relative path
>
> > * 22:04:55 ERROR  required library gncmod-backend-xml not
>
> > found.
>
> >
>
> > >>> import gnucash.gnucash_core_c
>
> > >>> print(gnucash.gnucash_core_c.CREC)
>
> >
>
> > c
>
> >
>
> > >>> exit()
>
> >
>
> > (build) ~/hack/gnucash/build > ls -a lib/python3.8/site-packages
>
> > total 40
>
> > drwxr-xr-x 9 andy andy 4096 Apr 16 18:06 .
>
> > drwxr-xr-x 3 andy andy 4096 Apr 16 17:46 ..
>
> > -rw-r--r-- 1 andy andy 126 Apr 16 18:06 easy_install.py
>
> > drwxr-xr-x 3 andy andy 4096 Apr 16 18:00 gnucash
>
> > drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pip
>
> > drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 pip-19.2.3.dist-info
>
> > drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pkg_resources
>
> > drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 __pycache__
>
> > drwxr-xr-x 6 andy andy 4096 Apr 16 18:06 setuptools
>
> > drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 setuptools-41.2.0.dist-info
>
> > (build) ~/hack/gnucash/build > ls -a
>
> > lib/python3.8/site-packages/gnucash
>
> > total 2556
>
> > drwxr-xr-x 3 andy andy 4096 Apr 16 18:00 .
>
> > drwxr-xr-x 9 andy andy 4096 Apr 16 18:06 ..
>
> > -rw-r--r-- 1 andy andy 552 Apr 16 18:00 app_utils.py
>
> > -rw-r--r-- 1 andy andy 9286 Apr 16 18:00 function_class.py
>
> > -rw-r--r-- 1 andy andy 14460 Apr 16 18:00 gnucash_business.py
>
> > -rw-r--r-- 1 andy andy 272455 Apr 16 18:00 gnucash_core_c.py
>
> > -rwxr-xr-x 1 andy andy 1872240 Apr 16 18:00 _gnucash_core_c.so
>
> > -rw-r--r-- 1 andy andy 33878 Apr 16 18:00 gnucash_core.py
>
> > -rw-r--r-- 1 andy andy 443 Apr 16 18:00 __init__.py
>
> > drwxr-xr-x 2 andy andy 4096 Apr 16 18:00 __pycache__
>
> > -rw-r--r-- 1 andy andy 3772 Apr 16 17:58 sw_app_utils.py
>
> > -rwxr-xr-x 1 andy andy 163488 Apr 16 17:58 _sw_app_utils.so
>
> > -rw-r--r-- 1 andy andy 14200 Apr 16 17:59 sw_core_utils.py
>
> > -rwxr-xr-x 1 andy andy 196176 Apr 16 17:59 _sw_core_utils.so
>
> >
>
> > Sent: Sunday, April 19, 2020 at 10:43 AM
>
> > From: "Mark" 
>
> > To: "gnucash-devel" 
>
> > Subject: [GNC-dev] Fwd: Testing python
>
> > Forgot to reply all...
>
> > *Mark*
>
> > *episte...@gmail.com *
>
> > *(613) 447-5385*
>
> > -- Forwarded message -
>
> > From: Mark 
>
> > Date: Sun, Apr 19, 2020 at 11:42 AM
>
> > Subject: Re: [GNC-dev] Testing python
>
> > To: Andy Goblins 
>
> > From a terminal with your venv activated, can you show the actual
>

Re: [GNC-dev] Fwd: Testing python

[Geert Janssens]

Hi,

I presume you are building from git. What commit are you building from ? There 
was an issue 
with detecting uninstalled builds that got fix right after the 3.10 release. So 
you'd need a very 
recent checkout to have this fix. This bug may be causing the symptoms you 
experience.

Regards,

Geert

Op dinsdag 21 april 2020 05:15:53 CEST schreef Andy Goblins:
>My environment seems much the same as yours. But for some reason, it
>can't find the gncmod-backend-* files, which are compiled into the
>build/lib/gnucash directory:
> 
>Python 3.8.2 (default, Apr  8 2020, 14:31:25)
>[GCC 9.3.0] on linux
>Type "help", "copyright", "credits" or "license" for more information.
> 
>>>> import sys
>>>> print(sys.path)
> 
>['', '/usr/lib/python38.zip', '/usr/lib/python3.8',
>'/usr/lib/python3.8/lib-dynload',
>'/home/andy/hack/gnucash/build/lib/python3.8/site-packages',
>'/home/andy/.local/lib/python3.8/site-packages',
>'/usr/lib/python3.8/site-packages']
> 
>>>> import gnucash
> 
>* 22:04:55  WARN  failed to load gncmod-backend-dbi from
>relative path
>* 22:04:55 ERROR  required library gncmod-backend-dbi not
>found.
>* 22:04:55  WARN  failed to load gncmod-backend-xml from
>relative path
>* 22:04:55 ERROR  required library gncmod-backend-xml not
>found.
> 
>>>> import gnucash.gnucash_core_c
>>>> print(gnucash.gnucash_core_c.CREC)
> 
>c
> 
>>>> exit()
> 
>(build) ~/hack/gnucash/build > ls -a lib/python3.8/site-packages
>total 40
>drwxr-xr-x 9 andy andy 4096 Apr 16 18:06 .
>drwxr-xr-x 3 andy andy 4096 Apr 16 17:46 ..
>-rw-r--r-- 1 andy andy  126 Apr 16 18:06 easy_install.py
>drwxr-xr-x 3 andy andy 4096 Apr 16 18:00 gnucash
>drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pip
>drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 pip-19.2.3.dist-info
>drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pkg_resources
>drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 __pycache__
>drwxr-xr-x 6 andy andy 4096 Apr 16 18:06 setuptools
>drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 setuptools-41.2.0.dist-info
>(build) ~/hack/gnucash/build > ls -a
>lib/python3.8/site-packages/gnucash
>total 2556
>drwxr-xr-x 3 andy andy4096 Apr 16 18:00 .
>drwxr-xr-x 9 andy andy4096 Apr 16 18:06 ..
>-rw-r--r-- 1 andy andy 552 Apr 16 18:00 app_utils.py
>-rw-r--r-- 1 andy andy9286 Apr 16 18:00 function_class.py
>-rw-r--r-- 1 andy andy   14460 Apr 16 18:00 gnucash_business.py
>-rw-r--r-- 1 andy andy  272455 Apr 16 18:00 gnucash_core_c.py
>-rwxr-xr-x 1 andy andy 1872240 Apr 16 18:00 _gnucash_core_c.so
>-rw-r--r-- 1 andy andy   33878 Apr 16 18:00 gnucash_core.py
>-rw-r--r-- 1 andy andy 443 Apr 16 18:00 __init__.py
>drwxr-xr-x 2 andy andy4096 Apr 16 18:00 __pycache__
>-rw-r--r-- 1 andy andy3772 Apr 16 17:58 sw_app_utils.py
>-rwxr-xr-x 1 andy andy  163488 Apr 16 17:58 _sw_app_utils.so
>-rw-r--r-- 1 andy andy   14200 Apr 16 17:59 sw_core_utils.py
>-rwxr-xr-x 1 andy andy  196176 Apr 16 17:59 _sw_core_utils.so
> 
>Sent: Sunday, April 19, 2020 at 10:43 AM
>From: "Mark" 
>To: "gnucash-devel" 
>Subject: [GNC-dev] Fwd: Testing python
>Forgot to reply all...
>*Mark*
>*episte...@gmail.com *
>*(613) 447-5385*
>-- Forwarded message -
>From: Mark 
>Date: Sun, Apr 19, 2020 at 11:42 AM
>Subject: Re: [GNC-dev] Testing python
>To: Andy Goblins 
>From a terminal with your venv activated, can you show the actual
>output
>you get from a test like so:
>(venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:16:23 |
>marksa@Ares-A717-72G | bash 4.4.20
>2038 > python
>Python 3.9.0a5+ (heads/master-dirty:3e0dd3730b, Apr 12 2020, 06:54:39)
>[GCC 7.5.0] on linux
>Type "help", "copyright", "credits" or "license" for more information.
> 
>>>> import sys
>>>> print(sys.path)
> 
>['', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9',
>'/usr/local/lib/python3.9/lib-dynload',
>'/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages',
>'/home/marksa/.local/lib/python3.9/site-packages',
>'/usr/local/lib/python3.9/site-packages']
> 
>>>> import gnucash
>>>> import gnucash.gnucash_core_c
>>>> print(gnucash.gnucash_core_c.CREC)
> 
>c
> 
>>>> exit()
> 
>This is the simple test I run to make sure I have properly set up a new
>venv for running the gnucash python bindings. I presume you are getting
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Testing python

[Mark]

ass.cpython-39.pyc
matches
/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages/gnucash/function_class.py
# code object from
'/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages/gnucash/__pycache__/function_class.cpython-39.pyc'
import 'gnucash.function_class' #
<_frozen_importlib_external.SourceFileLoader object at 0x7f801167b520>
import 'gnucash.gnucash_core' #
<_frozen_importlib_external.SourceFileLoader object at 0x7f8012047cd0>
import 'gnucash' # <_frozen_importlib_external.SourceFileLoader object at
0x7f8012047ac0>


*>>> import gnucash.gnucash_core_c>>> print(gnucash.gnucash_core_c.CREC)*c


Gives a hell of a lot of output, but hopefully the difference in the output
of my 'import gnucash' and yours can tell you how your venv is different.


cheers,

*Mark*
*episte...@gmail.com *
*(613) 447-5385*



On Mon, Apr 20, 2020 at 11:15 PM Andy Goblins  wrote:

> My environment seems much the same as yours. But for some reason, it can't
> find the gncmod-backend-* files, which are compiled into the
> build/lib/gnucash directory:
>
> Python 3.8.2 (default, Apr  8 2020, 14:31:25)
> [GCC 9.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> print(sys.path)
> ['', '/usr/lib/python38.zip', '/usr/lib/python3.8',
> '/usr/lib/python3.8/lib-dynload',
> '/home/andy/hack/gnucash/build/lib/python3.8/site-packages',
> '/home/andy/.local/lib/python3.8/site-packages',
> '/usr/lib/python3.8/site-packages']
> >>> import gnucash
> * 22:04:55  WARN  failed to load gncmod-backend-dbi from
> relative path
> * 22:04:55 ERROR  required library gncmod-backend-dbi not
> found.
> * 22:04:55  WARN  failed to load gncmod-backend-xml from
> relative path
> * 22:04:55 ERROR  required library gncmod-backend-xml not
> found.
> >>> import gnucash.gnucash_core_c
> >>> print(gnucash.gnucash_core_c.CREC)
> c
> >>> exit()
> (build) ~/hack/gnucash/build > ls -a lib/python3.8/site-packages
> total 40
> drwxr-xr-x 9 andy andy 4096 Apr 16 18:06 .
> drwxr-xr-x 3 andy andy 4096 Apr 16 17:46 ..
> -rw-r--r-- 1 andy andy  126 Apr 16 18:06 easy_install.py
> drwxr-xr-x 3 andy andy 4096 Apr 16 18:00 gnucash
> drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pip
> drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 pip-19.2.3.dist-info
> drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pkg_resources
> drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 __pycache__
> drwxr-xr-x 6 andy andy 4096 Apr 16 18:06 setuptools
> drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 setuptools-41.2.0.dist-info
> (build) ~/hack/gnucash/build > ls -a lib/python3.8/site-packages/gnucash
> total 2556
> drwxr-xr-x 3 andy andy4096 Apr 16 18:00 .
> drwxr-xr-x 9 andy andy4096 Apr 16 18:06 ..
> -rw-r--r-- 1 andy andy 552 Apr 16 18:00 app_utils.py
> -rw-r--r-- 1 andy andy9286 Apr 16 18:00 function_class.py
> -rw-r--r-- 1 andy andy   14460 Apr 16 18:00 gnucash_business.py
> -rw-r--r-- 1 andy andy  272455 Apr 16 18:00 gnucash_core_c.py
> -rwxr-xr-x 1 andy andy 1872240 Apr 16 18:00 _gnucash_core_c.so
> -rw-r--r-- 1 andy andy   33878 Apr 16 18:00 gnucash_core.py
> -rw-r--r-- 1 andy andy 443 Apr 16 18:00 __init__.py
> drwxr-xr-x 2 andy andy4096 Apr 16 18:00 __pycache__
> -rw-r--r-- 1 andy andy    3772 Apr 16 17:58 sw_app_utils.py
> -rwxr-xr-x 1 andy andy  163488 Apr 16 17:58 _sw_app_utils.so
> -rw-r--r-- 1 andy andy   14200 Apr 16 17:59 sw_core_utils.py
> -rwxr-xr-x 1 andy andy  196176 Apr 16 17:59 _sw_core_utils.so
>
> *Sent:* Sunday, April 19, 2020 at 10:43 AM
> *From:* "Mark" 
> *To:* "gnucash-devel" 
> *Subject:* [GNC-dev] Fwd: Testing python
> Forgot to reply all...
>
> *Mark*
>
>
> *episte...@gmail.com *
> *(613) 447-5385*
>
>
>
> -- Forwarded message -
> From: Mark 
> Date: Sun, Apr 19, 2020 at 11:42 AM
> Subject: Re: [GNC-dev] Testing python
> To: Andy Goblins 
>
>
> From a terminal with your venv activated, can you show the actual output
> you get from a test like so:
>
> (venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:16:23 |
> marksa@Ares-A717-72G | bash 4.4.20
> 2038 > python
> Python 3.9.0a5+ (heads/master-dirty:3e0dd3730b, Apr 12 2020, 06:54:39)
> [GCC 7.5.0] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import sys
> >>> print(sys.path)
> ['', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9',
> '/usr/local/lib/python3.9/lib-dynload',
> '/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages',
> '/home/marksa/.local/lib/python3.9/site-packages',
> '/usr/local/lib/python3.9/site-pac

Re: [GNC-dev] Fwd: Testing python

[Andy Goblins]

   My environment seems much the same as yours. But for some reason, it
   can't find the gncmod-backend-* files, which are compiled into the
   build/lib/gnucash directory:

   Python 3.8.2 (default, Apr  8 2020, 14:31:25)
   [GCC 9.3.0] on linux
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import sys
   >>> print(sys.path)
   ['', '/usr/lib/python38.zip', '/usr/lib/python3.8',
   '/usr/lib/python3.8/lib-dynload',
   '/home/andy/hack/gnucash/build/lib/python3.8/site-packages',
   '/home/andy/.local/lib/python3.8/site-packages',
   '/usr/lib/python3.8/site-packages']
   >>> import gnucash
   * 22:04:55  WARN  failed to load gncmod-backend-dbi from
   relative path
   * 22:04:55 ERROR  required library gncmod-backend-dbi not
   found.
   * 22:04:55  WARN  failed to load gncmod-backend-xml from
   relative path
   * 22:04:55 ERROR  required library gncmod-backend-xml not
   found.
   >>> import gnucash.gnucash_core_c
   >>> print(gnucash.gnucash_core_c.CREC)
   c
   >>> exit()
   (build) ~/hack/gnucash/build > ls -a lib/python3.8/site-packages
   total 40
   drwxr-xr-x 9 andy andy 4096 Apr 16 18:06 .
   drwxr-xr-x 3 andy andy 4096 Apr 16 17:46 ..
   -rw-r--r-- 1 andy andy  126 Apr 16 18:06 easy_install.py
   drwxr-xr-x 3 andy andy 4096 Apr 16 18:00 gnucash
   drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pip
   drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 pip-19.2.3.dist-info
   drwxr-xr-x 5 andy andy 4096 Apr 16 18:06 pkg_resources
   drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 __pycache__
   drwxr-xr-x 6 andy andy 4096 Apr 16 18:06 setuptools
   drwxr-xr-x 2 andy andy 4096 Apr 16 18:06 setuptools-41.2.0.dist-info
   (build) ~/hack/gnucash/build > ls -a
   lib/python3.8/site-packages/gnucash
   total 2556
   drwxr-xr-x 3 andy andy4096 Apr 16 18:00 .
   drwxr-xr-x 9 andy andy4096 Apr 16 18:06 ..
   -rw-r--r-- 1 andy andy 552 Apr 16 18:00 app_utils.py
   -rw-r--r-- 1 andy andy9286 Apr 16 18:00 function_class.py
   -rw-r--r-- 1 andy andy   14460 Apr 16 18:00 gnucash_business.py
   -rw-r--r-- 1 andy andy  272455 Apr 16 18:00 gnucash_core_c.py
   -rwxr-xr-x 1 andy andy 1872240 Apr 16 18:00 _gnucash_core_c.so
   -rw-r--r-- 1 andy andy   33878 Apr 16 18:00 gnucash_core.py
   -rw-r--r-- 1 andy andy 443 Apr 16 18:00 __init__.py
   drwxr-xr-x 2 andy andy4096 Apr 16 18:00 __pycache__
   -rw-r--r-- 1 andy andy3772 Apr 16 17:58 sw_app_utils.py
   -rwxr-xr-x 1 andy andy  163488 Apr 16 17:58 _sw_app_utils.so
   -rw-r--r-- 1 andy andy   14200 Apr 16 17:59 sw_core_utils.py
   -rwxr-xr-x 1 andy andy  196176 Apr 16 17:59 _sw_core_utils.so

   Sent: Sunday, April 19, 2020 at 10:43 AM
   From: "Mark" 
   To: "gnucash-devel" 
   Subject: [GNC-dev] Fwd: Testing python
   Forgot to reply all...
   *Mark*
   *episte...@gmail.com *
   *(613) 447-5385*
   -- Forwarded message -
   From: Mark 
   Date: Sun, Apr 19, 2020 at 11:42 AM
   Subject: Re: [GNC-dev] Testing python
   To: Andy Goblins 
   From a terminal with your venv activated, can you show the actual
   output
   you get from a test like so:
   (venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:16:23 |
   marksa@Ares-A717-72G | bash 4.4.20
   2038 > python
   Python 3.9.0a5+ (heads/master-dirty:3e0dd3730b, Apr 12 2020, 06:54:39)
   [GCC 7.5.0] on linux
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import sys
   >>> print(sys.path)
   ['', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9',
   '/usr/local/lib/python3.9/lib-dynload',
   '/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages',
   '/home/marksa/.local/lib/python3.9/site-packages',
   '/usr/local/lib/python3.9/site-packages']
   >>> import gnucash
   >>> import gnucash.gnucash_core_c
   >>> print(gnucash.gnucash_core_c.CREC)
   c
   >>> exit()
   This is the simple test I run to make sure I have properly set up a new
   venv for running the gnucash python bindings. I presume you are getting
   the
   error messages as soon as you try to 'import gnucash'? As far as I can
   tell, as long as you have the properly built bindings in one of the
   site-packages or other directories in your sys.path, you should be able
   to
   run ok. So my venv 'lib/python3.9/site-packages' looks like this:
   (venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:04:19 |
   marksa@Ares-A717-72G | bash 4.4.20
   2010 > go lib/python3.9/site-packages/
   total 12
   drwxrwxr-x 2 marksa marksa 4096 Apr 15 09:12 PyQt5-stubs
   drwxrwxr-x 2 marksa marksa 4096 Apr 15 09:12
   PyQt5_stubs-5.14.2.0.dist-info
   drwxrwxr-x 3 marksa marksa 4096 Apr 12 08:59 gnucash
   (venv39)
   /newdata/dev/git/Python/VENV/venv39/lib/python3.9/site-packages |
   Sun Apr 19 11:04:27 | marksa@Ares-A717-72G | b

[GNC-dev] Fwd: Testing python

[Mark]

Forgot to reply all...

*Mark*


*episte...@gmail.com *
*(613) 447-5385*



-- Forwarded message -
From: Mark 
Date: Sun, Apr 19, 2020 at 11:42 AM
Subject: Re: [GNC-dev] Testing python
To: Andy Goblins 


>From a terminal with your venv activated, can you show the actual output
you get from a test like so:

(venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:16:23 |
marksa@Ares-A717-72G | bash 4.4.20
2038 > python
Python 3.9.0a5+ (heads/master-dirty:3e0dd3730b, Apr 12 2020, 06:54:39)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print(sys.path)
['', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9',
'/usr/local/lib/python3.9/lib-dynload',
'/newdata/dev/Python/VENV/venv39/lib/python3.9/site-packages',
'/home/marksa/.local/lib/python3.9/site-packages',
'/usr/local/lib/python3.9/site-packages']
>>> import gnucash
>>> import gnucash.gnucash_core_c
>>> print(gnucash.gnucash_core_c.CREC)
c
>>> exit()

This is the simple test I run to make sure I have properly set up a new
venv for running the gnucash python bindings. I presume you are getting the
error messages as soon as you try to 'import gnucash'? As far as I can
tell, as long as you have the properly built bindings in one of the
site-packages or other directories in your sys.path, you should be able to
run ok. So my venv 'lib/python3.9/site-packages' looks like this:

(venv39) /newdata/dev/git/Python/VENV/venv39 | Sun Apr 19 11:04:19 |
marksa@Ares-A717-72G | bash 4.4.20
2010 > go lib/python3.9/site-packages/
total 12
drwxrwxr-x 2 marksa marksa 4096 Apr 15 09:12 PyQt5-stubs
drwxrwxr-x 2 marksa marksa 4096 Apr 15 09:12 PyQt5_stubs-5.14.2.0.dist-info
drwxrwxr-x 3 marksa marksa 4096 Apr 12 08:59 gnucash
(venv39) /newdata/dev/git/Python/VENV/venv39/lib/python3.9/site-packages |
Sun Apr 19 11:04:27 | marksa@Ares-A717-72G | bash 4.4.20
2011 > go gnucash/
total 14344
drwxrwxr-x 2 marksa marksa4096 Apr 14 22:21 __pycache__
-rw-r--r-- 1 root   root   5588952 Apr 12 08:59 _gnucash_core_c.so
-rw-r--r-- 1 root   root   4345088 Apr 12 08:59 _sw_app_utils.so
-rw-r--r-- 1 root   root   4364912 Apr 12 08:59 _sw_core_utils.so
-rw-r--r-- 1 root   root276305 Apr 12 08:58 gnucash_core_c.py
-rw-r--r-- 1 root   root   552 Apr 11 12:28 app_utils.py
-rw-r--r-- 1 root   root  9286 Apr 11 12:28 function_class.py
-rw-r--r-- 1 root   root 33315 Apr 11 12:28 gnucash_core.py
-rw-r--r-- 1 root   root 14460 Mar 29 14:50 gnucash_business.py
-rw-rw-r-- 1 marksa marksa   17808 Jan 12 16:57 sw_core_utils.py
-rw-rw-r-- 1 marksa marksa4870 Jan 12 16:57 sw_app_utils.py
-rw-r--r-- 1 root   root   443 Sep 14  2019 __init__.py

For me it doesn't look like you need an actual gnucash app installed in the
venv to run the python bindings. But that I'm not sure about. If everything
you have looks good and you are still getting the error messages then you
may need some advice from someone who knows more about the way the bindings
are actually accessing system libraries.


cheers,

*Mark*


*episte...@gmail.com *
*(613) 447-5385*



On Sun, Apr 19, 2020 at 10:18 AM Andy Goblins  wrote:

> Since my python virtual environment is installed in the base of my build
> directory, I assume it naturally has access to build/lib/gnucash and
> build/lib/python3.8/site-packages. This appears to be working partially; it
> picks up the altered gnucash library in build/lib/python3.8 but it isn't
> getting the C libraries in build/lib/gnucash.
>
> I also tried skipping the virtual environment and just running
> "GNC_UNINSTALLED=1;GNC_BUILDDIR= dir>;PYTHONPATH=$GNC_BUILDDIR/lib/python3.8/site-packages:$GNC_BUILDDIR/lib/gnucash
> python" just like the cmake tests use, but I get the same result; it's not
> finding the libgncmod-backend stuff in build/lib/gnucash.
>
> *Sent:* Saturday, April 18, 2020 at 12:47 PM
> *From:* "Mark" 
> *To:* "andygoblins" 
> *Cc:* "GnuCash Developer" 
> *Subject:* Re: [GNC-dev] Testing python
> I use the python bindings regularly but I've never got any warnings or
> errors such as you describe. Just to cover the basics first, are you sure
> you didn't want to issue the venv command with the '--system-site-packages'
> switch? Did you have pygnucash loaded to the pip of the python you used for
> venv? Or instead did you make sure that in your venv you have included the
> path to your tinkered bindings in your PYTHONPATH? And you activated the
> venv before using? Sorry if this is all basic stuff you already know about.
>
>
>
>
> *Mark*
> *episte...@gmail.com *
> *(613) 447-5385*
>
>
>
> On Sat, Apr 18, 2020 at 10:08 AM andygoblins  wrote:
>
>>I'm tinkering with the python bindings, but I'm having trouble test

Re: [GNC-dev] Testing python

[Andy Goblins]

   Since my python virtual environment is installed in the base of my
   build directory, I assume it naturally has access to build/lib/gnucash
   and build/lib/python3.8/site-packages. This appears to be working
   partially; it picks up the altered gnucash library in
   build/lib/python3.8 but it isn't getting the C libraries in
   build/lib/gnucash.

   I also tried skipping the virtual environment and just running
   "GNC_UNINSTALLED=1;GNC_BUILDDIR=;PYTHONPATH=$GNC_BUILDDIR/lib/python3.8/site-packages:$GNC_BUILDDIR
   /lib/gnucash python" just like the cmake tests use, but I get the same
   result; it's not finding the libgncmod-backend stuff in
   build/lib/gnucash.

   Sent: Saturday, April 18, 2020 at 12:47 PM
   From: "Mark" 
   To: "andygoblins" 
   Cc: "GnuCash Developer" 
   Subject: Re: [GNC-dev] Testing python
   I use the python bindings regularly but I've never got any warnings or
   errors such as you describe. Just to cover the basics first, are you
   sure you didn't want to issue the venv command with the
   '--system-site-packages' switch? Did you have pygnucash loaded to the
   pip of the python you used for venv? Or instead did you make sure that
   in your venv you have included the path to your tinkered bindings in
   your PYTHONPATH? And you activated the venv before using? Sorry if this
   is all basic stuff you already know about.



   Mark
   [1]episte...@gmail.com
   (613) 447-5385



   On Sat, Apr 18, 2020 at 10:08 AM andygoblins <[2]andygobl...@gmx.com>
   wrote:

I'm tinkering with the python bindings, but I'm having trouble
 testing
the results of my changes. Could anyone give me some advice?
Currently, I build gnucash with ninja and then run 'python -m
 venv
' to set up a virtual python environment right next to
 the
fresh build. But when I try to import gnucash in the virtual
environment, it doesn't load any of the backends:
WARN  failed to load gncmod-backend-dbi from relative
 path
ERROR  required library gncmod-backend-dbi not found.
WARN  failed to load gncmod-backend-xml from relative
 path
ERROR  required library gncmod-backend-xml not found.
Any ideas on how to fix my path so I can load backends in my test
environment?
 ___
 gnucash-devel mailing list
 [3]gnucash-devel@gnucash.org
 [4]https://lists.gnucash.org/mailman/listinfo/gnucash-devel

References

   1. mailto:episte...@gmail.com
   2. mailto:andygobl...@gmx.com
   3. mailto:gnucash-devel@gnucash.org
   4. https://lists.gnucash.org/mailman/listinfo/gnucash-devel
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Testing python

[Mark]

I use the python bindings regularly but I've never got any warnings or
errors such as you describe. Just to cover the basics first, are you sure
you didn't want to issue the venv command with the '--system-site-packages'
switch? Did you have pygnucash loaded to the pip of the python you used for
venv? Or instead did you make sure that in your venv you have included the
path to your tinkered bindings in your PYTHONPATH? And you activated the
venv before using? Sorry if this is all basic stuff you already know about.



*Mark*
*episte...@gmail.com *
*(613) 447-5385*



On Sat, Apr 18, 2020 at 10:08 AM andygoblins  wrote:

>I'm tinkering with the python bindings, but I'm having trouble testing
>the results of my changes. Could anyone give me some advice?
>Currently, I build gnucash with ninja and then run 'python -m venv
>' to set up a virtual python environment right next to the
>fresh build. But when I try to import gnucash in the virtual
>environment, it doesn't load any of the backends:
>WARN  failed to load gncmod-backend-dbi from relative path
>ERROR  required library gncmod-backend-dbi not found.
>WARN  failed to load gncmod-backend-xml from relative path
>ERROR  required library gncmod-backend-xml not found.
>Any ideas on how to fix my path so I can load backends in my test
>environment?
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Testing python

[andygoblins]

   I'm tinkering with the python bindings, but I'm having trouble testing
   the results of my changes. Could anyone give me some advice?
   Currently, I build gnucash with ninja and then run 'python -m venv
   ' to set up a virtual python environment right next to the
   fresh build. But when I try to import gnucash in the virtual
   environment, it doesn't load any of the backends:
   WARN  failed to load gncmod-backend-dbi from relative path
   ERROR  required library gncmod-backend-dbi not found.
   WARN  failed to load gncmod-backend-xml from relative path
   ERROR  required library gncmod-backend-xml not found.
   Any ideas on how to fix my path so I can load backends in my test
   environment?
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] stress-testing reports

[Christopher Lam]

Hi all

To aid in development and refactoring of the numerous reports, I've
developed a report-options stress test.


*Premise:*
Most reports are currently defined in scheme. The reporting engine expects,
at a minimum, 2 functions to be defined - an options generator, and a
renderer.

The options generator will create a blank (gnc:report-options) object,
modify it by adding various options eg (gnc:make-string-option),
(gnc:make-simple-boolean-option), and return the options object to the
engine. This forms the basis of the report options UI.

The renderer will accept a report ID, and the options object. The renderer
will read the options used, query the database, and present a
gnc:html-document object to the engine. I'm not sure what happens
afterwards; the engine will render the html-document in Webkit.

*Refactoring*
Most of the report infrastructure was designed about 15-20 years ago...
this was using scheme/lisp conventions - bearing in mind LISP was designed
in the 1970s, and modern scripting engines such as python etc were nascent
- nonetheless scheme was chosen, for reasons that are apparent to schemers
only -- pythonistas will argue otherwise, but I do now that scheme is a
more flexible language to design financial reports; scheme has also evolved
in the past 15 years to become a powerful compilable language... Guile is
no different and will continue to evolve in a positive direction.

Unfortunately the state of Gnucash scheme code as of 2018 is stuck in the
past; for various reasons they have been kept on life support, limping
forward via every bugzilla report, and very difficult to understand and
create new types of reports. It would be good to refactor the numerous
scheme functions but, as some users have found out, refactoring the cryptic
code with good intentions do create some unusual report crashes.

*Proposal*
I have designed a mechanism whereby most standard reports in Gnucash have
been queried, and their options (string/boolean/etc) dumped, and a
test-stress-options is run continuously... This will repeatedly render the
options with various combinations of options, simply testing whether the
report will actually run. It does not verify the contents of the report.
It's designed to catch errors whereby e.g. finding periodic average on a
regular report is working well, but a refactored report whereby calculating
the average will fail on an empty book causing (total amount / num columns)
will trigger a division by zero.

The test-stress-options will come in 2 guises:

The first will perform a simple-stress-test, whereby all options are set to
successive values... if a report has 3 booleans (t/f) and 1 multichoice
with 4 values (a/b/c/d), it will run them with: (t,t,t,a), (f,f,f,b),
(t,t,t,c), (f,f,f,d) - this is fairly simple.

The second test will perform a combinatorial stress test, whereby the
number of options is sent to a local build of jenny from
http://burtleburtle.net/bob/math/jenny.html (thanks rgmerk); guile will
subprocess "jenny 2 2 2 4" which will generate an efficient list of options
(1a 2b 3a 4a), (1b 2b 3a 4b) etc, which is then interpreted by guile to run
the report repeatedly, hopefully catching more errors.

Either test is first run on an empty book, then on a book with sample
transactions.

On my laptop, a Intel i5, the simple-stress-test compiles in 1s and runs
most standard reports in 5 seconds and the combinatorial-stress-test
compiles in 8s and runs them in 20s. See its output at
https://gist.github.com/christopherlam/c04d43398ecac486d662c4e74eb293ca

Some reports e.g. multicolumn, hello-world, and eguile-based reports refuse
to be run, and are excluded.

IMHO this strategy, although complicated, is a safe and effective way to
ensure that refactoring internal functions do not lead to unexpected report
crashes. I'd think the simple stress test would be sufficient for daily
use, and combinatorics stress test prior to release. Code currently lives
on at https://github.com/Gnucash/gnucash/pull/378

Comments welcome!
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Great.
Thanks for testing!

-derek
Sent using my mobile device. Please excuse any typos.
On June 30, 2018 9:43:19 PM "Chris Good"  wrote:


Hi Derek + John,

Works now thanks.

Regards, Chris Good


-Original Message-
From: Derek Atkins 
Sent: Sunday, 1 July 2018 11:25 AM
To: John Ralls 
Cc: Derek Atkins ; Chris Good ;
gnucash-devel@gnucash.org
Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

I needed "IS NULL", not "= NULL", but this has been executed.

-derek


On Sat, June 30, 2018 8:44 pm, John Ralls wrote:
> Derek,
>
> That one shows as having no modified date. I expect it has no
> bugs_activity records, so it needs to have delta_ts set to creation_ts:
>
> UPDATE bugs SET delta_ts = creation_ts WHERE delta_ts = NULL;
>
> Regards,
> John Ralls
>
>
>> On Jun 30, 2018, at 5:35 PM, Derek Atkins  wrote:
>>
>> Thanks.
>> I bet this is related to a database "fix" that John and I did.
>> I'll take a look to ensure all bugs have a valid delta_ts.
>>
>> -derek
>> Sent using my mobile device. Please excuse any typos.
>> On June 30, 2018 8:30:15 PM "Chris Good" 
wrote:
>>
>>>> -Original Message-
>>>> From: Derek Atkins 
>>>> Sent: Tuesday, 26 June 2018 11:30 PM
>>>> To: Chris Good 
>>>> Cc: gnucash-devel@gnucash.org
>>>> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final
>>>> Testing
>>>>
>>>> Chris,
>>>>
>>>> "Chris Good"  writes:
>>>>
>>>> > Hi Derek,
>>>> >
>>>> > Thanks for all your work on this.
>>>> > There seems to be a problem with dates/times.
>>>> >
>>>> > In the old and new websites, I changed my preference to Timezone
>>>> used
>>>> > to display dates and times : Australia/Sydney
>>>> >
>>>> > Now:
>>>> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
>>>> > Reported: 2018-05-16 10:42 AEST by Chris Good
>>>> >
>>>> > https://bugs.gnucash.org/show_bug.cgi?id=796154
>>>> > Reported: 2018-05-16 14:42 AEST by Chris Good
>>>> >
>>>> > Sorry in advance if this is something you already have mentioned.
>>>>
>>>> I believe I have fixed this.  Can you please re-check?  (You will
>>>> need to
>>> reset your
>>>> preferences -- I dumped the database in trying to get this working).
>>> However
>>>> comparing a bug on GnomeBZ, I see the times in UTC on GnomeBZ and
>>>> EST/EDT on GnuCash-BZ with the correct 4/5-hour offsets.  So I
>>>> THINK this is now
>>> fixed
>>>> but would appreciate it if you coud verify.
>>>>
>>>> Thanks,
>>>>
>>>> > Regards, Chris Good
>>>>
>>>> -derek
>>>>
>>>> --
>>>>   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>>>   Member, MIT Student Information Processing Board  (SIPB)
>>>>   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>>>>   warl...@mit.eduPGP key available
>>>
>>> Hi Derek,
>>>
>>> Sorry for the delay testing this.
>>> Date/Time is correct now thanks.
>>>
>>> However,
>>>
>>> After resetting my password, logging in again to
>>> https://bugs.gnucash.org/show_bug.cgi?id=796154
>>> changing my preference
>>> "Timezone used to display dates and times"  to Australia/Sydney
>>>
>>> I tried to update the Bug Summary and get this error:
>>>
>>> https://bugs.gnucash.org/process_bug.cgi
>>>
>>> An unexpected error occurred. This could be a temporary problem, or
>>> some code is behaving incorrectly. If this problem persists, please
>>> email this page to de...@ihtfp.com with details of what you were
>>> doing at the time this message appeared.
>>>
>>> URL:
>>>
https://bugs.gnucash.org/process_bug.cgi?tag===Normal
ug_
>>>
status=NEW=_also=_contact=import%40gnucash.bugs
_id=
>>>
s_whiteboard=_desc=Generic%20import%20transaction%20matcher%20
should%2
>>>
0highlight%20the%20current%20line_platform=Other_severity=enhan
cemen
>>> t_to=import%40gnucash.bugs=_ts=-00-
00%2000%3A00%
>>>
3A00=_bug_ignored=1_milestone=future
on=
>>> ken=1530404201-
I3MkbYeJGLIf4WyJlcSSpcsU3Pn6peHLVYrVsfomUqk=3.1
>>>
ification=Unclassified=GnuCash=_sys=Windows
ent=Imp
>>> ort%20-%20OFX=796154_file_loc=
>>>
>>> The entered timestamp -00-00 00:00:00 could not be parsed into a
>>> valid
>>> date and time.
>>> Traceback:
>>>
>>> at /usr/share/bugzilla/process_bug.cgi line 107.
>>>
>>> Regards, Chris Good




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Chris Good]

Hi Derek + John,

Works now thanks.

Regards, Chris Good

> -Original Message-
> From: Derek Atkins 
> Sent: Sunday, 1 July 2018 11:25 AM
> To: John Ralls 
> Cc: Derek Atkins ; Chris Good ;
> gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
> 
> I needed "IS NULL", not "= NULL", but this has been executed.
> 
> -derek
> 
> 
> On Sat, June 30, 2018 8:44 pm, John Ralls wrote:
> > Derek,
> >
> > That one shows as having no modified date. I expect it has no
> > bugs_activity records, so it needs to have delta_ts set to creation_ts:
> >
> > UPDATE bugs SET delta_ts = creation_ts WHERE delta_ts = NULL;
> >
> > Regards,
> > John Ralls
> >
> >
> >> On Jun 30, 2018, at 5:35 PM, Derek Atkins  wrote:
> >>
> >> Thanks.
> >> I bet this is related to a database "fix" that John and I did.
> >> I'll take a look to ensure all bugs have a valid delta_ts.
> >>
> >> -derek
> >> Sent using my mobile device. Please excuse any typos.
> >> On June 30, 2018 8:30:15 PM "Chris Good" 
> wrote:
> >>
> >>>> -Original Message-
> >>>> From: Derek Atkins 
> >>>> Sent: Tuesday, 26 June 2018 11:30 PM
> >>>> To: Chris Good 
> >>>> Cc: gnucash-devel@gnucash.org
> >>>> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final
> >>>> Testing
> >>>>
> >>>> Chris,
> >>>>
> >>>> "Chris Good"  writes:
> >>>>
> >>>> > Hi Derek,
> >>>> >
> >>>> > Thanks for all your work on this.
> >>>> > There seems to be a problem with dates/times.
> >>>> >
> >>>> > In the old and new websites, I changed my preference to Timezone
> >>>> used
> >>>> > to display dates and times : Australia/Sydney
> >>>> >
> >>>> > Now:
> >>>> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
> >>>> > Reported:  2018-05-16 10:42 AEST by Chris Good
> >>>> >
> >>>> > https://bugs.gnucash.org/show_bug.cgi?id=796154
> >>>> > Reported:  2018-05-16 14:42 AEST by Chris Good
> >>>> >
> >>>> > Sorry in advance if this is something you already have mentioned.
> >>>>
> >>>> I believe I have fixed this.  Can you please re-check?  (You will
> >>>> need to
> >>> reset your
> >>>> preferences -- I dumped the database in trying to get this working).
> >>> However
> >>>> comparing a bug on GnomeBZ, I see the times in UTC on GnomeBZ and
> >>>> EST/EDT on GnuCash-BZ with the correct 4/5-hour offsets.  So I
> >>>> THINK this is now
> >>> fixed
> >>>> but would appreciate it if you coud verify.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> > Regards, Chris Good
> >>>>
> >>>> -derek
> >>>>
> >>>> --
> >>>>   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >>>>   Member, MIT Student Information Processing Board  (SIPB)
> >>>>   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
> >>>>   warl...@mit.eduPGP key available
> >>>
> >>> Hi Derek,
> >>>
> >>> Sorry for the delay testing this.
> >>> Date/Time is correct now thanks.
> >>>
> >>> However,
> >>>
> >>> After resetting my password, logging in again to
> >>> https://bugs.gnucash.org/show_bug.cgi?id=796154
> >>> changing my preference
> >>> "Timezone used to display dates and times"  to Australia/Sydney
> >>>
> >>> I tried to update the Bug Summary and get this error:
> >>>
> >>> https://bugs.gnucash.org/process_bug.cgi
> >>>
> >>> An unexpected error occurred. This could be a temporary problem, or
> >>> some code is behaving incorrectly. If this problem persists, please
> >>> email this page to de...@ihtfp.com with details of what you were
> >>> doing at the time this message appeared.
> >>>
> >>> URL:
> >>>
> https://bugs.gnucash.org/process_bug.cgi?tag===Normal
> ug_
> >>>
> status=NEW=_also=_contact=import%40gnucash.bugs
> _id=
> >>>
> s_whiteboard=_desc=Generic%20import%20transaction%20matcher%20
> should%2
> >>>
> 0highlight%20the%20current%20line_platform=Other_severity=enhan
> cemen
> >>> t_to=import%40gnucash.bugs=_ts=-00-
> 00%2000%3A00%
> >>>
> 3A00=_bug_ignored=1_milestone=future
> on=
> >>> ken=1530404201-
> I3MkbYeJGLIf4WyJlcSSpcsU3Pn6peHLVYrVsfomUqk=3.1
> >>>
> ification=Unclassified=GnuCash=_sys=Windows
> ent=Imp
> >>> ort%20-%20OFX=796154_file_loc=
> >>>
> >>> The entered timestamp -00-00 00:00:00 could not be parsed into a
> >>> valid
> >>> date and time.
> >>> Traceback:
> >>>
> >>> at /usr/share/bugzilla/process_bug.cgi line 107.
> >>>
> >>> Regards, Chris Good

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[John Ralls]

Derek,

That one shows as having no modified date. I expect it has no bugs_activity 
records, so it needs to have delta_ts set to creation_ts:

UPDATE bugs SET delta_ts = creation_ts WHERE delta_ts = NULL;

Regards,
John Ralls


> On Jun 30, 2018, at 5:35 PM, Derek Atkins  wrote:
> 
> Thanks.
> I bet this is related to a database "fix" that John and I did.
> I'll take a look to ensure all bugs have a valid delta_ts.
> 
> -derek
> Sent using my mobile device. Please excuse any typos.
> On June 30, 2018 8:30:15 PM "Chris Good"  wrote:
> 
>>> -Original Message-
>>> From: Derek Atkins 
>>> Sent: Tuesday, 26 June 2018 11:30 PM
>>> To: Chris Good 
>>> Cc: gnucash-devel@gnucash.org
>>> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
>>> 
>>> Chris,
>>> 
>>> "Chris Good"  writes:
>>> 
>>> > Hi Derek,
>>> >
>>> > Thanks for all your work on this.
>>> > There seems to be a problem with dates/times.
>>> >
>>> > In the old and new websites, I changed my preference to Timezone used
>>> > to display dates and times : Australia/Sydney
>>> >
>>> > Now:
>>> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
>>> > Reported: 2018-05-16 10:42 AEST by Chris Good
>>> >
>>> > https://bugs.gnucash.org/show_bug.cgi?id=796154
>>> > Reported: 2018-05-16 14:42 AEST by Chris Good
>>> >
>>> > Sorry in advance if this is something you already have mentioned.
>>> 
>>> I believe I have fixed this.  Can you please re-check?  (You will need to
>> reset your
>>> preferences -- I dumped the database in trying to get this working).
>> However
>>> comparing a bug on GnomeBZ, I see the times in UTC on GnomeBZ and EST/EDT
>>> on GnuCash-BZ with the correct 4/5-hour offsets.  So I THINK this is now
>> fixed
>>> but would appreciate it if you coud verify.
>>> 
>>> Thanks,
>>> 
>>> > Regards, Chris Good
>>> 
>>> -derek
>>> 
>>> --
>>>   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>>   Member, MIT Student Information Processing Board  (SIPB)
>>>   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>>>   warl...@mit.eduPGP key available
>> 
>> Hi Derek,
>> 
>> Sorry for the delay testing this.
>> Date/Time is correct now thanks.
>> 
>> However,
>> 
>> After resetting my password, logging in again to
>> https://bugs.gnucash.org/show_bug.cgi?id=796154
>> changing my preference
>> "Timezone used to display dates and times"  to Australia/Sydney
>> 
>> I tried to update the Bug Summary and get this error:
>> 
>> https://bugs.gnucash.org/process_bug.cgi
>> 
>> An unexpected error occurred. This could be a temporary problem, or some
>> code is behaving incorrectly. If this problem persists, please email this
>> page to de...@ihtfp.com with details of what you were doing at the time this
>> message appeared.
>> 
>> URL:
>> https://bugs.gnucash.org/process_bug.cgi?tag===Normal_
>> status=NEW=_also=_contact=import%40gnucash.bugs_id=
>> s_whiteboard=_desc=Generic%20import%20transaction%20matcher%20should%2
>> 0highlight%20the%20current%20line_platform=Other_severity=enhancemen
>> t_to=import%40gnucash.bugs=_ts=-00-00%2000%3A00%
>> 3A00=_bug_ignored=1_milestone=future=
>> ken=1530404201-I3MkbYeJGLIf4WyJlcSSpcsU3Pn6peHLVYrVsfomUqk=3.1
>> ification=Unclassified=GnuCash=_sys=Windows=Imp
>> ort%20-%20OFX=796154_file_loc=
>> 
>> The entered timestamp -00-00 00:00:00 could not be parsed into a valid
>> date and time.
>> Traceback:
>> 
>> at /usr/share/bugzilla/process_bug.cgi line 107.
>> 
>> Regards, Chris Good
> 
> 
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Thanks.
I bet this is related to a database "fix" that John and I did.
I'll take a look to ensure all bugs have a valid delta_ts.

-derek
Sent using my mobile device. Please excuse any typos.
On June 30, 2018 8:30:15 PM "Chris Good"  wrote:


-Original Message-
From: Derek Atkins 
Sent: Tuesday, 26 June 2018 11:30 PM
To: Chris Good 
Cc: gnucash-devel@gnucash.org
Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

Chris,

"Chris Good"  writes:

> Hi Derek,
>
> Thanks for all your work on this.
> There seems to be a problem with dates/times.
>
> In the old and new websites, I changed my preference to Timezone used
> to display dates and times : Australia/Sydney
>
> Now:
> https://bugzilla.gnome.org/show_bug.cgi?id=796154
> Reported:  2018-05-16 10:42 AEST by Chris Good
>
> https://bugs.gnucash.org/show_bug.cgi?id=796154
> Reported:  2018-05-16 14:42 AEST by Chris Good
>
> Sorry in advance if this is something you already have mentioned.

I believe I have fixed this.  Can you please re-check?  (You will need to

reset your

preferences -- I dumped the database in trying to get this working).

However

comparing a bug on GnomeBZ, I see the times in UTC on GnomeBZ and EST/EDT
on GnuCash-BZ with the correct 4/5-hour offsets.  So I THINK this is now

fixed

but would appreciate it if you coud verify.

Thanks,

> Regards, Chris Good

-derek

--
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.edu    PGP key available


Hi Derek,

Sorry for the delay testing this.
Date/Time is correct now thanks.

However,

After resetting my password, logging in again to
https://bugs.gnucash.org/show_bug.cgi?id=796154
changing my preference
"Timezone used to display dates and times"  to Australia/Sydney

I tried to update the Bug Summary and get this error:

https://bugs.gnucash.org/process_bug.cgi

An unexpected error occurred. This could be a temporary problem, or some
code is behaving incorrectly. If this problem persists, please email this
page to de...@ihtfp.com with details of what you were doing at the time this
message appeared.

URL:
https://bugs.gnucash.org/process_bug.cgi?tag===Normal_
status=NEW=_also=_contact=import%40gnucash.bugs_id=
s_whiteboard=_desc=Generic%20import%20transaction%20matcher%20should%2
0highlight%20the%20current%20line_platform=Other_severity=enhancemen
t_to=import%40gnucash.bugs=_ts=-00-00%2000%3A00%
3A00=_bug_ignored=1_milestone=future=
ken=1530404201-I3MkbYeJGLIf4WyJlcSSpcsU3Pn6peHLVYrVsfomUqk=3.1
ification=Unclassified=GnuCash=_sys=Windows=Imp
ort%20-%20OFX=796154_file_loc=

The entered timestamp -00-00 00:00:00 could not be parsed into a valid
date and time.
Traceback:

at /usr/share/bugzilla/process_bug.cgi line 107.

Regards, Chris Good




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Chris Good]

> -Original Message-
> From: Derek Atkins 
> Sent: Tuesday, 26 June 2018 11:30 PM
> To: Chris Good 
> Cc: gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
> 
> Chris,
> 
> "Chris Good"  writes:
> 
> > Hi Derek,
> >
> > Thanks for all your work on this.
> > There seems to be a problem with dates/times.
> >
> > In the old and new websites, I changed my preference to Timezone used
> > to display dates and times : Australia/Sydney
> >
> > Now:
> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
> > Reported:   2018-05-16 10:42 AEST by Chris Good
> >
> > https://bugs.gnucash.org/show_bug.cgi?id=796154
> > Reported:   2018-05-16 14:42 AEST by Chris Good
> >
> > Sorry in advance if this is something you already have mentioned.
> 
> I believe I have fixed this.  Can you please re-check?  (You will need to
reset your
> preferences -- I dumped the database in trying to get this working).
However
> comparing a bug on GnomeBZ, I see the times in UTC on GnomeBZ and EST/EDT
> on GnuCash-BZ with the correct 4/5-hour offsets.  So I THINK this is now
fixed
> but would appreciate it if you coud verify.
> 
> Thanks,
> 
> > Regards, Chris Good
> 
> -derek
> 
> --
>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>Member, MIT Student Information Processing Board  (SIPB)
>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>warl...@mit.eduPGP key available

Hi Derek,

Sorry for the delay testing this.
Date/Time is correct now thanks.

However,

After resetting my password, logging in again to
https://bugs.gnucash.org/show_bug.cgi?id=796154 
changing my preference
"Timezone used to display dates and times"  to Australia/Sydney

I tried to update the Bug Summary and get this error:

https://bugs.gnucash.org/process_bug.cgi

An unexpected error occurred. This could be a temporary problem, or some
code is behaving incorrectly. If this problem persists, please email this
page to de...@ihtfp.com with details of what you were doing at the time this
message appeared.

URL:
https://bugs.gnucash.org/process_bug.cgi?tag===Normal_
status=NEW=_also=_contact=import%40gnucash.bugs_id=
s_whiteboard=_desc=Generic%20import%20transaction%20matcher%20should%2
0highlight%20the%20current%20line_platform=Other_severity=enhancemen
t_to=import%40gnucash.bugs=_ts=-00-00%2000%3A00%
3A00=_bug_ignored=1_milestone=future=
ken=1530404201-I3MkbYeJGLIf4WyJlcSSpcsU3Pn6peHLVYrVsfomUqk=3.1
ification=Unclassified=GnuCash=_sys=Windows=Imp
ort%20-%20OFX=796154_file_loc=

The entered timestamp -00-00 00:00:00 could not be parsed into a valid
date and time.
Traceback:

 at /usr/share/bugzilla/process_bug.cgi line 107.

Regards, Chris Good

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Richard Ullger]

Hi Derek,

> Hi Richard,
> 
> I THINK I fixed this.  Can you please go take a look.
> 
> Thanks,
> 
> -derek
> 
> On Tue, June 26, 2018 9:35 am, Derek Atkins wrote:
>> Hi,
>>
>> Thanks for catching this.  I'll go take a look.
>>
>> -derek
>>
>> Richard Ullger  writes:
>>
>>> Hi Derek,
>>>
>>> Comments relating to an attachment are duplicated. For example, comment
>>> 1 on bug https://bugs.gnucash.org/show_bug.cgi?id=793593 ...
>>>
>>> -
>>> Richard Ullger 2018-02-19 16:08:41 GMT
>>>
>>> Created attachment 368555 [details]
>>> Reconciled balances showing zero difference
>>>
>>> Created attachment 368555 [details]
>>> Reconciled balances showing zero difference
>>> -
>>>
>>> Whereas on Gnome bugzilla you get a single occurrence of the comment.
>>>
>>> Regards,
>>>
>>> Richard

Yes, it looks good.

Regards,

Richard.




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Hi Richard,

I THINK I fixed this.  Can you please go take a look.

Thanks,

-derek

On Tue, June 26, 2018 9:35 am, Derek Atkins wrote:
> Hi,
>
> Thanks for catching this.  I'll go take a look.
>
> -derek
>
> Richard Ullger  writes:
>
>> Hi Derek,
>>
>> Comments relating to an attachment are duplicated. For example, comment
>> 1 on bug https://bugs.gnucash.org/show_bug.cgi?id=793593 ...
>>
>> -
>> Richard Ullger 2018-02-19 16:08:41 GMT
>>
>> Created attachment 368555 [details]
>> Reconciled balances showing zero difference
>>
>> Created attachment 368555 [details]
>> Reconciled balances showing zero difference
>> -
>>
>> Whereas on Gnome bugzilla you get a single occurrence of the comment.
>>
>> Regards,
>>
>> Richard
>>
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>
> --
>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>Member, MIT Student Information Processing Board  (SIPB)
>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>warl...@mit.eduPGP key available
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>


-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Hi,

Thanks for catching this.  I'll go take a look.

-derek

Richard Ullger  writes:

> Hi Derek,
>
> Comments relating to an attachment are duplicated. For example, comment
> 1 on bug https://bugs.gnucash.org/show_bug.cgi?id=793593 ...
>
> -
> Richard Ullger 2018-02-19 16:08:41 GMT
>
> Created attachment 368555 [details]
> Reconciled balances showing zero difference
>
> Created attachment 368555 [details]
> Reconciled balances showing zero difference
> -
>
> Whereas on Gnome bugzilla you get a single occurrence of the comment.
>
> Regards,
>
> Richard
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

John Ralls  writes:

> ISTR talking about this on IRC a couple of weeks ago. The times in the import
> data are getting treated as the wrong TZ by the import. Based on the shift I’d
> guess that they’re UTC in the data but the import program is treating them as
> local, i.e. -0400.

This is indeed what happened.  There were two issues:

1) The parse_date function would fall through to "local time" if the tz
offset was '0'

2) My import scripts were never calling the parse_date function!

> As long as the events are all in the same order it doesn’t really matter at
> exactly what time an event happened. The only risk is that an event on 
> bugzila.gnome.org entered right before the final dump will be briefly in the
> future on bugs.gnucash.org and so an event on the same bug entered on 
> bugs.gnucash.org might get out-of-order.

True..  But I'd rather the data be correct.

It's fixed now.

> Regards,
> John Ralls

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Chris,

"Chris Good"  writes:

> Hi Derek,
>
> Thanks for all your work on this.
> There seems to be a problem with dates/times.
>
> In the old and new websites, I changed my preference to
> Timezone used to display dates and times : Australia/Sydney
>
> Now:
> https://bugzilla.gnome.org/show_bug.cgi?id=796154
> Reported: 2018-05-16 10:42 AEST by Chris Good
>
> https://bugs.gnucash.org/show_bug.cgi?id=796154
> Reported: 2018-05-16 14:42 AEST by Chris Good
>
> Sorry in advance if this is something you already have mentioned.

I believe I have fixed this.  Can you please re-check?  (You will need
to reset your preferences -- I dumped the database in trying to get this
working).  However comparing a bug on GnomeBZ, I see the times in UTC on
GnomeBZ and EST/EDT on GnuCash-BZ with the correct 4/5-hour offsets.  So
I THINK this is now fixed but would appreciate it if you coud verify.

Thanks,

> Regards, Chris Good

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Richard Ullger]

On 15/06/18 22:18, Derek Atkins wrote:
> Hi Everyone,
> 
> I've been working on the BZ migration and finished yet another migration
> test.  At this point I *THINK* we've got everything the way we want in
> preparation for our final migration.
> 
> Please take a look at https://bugs.gnucash.org/
> 
> Peruse the bug list.  Check it out.  See if there are any problems.
> Also check out the wiki page for other notes and status:
>   https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installation
> 
> NOTES:
> 1) All users have accounts in the database, but you will need to reset
>your password in order to access it.
> 2) The database will be blown away when we perform the final migration,
>so you will need to reset your password again when we do the final
>migration.
> 3) Bug creation will not work, so don't try.
> 4) I have not migrated any GnomeBZ extensions -- we can always add those
>later (e.g. their browse page).
> 
> Final migration is planned for the week of June 25.
> 
> Please let me know if you find any issues!
> 
> Thanks,
> 
> -derek
> 

Hi Derek,

Comments relating to an attachment are duplicated. For example, comment
1 on bug https://bugs.gnucash.org/show_bug.cgi?id=793593 ...

-
Richard Ullger 2018-02-19 16:08:41 GMT

Created attachment 368555 [details]
Reconciled balances showing zero difference

Created attachment 368555 [details]
Reconciled balances showing zero difference
-

Whereas on Gnome bugzilla you get a single occurrence of the comment.

Regards,

Richard



signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[John Ralls]

ISTR talking about this on IRC a couple of weeks ago. The times in the import 
data are getting treated as the wrong TZ by the import. Based on the shift I’d 
guess that they’re UTC in the data but the import program is treating them as 
local, i.e. -0400.

As long as the events are all in the same order it doesn’t really matter at 
exactly what time an event happened. The only risk is that an event on 
bugzila.gnome.org <http://bugzila.gnome.org/> entered right before the final 
dump will be briefly in the future on bugs.gnucash.org and so an event on the 
same bug entered on bugs.gnucash.org <http://bugs.gnucash.org/> might get 
out-of-order.

Regards,
John Ralls

> On Jun 16, 2018, at 1:17 AM, Derek Atkins  wrote:
> 
> Thanks.
> 
> -derek
> Sent using my mobile device. Please excuse any typos.
> On June 16, 2018 4:15:12 AM "Chris Good"  wrote:
> 
>> Hi Derek,
>> 
>> I have added this task to the wiki TODO list.
>> 
>> Regards, Chris Good
>> 
>>> -Original Message-
>>> From: Derek Atkins 
>>> Sent: Saturday, 16 June 2018 6:09 PM
>>> To: Chris Good ; gnucash-devel@gnucash.org
>>> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
>>> 
>>> Interesting.
>>> I wonder if there in an import confusion between edt and gmt?
>>> Please add this to the wiki todo list?
>>> 
>>> -derek
>>> Sent using my mobile device. Please excuse any typos.
>>> On June 16, 2018 1:18:19 AM "Chris Good"  wrote:
>>> 
>>> >> Message: 6
>>> >> Date: Fri, 15 Jun 2018 17:18:05 -0400
>>> >> From: Derek Atkins 
>>> >> To: gnucash-devel@gnucash.org
>>> >> Subject: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
>>> >> Message-ID: 
>>> >> Content-Type: text/plain
>>> >>
>>> >> Hi Everyone,
>>> >>
>>> >> I've been working on the BZ migration and finished yet another
>>> >> migration
>>> > test.
>>> >> At this point I *THINK* we've got everything the way we want in
>>> > preparation for
>>> >> our final migration.
>>> >>
>>> >> Please take a look at https://bugs.gnucash.org/
>>> >>
>>> >> Peruse the bug list.  Check it out.  See if there are any problems.
>>> >> Also check out the wiki page for other notes and status:
>>> >>
>>> >> https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installatio
>>> >> n
>>> >>
>>> >> NOTES:
>>> >> 1) All users have accounts in the database, but you will need to reset
>>> >>your password in order to access it.
>>> >> 2) The database will be blown away when we perform the final migration,
>>> >>so you will need to reset your password again when we do the final
>>> >>migration.
>>> >> 3) Bug creation will not work, so don't try.
>>> >> 4) I have not migrated any GnomeBZ extensions -- we can always add
>> those
>>> >>later (e.g. their browse page).
>>> >>
>>> >> Final migration is planned for the week of June 25.
>>> >>
>>> >> Please let me know if you find any issues!
>>> >>
>>> >> Thanks,
>>> >>
>>> >> -derek
>>> >> --
>>> >>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>> >>Member, MIT Student Information Processing Board  (SIPB)
>>> >>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>>> >>warl...@mit.eduPGP key available
>>> >>
>>> >>
>>> >> --
>>> >
>>> > Hi Derek,
>>> >
>>> > Thanks for all your work on this.
>>> > There seems to be a problem with dates/times.
>>> >
>>> > In the old and new websites, I changed my preference to Timezone used
>>> > to display dates and times : Australia/Sydney
>>> >
>>> > Now:
>>> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
>>> > Reported: 2018-05-16 10:42 AEST by Chris Good
>>> >
>>> > https://bugs.gnucash.org/show_bug.cgi?id=796154
>>> > Reported: 2018-05-16 14:42 AEST by Chris Good
>>> >
>>> > Sorry in advance if this is something you already have mentioned.
>>> >
>>> > Regards, Chris Good
>>> >
>>> > ___
>>> > gnucash-devel mailing list
>>> > gnucash-devel@gnucash.org
>>> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>> 
> 
> 
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Thanks.

-derek
Sent using my mobile device. Please excuse any typos.
On June 16, 2018 4:15:12 AM "Chris Good"  wrote:


Hi Derek,

I have added this task to the wiki TODO list.

Regards, Chris Good


-Original Message-
From: Derek Atkins 
Sent: Saturday, 16 June 2018 6:09 PM
To: Chris Good ; gnucash-devel@gnucash.org
Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

Interesting.
I wonder if there in an import confusion between edt and gmt?
Please add this to the wiki todo list?

-derek
Sent using my mobile device. Please excuse any typos.
On June 16, 2018 1:18:19 AM "Chris Good"  wrote:

>> Message: 6
>> Date: Fri, 15 Jun 2018 17:18:05 -0400
>> From: Derek Atkins 
>> To: gnucash-devel@gnucash.org
>> Subject: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
>> Message-ID: 
>> Content-Type: text/plain
>>
>> Hi Everyone,
>>
>> I've been working on the BZ migration and finished yet another
>> migration
> test.
>> At this point I *THINK* we've got everything the way we want in
> preparation for
>> our final migration.
>>
>> Please take a look at https://bugs.gnucash.org/
>>
>> Peruse the bug list.  Check it out.  See if there are any problems.
>> Also check out the wiki page for other notes and status:
>>
>> https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installatio
>> n
>>
>> NOTES:
>> 1) All users have accounts in the database, but you will need to reset
>>your password in order to access it.
>> 2) The database will be blown away when we perform the final migration,
>>so you will need to reset your password again when we do the final
>>migration.
>> 3) Bug creation will not work, so don't try.
>> 4) I have not migrated any GnomeBZ extensions -- we can always add

those

>>later (e.g. their browse page).
>>
>> Final migration is planned for the week of June 25.
>>
>> Please let me know if you find any issues!
>>
>> Thanks,
>>
>> -derek
>> --
>>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>>Member, MIT Student Information Processing Board  (SIPB)
>>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>>warl...@mit.eduPGP key available
>>
>>
>> --
>
> Hi Derek,
>
> Thanks for all your work on this.
> There seems to be a problem with dates/times.
>
> In the old and new websites, I changed my preference to Timezone used
> to display dates and times : Australia/Sydney
>
> Now:
> https://bugzilla.gnome.org/show_bug.cgi?id=796154
> Reported:  2018-05-16 10:42 AEST by Chris Good
>
> https://bugs.gnucash.org/show_bug.cgi?id=796154
> Reported:  2018-05-16 14:42 AEST by Chris Good
>
> Sorry in advance if this is something you already have mentioned.
>
> Regards, Chris Good
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel





___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Chris Good]

Hi Derek,

I have added this task to the wiki TODO list.

Regards, Chris Good

> -Original Message-
> From: Derek Atkins 
> Sent: Saturday, 16 June 2018 6:09 PM
> To: Chris Good ; gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
> 
> Interesting.
> I wonder if there in an import confusion between edt and gmt?
> Please add this to the wiki todo list?
> 
> -derek
> Sent using my mobile device. Please excuse any typos.
> On June 16, 2018 1:18:19 AM "Chris Good"  wrote:
> 
> >> Message: 6
> >> Date: Fri, 15 Jun 2018 17:18:05 -0400
> >> From: Derek Atkins 
> >> To: gnucash-devel@gnucash.org
> >> Subject: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
> >> Message-ID: 
> >> Content-Type: text/plain
> >>
> >> Hi Everyone,
> >>
> >> I've been working on the BZ migration and finished yet another
> >> migration
> > test.
> >> At this point I *THINK* we've got everything the way we want in
> > preparation for
> >> our final migration.
> >>
> >> Please take a look at https://bugs.gnucash.org/
> >>
> >> Peruse the bug list.  Check it out.  See if there are any problems.
> >> Also check out the wiki page for other notes and status:
> >>
> >> https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installatio
> >> n
> >>
> >> NOTES:
> >> 1) All users have accounts in the database, but you will need to reset
> >>your password in order to access it.
> >> 2) The database will be blown away when we perform the final migration,
> >>so you will need to reset your password again when we do the final
> >>migration.
> >> 3) Bug creation will not work, so don't try.
> >> 4) I have not migrated any GnomeBZ extensions -- we can always add
those
> >>later (e.g. their browse page).
> >>
> >> Final migration is planned for the week of June 25.
> >>
> >> Please let me know if you find any issues!
> >>
> >> Thanks,
> >>
> >> -derek
> >> --
> >>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >>Member, MIT Student Information Processing Board  (SIPB)
> >>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
> >>warl...@mit.eduPGP key available
> >>
> >>
> >> --
> >
> > Hi Derek,
> >
> > Thanks for all your work on this.
> > There seems to be a problem with dates/times.
> >
> > In the old and new websites, I changed my preference to Timezone used
> > to display dates and times : Australia/Sydney
> >
> > Now:
> > https://bugzilla.gnome.org/show_bug.cgi?id=796154
> > Reported:   2018-05-16 10:42 AEST by Chris Good
> >
> > https://bugs.gnucash.org/show_bug.cgi?id=796154
> > Reported:   2018-05-16 14:42 AEST by Chris Good
> >
> > Sorry in advance if this is something you already have mentioned.
> >
> > Regards, Chris Good
> >
> > ___
> > gnucash-devel mailing list
> > gnucash-devel@gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Interesting.
I wonder if there in an import confusion between edt and gmt?
Please add this to the wiki todo list?

-derek
Sent using my mobile device. Please excuse any typos.
On June 16, 2018 1:18:19 AM "Chris Good"  wrote:


Message: 6
Date: Fri, 15 Jun 2018 17:18:05 -0400
From: Derek Atkins 
To: gnucash-devel@gnucash.org
Subject: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
Message-ID: 
Content-Type: text/plain

Hi Everyone,

I've been working on the BZ migration and finished yet another migration

test.

At this point I *THINK* we've got everything the way we want in

preparation for

our final migration.

Please take a look at https://bugs.gnucash.org/

Peruse the bug list.  Check it out.  See if there are any problems.
Also check out the wiki page for other notes and status:
  https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installation

NOTES:
1) All users have accounts in the database, but you will need to reset
   your password in order to access it.
2) The database will be blown away when we perform the final migration,
   so you will need to reset your password again when we do the final
   migration.
3) Bug creation will not work, so don't try.
4) I have not migrated any GnomeBZ extensions -- we can always add those
   later (e.g. their browse page).

Final migration is planned for the week of June 25.

Please let me know if you find any issues!

Thanks,

-derek
--
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available


--


Hi Derek,

Thanks for all your work on this.
There seems to be a problem with dates/times.

In the old and new websites, I changed my preference to
Timezone used to display dates and times : Australia/Sydney

Now:
https://bugzilla.gnome.org/show_bug.cgi?id=796154
Reported:   2018-05-16 10:42 AEST by Chris Good

https://bugs.gnucash.org/show_bug.cgi?id=796154
Reported:   2018-05-16 14:42 AEST by Chris Good

Sorry in advance if this is something you already have mentioned.

Regards, Chris Good

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Chris Good]

> Message: 6
> Date: Fri, 15 Jun 2018 17:18:05 -0400
> From: Derek Atkins 
> To: gnucash-devel@gnucash.org
> Subject: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing
> Message-ID: 
> Content-Type: text/plain
> 
> Hi Everyone,
> 
> I've been working on the BZ migration and finished yet another migration
test.
> At this point I *THINK* we've got everything the way we want in
preparation for
> our final migration.
> 
> Please take a look at https://bugs.gnucash.org/
> 
> Peruse the bug list.  Check it out.  See if there are any problems.
> Also check out the wiki page for other notes and status:
>   https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installation
> 
> NOTES:
> 1) All users have accounts in the database, but you will need to reset
>your password in order to access it.
> 2) The database will be blown away when we perform the final migration,
>so you will need to reset your password again when we do the final
>migration.
> 3) Bug creation will not work, so don't try.
> 4) I have not migrated any GnomeBZ extensions -- we can always add those
>later (e.g. their browse page).
> 
> Final migration is planned for the week of June 25.
> 
> Please let me know if you find any issues!
> 
> Thanks,
> 
> -derek
> --
>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>Member, MIT Student Information Processing Board  (SIPB)
>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>warl...@mit.eduPGP key available
> 
> 
> --

Hi Derek,

Thanks for all your work on this.
There seems to be a problem with dates/times.

In the old and new websites, I changed my preference to
Timezone used to display dates and times : Australia/Sydney

Now:
https://bugzilla.gnome.org/show_bug.cgi?id=796154
Reported:   2018-05-16 10:42 AEST by Chris Good

https://bugs.gnucash.org/show_bug.cgi?id=796154
Reported:   2018-05-16 14:42 AEST by Chris Good

Sorry in advance if this is something you already have mentioned.

Regards, Chris Good

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[David Carlson]

Since that is almost the same time as release 3.2 happens there could be a
flurry of users wanting to read bugs listed in the release announcement and
perhaps enter new bugs or updates.

I suggest that the 6.3 release announcement mention the BZ release and warn
as appropriate.

David C

On Fri, Jun 15, 2018, 4:19 PM Derek Atkins  wrote:

> Hi Everyone,
>
> I've been working on the BZ migration and finished yet another migration
> test.  At this point I *THINK* we've got everything the way we want in
> preparation for our final migration.
>
> Please take a look at https://bugs.gnucash.org/
>
> Peruse the bug list.  Check it out.  See if there are any problems.
> Also check out the wiki page for other notes and status:
>   https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installation
>
> NOTES:
> 1) All users have accounts in the database, but you will need to reset
>your password in order to access it.
> 2) The database will be blown away when we perform the final migration,
>so you will need to reset your password again when we do the final
>migration.
> 3) Bug creation will not work, so don't try.
> 4) I have not migrated any GnomeBZ extensions -- we can always add those
>later (e.g. their browse page).
>
> Final migration is planned for the week of June 25.
>
> Please let me know if you find any issues!
>
> Thanks,
>
> -derek
> --
>Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>Member, MIT Student Information Processing Board  (SIPB)
>URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
>warl...@mit.eduPGP key available
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] BZ: Migration Status (2018-06-15) -- Final Testing

[Derek Atkins]

Hi Everyone,

I've been working on the BZ migration and finished yet another migration
test.  At this point I *THINK* we've got everything the way we want in
preparation for our final migration.

Please take a look at https://bugs.gnucash.org/

Peruse the bug list.  Check it out.  See if there are any problems.
Also check out the wiki page for other notes and status:
  https://wiki.gnucash.org/wiki/Bugzilla_Administration#New_Installation

NOTES:
1) All users have accounts in the database, but you will need to reset
   your password in order to access it.
2) The database will be blown away when we perform the final migration,
   so you will need to reset your password again when we do the final
   migration.
3) Bug creation will not work, so don't try.
4) I have not migrated any GnomeBZ extensions -- we can always add those
   later (e.g. their browse page).

Final migration is planned for the week of June 25.

Please let me know if you find any issues!

Thanks,

-derek
-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Build issues and some free testing

[Robert Merkel]

Win!

By the way, 90% code coverage seems to be better, if anything, than what
industry does.

Cheers,

Robert.

On Wed, Jun 13, 2018 at 2:32 PM, Christopher Lam 
wrote:

> Dear rgmerk
> Finally understood the use for combinatorics :)
> https://github.com/Gnucash/gnucash/commit/da1d1b9a47939ad08ac645024f448a
> 4820103ad8#diff-1625b4f2db9166674389d58f2f585131R497
> SRFI-64 is now firmly established as the testing framework to be used in
> Gnucash from now on.
> I think transaction.scm and invoice.scm now have about 90% code coverage.
> I'll add more as time goes on...
> Chris
>
> On 24 January 2018 at 11:59, John Ralls  wrote:
>
>> Robert,
>>
>> Cool. If they should wind up writing some nice unit tests for areas where
>> our coverage is poor (pretty much everywhere) we’ll happily and gratefully
>> take them.
>>
>> Regards,
>> John Ralls
>>
>> > On Jan 23, 2018, at 4:26 PM, Robert Merkel 
>> wrote:
>> >
>> > Thanks all.
>> >
>> > I realised the VM I was working with was an LTS version, and upgraded
>> to the most recent Ubuntu release.  Gnucash built without problems in the
>> upgraded VM.
>> >
>> > It seems like the fixes were a good piece of housekeeping anyway.
>> >
>> > Just to let you know it's looking increasingly likely I'm going to have
>> a bunch of students poking and prodding at gnucash some time in April.
>> I'll make sure to file bug reports for any real bugs they find.  I'll ask
>> them to route any questions they have through me, so it shouldn't result in
>> masses of mailing list traffic.
>> >
>> > Regards,
>> >
>> > Robert.
>> >
>> > On Wed, 24 Jan 2018 at 11:19 John Ralls > jra...@ceridwen.us>> wrote:
>> >
>> >
>> > > On Jan 22, 2018, at 6:56 PM, Robert Merkel <
>> robert.mer...@benambra.org <mailto:robert.mer...@benambra.org>> wrote:
>> > >
>> > > Hello all.
>> > >
>> > > If you dig far enough into the mailing list archives or the
>> changelogs, you
>> > > might find me :)
>> > >
>> > > I spoke to Christopher Lam recently, who told me about the work he's
>> been
>> > > doing on the transaction report which I worked on many many years ago.
>> > >
>> > > These days, my day job is teaching students about software
>> engineering and,
>> > > this upcoming semester, I'm teaching a unit on testing and quality
>> > > assurance.  For one of the assignments, we need some software for
>> students
>> > > to test, and I thought I might get them to test Gnucash.
>> > >
>> > > So, for the first time for quite a while, I have tried to download and
>> > > build gnucash from the git repository using cmake.  I've found the
>> > > following build issues:
>> > >
>> > > * The build process requires xsltproc and makeinfo, which are not
>> mentioned
>> > > in the dependency list and cmake doesn't seem to check for them.
>> > >
>> > > * The build failed on my Ubuntu machine with the stock version of
>> > > libwebkit2-gtk available on that distribution (2.4.11).  It appears
>> that
>> > > Gnucash requires version
>> > > 2.6 of this library, as "WebKitNavigationAction" was apparently added
>> in
>> > > version 2.6.  Again, the minimum version isn't listed and cmake
>> doesn't
>> > > have a check for it.
>> >
>> > Hi, Robert.
>> >
>> > Welcome back! Chris mentioned his meeting with you on IRC.
>> >
>> > Thanks for bringing those to our attention. I've pushed a fix.
>> >
>> > You will need to install xsltproc. In some distros it's part of the
>> libxslt package, which may be why it wasn't mentioned separately in
>> README.dependencies. You won't need makeinfo, I've made that optional. It's
>> only for an obsolete design information document that is now mostly
>> superseded by Doxygen comments.
>> >
>> > The webkit2gtk-3.0 package provided by Ubuntu 14.04LTS is fine, and
>> CMake did correctly detect it and set the compile accordingly--the first
>> time through. If you then subsequently ran cmake again it would see that
>> WEBKIT_FOUND was true and set up for the preferred webkit2gtk-4.0. I've
>> corrected that by having separate WEBKIT2_3_FOUND and WEBKIT2_4_FOUND
>> variables.
>> >
>> > Regards,
>> > John Ralls
>> >
>> >
>>
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Build issues and some free testing

[Christopher Lam]

Dear rgmerk
Finally understood the use for combinatorics :)
https://github.com/Gnucash/gnucash/commit/da1d1b9a47939ad08ac645024f448a4820103ad8#diff-1625b4f2db9166674389d58f2f585131R497
SRFI-64 is now firmly established as the testing framework to be used in
Gnucash from now on.
I think transaction.scm and invoice.scm now have about 90% code coverage.
I'll add more as time goes on...
Chris

On 24 January 2018 at 11:59, John Ralls  wrote:

> Robert,
>
> Cool. If they should wind up writing some nice unit tests for areas where
> our coverage is poor (pretty much everywhere) we’ll happily and gratefully
> take them.
>
> Regards,
> John Ralls
>
> > On Jan 23, 2018, at 4:26 PM, Robert Merkel 
> wrote:
> >
> > Thanks all.
> >
> > I realised the VM I was working with was an LTS version, and upgraded to
> the most recent Ubuntu release.  Gnucash built without problems in the
> upgraded VM.
> >
> > It seems like the fixes were a good piece of housekeeping anyway.
> >
> > Just to let you know it's looking increasingly likely I'm going to have
> a bunch of students poking and prodding at gnucash some time in April.
> I'll make sure to file bug reports for any real bugs they find.  I'll ask
> them to route any questions they have through me, so it shouldn't result in
> masses of mailing list traffic.
> >
> > Regards,
> >
> > Robert.
> >
> > On Wed, 24 Jan 2018 at 11:19 John Ralls  jra...@ceridwen.us>> wrote:
> >
> >
> > > On Jan 22, 2018, at 6:56 PM, Robert Merkel  <mailto:robert.mer...@benambra.org>> wrote:
> > >
> > > Hello all.
> > >
> > > If you dig far enough into the mailing list archives or the
> changelogs, you
> > > might find me :)
> > >
> > > I spoke to Christopher Lam recently, who told me about the work he's
> been
> > > doing on the transaction report which I worked on many many years ago.
> > >
> > > These days, my day job is teaching students about software engineering
> and,
> > > this upcoming semester, I'm teaching a unit on testing and quality
> > > assurance.  For one of the assignments, we need some software for
> students
> > > to test, and I thought I might get them to test Gnucash.
> > >
> > > So, for the first time for quite a while, I have tried to download and
> > > build gnucash from the git repository using cmake.  I've found the
> > > following build issues:
> > >
> > > * The build process requires xsltproc and makeinfo, which are not
> mentioned
> > > in the dependency list and cmake doesn't seem to check for them.
> > >
> > > * The build failed on my Ubuntu machine with the stock version of
> > > libwebkit2-gtk available on that distribution (2.4.11).  It appears
> that
> > > Gnucash requires version
> > > 2.6 of this library, as "WebKitNavigationAction" was apparently added
> in
> > > version 2.6.  Again, the minimum version isn't listed and cmake doesn't
> > > have a check for it.
> >
> > Hi, Robert.
> >
> > Welcome back! Chris mentioned his meeting with you on IRC.
> >
> > Thanks for bringing those to our attention. I've pushed a fix.
> >
> > You will need to install xsltproc. In some distros it's part of the
> libxslt package, which may be why it wasn't mentioned separately in
> README.dependencies. You won't need makeinfo, I've made that optional. It's
> only for an obsolete design information document that is now mostly
> superseded by Doxygen comments.
> >
> > The webkit2gtk-3.0 package provided by Ubuntu 14.04LTS is fine, and
> CMake did correctly detect it and set the compile accordingly--the first
> time through. If you then subsequently ran cmake again it would see that
> WEBKIT_FOUND was true and set up for the preferred webkit2gtk-4.0. I've
> corrected that by having separate WEBKIT2_3_FOUND and WEBKIT2_4_FOUND
> variables.
> >
> > Regards,
> > John Ralls
> >
> >
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] BZ: Migration Status -- Full Load for testing

[Derek Atkins]

Hi,

I've just completed a "full" migration load for testing.  This contains
all bug data as of about 2 days ago.  This also means all users are in
there as well.

Note:  This is NOT a final migration -- I intend to dump the database at
least one more time, probably more!  So if you reset your password before,
you will need to do it again -- and if you do it now, you will likely have
to do it again later.  You've been warned.

Also note:  There are several fields that are broken or wrong, especially
in the history.  For example, we do not currently have an
"attachments.gnome_attachment_status" field, or "cf_gnome_version" or
"cf_gnome_target"..I'm also not 100% sure I properly migrated some
other history tags, either.

There was at least one bug with a bogus mime-type which I fix in post.

There was also one bug that has a bogus see_also URL (https:/bugzilla...
is not a valid URL) -- I fixed that manually in my json.

For DUP and DEPENDS_ON references to non-gnucash bugs, I removed the
entries and added a see-also URL.  Please check I did it correctly.  I
have a list of these at the end.

We still need to set up our process, and then I need to translate the
status/resolution fields appropriately.  That is still TBD.

So please, test away.  Let me know if there is bogus data, or weird
attributes, or anything like that.  Configuration bugs are also welcome.

Thanks!

-derek

# Depends-on list:
Round 3: (68) 28: 114245(344005) 119040(340007) 327625(332884)
328114(330017) 337185(337780) 342487(328114) 343472(327625) 343607(359224)
347191(328114) 347533(328114) 351371(364936) 359224(580545) 395327(371036)
402524(351371) 405177(405228) 405228(364946) 410703(405228) 457017(395327)
463733(395327) 467000(395327) 469464(363648) 478501(395327) 480517(469464)
488608(469464) 513906(514621) 627718(627829) 651690(512562) 746873(748625)

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: how exactly to do unit testing in scheme...

[Christopher Lam]

Hi Robert and devel,

Thank you for pointers, this is useful. The examples below illustrate 
how to test multiple items together. But I think the complexity of the 
52(and counting) options (37 binary, the rest are multiples/multichoice) 
means, I think it'll be better to handwrite tests. I'll need to reuse 
existing test frameworks to attempt maximise coverage.


C

On 31/01/18 09:01, Robert Merkel wrote:

Sorry for the tardy response - I went away for the long weekend and was
busy yesterday!

As Phil says, you can test both leaf functions and controller code with
unit tests. With controller code, you may need to write mocks for some or
all of the called code.  I don't know whether there are prewritten mocking
libraries for guile, but given the extreme flexibility of scheme it
shouldn't be difficult to write code to replace one function call with
another where necessary.

As long as xaccTransGetDate and xaccSplitGetParent are adequately tested,
there is no particular reason from a testing perspective to throw in an
intermediate function.

As far as which options to test, if testing all the combinations
exhaustively results in too many tests (and it sounds like it does) try
pairwise combinatoric testing, which works as follows:

Say you've got options {o_1, o_2, o_3, ... o_n}, each of which can take a
limited set of values {o_i^1, o_i_2, o_i^k} (for instance, if the option
can either be "on" or "off" it has two values).

For any pair of options o_x and o_y, for all the possible combinations of
option values there should be at least one test that has that combination.

To give a very simple case, for three options {a, b, c}  each of which can
take two values {off, on}, you could have the following tests:

  Option   a b c
Test
1 off  off   off
2 off   on  off
3 on   off   on
4 onon  off
5 off   offon

For the pair (a,b) tests 1 through 4 give all the possible combinations,
for the pair (a, c) tests {1, 3, 4, 5} give all the possible combinations,
and for the pair (b, c) tests {1, 2, 3, 4} give all the possible
combinations.

5 is the minimum number of tests that can meet the pairwise combinatoric
criterion, as compared to 8 if you tried all the possible combinations.
However, it becomes an even bigger win if you're trying lots of options:
you only need 9 tests for 8 options with two values, whereas you would need
256 tests to try every possible option combination!

To generate optimal pairwise test sets, you can use "jenny" (this is a
really useful but unmaintained tool, I really should take over the
maintenance):

http://burtleburtle.net/bob/math/jenny.html

Hope this helps, and feel free to ask more questions.  I will try to
respond more promptly!


On Thu, Jan 25, 2018 at 3:03 AM, Christopher Lam <christopher@gmail.com>
wrote:


Dear Devel



To rgmerk: Welcome back, and it was a nice to meet irl!



While simplifying transaction.scm and thinking of unit testing, I now have
a conundrum worthy of an expert view.



The reports require 2 main functions – the options generator and the
renderer; the options generator generates a options.scm controller object,
and the renderer takes options and outputs html.



I understand unit testing to handle testing of ‘leaf’ functions e.g.
(split->date), rather than the controller code (e.g. renderer takes options
and outputs html) – but to me this is rather silly because split->date only
tests xaccTransGetDate and xaccSplitGetParent, whereas the controller tests
actual functionality.



With regards to unit testing I can see several issues



1. The refactored report has inlined most single-use functions into
lambda expressions – I figured that directly stating (xaccTransGetDate
(xaccSplitGetParent split)) is much more descriptive to a programmer than
to create a testable leaf function (split->date split). I can see the
benefits of both – leave as lambda expressions which will can be
understandable by anyone who is familiar with the API, or break them out
into 100s of single use functions which can be tested, but introduces a
whole layer of cognitive load to anyone hacking code – (what does
split->date actually do? Where is its definition). Also, breaking the
lambda functions into testable functions means the implementation is frozen
and the next hacker will have lesser scope to rework/optimise the report.



1. The refactored report is now flexible enough to accommodate derived
reports with a different multicolumn data function – eg
income-gst-statement.scm has been reworked into a transaction.scm
derivative which passes its own calculated-cells to report on GST sales and
purchases. This is not yet committed.



1. I think the most useful testing approach for a complex
transaction.scm will be to test functions of various combinations of

Re: how exactly to do unit testing in scheme...

[Robert Merkel]

Sorry for the tardy response - I went away for the long weekend and was
busy yesterday!

As Phil says, you can test both leaf functions and controller code with
unit tests. With controller code, you may need to write mocks for some or
all of the called code.  I don't know whether there are prewritten mocking
libraries for guile, but given the extreme flexibility of scheme it
shouldn't be difficult to write code to replace one function call with
another where necessary.

As long as xaccTransGetDate and xaccSplitGetParent are adequately tested,
there is no particular reason from a testing perspective to throw in an
intermediate function.

As far as which options to test, if testing all the combinations
exhaustively results in too many tests (and it sounds like it does) try
pairwise combinatoric testing, which works as follows:

Say you've got options {o_1, o_2, o_3, ... o_n}, each of which can take a
limited set of values {o_i^1, o_i_2, o_i^k} (for instance, if the option
can either be "on" or "off" it has two values).

For any pair of options o_x and o_y, for all the possible combinations of
option values there should be at least one test that has that combination.

To give a very simple case, for three options {a, b, c}  each of which can
take two values {off, on}, you could have the following tests:

 Option   a b c
Test
1 off  off   off
2 off   on  off
3 on   off   on
4 onon  off
5 off   offon

For the pair (a,b) tests 1 through 4 give all the possible combinations,
for the pair (a, c) tests {1, 3, 4, 5} give all the possible combinations,
and for the pair (b, c) tests {1, 2, 3, 4} give all the possible
combinations.

5 is the minimum number of tests that can meet the pairwise combinatoric
criterion, as compared to 8 if you tried all the possible combinations.
However, it becomes an even bigger win if you're trying lots of options:
you only need 9 tests for 8 options with two values, whereas you would need
256 tests to try every possible option combination!

To generate optimal pairwise test sets, you can use "jenny" (this is a
really useful but unmaintained tool, I really should take over the
maintenance):

http://burtleburtle.net/bob/math/jenny.html

Hope this helps, and feel free to ask more questions.  I will try to
respond more promptly!


On Thu, Jan 25, 2018 at 3:03 AM, Christopher Lam <christopher@gmail.com>
wrote:

> Dear Devel
>
>
>
> To rgmerk: Welcome back, and it was a nice to meet irl!
>
>
>
> While simplifying transaction.scm and thinking of unit testing, I now have
> a conundrum worthy of an expert view.
>
>
>
> The reports require 2 main functions – the options generator and the
> renderer; the options generator generates a options.scm controller object,
> and the renderer takes options and outputs html.
>
>
>
> I understand unit testing to handle testing of ‘leaf’ functions e.g.
> (split->date), rather than the controller code (e.g. renderer takes options
> and outputs html) – but to me this is rather silly because split->date only
> tests xaccTransGetDate and xaccSplitGetParent, whereas the controller tests
> actual functionality.
>
>
>
> With regards to unit testing I can see several issues
>
>
>
>1. The refactored report has inlined most single-use functions into
>lambda expressions – I figured that directly stating (xaccTransGetDate
>(xaccSplitGetParent split)) is much more descriptive to a programmer than
>to create a testable leaf function (split->date split). I can see the
>benefits of both – leave as lambda expressions which will can be
>understandable by anyone who is familiar with the API, or break them out
>into 100s of single use functions which can be tested, but introduces a
>whole layer of cognitive load to anyone hacking code – (what does
>split->date actually do? Where is its definition). Also, breaking the
>lambda functions into testable functions means the implementation is frozen
>and the next hacker will have lesser scope to rework/optimise the report.
>
>
>
>1. The refactored report is now flexible enough to accommodate derived
>reports with a different multicolumn data function – eg
>income-gst-statement.scm has been reworked into a transaction.scm
>derivative which passes its own calculated-cells to report on GST sales and
>purchases. This is not yet committed.
>
>
>
>1. I think the most useful testing approach for a complex
>transaction.scm will be to test functions of various combinations of
>options values, and test the resulting html for satisfactory output. There
>are now dozens of bools and multichoices that can be triggered, each
>effecting html in var

Re: how exactly to do unit testing in scheme...

[Christopher Lam]

Thank you Phil, with help from IRC I'll be separating the renderer into
multiple testable steps.

Options to accountlist, to splits, to filtered splits, and finally to
table.

Each one uses different parts of options.

On 26 Jan 2018 1:55 AM, "Phil Longstaff" <phil.longst...@gmail.com> wrote:

> Usually, unit testing controller code is done by writing mocks for the
> code that is called. In this case, this would be the options.scm controller
> and the renderer. The mock code would test that the expected arguments are
> passed, and would return a canned response. This both checks the logic of
> the controller but also allows error and other paths to be tested.
>
> On Wed, Jan 24, 2018 at 11:03 AM, Christopher Lam <
> christopher@gmail.com> wrote:
>
>> Dear Devel
>>
>> To rgmerk: Welcome back, and it was a nice to meet irl!
>>
>> While simplifying transaction.scm and thinking of unit testing, I now
>> have a conundrum worthy of an expert view.
>>
>> The reports require 2 main functions – the options generator and the
>> renderer; the options generator generates a options.scm controller object,
>> and the renderer takes options and outputs html.
>>
>> I understand unit testing to handle testing of ‘leaf’ functions e.g.
>> (split->date), rather than the controller code (e.g. renderer takes options
>> and outputs html) – but to me this is rather silly because split->date only
>> tests xaccTransGetDate and xaccSplitGetParent, whereas the controller tests
>> actual functionality.
>>
>> With regards to unit testing I can see several issues
>>
>> 1) The refactored report has inlined most single-use functions into
>> lambda expressions – I figured that directly stating (xaccTransGetDate
>> (xaccSplitGetParent split)) is much more descriptive to a programmer than
>> to create a testable leaf function (split->date split). I can see the
>> benefits of both – leave as lambda expressions which will can be
>> understandable by anyone who is familiar with the API, or break them out
>> into 100s of single use functions which can be tested, but introduces a
>> whole layer of cognitive load to anyone hacking code – (what does
>> split->date actually do? Where is its definition). Also, breaking the
>> lambda functions into testable functions means the implementation is frozen
>> and the next hacker will have lesser scope to rework/optimise the report.
>>
>> 2) The refactored report is now flexible enough to accommodate derived
>> reports with a different multicolumn data function – eg
>> income-gst-statement.scm has been reworked into a transaction.scm
>> derivative which passes its own calculated-cells to report on GST sales and
>> purchases. This is not yet committed.
>>
>> 3) I think the most useful testing approach for a complex transaction.scm
>> will be to test functions of various combinations of options values, and
>> test the resulting html for satisfactory output. There are now dozens of
>> bools and multichoices that can be triggered, each effecting html in
>> various ways. How best to test?
>>
>> 4) My view would be the unit test would check that:
>> a. the TR actually exists
>> b. it can display empty-report
>> c. it can understand passing of custom-calculated-cells
>> d. each of the options can be toggled, and the resulting html
>> displays/hides cells/detail as expected
>> e. and sorting options generate sorted rows
>>
>> Comments welcome, I had no formal training ☹
>> ___
>> gnucash-devel mailing list
>> gnucash-devel@gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: how exactly to do unit testing in scheme...

[Phil Longstaff]

Usually, unit testing controller code is done by writing mocks for the code
that is called. In this case, this would be the options.scm controller and
the renderer. The mock code would test that the expected arguments are
passed, and would return a canned response. This both checks the logic of
the controller but also allows error and other paths to be tested.

On Wed, Jan 24, 2018 at 11:03 AM, Christopher Lam <christopher@gmail.com
> wrote:

> Dear Devel
>
> To rgmerk: Welcome back, and it was a nice to meet irl!
>
> While simplifying transaction.scm and thinking of unit testing, I now have
> a conundrum worthy of an expert view.
>
> The reports require 2 main functions – the options generator and the
> renderer; the options generator generates a options.scm controller object,
> and the renderer takes options and outputs html.
>
> I understand unit testing to handle testing of ‘leaf’ functions e.g.
> (split->date), rather than the controller code (e.g. renderer takes options
> and outputs html) – but to me this is rather silly because split->date only
> tests xaccTransGetDate and xaccSplitGetParent, whereas the controller tests
> actual functionality.
>
> With regards to unit testing I can see several issues
>
> 1) The refactored report has inlined most single-use functions into lambda
> expressions – I figured that directly stating (xaccTransGetDate
> (xaccSplitGetParent split)) is much more descriptive to a programmer than
> to create a testable leaf function (split->date split). I can see the
> benefits of both – leave as lambda expressions which will can be
> understandable by anyone who is familiar with the API, or break them out
> into 100s of single use functions which can be tested, but introduces a
> whole layer of cognitive load to anyone hacking code – (what does
> split->date actually do? Where is its definition). Also, breaking the
> lambda functions into testable functions means the implementation is frozen
> and the next hacker will have lesser scope to rework/optimise the report.
>
> 2) The refactored report is now flexible enough to accommodate derived
> reports with a different multicolumn data function – eg
> income-gst-statement.scm has been reworked into a transaction.scm
> derivative which passes its own calculated-cells to report on GST sales and
> purchases. This is not yet committed.
>
> 3) I think the most useful testing approach for a complex transaction.scm
> will be to test functions of various combinations of options values, and
> test the resulting html for satisfactory output. There are now dozens of
> bools and multichoices that can be triggered, each effecting html in
> various ways. How best to test?
>
> 4) My view would be the unit test would check that:
> a. the TR actually exists
> b. it can display empty-report
> c. it can understand passing of custom-calculated-cells
> d. each of the options can be toggled, and the resulting html
> displays/hides cells/detail as expected
> e. and sorting options generate sorted rows
>
> Comments welcome, I had no formal training ☹
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

how exactly to do unit testing in scheme...

[Christopher Lam]

Dear Devel 

To rgmerk: Welcome back, and it was a nice to meet irl!

While simplifying transaction.scm and thinking of unit testing, I now have a 
conundrum worthy of an expert view.

The reports require 2 main functions – the options generator and the renderer; 
the options generator generates a options.scm controller object, and the 
renderer takes options and outputs html.

I understand unit testing to handle testing of ‘leaf’ functions e.g. 
(split->date), rather than the controller code (e.g. renderer takes options and 
outputs html) – but to me this is rather silly because split->date only tests 
xaccTransGetDate and xaccSplitGetParent, whereas the controller tests actual 
functionality.

With regards to unit testing I can see several issues

1) The refactored report has inlined most single-use functions into lambda 
expressions – I figured that directly stating (xaccTransGetDate 
(xaccSplitGetParent split)) is much more descriptive to a programmer than to 
create a testable leaf function (split->date split). I can see the benefits of 
both – leave as lambda expressions which will can be understandable by anyone 
who is familiar with the API, or break them out into 100s of single use 
functions which can be tested, but introduces a whole layer of cognitive load 
to anyone hacking code – (what does split->date actually do? Where is its 
definition). Also, breaking the lambda functions into testable functions means 
the implementation is frozen and the next hacker will have lesser scope to 
rework/optimise the report.

2) The refactored report is now flexible enough to accommodate derived reports 
with a different multicolumn data function – eg income-gst-statement.scm has 
been reworked into a transaction.scm derivative which passes its own 
calculated-cells to report on GST sales and purchases. This is not yet 
committed.

3) I think the most useful testing approach for a complex transaction.scm will 
be to test functions of various combinations of options values, and test the 
resulting html for satisfactory output. There are now dozens of bools and 
multichoices that can be triggered, each effecting html in various ways. How 
best to test?

4) My view would be the unit test would check that:
a. the TR actually exists
b. it can display empty-report
c. it can understand passing of custom-calculated-cells
d. each of the options can be toggled, and the resulting html displays/hides 
cells/detail as expected
e. and sorting options generate sorted rows

Comments welcome, I had no formal training ☹
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Build issues and some free testing

[John Ralls]

Robert,

Cool. If they should wind up writing some nice unit tests for areas where our 
coverage is poor (pretty much everywhere) we’ll happily and gratefully take 
them.

Regards,
John Ralls

> On Jan 23, 2018, at 4:26 PM, Robert Merkel <robert.mer...@benambra.org> wrote:
> 
> Thanks all.
> 
> I realised the VM I was working with was an LTS version, and upgraded to the 
> most recent Ubuntu release.  Gnucash built without problems in the upgraded 
> VM.
> 
> It seems like the fixes were a good piece of housekeeping anyway.
> 
> Just to let you know it's looking increasingly likely I'm going to have a 
> bunch of students poking and prodding at gnucash some time in April.  I'll 
> make sure to file bug reports for any real bugs they find.  I'll ask them to 
> route any questions they have through me, so it shouldn't result in masses of 
> mailing list traffic.
> 
> Regards,
> 
> Robert.
> 
> On Wed, 24 Jan 2018 at 11:19 John Ralls <jra...@ceridwen.us 
> <mailto:jra...@ceridwen.us>> wrote:
> 
> 
> > On Jan 22, 2018, at 6:56 PM, Robert Merkel <robert.mer...@benambra.org 
> > <mailto:robert.mer...@benambra.org>> wrote:
> >
> > Hello all.
> >
> > If you dig far enough into the mailing list archives or the changelogs, you
> > might find me :)
> >
> > I spoke to Christopher Lam recently, who told me about the work he's been
> > doing on the transaction report which I worked on many many years ago.
> >
> > These days, my day job is teaching students about software engineering and,
> > this upcoming semester, I'm teaching a unit on testing and quality
> > assurance.  For one of the assignments, we need some software for students
> > to test, and I thought I might get them to test Gnucash.
> >
> > So, for the first time for quite a while, I have tried to download and
> > build gnucash from the git repository using cmake.  I've found the
> > following build issues:
> >
> > * The build process requires xsltproc and makeinfo, which are not mentioned
> > in the dependency list and cmake doesn't seem to check for them.
> >
> > * The build failed on my Ubuntu machine with the stock version of
> > libwebkit2-gtk available on that distribution (2.4.11).  It appears that
> > Gnucash requires version
> > 2.6 of this library, as "WebKitNavigationAction" was apparently added in
> > version 2.6.  Again, the minimum version isn't listed and cmake doesn't
> > have a check for it.
> 
> Hi, Robert.
> 
> Welcome back! Chris mentioned his meeting with you on IRC.
> 
> Thanks for bringing those to our attention. I've pushed a fix.
> 
> You will need to install xsltproc. In some distros it's part of the libxslt 
> package, which may be why it wasn't mentioned separately in 
> README.dependencies. You won't need makeinfo, I've made that optional. It's 
> only for an obsolete design information document that is now mostly 
> superseded by Doxygen comments.
> 
> The webkit2gtk-3.0 package provided by Ubuntu 14.04LTS is fine, and CMake did 
> correctly detect it and set the compile accordingly--the first time through. 
> If you then subsequently ran cmake again it would see that WEBKIT_FOUND was 
> true and set up for the preferred webkit2gtk-4.0. I've corrected that by 
> having separate WEBKIT2_3_FOUND and WEBKIT2_4_FOUND variables.
> 
> Regards,
> John Ralls
> 
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Build issues and some free testing

[Robert Merkel]

Thanks all.

I realised the VM I was working with was an LTS version, and upgraded to
the most recent Ubuntu release.  Gnucash built without problems in the
upgraded VM.

It seems like the fixes were a good piece of housekeeping anyway.

Just to let you know it's looking increasingly likely I'm going to have a
bunch of students poking and prodding at gnucash some time in April.  I'll
make sure to file bug reports for any real bugs they find.  I'll ask them
to route any questions they have through me, so it shouldn't result in
masses of mailing list traffic.

Regards,

Robert.

On Wed, 24 Jan 2018 at 11:19 John Ralls <jra...@ceridwen.us> wrote:

>
>
> > On Jan 22, 2018, at 6:56 PM, Robert Merkel <robert.mer...@benambra.org>
> wrote:
> >
> > Hello all.
> >
> > If you dig far enough into the mailing list archives or the changelogs,
> you
> > might find me :)
> >
> > I spoke to Christopher Lam recently, who told me about the work he's been
> > doing on the transaction report which I worked on many many years ago.
> >
> > These days, my day job is teaching students about software engineering
> and,
> > this upcoming semester, I'm teaching a unit on testing and quality
> > assurance.  For one of the assignments, we need some software for
> students
> > to test, and I thought I might get them to test Gnucash.
> >
> > So, for the first time for quite a while, I have tried to download and
> > build gnucash from the git repository using cmake.  I've found the
> > following build issues:
> >
> > * The build process requires xsltproc and makeinfo, which are not
> mentioned
> > in the dependency list and cmake doesn't seem to check for them.
> >
> > * The build failed on my Ubuntu machine with the stock version of
> > libwebkit2-gtk available on that distribution (2.4.11).  It appears that
> > Gnucash requires version
> > 2.6 of this library, as "WebKitNavigationAction" was apparently added in
> > version 2.6.  Again, the minimum version isn't listed and cmake doesn't
> > have a check for it.
>
> Hi, Robert.
>
> Welcome back! Chris mentioned his meeting with you on IRC.
>
> Thanks for bringing those to our attention. I've pushed a fix.
>
> You will need to install xsltproc. In some distros it's part of the
> libxslt package, which may be why it wasn't mentioned separately in
> README.dependencies. You won't need makeinfo, I've made that optional. It's
> only for an obsolete design information document that is now mostly
> superseded by Doxygen comments.
>
> The webkit2gtk-3.0 package provided by Ubuntu 14.04LTS is fine, and CMake
> did correctly detect it and set the compile accordingly--the first time
> through. If you then subsequently ran cmake again it would see that
> WEBKIT_FOUND was true and set up for the preferred webkit2gtk-4.0. I've
> corrected that by having separate WEBKIT2_3_FOUND and WEBKIT2_4_FOUND
> variables.
>
> Regards,
> John Ralls
>
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Build issues and some free testing

[John Ralls]

> On Jan 22, 2018, at 6:56 PM, Robert Merkel <robert.mer...@benambra.org> wrote:
> 
> Hello all.
> 
> If you dig far enough into the mailing list archives or the changelogs, you
> might find me :)
> 
> I spoke to Christopher Lam recently, who told me about the work he's been
> doing on the transaction report which I worked on many many years ago.
> 
> These days, my day job is teaching students about software engineering and,
> this upcoming semester, I'm teaching a unit on testing and quality
> assurance.  For one of the assignments, we need some software for students
> to test, and I thought I might get them to test Gnucash.
> 
> So, for the first time for quite a while, I have tried to download and
> build gnucash from the git repository using cmake.  I've found the
> following build issues:
> 
> * The build process requires xsltproc and makeinfo, which are not mentioned
> in the dependency list and cmake doesn't seem to check for them.
> 
> * The build failed on my Ubuntu machine with the stock version of
> libwebkit2-gtk available on that distribution (2.4.11).  It appears that
> Gnucash requires version
> 2.6 of this library, as "WebKitNavigationAction" was apparently added in
> version 2.6.  Again, the minimum version isn't listed and cmake doesn't
> have a check for it.

Hi, Robert. 

Welcome back! Chris mentioned his meeting with you on IRC.

Thanks for bringing those to our attention. I've pushed a fix. 

You will need to install xsltproc. In some distros it's part of the libxslt 
package, which may be why it wasn't mentioned separately in 
README.dependencies. You won't need makeinfo, I've made that optional. It's 
only for an obsolete design information document that is now mostly superseded 
by Doxygen comments.

The webkit2gtk-3.0 package provided by Ubuntu 14.04LTS is fine, and CMake did 
correctly detect it and set the compile accordingly--the first time through. If 
you then subsequently ran cmake again it would see that WEBKIT_FOUND was true 
and set up for the preferred webkit2gtk-4.0. I've corrected that by having 
separate WEBKIT2_3_FOUND and WEBKIT2_4_FOUND variables.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Build issues and some free testing

[Tommy Trussell]

On Mon, Jan 22, 2018 at 8:56 PM, Robert Merkel 
wrote:

> So, for the first time for quite a while, I have tried to download and
> build gnucash from the git repository using cmake.  I've found the
> following build issues:
>
> * The build process requires xsltproc and makeinfo, which are not mentioned
> in the dependency list and cmake doesn't seem to check for them.
>
> * The build failed on my Ubuntu machine with the stock version of
> libwebkit2-gtk available on that distribution (2.4.11).  It appears that
> Gnucash requires version
> 2.6 of this library, as "WebKitNavigationAction" was apparently added in
> version 2.6.  Again, the minimum version isn't listed and cmake doesn't
> have a check for it.
>
>
Hi -- I have been tinkering with the Ubuntu builds lately myself, but
mainly because GetDeb has gotten behind, and I'm trying to teach myself
enough packaging to figure out if I can help. Unfortunately "backporting"
even the stable GnuCash packages to Ubuntu 16.04 LTS "Xenial" in recent
months has become trickier as it drifts farther from the current release of
Debian.

You didn't mention which version of Ubuntu you are building for, nor which
release of GnuCash you're building. I presume you're probably building the
unstable release of GnuCash.

As an Ubuntu user you might find it interesting looking at the Debian
Tracker for Gnucash so you can see what the Debian maintainer for the
GnuCash package is up to. The tracker also shows the latest version that
has been automatically included in the development release of Ubuntu, and
links to the launchpad pages.

https://tracker.debian.org/pkg/gnucash

Be sure to hover over all the symbols and follow some of the links to get
more of the useful information that dense tracker page points to.

As you can see Micha Lenk is keeping close track of the 2.7 / 3.0 release
(because otherwise GnuCash was to get dropped from Debian due to the legacy
dependence upon the old webkit) but the package is only barely in
Experimental. If you notice his .dsc file for GnuCash 2.7.3 has these
dependencies (which of course are Debian package names, some of which may
differ from your version of Ubuntu):

Build-Depends: debhelper (>= 10), intltool, pkg-config, dh-python, cmake,
> googletest, guile-2.0-dev, imagemagick, libaqbanking-dev, libboost-dev,
> libboost-date-time-dev, libboost-filesystem-dev, libboost-locale-dev,
> libboost-regex-dev, libdbi-dev, libdbd-sqlite3, libglib2.0-dev,
> libsecret-1-dev, libgoffice-0.10-dev, libgtk-3-dev, libgwengui-gtk2-dev,
> libofx-dev, libwebkit2gtk-4.0-dev, libxml2-dev, libxslt1-dev, python,
> python-dev, texinfo, xsltproc, zlib1g-dev, locales-all
> Build-Conflicts: guile-1.8



As we get closer to release maybe you can add your collected hints or tips
on the relevant page(s) on the GnuCash wiki. I presume the Building page
might need new sections to cover GnuCash unstable /2.7.x/ 3.0 and the
upcoming Ubuntu 18.04 LTS "Bionic" release as it passes its freeze dates.

https://wiki.gnucash.org/wiki/Building

https://wiki.gnucash.org/wiki/Ubuntu


> __
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Build issues and some free testing

[Robert Merkel]

Hello all.

If you dig far enough into the mailing list archives or the changelogs, you
might find me :)

I spoke to Christopher Lam recently, who told me about the work he's been
doing on the transaction report which I worked on many many years ago.

These days, my day job is teaching students about software engineering and,
this upcoming semester, I'm teaching a unit on testing and quality
assurance.  For one of the assignments, we need some software for students
to test, and I thought I might get them to test Gnucash.

So, for the first time for quite a while, I have tried to download and
build gnucash from the git repository using cmake.  I've found the
following build issues:

* The build process requires xsltproc and makeinfo, which are not mentioned
in the dependency list and cmake doesn't seem to check for them.

* The build failed on my Ubuntu machine with the stock version of
libwebkit2-gtk available on that distribution (2.4.11).  It appears that
Gnucash requires version
2.6 of this library, as "WebKitNavigationAction" was apparently added in
version 2.6.  Again, the minimum version isn't listed and cmake doesn't
have a check for it.

Hope this is useful.

Regards,

Robert Merkel.

PS Specific build error follows below:

/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c: In function
‘perform_navigation_policy’:
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:604:6: error:
unknown type name ‘WebKitNavigationAction’
  WebKitNavigationAction *action =
  ^
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:605:7: error:
implicit declaration of function
‘webkit_navigation_policy_decision_get_navigation_action’
[-Werror=implicit-function-declaration]
   webkit_navigation_policy_decision_get_navigation_action (decision);
   ^
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:605:7: error:
initialization makes pointer from integer without a cast
[-Werror=int-conversion]
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:606:10: error:
implicit declaration of function
‘webkit_navigation_action_get_navigation_type’
[-Werror=implicit-function-declaration]
  if (webkit_navigation_action_get_navigation_type (action) !=
  ^
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:612:12: error:
implicit declaration of function ‘webkit_navigation_action_get_request’
[-Werror=implicit-function-declaration]
  req = webkit_navigation_action_get_request (action);
^
/home/xubuntu/src/gnucash/gnucash/html/gnc-html-webkit2.c:612:10: error:
assignment makes pointer from integer without a cast
[-Werror=int-conversion]
  req = webkit_navigation_action_get_request (action);
  ^
cc1: all warnings being treated as errors
gnucash/html/CMakeFiles/gncmod-html.dir/build.make:163: recipe for target
'gnucash/html/CMakeFiles/gncmod-html.dir/gnc-html-webkit2.c.o' failed
make[2]: *** [gnucash/html/CMakeFiles/gncmod-html.dir/gnc-html-webkit2.c.o]
Error 1
CMakeFiles/Makefile2:8610: recipe for target
'gnucash/html/CMakeFiles/gncmod-html.dir/all' failed
make[1]: *** [gnucash/html/CMakeFiles/gncmod-html.dir/all] Error 2
Makefile:160: recipe for target 'all' faile
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Jacob Zimmermann via gnucash-devel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Geert

It can be found here:

https://github.com/jacobzimmermann/gnucash-jz-snap

It's currently set-up to auto build and push all commits to that repo. I
don't know much about building flatpaks but AFAIK snap should work on
Fedora too.

Regards

Jacob

On 10/08/17 19:12, Geert Janssens wrote:
> Hi Jacob,
> 
> That's a very interesting project you have there. I haven't had the ch
ance to
> look at it as I'm totally focussed on getting gnucash ready for the fi
rst 2.7
> development snapshot which is planned for the end of the month.
> 
> After that however I will start playing with your snap package.
> 
> Are you willing to share your snap build scripts with us ?
> 
> I'm asking because I have been wanting to set up an automated nightly 
build in
> a portable format such as snap for a long time [1]. That way it would 
be
> *much* easier for linux users to test unreleased changes and provide f
eedback.
> 
> Regards,
> 
> Geert
> 
> [1]  I had flatpack in mind for this as that's what Fedora is pushing 
and
> Fedora happens to be my primary OS, but snap fits the bill equally wel
l.
-BEGIN PGP SIGNATURE-

iG0EAREIABUFAlmOORUOHHBwYUBqemltbS5uZXQACgkQsrcWi70eWMT2dQEAhI+c
y6MLu3NEyomxeNIWQ3LOY9grt57AJA8FU1PiQ4MA/i0ZtSjSvqvrGmP7k/xb3oRG
V5+uxnqQab1MpEfHmGFA
=fK9E
-END PGP SIGNATURE-
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Geert Janssens]

On woensdag 2 augustus 2017 11:40:10 CEST Jacob Zimmermann via gnucash-devel 
wrote:
> Hi all,
> 
> I have built a snap package of GNUCash and am seeking some feedback and
> testing. On Linux distros that support snap, the package can be
> installed using the following command:
> 
> sudo snap install --beta gnucash-jz
> 
> Builds for AMD64 and ARM are available.
> 
> Regards,
> Jacob

Hi Jacob,

That's a very interesting project you have there. I haven't had the chance to 
look at it as I'm totally focussed on getting gnucash ready for the first 2.7 
development snapshot which is planned for the end of the month.

After that however I will start playing with your snap package.

Are you willing to share your snap build scripts with us ?

I'm asking because I have been wanting to set up an automated nightly build in 
a portable format such as snap for a long time [1]. That way it would be 
*much* easier for linux users to test unreleased changes and provide feedback.

Regards,

Geert

[1]  I had flatpack in mind for this as that's what Fedora is pushing and 
Fedora happens to be my primary OS, but snap fits the bill equally well.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Testing attachments. Please ignore

[Derek Atkins]

Hi,
You should see a small attachment of the IHTFP logo attached to this email.
No need to respond; I'll see the email myself.
Just ensuring that actual "attachments" are not blocked (they shouldn't me).
Note that *INLINE* attachments still fail.  But actual attachments like
this should work.

Thanks, and sorry to fill your inbox.

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Jacob Zimmermann via gnucash-devel]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 05/08/17 20:07, Frank H. Ellenberger wrote:
> ... and aqbanking, ofx, ...? 
It is included as far as GNC plugins and scripts go. Standalone
non-Gnucash aqbanking scripts are not included.

> For that readers unknowing snap: > 
> https://en.wikipedia.org/wiki/Snappy_(package_manager) >
That article misses the most important advantage of Snap: the same
package is installable and works on any distro that supports Snap. There
are no Ubuntu snaps, Debian snaps, Fedora snaps etc. The same snap can
be used by everyone.
-BEGIN PGP SIGNATURE-

iG0EAREIABUFAlmGT3MOHHBwYUBqemltbS5uZXQACgkQsrcWi70eWMRYYgEAjX8H
6rHTaOVJLwEbk/FoOzaK/llcw5pcvPJWWM/x9GABAL0LRTBWrMJqK5MbDveSQJBG
hcjFTX2BCfmefE+c/6tX
=1Hbz
-END PGP SIGNATURE-

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Frank H. Ellenberger]

Hi Jakob,

Am 03.08.2017 um 00:55 schrieb Jacob Zimmermann via gnucash-devel:
> It's 2.6.17, built from upstream source, with libdbd-mysql and
> libdbd-pgsql included.

... and aqbanking, ofx, ...?

For that readers unknowing snap:
https://en.wikipedia.org/wiki/Snappy_(package_manager)

> 
> On 02/08/17 23:54, Colin Law wrote:
>> Which version of gnucash is it?
>>
>> Colin

Regards
Frank
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: FYI: GnuCash removed from Debian (testing) due to webkitgtk deprecation

[John Ralls]

> On Aug 3, 2017, at 10:00 PM, Tommy Trussell  wrote:
> 
> On Thu, Aug 3, 2017 at 1:46 PM, Tommy Trussell 
> wrote:
> 
>> As I just mentioned in the gnucash-user list, GnuCash got bumped out of
>> Debian on July 31st because it depends upon webkitgtk. I haven't seen any
>> discussion about it on this list so I figured I would mention it.
>> 
>> I haven't been in touch with the maintainer, though it's the same person
>> who has done it for years, and I presume he might have been in touch via
>> IRC or somewhere.
>> 
>> Package page: https://packages.debian.org/sid/gnucash
>> 
>> Debian Bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
>> 790204
>> 
>> 
>> 
> I don't know why my message(s) aren't appearing on gnucash-dev but I now
> see the extensive discussion at
> https://bugzilla.gnome.org/show_bug.cgi?id=751635  (linked from the Debian
> bug above).

Your messages are appearing on gnucash-dev. I didn't reply here because I 
already had replied to your message on gnucash-user.

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: FYI: GnuCash removed from Debian (testing) due to webkitgtk deprecation

[Tommy Trussell]

On Thu, Aug 3, 2017 at 1:46 PM, Tommy Trussell 
wrote:

> As I just mentioned in the gnucash-user list, GnuCash got bumped out of
> Debian on July 31st because it depends upon webkitgtk. I haven't seen any
> discussion about it on this list so I figured I would mention it.
>
> I haven't been in touch with the maintainer, though it's the same person
> who has done it for years, and I presume he might have been in touch via
> IRC or somewhere.
>
> Package page: https://packages.debian.org/sid/gnucash
>
> Debian Bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
> 790204
>
>
>
I don't know why my message(s) aren't appearing on gnucash-dev but I now
see the extensive discussion at
https://bugzilla.gnome.org/show_bug.cgi?id=751635  (linked from the Debian
bug above).
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

FYI: GnuCash removed from Debian (testing) due to webkitgtk deprecation

[Tommy Trussell]

As I just mentioned in the gnucash-user list, GnuCash got bumped out of
Debian on July 31st because it depends upon webkitgtk. I haven't seen any
discussion about it on this list so I figured I would mention it.

I haven't been in touch with the maintainer, though it's the same person
who has done it for years, and I presume he might have been in touch via
IRC or somewhere.

Package page: https://packages.debian.org/sid/gnucash

Debian Bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790204
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Jacob Zimmermann via gnucash-devel]

It's 2.6.17, built from upstream source, with libdbd-mysql and
libdbd-pgsql included.


On 02/08/17 23:54, Colin Law wrote:
> Which version of gnucash is it?
>
> Colin
>




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Call for testing: snap package

[Colin Law]

Which version of gnucash is it?

Colin

On 2 August 2017 at 10:40, Jacob Zimmermann via gnucash-devel
<gnucash-devel@gnucash.org> wrote:
> Hi all,
>
> I have built a snap package of GNUCash and am seeking some feedback and
> testing. On Linux distros that support snap, the package can be
> installed using the following command:
>
> sudo snap install --beta gnucash-jz
>
> Builds for AMD64 and ARM are available.
>
> Regards,
> Jacob
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Call for testing: snap package

[Jacob Zimmermann via gnucash-devel]

Hi all,

I have built a snap package of GNUCash and am seeking some feedback and
testing. On Linux distros that support snap, the package can be
installed using the following command:

sudo snap install --beta gnucash-jz

Builds for AMD64 and ARM are available.

Regards,
Jacob

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [PATCH] Small typos found while testing Lithuanian translation

[Cristian Marchi]

Patches committed...Thanks for your work!

Regards Cristian

Il 07/07/2013 14:53, Aurimas Fis(eras ha scritto:



___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [PATCH] Small typos found while testing Lithuanian translation

[Aurimas Fišeras]

2013.07.08 23:03, Cristian Marchi rašė:
 Patches committed...Thanks for your work!
 
 Regards Cristian
 
Hello, Cristian,
for some reason I don't see the last patch (Lithuanian translation
update) applied in GitHub:
https://github.com/Gnucash/gnucash/commits/trunk

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[PATCH] Small typos found while testing Lithuanian translation

[Aurimas Fišeras]

From c6f7608d8919f116dc08b33b0215cb65aac42e0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Aurimas=20Fi=C5=A1eras?= auri...@members.fsf.org
Date: Sun, 7 Jul 2013 15:49:38 +0300
Subject: Payable/Receivable Aging: fix translation of table headers

---
 src/report/business-reports/aging.scm | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/report/business-reports/aging.scm b/src/report/business-reports/aging.scm
index 9d56404..a59d0be 100644
--- a/src/report/business-reports/aging.scm
+++ b/src/report/business-reports/aging.scm
@@ -460,13 +460,13 @@ totals to report currency)
   ;; more general interval scheme in this report
   (define (make-heading-list)
 (list 
- (N_ Company)
- (N_ Current)
- (N_ 0-30 days)
- (N_ 31-60 days)
- (N_ 61-90 days)
- (N_ 91+ days)
- (N_ Total)))
+ (_ Company)
+ (_ Current)
+ (_ 0-30 days)
+ (_ 31-60 days)
+ (_ 61-90 days)
+ (_ 91+ days)
+ (_ Total)))
 
 
   ;;  Make a list of commodity collectors for column totals
-- 
1.8.3.2

From a13c90ba1721bca637d419bb4cba9fbda383af1a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Aurimas=20Fi=C5=A1eras?= auri...@members.fsf.org
Date: Sun, 7 Jul 2013 15:30:09 +0300
Subject: Price Scatterplot: fix typo preventing dash marker usage

---
 src/report/standard-reports/price-scatter.scm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/report/standard-reports/price-scatter.scm b/src/report/standard-reports/price-scatter.scm
index 5897e93..1c5c9d7 100644
--- a/src/report/standard-reports/price-scatter.scm
+++ b/src/report/standard-reports/price-scatter.scm
@@ -210,7 +210,7 @@
 ((square) square)
 ((cross) x)
 ((plus) plus)
-((dash) dasg)
+((dash) dash)
 ((filleddiamond) filledDiamond)
 ((filledcircle) filledCircle)
 ((filledsquare) filledSquare)))
-- 
1.8.3.2

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Unit Testing (was: Re: Notification mails for git repos)

[Geert Janssens]

On 31-01-13 19:04, John Ralls wrote:



How can we in the future improve our process to something in which the
history clearly reflects what actually happened, in which no work is
lost (by forgetting to backport) and without too much overhead.

And also test/review changes before they go into the release branch?

The generally accepted best practice for that is to require 100% test coverage 
and to require that all tests (including a new one that covers the current 
change) pass. It doesn't seem likely that we would adopt that practice.

No, we're not set up for that. But I believe it should be one of our goals to 
get better test coverage. I know you have this on your agenda and I'm quite 
happy about it.
A couple of times I started looking into writing tests myself, but never 
managed to actually produce some due to lack of time and experience. Perhaps 
this is a good time to ask:
a. do you know of a good introduction to unit testing ?
b. is there some documentation on the unit testing framework used in gnucash ? 
How should a test be constructed ? Are there particular functions that should 
be used ? Things like that.


We have a wiki page [2] on the subject, but it's a bit light. I'll work on that 
a bit. Perhaps you (and others) could look it over and suggest more topics that 
it needs to cover.

Regards,
John Ralls

[1] http://wiki.gnucash.org/wiki/Development_Process#Changeset_Auditing_Process
[2] http://wiki.gnucash.org/wiki/Testing

The wiki page is already a good starting point. Thanks. For some reason 
I hadn't found it before (probably didn't look hard enough).


Any reason you have decided to the unstable documentation of the GLib 
testing framework ?


Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Unit Testing (was: Re: Notification mails for git repos)

[John Ralls]

On Jan 31, 2013, at 11:32 AM, Geert Janssens janssens-ge...@telenet.be wrote:

 On 31-01-13 19:04, John Ralls wrote:
 
 How can we in the future improve our process to something in which the
 history clearly reflects what actually happened, in which no work is
 lost (by forgetting to backport) and without too much overhead.
 And also test/review changes before they go into the release branch?
 The generally accepted best practice for that is to require 100% test 
 coverage and to require that all tests (including a new one that covers 
 the current change) pass. It doesn't seem likely that we would adopt that 
 practice.
 No, we're not set up for that. But I believe it should be one of our goals 
 to get better test coverage. I know you have this on your agenda and I'm 
 quite happy about it.
 A couple of times I started looking into writing tests myself, but never 
 managed to actually produce some due to lack of time and experience. 
 Perhaps this is a good time to ask:
 a. do you know of a good introduction to unit testing ?
 b. is there some documentation on the unit testing framework used in 
 gnucash ? How should a test be constructed ? Are there particular functions 
 that should be used ? Things like that.
 
 We have a wiki page [2] on the subject, but it's a bit light. I'll work on 
 that a bit. Perhaps you (and others) could look it over and suggest more 
 topics that it needs to cover.
 
 Regards,
 John Ralls
 
 [1] 
 http://wiki.gnucash.org/wiki/Development_Process#Changeset_Auditing_Process
 [2] http://wiki.gnucash.org/wiki/Testing
 
 The wiki page is already a good starting point. Thanks. For some reason I 
 hadn't found it before (probably didn't look hard enough).
 
 Any reason you have decided to the unstable documentation of the GLib testing 
 framework ?

Sloth. When I'm working on that stuff, it's on master branches and I need to 
use the latest docs, so that's what I have bookmarked. Shouldn't have changed 
significantly, though: The first page of changes [1] goes back to 2008.

Regards,
John Ralls

[1] http://git.gnome.org/browse/glib/log/glib/gtestutils.c


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Geert Janssens]

On 14-01-13 00:17, Yawar Amin wrote:

Geert,

On 2013-01-13 14:07, Geert Janssens wrote:

[...]
Backporting follows these general criteria:
- only bugfixes are backported, not enhancements.
- and then only if the backport is fairly trivial. Complex fixes will
not be backported because the risk on new bugs in the fixes is too high.
[...]

This is excellent information. I'm berating myself a little now for not
searching the wiki before asking about this. The Subversion page
(http://wiki.gnucash.org/wiki/Subversion#Backport_Rules) has pretty much
exactly what you told me.

Still, I've added some more details to that wiki page taken from an
earlier email of yours that I just read through properly:
http://wiki.gnucash.org/wiki/Subversion#Backport_comment_format

So now I have a much better understanding of backporting.

Thanks muchly,

Yawar



You're welcome and thanks for taking the time to improve the wiki page.

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Geert Janssens]

On 12-01-13 20:44, Yawar Amin wrote:

Hi folks,

On 2013-01-12 13:44, Yawar Amin wrote:

[...]
Excellent! That's exactly what I needed. Am writing this up in the wiki
(http://wiki.gnucash.org/wiki/Documentation_Update_Instructions) now.

Wiki update done. Let me know if any mistakes/changes needed.

http://wiki.gnucash.org/wiki/Documentation_Update_Instructions#Step_7_-_test_documentation_in_Linux

Thanks,

Yawar



Your explanation looks clear to me. Thanks for adding it to the wiki !

Regarding your comment in 7.3: it is indeed not possible to use the 
XDG_DATA_DIRS method to load a different set of documentation for the 
system-installed gnucash. This is because the 2.4 series uses a 
different mechanism to locate the documentation, which is hard-coded at 
compile time. So XDG_DATA_DIRS only works with fairly recent trunk 
builds and for future system-installed gnucash starting from GnuCash 2.6.


Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Yawar Amin]

Hi Geert,

On 2013-01-13, at 10:28, Geert Janssens janssens-ge...@telenet.be wrote:

 Regarding your comment in 7.3: it is indeed not possible to use the 
 XDG_DATA_DIRS method to load a different set of documentation for the 
 system-installed gnucash. This is because the 2.4 series uses a different 
 mechanism to locate the documentation, which is hard-coded at compile time. 
 So XDG_DATA_DIRS only works with fairly recent trunk builds and for future 
 system-installed gnucash starting from GnuCash 2.6.

Ah, that makes sense. I'll update the wiki page with that. In general, are 
improvements like this not often backported to 2.4? I'm not very familiar with 
the GnuCash release management policies, sorry for asking n00b questions :-)

Thanks,

Yawar


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Geert Janssens]

On 13-01-13 19:44, Yawar Amin wrote:

Hi Geert,

On 2013-01-13, at 10:28, Geert Janssens janssens-ge...@telenet.be wrote:


Regarding your comment in 7.3: it is indeed not possible to use the 
XDG_DATA_DIRS method to load a different set of documentation for the 
system-installed gnucash. This is because the 2.4 series uses a different 
mechanism to locate the documentation, which is hard-coded at compile time. So 
XDG_DATA_DIRS only works with fairly recent trunk builds and for future 
system-installed gnucash starting from GnuCash 2.6.

Ah, that makes sense. I'll update the wiki page with that. In general, are 
improvements like this not often backported to 2.4? I'm not very familiar with 
the GnuCash release management policies, sorry for asking n00b questions :-)

Thanks,

Yawar


Yawar,

Feel free to ask any question, n00b or advanced :)

Backporting follows these general criteria:
- only bugfixes are backported, not enhancements.
- and then only if the backport is fairly trivial. Complex fixes will 
not be backported because the risk on new bugs in the fixes is too high.


Exceptions exist, but must be evaluated case by case if it makes sense 
to backport.


For example during the 2.4.9 cycle it was decided to backport the 
changes required to get the Windows build working with guile 1.8. This 
was a difficult decision because it was a very complex code change. On 
the other hand it only influenced the Windows build and the Windows 
specific code was becoming increasingly difficult to maintain if we 
continued depending with guile 1.6. So eventually it was agreed to 
proceed anyway with this backport. It cost us the 2.4.9 release 
(completely broken on Windows) to get it straight.


The change to allow documentation testing based on XDG_DATA_DIRS is not 
a bugfix but an enhancement. So by the above criteria it's normally not 
backported. It could be argued that only developers would notice (and 
benefit from) this change so a backport could be considered.


However, this change is actually a side effect of a much larger effort 
drop all libgnome dependencies (GnuCash is still a Gnome program, but 
Gnome itself has abandoned libgnome). This effort touches many parts of 
the code and are not suited for backporting. That's a second reason the 
XDG_DATA_DIRS changes aren't backported.


Hopefully that clears it up a bit.

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Yawar Amin]

Geert,

On 2013-01-13 14:07, Geert Janssens wrote:
 [...]
 Backporting follows these general criteria:
 - only bugfixes are backported, not enhancements.
 - and then only if the backport is fairly trivial. Complex fixes will
 not be backported because the risk on new bugs in the fixes is too high.
 [...]

This is excellent information. I'm berating myself a little now for not
searching the wiki before asking about this. The Subversion page
(http://wiki.gnucash.org/wiki/Subversion#Backport_Rules) has pretty much
exactly what you told me.

Still, I've added some more details to that wiki page taken from an
earlier email of yours that I just read through properly:
http://wiki.gnucash.org/wiki/Subversion#Backport_comment_format

So now I have a much better understanding of backporting.

Thanks muchly,

Yawar




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Yawar Amin]

Hi Geert,

On 2013-01-12 06:44, Geert Janssens wrote:
 [...]
 Now to be able to load the locally installed docs from within gnucash,
 you can run
 XDG_DATA_DIRS=/home/geert/gnucash-docs/share/:/usr/local/share/:/usr/share/
 /home/geert/gnucash/bin/gnucash

 [...]

Excellent! That's exactly what I needed. Am writing this up in the wiki
(http://wiki.gnucash.org/wiki/Documentation_Update_Instructions) now.

Thanks a lot,

Yawar




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Yawar Amin]

Hi folks,

On 2013-01-12 13:44, Yawar Amin wrote:
 [...]
 Excellent! That's exactly what I needed. Am writing this up in the wiki
 (http://wiki.gnucash.org/wiki/Documentation_Update_Instructions) now.

Wiki update done. Let me know if any mistakes/changes needed.

http://wiki.gnucash.org/wiki/Documentation_Update_Instructions#Step_7_-_test_documentation_in_Linux

Thanks,

Yawar




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Testing docs in development version

[Yawar Amin]

Hi Geert,

In http://svn.gnucash.org/trac/changeset/22378 you said that there would
be a way to test the help documentation on Linux when building and
testing from source--can you point me to how to do that? I.e. how to
solve the problem of Yelp not finding gnucash-help and gnucash-guide
when I've them built from source.

If anybody else knows how to do this, please feel free to chip in.

Thanks,

Yawar




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Testing docs in development version

[Yawar Amin]

On 2013-01-11 20:25, Yawar Amin wrote:
 Hi Geert,

 In http://svn.gnucash.org/trac/changeset/22378 you said that there would
 be a way to test the help documentation on Linux when building and
 testing from source--can you point me to how to do that? I.e. how to
 solve the problem of Yelp not finding gnucash-help and gnucash-guide
 when I've them built from source.

 If anybody else knows how to do this, please feel free to chip in.

I should have also mentioned that I'm trying to test the docs with both
GnuCash and the docs built from source, GnuCash installed under my home
directory, and the docs not installed at all.

I'm guessing I'll need to install the docs somewhere at least, and then
do something to tell Yelp (or scrollkeeper?) where that is.

But I don't have a solid idea, so any help appreciated.

Yawar




signature.asc
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r22127 - gnucash/trunk/src/engine - Testing: Unit tests for Split.c

[Christian Stimming]

Alex,

I've just committed a small bugfix for those two minor issues. Does it work 
for you now?

Regards,

Christian

Am Samstag, 31. März 2012, 16:03:40 schrieb Alex Aycinena:
 On Sat, Mar 31, 2012 at 3:59 PM, Alex Aycinena alex.aycin...@gmail.com 
wrote:
  John,
  
  On Sat, Mar 31, 2012 at 3:12 PM, John Ralls jra...@code.gnucash.org 
wrote:
  Author: jralls
  Date: 2012-03-31 18:12:36 -0400 (Sat, 31 Mar 2012)
  New Revision: 22127
  Trac: http://svn.gnucash.org/trac/changeset/22127
  
  Added:
gnucash/trunk/src/engine/test/utest-Split.c
  Modified:
gnucash/trunk/src/engine/Split.c
gnucash/trunk/src/engine/SplitP.h
gnucash/trunk/src/engine/test/Makefile.am
gnucash/trunk/src/engine/test/test-engine.c
  Log:
  Testing: Unit tests for Split.c
  
  ___
  gnucash-patches mailing list
  gnucash-patc...@gnucash.org
  https://lists.gnucash.org/mailman/listinfo/gnucash-patches
  
  It's not building because of:
  
  /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-S
  plit.c:485:1: error: /* within comment [-Werror=comment]
  /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-S
  plit.c:486:1: error: /* within comment [-Werror=comment]
  /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-S
  plit.c:1620:1: error: /* within comment [-Werror=comment]
  cc1: all warnings being treated as errors
  make[5]: *** [utest-Split.lo] Error 1
  make[5]: Leaving directory
  `/home/gnucash-dev/svncheckouts/gnucash-working-t-build/src/engine/test'
  
  Regards,
  
  Alex
 
 Also,
 
 /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/test-engine
 .c: In function ‘main’:
 /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/test-engine
 .c:46:5: error: implicit declaration of function ‘test_suite_split’
 [-Werror=implicit-function-declaration]
 cc1: all warnings being treated as errors
 make[5]: *** [test_engine-test-engine.o] Error 1
 
 Alex


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r22127 - gnucash/trunk/src/engine - Testing: Unit tests for Split.c

[Alex Aycinena]

John,


On Sat, Mar 31, 2012 at 3:12 PM, John Ralls jra...@code.gnucash.org wrote:
 Author: jralls
 Date: 2012-03-31 18:12:36 -0400 (Sat, 31 Mar 2012)
 New Revision: 22127
 Trac: http://svn.gnucash.org/trac/changeset/22127

 Added:
   gnucash/trunk/src/engine/test/utest-Split.c
 Modified:
   gnucash/trunk/src/engine/Split.c
   gnucash/trunk/src/engine/SplitP.h
   gnucash/trunk/src/engine/test/Makefile.am
   gnucash/trunk/src/engine/test/test-engine.c
 Log:
 Testing: Unit tests for Split.c

 ___
 gnucash-patches mailing list
 gnucash-patc...@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-patches

It's not building because of:

/home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:485:1:
error: /* within comment [-Werror=comment]
/home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:486:1:
error: /* within comment [-Werror=comment]
/home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:1620:1:
error: /* within comment [-Werror=comment]
cc1: all warnings being treated as errors
make[5]: *** [utest-Split.lo] Error 1
make[5]: Leaving directory
`/home/gnucash-dev/svncheckouts/gnucash-working-t-build/src/engine/test'

Regards,

Alex

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r22127 - gnucash/trunk/src/engine - Testing: Unit tests for Split.c

[Alex Aycinena]

On Sat, Mar 31, 2012 at 3:59 PM, Alex Aycinena alex.aycin...@gmail.com wrote:
 John,


 On Sat, Mar 31, 2012 at 3:12 PM, John Ralls jra...@code.gnucash.org wrote:
 Author: jralls
 Date: 2012-03-31 18:12:36 -0400 (Sat, 31 Mar 2012)
 New Revision: 22127
 Trac: http://svn.gnucash.org/trac/changeset/22127

 Added:
   gnucash/trunk/src/engine/test/utest-Split.c
 Modified:
   gnucash/trunk/src/engine/Split.c
   gnucash/trunk/src/engine/SplitP.h
   gnucash/trunk/src/engine/test/Makefile.am
   gnucash/trunk/src/engine/test/test-engine.c
 Log:
 Testing: Unit tests for Split.c

 ___
 gnucash-patches mailing list
 gnucash-patc...@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-patches

 It's not building because of:

 /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:485:1:
 error: /* within comment [-Werror=comment]
 /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:486:1:
 error: /* within comment [-Werror=comment]
 /home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/utest-Split.c:1620:1:
 error: /* within comment [-Werror=comment]
 cc1: all warnings being treated as errors
 make[5]: *** [utest-Split.lo] Error 1
 make[5]: Leaving directory
 `/home/gnucash-dev/svncheckouts/gnucash-working-t-build/src/engine/test'

 Regards,

 Alex

Also,

/home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/test-engine.c:
In function ‘main’:
/home/gnucash-dev/svncheckouts/gnucash-working-t/src/engine/test/test-engine.c:46:5:
error: implicit declaration of function ‘test_suite_split’
[-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
make[5]: *** [test_engine-test-engine.o] Error 1

Alex

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21829 - gnucash/trunk/src/libqof/qof - [GSOC][Testing] Modifications to qofsession for testability

[Alex Aycinena]

John,

Trunk doesn't build with:

/home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:705:1:
error: no previous prototype for 'qof_instance_copy_to_session'
[-Werror=missing-prototypes]
/home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:745:10:
error: no previous prototype for 'qof_instance_copy_list'
[-Werror=missing-prototypes]
/home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:771:1:
error: no previous prototype for 'qof_instance_copy_coll'
[-Werror=missing-prototypes]
/home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:944:1:
error: no previous prototype for 'qof_instance_copy_coll_r'
[-Werror=missing-prototypes]
/home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:966:10:
error: no previous prototype for 'qof_instance_copy_one_r'
[-Werror=missing-prototypes]
cc1: all warnings being treated as errors

Alex

On Mon, Jan 9, 2012 at 3:09 PM, John Ralls jra...@code.gnucash.org wrote:
 Author: jralls
 Date: 2012-01-09 18:09:47 -0500 (Mon, 09 Jan 2012)
 New Revision: 21829
 Trac: http://svn.gnucash.org/trac/changeset/21829

 Modified:
   gnucash/trunk/src/libqof/qof/Makefile.am
   gnucash/trunk/src/libqof/qof/qofsession-p.h
   gnucash/trunk/src/libqof/qof/qofsession.c
 Log:
 [GSOC][Testing] Modifications to qofsession for testability

 Author: Muslim Chochlov

 ___
 gnucash-patches mailing list
 gnucash-patc...@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-patches

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21829 - gnucash/trunk/src/libqof/qof - [GSOC][Testing] Modifications to qofsession for testability

[John Ralls]

On Jan 9, 2012, at 4:53 PM, Alex Aycinena wrote:

 John,
 
 Trunk doesn't build with:
 
 /home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:705:1:
 error: no previous prototype for 'qof_instance_copy_to_session'
 [-Werror=missing-prototypes]
 /home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:745:10:
 error: no previous prototype for 'qof_instance_copy_list'
 [-Werror=missing-prototypes]
 /home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:771:1:
 error: no previous prototype for 'qof_instance_copy_coll'
 [-Werror=missing-prototypes]
 /home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:944:1:
 error: no previous prototype for 'qof_instance_copy_coll_r'
 [-Werror=missing-prototypes]
 /home/gnucash-dev/svncheckouts/gnucash-clean/src/libqof/qof/qofsession.c:966:10:
 error: no previous prototype for 'qof_instance_copy_one_r'
 [-Werror=missing-prototypes]
 cc1: all warnings being treated as errors

Alex,

Darn it, I meant to add that flag to my CFLAGS the last time you caught me with 
it and forgot. It's in now, and the warnings are fixed, too.

Thanks.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Testing

[Derek Atkins]

Just a test of the mailing list.  Please ignore.

-derek
-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21677 - gnucash/trunk/src/gnc-module/test - [Testing] Gnc-module: Provide checked error messages to replace noted warnings (c-files only)

[Geert Janssens]

Op zondag 4 december 2011 19:08:10 schreef John Ralls:
 Author: jralls
 Date: 2011-12-04 19:08:10 -0500 (Sun, 04 Dec 2011)
 New Revision: 21677
 Trac: http://svn.gnucash.org/trac/changeset/21677
 
 Modified:
gnucash/trunk/src/gnc-module/test/misc-mods/Makefile.am
gnucash/trunk/src/gnc-module/test/test-agedver.c
gnucash/trunk/src/gnc-module/test/test-dynload.c
gnucash/trunk/src/gnc-module/test/test-incompatdep.c
gnucash/trunk/src/gnc-module/test/test-load-c.c
gnucash/trunk/src/gnc-module/test/test-modsysver.c
 Log:
 [Testing] Gnc-module: Provide checked error messages to replace noted
 warnings (c-files only)
 
 
 Much better for expected warnings to be tested for than to have a lead-in
 message saying that they're really OK.
 
 Don't have the test utilities in Scheme yet.
 
 Set the phony modules in misc-modules to be libtool modules instead of
 shared libraries. Aside from being more correct, this ensures that they'll
 have the same name on Linux and OSX.
 
 ___
 gnucash-patches mailing list
 gnucash-patc...@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-patches

When I started my fixes on the tests (which you have nicely completed), I 
considered backporting the changes to the 2.4 branch. I did port most of my 
changes like that.

Would it make sense to backport your test fixes and if so, before 2.4.9 is 
released this weekend ?

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21677 - gnucash/trunk/src/gnc-module/test - [Testing] Gnc-module: Provide checked error messages to replace noted warnings (c-files only)

[John Ralls]

On Dec 7, 2011, at 3:30 AM, Geert Janssens wrote:

 Op zondag 4 december 2011 19:08:10 schreef John Ralls:
 Author: jralls
 Date: 2011-12-04 19:08:10 -0500 (Sun, 04 Dec 2011)
 New Revision: 21677
 Trac: http://svn.gnucash.org/trac/changeset/21677
 
 Modified:
   gnucash/trunk/src/gnc-module/test/misc-mods/Makefile.am
   gnucash/trunk/src/gnc-module/test/test-agedver.c
   gnucash/trunk/src/gnc-module/test/test-dynload.c
   gnucash/trunk/src/gnc-module/test/test-incompatdep.c
   gnucash/trunk/src/gnc-module/test/test-load-c.c
   gnucash/trunk/src/gnc-module/test/test-modsysver.c
 Log:
 [Testing] Gnc-module: Provide checked error messages to replace noted
 warnings (c-files only)
 
 
 Much better for expected warnings to be tested for than to have a lead-in
 message saying that they're really OK.
 
 Don't have the test utilities in Scheme yet.
 
 Set the phony modules in misc-modules to be libtool modules instead of
 shared libraries. Aside from being more correct, this ensures that they'll
 have the same name on Linux and OSX.
 
 ___
 gnucash-patches mailing list
 gnucash-patc...@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-patches
 
 When I started my fixes on the tests (which you have nicely completed), I 
 considered backporting the changes to the 2.4 branch. I did port most of my 
 changes like that.
 
 Would it make sense to backport your test fixes and if so, before 2.4.9 is 
 released this weekend ?
 

I'm not done yet. There are still messages that need to be suppressed.

I don't see any real benefit to backporting it. It wouldn't do any harm, but 
it's not user-facing and it's not likely to have any affect on quality in 2.4.

Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21677 - gnucash/trunk/src/gnc-module/test - [Testing] Gnc-module: Provide checked error messages to replace noted warnings (c-files only)

[Geert Janssens]

Op woensdag 7 december 2011 06:56:54 schreef John Ralls:
 On Dec 7, 2011, at 3:30 AM, Geert Janssens wrote:
  Op zondag 4 december 2011 19:08:10 schreef John Ralls:
  Author: jralls
  Date: 2011-12-04 19:08:10 -0500 (Sun, 04 Dec 2011)
  New Revision: 21677
  Trac: http://svn.gnucash.org/trac/changeset/21677
  
  Modified:
gnucash/trunk/src/gnc-module/test/misc-mods/Makefile.am
gnucash/trunk/src/gnc-module/test/test-agedver.c
gnucash/trunk/src/gnc-module/test/test-dynload.c
gnucash/trunk/src/gnc-module/test/test-incompatdep.c
gnucash/trunk/src/gnc-module/test/test-load-c.c
gnucash/trunk/src/gnc-module/test/test-modsysver.c
  
  Log:
  [Testing] Gnc-module: Provide checked error messages to replace noted
  warnings (c-files only)
  
  
  Much better for expected warnings to be tested for than to have a
  lead-in message saying that they're really OK.
  
  Don't have the test utilities in Scheme yet.
  
  Set the phony modules in misc-modules to be libtool modules instead of
  shared libraries. Aside from being more correct, this ensures that
  they'll have the same name on Linux and OSX.
  
  ___
  gnucash-patches mailing list
  gnucash-patc...@gnucash.org
  https://lists.gnucash.org/mailman/listinfo/gnucash-patches
  
  When I started my fixes on the tests (which you have nicely completed),
  I
  considered backporting the changes to the 2.4 branch. I did port most of
  my changes like that.
  
  Would it make sense to backport your test fixes and if so, before 2.4.9
  is released this weekend ?
 
 I'm not done yet. There are still messages that need to be suppressed.
 
 I don't see any real benefit to backporting it. It wouldn't do any harm, but
 it's not user-facing and it's not likely to have any affect on quality in
 2.4.
 
Agreed. I more or less came to the same conclusion after I sent the question.

I was mostly thinking of distribution packagers that currently can't depend on 
make check to see if all is ok. Before your changes, some of the tests simply 
failed or emitted lots of ugly looking warnings you may or may not have been 
told to ignore before. Not really a comfortable situation to evaluate if the 
application is good to go.

But since we started planning towards 2.6 in a not so distant future, it may 
not really matter in 2.4.

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21525 - gnucash/trunk/src - [Engine Unit Testing] Unit tests for Account.c

[Christian Stimming]

Am Sonntag, 6. November 2011 schrieb John Ralls:
 Author: jralls
 Date: 2011-11-05 19:05:00 -0400 (Sat, 05 Nov 2011)
 New Revision: 21525
 Trac: http://svn.gnucash.org/trac/changeset/21525
 
 Added:
gnucash/trunk/src/engine/test/test-engine.c
gnucash/trunk/src/engine/test/utest-Account.c
 Modified:
gnucash/trunk/src/engine/Account.c
gnucash/trunk/src/engine/Account.h
gnucash/trunk/src/engine/AccountP.h
gnucash/trunk/src/engine/test/Makefile.am
gnucash/trunk/src/libqof/qof/test/Makefile.am
 Log:
 [Engine Unit Testing] Unit tests for Account.c

Thanks for starting with the large task of adding unit tests in this area!

Unfortunately, this commit contains a few compile errors:

gnc_coll_get_root_account() needs to be declared static or alternatively need 
a declaration beforehand.

g_list_free_full() in utest-Account.c:455 - The function g_list_free_full() is 
new in glib-2.28 and hence not available e.g. in my glib-2.24 on a half-year 
old Ubuntu.

src/engine/test/utest-Account.c: In function 
‘test_gnc_account_list_name_violations’:
src/engine/test/utest-Account.c:440: error: ‘msg’ is used uninitialized in 
this function

I'm not completely sure how those three errors should be fixed, so I better 
leave this up to you.

Best Regards,

Christian

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: r21525 - gnucash/trunk/src - [Engine Unit Testing] Unit tests for Account.c

[John Ralls]

On Nov 6, 2011, at 1:02 PM, Christian Stimming wrote:

 Am Sonntag, 6. November 2011 schrieb John Ralls:
 Author: jralls
 Date: 2011-11-05 19:05:00 -0400 (Sat, 05 Nov 2011)
 New Revision: 21525
 Trac: http://svn.gnucash.org/trac/changeset/21525
 
 Added:
   gnucash/trunk/src/engine/test/test-engine.c
   gnucash/trunk/src/engine/test/utest-Account.c
 Modified:
   gnucash/trunk/src/engine/Account.c
   gnucash/trunk/src/engine/Account.h
   gnucash/trunk/src/engine/AccountP.h
   gnucash/trunk/src/engine/test/Makefile.am
   gnucash/trunk/src/libqof/qof/test/Makefile.am
 Log:
 [Engine Unit Testing] Unit tests for Account.c
 
 Thanks for starting with the large task of adding unit tests in this area!
 
 Unfortunately, this commit contains a few compile errors:
 
 gnc_coll_get_root_account() needs to be declared static or alternatively need 
 a declaration beforehand.
 
 g_list_free_full() in utest-Account.c:455 - The function g_list_free_full() 
 is 
 new in glib-2.28 and hence not available e.g. in my glib-2.24 on a half-year 
 old Ubuntu.
 
 src/engine/test/utest-Account.c: In function 
 ‘test_gnc_account_list_name_violations’:
 src/engine/test/utest-Account.c:440: error: ‘msg’ is used uninitialized in 
 this function
 
 I'm not completely sure how those three errors should be fixed, so I better 
 leave this up to you.

Fixed, along with another problem I discovered when I built it on Debian Stable 
64 bit.

I guess I should set up a minimum environment to work in so I don't mess this 
up in my maximum environment.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: GSoC 2011: Data model unit testing

[Muslim Chochlov]

Hi Phil,


 Hi Muslim,

 I took a quick look at the qofbook tests.  Are this written using the
 glib test framework?


Yes they are. Actually, there were already a few tests created by John so I
just continued to follow the same path.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: GSoC 2011: Data model unit testing

[Geert Janssens]

Hi Muslim,

Welcome to the GnuCash community. You have chosen a very nice project for this 
summer. Completing it successfully will create a powerful base for future 
refactorings we are planning and it will benifit both GnuCash and Cutecash.

I intend to check out your private branch from time to time to follow your 
progress if my own busy schedule permits.

I wish you a very fulfilling experience while you work on your project.

Geert

On dinsdag 24 mei 2011, Muslim Chochlov wrote:
 Hello everyone,
 
 My name is Muslim and I'm one of the three students who contribute this
 year to Gnucash. Yesterday there was
 an official start of coding and I think you might be interested in what was
 already done and what are my further plans.
 
 The goal of my project is to document most crucial parts of code in libqof
 module such as QofInstance, QofBook, QofSession and others to allow more
 easy and less complicated refactoring. I started out by writing unit tests
 for QofBook and currently it's almost fully covered. As a part of this
 process I created 19 unit tests, added two macros to make tests writing
 easier and identified unused functions in qofbook. I currently work on
 finishing with UT for qofbook, which are 4-5 left and start investigating
 qofinstance. My plan is to start putting qofinstance functions under the
 tests from next Monday.
 
 I have a separate branch on github (https://github.com/mchochlov/Gnucash)
 where you can see all recent changes (dmut-gsoc2011). Of course you are
 welcome to give feedback by leaving comments on github or replying to
 current thread. I'll keep this thread updated to make sure you are aware
 what's the progress of my project.
 
 Regards,
 
 Muslim Chochlov
 ___
 gnucash-devel mailing list
 gnucash-devel@gnucash.org
 https://lists.gnucash.org/mailman/listinfo/gnucash-devel

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

GSoC 2011: Data model unit testing

[Muslim Chochlov]

Hello everyone,

My name is Muslim and I'm one of the three students who contribute this year
to Gnucash. Yesterday there was
an official start of coding and I think you might be interested in what was
already done and what are my further plans.

The goal of my project is to document most crucial parts of code in libqof
module such as QofInstance, QofBook, QofSession and others to allow more
easy and less complicated refactoring. I started out by writing unit tests
for QofBook and currently it's almost fully covered. As a part of this
process I created 19 unit tests, added two macros to make tests writing
easier and identified unused functions in qofbook. I currently work on
finishing with UT for qofbook, which are 4-5 left and start investigating
qofinstance. My plan is to start putting qofinstance functions under the
tests from next Monday.

I have a separate branch on github (https://github.com/mchochlov/Gnucash)
where you can see all recent changes (dmut-gsoc2011). Of course you are
welcome to give feedback by leaving comments on github or replying to
current thread. I'll keep this thread updated to make sure you are aware
what's the progress of my project.

Regards,

Muslim Chochlov
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: GSoC 2011: Data model unit testing

[Phil Longstaff]

On Tue, 2011-05-24 at 23:26 +0200, Muslim Chochlov wrote:
 Hello everyone,
 
 My name is Muslim and I'm one of the three students who contribute this year
 to Gnucash. Yesterday there was
 an official start of coding and I think you might be interested in what was
 already done and what are my further plans.
 
 The goal of my project is to document most crucial parts of code in libqof
 module such as QofInstance, QofBook, QofSession and others to allow more
 easy and less complicated refactoring. I started out by writing unit tests
 for QofBook and currently it's almost fully covered. As a part of this
 process I created 19 unit tests, added two macros to make tests writing
 easier and identified unused functions in qofbook. I currently work on
 finishing with UT for qofbook, which are 4-5 left and start investigating
 qofinstance. My plan is to start putting qofinstance functions under the
 tests from next Monday.
 
 I have a separate branch on github (https://github.com/mchochlov/Gnucash)
 where you can see all recent changes (dmut-gsoc2011). Of course you are
 welcome to give feedback by leaving comments on github or replying to
 current thread. I'll keep this thread updated to make sure you are aware
 what's the progress of my project.

Hi Muslim,

I took a quick look at the qofbook tests.  Are this written using the
glib test framework?

Phil

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GSOC] Data model unit testing

[John Ralls]

On Mar 31, 2011, at 1:20 AM, Christian Stimming wrote:

 Zitat von John Ralls jra...@ceridwen.us:
 
 I'm making good progress on the Gir2Umi program, so I hope to have a 
 skeleton UML model in another week or so. Once we have that we can assess 
 how much hand-modelling we need to do.
 
 There's no real priority within LibQof. It's at the middle of Gnucash and in 
 the way of some important changes that we need to make, and we need to be 
 sure that we don't break anything when we make those changes. That's what 
 the tests are for. It seems to me that that should make a pretty clear goal 
 for your application, too.
 
 Indeed. Thanks for the UML modelling work - I'm curious how this is going to 
 look like when it's ready :-)
 

I've got the first try ready. You can download it at 

https://github.com/jralls/gnucash/raw/introspection/src/libqof/qof/Qof-1.xmi

It loads happily into argouml and almost-happily into umbrello. In umbrello, 
the enumeration values don't show up because of a difference in the way argouml 
(actually, Oracle's jmi java library which argo uses) and umbrello interpret 
the UML DTD. To get umbrello to recognize the enumeration values, run

sed -i '/Enumeration.literal/ d' Qof-1.xmi

after you download the model.

There aren't any graphical elements in the model (those are incompatible 
between the two) and the classes are so huge that it's not really practical to 
make a picture. Class inheritance is shown (not that there's much: QofBook 
inherits from QofInstance and QofInstance from GObject.) Associations aren't 
included, but umbrello infers them automatically from attribute types.

The reason that there aren't any associations is that I used SAX in a perl 
program to process the gir file, and realized today that it's the wrong tool 
because it's sequential on the gir order of elements, so I need to rewrite it 
using DOM, which allows me to work through the tree in a more logical order and 
perhaps more importantly to adjust existing elements in the output. That's 
something I need to do to deal properly with a few issues (though associations 
for argouml aren't one of them, they're blocked by one).

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GSOC] Data model unit testing

[Muslim Chochlov]

Hi,

2011/4/2 Christian Stimming stimm...@tuhh.de

 Am Freitag, 1. April 2011 schrieb John Ralls:
  I found the most heavily used to be QofObject, Guid, and gnc-numeric with
  197, 197, and 174 external references respectively. However, the latter
  two are straightforward data manipulation libraries (which probably
 belong
  in core-utils anyway, as does gnc-date (42)) and testing will be pretty
  simple. I think you can ignore them.
 
  QofObject is an interface description which is widely used and needs to
 be
  very thoroughly tested. Next on the list is QofInstance (105), the only
  direct GObject subclass and the base class for 14 engine classes. It has
 a
  helper class, QofId (34) which will probably need to be tested in concert
  with it. qof_util.c (22) implements some important transactional
 functions
  which we need to ensure work perfectly and then use widely.
 
  QofSession (48) is very important and has some of the most convoluted
 code.
  it shares with QofBook (72) the organization of the objects upon which
  Gnucash operates. They have a major helper class KVP_Frame (71) which
  isn't in any object framework AFAICT, it's just normal functional C. It's
  one of our major problem areas with the sql backend and has no test
  coverage.

 I agree that the following list should be the highest priority for
 unittesting:
 - QofObject
 - QofInstance
 - QofSession
 - QofBook
 - kvp_frame


Then if it is ok with you, I'll consider covering the entities above with
unit tests as a final goal. There is almost three times less branching in
them, than in the whole libqof module (~1200) so I'll be able to dedicate 3
times more effort to test each case (2tests/hour).  And I guess that would
be more than realistic approach :)
If you confirm I'll make final tweaks to my proposal today or tomorrow and
hope for the best :)



   QofQuery (50), QofEvent (43), and QofClass (30) form another work group
  which is supposed to abstract data retrieval. I haven't yet worked out
  whether it's a useful abstraction, though, so perhaps it can be lower
  priority.

 Right, those would be lower priority. The QofQuery code might need
 modification and unittesting once we try to go into the multi-user backend
 direction, but that is not yet the case.

  QofBackend (10) is an interface that is tested adequately for now; its
  users are in src/backend.

 Agreed.

  QofLog (9) is mostly a wrapper around the g_log
  functions from GLib. It's not worth any testing effort.
 
  Groups with no outside users are QofGobject, QofSql, QofSerialize, and
  QofDeserialize. Those with very few and which I haven't looked at in
  detail are QofReference (1), QofChoice (6), and Md5.

 All those latter ones are probably strong candidates to be removed (and
 QofLog
 replaced by pure g_log usage). Maybe I'll just start removing those where
 it
 can easily be confirmed that no-one uses them inside gnucash. But that's
 surely not Muslim's task here.

 Regards,

 Christian


Saluti,

M.Chochlov
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GSOC] Data model unit testing

[John Ralls]

On Apr 6, 2011, at 3:00 PM, Muslim Chochlov wrote:

 
 Then if it is ok with you, I'll consider covering the entities above with 
 unit tests as a final goal. There is almost three times less branching in 
 them, than in the whole libqof module (~1200) so I'll be able to dedicate 3 
 times more effort to test each case (2tests/hour).  And I guess that would be 
 more than realistic approach :)
 If you confirm I'll make final tweaks to my proposal today or tomorrow and 
 hope for the best :)


Muslim,

That looks like a good goal; quite a bit more realistic.

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel