Error: Invalid property format: type: Hitoduma Medusa-san tono NTR

sizer99 · 2024-02-25T08:17:42.919Z

Operating system

Windows

Joplin version

2.13.15

Desktop version info

Joplin 2.13.15 (prod, win32)

Client ID: 4aaec9e59fe6455b9687d8c81b0e5bf7
Sync Version: 3
Profile Version: 44
Keychain Supported: Yes

Revision: 7d2c1c0

Csv Import: 1.0.1
Favorites: 1.3.0
Markdown Table: Sortable: 1.2.2
Math Mode: 0.5.3

Sync target

File system

What issue do you have?

I just sync to another directory (which gets backed up by pCloud).

I translate a lot of Japanese Manga for various groups, and about a month ago I did a gag manga about a cheating medusa wife and Joplin started throwing sync errors. I suspect it's because I initially named the note with Kanji and it doesn't know how to deal with that?

I did the How to enable debugging | Joplin thing, and got a log with errors, but don't see anything that tells me how to fix this - any help? Thank you.

Log file

log.txt (76.3 KB)

JackGruber · 2024-02-25T08:26:40.299Z

Hello,

have you edit the md files in the SyncTarget where you have selected FileSystem outside of Joplin?
Because the file 29154f53183c464f9687d8b5a39464f5 is no longer valid, the type field is messed up.

Could you upload the 29154f53183c464f9687d8b5a39464f5 file.

sizer99 · 2024-02-25T08:42:05.311Z

I had not, because I don't know enough to manually edit any of the Joplin files. However, with your info I was able to determine that pCloud had created a 29154f53183c464f9687d8b5a39464f5 (conflicted).md5 file in the sync directory, which was what was upsetting Joplin. Now I know to look for those, thank you.

laurent · 2024-02-25T11:03:31.218Z

Also is pCloud based on Nextcloud? Because simply opening a file in Nextcloud (without even changing it) is going to corrupt it. That won't be fixed as they consider it's working as expected...

github.com/laurent22/joplin

Nextcloud sync: Very easy to cause data corruption with Nextcloud's rich text editor

opened 03:08PM - 08 Feb 24 UTC

personalizedrefrigerator

bug sync high

### Operating system Linux ### Joplin version 2.14.12 ### Desktop ve…rsion info _No response_ ### Current behaviour 1. Open a file on the Nextcloud web interface (left-click) 2. Leave open for about 30 seconds (long enough to auto-save) 3. Try to sync Joplin Currently, ```yaml id: 36dc5bb035a0433da224b8fcc0368081 parent_id: item_type: 1 item_id: ee829a38b5e84cd48d74aeee602b1e72 item_updated_time: 1707265701979 title_diff: "[{\"diffs\":[[1,\"Test NUL 2\"]],\"start1\":0,\"start2\":0,\"length1\":0,\"length2\":10}]" body_diff: "[{\"diffs\":[[1,\"Test NUL 2\\\n\\\n\\\n\\\n[js-draw.pdf](:/3529017ac0974c8a8fd463f60b3d16a8)\\\n\\\n\"]],\"start1\":0,\"start2\":0,\"length1\":0,\"length2\":65}]" metadata_diff: {"new":{"id":"ee829a38b5e84cd48d74aeee602b1e72","parent_id":"248e9425a4e042cda71d51f42b6d498f","latitude":"123.45678","longitude":"9101112.13141","altitude":"0.0000","author":"","source_url":"","is_todo":0,"todo_due":0,"todo_completed":0,"source":"joplindev-desktop","source_application":"net.cozic.joplindev-desktop","application_data":"","order":0,"markup_language":1,"is_shared":0,"share_id":"","conflict_original_id":"","master_key_id":"","user_data":""},"deleted":[]} encryption_cipher_text: encryption_applied: 0 updated_time: 2024-02-07T00:34:40.150Z created_time: 2024-02-07T00:34:40.150Z type_: 13 ``` becomes ```yaml id: 36dc5bb035a0433da224b8fcc0368081 parent_id: item_type: 1 item_id: ee829a38b5e84cd48d74aeee602b1e72 item_updated_time: 1707265701979 title_diff: "[{"diffs":\[\[1,"Test NUL 2"\]\],"start1":0,"start2":0,"length1":0,"length2":10}]" body_diff: "[{"diffs":\[\[1,"Test NUL 2\\\\n\\\\n\\\\n\\\\n[js-draw.pdf](:/3529017ac0974c8a8fd463f60b3d16a8)\\\\n\\\\n"\]\],"start1":0,"start2":0,"length1":0,"length2":65}]" metadata_diff: {"new":{"id":"ee829a38b5e84cd48d74aeee602b1e72","parent_id":"248e9425a4e042cda71d51f42b6d498f","latitude":"123.45678","longitude":"9101112.13141","altitude":"0.0000","author":"","source_url":"","is_todo":0,"todo_due":0,"todo_completed":0,"source":"joplindev-desktop","source_application":"net.cozic.joplindev-desktop","application_data":"","order":0,"markup_language":1,"is_shared":0,"share_id":"","conflict_original_id":"","master_key_id":"","user_data":""},"deleted":\[\]} encryption_cipher_text: encryption_applied: 0 updated_time: 2024-02-07T00:34:40.150Z created_time: 2024-02-07T00:34:40.150Z type\_: 13 ``` Sync with Joplin then fails (key `type_` not found). ### Expected behaviour Either 1. Joplin should be able to handle characters escaped by Nextcloud - **Edit**: This doesn't seem feasible — Nextcloud changes more than just `type_` -> `type\_` (compare `body_diff` and `title_diff` above). 3. It shouldn't be possible to edit Joplin sync files in Nextcloud's rich text editor UI (e.g. make them use a `.yaml` extension) - **Edit**: This isn't feasible either — see below. ### Logs _No response_

sizer99 · 2024-02-25T18:10:21.388Z

Hi Laurent - I don't believe so. It's their own sauce, they've been around since 2014.

From experience, it creating a '(conflicted)' version of a file happens when it can't reconcile the cloud version with local changes - the three way diff fails so it creates the extra (conflicted) file so at least you don't lose anything. I've been using pCloud with Joplin for about a year now, syncing from Joplin to a directory that's pCloud backed up, and this is the only (conflicted) file so far. And now I know what to do if that happens again.

laurent · 2024-02-25T18:59:18.833Z

Handling conflicts is something that happens client-side which means it's probably the pCloud sync client that created that conflict file. I suppose it could happen but it could cause issues with Joplin's own conflict resolution algorithm.

When this happens, move the (conflicted) file out of the folder but maybe keep it somewhere in case it turns you need it to restore data.

system · 2024-03-26T18:59:31.310Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.