-
Notifications
You must be signed in to change notification settings - Fork 241
bug fixes of both issues of #838 #839
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
Conversation
…ord, the keyword is shown in PiGallery2 character by character, each prefixed by a hash sign, all separated by comma and space
…extension of the tagged file, no keywords and ratings are shown in PiGallery's frontend.
|
Thank you for your addition! There as a bigger MetadataLoader.ts change with one the latest PR that conflicts with the PR. Can you please resolve the conflict? |
# Conflicts: # src/backend/model/fileaccess/MetadataLoader.ts # test/backend/unit/model/threading/MetaDataLoader.spec.ts
|
Can you please rebase again? There was a bug in the MetadataLoader over the week that got fixed now. |
# Conflicts: # src/backend/model/fileaccess/MetadataLoader.ts
|
Thanks! The sidecar tests are failing, can you please take a look? |
Not for me 😄 |
|
My guess those files do not have a creation date in metadata and app falls back to the filesystem's date, so the test are flaky. Did you happen to touch those files? @grasdk do you have any idea? I take a look later but I won't be at computer during the next few weeks. |
|
I'll take a look tonight CET. @kagahd did you try removing the node modules dir or git clone your code into a new empty dir and rebuild everything from scratch? This would have an affect on the environment similar to what the automated test that fails has. Also: what is your timezone? I added timezone support..if metadata does not have timezone, local timezone is assumed. Your timezone might not be the same as the build server's timezone, which may cause irreproducible test results between your environment and the build server's. You can mitigate that by.expmicitly adfing timezone offset tonyour test data. /Regards |
|
@bpatrik was right. In the absense of reading creation date from metadata, file date was read. Since the test files were created at different times on the server and on @kagahd 's test environment, there was a failure. I made a not-too-pretty pull request for @kagahd 's branch: kagahd#1 that fixes the immediate problem. I think the test data that this PR brings is worth it. Also I think that these tests will benefit the other pull request for metadata: #841 |
Added read of CreationDate to sidecar and fixed tests
|
Thank you for both of you! |

dc.subjectto an array of one String so that the loop iterates not over the characters of the String but over the String(s) of the array.