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
void MavlinkCommandSender::queue_command_async( const CommandLong& command, const CommandResultCallback& callback) { if (_command_debugging) { LogDebug() << "COMMAND_LONG " << (int)(command.command) << " to send to " << (int)(command.target_system_id) << ", " << (int)(command.target_component_id); } CommandIdentification identification = identification_from_command(command); for (const auto& work : _work_queue) { if (work->identification == identification && callback == nullptr) { if (_command_debugging) { LogDebug() << "Dropping command " << static_cast<int>(identification.command) << " that is already being sent"; } return; } } // ... }
Access to _work_queue without locking the mutex
_work_queue
The text was updated successfully, but these errors were encountered:
Hmm 🤔, that doesn't look right indeed. Do you want to make a pull request to fix it?
Sorry, something went wrong.
Given the system_tests segfaults, I wanted to try this out immediately and did the PR, sorry.
Thank you :)
Successfully merging a pull request may close this issue.
Access to
_work_queue
without locking the mutexThe text was updated successfully, but these errors were encountered: