GO-CAM browser stuck on "Loading Models ..."

[kimrutherford]

Hi.

The model browser here hasn't worked for me for a few days: https://geneontology.cloud/browse

It's stuck on "Loading Models ..." and there are many browser console errors like:

gocam <http://model.geneontology.org/5323da1800000002> does not seem to have GO-Terms

and

ERROR TypeError: n.forEach is not a function
    gpSub https://geneontology.cloud/main.55414a8b72e05ebac877.js:1
    __tryOrUnsub https://geneontology.cloud/main.55414a8b72e05ebac877.js:1

Tested on Chrome and Firefox on Linux and Edge on Windows.

[kltm]

@kimrutherford Yeah, I'm seeing this too. Hm.

@dustine32 @tmushayahama Would either of you have any idea what's going on here? I'd note that there is an off 403 error, but other things seem to be fine on the network. The JS error noted above is also odd--as the code has not changed (to my knowledge), that would seem like either a server issue (are there even any servers here?) or a data issue with the recent release. I'll take a look at the latter, but could one of you explore the former?

[kltm]

@dustine32 I'm also kinda wondering if there might have been a bootstrap issue? With the recent outages we've been having, if it tried to get data initial data on a restart/rebuild and nothing was there, could that have seeded an issue? I only mention this as that is the only real change we've had recently. (We did also have a release not too far back, but it was fairly by-the-book.)

[dustine32]

@kltm I'm suspecting it's due to the current contents of gocam-gps.json:

{"error":{"code":"ESOCKETTIMEDOUT","connect":false}}

This might be a fluke error from blazegraph when the file was generated. We could try rerunning the pipeline issue-265-go-cam-products branch to see if this see error happens again?

[kltm]

@dustine32 Cheers--re-running.

[kltm]

(@dustine32 And thank you! Great catch :)

[kltm]

@dustine32 and @kimrutherford The current files in http://skyhook.berkeleybop.org/issue-265-go-cam-products/products/api-static-files/ are looking hopeful. Pushing out to AWS now; should be out in just over an hour. Will check again then.

[kltm]

Thank you @dustine32--it looks like that did the trick.

@kimrutherford If you could confirm?

[kimrutherford]

That works now. Thanks for the quick fix!

[kltm]

Thank you for the head ups!