Fix for CFDP service configured with enableAtStartup: false. Before the fix, the service was still processing incoming PDUs.
Yamcs 5.7.7
some fixes in the CFDP implementation:
when the FIN ACK is lost: the sender will keep sending FIN ACK for each FIN packet received (even if the transaction from the sender point of view is completed)
when the receiver is dead (or it does not acknowledge the EOF case). In that case Yamcs wanted to cancel the transaction but it got stuck
when the service is stopped, do not process incoming packets
add support for (variable length) array command arguments (only one-dimensional arrays supported for now)
various tweaks and fixes
Yamcs 5.7.6
added a low priority option when subscribing via websocket. This allows the yamcs-web to keep connected if there is high incoming data rate, at the expense of some of the messages not displayed.
bug fix parameter archive retrieval end conditions (sometimes it would send data that was past the stop time of the request)
allow java algorithms to specify their input list (if for any reason is not available in the xtce definition)
yamcs-web: Persist command stack options
Various tweaks and fixes
Yamcs 5.7.5
CFDP fixes
the pendingAfterCompletion parameter can be specified. previously it was not accepted in the configuration file.
fixed the number of pending downloads used to compare with the maxNumberDownloads parameter. Previously it would count also the already finished downloads and also the uploads.
Yamcs 5.7.4
added an option to the /api/stream-archive/{instance}:streamParameterValues (which extracts parameters using replays) to filter the packets based on the tm links
on which they have been originally received.
For example typically a different link is used to receive dump (recorded on-board) packets; This option can be used to extract parameters only from those. Or could be used to retrieve only from the realtime packets skipping the dump.
Yamcs 5.7.3
CCSDS TM/TC randomizer: fixed the interpretation of offset/length arguments (may affect custom encoders which want to randomize/derandomize only parts of the frames).
Allow custom (Java) algorithms to provide the list of output parameters at runtime (rather than in the MDB definition) such that those algorithms are not skipped at replay time if no output parameter has been declared in the MDB.
MDB: added internal support for ToString allowing to define how to display the values of parameters (will be implemented in the future in yamcs-web and Yamcs Studio)
yamcs-web:
Show favicon badge when there is an alarm
Add group action for queues
Show process tree on system page
Add Command detail page
Yamcs 5.7.2
yamcs-web: fix render issue with enumerated and command aggregate arguments
Yamcs 5.7.1
Allow 200 aliases in the yaml configuration files (the default was 50). The number can be configured via the java property org.yamcs.yaml.maxAliases
yamcs-web: Show detail field on links page
yamcs-client: fix generation of command source for command with binary arguments
fixed units in the data links synthesized parameters (e.g. /yamcs//tm_realtime/packetRate)
Yamcs 5.7.0
Renamed several java packages to avoid having the same package in different jars (this practice has been discouraged since the introduction of java modules)
The "org.yamcs.xtceproc" and "org.yamcs.xtce" in yamcs-core has bene renamed to "org.yamcs.mdb". May require update of custom plugins if they use classes from those packages.
Fix for a case when CFDP service was configured with enableAtStartup: false. Before the fix, the service was still processing incoming PDUs.
Version 5.7.7 released 3-Oct-2022
some fixes in the CFDP implementation:
when the FIN ACK is lost: the sender will keep sending FIN ACK for each FIN packet received (even if the transaction from the sender point of view is completed)
when the receiver is dead (or it does not acknowledge the EOF case). In that case Yamcs wanted to cancel the transaction but it got stuck
when the service is stopped, do not process incoming packets
add support for (variable length) array command arguments (only one-dimensional arrays supported for now)
various tweaks and fixes
Version 5.7.6 released 27-Jul-2022
added a low priority option when subscribing via websocket. This allows the yamcs-web to keep connected if there is high incoming data rate, at the expense of some of the messages not displayed.
bug fix parameter archive retrieval end conditions (sometimes it would send data that was past the stop time of the request)
allow java algorithms to specify their input list (if for any reason is not available in the xtce definition)
Version 5.7.5 released 24-Jul-2022
CFDP fixes
the pendingAfterCompletion parameter can be specified now
when starting a new download the number of pending downloads excludes the ones just finished and also the uploads. The number is used to compare with the maxNumberDownloads parameter - if the maximum would be exceeded a new download transfer would not be initiated and the respective PDU dropped
Version 5.7.4 released 15-Jun-2022
added an option to the /api/stream-archive/{instance}:streamParameterValues (which extracts parameters using replays) to filter the packets based on the tm links
on which they have been originally received.
For example typically a different link is used to receive dump (recorded on-board) packets; This option can be used to extract parameters only from those. Or could be used to retrieve only from the realtime packets skipping the dump.
Version 5.7.3 released 9-Jun-2022
CCSDS TM/TC randomizer: fixed the interpretation of offset/length parameters (may affect custom encoders which want to randomize/derandomzie only parts of the frames).
Allow custom (Java) algorithms to provide the list of output parameters at runtime (rather than in the MDB definition) such that the algorithms are not skipped at replay time if no output parameter has been declared in the MDB def.
MDB: added internal support for ToString allowing to define how to display the values of parameters (will be implemented in the future in yamcs-web and Yamcs Studio)
yamcs-web:
Show favicon badge when there is an alarm
Add group action for queues
Show process tree on system page
Add Command detail page
)
Version 5.7.2 released 3-Jun-2022
yamcs-web: fix render issue with enumerated and command aggregate arguments
Version 5.7.1 released 30-May-2022
Allow 200 aliaes in the yaml files (used to be 50). The number can be configured via the java property org.yamcs.yaml.maxAliases
yamcs-web: Show detail field on links page
yamcs-client: fix generation of command source for command with binary arguments
fixed units in the data links synthesized parameters (e.g. /yamcs//tm_realtime/packetRate)
Version 5.7.0 relased 27-May-2022
implemented backend support for raw TCs (telecommands which are not generated from the mission database) and bypassing the postprocessor.
Renamed several java packages to avoid having the same package in different jars (this practice has been discouraged since the introduction of java modules)
Fix for CFDP service configured with enableAtStartup: false. Before the fix, the service was still processing incoming PDUs.
Yamcs 5.7.7
some fixes in the CFDP implementation:
when the FIN ACK is lost: the sender will keep sending FIN ACK for each FIN packet received (even if the transaction from the sender point of view is completed)
when the receiver is dead (or it does not acknowledge the EOF case). In that case Yamcs wanted to cancel the transaction but it got stuck
when the service is stopped, do not process incoming packets
add support for (variable length) array command arguments (only one-dimensional arrays supported for now)
various tweaks and fixes
Yamcs 5.7.6
added a low priority option when subscribing via websocket. This allows the yamcs-web to keep connected if there is high incoming data rate, at the expense of some of the messages not displayed.
bug fix parameter archive retrieval end conditions (sometimes it would send data that was past the stop time of the request)
allow java algorithms to specify their input list (if for any reason is not available in the xtce definition)
yamcs-web: Persist command stack options
Various tweaks and fixes
Yamcs 5.7.5
CFDP fixes
the pendingAfterCompletion parameter can be specified. previously it was not accepted in the configuration file.
fixed the number of pending downloads used to compare with the maxNumberDownloads parameter. Previously it would count also the already finished downloads and also the uploads.
Yamcs 5.7.4
added an option to the /api/stream-archive/{instance}:streamParameterValues (which extracts parameters using replays) to filter the packets based on the tm links
on which they have been originally received.
For example typically a different link is used to receive dump (recorded on-board) packets; This option can be used to extract parameters only from those. Or could be used to retrieve only from the realtime packets skipping the dump.
Yamcs 5.7.3
CCSDS TM/TC randomizer: fixed the interpretation of offset/length arguments (may affect custom encoders which want to randomize/derandomize only parts of the frames).
Allow custom (Java) algorithms to provide the list of output parameters at runtime (rather than in the MDB definition) such that those algorithms are not skipped at replay time if no output parameter has been declared in the MDB.
MDB: added internal support for ToString allowing to define how to display the values of parameters (will be implemented in the future in yamcs-web and Yamcs Studio)
yamcs-web:
Show favicon badge when there is an alarm
Add group action for queues
Show process tree on system page
Add Command detail page
Yamcs 5.7.2
yamcs-web: fix render issue with enumerated and command aggregate arguments
Yamcs 5.7.1
Allow 200 aliases in the yaml configuration files (the default was 50). The number can be configured via the java property org.yamcs.yaml.maxAliases
yamcs-web: Show detail field on links page
yamcs-client: fix generation of command source for command with binary arguments
fixed units in the data links synthesized parameters (e.g. /yamcs//tm_realtime/packetRate)
Yamcs 5.7.0
Renamed several java packages to avoid having the same package in different jars (this practice has been discouraged since the introduction of java modules)
The "org.yamcs.xtceproc" and "org.yamcs.xtce" in yamcs-core has bene renamed to "org.yamcs.mdb". May require update of custom plugins if they use classes from those packages.
Fix for a case when CFDP service was configured with enableAtStartup: false. Before the fix, the service was still processing incoming PDUs.
Version 5.7.7 released 3-Oct-2022
some fixes in the CFDP implementation:
when the FIN ACK is lost: the sender will keep sending FIN ACK for each FIN packet received (even if the transaction from the sender point of view is completed)
when the receiver is dead (or it does not acknowledge the EOF case). In that case Yamcs wanted to cancel the transaction but it got stuck
when the service is stopped, do not process incoming packets
add support for (variable length) array command arguments (only one-dimensional arrays supported for now)
various tweaks and fixes
Version 5.7.6 released 27-Jul-2022
added a low priority option when subscribing via websocket. This allows the yamcs-web to keep connected if there is high incoming data rate, at the expense of some of the messages not displayed.
bug fix parameter archive retrieval end conditions (sometimes it would send data that was past the stop time of the request)
allow java algorithms to specify their input list (if for any reason is not available in the xtce definition)
Version 5.7.5 released 24-Jul-2022
CFDP fixes
the pendingAfterCompletion parameter can be specified now
when starting a new download the number of pending downloads excludes the ones just finished and also the uploads. The number is used to compare with the maxNumberDownloads parameter - if the maximum would be exceeded a new download transfer would not be initiated and the respective PDU dropped
Version 5.7.4 released 15-Jun-2022
added an option to the /api/stream-archive/{instance}:streamParameterValues (which extracts parameters using replays) to filter the packets based on the tm links
on which they have been originally received.
For example typically a different link is used to receive dump (recorded on-board) packets; This option can be used to extract parameters only from those. Or could be used to retrieve only from the realtime packets skipping the dump.
Version 5.7.3 released 9-Jun-2022
CCSDS TM/TC randomizer: fixed the interpretation of offset/length parameters (may affect custom encoders which want to randomize/derandomzie only parts of the frames).
Allow custom (Java) algorithms to provide the list of output parameters at runtime (rather than in the MDB definition) such that the algorithms are not skipped at replay time if no output parameter has been declared in the MDB def.
MDB: added internal support for ToString allowing to define how to display the values of parameters (will be implemented in the future in yamcs-web and Yamcs Studio)
yamcs-web:
Show favicon badge when there is an alarm
Add group action for queues
Show process tree on system page
Add Command detail page
)
Version 5.7.2 released 3-Jun-2022
yamcs-web: fix render issue with enumerated and command aggregate arguments
Version 5.7.1 released 30-May-2022
Allow 200 aliaes in the yaml files (used to be 50). The number can be configured via the java property org.yamcs.yaml.maxAliases
yamcs-web: Show detail field on links page
yamcs-client: fix generation of command source for command with binary arguments
fixed units in the data links synthesized parameters (e.g. /yamcs//tm_realtime/packetRate)
Version 5.7.0 relased 27-May-2022
implemented backend support for raw TCs (telecommands which are not generated from the mission database) and bypassing the postprocessor.
Renamed several java packages to avoid having the same package in different jars (this practice has been discouraged since the introduction of java modules)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
1 year ago
Bumps
yamcsVersionfrom 5.6.0 to 5.7.8. Updatesyamcs-corefrom 5.6.0 to 5.7.8Release notes
Sourced from yamcs-core's releases.
... (truncated)
Changelog
Sourced from yamcs-core's changelog.
... (truncated)
Commits
9f5145cPrepare release yamcs-5.7.82386fadfix disabledAtStartup cfdp service1469975fail transfers of empty files7825c22Prepare next development iterationaede5c5Prepare release yamcs-5.7.732afa62Merge pull request #724 from loricvdt/segment-rq-fix082a979Merge pull request #721 from loricvdt/cfdp-stop-fixa7528c0Merge pull request #722 from fqqb/next47f8988Define SegmentRequest.toString, fixing #72387d8bb1Fix stack entries with aggregate/array arguments #699Updates
yamcs-webfrom 5.6.0 to 5.7.8Release notes
Sourced from yamcs-web's releases.
... (truncated)
Changelog
Sourced from yamcs-web's changelog.
... (truncated)
Commits
9f5145cPrepare release yamcs-5.7.82386fadfix disabledAtStartup cfdp service1469975fail transfers of empty files7825c22Prepare next development iterationaede5c5Prepare release yamcs-5.7.732afa62Merge pull request #724 from loricvdt/segment-rq-fix082a979Merge pull request #721 from loricvdt/cfdp-stop-fixa7528c0Merge pull request #722 from fqqb/next47f8988Define SegmentRequest.toString, fixing #72387d8bb1Fix stack entries with aggregate/array arguments #699Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)