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.6 #43

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

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

Release notes

Sourced from yamcs-core's releases.

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.
  • Fixed a memory leak in relation to rocksdb snapshots (snapshots taken during parameter archive buildup were never released) and iterators (iterators were not closed when the replay was stopped before reaching the end)
  • Various tweaks and fixes

Yamcs 5.6.2

  • Added support for Java 17 by using Nashorn javascript engine as a module
  • Removed support for Java 1.8 - 19
  • Various tweaks and fixes

Yamcs 5.6.1

  • Replication: detect and recover dead replication links
  • Replication: allow to synchronize the mission time across replication

... (truncated)

Changelog

Sourced from yamcs-core's changelog.

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) 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.
  • Various tweaks and fixes

Version 5.6.2 released 11-Apr-2022

  • Added support for Java 17 by using Nashorn javascript engine as a module
  • Removed support for Java 1.8 - 19
  • Various tweaks and fixes

Version 5.6.1 released 4-Apr-2022

  • Replication: detect and recover dead replication links

... (truncated)

Commits
  • 5e888e6 Prepare release yamcs-5.7.6
  • 3b59618 allow algorithms to specify their inputs
  • 0968ebc Merge branch 'ws-low-prio'
  • 460ac29 Bump default high watermark from 64KB to 128KB
  • 46447c0 Display one-time warning upon message loss of a lowPriority call #691
  • 8948cbf Use lowPriority option for parameter/stream subscriptions
  • 6166fd2 Merge pull request #696 from fqqb/next
  • 29b73c1 Merge pull request #674 from yamcs/dependabot/maven/io.netty-netty-codec-http...
  • 78933e6 Moved message encoding to netty thread
  • 92d198b name the unamed thread
  • Additional commits viewable in compare view


Updates yamcs-web from 5.6.0 to 5.7.6

Release notes

Sourced from yamcs-web's releases.

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.
  • Fixed a memory leak in relation to rocksdb snapshots (snapshots taken during parameter archive buildup were never released) and iterators (iterators were not closed when the replay was stopped before reaching the end)
  • Various tweaks and fixes

Yamcs 5.6.2

  • Added support for Java 17 by using Nashorn javascript engine as a module
  • Removed support for Java 1.8 - 19
  • Various tweaks and fixes

Yamcs 5.6.1

  • Replication: detect and recover dead replication links
  • Replication: allow to synchronize the mission time across replication

... (truncated)

Changelog

Sourced from yamcs-web's changelog.

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) 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.
  • Various tweaks and fixes

Version 5.6.2 released 11-Apr-2022

  • Added support for Java 17 by using Nashorn javascript engine as a module
  • Removed support for Java 1.8 - 19
  • Various tweaks and fixes

Version 5.6.1 released 4-Apr-2022

  • Replication: detect and recover dead replication links

... (truncated)

Commits
  • 5e888e6 Prepare release yamcs-5.7.6
  • 3b59618 allow algorithms to specify their inputs
  • 0968ebc Merge branch 'ws-low-prio'
  • 460ac29 Bump default high watermark from 64KB to 128KB
  • 46447c0 Display one-time warning upon message loss of a lowPriority call #691
  • 8948cbf Use lowPriority option for parameter/stream subscriptions
  • 6166fd2 Merge pull request #696 from fqqb/next
  • 29b73c1 Merge pull request #674 from yamcs/dependabot/maven/io.netty-netty-codec-http...
  • 78933e6 Moved message encoding to netty thread
  • 92d198b name the unamed thread
  • 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)
dmitri-mcguckin commented 2 years ago

Supplanted by candidate PR #44.

dependabot[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

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