We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since I'm always getting a "BAD_REQUEST" error from the platform when executing dl_docs, I tried to limit the download to the last 5 days by using:
pytr dl_docs --last_days 5 .
This seems to have no effect for me. The download still starts at 01.06., which is where the first document was placed in my account.
EDIT: btw: the BAD_REQUEST seems to stem from the entry to verify your bank-account, so maybe it could be implemented to be skipped at the download
The text was updated successfully, but these errors were encountered:
Is this error still occuring in the latest version?
Sorry, something went wrong.
Confirmed that the last_days parameter indeed works.
last_days
pytr -V 0.1.9
This works for me.
pytr dl_docs --last_days 30 ./
Maybee the documents are not available. I used this also in older versions, so I can not confirm a bug
Maybe there is confusion because the terminal log always shows all the documents (from all time) when pytr is executed.
But only the documents from the timeframe given by --last_days parameter are actually saved to PATH. So I guess it works as intended.
--last_days
PATH
No branches or pull requests
Since I'm always getting a "BAD_REQUEST" error from the platform when executing dl_docs, I tried to limit the download to the last 5 days by using:
pytr dl_docs --last_days 5 .
This seems to have no effect for me. The download still starts at 01.06., which is where the first document was placed in my account.
EDIT: btw: the BAD_REQUEST seems to stem from the entry to verify your bank-account, so maybe it could be implemented to be skipped at the download
The text was updated successfully, but these errors were encountered: