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
Currently there exists logic to prevent automatic stcpr transport creation to non-public visors - which may be overridden by the -f flag of skywire cli tp add
This logic is actually implemented incorrectly as it blocks creation of stcpr transports regardless of if the visor is public or not.
In the second place, it was the wrong choice to use the public visor service discovery to make this determination.
the address resolver should be used to predetermine what transport types may be created to remote visors. including sudph. And we should show an error message based on if the visor attempting to be transported is shown to be available for certain transport types.
the -f flag should force a transport creation attempt for certain types of transports.
The text was updated successfully, but these errors were encountered:
Currently there exists logic to prevent automatic stcpr transport creation to non-public visors - which may be overridden by the
-f
flag ofskywire cli tp add
This logic is actually implemented incorrectly as it blocks creation of stcpr transports regardless of if the visor is public or not.
In the second place, it was the wrong choice to use the public visor service discovery to make this determination.
the address resolver should be used to predetermine what transport types may be created to remote visors. including sudph. And we should show an error message based on if the visor attempting to be transported is shown to be available for certain transport types.
the -f flag should force a transport creation attempt for certain types of transports.
The text was updated successfully, but these errors were encountered: