Comments (3)
We have just released version 0.5.5, where these internal data structures have been switched from NamedTuples to dataclasses. We have also added some automated checks through GitHub actions, so we can realize sooner this issues when newer python versions are released.
Could you give it a try, please?
from wfexs-backend.
I did the following:
cd Development/python/workspace/WfExS-backend/
git fetch --all
git status
git diff
git reset --hard
git status
git rebase upstream/main
git status
source venv/bin/activate
pip install -U pip
pip install -U .
Which synced my branch and re-installed the current main
branch. Then running the same command that I used when I reported this issue:
(venv) kinow@ranma:~/Development/python/workspace/WfExS-backend$ python WfExS-backend.py --full-help
usage: WfExS-backend.py [-h] [--log-file LOGFILENAME] [-q] [-v] [-d] [-L LOCALCONFIGFILENAME] [--cache-dir CACHEDIR] [-V] [--full-help]
{init,cache,staged-workdir,export,config-validate,stage,mount-workdir,export-stage,offline-execute,execute,export-results,export-crate} ...
WfExS (workflow execution service) backend 0.5.5-5-g2b1a528 (2b1a528751100c428833d4286586095fe459668c)
optional arguments:
-h, --help show this help message and exit
--log-file LOGFILENAME
Store messages in a file instead of using standard error and standard output (default: None)
-q, --quiet Only show engine warnings and errors (default: None)
-v, --verbose Show verbose (informational) messages (default: None)
-d, --debug Show debug messages (use with care, as it can disclose passphrases and passwords) (default: None)
-L LOCALCONFIGFILENAME, --local-config LOCALCONFIGFILENAME
Local installation configuration file (default: /home/kinow/Development/python/workspace/WfExS-backend/wfexs_config.yml)
--cache-dir CACHEDIR Caching directory (default: None)
-V, --version show program's version number and exit
--full-help It returns full help (default: False)
commands:
Command to run. It must be one of these
{init,cache,staged-workdir,export,config-validate,stage,mount-workdir,export-stage,offline-execute,execute,export-results,export-crate}
init Init local setup
cache Cache handling subcommands
staged-workdir Staged working directories handling subcommands
export Staged working directories export subcommands
config-validate Validate the configuration files to be used for staging and execution
stage Prepare the staging (working) directory for workflow execution, fetching dependencies and contents
mount-workdir Mount the encrypted staging directory on secure staging scenarios
export-stage Export the staging directory as an RO-Crate
offline-execute Execute an already prepared workflow in the staging directory
execute Execute the stage + offline-execute + export steps
export-results Export the results to a remote location, gathering their public ids
export-crate Export an already executed workflow in the staging directory as an RO-Crate
Subparser 'init'
usage: WfExS-backend.py init [-h]
optional arguments:
-h, --help show this help message and exit
Subparser 'cache'
usage: WfExS-backend.py cache [-h] [-r] [--cascade] [-g] {ls,inject,fetch,rm,validate} {input,ro-crate,ga4gh-trs,workflow} [cache_command_args ...]
positional arguments:
{ls,inject,fetch,rm,validate}
Cache command to perform
ls List the cache entries
inject Inject a new entry in the cache
fetch Fetch a new cache entry, giving as input both the URI and optionally both a security context file and a security context name
rm Remove an entry from the cache
validate Validate the consistency of the cache
{input,ro-crate,ga4gh-trs,workflow}
Cache type to perform the cache command
input Cached or injected inputs
ro-crate Cached RO-Crates (usually from WorkflowHub)
ga4gh-trs Cached files from tools described at GA4GH TRS repositories
workflow Cached workflows, which come from a git repository
cache_command_args Optional cache element names (default: None)
optional arguments:
-h, --help show this help message and exit
-r Try doing the operation recursively (i.e. both metadata and data) (default: False)
--cascade Try doing the operation in cascade (including the URIs which resolve to other URIs) (default: False)
-g, --glob Given cache element names are globs (default: False)
Subparser 'staged-workdir'
usage: WfExS-backend.py staged-workdir [-h] [-g] {offline-exec,ls,mount,rm,shell,status} [staged_workdir_command_args ...]
positional arguments:
{offline-exec,ls,mount,rm,shell,status}
Staged working directory command to perform
offline-exec Offline execute the staged instances which match the input pattern
ls List the staged instances
It shows the instance id, nickname,
encryption and whether they are damaged
mount Mount the staged instances which match the input pattern
rm Removes the staged instances which match the input pattern
shell Launches a command in the workdir
First parameter is either the staged instance id or the nickname.
It launches the command specified after the id.
If there is no additional parameters, it launches a shell
in the mounted working directory of the instance
status Shows staged instances status
staged_workdir_command_args
Optional staged working directory element names (default: None)
optional arguments:
-h, --help show this help message and exit
-g, --glob Given staged workflow names are globs (default: False)
Subparser 'export'
usage: WfExS-backend.py export [-h] [-Z SECURITYCONTEXTSCONFIGFILENAME] [-E EXPORTSCONFIGFILENAME] -J WORKFLOWWORKINGDIRECTORY {ls,run} [export_contents_command_args ...]
positional arguments:
{ls,run} Export operations from staged working directory to perform
ls List the public identifiers obtained from previous export actions
run Run the different export actions, pushing the exported content and gathering the obtained permanent / public identifiers
export_contents_command_args
Optional export names (default: None)
optional arguments:
-h, --help show this help message and exit
-Z SECURITYCONTEXTSCONFIGFILENAME, --creds-config SECURITYCONTEXTSCONFIGFILENAME
Configuration file, describing security contexts, which hold credentials and similar (default: None)
-E EXPORTSCONFIGFILENAME, --exports-config EXPORTSCONFIGFILENAME
Configuration file, describing exports which can be done (default: None)
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
Subparser 'config-validate'
usage: WfExS-backend.py config-validate [-h] -W WORKFLOWCONFIGFILENAME [-Z SECURITYCONTEXTSCONFIGFILENAME] [-n NICKNAME_PREFIX]
optional arguments:
-h, --help show this help message and exit
-W WORKFLOWCONFIGFILENAME, --workflow-config WORKFLOWCONFIGFILENAME
Configuration file, describing workflow and inputs (default: None)
-Z SECURITYCONTEXTSCONFIGFILENAME, --creds-config SECURITYCONTEXTSCONFIGFILENAME
Configuration file, describing security contexts, which hold credentials and similar (default: None)
-n NICKNAME_PREFIX, --nickname-prefix NICKNAME_PREFIX
Nickname prefix to be used on staged workdir creation (default: None)
Subparser 'stage'
usage: WfExS-backend.py stage [-h] -W WORKFLOWCONFIGFILENAME [-Z SECURITYCONTEXTSCONFIGFILENAME] [-n NICKNAME_PREFIX]
optional arguments:
-h, --help show this help message and exit
-W WORKFLOWCONFIGFILENAME, --workflow-config WORKFLOWCONFIGFILENAME
Configuration file, describing workflow and inputs (default: None)
-Z SECURITYCONTEXTSCONFIGFILENAME, --creds-config SECURITYCONTEXTSCONFIGFILENAME
Configuration file, describing security contexts, which hold credentials and similar (default: None)
-n NICKNAME_PREFIX, --nickname-prefix NICKNAME_PREFIX
Nickname prefix to be used on staged workdir creation (default: None)
Subparser 'mount-workdir'
usage: WfExS-backend.py mount-workdir [-h] -J WORKFLOWWORKINGDIRECTORY
optional arguments:
-h, --help show this help message and exit
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
Subparser 'export-stage'
usage: WfExS-backend.py export-stage [-h] -J WORKFLOWWORKINGDIRECTORY [--full]
optional arguments:
-h, --help show this help message and exit
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
--full Should the RO-Crate contain a copy of the inputs (and outputs)? (default: False)
Subparser 'offline-execute'
usage: WfExS-backend.py offline-execute [-h] -J WORKFLOWWORKINGDIRECTORY
optional arguments:
-h, --help show this help message and exit
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
Subparser 'execute'
usage: WfExS-backend.py execute [-h] -W WORKFLOWCONFIGFILENAME [-Z SECURITYCONTEXTSCONFIGFILENAME] [-E EXPORTSCONFIGFILENAME] [-n NICKNAME_PREFIX] [--full]
optional arguments:
-h, --help show this help message and exit
-W WORKFLOWCONFIGFILENAME, --workflow-config WORKFLOWCONFIGFILENAME
Configuration file, describing workflow and inputs (default: None)
-Z SECURITYCONTEXTSCONFIGFILENAME, --creds-config SECURITYCONTEXTSCONFIGFILENAME
Configuration file, describing security contexts, which hold credentials and similar (default: None)
-E EXPORTSCONFIGFILENAME, --exports-config EXPORTSCONFIGFILENAME
Configuration file, describing exports which can be done (default: None)
-n NICKNAME_PREFIX, --nickname-prefix NICKNAME_PREFIX
Nickname prefix to be used on staged workdir creation (default: None)
--full Should the RO-Crate contain a copy of the inputs (and outputs)? (default: False)
Subparser 'export-results'
usage: WfExS-backend.py export-results [-h] -J WORKFLOWWORKINGDIRECTORY
optional arguments:
-h, --help show this help message and exit
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
Subparser 'export-crate'
usage: WfExS-backend.py export-crate [-h] -J WORKFLOWWORKINGDIRECTORY [--full]
optional arguments:
-h, --help show this help message and exit
-J WORKFLOWWORKINGDIRECTORY, --staged-job-dir WORKFLOWWORKINGDIRECTORY
Already staged job directory (default: None)
--full
So no more traceback! 🎉
Closing now. Thanks @jmfernandez !
from wfexs-backend.
My version:
(venv) kinow@ranma:~/Development/python/workspace/WfExS-backend$ git log -n 1
commit f260476e782edb52d168703d2c666daf56d48de3 (HEAD -> main, tag: 0.5.4, upstream/main, upstream/HEAD)
Author: José María Fernández <[email protected]>
Date: Wed Jun 1 20:46:48 2022 +0200
Removed indirect GPLv3+ dependency which was fetched as an optional jsonschema dependency.
Also, updated the version tag and copyright year in headers.
(venv) kinow@ranma:~/Development/python/workspace/WfExS-backend$ python WfExS-backend.py -V
WfExS-backend.py version 0.5.4 (f260476e782edb52d168703d2c666daf56d48de3)
(venv) kinow@ranma:~/Development/python/workspace/WfExS-backend$
from wfexs-backend.
Related Issues (20)
- Add support for compact `drs` identifiers HOT 1
- Add support for `secondaryFiles` CWL HOT 3
- Add support to `dav` and `davs` schemes
- Cannot download content from ftp HOT 5
- Parsing of Nextflow DSL2 workflows HOT 1
- Add support for swh permanent identifiers HOT 1
- Add several checks in the code to detect containers unavailable for the current hardware architecture
- Consider supporting other processor architectures through multiarch/qemu-user-static HOT 1
- Use pyinvoke and Fabric
- Fix dependency on newer versions of python-dxf HOT 1
- Introduce codemeta.json
- Secrets/secret inputs HOT 2
- Allow using as a staging source a Workflow Run RO-Crate
- Bug in path resolution in local config file HOT 3
- Error while running WfExS using a local workflow file/directory HOT 7
- PermissionError: [Errno 13] Permission denied: '/home/ansible/wfexs-backend-test/wf-cache' HOT 3
- Can't execute workflows using podman HOT 3
- `dot` dependency should be optional
- WfExS-backend init issues
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wfexs-backend.