Repository navigation
0.7.10: imported repos finish indexing; big imports go local - #7
Merged
Merged
Conversation
…ff, so imported repos stayed Pending); sources over 500 MB import from the owner's machine instead of the container. 0.7.10
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Imported repos stayed Pending. The import finish ran
finishImportRefsand only thenscheduleIndex, all insidewaitUntil. That work outlasts waitUntil's ~30s, so the index was never woken: import-probe4 still advertisesrefs/heads/import/pr/1and itsprepared_repository_refsrow stayspending=1. The index is now woken (a durable DO alarm) before the finishing work and again after it.Big repos. The import container is
basic(1 GiB memory, 4 GB disk). On create and on retry, the source's size is read from GitHub (size, KB) or GitLab (statistics.repository_size). Over 500 MB, the job is not dispatched to the container (the DO alarm is capped too) and its status says: "Too large to import on gild's servers (N GB). Import it from your machine: gild repo resume owner/name".gild repo importalready claims an unclaimed job and runs it locally, so no CLI release is needed. An unknown size (plain git, API failure) goes to the container as before.Evidence:
npm run typecheck0;npm test20/20 pass, including the newsrc/server/import/dispatch.test.ts(GitHub KB→bytes plus auth header, GitLab bytes, unknown → null).-claude