-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chokes on long payees #16
Comments
Can you send me the payee that is a problem? It might be a quoting issue rather than a length issue. Thanks! |
Anonymized to just indicate letters/numbers/other, they're of the form: XXX XXXX XX 000000 XXXXXXXXXX:XXXXXXXX, XXX. XX/000000000000 XXXXXX XXXXXXX, XXXX XXXX 0 XXX XXXX XXXXX, 00XX XXXXX XXX XXXX XX 000000000 XXXXXXXX, X.X. XXX:000000000 XXXXXXXXXXX:XXXXXXXX XXXXXX XX/0000000000 000 XXXXX XXX XX X XXXXXXXXXX XX 000000000 |
Correction; I'd just grabbed a similar payee, but it seems like they're not all exactly identical. One grabbed directly from the error message is: XXX XXXX XX 000000 XXXXXXXXXX:XXXXXXXX, XXX. XXXXXXXXX XXXXXX XX/000000000000 XXXXXX XXXXXXX, XXXX XXX 0 XXX XXXX XXXXX, XXXXX 00 XXX XXXX XX 000000000 XXXXXXXX, X.X. XXX:000000000 XXXXXXXXXXX:XXXXXXXX XXXXXX XX/0000000000 000 XXXXX XXX XX X XXXXXXXXXX XX 000000000 |
(That includes the escaping of the slashes, incidentally, since it's from the error message. The original payee doesn't have those." |
Thanks for this! Should be fixed now (in master, not yet released). |
I originally came to file this more urgently as it appeared that it was causing the program to immediately stop and only whatever partial output had been flushed at that point survived, but as I was doing a final repro on this I found myself unable to reproduce that part of it. Hmm. If I see that again, I'll let you know, but for now this seems to be simply a logged error that's not blocking functionality.
The text was updated successfully, but these errors were encountered: