Query renamed my tag to an invalid name, corrupting database

[kerim]

Search first

• I searched and no similar issues were found

What Happened?

I use a tag #ck to add a checkbox to blocks when I don't want a full-blown task (such as with checklists for tasks). I thought I'd do a simple query to find all blocks that have the tag #ck where the box is unchecked. However, doing this renamed #ck to "["~bQGD0FasMYj+fvnJe","~bEG0qFN0Xy/WaiN3Vs85IxOpY"] and then gave me an invalid graph error because that is not a valid name for a tag. I tried renaming it, but it won't let me.

Reproduce the Bug

see above

Expected Behavior

see above

Files

error log.txt

Browser, Desktop or Mobile Platform Information

logseq/logseq@d867bf6
macOS desktop app

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[kerim]

I was able to fix the problem by adding a new tag #cb and removing the old tag #["~bQGD0FasMYj+fvnJe","~bEG0qFN0Xy/WaiN3Vs85IxOpY"]. When I added the simple checkbox property to #cb, all my checkbox states were restored as from before, so luckily I didn't loose any data.

[kerim]

Yikes. I then tried to create a query for #cb and the SAME THING happened again!

All my #cb tags were renamed to #["~bJxGHaL3V//78sCHb","~biwg1fy0EI0819PUCW7xItT5d"]!!!

error log 2.txt

[kerim]

This time it did allow me to rename directly, so fixing it was a bit easier.

Here is a transit log.

logseq_db_e2ee restore 2-debug-datoms_1765001203.transit.zip

[kerim]

Can confirm that the bug is still present in logseq/logseq@05f21dd

[RCmerci]

thanks for the report! I think this issue is same as #651

I can reproduce it now

[tiensonqin]

@RCmerci pushed some fixes, @kerim please give the latest release a try.
https://github.com/logseq/logseq/actions/runs/20120154317

[kerim]

Yup, seems fixed. Thanks.