Graph with pdf larger than 100 MB fails to publish
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 313
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
What Happened?
Given: I hit save on Logseq with a pdf larger then 100 MB.
Then: I need that change to be saved on my Github-Pages website.
What's actually happening: I'm getting an error during the final push to the github actions branch.
/usr/bin/git push --force ***github.com/varnem2/cyberpunk.git github-pages-deploy-action/23m5o9btt:gh-pages
remote: error: Trace: 43ac3ee0bbb1b176ddf473ae9c74f4ff23c427637c6edf396b321c047863cdf2
remote: error: See https://gh.io/lfs for more information.
remote: error: File assets/Cyberpunk_Red_1755890258178_0.pdf is 294.64 MB; this exceeds GitHub's file size limit of 100.00 MB
remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com./
To https://github.com/varnem2/cyberpunk.git
! [remote rejected] github-pages-deploy-action/23m5o9btt -> gh-pages (pre-receive hook declined)
error: failed to push some refs to 'https://github.com/varnem2/cyberpunk.git'
Running post deployment cleanup jobs… 🗑️
/usr/bin/git checkout -B github-pages-deploy-action/23m5o9btt
Reset branch 'github-pages-deploy-action/23m5o9btt'
/usr/bin/chmod -R +rw github-pages-deploy-action-temp-deployment-folder
/usr/bin/git worktree remove github-pages-deploy-action-temp-deployment-folder --force
Error: The deploy step encountered an error: The process '/usr/bin/git' failed with exit code 1 ❌
Notice: Deployment failed! ❌
Other Comments:
Per https://github.com/JamesIves/github-pages-deploy-action/issues/1139 the github action step https://github.com/logseq/publish-spa/blob/main/action.yml#L37-L41 needs the following yaml added to enable lfs.
- name: Checkout action
uses: actions/checkout@v4
with:
repository: logseq/publish-spa
path: .logseq-publish-spa
lfs: true
Reproduce the Bug
- Create a new Github Repo and configure git lfs.
git init && git lfs install && git lfs track *.pdf
- Create Github repo and run command to add repo as valid remote
git remote add origin $repo
- Ensure github pages classic is enabled in the repo
- Follow the steps 2 through 11 under the creating-your-website header.
- Open folder as logseq vault using the most recent beta version 0.10.13
- Add in github actions build.yml
- Mark page public using the 3 dots at the top of the screen.
- Drag pdf into the desktop window in that's larger then 100MB.
- Ensure logseq has successfully committed the file by checking your repo
- Review logs to ensure build is successful
- Go to github pages url and navigate to where you expect to see the pdf
Expected Behavior
I expect github action to deploy the asset successfully.
Desktop or Mobile Platform Information
Logseq App Version: 0.10.13
Example repos:
https://github.com/varnem2/cyberpunk/actions/runs/17165808918/job/48705870314
https://github.com/varnem2/cyberpunk/blob/master/.github/workflows/main1.yml
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing action.yml at lines 37-41, where the publish-spa checkout is configured, and compare it with the linked GitHub Actions issue. Reproduce the workflow with a Git LFS-tracked PDF over 100 MB. Done means the GitHub Pages deployment completes and the PDF is available at the expected page URL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100