chore: restore solana-tx-landing-latency (027) on dev after auto-sync deletion - #1386
Merged
Merged
Conversation
… deletion Bench was deleted from main via #1384 (never got prod data since 2026-07-03, duplicate of 016 solana-tx-landing). Auto-sync then removed it from dev too since dev hadn't modified the file — but intent was to keep on dev for staging validation of the active-probe design. Restored from 3b1d306 (last dev commit before the auto-sync deletion). Present on dev, absent on main — same pattern as solana-dex-quote-latency kept on dev-only via #300.
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.
Follow-up to #1384. Bench 027 was removed from main; auto-sync then dropped it from dev too. Restoring on dev so staging can still validate the active-probe design.
Same pattern as solana-dex-quote-latency kept on dev-only via #300.