How to avoid `target registration (<target.ID>, <target.Type>) not accepted by server`

[yhzs8]

Version: v0.0.0-20220524190229-125331eabdde

I got this from time to time during the scenario:

• Targets are registered properly.
• The gRPC connection is broken
• The gRPC connection is restored
• Try to do tunnel.NewClient(), client.Register() and client.Start() immediately. (during tunnel.NewClient() I am sending in targets in ts map[Target]struct{} so they would be added to the server during client.Register())

Anything I can try to do before client.Register() and client.Start() to get rid of this error?

[yhzs8]

Update: I printed out the target.Error when the issue happens on this line and it seems the error is originated here

So I will try to remove the targets before adding them back again when the gRPC connection is restored.

[yhzs8]

Update: the proposal is not working, I did it in the following order:

1. tunnel.NewClient() with ts set to the targets
2. client.DeleteTarget() with those targets
3. client.Start()
4. blocking wait for client.Error()

for normal cases, step 2 would have failed (there is no target to delete) and it was picked up in 4 and cancelled my workflow. Since all target operations are asynchronous and there is no way to distinguish the error thrown at step 2 and 3 so I cannot swallow the error for step 2 only.

Next proposal: using unique target.ID for subsequent target registrations.