Change Base64 encoded MD5s in filehandles into hex encoded MD5s

Description

None

Environment

None

Activity

Show:
Ziming Dong
January 17, 2020, 2:19 AM

syn17013485 was the table that had Base64 encoded MD5s in synapse when Dwayne and I were debugging the issue with uploads.

Specificlally, filehandle id 47392642 was shared with me.

For a more general validation, Base64 encoded md5 strings will always have a length of 24 characters since all MD5 digests have a size of 128 bits. The base 64 representations of MD5s should also always be padded with 2 equals signs "==" at the end

Bruce Hoff
January 17, 2020, 10:02 PM

On prod:

On staging:

Ziming Dong
January 17, 2020, 11:43 PM

I think you used the prod endpoint twice. From the python client:

Bruce Hoff
January 20, 2020, 3:08 PM

, I think you are right: I did do the R equivalent of 'setEndpoints' but (as is clear above) I should have specified 'https://repo-staging.prod.sagebase.org/file/v1' not 'https://repo-prod.prod.sagebase.org/file/v1' in my 'synRestGET()' command. I will validate again.

Bruce Hoff
January 20, 2020, 3:10 PM
Fixed

Assignee

Ziming Dong

Reporter

Ziming Dong

Labels

None

Validator

Bruce Hoff

Development Area

None

Release Version History

None

Fix versions

Priority

Major
Configure