Amazon module is failing after reaching 2018 in my order history

[philipsd6]

Amazon module is failing after reaching 2018 in my order history

[jbms]

In interactive mode I usually first call run(), and see where it gets stuck/throws an error. If it gets stuck, you can press Control+C to interrupt. You can use the ipython %debug command to enter the debugger, or you can just look at the stack trace to see where it was. Then I usually manually paste in the relevant snippets of code from the module being executed to see what is being returned. The ipython shell is set up to attempt to autoreload modified source files, so you can also modify the code to try to fix it and re-run the whole thing or just a particular function to see if it worked. However, the autoreload does not always work, and generally only works to modify existing methods, not to add new ones.

Regarding it failing on an old invoice, I'm not seeing that on invoices back to 2012 --- if you can figure out a way to detect or handle that it would be great.

Note that the lastupdate file is only used by the status command, but does not affect which invoices are downloaded --- it attempts to download any invoices not already in the output directory.

[jbms]

Sounds like maybe a change in the website --- I'll have to take a look. In general the way I debug these issues is to run in interactive mode.

[jbms]

I believe this is fixed now.

[philipsd6]

@jbms if you happen to review a closed issue, can you expand a bit somewhere on how you debug these issues in interactive mode? I tried that, and the docs just said call run(), which just does the whole thing, and I didn't have the time/patience to dig into the code to see if I can go step by step to isolate the issue...

[philipsd6]

Also, yes, it's working for me now, although it eventually fails due to an Amazon error on downloading an invoice from waaaaaay in the past. I just touched logs/amazon.lastupdate.