-
Notifications
You must be signed in to change notification settings - Fork 535
Closed
Description
Summary
The DataSink interface does not work.
Actual behavior
Only the local copy works. Oddly, when used in a workflow, DataSink creates a local directory named s3:/
instead.
Expected behavior
DataSink creates objects in S3 buckets when base_directory starts with s3://
.
How to replicate the behavior
ds = DataSink()
ds.inputs.base_directory = 's3://kimsin-test'
ds.inputs.creds_path = os.path.abspath('aws.csv')
ds.inputs.encrypt_bucket_keys = True
ds.inputs.local_copy = os.path.abspath('log')
setattr(ds.inputs, 'out_s3', 'DELETE.me')
ds.run()
This basic S3 test code does not create the desired output in the S3 bucket.
Platform details:
{'commit_hash': '%h',
'commit_source': 'archive substitution',
'networkx_version': '2.4',
'nibabel_version': '2.5.1',
'nipype_version': '1.3.0-rc1',
'numpy_version': '1.17.3',
'pkg_path': '/opt/miniconda-latest/envs/neuro/lib/python3.6/site-packages/nipype',
'scipy_version': '1.3.1',
'sys_executable': '/opt/miniconda-latest/envs/neuro/bin/python',
'sys_platform': 'linux',
'sys_version': '3.6.7 | packaged by conda-forge | (default, Jul 2 2019, '
'02:18:42) \n'
'[GCC 7.3.0]',
'traits_version': '5.1.2'}
Execution environment
- My python environment inside container
Metadata
Metadata
Assignees
Labels
No labels