Closed andrewxhill closed 5 years ago
Are you registered with an older cafe? On Jun 26, 2019, 7:03 AM -0700, Andrew W. Hill notifications@github.com, wrote:
Using 0.5.0, I run, ` textile contacts search --name="multidaft" 404 page not found
increasing the
wait
doesn't help, it returns immediately — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
"cafe": {
"address": "P7kneNPCLSFFWeiDj69VvjqfZqC1ru8gU5tXm5bFneY4hxpM",
"api": "v0",
"node": "0.2.8",
"peer": "12D3KooWFrrmGJcQhE5h6VUvUEXdLH7gPKdWh2q4CEM62rFGcFpr",
"protocol": "/textile/cafe/1.0.0",
"url": "https://us-west-beta.textile.cafe"
},
just tried again and it's still same error
I see... it's hitting the v0 search because that's what the session is defining.
addr := fmt.Sprintf("%s/api/%s/search", session.Cafe.Url, session.Cafe.Api)
I didn't notice before because my tests all get a fresh session. v0 search is handled by the catch-all /service
endpoint. We can just redirect /v0/search
-> /v1/search
Using 0.5.0, I run,
increasing the
wait
doesn't help, it returns immediately