-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
log_files: add blocking download_file; add erase log file function #1649
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @dayjaby!
@julianoes thanks for the review! One more question: should this erase log files be a "fire and forget"-function, like in native MAVLink...or does it make sense to call get_entries after a short amount of time and check whether they got deleted or not? And provide some feedback with either |
Yer, that's the question. I'm not sure, mostly because the list function takes quite a bit of time. You could add a comment that says "if you want to be sure the log has been deleted, you have to list it again and check". |
…nchronous download_log_file
5b7556f
to
f73c11c
Compare
@dayjaby I've rebased this, fixed it up, and force pushed it. Let's hope it's now mergeable. |
CI failure probably unrelated. |
This PR adds two new functions to the log_files plugin:
Note, that for the erase function, LOG_ERASE is being used. This mavlink message does not prescribe any feedback. To check whether the logs got really deleted, you can verify with get_entries.
Running the example looks like: