It's been long enough since I worked on the frontend code (well prior to the first gopherjs patch) that debugging this might take awhile, for me. No obvious errors in the console, so i suspect this is purely client-side. or maybe a data format change on the server coupled with lazy validation on the client. should throw an error to console if the data doesn't look right. Want to open an issue?
On Wed, Jan 17, 2018 at 6:31 AM, Eric Drechsel <[email protected]> wrote: > I fired up devcam server last night (for the first time in.. awhile, > let's say. #dayjob) and also noticed that the detail aspects don't load > when you click on a permanode in the default "recent changes" view. *Poking > around in the browser inspector* > > On Wed, Jan 17, 2018 at 5:17 AM, Attila Tajti <[email protected]> > wrote: > >> Something is still broken. SHA1 blobs are missing and don't seem to work >> at all. I've tried >> >> cd perkeep.org >> git co -b old 504604e22dcbeb86a597b4a75992f34157701673 <(415)%20770-1673> >> rm -rf tmp && go run make.go >> devcam server >> devcam put file ... # upload random photos, output: >> # sha1-66bfc81fd2440d6b0f78d27fd76a84867673d0bf >> # sha1-e1f3812bc9fa79aca71b9d5311c2955b6a277b8a >> # sha1-8345ec627a4661a26c6398e7547bc0035c25a84d >> # ... >> ^C >> git co master >> rm -rf tmp && go run make.go >> devcam server >> >> >> The old blobs don't seem to work >> >> $ devcam tool describe sha1-66bfc81fd2440d6b0f78d27fd76a84867673d0bf >> { >> "meta": { >> "sha1-66bfc81fd2440d6b0f78d27fd76a84867673d0bf": { >> "blobRef": "sha1-66bfc81fd2440d6b0f78d27fd76a84867673d0bf", >> "camliType": "permanode", >> "size": 615, >> "permanode": { >> "attr": {}, >> "modtime": "0001-01-01T00:00:00Z" >> } >> } >> } >> } >> $ devcam tool claims sha1-66bfc81fd2440d6b0f78d27fd76a84867673d0bf >> { >> "claims": null >> } >> $ devcam tool describe sha1-e1f3812bc9fa79aca71b9d5311c2955b6a277b8a >> { >> "meta": { >> "sha1-e1f3812bc9fa79aca71b9d5311c2955b6a277b8a": { >> "blobRef": "sha1-e1f3812bc9fa79aca71b9d5311c2955b6a277b8a", >> "camliType": "claim", >> "size": 740 >> } >> } >> } >> $ devcam tool describe sha1-8345ec627a4661a26c6398e7547bc0035c25a84d >> { >> "meta": { >> "sha1-8345ec627a4661a26c6398e7547bc0035c25a84d": { >> "blobRef": "sha1-8345ec627a4661a26c6398e7547bc0035c25a84d", >> "camliType": "file", >> "size": 1456, >> "file": { >> "fileName": "DSC00700.JPG", >> "size": 7656409, >> "mimeType": "image/jpeg", >> "time": "2017-08-22T08:05:26Z", >> "modTime": "2017-08-22T08:05:27Z", >> "wholeRef": "sha1-c1eebf4f9fd7bb1ec786d625079954c48b494838" >> }, >> "image": { >> "width": 5472, >> "height": 3648 >> } >> } >> } >> } >> >> >> >> On Wednesday, January 17, 2018 at 12:57:43 PM UTC+1, Attila Tajti wrote: >>> >>> I've noticed the Web UI doesn't work with sha224 blobs properly. >>> >>> Clicking the refs doesn't show anything, it changes window.location only. >>> >>> The changes in my CL[1] seemed to fix this issue for me, but I haven't >>> checked it with both sha1 and sha224 blobs yet. >>> >>> [1] https://camlistore-review.googlesource.com/c/camlistore/+/13566 >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Camlistore" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > best, Eric > eric.pdxhub.org <http://pdxhub.org/people/eric> > > -- best, Eric eric.pdxhub.org <http://pdxhub.org/people/eric> -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
