Bugzilla

Last night's Airflow run failed again. The new Glean SDK release v33.6.0 resolved the timeout issue that we were seeing with v33.4.0, but Glean does not seem to upload pings to the data-platform. For example:

```sql
SELECT
  *
FROM
  `moz-fx-data-shared-prod.burnham_live.discovery_v1`
WHERE
  submission_timestamp BETWEEN TIMESTAMP_SUB("2020-12-03T00:00:49.693927+00:00", INTERVAL 1 HOUR)
  AND TIMESTAMP_ADD("2020-12-03T00:00:49.693927+00:00", INTERVAL 3 HOUR)
  AND metrics.uuid.test_run = "b5e185a8-00ba-4fd5-9d59-d457572b2485"
  AND metrics.string.test_name = "test_burnham"
```

This can be reproduced locally using the burnham `main` branch and running `docker-compose up --build`. The *fake-data--platform* service is programmed to log incoming requests from the burnham clients. Running burnham with v33.6.0 doesn't produce these log entries even though the client logs report that pings were submitted and will be sent as soon as possible.

Last night's Airflow run failed again. The new Glean SDK release v33.6.0 resolved the timeout issue that we were seeing with v33.4.0, but Glean does not seem to upload pings to the data-platform. For example:

```sql
SELECT
  *
FROM
  `moz-fx-data-shared-prod.burnham_live.discovery_v1`
WHERE
  submission_timestamp BETWEEN TIMESTAMP_SUB("2020-12-03T00:00:49.693927+00:00", INTERVAL 1 HOUR)
  AND TIMESTAMP_ADD("2020-12-03T00:00:49.693927+00:00", INTERVAL 3 HOUR)
  AND metrics.uuid.test_run = "b5e185a8-00ba-4fd5-9d59-d457572b2485"
  AND metrics.string.test_name = "test_burnham"
```

This can be reproduced locally using the burnham `main` branch and running `docker-compose up --build`. The **fake-data-platform** service is programmed to log incoming requests from the burnham clients. Running burnham with v33.6.0 doesn't produce these log entries even though the client logs report that pings were submitted and will be sent as soon as possible.