Sleep timers included due to Microsoft store not liking having pings sent too quickly. If there is no data for an app, and the script immediately goes to the next app, the MS store will throw an error and ask for the user to wait a few seconds before pinging again.
For some reason, the appchannel conversion link returns nulls in the date field as well as others. Python doesn't like that, so these nulls need to be turned into strings before processing can occur
Checklist for reviewer:
[ ] Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title).
[ ] If the PR comes from a fork, trigger integration CI tests by running the Push to upstream workflow and provide the <username>:<branch> of the fork as parameter. The parameter will also show up
in the logs of the manual-trigger-required-for-fork CI task together with more detailed instructions.
[ ] If adding a new field to a query, ensure that the schema and dependent downstream schemas have been updated.
[ ] When adding a new derived dataset, ensure that data is not available already (fully or partially) and recommend extending an existing dataset in favor of creating new ones. Data can be available in the bigquery-etl repository, looker-hub or in looker-spoke-default.
For modifications to schemas in restricted namespaces (see CODEOWNERS):
…cript to deal with null dates.
Sleep timers included due to Microsoft store not liking having pings sent too quickly. If there is no data for an app, and the script immediately goes to the next app, the MS store will throw an error and ask for the user to wait a few seconds before pinging again.
For some reason, the appchannel conversion link returns nulls in the date field as well as others. Python doesn't like that, so these nulls need to be turned into strings before processing can occur
Checklist for reviewer:
<username>:<branch>
of the fork as parameter. The parameter will also show up in the logs of themanual-trigger-required-for-fork
CI task together with more detailed instructions.For modifications to schemas in restricted namespaces (see
CODEOWNERS
):┆Issue is synchronized with this Jira Task