Re: USAA Direct Connect is Broken Again
I was away so I could not look at this until now.
All of my systems were on versions I compiled before Dec 26 and after the
previous changes earlier in December. USAA import was working. As a
reminder, USAA imports failed on all 3 Fedora 35 systems when KMM was
compiled after Dec 26. On at least one of the systems KMM had been compiled
twice after Dec 26.
This morning all 3 systems were switched back to the post Dec 26 versions
that previously failed to import from USAA. They all were able to import
from USAA. When I compiled new versions from the 5.1 branch today, USAA
direct connect works fine.
I do not think this was a USAA problem because I think it was still failing
on systems with the post Dec 26 version after it was working on systems
that had been rolled back. {lus it seems unlikely that they fixed it in the
30 minutes it took to roll back the version.
It may be a library update on Fedora 35 but that seems like it would be
hard to explain over 3 systems.
I use a build script and an install script that I wrote for KMM. Each time
I build I download the full tree from the target branch and name it with a
date and time stamp. I usually keep the build tree directory arund for a
month or two so I can switch back if necessary.
My install script basically runs make uninstall for the appropriate build
directory and then switches to the target build directory and runs make
install (both with the appropriate arguments).
One thing I did observe when switching from the post Dec 26 version back to
the older version, it took quite a while. It almost looked like the build
script was running again. When I switched back to the post Dec 26 version
this morning, it was much faster and looked like a normal install process
after a new build. This was the same on all 3 systems. I suspect something
on the Fedora systems changed to trigger this but I don't understand the
process enough to explain it.
Not sure why this happened or why it went away but it works now so I'm
happy.
**
*Brendan Coupe*
On Mon, Jan 3, 2022 at 11:50 PM Thomas Baumgart wrote:
> Hi Brendan,
>
> no, no changes at all on our side since Dec 26th.
> See https://invent.kde.org/office/kmymoney/-/commits/5.1
>
> Strange, maybe USAA DC changed something on their side :)
>
> Thomas
>
>
> On Dienstag, 4. Januar 2022 05:35:30 CET you wrote:
>
> > Did you change anything? I recompiled tonight to get the error message
> and
> > USAA Direct Connect is working. This happened on 3 different systems but
> I
> > can only test one until the weekend.
> >
> > **
> > *Brendan Coupe*
> >
> >
> > On Mon, Jan 3, 2022 at 10:47 AM Thomas Baumgart
> wrote:
> >
> > > On Montag, 3. Januar 2022 18:33:14 CET Brendan Coupe wrote:
> > >
> > > > Sorry, wrong terminology. Builds do not fail, the Direct Connect
> problem
> > > > appears in my builds after December 23. I do not have any builds on
> Dec
> > > 24
> > > > & 5.
> > >
> > > The only change that was added in that time frame is
> > >
> > >
> > >
> https://invent.kde.org/office/kmymoney/-/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
> > >
> > > Here's the log from IRC:
> > >
> > > 00:00:00 - {Day changed to Sonntag, 26. Dezember 2021}
> > > 11:11:47 --> pursuivant (pursuivant@user/pursuivant) has joined
> #kmymoney
> > > 11:11:47 office/kmymoney (master) v5.0.8-1673-g19e6a0af6
> *
> > > Thomas Baumgart: kmymoney (5 files in 3 dirs)
> > > 11:11:48 Increased price precision to 20 digits maximum
> > > 11:11:49 BUG: 447480
> > > 11:11:49 FIXED-IN: 5.1.3
> > > 11:11:50
> > >
> https://invent.kde.org/office/kmymoney/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
> > > 11:12:36 office/kmymoney (5.1) v5.1.2-127-g657dbcf2f *
> > > Thomas Baumgart: kmymoney (5 files in 3 dirs)
> > > 11:12:36 Increased price precision to 20 digits maximum
> > > 11:12:37 BUG: 447480
> > > 11:12:38 FIXED-IN: 5.1.3
> > > 11:12:39
> > >
> https://invent.kde.org/office/kmymoney/commit/657dbcf2f17a56dc78951f172f0db35554a2785b
> > > 19:30:32 Hey all, so is it possible to run
> KMyMoney
> > > in debug mode on kdevelop?
> > > 21:48:45 Yes, that's what I use here.
> > > 00:00:00 - {Day changed to Montag, 27. Dezember 2021}
> > >
> > > One of the two commits was on 5.1 and the other one on master. That
> change
> > > only changes the maximum precision that a number can be displayed with
> > > (formatted for output) and I have honestly no idea how that can affect
> the
> > > USAA thingy, especially when the changed method is not even referenced
> in
> > > all of the ofx plugin code. I see some references though, but they are
> all
> > > commented and not compiled.
> > >
> > > > The error was about username and/or password error.
> > > >
> > > > To be clear, this is the change you made some time last year based on
> > > some
> > > > work GNUCash had done to get KMM to work on USAA again. I think you
> added
> > > > User Agent and maybe some other tricks. I thought you made this for
> USAA
> > > > accounts only, at
Re: USAA Direct Connect is Broken Again
Hi Brendan,
no, no changes at all on our side since Dec 26th.
See https://invent.kde.org/office/kmymoney/-/commits/5.1
Strange, maybe USAA DC changed something on their side :)
Thomas
On Dienstag, 4. Januar 2022 05:35:30 CET you wrote:
> Did you change anything? I recompiled tonight to get the error message and
> USAA Direct Connect is working. This happened on 3 different systems but I
> can only test one until the weekend.
>
> **
> *Brendan Coupe*
>
>
> On Mon, Jan 3, 2022 at 10:47 AM Thomas Baumgart wrote:
>
> > On Montag, 3. Januar 2022 18:33:14 CET Brendan Coupe wrote:
> >
> > > Sorry, wrong terminology. Builds do not fail, the Direct Connect problem
> > > appears in my builds after December 23. I do not have any builds on Dec
> > 24
> > > & 5.
> >
> > The only change that was added in that time frame is
> >
> >
> > https://invent.kde.org/office/kmymoney/-/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
> >
> > Here's the log from IRC:
> >
> > 00:00:00 - {Day changed to Sonntag, 26. Dezember 2021}
> > 11:11:47 --> pursuivant (pursuivant@user/pursuivant) has joined #kmymoney
> > 11:11:47 office/kmymoney (master) v5.0.8-1673-g19e6a0af6 *
> > Thomas Baumgart: kmymoney (5 files in 3 dirs)
> > 11:11:48 Increased price precision to 20 digits maximum
> > 11:11:49 BUG: 447480
> > 11:11:49 FIXED-IN: 5.1.3
> > 11:11:50
> > https://invent.kde.org/office/kmymoney/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
> > 11:12:36 office/kmymoney (5.1) v5.1.2-127-g657dbcf2f *
> > Thomas Baumgart: kmymoney (5 files in 3 dirs)
> > 11:12:36 Increased price precision to 20 digits maximum
> > 11:12:37 BUG: 447480
> > 11:12:38 FIXED-IN: 5.1.3
> > 11:12:39
> > https://invent.kde.org/office/kmymoney/commit/657dbcf2f17a56dc78951f172f0db35554a2785b
> > 19:30:32 Hey all, so is it possible to run KMyMoney
> > in debug mode on kdevelop?
> > 21:48:45 Yes, that's what I use here.
> > 00:00:00 - {Day changed to Montag, 27. Dezember 2021}
> >
> > One of the two commits was on 5.1 and the other one on master. That change
> > only changes the maximum precision that a number can be displayed with
> > (formatted for output) and I have honestly no idea how that can affect the
> > USAA thingy, especially when the changed method is not even referenced in
> > all of the ofx plugin code. I see some references though, but they are all
> > commented and not compiled.
> >
> > > The error was about username and/or password error.
> > >
> > > To be clear, this is the change you made some time last year based on
> > some
> > > work GNUCash had done to get KMM to work on USAA again. I think you added
> > > User Agent and maybe some other tricks. I thought you made this for USAA
> > > accounts only, at least for now.
> > >
> > > It's setable in my USAA accounts (set to InetClntApp/3.0) and grayed out
> > on
> > > my other accounts.
> >
> > Yes, I remember, but how exactly does the failure show up? Did you
> > re-compile and install the plugins as well?
> >
> >
> > --
> >
> > Regards
> >
> > Thomas Baumgart
> >
> > https://www.signal.org/ Signal, the better WhatsApp
> > -
> > Intelligence is the ability to avoid doing
> > work, yet getting the work done.
> > -
> >
>
--
Regards
Thomas Baumgart
https://www.signal.org/ Signal, the better WhatsApp
-
There are only 10 types of people in the world: those who
understand binary arithmetic and those who don't.
-
signature.asc
Description: This is a digitally signed message part.
Re: USAA Direct Connect is Broken Again
Did you change anything? I recompiled tonight to get the error message and
USAA Direct Connect is working. This happened on 3 different systems but I
can only test one until the weekend.
**
*Brendan Coupe*
On Mon, Jan 3, 2022 at 10:47 AM Thomas Baumgart wrote:
> On Montag, 3. Januar 2022 18:33:14 CET Brendan Coupe wrote:
>
> > Sorry, wrong terminology. Builds do not fail, the Direct Connect problem
> > appears in my builds after December 23. I do not have any builds on Dec
> 24
> > & 5.
>
> The only change that was added in that time frame is
>
>
> https://invent.kde.org/office/kmymoney/-/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
>
> Here's the log from IRC:
>
> 00:00:00 - {Day changed to Sonntag, 26. Dezember 2021}
> 11:11:47 --> pursuivant (pursuivant@user/pursuivant) has joined #kmymoney
> 11:11:47 office/kmymoney (master) v5.0.8-1673-g19e6a0af6 *
> Thomas Baumgart: kmymoney (5 files in 3 dirs)
> 11:11:48 Increased price precision to 20 digits maximum
> 11:11:49 BUG: 447480
> 11:11:49 FIXED-IN: 5.1.3
> 11:11:50
> https://invent.kde.org/office/kmymoney/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
> 11:12:36 office/kmymoney (5.1) v5.1.2-127-g657dbcf2f *
> Thomas Baumgart: kmymoney (5 files in 3 dirs)
> 11:12:36 Increased price precision to 20 digits maximum
> 11:12:37 BUG: 447480
> 11:12:38 FIXED-IN: 5.1.3
> 11:12:39
> https://invent.kde.org/office/kmymoney/commit/657dbcf2f17a56dc78951f172f0db35554a2785b
> 19:30:32 Hey all, so is it possible to run KMyMoney
> in debug mode on kdevelop?
> 21:48:45 Yes, that's what I use here.
> 00:00:00 - {Day changed to Montag, 27. Dezember 2021}
>
> One of the two commits was on 5.1 and the other one on master. That change
> only changes the maximum precision that a number can be displayed with
> (formatted for output) and I have honestly no idea how that can affect the
> USAA thingy, especially when the changed method is not even referenced in
> all of the ofx plugin code. I see some references though, but they are all
> commented and not compiled.
>
> > The error was about username and/or password error.
> >
> > To be clear, this is the change you made some time last year based on
> some
> > work GNUCash had done to get KMM to work on USAA again. I think you added
> > User Agent and maybe some other tricks. I thought you made this for USAA
> > accounts only, at least for now.
> >
> > It's setable in my USAA accounts (set to InetClntApp/3.0) and grayed out
> on
> > my other accounts.
>
> Yes, I remember, but how exactly does the failure show up? Did you
> re-compile and install the plugins as well?
>
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/ Signal, the better WhatsApp
> -
> Intelligence is the ability to avoid doing
> work, yet getting the work done.
> -
>
Re: USAA Direct Connect is Broken Again
On Montag, 3. Januar 2022 18:33:14 CET Brendan Coupe wrote:
> Sorry, wrong terminology. Builds do not fail, the Direct Connect problem
> appears in my builds after December 23. I do not have any builds on Dec 24
> & 5.
The only change that was added in that time frame is
https://invent.kde.org/office/kmymoney/-/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
Here's the log from IRC:
00:00:00 - {Day changed to Sonntag, 26. Dezember 2021}
11:11:47 --> pursuivant (pursuivant@user/pursuivant) has joined #kmymoney
11:11:47 office/kmymoney (master) v5.0.8-1673-g19e6a0af6 * Thomas
Baumgart: kmymoney (5 files in 3 dirs)
11:11:48 Increased price precision to 20 digits maximum
11:11:49 BUG: 447480
11:11:49 FIXED-IN: 5.1.3
11:11:50
https://invent.kde.org/office/kmymoney/commit/19e6a0af6cccd3c098480b0d0885dc3f036030ab
11:12:36 office/kmymoney (5.1) v5.1.2-127-g657dbcf2f * Thomas
Baumgart: kmymoney (5 files in 3 dirs)
11:12:36 Increased price precision to 20 digits maximum
11:12:37 BUG: 447480
11:12:38 FIXED-IN: 5.1.3
11:12:39
https://invent.kde.org/office/kmymoney/commit/657dbcf2f17a56dc78951f172f0db35554a2785b
19:30:32 Hey all, so is it possible to run KMyMoney in
debug mode on kdevelop?
21:48:45 Yes, that's what I use here.
00:00:00 - {Day changed to Montag, 27. Dezember 2021}
One of the two commits was on 5.1 and the other one on master. That change only
changes the maximum precision that a number can be displayed with (formatted
for output) and I have honestly no idea how that can affect the USAA thingy,
especially when the changed method is not even referenced in all of the ofx
plugin code. I see some references though, but they are all commented and not
compiled.
> The error was about username and/or password error.
>
> To be clear, this is the change you made some time last year based on some
> work GNUCash had done to get KMM to work on USAA again. I think you added
> User Agent and maybe some other tricks. I thought you made this for USAA
> accounts only, at least for now.
>
> It's setable in my USAA accounts (set to InetClntApp/3.0) and grayed out on
> my other accounts.
Yes, I remember, but how exactly does the failure show up? Did you re-compile
and install the plugins as well?
--
Regards
Thomas Baumgart
https://www.signal.org/ Signal, the better WhatsApp
-
Intelligence is the ability to avoid doing
work, yet getting the work done.
-
signature.asc
Description: This is a digitally signed message part.
Re: USAA Direct Connect is Broken Again
Sorry, wrong terminology. Builds do not fail, the Direct Connect problem appears in my builds after December 23. I do not have any builds on Dec 24 & 5. The error was about username and/or password error. To be clear, this is the change you made some time last year based on some work GNUCash had done to get KMM to work on USAA again. I think you added User Agent and maybe some other tricks. I thought you made this for USAA accounts only, at least for now. It's setable in my USAA accounts (set to InetClntApp/3.0) and grayed out on my other accounts. ** *Brendan Coupe* On Mon, Jan 3, 2022 at 10:25 AM Thomas Baumgart via KMyMoney-devel < kmymoney-devel@kde.org> wrote: > Brendan, > > On Montag, 3. Januar 2022 17:26:09 CET Brendan Coupe via KMyMoney-devel > wrote: > > > I just found a version compiled on Dec 23 on my laptop. The problem is > not > > present in that version either. > > OK, so it seems to be the Dec 26th change then that's causing a bit > different > behavior. I tried to find some details on 'Several recent builds have > failed' > but did not see a more detail explanation as to what fails. If a build > fails, > that usually means, the program does not build. If it is anything else that > is not working, then I would need much more details about the problem > itself > because I still don't understand it. > > Thanks in advance. Very much appreciate your QA work there. > > Thomas > > -- > > Regards > > Thomas Baumgart > > https://www.signal.org/ Signal, the better WhatsApp > - > Linux - Life is too short for reboots > - >
Re: USAA Direct Connect is Broken Again
Brendan, On Montag, 3. Januar 2022 17:26:09 CET Brendan Coupe via KMyMoney-devel wrote: > I just found a version compiled on Dec 23 on my laptop. The problem is not > present in that version either. OK, so it seems to be the Dec 26th change then that's causing a bit different behavior. I tried to find some details on 'Several recent builds have failed' but did not see a more detail explanation as to what fails. If a build fails, that usually means, the program does not build. If it is anything else that is not working, then I would need much more details about the problem itself because I still don't understand it. Thanks in advance. Very much appreciate your QA work there. Thomas -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Linux - Life is too short for reboots - signature.asc Description: This is a digitally signed message part.
Re: USAA Direct Connect is Broken Again
I just found a version compiled on Dec 23 on my laptop. The problem is not present in that version either. ** *Brendan Coupe* On Mon, Jan 3, 2022 at 9:24 AM Brendan Coupe wrote: > Luckily I compile fairly often and have not deleted some of my recent > builds. > > I am using the 5.1 branch. > > The problem is not present in the version I compiled on Dec 19. I think > this points to the Dec 26 change. > > ** > *Brendan Coupe* > > > On Mon, Jan 3, 2022 at 12:53 AM Thomas Baumgart via KMyMoney-devel < > kmymoney-devel@kde.org> wrote: > >> Brendan et al, >> >> Happy New Year to all of you. These are not good news to start the year >> with, though. >> More below. >> >> On Montag, 3. Januar 2022 02:47:16 CET Brendan Coupe via KMyMoney-devel >> wrote: >> >> > It appears that something has changed recently that has broken the fix >> that >> > Thomas made to get USAA direct connect to work. >> > >> > Several recent builds have failed. I reinstalled a build from 2021.12.07 >> > and it works fine. >> >> The only changes I see in the 5.1 branch since Dec 12th are: >> >> commit 657dbcf2f17a56dc78951f172f0db35554a2785b (origin/5.1, 5.1) >> Author: Thomas Baumgart >> Date: Sun Dec 26 11:12:21 2021 +0100 >> >> Increased price precision to 20 digits maximum >> >> BUG: 447480 >> FIXED-IN: 5.1.3 >> >> (cherry picked from commit 19e6a0af6cccd3c098480b0d0885dc3f036030ab) >> >> commit 2344c2ce4c69f835c5b8ef4ad270eaffd164f8ea >> Author: Thomas Baumgart >> Date: Sat Dec 18 10:34:37 2021 +0100 >> >> Fix calculation of next due date >> >> In case the option "Process this schedule always on the last day of a >> month" is active, the next due date was not calculated correctly in >> all >> cases. >> >> BUG: 447025 >> FIXED-IN: 5.1.3 >> >> commit b247f26c33c94965e3ac836a8bcb797a35747122 >> Author: Thomas Baumgart >> Date: Sat Dec 18 09:45:20 2021 +0100 >> >> Added additional testcases for scheduled transactions >> >> CCBUG: 447025 >> >> commit 9308f3c3345abf6f4f91b0154f0541eb4546b6f4 >> Author: Thomas Baumgart >> Date: Sat Dec 11 17:05:52 2021 +0100 >> >> Prevent crashes in libofx under MS-Windows >> >> >> and of those only the last one is in the area of OFX download and only >> affects builds on Windows. So I am puzzled to what you encounter. Or >> do you work off the master branch (which is not recommended atm). >> >> Can you identify the commit that makes it to fail? (see git-bisect) >> >> Cheers >> >> Thomas >> >> -- >> >> Regards >> >> Thomas Baumgart >> >> https://www.signal.org/ Signal, the better WhatsApp >> - >> Did you know that the browser that runs on all >> mobile phones originated in the KDE projects >> - >> >
Re: USAA Direct Connect is Broken Again
Luckily I compile fairly often and have not deleted some of my recent builds. I am using the 5.1 branch. The problem is not present in the version I compiled on Dec 19. I think this points to the Dec 26 change. ** *Brendan Coupe* On Mon, Jan 3, 2022 at 12:53 AM Thomas Baumgart via KMyMoney-devel < kmymoney-devel@kde.org> wrote: > Brendan et al, > > Happy New Year to all of you. These are not good news to start the year > with, though. > More below. > > On Montag, 3. Januar 2022 02:47:16 CET Brendan Coupe via KMyMoney-devel > wrote: > > > It appears that something has changed recently that has broken the fix > that > > Thomas made to get USAA direct connect to work. > > > > Several recent builds have failed. I reinstalled a build from 2021.12.07 > > and it works fine. > > The only changes I see in the 5.1 branch since Dec 12th are: > > commit 657dbcf2f17a56dc78951f172f0db35554a2785b (origin/5.1, 5.1) > Author: Thomas Baumgart > Date: Sun Dec 26 11:12:21 2021 +0100 > > Increased price precision to 20 digits maximum > > BUG: 447480 > FIXED-IN: 5.1.3 > > (cherry picked from commit 19e6a0af6cccd3c098480b0d0885dc3f036030ab) > > commit 2344c2ce4c69f835c5b8ef4ad270eaffd164f8ea > Author: Thomas Baumgart > Date: Sat Dec 18 10:34:37 2021 +0100 > > Fix calculation of next due date > > In case the option "Process this schedule always on the last day of a > month" is active, the next due date was not calculated correctly in all > cases. > > BUG: 447025 > FIXED-IN: 5.1.3 > > commit b247f26c33c94965e3ac836a8bcb797a35747122 > Author: Thomas Baumgart > Date: Sat Dec 18 09:45:20 2021 +0100 > > Added additional testcases for scheduled transactions > > CCBUG: 447025 > > commit 9308f3c3345abf6f4f91b0154f0541eb4546b6f4 > Author: Thomas Baumgart > Date: Sat Dec 11 17:05:52 2021 +0100 > > Prevent crashes in libofx under MS-Windows > > > and of those only the last one is in the area of OFX download and only > affects builds on Windows. So I am puzzled to what you encounter. Or > do you work off the master branch (which is not recommended atm). > > Can you identify the commit that makes it to fail? (see git-bisect) > > Cheers > > Thomas > > -- > > Regards > > Thomas Baumgart > > https://www.signal.org/ Signal, the better WhatsApp > - > Did you know that the browser that runs on all > mobile phones originated in the KDE projects > - >
Re: USAA Direct Connect is Broken Again
Brendan et al, Happy New Year to all of you. These are not good news to start the year with, though. More below. On Montag, 3. Januar 2022 02:47:16 CET Brendan Coupe via KMyMoney-devel wrote: > It appears that something has changed recently that has broken the fix that > Thomas made to get USAA direct connect to work. > > Several recent builds have failed. I reinstalled a build from 2021.12.07 > and it works fine. The only changes I see in the 5.1 branch since Dec 12th are: commit 657dbcf2f17a56dc78951f172f0db35554a2785b (origin/5.1, 5.1) Author: Thomas Baumgart Date: Sun Dec 26 11:12:21 2021 +0100 Increased price precision to 20 digits maximum BUG: 447480 FIXED-IN: 5.1.3 (cherry picked from commit 19e6a0af6cccd3c098480b0d0885dc3f036030ab) commit 2344c2ce4c69f835c5b8ef4ad270eaffd164f8ea Author: Thomas Baumgart Date: Sat Dec 18 10:34:37 2021 +0100 Fix calculation of next due date In case the option "Process this schedule always on the last day of a month" is active, the next due date was not calculated correctly in all cases. BUG: 447025 FIXED-IN: 5.1.3 commit b247f26c33c94965e3ac836a8bcb797a35747122 Author: Thomas Baumgart Date: Sat Dec 18 09:45:20 2021 +0100 Added additional testcases for scheduled transactions CCBUG: 447025 commit 9308f3c3345abf6f4f91b0154f0541eb4546b6f4 Author: Thomas Baumgart Date: Sat Dec 11 17:05:52 2021 +0100 Prevent crashes in libofx under MS-Windows and of those only the last one is in the area of OFX download and only affects builds on Windows. So I am puzzled to what you encounter. Or do you work off the master branch (which is not recommended atm). Can you identify the commit that makes it to fail? (see git-bisect) Cheers Thomas -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Did you know that the browser that runs on all mobile phones originated in the KDE projects - signature.asc Description: This is a digitally signed message part.
