| Summary: | [server] Runtime exception thrown with orphan files in the Orion repository | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Anthony Hunter <ahunter.eclipse> |
| Component: | Server | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | john.arthorne |
| Version: | 4.0 | Flags: | john.arthorne:
review+
|
| Target Milestone: | 4.0 RC2 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Anthony Hunter
I have fixed the orphan folders case as well. 2013-10-10 15:07:41.372 [Worker-0] WARN org.eclipse.orion.server.config - Meta File Error, root contains invalid metadata:/workspace/foo/zz at zz 2013-10-10 15:07:41.373 [Worker-0] WARN org.eclipse.orion.server.config - Meta File Error, root contains invalid metadata:/workspace/foo/A at B 2013-10-10 15:07:41.374 [Worker-0] WARN org.eclipse.orion.server.config - Meta File Error, root contains invalid metadata:/workspace/foo/ls.txt at ls.txt The fix is at commit: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?h=ah-Bug419176&id=dc6ea07f4ed771843f1c79a6c9b68b75d8518a02 Looks good. Not as urgent but we should have some tests for these kinds of scenarios. I.e., place a bunch of bogus files on disk in places where we expect metadata and make sure it doesn't trip us up. Also metadata files that have correct names but JSON syntax errors for example. Printing warnings in the log is good but we should be resilient to corrupt metadata in all forms. (In reply to Anthony Hunter from comment #1) > The fix is at commit: > http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?h=ah- > Bug419176&id=dc6ea07f4ed771843f1c79a6c9b68b75d8518a02 The fix is in master with commit: http://git.eclipse.org/c/orion/org.eclipse.orion.server.git/commit/?id=dc6ea07f4ed771843f1c79a6c9b68b75d8518a02 |