Validate DB failed

[hdansou]

Search first

• I searched and no similar issues were found

What Happened?

Triggering the validate Graph returns errors in the console - refer to the log files attached.

Reproduce the Bug

1. CMD + Ship + p
2. Select validate graph
3. Open the console and look for the error message

Expected Behavior

graph validation should complete successfully and return the result on the popup.

Files

-1736051267968.log
-1736051257705.log
-1736051227344.log

Browser, Desktop or Mobile Platform Information

macOS Sequoia
Latest build (2025-01-04) from feat/DB
Desktop version

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!)

[logseq-cldwalker]

Hi. Looks like this command failing to run was fixed by logseq/logseq@a45da56. Should be up on test in ~10m

[hdansou]

@logseq-cldwalker, that is an improvement. we have now a message.

The message signals that there are blocks with issues but does not give references to those blocks. Therefore, the user can't take any action. What can we do to improve it?

[Bad3r]

Oof

The full console log is +700kb
https://gist.github.com/Bad3r/338b71dc5fd2ea3fca4bdebb4253197b

[logseq-cldwalker]

@hdansou The invalid blocks should be printed in the console. DB validation is primarily intended for Logseq developers so I wouldn't expect this to be actionable for users. Unfortunately we don't have the bandwidth to look at users' graphs and help them understand this output. For other users who are technical minded it could be helpful to chat about this in discord threads
@tiensonqin Any other suggestions to add?

[hdansou]

@logseq-cldwalker I found the output in the info messages. Here is one example for reference.

{:entity {:block/tx-id 536951925, :db/index true, :block/uuid #uuid "00000002-1340-4105-1600-000000000000", :db/valueType :db.type/ref, :block/updated-at 1726271820532, :block/refs #{47}, :block/created-at 1726271770460, 
:block/schema {:type :node}, :block/tags [{:db/ident :block/tags, :db/valueType :db.type/ref, :db/cardinality :db.cardinality/many, 
:block/schema {:type :class}} #{9653 9655} {:page-class-id 9655, :all-page-class-ids #{9653 9655 9654 56 9656}}], :block/title "Category", :db/cardinality :db.cardinality/one, :db/ident :user.property/qZPF5s__G0PURsosgNAp5-Category, :block/path-refs #{47}, :block/order "bSG", :block/name "category"}, :errors {0 {:block/tags ["should not have other built-in page tags when tagged with #Page"]}}}

I am technical and happy to chat about it and find a solution. Side note: All my graphs failed the validation except the one that was created brand new without any content. I suspect this would be happening on other users' graphs, too.

Here is the discord thread: https://discord.com/channels/725182569297215569/1326302187869048842

[tiensonqin]

@hdansou @Bad3r Can you try the latest feat/db branch? I'm trying to fix all the issues I can reproduce with the exported graph transit file. Let me know if there are still invalid blocks.

[tiensonqin]

Notice that we can't ensure the db is validated if you're using the feat/db branch, so please choose the test/db branch for your daily usage.

[hdansou]

It is much better now. After I pulled the latest code, I ran the validate DB and had ~900 errors. I rerun, and it dropped to ~20 and then down to 1.
I checked the block in question and found that I was using a URL as a property, with the URL set as follows: . After fixing it, all validations passed.

Last, I have updated my build script to use test/db

[hdansou]

@tiensonqin can you provide a couple of bullet points about how this feature works and how we will use it? We will use that to update the documentation as we progress.

[tiensonqin]

@hdansou It's precisely the steps you took above: re-run the db validation if there are any errors, and send the console log to us if there are any errors you don't know how to fix.

I'm closing this issue for now.