[DB 2.0.2] Asset size filter causes #Asset page to crash
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the crash on the #Asset page with a size-zero filter after importing a graph with missing PDFs; compare the affected graph with the Demo graph. The developer console reports Expected number or lookup ref for entity id, got 0, and the issue identifies logseq.property.table/filters as the view property whose removal restores access. Done means the filter no longer crashes the page, or the view can be reset gracefully.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
After an import with missing PDFs, the #Asset page was super sluggish. When I created a filter to find items of size 0, the page crashed and kept crashing upon opening the page. I was not able to open the #Asset page at all.
The developer console showed:
Expected number or lookup ref for entity id, got 0
The same page worked correctly in the Demo graph.
After deleting the filter with the CLI (and the missing PDF records), the page worked again.
Reproduce the Bug
- Import a graph with missing PDF files
- Go to the #Asset page
- Create a filter for size zero
- See crash
Expected Behavior
The page should not crash in the first place.
In beast case, Logseq would handle it gracefully or provide a way to reset the view.
Screenshots
No response
Desktop or Mobile Platform Information
Linux, zip based desktop app
Additional Context
Removing the logseq.property.table/filters property from the affected view using the CLI fixed it.
logseq --graph "GRAPH_NAME" upsert block
--uuid VIEW_UUID
--remove-properties '[:logseq.property.table/filters]'
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- No language data
- Stars
- 29
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/db-test
-
Web build on a phone: the fold arrow of an h1/h2 block lies on its bullet, so tapping the bullet folds instead of zooming inPossibly taken @tiensonqin claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Page titles with `$$`, `$&`, `` $` `` or `$'` change when block refs are resolvedPossibly taken @RaphaelFakhri claimed this 19 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
`#Asset` label is not displayed on asset nodes when `Hide from Node` is disabledPossibly taken @tiensonqin claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug sharing & sync
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
navikt/pensjonskalkulator-frontend-monorepo#270 ·
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
anomalyco/opencode#62873 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
inveniosoftware/invenio-app-rdm#3630 ·
Maintainers usually reply within 2 days