Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sqlite3.OperationalError: database or disk is full #132

Open
Bouni opened this issue Jul 3, 2024 · 4 comments
Open

sqlite3.OperationalError: database or disk is full #132

Bouni opened this issue Jul 3, 2024 · 4 comments

Comments

@Bouni
Copy link

Bouni commented Jul 3, 2024

Hi,

I just realized that you encounter the exact same issue as I do with my KiCAD plugin as we use your cache.

https://github.com/yaqwsx/jlcparts/actions/runs/9771283483/job/26973813599#step:5:258

My guess is that the GH actions runners have disk that is now insufficient to store the database file ...

Do you have a plan on how to solve this?

I lack the time at the moment, but I would really like to build an API that serves JLC parts data, sanitized and usable.

@dougy83
Copy link
Contributor

dougy83 commented Jul 10, 2024

If you combine the multipart zip files into one file, you can mount the zip file using fuse-zip, and then use the mounted cache.sqlite3 as normal. The speed is pretty good too. E.g.

cat cache.z* > cache-combined-bad.zip
echo -e 'z\r\n' | zip -FF cache-combined-bad.zip -O cache-combined.zip
mkdir /tmp/cachezip
fuse-zip cache-combined.zip /tmp/cachezip
jlcparts buildtables --jobs 0 --ignoreoldstock 30 /tmp/cachezip/cache.sqlite3 web/build/data
fusermount -u /tmp/cachezip

@Bouni
Copy link
Author

Bouni commented Jul 12, 2024

I'll look into yor suggestion as soon as I have a bit of spare time 👍🏽

@ukd1 ukd1 mentioned this issue Jul 12, 2024
@yaqwsx
Copy link
Owner

yaqwsx commented Jul 23, 2024

As a quick work-around, I tried to save some space on the CI machine. At the moment, it has been working just fine for 4 days now so the problem is solved - at least for now. I like the proposal of @dougy83, and I will look into it in the future.

@dougy83
Copy link
Contributor

dougy83 commented Jul 26, 2024

@yaqwsx I've put the changes in PR #136 . I did mention that I came across write issues/corruption when using fuse-zip, but haven't been able to reproduce, and writing seems to work cleanly (not sure what I stuffed up before).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants