When subscribePeer runs, a remote peer PubSubPeer is created, but with the local peer pubsub.codecs instead of those from the remote one. The remote peer is added to the local peer's peers table. When handleConn executes - now with the right codec - the remote peer continues with the wrong codecs, as it's already present in the table and it isn't created again or modified.
When subscribePeer runs, a remote peer
PubSubPeeris created, but with the local peerpubsub.codecsinstead of those from the remote one. The remote peer is added to the local peer'speerstable. When handleConn executes - now with the right codec - the remote peer continues with the wrong codecs, as it's already present in the table and it isn't created again or modified.