Repository navigation
README: magmalake as the working example - #2
Merged
Merged
Conversation
The job and its place in the ci gate as zstd.mojo has them, and the two kinds of finding adding it turned up: postgres.mojo's connection/copy cycle, and parquet.mojo's imports through a shim, fixed by making the shim a package. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds an Example: magmalake section: the
customsjob and its place in thecigate, as merged in zstd.mojo, and the two kinds of finding adding it turned up: postgres.mojo#20's connection/copy cycle, and parquet.mojo#69's imports through a compatibility shim. Also rewraps one long line under Usage.🤖 Generated with Claude Code