You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using rucio download --dir {scope} --scope {scope} {file} an unknown database error is raised.
This is because "scope" is not parsed as a scope, producing the request data: [{"dids": [{"scope": "file", "name": "file"}], ... instead of the expected [{"dids": [{"scope": "scope "name": "file"}]
This seems to be somewhat intentional behavior (the DID is incorrectly supplied, missing the scope), but the kwargs do not make sense in that sense. If a scope is supplied, it should be used for the DID even if 'filter' is not used.
The argument descriptions for reference
Usage: rucio download [OPTIONS] [DIDS]...
Download DID(s) (in the form of scope:name) to a local dir
Options:
--dir TEXT The directory to store the downloaded file.
--allow-tape Also consider tape endpoints as source of
the download.
--rses, --rse-exp TEXT RSE Expression to specify allowed sources
--impl TEXT Transfer protocol implementation to use
(e.g: xrootd, gfal.NoRename, webdav,
ssh.Rsync, rclone).
--protocol TEXT Force the protocol to use.
--nrandom INTEGER Download N random files from the DID.
--ndownloader INTEGER Choose the number of parallel processes for
download.
--no-subdir Don't create a subdirectory for the scope of
the files.
--pfn TEXT Specify the exact PFN for the download.
--no-resolve-archives If set archives will not be considered for
download.
--ignore-checksum Don't validate checksum for downloaded
files.
--check-local-with-filesize-only
Don't use checksum verification for already
downloaded files, use filesize instead.
--transfer-timeout FLOAT Transfer timeout (in seconds). Default:
computed dynamically from --transfer-speed-
timeout. If set to any value >= 0,
--transfer-speed-timeout is ignored.
--transfer-speed-timeout FLOAT Minimum allowed average transfer speed (in
KBps). Default: 500. Used to dynamically
compute the timeout if --transfer-timeout
not set. Is not supported for --pfn.
--aria BOOLEAN Use aria2c utility if possible.
(EXPERIMENTAL)
--filter TEXT Filter files by key-value pairs like
guid=2e2232aafac8324db452070304f8d745.
--scope TEXT Scope if you are using the filter option and
no full DID.
--metalink TEXT Path to a metalink file.
--no-show-download-exceptions Does not raise NoFilesDownloaded,
NotAllFilesDownloaded or incorrect number of
output queue files Exception.
--replica-selection TEXT Select the best replica using a replica
sorting algorithm provided by replica sorter
(e.g., random, geoip).
-h, --help Show this message and exit.
Description
When using
rucio download --dir {scope} --scope {scope} {file}
an unknown database error is raised.This is because "scope" is not parsed as a scope, producing the request data:
[{"dids": [{"scope": "file", "name": "file"}], ...
instead of the expected[{"dids": [{"scope": "scope "name": "file"}]
This seems to be somewhat intentional behavior (the DID is incorrectly supplied, missing the scope), but the kwargs do not make sense in that sense. If a scope is supplied, it should be used for the DID even if 'filter' is not used.
The argument descriptions for reference
Steps to reproduce
In a testing setup - run
and see the file fails to upload.
Compare to the scope-less version, which works.
rucio download --dir {tmp_dir} {scope}:{tmp_file}
Rucio Version
No response
Additional Information
Full verbose log:
The text was updated successfully, but these errors were encountered: