Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default checksum algorithms not triggered #3138

Closed
gabrielefronze opened this issue Nov 27, 2019 · 0 comments · Fixed by #3140
Closed

Default checksum algorithms not triggered #3138

gabrielefronze opened this issue Nov 27, 2019 · 0 comments · Fixed by #3140

Comments

@gabrielefronze
Copy link
Contributor

gabrielefronze commented Nov 27, 2019

Motivation

If the custom checksum support RSE attribute supported_checksums is not set, the RSE is by default defined compatible with the standard checksum algorithms.

Due to how get_rse_attribute works, when supported_checksums is not found, an empty string containing is returned instead of a None string.

The following logic assumed to have an None string, instead of a string formatted like that.

Modification

Update the logic to sense such behavior and return the standard GLOBALLY_SUPPORTED_CHECKSUMS list in that case.

bari12 added a commit that referenced this issue Nov 28, 2019
…um_algorithm_is_not_triggered

Transfers: Default checksum algorithm is not triggered; Fix #3138
bari12 added a commit that referenced this issue Nov 28, 2019
…um_algorithm_is_not_triggered

Transfers: Default checksum algorithm is not triggered; Fix #3138
bari12 added a commit that referenced this issue Nov 28, 2019
…um_algorithm_is_not_triggered

Transfers: Default checksum algorithm is not triggered; Fix #3138
@bari12 bari12 added this to the 1.21.0.post2 milestone Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants