Releases: fgcz/bfabricPy
Releases · fgcz/bfabricPy
app_runner/0.0.9
Added
- App specs can now define multiple versions in one file. (AppSpec = Collection of app versions and other information.)
- To avoid boilerplate, mako templates can be used inside of strings.
- Apps will resolve the version to use based on the
application_version
field. - Validation functionality for the new app specification has been added.
- App versions can define a submitter, however this information is not yet used.
1.13.14
app_runner/0.0.8
Added
- Register single file command:
bfabric-app-runner outputs register-single-file
- Implement copy resource
UpdateExisting.IF_EXISTS
andUpdateExisting.REQUIRED
support. - The following fields have been added to
WorkunitRegistrationDefinition
:storage_id
storage_output_folder
application_id
application_name
Changed
- App-runner code related to output staging accepts workunit-definition file like the other steps.
1.13.13
Changed
- Move
bfabric-cli read
tobfabric-cli api read
. - (internal)
use_client
decorator is introduced to simplify and standardize the client usage in the new CLI code.
Added
- Functionality to log by specifying the workunit instead of external job, which is used in some legacy scripts.
- Add logging commands to
bfabric-cli api log
. - Add
bfabric-cli api save
. - Submitter script prints the id and hostname of apps, which in practice can be very useful.
Fixed
- A bug in bfabric_save_workflowstep.py that crashed the script.
1.13.12
Changed
- The submitter ensures that workunits always get set to
processing
.
Fixed
- The script
bfabric_setResourceStatus_available.py
and other uses ofreport_resource
, correctly search files which
have a relative path starting with/
as in the case of the legacy wrapper creator.
1.13.11
Fixed
- The script
bfabric_setWorkunitStatus.py
did always set the status toavailable
, instead of the specified status.
Changed
bfabric_setResourceStatus_available.py
calls thereport_resource
function, in general this functionality has been refactored.
1.13.10
Fixed
- If
bfabricpy.yml
contains a root-level key which is not a dictionary, a correct error message is shown instead of raising an exception. - A bug introduced while refactoring in
slurm.py
which passedPath
objects tosubprocess
instead of strings. - Submitter
- does not use unset
JOB_ID
environment variable anymore. - does not set unused
STAMP
environment variable anymore.
- does not use unset
- Fix
bfabric_save_workflowstep.py
bugs from refactoring.
Added
- Experimental bfabric-cli interface. Please do not use it in production yet as it will need a lot of refinement.
1.13.9
From this release onwards, the experimental app runner is not part of the main bfabric package and
instead a separate Python package with its individual changelog.
Added
- Relationship:
ExternalJob.executable
- (experimental) EntityLookupCache that allows to cache entity lookups in a script to avoid redundant requests.
- Specific use case script: bfabric_save_resource_description.py (the functionality will be available in a future CLI).
Fixed
Entity.find_all
returns no values when an empty list is passed as an argument.
Changed
- Except for macOS x86_64 (which we assume is Rosetta emulation nowadays), we use the faster
polars
instead ofpolars-lts-cpu
. BfabricRequestError
is now aRuntimeError
subclass.- Add
py.typed
marker.
Removed
bfabric_legacy.py
has been removed.math_helper.py
has been removed.
app_runner/0.0.7
Fixed
- When executing
app run
the experimental entity cache created incorrect behavior. The caching is temporarily disabled,
until the issue is resolved.
app_runner/0.0.6
add test for app spec as well