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
Error: Trying to get property 'id' of non-object #338
Comments
P.P.S. There are suspicions that this is due to the cache |
Hey, the issue is we are currently not removing deleted entries from the index after removing the metadata itself, so on subsequent cleanup commands we find entries for which we no longer have any metadata. Looking into this now. |
Is this index really necessary? In my opinion, deleting directly from the file system with checking by |
The index is mainly used in the requests search, since without an index file we would need to read and parse all the individual json files. It's also used in the web UI to find next/previous requests a little bit faster. Single requests retrieved by id bypass the index. This is what happens in a typical usage in Chrome/Firefox extensions, so it's not less efficient in the most common case. Cleanup itself is a little bit slower atm, but it runs only once in ~100 requests, so it shouldn't be too bad. I've got some ideas to improve it in future though. I've tagged 4.0.5 with a whole bunch of FileStorage cleanup fixes including the crash fix. |
An error
Trying to get property 'id' of non-object
occuring whileclockwork:clean
command launch.Here:
clockwork/Clockwork/Storage/FileStorage.php
Line 106 in 8aedfa4
Raw Exception:
P.S.
Laravel: 5.8
Clockwork: 4.0
The text was updated successfully, but these errors were encountered: