Use info-tester in Maestro GUI fetches - #6149
Merged
Merged
Conversation
Maestro already pointed Core at tester login/info/sync hosts; route GUI info-server requests the same way so builds stay off production.
j0ntz
approved these changes
Aug 11, 2026
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
2 participants
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.
Summary
fetchInfo/ info-server rollup requests throughinfo-tester.edge.appwhen Maestro (orENABLE_TEST_SERVERS) is enabledshouldUseTestServers()so Core and GUI stay alignedTest plan
ENABLE_MAESTRO_BUILD=trueand confirm GUI logs / network hits go toinfo-tester.edge.appinfo1/info2ENV.INFO_SERVERstill overrides when setMade with Cursor