0.27.0

What's Changed

• [feature] Added new S3Location and S3Bucket types that render S3 links in the Dashboard, and
  documented them
• [feature] Added a new Image type that render images in the Dashboard, and documented it
• [example] Added TorchLightning + Resnet + Ray example
• [example] Added Ray AIR example
• [example] Added various enhancements to the example Testing Pipeline
• [improvement] BREAKING CHANGE: image_layers field in sematic_pipeline bazel macro
  now ONLY gets passed to image layering, and not also to the Sematic binary target.
  if you are using image_layers to express dependencies of a pipeline, you will now
  need to duplicate them in the deps field.
• [improvement] Added support for Python 3.10
• [improvement] Added support for Python 3.10-style type hints
• [improvement] The Dashboard login flow will now redirect to the requested page instead of to
  the homepage
• [improvement] Displaying the user who started a Run in the Dashboard Run list page and in the
  Run history drop-down
• [improvement] Various documentation updates and fixes
• [improvement] Various log message improvements and enhancements
• [improvement] Sped up Docker image generation through various improvements
• [improvement] Automatically update npm dependencies when building the wheel
• [improvement] Added deep-linking selected panel stickiness in the Dashboard
• [improvement] Filtered only pipelines launched by the current user in the Dashboard homepage
  last run widget
• [improvement] Documented Ray integration architecture
• [improvement] Improved wheel building portability by defaulting to bash
• [improvement] Improved reaction time of the CloudResolver after a very long-running cloud Run
  has ended
• [improvement] Improved handling of incorrect cleanup of or errors in subprocess spawned by
  user code
• [improvement] Various internal refactorings, cleanups, and build improvements
• [improvement] Switched from MB and GB to GiB and MiB in the Ray configurations, for
  consistency and standardization reasons
• [improvement] Added checks and documentation for the new libmagic dependency
• [improvement] Resolution failures caused by Resolver errors now get marked as failed instead
  of canceled
• [bugfix] Pinned MNIST example pipeline dependencies after a new dependency release broke the
  execution
• [bugfix] Fixed a bug that prevented the browser back/forward buttons from working correctly
  in the Dashboard
• [bugfix] Fixed a bug that sometimes prevented the Dashboard Run tree panel from updating
• [bugfix] Fixed sorting of the Runs in the Dashboard Run tree panel by creation time
• [bugfix] Fixed a race condition where Kubernetes job updates would be incorrectly handled,
  and added safeguards for incorrect Run state transitions
• [bugfix] Fixed a bug where killing a subprocess spawned by user code would prematurely
  terminate the Run, or leave the Resolver in an inconsistent state
• [bugfix] Fixed a race condition that would prevent a fresh deployment on Kubernetes due to
  missing resources
• [bugfix] Fixed a bug in the Dashboard that prevented the log panel error messages from
  refreshing when seeking to a different Run
• [bugfix] Fixed a bug where failure to notify the Dashboard or Resolver with Run updates via
  socketio messages would cause the Resolution to fail

Full Changelog: v0.26.0...v0.27.0

Compatibility

Sematic Servers on this version can support pip packages back to v0.24.1.

0.26.0

What's Changed

• [feature] Added optional anonymized user analytics to track Sematic usage
• [improvement] Atomic database migrations with Helm hooks
• [improvement] Move future pickle storage to new server-generated locations
• [improvement] Refactor in-app links to use react router
• [improvement] Minor UI test improvements with Cypress
• [improvement] Minor documentation fixes for rerun-from-here
• [bugfix] Fix noop SQL migrations

Full Changelog: v0.25.0...v0.26.0

Compatibility

Sematic servers on this version can support pip packages back to v0.24.1

0.25.0

What's Changed

• [feature] New dashboard page showing a searchable list of runs
• [feature] Enable links to runs using only the run id (pipeline path not required)
• [improvement] Expose image layer caching configuration for bazel-built pipelines
• [improvement] Make allocation timeouts for Ray clusters configurable
• [improvement] Small changes to layout of pipeline display page
• [improvement] Have Ray workers use same Kubernetes SA as Sematic workers
• [improvement] Minor user docs improvements
• [bugfix] Fix a bug that was preventing configuration of Slack via helm
• [bugfix] Remove error occurring when a local settings file configures server-only settings
• [bugfix] Be more resilient against non-standard failures during torch imports
• [bugfix] More robust cleanup of Ray clusters on pipeline cancellation

Full Changelog: v0.24.1...v0.25.0

Compatibility

Sematic servers on this version can support pip packages back to v0.22.1

0.24.1

What's Changed

• [improvement] Show more detailed errors on failures of DB migrations
• [bugfix] Reduce wheel size

Full Changelog: v0.24.0...v0.24.1

Compatibility

Sematic servers on this version can support pip packages back to v0.22.1

0.24.0

What's Changed

• [feature] Introduction of RayCluster¹
• [feature] "Tee" cloud function logs so they appear in Sematic dashboard and the pod logs
• [improvement] Visualize better which run was the true "root failure" when a resolution fails
• [improvement] Improve an error message when using untyped dicts in type annotations
• [improvement] Various improvements to Sematic internal test infrastructure
• [bugfix] Remove a possible server crash for local servers running on Macs
• [bugfix] Eliminate a bug that could leave runs hanging if multiple cancellation events were sent
• [bugfix] Fix a bug that removed a useful default for image tag in the Helm chart
• [bugfix] Rename an incorrectly named helm-chart value for Slack integration
• [bugfix] Gracefully terminate runs when a resolver pod restarts mid-resolution

Full Changelog: v0.23.0...v0.24.0

Compatibility

Sematic servers on this version can support pip packages back to v0.22.1

1. This feature is for Sematic's "Enterprise Edition" only. Please reach out if
   you are interested in using Sematic EE. ↩

0.23.0

What's Changed

• [feature] Ability to deploy socket.io micro-service separately.
• [feature] Expose external resources in the dashboard.
• [feature] Slack notification integration for failed resolutions.
• [feature] Support the debug query parameter which can be added to any URL to enforce the front-end application to emit logs.
• [improvement] Minor dependency and CI improvement.
• [improvement] Minor development documentation improvements.
• [bugfix] Fix a bug in the dashboard which prevents successful resolution of status update.

Full Changelog: v0.22.2...v0.23.0

Compatibility

Sematic servers on this version can support pip packages back to version v0.21.1

0.22.2

What's Changed

• [feature] Add the ability to cache the output of a function and avoid its re-execution in the future
• [feature] Add the ability to disable Sematic log ingestion for remote runs
• [feature] Expose cloned run information in the dashboard
• [improvement] Minor logging improvements
• [improvement] Support configuring plugins from the CLI
• [improvement] Add support for Bazel 6.0.0
• [improvement] Add a link in output panel pointing to logs panel in case of error
• [improvement] Improve robustness of data persistence
• [improvement] Minor Helm documentation improvements
• [improvement] Make the header sticky on the run details page
• [improvement] Minor dashboard experience improvement
• [improvement] Internal API endpoints expansion
• [improvement] Support for non-deterministic cached builds in Bazel
• [bugfix] Support override of settings even when no settings file exists
• [bugfix] Minor cross version client support fixes
• [bugfix] Make _getitem importable on graph cloning

Compatibility

Sematic servers on this version can support pip packages back to version v0.21.1

Full Changelog: v0.22.1...v0.22.2

0.22.1

What's Changed

• [feature] Hide some "utility" autogenerated runs in the UI (ex: _getitem)
• [improvement] Added functionality to some server APIs
• [bugfix] To the script to allow auto-upgrading settings files. IMPORTANT: Users should run sematic migrate upon install

Full Changelog: v0.22.0...v0.22.1

Migration

⚠️ Users should run this command after installation in order to migrate their settings files:

$ sematic migrate

Compatibility

The new 0.22.1 Server supports communicating with Clients with version 0.21.1 or later, but it introduces new features which are only available for Clients versions 0.22.0 or later.

0.22.0

What's Changed

• [feature] Expose in the dashboard when a run is cloned from another
• [feature] Allow specifying multiple e-mail domains that can authenticate to Sematic
• [feature] Deep linking for highlighting nested runs in the dashboard
• [feature] Deep linking for tabs in the dashboard
• [feature] Support clicking artifacts in the DAG view to get to their display page
• [feature] Allow configuration for expanded shared memory on cloud workers
• [feature] BREAKING CHANGE: Significant changes to our helm chart. Read our deployment docs for more information.
• [improvement] Improvements to logging UI performance
• [improvement] Give an error message if there are futures that are not used for a function's final output
• [improvement] Avoid warning about SQLite version when SQLite is not in use
• [improvement] User-facing documentation revamp
• [bugfix] Add sematic.testing to python wheel
• [bugfix] Fix a bug with deserializing Tuple objects
• [bugfix] Propagate tags and properties to cloned runs
• [bugfix] Improve the behavior of the logging UI in case of errors
• [bugfix] Better display of Union types in the dashboard
• [bugfix] Add a missing requirement for one of the example pipelines
• [bugfix] Prevent the dashboard from spamming the backend with requests
• [bugfix] Fix corrupted settings files from 0.21.1

Full Changelog: v0.21.1...v0.22.0

Compatibility

The new 0.22.0 Server supports communicating with Clients with version 0.21.1 or later, but it introduces new features which are only available for Clients with the new 0.22.0 version.

0.21.1

What's Changed

• [bugfix] Add back feature allowing configuration of custom API URL to be used by workers

Full Changelog: v0.21.0...v0.21.1