[MAGNOLIA-6611] Relativize paths for deleted resources in FileSystemResourceOrigin Created: 22/Mar/16  Updated: 24/Apr/16  Resolved: 15/Apr/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.5
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-6278 Files added at the same time as their... Closed
supersession
is superseded by MAGNOLIA-6223 Provide proper API for resource chang... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: Basel 40
Story Points: 1

 Description   

Current workaround for deleted file support has a flaw in FileWatcherCallback - the path passed into a stub object is not one compatible with FileSystemResourceOrigin but the real file path. This can lead to problems with evaluating such paths further in resource framework pipeline, especially on Windows, whose real paths lead to exceptions when tried against a JcrResourceOrigin (e.g. this stacktrace: https://s3-eu-west-1.amazonaws.com/uploads-eu.hipchat.com/20450/492569/le3EQDqeD2yBtZC/namespace-error.txt).



 Comments   
Comment by Mikaël Geljić [ 31/Mar/16 ]

We should probably get that scheduled (and mention quickly again who came across this, wasn't it via support or services?)

Comment by Mikaël Geljić [ 15/Apr/16 ]

Ok, that was originally reported by cmeier, on behalf of Ruth.

I got forwarded an interesting error message from @Ruth She got it while working on some templates examples with M 5.4.5 on windows.
Unfortunately she can't remember exactly the context when it happened.

Anyway, if you could drop a line why it was obsoleted, or point to a concept, would be great O
—let me remove fix version then too.

Generated at Mon Feb 12 04:16:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.