fix: add missing entity id in FsEventMapper::getFromQueue() #196
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.
The FileSystemListener background job tries to delete events from the queue if the home-dir of the user cannot be found (e.g. because the user account has been removed):
context_chat/lib/BackgroundJobs/FileSystemListenerJob.php
Line 104 in f8566e5
However, this call to
FsEventMapper::delete()cannot succeed if the entity id is missing, as is currently the case because ATMFsEventMapper::getFromQueue()omits the id in its result "entities" (which are in fact then only partial entities).Another way to fix this would be to use
FsEventMapper::deleteByContent()instead.I stumbled over this cause of errors in the NC log like
with stack trace back to
As such this is just ok and the effect of trying to access the home-directory of a no-longer existing user, but those messages do not go away, they appear over and over again because that delete attempt from
context_chat/lib/BackgroundJobs/FileSystemListenerJob.php
Line 104 in f8566e5
fails as the data returned by
FsEventMapper::getFromQueue()does not include the entity id.