Project

General

Profile

Actions
Copy link

Bug #7317

closed

[Workbench] Refusing to parse existing collection manifests with unescaped whitespace

Added by Nancy Ouyang over 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Story points:
-

Description

790 https://workbench.su92l.arvadosapi.com/collections/su92l-4zz18-ycisnf6v8xfs6fs fiddlesticks
783 https://workbench.su92l.arvadosapi.com/collections/su92l-4zz18-cfplid7uwl93wdb fiddlesticks
594 https://workbench.su92l.arvadosapi.com/collections/su92l-4zz18-syy066bpiha2wln fiddlesticks

parent project
https://workbench.su92l.arvadosapi.com/projects/su92l-j7d0g-1d2se4f08r0q7ta#Data_collections

I did not exhaustively search these, I polled only the ones with 23andMe data.

Actions
Copy link
 #1

Updated by Brett Smith over 10 years ago

  • Subject changed from Fiddlesticks while accessing collection contents to [Workbench] Refusing to parse existing collection manifests with unescaped whitespace
  • Category set to Workbench

Nancy,

This is happening because the manifests for these collections have unescaped whitespace in filenames. This is not supported in modern Arvados.

It's relatively easy to fix the manifests (just change all the spaces to \040 in the filenames), but that does change the content address, which might potentially affect provenance information. Do you know if there's any provenance information around these collections that needs to be kept?

Actions
Copy link
 #2

Updated by Nancy Ouyang over 10 years ago

I don't think any provenance information needs to be kept and I was also able to work around it I believe. So this bug can be tabled.

Apologies for the delay, I guess I didn't "watch" this bug :(

Actions
Copy link
 #3

Updated by Peter Amstutz about 6 years ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF