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

Getting a new identity every time I spacetime publish/call #333

Closed
jdetter opened this issue Sep 27, 2023 · 5 comments
Closed

Getting a new identity every time I spacetime publish/call #333

jdetter opened this issue Sep 27, 2023 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@jdetter
Copy link
Collaborator

jdetter commented Sep 27, 2023

image

@jdetter jdetter added the bug Something isn't working label Sep 27, 2023
@gefjon
Copy link
Contributor

gefjon commented Oct 2, 2023

As yet unable to reproduce. If anyone else runs into this, please save your ~/.spacetime/config.toml, and ideally the series of spacetime CLI invocations that got you to this point.

@jdetter
Copy link
Collaborator Author

jdetter commented Oct 26, 2023

I randomly get into this state from time to time, next time it happens I'll dump my config here

@kim
Copy link
Contributor

kim commented Apr 18, 2024

I can reproduce this by not having a default_identity for a server. Which I think I don't have because server add doesn't set it.

@kim
Copy link
Contributor

kim commented Apr 18, 2024

Sometimes it seems the fresh identity is then set as the default, but sometimes not.

Maybe we should just prompt to select an identity if it wasn't set as a default nor an argument?

kim added a commit that referenced this issue Apr 18, 2024
When a server key rotation is suspected, suggest to make the new
identity the default.

This usually happens during development using an ephemeral instance. If
one follows the instructions, the `default_identity` is not set for the
existing server, which makes the CLI generate a fresh identity every
time.

See also: #333
github-merge-queue bot pushed a commit that referenced this issue Apr 19, 2024
When a server key rotation is suspected, suggest to make the new
identity the default.

This usually happens during development using an ephemeral instance. If
one follows the instructions, the `default_identity` is not set for the
existing server, which makes the CLI generate a fresh identity every
time.

See also: #333
@gefjon
Copy link
Contributor

gefjon commented Jun 11, 2024

I suspect this is fixed by #1109 , #1196 and #1341 . Closing, but if it reappears we can reopen.

@gefjon gefjon closed this as completed Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants