{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenBazaar/openbazaar-go/issues/73","repository_url":"https://api.github.com/repos/OpenBazaar/openbazaar-go","labels_url":"https://api.github.com/repos/OpenBazaar/openbazaar-go/issues/73/labels{/name}","comments_url":"https://api.github.com/repos/OpenBazaar/openbazaar-go/issues/73/comments","events_url":"https://api.github.com/repos/OpenBazaar/openbazaar-go/issues/73/events","html_url":"https://github.com/OpenBazaar/openbazaar-go/issues/73","id":170228125,"number":73,"title":"Irregularly, but steadily getting IPNS pinned errors.","user":{"login":"rmisio","id":794517,"avatar_url":"https://avatars.githubusercontent.com/u/794517?v=3","gravatar_id":"","url":"https://api.github.com/users/rmisio","html_url":"https://github.com/rmisio","followers_url":"https://api.github.com/users/rmisio/followers","following_url":"https://api.github.com/users/rmisio/following{/other_user}","gists_url":"https://api.github.com/users/rmisio/gists{/gist_id}","starred_url":"https://api.github.com/users/rmisio/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rmisio/subscriptions","organizations_url":"https://api.github.com/users/rmisio/orgs","repos_url":"https://api.github.com/users/rmisio/repos","events_url":"https://api.github.com/users/rmisio/events{/privacy}","received_events_url":"https://api.github.com/users/rmisio/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-09T17:46:17Z","updated_at":"2016-08-09T17:46:17Z","closed_at":null,"body":"I don't know what the exact steps to reproduce are, because it doesn't always happen. But, it has been happening enough to multiple developers that I think it requires attention. Anyhow, often times, after wiping your data and starting with a fresh server, POSTs on the profile are failing with a 'not pinned' error:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/794517/17526879/fb587c1c-5e1d-11e6-996a-58fee60d4a83.png)\r\n\r\nThen, a subsequent fetch returns a 404, whereas a subsequent PUT fails with 'Profile already exists. Use PUT':\r\n\r\n![image](https://cloud.githubusercontent.com/assets/794517/17526912/1ea85cc8-5e1e-11e6-8f64-1c2b130e5d99.png)\r\n\r\nOnce again, i think the crux of the problem is that the Profile is 404ing, when the file does indeed exists. It shouldn't 404 in this case, otherwise the client has no reliable way of knowing whether to onboard or not and whether to save a profile via PUT or POST.\r\n"}}
{"actor":{"display_login":"rmisio"}}