-
-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUGFIX: Fusion avoid error on cache invalidation while developing #4838
Merged
kitsunet
merged 1 commit into
neos:8.0
from
mhsdesign:bugfix/4415-fusion-error-on-dev-cache-invalidation-attempt-2
Jan 16, 2024
Merged
BUGFIX: Fusion avoid error on cache invalidation while developing #4838
kitsunet
merged 1 commit into
neos:8.0
from
mhsdesign:bugfix/4415-fusion-error-on-dev-cache-invalidation-attempt-2
Jan 16, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 tasks
kdambekalns
reviewed
Jan 16, 2024
Replaces neos#4509 Resolves neos#4415 After deleting a fusion file like `BrandLogo.fusion` one will face the error after booting flow and thus triggering the file monitor and its listeners: (even like a simple `flow help`) ``` Couldn't resolve realpath for: '/absolutePath/Code/core/Neos.NeosIo/Packages/Sites/Neos.NeosIo/Resources/Private/Fusion/Content/BrandLogo/BrandLogo.fusion' ``` This is caused as `realpath` returns false if the file was deleted, and we were to eager validating this. But as flows file monitor already returns absolute paths we can skip the realpath calculation here and move it to the `ParserCache::cacheForFusionFile`. Initially the call to `realpath` was made in a single place to avoid making to many assumptions about the form flow returned file paths.
mhsdesign
force-pushed
the
bugfix/4415-fusion-error-on-dev-cache-invalidation-attempt-2
branch
from
January 16, 2024 15:24
c675950
to
5377b86
Compare
kitsunet
approved these changes
Jan 16, 2024
6 tasks
kdambekalns
approved these changes
Jan 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 by 👀
mhsdesign
deleted the
bugfix/4415-fusion-error-on-dev-cache-invalidation-attempt-2
branch
January 16, 2024 18:32
The thesis
was wrong. There will be symlinks instead of actual files which causes this regression: |
This was referenced Feb 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #4509
Resolves #4415
After deleting a fusion file like
BrandLogo.fusion
one will face the error after booting flow and thus triggering the file monitor and its listeners: (even like a simpleflow help
)This is caused as
realpath
returns false if the file was deleted, and we were to eager validating this. But as flows file monitor already returns absolute paths we can skip the realpath calculation here and move it to theParserCache::cacheForFusionFile
. Initially the call torealpath
was made in a single place to avoid making to many assumptions about the form flow returned file paths.Upgrade instructions
Review instructions
Checklist
FEATURE|TASK|BUGFIX
!!!
and have upgrade-instructions