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

Prevent /Temp filling up with temporary files #451

Closed

Conversation

Gee-64
Copy link
Contributor

@Gee-64 Gee-64 commented Jan 4, 2025

Limits number of temporary files from the HTTP API as well as from the Assembly64 integration. House keeping retains at least 2 files, but may go up to 16 files or 1MB of total size, whichever is reached first. Older files are deleted before newer. The limits are counted separately for API files and Assemby64 files.

Temporary filenames were changed to have a slightly nicer (?) names and start numbering at 1 instead of 0 since this is (arguably) more intuitive to the user.

Also fixes a tiny typo in a comment.

This solves #435.

@Gee-64 Gee-64 force-pushed the feature/temp-files-house-keeping branch from 3227ad1 to 9e233b5 Compare January 4, 2025 22:59
Limits number of temporary files from the HTTP API as well as from the
Assembly64 integration. House keeping retains at least 2 files, but may go up
to 16 files or 1MB of total size, whichever is reached first. Older files are
deleted before newer. The limits are counted separately for API files and
Assemby64 files.

Temporary filenames were changed to have a slightly nicer (?) names and start
numbering at 1 instead of 0 since this is (arguably) more intuitive to the
user.

Also fixes a tiny typo in a comment.
@Gee-64 Gee-64 force-pushed the feature/temp-files-house-keeping branch from 9e233b5 to 0e09c79 Compare February 23, 2025 15:04
@Gee-64 Gee-64 changed the base branch from master to u64ii February 23, 2025 15:04
@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 23, 2025

Rebased on top of u64ii to once again test the build caching. @GideonZ

@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 23, 2025

Ah, but maybe you are right that it won't work though - the u64ii branch had a build when you merged master back into it... And the cache should have been seeded then.

@GideonZ
Copy link
Owner

GideonZ commented Feb 23, 2025

@Gee-64 I checked the caches. Same hash. I don't understand! Grrrrr.... You could check my build.yml if you like.

@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 23, 2025

@GideonZ Dang. I'll try and read up on GitHub Actions and have a look.

@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 23, 2025

@GideonZ Everything looks fine to me in build.yml. Even when taking into consideration the quite restrictive cache lookup rules enforced by GitHub, a PR branch should be able to restore files from the PRs "base branch" (i am assuming this would be u64ii in our case). The only thing I can think of to try would be to check if caching starts working when u64ii is merged into master (since the cache for the "default" branch should be available to all other branches). Alternatively temporarily making the u64ii branch the default branch.

@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 24, 2025

Moving future discussion of build cache back to #465.

@Gee-64 Gee-64 closed this Feb 24, 2025
@Gee-64 Gee-64 deleted the feature/temp-files-house-keeping branch February 24, 2025 10:10
@Gee-64 Gee-64 restored the feature/temp-files-house-keeping branch February 24, 2025 10:11
@Gee-64
Copy link
Contributor Author

Gee-64 commented Feb 24, 2025

Wups, accidentally deleted this branch while cleaning out stale branches. This PR was closed so will re-open a new one.

@Gee-64 Gee-64 deleted the feature/temp-files-house-keeping branch February 24, 2025 10:27
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 this pull request may close these issues.

2 participants