File-to-DB import does not work with multiple file uploads
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- database
Research direction
The report describes importing Markdown notes through “File to Graph” in DB 2.0, failing after about 898 pages with “fail to fetch.” Start by reproducing the import with the attached file and checking where the import request fails as page and property counts grow. Done means the reported files import successfully, or the failing limit is identified and documented.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
-
What Happened?
The import worked fine when there were only a few documents with a small number of property, but as the number of pages increased and the number of property exceeded 40,000, I kept getting "fail to fetch" errors. Is there a limit to the number of property that can be imported?
I ran a Python script created by another user(benjypng) to check if there were any issues with the MD files, but it reported no problems. I’m not sure if this is simply a bug or a numerical limit.(db 2.0. 2 nightly 22a29b3-dirty) Any suggestion?
Reproduce the Bug
-
Reproduce the Bug
1- Import existing notes
2- Choose File to Graph
3- wait and until 898 page fine
4- but error 'fetch fail'
Expected Behavior
Import all the md files
Screenshots
No response
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
-
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
jasonacox/pypowerwall#472 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
surrealdb/surrealdb.py#439 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
mattgodbolt/zindex#67 ·
Maintainers usually reply within 1 day