Skip to content

Client log does not store info about exceptions during download/pull/push #156

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

Closed
wonder-sk opened this issue Jan 6, 2023 · 0 comments · Fixed by #182
Closed

Client log does not store info about exceptions during download/pull/push #156

wonder-sk opened this issue Jan 6, 2023 · 0 comments · Fixed by #182
Assignees
Labels
bug Something isn't working

Comments

@wonder-sk
Copy link
Contributor

Currently if there is an unhandled exception while e.g. downloading, it is not added to the log - this makes logs less useful...

To simulate, one can add an invalid statement to download_blocking() function.

@wonder-sk wonder-sk added the bug Something isn't working label Jan 6, 2023
@wonder-sk wonder-sk assigned JanCaha and alexbruy and unassigned JanCaha Oct 10, 2023
wonder-sk pushed a commit that referenced this issue Oct 30, 2023
* copy log file to the temp dir before removing project directory if
download fails

* address review

* codestyle

* add active waiting test

* log errors when project download fails (refs #156)

* write traceback to the log
check that traceback present in the log in test

* formatting

* address review
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants