You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is no longer true in recent versions of maestro. By default, maestro uses port 7001 as discussed here
If this change was intended, could the docs please be updated to reflect it?
I'm opening an issue rather than a simple PR to change "22087" to "7001" because it seems the reality is more complicated and nuanced than that. As discussed here, the new sharding execution logic means maestro could be running on any port in the range of (7001..7128). Given that complication, it is not clear to me how the docs should be updated to account for this.
I'd be happy to open a PR with my best attempt at updating the docs to reflect the current situation. But I wanted to open this issue first because perhaps the maintainers have some context or understanding that I am lacking.
Please let me know if you'd like me to submit a PR for this change!
Or if there is some nuance or context you can share to clarify the situation, that would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
The docs for Detect Maestro in your app state that iOS uses port
22087
This is no longer true in recent versions of maestro. By default, maestro uses port
7001
as discussed hereIf this change was intended, could the docs please be updated to reflect it?
I'm opening an issue rather than a simple PR to change "22087" to "7001" because it seems the reality is more complicated and nuanced than that. As discussed here, the new sharding execution logic means maestro could be running on any port in the range of
(7001..7128)
. Given that complication, it is not clear to me how the docs should be updated to account for this.I'd be happy to open a PR with my best attempt at updating the docs to reflect the current situation. But I wanted to open this issue first because perhaps the maintainers have some context or understanding that I am lacking.
Please let me know if you'd like me to submit a PR for this change!
Or if there is some nuance or context you can share to clarify the situation, that would be greatly appreciated.
The text was updated successfully, but these errors were encountered: