Skip to content

When validate reports a directory has a warning it says "XML could not be parsed." which is misleading. #1510

@tbarnes4

Description

@tbarnes4

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

Very low priority bug.

When I run validate with the -R pds4.bundle (assume similar with -R pds4.collection), if I get a directory with the warning that the "Directory name is reserved and not in the recommended location in the bundle root directory", the title line has the text "(XML could not be parsed.)" which is odd since there should be no XML to parse for a directory. Example message:

PASS: file:/sdata01/staging/300/60438/data/ (XML could not be parsed.)
WARNING [warning.sub_directory.unallowed_name] Directory name is reserved and not in the >recommended location in the bundle root directory

For reference 300 is the root directory of the bundle and 60438 is the collection level.

🕵️ Expected behavior

I expect a message that makes sense or no message.

📜 To Reproduce

Run validate -R pds4.bundle on a bundle that has a collection that has a subdirectory with a reserved name being used.

🖥 Environment Info

N/A

📚 Version of Software Used

validate Version 4.0.8

🩺 Test Data / Additional context

No response

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

Metadata

Metadata

Assignees

Labels

B17B18bugSomething isn't workings.mediumsprint-backlogtask-spillovertask from previous build increment have spilled over into current planning increment.

Type

Projects

Status

ToDo

Status

Review/QA

Status

Review/QA

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions