Changelog
Wave v1.17.1
Feature updates and improvements
- Removed server from OpenAPI spec by @munishchouhan in https://github.com/seqeralabs/wave/pull/793
- Added container index support to inspect view by @pditommaso in https://github.com/seqeralabs/wave/pull/792
Full changelog: https://github.com/seqeralabs/wave/compare/v1.17.0...v1.17.1
Seqera Enterprise v24.2.4
Wave v1.17.0
Feature updates and improvements
- Bumped BuildKit to version 0.18.2 by @pditommaso in https://github.com/seqeralabs/wave/pull/787
- Normalized URL in conda package while using them to generate target image by @munishchouhan in https://github.com/seqeralabs/wave/pull/786
- Updated docs by @munishchouhan in https://github.com/seqeralabs/wave/pull/790
- Render html from OpenAPI spec generated by typespec by @munishchouhan in https://github.com/seqeralabs/wave/pull/707
Full changelog: https://github.com/seqeralabs/wave/compare/v1.16.8...v1.17.0
Fusion v2.5.1
Bugfix release to improve stability.
Bug fixes
- Fixed logs removed when
removeLogsis false. - Fixed unique IDs in file fragments.
- Removed exit code on
serveFusion.
How to pin this version
fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.5.1-amd64.json'
}
For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.5.1-arm64.json'.
Seqera Cloud v24.3.0_024e9bb
Breaking changes
- Restore
errorStrategyandmaxRetriesdefault Nextflow config for AWS and GCP launches. Platform will not overwrite existing error strategy coded in the pipeline repository. - If you want to automatically retry on task failures (e.g., from spot reclamations), you will now need to explicitly set
errorStrategyandmaxRetries. - Automatic spot retries in AWS and GCP now require active enablement. Alternatively Nextflow handles the generic failure at the Nextflow level.
You can revert to the default setting used in Nextflow prior to 24.10 with the following configuration options:
aws.batch.maxSpotAttempts = 5
google.batch.maxSpotAttempts = 5
Set task.maxRetries to a non-zero value to restore Platform to prior behaviour.
How do I retry Spot failures while making them visible?
There is no mechanism in Nextflow to specifically report Spot retries. However you can set process.maxRetries = 5 to retry all failures (including Spot reclamations) a specified number of times before failure.
Feature updates and improvements
Studios
- Added data studio API endpoints to the OpenAPI spec.
Permissions and roles
- New organization types added to allow free tier users to monitor their usage and limits.
Workflows
- Restore
errorStrategydefault Nextflow config for AWS and GCP launches. The Nextflow job now correctly terminates after pipeline completion. - The system now automatically terminates Azure jobs after all tasks complete.
Compute environments
- Updated list of EC2 families with NVMe disks available.
Launchpad
- Send only added/updated run parameters when launching a pipeline. This includes all defaults and parameters passed during the launch.
Pipelines
- Improved error messaging when pipeline info can't be fetched indicates whether the issue is due to a missing resource, or failed authentication due to expired credentials.
UI/UX
- New dynamic page title for easy bookmarking.
General
- Upgraded to Angular 17
- Bumped Nextflow launcher to 24.10.3
Bug fixes
Pipelines
- Allow unsetting
schemaNamewhen editing a pipeline. - Take into account the alternative
mainScriptpath.
General
- Use
preferred_usernameas fallback email field for OIDC login. - Drop the last characters in job definition name, if longer than the prescribed limit.
- Prohibited duplicate Git credentials and added tie-break on
lastUpdatedfor existing duplicates. Going forward, the system gives preference to the credentials updated last when multiple candidates exist. Additionally added a duplicate check when creating new credentials, to avoid new duplicate cases.
Compute environments
- Compute environment creation form allows pre- and post-run scripts to be longer than the accepted value of 1024 characters.
Workflows
- Disabled reset selection on data change in workflow list component.
MultiQC v1.27
Seqera Enterprise v24.2.3
Wave v1.16.8
Feature updates and improvements
- Added
TraceContextFilterlogging context propagation by @pditommaso in 396c10c2 - Improved proxy cache configuration by @pditommaso in 163e605f
- Improved logging pattern by @pditommaso in 0ab87164
- Improved request caching logic by @pditommaso in a95153be
- Bumped MN to 4.7.4 by @pditommaso in 4ce2a139
Full changelog: https://github.com/seqeralabs/wave/compare/v1.16.7...v1.16.8
Fusion v2.5.0
Fusion 2.5.0 significantly enhances performance and efficiency in file operations.
Fusion now handles small files more effectively and intelligently manages Nextflow task files by minimizing intermediate file uploads. A key improvement is the selective retention of only essential task output files upon completion, reducing storage overhead. Network optimization has been implemented to decrease bandwidth usage by consolidating upload operations. Additionally, the underlying architecture has undergone substantial refactoring to support the future integration of diverse remote storage solutions, setting the foundation for expanded storage capabilities.
Feature updates and improvements
- Chunked async content management.
- Nextflow-compatible pattern classifier.
- Defined a default exit code on Fusion-IO errors.
- Object API refactoring.
- Bumped golang.org/x/crypto to 0.31.0.
- Bumped golang.org/x/net to 0.33.0.
Bug fixes
- Fixed AsyncStore move issues.
- Fixed log file deletion during spot instance reclamation.
- Fixed transient object persistence.
How to pin this version
fusion {
enabled = true
containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.5.0-amd64.json'
}
For ARM64 CPU architecture, use containerConfigUrl = 'https://fusionfs.seqera.io/releases/v2.5.0-arm64.json'.