Skip to content
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

Improving error readability and handling returning infrastructure. #90

Open
blafry opened this issue Feb 5, 2025 · 0 comments
Open

Comments

@blafry
Copy link
Collaborator

blafry commented Feb 5, 2025

When attempting to connect the wormhole-client with a cleared storage to the wormhole-server, which contains information about the peer, it returns an error:

time="2025-02-05T12:28:08Z" level=error msg="attempted peering from peer pp-bench-t-uks: error, public key mismatch"

wormhole-client hang with the following log:

time="2025-02-05T12:28:08Z" level=info msg="Log level set to info"
time="2025-02-05T12:28:08Z" level=info msg="Starting prometheus metrics server on 0.0.0.0:8090"
time="2025-02-05T12:28:08Z" level=info msg="No cached pairing response found, pairing with server"

The log should be more readable, indicating the existence of an existing peer configuration on the wormhole-server side.

How else can this issue be resolved without deleting the peers.db file?

glothriel added a commit that referenced this issue Feb 7, 2025
glothriel added a commit that referenced this issue Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant