-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error "Space has no name" loading proof #1175
Comments
travis
added a commit
that referenced
this issue
Nov 21, 2023
@juliangruber reported an issue with our documented space creation flow when the exported space access delegation doesn't specify a name and the client doesn't specify one manually: #1175 I think it's reasonable to require a name for spaces at some level, but I think the access-client API is too low-level for this.
Thanks @juliangruber ! You've identified a bug we introduced late in the game - thanks! We need to confer as a team on how best to fix so it might take a couple days (especially on this holiday week) but you can track its progress here: #1177 |
alanshaw
pushed a commit
that referenced
this issue
Nov 22, 2023
@juliangruber reported an issue with our documented space creation flow when the exported space access delegation doesn't specify a name and the client doesn't specify one manually: #1175 I think it's reasonable to require a name for spaces at some level, but I think the access-client API is too low-level for this.
I can confirm this all works, after manually upgrading the |
gobengo
pushed a commit
that referenced
this issue
Nov 28, 2023
@juliangruber reported an issue with our documented space creation flow when the exported space access delegation doesn't specify a name and the client doesn't specify one manually: #1175 I think it's reasonable to require a name for spaces at some level, but I think the access-client API is too low-level for this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to follow https://web3.storage/docs/how-to/upload/ for setting up an agent with pkey and proof, to upload in a server environment where you can't do the email dance.
I'm getting this error:
I'm initializing the space like this:
I have created the pkey and proof like this:
The text was updated successfully, but these errors were encountered: