logseq / logseq/db-test

Large files are not uploaded to remote (logseq sync)

Open
#1,013 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

I just tried adding a PDF with a size of 87 MB, and Logseq adds it locally but cant upload it to remote, it stays on "1 pending assets upload"

### Reproduce the Bug

1. Add large file

### Expected Behavior

_No response_

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

Logseq 2.0.1

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by reproducing the issue in Logseq 2.0.1 with an 87 MB PDF and inspect the remote sync upload path. Done means the large asset uploads successfully and the pending-assets count clears.

Written by the indexing model from the issue text.

Assessment

Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.