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

Networking Key not included in passport folder when custodying L2 Planet via Invite Flow #1010

Open
tacryt-socryp opened this issue Mar 25, 2022 · 14 comments
Assignees

Comments

@tacryt-socryp
Copy link

tacryt-socryp commented Mar 25, 2022

Only the master ticket and management proxy were included? Really messes with the user experience because then they have to go back through Bridge if they want to boot. @nerveharp

@ixv
Copy link

ixv commented Mar 25, 2022

To clarify, the bridge page for claiming a planet explicitly says a networking key was included in the zip file, but its not there

@jamesacklin
Copy link
Contributor

Obviously not the intended result. @tomholford take a look?

@tomholford
Copy link
Collaborator

Obviously not the intended result. @tomholford take a look?

On it

@tomholford
Copy link
Collaborator

@tacryt-socryp @ixv What login method and browser was used when generating the invites?

@ixv
Copy link

ixv commented Mar 25, 2022

We generated the invites ourselves in hoon. I don't think we messed anything up because we were able to log in with the master ticket that was generated.

@ixv
Copy link

ixv commented Mar 25, 2022

The code for it is here: https://github.com/tirrel-corp/studio/blob/master/app/shop.hoon#L156
We do a spawn, configure-keys, and then transfer-point

@tomholford
Copy link
Collaborator

@ixv Approximately how much time passed between the invite creation and activation? wondering if the roller had not yet processed the batch before the activation

@tacryt-socryp
Copy link
Author

#1023 is the same issue. @zalberico @lukestiles

@zalberico
Copy link
Contributor

Tagging @nerveharp about this and asking internally, thanks. Have you seen it happen again (tweet looks old, digging around see speculation about it being inconsistent/load related - trying to narrow down)

@tacryt-socryp
Copy link
Author

Yes, it happened to a user of https://planet.market today.

@lukestiles
Copy link

@tacryt-socryp does this eventually resolve?

@tacryt-socryp
Copy link
Author

No, this is not resolved. This is a major issue, as it really affects the user experience of people buying L2 planets via an activation ticket.

@langalisc
Copy link

This is still an issue- getting more inbound issues from it.

@pkova
Copy link
Contributor

pkova commented Aug 26, 2022

I am fairly confident that the issue is that /app/shop does not set the management proxy like Bridge does.

This is a planet that exhibits the issue, and this one does not. The only difference in azimuth state is the management proxy stuff which happens here. Someone should test out this theory, @ixv @tacryt-socryp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Ready
Development

No branches or pull requests

8 participants