~thopiekar/mavlink/+git/MAVSDK:manual-example

Last commit made on 2022-08-16
Get this branch:
git clone -b manual-example https://git.launchpad.net/~thopiekar/mavlink/+git/MAVSDK

Branch merges

Branch information

Name:
manual-example
Repository:
lp:~thopiekar/mavlink/+git/MAVSDK

Recent commits

f856a9a... by Julian Oes

manual_control: ignore health

60b742c... by Julian Oes

manual_control: set manual, only arm when needed

561de26... by Julian Oes

manual_control: reduced example

8b974d8... by Julian Oes

Merge pull request #1865 from mavlink/v1.4-rtk-missing

mavsdk_server: add missing Rtk plugin

9f9dbe0... by Julian Oes

mavsdk_server: add missing Rtk plugin

This had been forgotten earlier.

2d2d85c... by Julian Oes

rtk: fix multi part data being sent

Instead of always sending the first part we should actually send the
remaining data as well, duh.

b1b0d69... by Julian Oes

core: fix another double promise

The problem is that the function called when a timeout happens, always
calls the _all_params_callback which it should not. In fact, there
should be two different timeout handlers instead.

5fbd395... by Julian Oes

core: keep lock while calling callback

I had introduced unlock calls before calling callbacks in order to
prevent deadlocks. I don't think this is required anymore, as all
callbacks back to the user are now served later from a queue. This does
assume that we don't have any such deadlocks internally though.

bc73a2b... by Julian Oes

params: fix double promise call

This fixes a segfault/abort when using get_all_params(). The issue was
that the timeout handler was not removed as it should have been, and so
after a successful completion, we got another call from the timeout
handler which then satisfies the promise a second time which is not
possible.

This did not show up in the integration test (or at least not often)
because the test was already destructed by the time the timeout would
trigger.

14918d7... by Julian Oes

telemetry: fix scope of subscription lock

It looks like the lock was released too early, so before the
_rc_status_subscription and _health_all_ok_subscription were used.

This presumably lead to a address sanitizer failure in CI.