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
With reference to #77
When request is rejected by either the server or the client, there should be some form of printout or logging that explains why it has been rejected.
The implementation for this should target main for now, there will be a separate feature request for the develop branch.
main
develop
The text was updated successfully, but these errors were encountered:
Closing with #145 as requests (now handled by the free fleet adapter) will report back the status of replies, and trigger replans when necessary.
Sorry, something went wrong.
No branches or pull requests
Feature request
Description
With reference to #77
When request is rejected by either the server or the client, there should be some form of printout or logging that explains why it has been rejected.
Implementation considerations
The implementation for this should target
main
for now, there will be a separate feature request for thedevelop
branch.Alternatives
Additional information
The text was updated successfully, but these errors were encountered: