forked from yamcs/yamcs
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
v5.9.7-Pixxel.SNAPSHOT-2.8.0 #87
Merged
Conversation
This file contains 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
Fix empty transferOptions in file transfer web UI
…mic-value String data encoding dynamic value
In case the direction of the file transfer is not set (likely due to a bug) the web app would not work either due to the NPE thrown when converting the string to TransferDirection enum. With this fix, null is returned instead. Fixes yamcs#847
introduced NEGATIVE_INFINITY/POSITIVE_INFINITY time values to be used in open time intervals. Unlike the MIN and MAX these are encoded to -inf/+inf as strings.
Otherwise the lookup can be ambiguous
When reconstructing the aggregate/arrays, skip over rows that do not have values for any member of the aggregate/array. This may happen since we have the sparse parameter archive.
The description can be specified with an annotation in the aggregate type definition: { uint16_def42 member1; @description(”a description for member 2”) float32_def314 member2; }
Remove unused import statements and fix spelling error in log message
CFDP operations are all from one thread with one exception: the getReceivedSize which is called via the API. That means the method can be called when an incoming segmnet is being added to the list causing ConcurrentModificationException. Fixes yamcs#895
The rebuild was not starting from the good position (was assuming that the index records are the first one in the database). The result is that the rebuild may have removed the first header record or not remove all the records. In the new version when a rebuild of the whole index is requested, remove the whole index instead of removing records apid by apid. This should correct errors caused by the previous rebuild. Also removed some unused methods.
Removed the updated link event. The update handler was one of the things keeping the link manager to be garbage collected when an instance was stopped
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.