Repository navigation
Conversation
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
1 participant
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.
Bring the existing, separately reviewed-scope fix from moosetechnology#1149 into the deem0n fork. This uses the same existing commits; no upstream PR is modified.
The live SQL audit image already contains this fix. FAMIXNGSQL v3 must include it in its pinned dependencies to avoid reintroducing the original failure. The branch includes its regression tests; the combined release qualification loads and runs them alongside the new SQL tests.
Tracks deem0n/FAMIXNGSQL#24 and draft qualification deem0n/FAMIXNGSQL#32. Review/merge this independent fix before the combined pin is promoted. Upstream moosetechnology#1149 is already merged; this preserves its exact reviewed head (1ee38d7) in the currently older fork base. CI results will be attached to this head.