This was added to enable a Pixhawk to be used as an RC input for e.g.
SITL. As far as we're aware of that's not really used. However, sending
this can cause issues if multiple Pixhawks are in the same network.
Also, is uses up some of the MAVLink bandwidth.
Therefore, it's probably best to remove that feature for now.
* bump container tags to 2019-10-04
* docker_run: update container name and tag
* generate_microRTPS_bridge.py: force FastRTPSGen to version 1.0 if the result of 'fastrtpsgen -version' command is not a number
* CI: temporarly disable avoidance and safe landing tests
* CI: try to revive tiltrotor test
- matrix in PX4/Firmware (cb369cb6a75cae71035d72a3bacecce3e109f971): c34e8dc98f
- matrix current upstream: 973999a4d3
- Changes: c34e8dc98f...973999a4d3973999a 2019-09-23 Matthias Grob - Fix some template type conversions and style
PR #12681 added a check to the MulticopterLandDetector::_get_maybe_landed_state() method for a valid vehicle_attitude.timstamp value to finish work in PR #9756. It was discovered that the addition of that check leaves it possible to fly in acro mode without a valid attitude and auto-disarm can engage, allowing the multicopter to fall out of the sky.
* adds a work_queue systemcmd that will bring a tree view of all active work queues and work items
* WorkQueues now track attached WorkItems and will shutdown when the last WorkItem is detached
My suggestion is to re-configure stale bot so it just adds the label
stale but does not close the issue/PR.
This enables us to look for outdated issues using the stale label and
close them.
This brings these advantages:
- No more endless re-opening of PRs and issues which is not fun (and I
will eventually give up on).
- Less stalebot comment noise. (Because it is handy to look for all
issues/PRs without any comments to see what is unanswered).
- I'm not listed as "participating" in all the issues/PRs just because
I was just fighting the stalebot.
- Less notifications meaning we can see anything in the noise.