Pending latest changes from Widehopf: Dev #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wiedehopf
force-pushed
the
dev
branch
7 times, most recently
from
5b827ae to
e7d8c49
Compare
wiedehopf
force-pushed
the
dev
branch
2 times, most recently
from
30bc0c1 to
6e2434f
Compare
wiedehopf
force-pushed
the
dev
branch
2 times, most recently
from
8c82ea5 to
ae987a9
Compare
client connects, data is sent normally writer caches data but before flushWrites is called the client disconnects writer doesn't clear its cache as flushWrites isn't called if the writer has no connections client connects and is presented with (a bit) of old data fix this by calling flushWrites even if there are no connections returning NULL out of prepareWrite when no connections are present is still a good CPU saving optimization this optimization was unnecessary and emitted old data
this is useful for accidents in which the transponder suddenly stops transmitting it provides high granularity data for by default for 64 data points before end of transmission --devel=traceLast,128 would double this to 128
this slightly increases CPU usage memory often being limited this seems worth it also hopefully not a huge increase in CPU usage
this shouldn't be needed by anyone really
this improves compatibility and reduces latency a tiny bit if there is any rtl-sdr issues with this (not that i expect it), the default might be changed back for rtl-sdr at least
filter planes without position as well when a negative distance is specified
reported-by: Stanislav Fort (Aisle Research)
reported-by: Stanislav Fort (Aisle Research)
reported-by: Stanislav Fort (Aisle Research)
reported-by: Stanislav Fort (Aisle Research)
reported-by: Stanislav Fort (Aisle Research)
this fixes disconnects with encapsulated UAT uplink messages which are quite long
was off by one so UAT messages would sit in the read buffer without being decoded until a successive unrelated message arrived
The return 0 statement was incorrectly placed inside the valid pressure range check (0-2048), causing the function to exit early and lose the accumulated score. Moved the return to the else block where it belongs, so the score is properly incremented when static pressure is valid.
fitipower tuners don't receive 1090 well, warn the user about it and put it in jsons so webinterfaces can also warn about it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.