-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ks-265 wrap local target in capability registry with transmission logic #13396
Conversation
44f6799
to
339b329
Compare
116aba1
to
e47e671
Compare
09f4fb6
to
4323490
Compare
4323490
to
51292df
Compare
dbe6559
to
1c588d6
Compare
} | ||
|
||
if opts.CapabilitiesRegistry == nil { | ||
peerID := externalPeerWrapper.GetPeer().ID() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't work. Peer is ready only after the wrapper is Start()-ed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PeerID is currently extracted from Keystore and that is not accessible until the services start.
return nil, fmt.Errorf("failed to create hardcoded Don network setup: %w", err) | ||
} | ||
|
||
if opts.CapabilitiesRegistry == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this ever be nil? Registry is created in shell.go.
See comments on #13396 Registry can't easily access PeerID when it is being created. This fix moves desired wrapping to the Engine.
See comments on #13396 Registry can't easily access PeerID when it is being created. This fix moves desired wrapping to the Engine.
No description provided.