search

arch-kiosk / arch-kiosk-office

💼 central place for collaboration
GNU Affero General Public License v3.0
1 stars 0 forks source link

JIAAW CA synchronization synchronized unmodified images #1188

Open urapadmin opened 3 years ago

urapadmin commented 3 years ago

image

For fun I downloaded JIAAWmac, which had been forked ages ago, and added a handful of images, and synchronized at 3:15pm CA time. I still got a scary “there is no file matching” report three times. And yet, in the file repository are all five of the images I just added.

Originally posted by @lbestock in https://github.com/urapadmin/kiosk/issues/1184#issuecomment-886117678

urapadmin commented 3 years ago

First of all: None of the "no file matching" lines refers to any of the new files (they were six).

The fork time of jiaaw_mac was 07.07.2021 14:02

The image 900eeb46-64fe-4df2-ade3-3f18cfe78c66 was modified 05.07.2021 17:21:54, so it is correct that filemaker did not export it. What I don't understand is why it got synchronized.

Same with 9582e89b-7a53-45fd-8b2c-93e99099c735: modified 05.07.2021 17:21:54.

Same with f1e236c9-5c56-43f9-b37c-75b92e178739: modified 05.07.2021 17:21:54

The dates are the same in the file repository (but they have also been synchronized)

urapadmin commented 3 years ago

These three images have no modified_by. In fact there is a ton of empty modified_by fields in PVD. And most of them have 05.VII.2021 or 07.VII.2021 as the modification date. I checked that all users have a repl-user id configured in kiosk. Many but not all of the records with an empty modified_by seem to stem from file imports. But not all of them AND not all images that come from file imports have an empty modified_by field.

urapadmin commented 3 years ago

I cannot really see anything special going on on 05.VII because there was too much going on. I found that housekeeping ran outside of a synchronization run, which indicates that I had started it manually. But there is no indication of trouble.

urapadmin commented 3 years ago

at least this does not seem to be connected to #1184. What exactly caused this behavior is not clear to me. It was definitely not harmful: The mentioned files are there and the data seems correct.

@test:

We have to see if these messages appear more often and if we see them in any of the real projects, too.

urapadmin commented 3 years ago

The logs for this case: kiosk_Sat_240721-1123.log log_05_and_07_07_2021.zip MCP_744_kiosk_Sat_240721-1814.log MCP_3416_kiosk_Sat_240721-1813.log

urapadmin commented 3 years ago

just a faint hunch: Could it be that this has anything to do with images that got "rewired"?

If so, I can't see any rewiring in the logs around 05.VII and 07.VII