Resource map sometimes fails to render

[dmullen17]

Ran into an error where the resource map will sometimes fail to render data objects on a landing page. It sends two duplicate 404 error messages:

Failed to load resource: the server responded with a status of 404 (Not Found) https://arcticdata.io/metacat/d1/mn/v2/meta/urn%3Auuid%3Ae8e15e18-8607-45d0-89b1-7c0067b4ffe3

And one warning message:

DevTools failed to parse SourceMap: https://arcticdata.io/catalog/components/annotator/v1.2.10/annotator-full.map

[jagoldstein]

@dmullen17 what are the OS and browser versions?

[dmullen17]

Good catch @jagoldstein. MacOS Sierra 10.12.6 and Chrome 74.0.3729.108

[laurenwalker]

When I access the dataset linked in the screenshot above (which is https://arcticdata.io/catalog/view/urn:uuid:462974fb-7f5c-4d64-8012-aca1e38e297c), I get a 404 for this identifier instead:

https://arcticdata.io/metacat/d1/mn/v2/meta/urn%3Auuid%3A10bd6f78-67af-4a1a-9326-d75725af5287

It's odd that the same dataset has 404s for different ids, both of which are not ids of objects in the package. This seems to be the source of this intermittent rendering issue.

[csjx]

This looks like an issue with caching and rendering. When I reload the page, the package table items don't render (with caching enabled). When I open the inspector, and disable caching, each time I reload the page, all items render correctly. Needs a deeper look into what is causing this.

[robyngit]

@taojing2002 found a way to reproduce this issue pretty consistently:

• I have a private package on sfwmd (https://sfwmd.dataone.org/view/urn%3Auuid%3A370d07fd-8dbd-4328-a0f9-da0cb8674d5e)
• If I search the package by id, and click the the link, the landing page shows the full package with data objects, which is good.
• However, if copy the view package link and open it on another browser tab, it only shows the metadata without data objects. This tab still shows that I logged in.
• If I clear the cache files of the browser, and refresh the page, the data objects show up!

I was able to reproduce this, but I had to refresh a couple of times for the data objects to disappear. I also noticed that I got the This dataset is private error that should only show up if you don't have permission to view a package.

@jeanetteclark noted that the behaviour is very inconsistent, and it's unconfirmed f it only happens on private packages.

[robyngit]

We should see if this is still an issue and work on it if needed after the Folders in Datasets #1450 epic.

[robyngit]

@rushirajnenuji I'm adding this to the File Hierarchy Phase 2 project. I wonder if you've already fixed it with the work you've done so far? To be tested.