search

uniclogs / yamcs

Yamcs-based mission control software for UniClOGS
GNU Affero General Public License v3.0
1 stars 3 forks source link

Bump yamcsVersion from 5.6.0 to 5.7.9 #49

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps yamcsVersion from 5.6.0 to 5.7.9. Updates yamcs-core from 5.6.0 to 5.7.9

Release notes

Sourced from yamcs-core's releases.

Yamcs 5.7.9

  • Added "cascading" feature: one Yamcs downstream server connects as a client to an upstream Yamcs server and receives TM packets, parameters, events and can send commands. It works best when the two servers share the same MDB. One common case in which the upstream server contains a partial command definition (perhaps only the headers) and the command from the downstream server is injected as the data part of that command, is not yet supported (but it will be soon!)
  • Improved the replay capabilities in yamcs-web
  • Various tweaks and fixes

Yamcs 5.7.8

  • 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

... (truncated)

Changelog

Sourced from yamcs-core's changelog.

Version 5.7.9 released 28-Oct-2022

  • Added cascading feature (one Yamcs downstream Yamcs server connecting to an upstream Yamcs server)
  • Improved the replay capabilities in yamcs-web
  • Various tweaks and fixes

Version 5.7.8 released 5-Oct-2022

  • 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

... (truncated)

Commits
  • c654828 Prepare release yamcs-5.7.9
  • 01a2cc8 refactor replays
  • 3f93bb4 Merge pull request #725 from yamcs/dependabot/maven/com.google.protobuf-proto...
  • 71052a6 Merge pull request #734 from fqqb/next
  • caff7fd Merge pull request #733 from yamcs/cascading
  • b016bf1 Fix cascading TM archive gap filling
  • 306bc97 Create ContainerFetcher for cascading TM links, and make small fixes
  • 900e2b5 Regroup cascaded records in separate Command instances
  • b55db17 Add username auth to cascading, add doc, and fix various
  • 3f73908 Log records with warning in cascading TM diff
  • Additional commits viewable in compare view


Updates yamcs-web from 5.6.0 to 5.7.9

Release notes

Sourced from yamcs-web's releases.

Yamcs 5.7.9

  • Added "cascading" feature: one Yamcs downstream server connects as a client to an upstream Yamcs server and receives TM packets, parameters, events and can send commands. It works best when the two servers share the same MDB. One common case in which the upstream server contains a partial command definition (perhaps only the headers) and the command from the downstream server is injected as the data part of that command, is not yet supported (but it will be soon!)
  • Improved the replay capabilities in yamcs-web
  • Various tweaks and fixes

Yamcs 5.7.8

  • 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

... (truncated)

Changelog

Sourced from yamcs-web's changelog.

Version 5.7.9 released 28-Oct-2022

  • Added cascading feature (one Yamcs downstream Yamcs server connecting to an upstream Yamcs server)
  • Improved the replay capabilities in yamcs-web
  • Various tweaks and fixes

Version 5.7.8 released 5-Oct-2022

  • 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

... (truncated)

Commits
  • c654828 Prepare release yamcs-5.7.9
  • 01a2cc8 refactor replays
  • 3f93bb4 Merge pull request #725 from yamcs/dependabot/maven/com.google.protobuf-proto...
  • 71052a6 Merge pull request #734 from fqqb/next
  • caff7fd Merge pull request #733 from yamcs/cascading
  • b016bf1 Fix cascading TM archive gap filling
  • 306bc97 Create ContainerFetcher for cascading TM links, and make small fixes
  • 900e2b5 Regroup cascaded records in separate Command instances
  • b55db17 Add username auth to cascading, add doc, and fix various
  • 3f73908 Log records with warning in cascading TM diff
  • Additional commits viewable in compare view


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

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.