Skip to main content

FarEarth 3.19.2 release notes

Release date: 6 June 2025

New Features​

  • Added TLS and compression support to MQTT communication
  • Added support for pull-through caching of embedded processor container images
  • Full backups now include the Application Runtime JSON configs
  • The Proj field in product IDs can now be set dynamically per product
  • Improved how lazy executor assignment works in generic workflows
  • L0 reports now include better details for temperatures and manifests
  • A global filesystem has been set up for the Gateway (enabling cloud backups)
  • Browse image extents now pull from a dedicated cloud storage endpoint

Bug Fixes​

  • Fixed a problem where local processor app pinning didn't work when using the Diagnostics executor
  • L0 Reports no longer show an empty Temperatures section if the linked metadata files are missing
  • Cleaned up duplicate logback.xml warnings that were appearing on startup
  • You'll now get a clear error if two lazy archives are matched — no more silent breakage
  • Enterprise Hub wizards now correctly respect user limits
  • Fixed Sentinel data download issues from the FarEarth Ancillary Mirror
  • Local processor capabilities now properly show up in the Gateway after installation
  • Executor matching logic was too strict — it now allows different executor instances with varying priorities
  • The maxJobs runtime config is now isolated per config — no more global sharing
  • Failed orders now get properly killed off and cleaned up
  • Old build directories are now cleaned up automatically
  • The OrderCleanupManager no longer picks a random archive for cleanup after order completion
  • Fixed an issue where lazy archive executor assignments were broadcasting data to all archives instead of just the target one
  • Job log download links now correctly point to the right processor
  • Re-deploying the Gateway no longer wipes out previously shared states
  • We now handle tagless images in the container registry (null ID) without crashing things
  • Fixed the case where a single archive step would be forced out if followed by two other archive steps
  • Report generation should no longer time out in low-resource deployments
  • Cleaned up excessive logging caused by DefaultGitSynchronizer when monitoring fetches fail
  • Executor flags no longer get wiped out to false after bumping to the latest API version
  • Fixed incorrect executor revision and build date reporting
  • You can now delete invalid archives without issue
  • Resolved log flooding in the MqttClientManager message client
  • Removed the unused “max processor jobs” column from the processor UI
  • Diagnostic executor's L1C parameter archiving no longer overwrites published assets, even with versioning enabled

Support​

  • Archive failure messages have been reworded to be clearer and more useful
  • Subscription deletion now properly handles dynamic resources
  • Fixed layout and styling problems in the Markdown viewer
  • Added support for running multiple executor versions at the same time in one runtime