Cannot import graph to logseq IDE
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- database
Research direction
The report says importing existing notes as a file to DB graph fails after the user selects the graph location; it provides screenshots but no error text or source files. Start by examining the import flow and the error shown in the screenshot, then reproduce with the supplied graph data if available. Done means the existing graph imports successfully and the failure has a confirmed cause.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
Dear logseq developer community,
I cannot re-import a logseq graph from my local storage. Due to an issue with a tag (I accidentally created a link that was huge and therefore made my system crash), I deleted the logseq application and saved all my logseq data locally and on a remote gitlab. After reinstalling the app, I now cannot import the data again as a graph...
Neither SQL, nor EDN, nor file import works...I am quite desperate since this is now 2 years of PhD work disappearing. It would be great if you can help me soon with this issue. Below I provided some screenshots of the data that is still on my computer. Thank you very much!
BR Victoria
Reproduce the Bug
- Import existing notes
- File to DB graph
- I choose the file location of the graph
- Import starts then error
Expected Behavior
No response
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
No response
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!)
- 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
-
Add: Hindi Hits LogoOpencheck:passed logos:add
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
backend prio:low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
digitalfabrik/entitlementcard#3262 ·
Maintainers usually reply within 2 days
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
madenvel/KalinkaPlayer#536 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
RedisStorage writes can persist a key without its sliding TTLPossibly taken @lianbie claimed this today. Opentriage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentscope-ai/agentscope#3878 · 1 comment ·
Maintainers usually reply within 2 days