@eric215 With every release files might be removed as they are not used any longer. Normally the update process should remove the files automatically. In some cases that might not work correctly for various reasons (like permissions). In that case those files will be reported in the integrity report. It is safe to simply remove those files.

@eric215 Matomo should for example not create libs/bower_components during a Matomo 4 release. Have you maybe removed that directly before, then updated and it was showing the same directory to delete again?

Sorry for the delay in responding, personal issues kept me offline.

Yes, I am confident that I deleted libs/bower_components in the past, and I do recall when I deleted it this time it had a timestamp of "today". I'm sorry I didn't think at the time to take a screen shot

Thanks @eric215 We're planning to do another release. Be great if you could check if it then complaints about the same files again and let us know if it does.

Upgrading from 4.0.5 to 4.1 I did NOT have an issue with any of the above-mentioned files hooray!

I did have a file-integrity failure on vendor/bin/lessc I can confirm that vendor/bin did not exist before the upgrade. I can create a separate issue if you'd prefer.

Thanks @eric215 I think this might be actually a new "regression" as we had just changed a library there and probably something needs adjusting. Thanks for this & happy holidays

I have noticed this issue, too, it is present for at least a year, possibly longer. Several different systems (vps, cloud), permissions and ownerships are in proper order, not a single other script that runs on different server setups complains about this, only Piwik/Matomo has a problem automatically removing obsolete files. I thought it was on purpose, to avoid problems when downgrading or when upgrade fails to complete. Think about this, if rights/owns were not in order, it would also fail in executing upgrades and other things (e.g. installing plugins). So, the issue, unless intentional feature, is with something else.

It's not intentional but we also haven't been able to reproduce any issue here yet except for when new files were added or removed and they weren't excluded yet for example.

Can we close this issue or is here anything left we should do?

Yes, whenever possible, the best way to "solve" the issue is to close it. 🤣

We aren't using some exotic systems that can be hard to reproduce, cloud linux and self-managed vps/dedi are ubiquotus these days, so that is not an excuse. On the other hand, matomo couldn't work properly if file and user systems are faulty, because caching would fail and many other things along the way, e.g. update itself.

Something just occurred to me, is it possible that shell_exec being disabled could be the cause of it? If yes, then you should add a fallback function to remove files.

@dev-101 shell_exec shouldn't be used during the update AFAIK.

@sgiehl @dev-101 I'll close the issue for now as the original file integrity issue should be fixed. We could always keep track of people experiencing file update issues in a separate issue (unless there is already one). Be great to know when someone experiences issues that files weren't correctly updated or deleted what operating system they use, how often this happens (eg on every update or only randomly etc)