Data Sync User
Data Sync User
[https://sql.telemetry.mozilla.org/queries/97053/source](https://sql.telemetry.mozilla.org/queries/97053/source) fenix is still hitting fxa quite a bit (I assume token server directs every query there)I think the reason desktop and iOS aren’t in that list is [https://github.com/mozilla/bigquery-etl/blob/db15c215868a76e7e41a843ece6ee1fa63954[…](https://github.com/mozilla/bigquery-etl/blob/db15c215868a76e7e41a843ece6ee1fa63954[…)ared-prod/firefox_accounts_derived/fxa_auth_events_v1/query.sql|https://github.com/mozilla/bigquery-etl/blob/db15c215868a76e7e41a843ece6ee1fa639541ec/sql/moz-fx-data-shared-prod/firefox_accounts_derived/fxa_auth_events_v1/query.sql#L55-L59] filtering...
Due to the age of the code and a number of other reasons, we often “hand craft” datetime and duration values as integers or strings instead of using well-known constants...
The “meta” collection (6) is a server readable field. It records all collections that a user may be storing on sync. The `modified` field indicates the last time that the...
The GCP implementations we use for Bigtable and Sync storage are using older protobuf versions. While there’s no problem with this right now, it does limit us to older libraries...
As we add datastores to syncstorage, we should make the DSN parse errors more consistent. Right now, we display `Spanner or SQLite database_url specified for MySQL feature, please correct.` or...
[Google has announced a price increase](https://cloud.google.com/sql/pricing#extended-support-pricing) for any service still using MySQL 5. We should migrate Tokenserver DB to 8.4.4 which is the current LTS. The price increase is scheduled...
We were holding off on updating to diesel 2.2 due to some complications, when outside contributor `tommie` provided this update as part of [https://github.com/mozilla-services/syncstorage-rs/pull/1644](https://github.com/mozilla-services/syncstorage-rs/pull/1644|smart-link) . Since there was a `cargo...
[https://sql.telemetry.mozilla.org/dashboard/sync-backend-dau?p_end date=2024-12-30&p_start date=2024-12-27](https://sql.telemetry.mozilla.org/dashboard/sync-backend-dau?p_end%20date=2024-12-30&p_start%20date=2024-12-27) shows we’re not receiving individual `hashed_device_id`s in our glean metrics: a `COUNT(DISTINCT metrics.string.)` shows the exact same count for both `syncstorage_hashed_fxa_uid` and `syncstorage_hashed_device_id` whereas there should be...
Followup to [https://mozilla-hub.atlassian.net/browse/SYNC-4475](https://mozilla-hub.atlassian.net/browse/SYNC-4475|smart-link) The `SeqCst` ordering doesn’t solve that original issue, let’s revert it and more simply guard against such underflows ┆Issue is synchronized with this [Jira Bug](https://mozilla-hub.atlassian.net/browse/SYNC-4642)
(From the original [https://github.com/mozilla-services/syncstorage-rs/issues/1031](https://github.com/mozilla-services/syncstorage-rs/issues/1031|smart-link)) Sentry event: [https://mozilla.sentry.io/issues/4700544013/events/c91e25b686d449a890b2efb951113200/](https://mozilla.sentry.io/issues/4700544013/events/c91e25b686d449a890b2efb951113200/) "A database error occurred: RpcFailure: 3-INVALID_ARGUMENT The transaction exceeds the maximum total bytes-size that can be handled by Spanner. Please reduce the size...