GnuCash
Contact   Instructions
Bug 797378 - QIF file import fails: Loading gives wrong type argument in position 2
Summary: QIF file import fails: Loading gives wrong type argument in position 2
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Import - QIF (show other bugs)
Version: git-maint
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: import
QA Contact: import
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-28 16:44 EDT by Christian Stimming
Modified: 2019-09-02 16:12 EDT (History)
3 users (show)

See Also:


Attachments
Sample QIF file (85 bytes, application/octet-stream)
2019-08-28 16:44 EDT, Christian Stimming
no flags Details

Description Christian Stimming 2019-08-28 16:44:47 EDT
Created attachment 373373 [details]
Sample QIF file

Upon loading the qif file, with commit a146d2cd5876a295d779b7a14c7627b0b1fbf946 I get the following error - before that one all works fine. Sample file attached.


In ice-9/boot-9.scm:
 160: 11 [catch #t #<catch-closure 55bc1e593760> ...]
In unknown file:
   ?: 10 [apply-smob/1 #<catch-closure 55bc1e593760>]
In c-interface.scm:
  64: 9 [gnc:backtrace-if-exception #<procedure 55bc20430500 at qif-file.scm:867:4 ()>]
  22: 8 [gnc:call-with-error-handling #<procedure 55bc20430500 at qif-file.scm:867:4 ()> ...]
In ice-9/boot-9.scm:
 160: 7 [catch #t #<procedure 55bc2041b7b0 at c-interface.scm:23:6 ()> ...]
In c-interface.scm:
  26: 6 [#<procedure 55bc2041b7b0 at c-interface.scm:23:6 ()>]
In ice-9/boot-9.scm:
 160: 5 [catch cancel #<procedure private-parse ()> ...]
In qif-file.scm:
 841: 4 [private-parse]
 924: 3 [check-and-parse-field #<procedure qif-xtn:split-amounts (self)> ...]
In qif-parse.scm:
 412: 2 [qif-parse:check-number-formats (#f "-9.71") (decimal comma)]
In unknown file:
   ?: 1 [filter #<procedure 55bc2041b540 at qif-parse.scm:382:10 (fmt)> #]
   ?: 0 [regexp-exec #<regexp 55bc1eedb5c0> #f #<undefined> #<undefined>]

ERROR: In procedure regexp-exec: Wrong type argument in position 2 (expecting string): #f
Comment 1 Christian Stimming 2019-09-02 16:12:07 EDT
Obviously fixed in bb4348fce97668af5de08e0a38867437d7e7f81f - thanks a lot!

Note You need to log in before you can comment on or make changes to this bug.