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
In addition, after contact with support, we just discovered how if we launch this command for the PRE tunnel:
run -c code/.sauce/config_local.yml --tunnel-name PRE --tunnel-owner srvcintqaops
It works too. But:
That's a change of behaviour respect two weeks ago.
That doesn't explain why the PRO tunnel doesn't need the flags but the PRE tunnel does.
Desired behavior
Config to reproduce
I need you to indicate what do you need for this, because is a pretty strange behaviour, first we should need an explanation about why two tunnels launched the same way require different flags to be used.
Versions
saucectl: 0.190.1
The text was updated successfully, but these errors were encountered:
Current behavior
We have right now two tunnels up and running: PRE and PRO.
Both tunnels are launched the same way by the same user, with the exact same configuration. And both tunnels are appearing as shared on the platform:
If we try the tunnels from our local environment, with this config:
And this command:
The results differ:
PRO works.
PRE doesn't work.
In addition, after contact with support, we just discovered how if we launch this command for the PRE tunnel:
It works too. But:
Desired behavior
Config to reproduce
I need you to indicate what do you need for this, because is a pretty strange behaviour, first we should need an explanation about why two tunnels launched the same way require different flags to be used.
Versions
saucectl: 0.190.1
The text was updated successfully, but these errors were encountered: