You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's difficult to debug missing build information. There are multiple places where a failure results in the build information being missing from the frontend:
failure in receiving the SQS message
failure in reading the message or pulling the file from S3
failure in adding the build information to Postgres
failure in indexing into Elasticsearch
We should have easy-to-use tools to surface problems in any of these places given an S3 key or archive.mozilla.org url.
Also, it's not clear where build information came from. Was the build information captured through ingestion? Was it migrated from another source? Was it added by backfill? Fixing issue #545 might alleviate that--I don't know what that page was supposed to show.
The text was updated successfully, but these errors were encountered:
It's difficult to debug missing build information. There are multiple places where a failure results in the build information being missing from the frontend:
We should have easy-to-use tools to surface problems in any of these places given an S3 key or archive.mozilla.org url.
Also, it's not clear where build information came from. Was the build information captured through ingestion? Was it migrated from another source? Was it added by backfill? Fixing issue #545 might alleviate that--I don't know what that page was supposed to show.
The text was updated successfully, but these errors were encountered: