Check when no package-level data is present and others

[tuxdna]

Carried forward from another issue: openshiftio/openshift.io#2047 (comment)

---

@tuxdna

package data (prod-bayesian-core-package-data) for a particular version is not present in S3 but package version does (prod-bayesian-core-data) have data in S3. For example there are 75 versions for arachne-ui but there is no package data present

I don't think that having no package-level data should be an issue for graph import. In case of arachne-ui, it looks like an error in ingestion pipeline, but in general, there can be components for which we simply won't have any package-level data.

Could you please check in data-importer, how it behaves when there are no package-level data? And file an issue, if it fails :) Thanks 😉

---

Adding more issues to investigate further:
openshiftio/openshift.io#2047 (comment)

---

The graph sync ran for few days now, and we have 92695 NPM package versions in the pending list. There are no more package-versions going through the sync anymore.

There are known reasons due to which this is happening

• package data (prod-bayesian-core-package-data) for a particular version is not present in S3 but package version does (prod-bayesian-core-data) have data in S3. For example there are 75 versions for arachne-ui but there is no package data present.
• there is no data at all in S3 for a particular package
• other reasons we haven't figured out yet.

Essentially for NPM, the graph-sync is done to the extent which it could be done in the current state.

---