Bump date-fns from 3.6.0 to 4.1.0 in /frontends/admin-panel#110
Open
dependabot[bot] wants to merge 10000 commits intomainfrom
Open
Bump date-fns from 3.6.0 to 4.1.0 in /frontends/admin-panel#110dependabot[bot] wants to merge 10000 commits intomainfrom
dependabot[bot] wants to merge 10000 commits intomainfrom
Conversation
…ecidiviz/recidiviz-data#33319) ## Description of the change Moves all code in `recidiviz/pipelines/normalization/utils/normalization_managers/` to new package `recidiviz/pipelines/ingest/state/normalization/normalization_managers/` in preparation for fully deleting the `recidiviz/pipelines/normalization/` once we've shipped normalization in ingest. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 755e8a8ce99c5c21cda96b2dae871d9fbdd0a00c
## Description of the change - Log GcsfsFilePath abs_path string instead of object - Select only relevant column for validations - Don't validate datetime columns can cast to datetime type. BQ can only parse datetimes that are in ISO format, which may not always be the format of the date. - Add additional info to egt_person yaml for validations testing ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#29135 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 29d60bb5c031c2492c74356a2a2d991053d0d394
…iviz-data#33434) ## Description of the change When switching to `docker buildx build` in Cloud Build, the `/app` workdir was chowned to `root`, but the app ran under the `node` user. This restores the permissions generated by `docker build` by chowning the directory. <img width="530" alt="Screenshot 2024-09-17 at 1 40 10 PM" src="https://github.com/user-attachments/assets/7df8b94d-c48c-400e-8623-051dd587c70f"> <img width="972" alt="Screenshot 2024-09-17 at 1 39 53 PM" src="https://github.com/user-attachments/assets/1948b5a3-833d-49a9-9ed8-215af1abb4a1"> ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33375 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b1356fd82b63fa90975ef44f49b96aa58e6322e4
…ata (Recidiviz/recidiviz-data#33353) ## Description of the change Following location metadata changes in Recidiviz/recidiviz-data#31706, this PR updates the county backup jail criteria query to reference the `location_subtype` codes `B8` and `BC`. Changes to the query result in a present-day list of 2464 people, which is about what we were seing before the changes in the `location_metadata` view. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: e2ab99d438bba48ee1e462a8eff12db11048d206
…diviz-data#33331) ## Description of the change Updates downstream processes to read from the results of the combined ingest and normalization pipelines in prod. With this change, all states will be fully launched on the combined pipelines and we can start deleting the legacy pipelines! I will merge this once testing from this week's prod deploy looks good and release this to prod via a cherry-pick so we don't spend a whole week running double pipelines unnecessarily. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 1680d5fce957e8f0e239c06e0ea711b56f6e637a
…ecidiviz/recidiviz-data#33332) ## Description of the change Deletes the `should_run_normalization_in_ingest()` feature gate (assume value is True), which controls whether we output normalized entities from the ingest pipeline to `us_xx_normalized_state_new`. As part of this change, remove the `--run_normalization_override` flag from ingest pipelines. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 937f66f617e4833c88d9dfaf2cb1a7e9f9a9e5a7
…ecidiviz-data#33247) Bumps [zod](https://github.com/colinhacks/zod) from 3.22.4 to 3.23.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/colinhacks/zod/releases">zod's releases</a>.</em></p> <blockquote> <h2>v3.23.8</h2> <h2>Commits:</h2> <ul> <li>0f4d403558ae0490c711e4c2bfcf6c200bd14e11 Add Bronze logos (<a href="https://redirect.github.com/colinhacks/zod/issues/3470">Recidiviz/recidiviz-data#3470</a>)</li> <li>19687315b5b24bbd1ff6c346bfc2975700221748 Tweak tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3471">Recidiviz/recidiviz-data#3471</a>)</li> <li>eda7df314399929f7ed737423868a5a0780cd944 Change RefinementCtx to interface</li> <li>ca42965df46b2f7e2747db29c40a26bcb32a51d5 v3.23.8</li> </ul> <h2>v3.23.7</h2> <h2>Commits:</h2> <ul> <li>29d2ea2a15f0b1ac4b89138041f786a3dafc490b Add copper</li> <li>d969423266fccee56ef769da6744cc8bacb04550 Fix <a href="https://redirect.github.com/colinhacks/zod/issues/3437">Recidiviz/recidiviz-data#3437</a>: extendShape erases JSDoc property documentation (<a href="https://redirect.github.com/colinhacks/zod/issues/3463">Recidiviz/recidiviz-data#3463</a>)</li> <li>2239ff3ccc9af4d28bee27bd6fb2a5632844480b Add social crow</li> <li>f985b5b922cb357dbf4b25bb43814d19f838e046 3.23.7</li> </ul> <h2>v3.23.6</h2> <h2>Commits:</h2> <ul> <li>bc0095aab9e7254deb18701adc63de128ca2c742 Test on latest node</li> <li>6e5699a30373cc22879f2bcb6902fc138518c980 Lint on latest node</li> <li>1f466d9d00f446d7bed1962990e7a1ce813ab0d4 describe how one can protect from cyclical objects starting an infini… (<a href="https://redirect.github.com/colinhacks/zod/issues/3447">Recidiviz/recidiviz-data#3447</a>)</li> <li>3fed6f21e0ea7adc91aa0cc44f75bcf4e526d98e Add zod playground link (<a href="https://redirect.github.com/colinhacks/zod/issues/3454">Recidiviz/recidiviz-data#3454</a>)</li> <li>04e1f379f6989d23dd45660fcabc78f76d7834f8 Fixed freezing async ZodReadonly results (<a href="https://redirect.github.com/colinhacks/zod/issues/3457">Recidiviz/recidiviz-data#3457</a>)</li> <li>b87e59d0e4bbb4403bf27243afdcda9fcdeec258 Update sponsor tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3453">Recidiviz/recidiviz-data#3453</a>)</li> <li>143886151bba3930bdcc10d34a1cff4bf9103ba8 Add copper tier (<a href="https://redirect.github.com/colinhacks/zod/issues/3460">Recidiviz/recidiviz-data#3460</a>)</li> <li>ce3711e1384952d255769b9495f9bfadfb327291 add VSCode dev container support and documenation</li> <li>93b480b12ec3466cbd3b4182f7ce292e5c61528c v3.23.6</li> </ul> <h2>v3.23.5</h2> <h2>Commits:</h2> <ul> <li>110b8211f991b3e060ab2da4fec7b63d600439ad Update README_ZH.md (<a href="https://redirect.github.com/colinhacks/zod/issues/3433">Recidiviz/recidiviz-data#3433</a>)</li> <li>c1910bdfc98709b8f14231e2cefc5a3be401e3ee Made ZodEnum take readonly string array (<a href="https://redirect.github.com/colinhacks/zod/issues/3444">Recidiviz/recidiviz-data#3444</a>)</li> <li>541a862e978f96eb391849a6bf16be84231aa1b3 3.23.5</li> </ul> <h2>v3.23.4</h2> <h2>Commits:</h2> <ul> <li>157b18d742c86d85b26a8421af46ad6d6d6b6ea7 Add 3.23 announcement</li> <li>aedf93f1435a29463d915c3be45b4dcbeefa8cc1 Revert change to default Input</li> <li>45107f7a7230fe48ee24dc37e621422c9dc64ec4 v3.23.4</li> </ul> <h2>v3.23.3</h2> <h2>Commits:</h2> <ul> <li>103d2436f85872ca0e0e6247652989cc93d46a39 3.23.3</li> </ul> <h2>v3.23.2</h2> <h2>Commits:</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/colinhacks/zod/commit/ca42965df46b2f7e2747db29c40a26bcb32a51d5"><code>ca42965</code></a> v3.23.8</li> <li><a href="https://github.com/colinhacks/zod/commit/eda7df314399929f7ed737423868a5a0780cd944"><code>eda7df3</code></a> Change RefinementCtx to interface</li> <li><a href="https://github.com/colinhacks/zod/commit/19687315b5b24bbd1ff6c346bfc2975700221748"><code>1968731</code></a> Tweak tiers (<a href="https://redirect.github.com/colinhacks/zod/issues/3471">Recidiviz/recidiviz-data#3471</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/0f4d403558ae0490c711e4c2bfcf6c200bd14e11"><code>0f4d403</code></a> Add Bronze logos (<a href="https://redirect.github.com/colinhacks/zod/issues/3470">Recidiviz/recidiviz-data#3470</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/f985b5b922cb357dbf4b25bb43814d19f838e046"><code>f985b5b</code></a> 3.23.7</li> <li><a href="https://github.com/colinhacks/zod/commit/2239ff3ccc9af4d28bee27bd6fb2a5632844480b"><code>2239ff3</code></a> Add social crow</li> <li><a href="https://github.com/colinhacks/zod/commit/d969423266fccee56ef769da6744cc8bacb04550"><code>d969423</code></a> Fix <a href="https://redirect.github.com/colinhacks/zod/issues/3437">Recidiviz/recidiviz-data#3437</a>: extendShape erases JSDoc property documentation (<a href="https://redirect.github.com/colinhacks/zod/issues/3463">Recidiviz/recidiviz-data#3463</a>)</li> <li><a href="https://github.com/colinhacks/zod/commit/29d2ea2a15f0b1ac4b89138041f786a3dafc490b"><code>29d2ea2</code></a> Add copper</li> <li><a href="https://github.com/colinhacks/zod/commit/93b480b12ec3466cbd3b4182f7ce292e5c61528c"><code>93b480b</code></a> v3.23.6</li> <li><a href="https://github.com/colinhacks/zod/commit/ce3711e1384952d255769b9495f9bfadfb327291"><code>ce3711e</code></a> add VSCode dev container support and documenation</li> <li>Additional commits viewable in <a href="https://github.com/colinhacks/zod/compare/v3.22.4...v3.23.8">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: eac652ecbd7a81feada099d13eafbe34c1a7f901
…types/prototype-app (Recidiviz/recidiviz-data#33253) Bumps @recidiviz/design-system from 4.2.0 to 5.7.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 3fd79fbadd1a7dc145f1e71418734fa2a9ba6d9d
…recidiviz-data#33442) Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 4.5.3 to 4.5.5. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vitejs/vite/blob/v4.5.5/packages/vite/CHANGELOG.md">vite's changelog</a>.</em></p> <blockquote> <h2><!-- raw HTML omitted -->4.5.5 (2024-09-16)<!-- raw HTML omitted --></h2> <h2><!-- raw HTML omitted -->4.5.4 (2024-09-16)<!-- raw HTML omitted --></h2> <ul> <li>fix: avoid DOM Clobbering gadget in <code>getRelativeUrlFromDocument</code> (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/18115">Recidiviz/recidiviz-data#18115</a>) (<a href="https://github.com/vitejs/vite/commit/e812716">e812716</a>), closes <a href="https://redirect.github.com/vitejs/vite/issues/18115">Recidiviz/recidiviz-data#18115</a></li> <li>fix: backport <a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/18112">Recidiviz/recidiviz-data#18112</a>, fs raw query (<a href="https://github.com/vitejs/vite/commit/b901438">b901438</a>), closes <a href="https://redirect.github.com/vitejs/vite/issues/18112">Recidiviz/recidiviz-data#18112</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vitejs/vite/commit/f1d8845fff4842c3a0fec69309d9475c12c30cd9"><code>f1d8845</code></a> release: v4.5.5</li> <li><a href="https://github.com/vitejs/vite/commit/2466c0862587c1beb4171daa02d8a541a8be18f6"><code>2466c08</code></a> release: v4.5.4</li> <li><a href="https://github.com/vitejs/vite/commit/e8127166979e7ace6eeaa2c3b733c8994caa31f3"><code>e812716</code></a> fix: avoid DOM Clobbering gadget in <code>getRelativeUrlFromDocument</code> (<a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/18115">Recidiviz/recidiviz-data#18115</a>)</li> <li><a href="https://github.com/vitejs/vite/commit/b901438f99e667f76662840826eec91c8ab3b3e7"><code>b901438</code></a> fix: backport <a href="https://github.com/vitejs/vite/tree/HEAD/packages/vite/issues/18112">Recidiviz/recidiviz-data#18112</a>, fs raw query</li> <li>See full diff in <a href="https://github.com/vitejs/vite/commits/v4.5.5/packages/vite">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/Recidiviz/recidiviz-data/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: 91b51951f63e86604b7d788ada0c5a1d129bffb8
…() feature gate (Recidiviz/recidiviz-data#33333) ## Description of the change Deletes the `is_combined_ingest_and_normalization_launched_in_env()` feature gate (assume value is True), which controls whether downstream processes read from legacy normalization pipelines vs new combined pipelines and whether we run a legacy normalization pipeline at all. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: e02f1c7cf2220eae822ca7c5a45e837071c5028d
…-panel (Recidiviz/recidiviz-data#33246) [//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps @recidiviz/design-system from 2.7.0 to 5.7.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: f2819cc06132c066a1a723589dc08bd47b02864c
…iz-data#33335) ## Description of the change Deletes the legacy normalization pipeline as well all other unused code in the `recidiviz.pipelines.normalization.comprehensive_normalization` package. Updates existing scripts to drop support for running legacy normalization pipelines. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 Closes Recidiviz/recidiviz-data#21376 Closes Recidiviz/recidiviz-data#21119 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: e7233941f08229d155f9efc54a930b1b006a4c58
…iviz/recidiviz-data#33248) Bumps [http-status](https://github.com/adaltas/node-http-status) from 1.7.3 to 1.7.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/adaltas/node-http-status/blob/master/CHANGELOG.md">http-status's changelog</a>.</em></p> <blockquote> <h3><a href="https://github.com/adaltas/node-http-status/compare/v1.7.3...v1.7.4">1.7.4</a> (2024-02-23)</h3> <h3>Bug Fixes</h3> <ul> <li><strong>types:</strong> improve TypeScript strict typing for numeric keys in HttpStatus (<a href="https://redirect.github.com/adaltas/node-http-status/issues/49">Recidiviz/recidiviz-data#49</a>) (<a href="https://github.com/adaltas/node-http-status/commit/4945afdc1f8aaba59fbc95983e7a2934238dab24">4945afd</a>), closes <a href="https://redirect.github.com/adaltas/node-http-status/issues/48">Recidiviz/recidiviz-data#48</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/adaltas/node-http-status/commit/9213069396ca33bd2c9c7ec0537c7cfb456a685e"><code>9213069</code></a> chore(release): 1.7.4</li> <li><a href="https://github.com/adaltas/node-http-status/commit/c8c2ac2c437bca9530dfc1c9a27c4fad7c98f769"><code>c8c2ac2</code></a> chore: add keywords</li> <li><a href="https://github.com/adaltas/node-http-status/commit/1a6f797f1979ce13e3bfb808e469b92f64808497"><code>1a6f797</code></a> ci: improve build vs publish workflow</li> <li><a href="https://github.com/adaltas/node-http-status/commit/a6dfa51668969989dae73836488dc137d9f7aeed"><code>a6dfa51</code></a> build: build and check git working tree before release</li> <li><a href="https://github.com/adaltas/node-http-status/commit/4945afdc1f8aaba59fbc95983e7a2934238dab24"><code>4945afd</code></a> fix(types): improve TypeScript strict typing for numeric keys in HttpStatus (...</li> <li>See full diff in <a href="https://github.com/adaltas/node-http-status/compare/v1.7.3...v1.7.4">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Dana Hoffman <1130694+danawillow@users.noreply.github.com> GitOrigin-RevId: ee5023ee74e22487ebf799025e47529f4d6ff8f8
…nes (Recidiviz/recidiviz-data#33337) ## Description of the change Deletes the source table collections for `us_xx_normalized_state` datasets. Once these datasets have been fully deleted, a follow-up PR will rename the `us_xx_normalized_state_new` datasets back to `us_xx_normalized_state`. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: bd9c254539ba0d0956f3ae480c2ccd47a57e3b27
…recidiviz-data#33382) ## Description of the change Deletes a number of util functions that are unused now that we've deleted the normalization pipeline. Adds the new `get_bq_schema_for_entity_table` util function as a convenience so it was easier to delete `bq_schema_for_normalized_state_association_table`. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: feb29ac2c26afcb4861aa1e5c0f94188f8d3abe9
Recidiviz/recidiviz-data#33396) ## Description of the change Moves the `normalized_state_dataset_for_state_code_ingest_pipeline_output` helper to the ingest pipelines package and renames it to `normalized_state_dataset_for_state_code`. Also moves the `normalized_entity_conversion_utils.py` file to the ingest pipeline package. With this change, the `recidiviz.pipelines.normalization` and `recidiviz.tests.pipelines.normalization` pipelines are fully deleted! ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 22bf7cbaa948e719044292298e4494a5e18890c3
…pplemental pipelines (Recidiviz/recidiviz-data#33399) ## Description of the change Updates so that all the metric and supplemental Dataflow pipelines read from the appropriate `us_xx_normalized_state_new` dataset, rather than `normalized_state`. This will allow us to update orchestration in a separate PR to run post-ingest pipelines directly after ingest pipelines without waiting for the `update_normalized_state` step. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#29518 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 35eff026424b0be9eaa0796800b7a7ced12cd83c
…viz-data#33419) ## Description of the change A user of the AR/CLD tool flagged that the incident type on TOMIS was different from what we surfaced in the tool. We discovered that there is also an infraction type and when this is different from Incident type it should be the one displayed. Because the process is not always straightforward in TN we are ingesting as metadata instead of in place of the incident type so we can have all the pieces to trace any mismatches in the future. successful ingest pipeline here: https://console.cloud.google.com/dataflow/jobs/us-west1/2024-09-17_12_17_51-6209966970692137745?authuser=0&organizationId=448885369991&project=recidiviz-staging ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33211 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 66818e60c7bdf0e21d01d312dcd5114c3492bf99
…loyers (Recidiviz/recidiviz-data#33424) ## Description of the change To support Recidiviz/recidiviz-dashboards#6330, pull the employment status into the client record. I discovered that we were missing employer names for some of the employers on the client record during the ClientRecord transformation to Zod. This led to an investigation that we have some employment periods that aren't necessarily "employed" periods, so we should show different copy based on the status of the period. Loaded with prefix `alexa_` ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-dashboards#6330 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: e6ccc9235a17d9b80a9592bb8c46b4fd22a4ac34
…viz/recidiviz-data#33291) ## Description of the change i had `NewFlashChecklistStore` implement `Hydratable` (a concept borrowed from polaris which i really liked) and simplifies a lot of the possibly undefined conditional logic. thank you anna for the suggested conditional logic refactor, made things 100x easier creates `DagFlashDatabaseChecklist.tsx` and adds the logic conditional to tell us if we can start flashing (i based this on the only ingest instance status logic), which is this conditional ``` !this.isFlashInProgress && this.currentRawFileProcessingStatus.hasProcessedFilesInSecondary() && !this.currentRawFileProcessingStatus.hasUnprocessedFilesInSecondary() && this.currentStaleSecondaryStatus.length === 0 ``` which translates to: - we are not currently flashing - we have a non-zero number files that have been successfully processed in secondary - we have no un-processed files in secondary - we have no "stale" secondary files, which is defined as: - there exist non-invalidated files that have been added to PRIMARY after the timestamp of the the earliest non-invalidated discovery time in SECONDARY - One or more of those files does not exist in SECONDARY ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Prework for Recidiviz/recidiviz-data#33150 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: eee895bbfde82b549c93e58ce4065a4ed6c1ad97
…testing (Recidiviz/recidiviz-data#33438) ## Description of the change Ungate IA secondary for testing ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#29135 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 6bf046dd0f9b37e797d8b20c05a593e3c38260ac
…le_historical_raw_data_counts_validation` exclusions (Recidiviz/recidiviz-data#33440) `##` Description of the change Adding `RECIDIVIZ_REFERENCE_community_opportunities` in `stable_historical_raw_data_counts_validation` exclusions This file is manually maintained for the PSI project, and large changes should be expected occasionally ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33274 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 7901e5387cb7ec2017bf7c1199571e90da108663
…n pipelines (Recidiviz/recidiviz-data#33398) ## Description of the change Renames everything `ingest_and_normalization*` to just `ingest` and anything `post_normalization*` to `post_ingest*`. When this deploys in each respective project, all open PagerDuty incidents that referenced the old task naming will have a new version reopened with the new naming. I'll do my best to manage closing out the old incidents when this happens. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29517 Part of Recidiviz/recidiviz-data#31741 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 6e98117e8c8cb3ca038e6bcffc81cd1d003551a8
…z-data#33310) ## Description of the change per anna's wonderful suggestion on slack, adds a single `CannotFlashDecisionComponent` that displays all the requirements that are not currently met to flash. here's a video walkthrough of some of those cases: https://github.com/user-attachments/assets/3e8052e9-879b-46d3-a9fd-1101b57ae8e1 ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#33150 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 003048de55f7e7a453b6b7297e5743b849380552
Recidiviz/recidiviz-data#33428) ## Description of the change Updates the `UnionAllBigQueryViewBuilder` to allow for UNION ALL views to query a collection of source tables instead of a collection of views. This will allow us to build `UnionAllBigQueryViewBuilder` views that generate the `state` and `normalized_state` datasets by unioning together `us_xx_state` and `us_xx_normalized_state_new` datasets. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#29515 Part of Recidiviz/recidiviz-data#29519 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 1123838f43025ca1bb0c43ac1bbf6a9dec41346e
…ata#33439) ## Description of the change ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 1822ef6ba5cecbb366daed40427b06a9eafb85fa
…iviz-data#33436) ## Description of the change Add a README to the prototypes project. GitOrigin-RevId: ee8f55e383b698c3a2af8b967cdeb14970fafc0a
…data#33346) ## Description of the change Adds `NewReimportCancelChecklist`. Here's a video of me clicking through the checklist twice -- - first time through: we have processed files so we go to the flash decision checklist - acquire resource locks! - clear secondary data - we do NOT release resource locks - when we click "return to decision", we reset our store that forces a re-fetch of all data - second time through: since we don't have processed files in secondary, we dont go to the flash decision checklist but can still cancel reimport - you'll notice the "acquire" resource locks button is not active since they are not free - we do release resource locks https://github.com/user-attachments/assets/7006bcf3-bd7e-4ff4-89a9-2e69d03e32ac ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#33150 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 64b864739a8df4665b2bf9e7892201dbee5f257f
## Description of the change
I realized we had some bugs in our logic for several criteria. These
could be summarized into two:
- We had this where clause: `start_date != end_date`. This dropped all
NULL end_dates, which was an unintended consequence.
- We had two issues in ND ATP: we weren't parsing dates in the right way
(since the raw data contains at least two different ways to store the
date). We fix that here.
I uploaded this into sandbox (under `hsalas`) and we do observe some
changes in eligibility. I checked them all and they are all expected.
```
python -m recidiviz.tools.load_views_to_sandbox \
--project_id recidiviz-staging\
--sandbox_dataset_prefix hsalas manual \
--dataset_ids_to_load task_eligibility_criteria_us_nd,task_eligibility_criteria_us_me,task_eligibility_criteria_us_ix,task_eligibility_spans_us_me,task_eligibility_spans_us_ix,task_eligibility_spans_us_nd,task_eligibility\
--update_descendants False
```
- The decrease in `TRANSFER_TO_MINIMUM_FACILITY_FORM` is all expected
since it's coming from us capturing referrals better.
- The increase in `TRANSFER_TO_ATP_FORM` is due to the
parole_review_dates we are now able to parse.
## Checklists
### Development
**This box MUST be checked by the submitter prior to merging**:
- [ ] **Double- and triple-checked that there is no Personally
Identifiable Information (PII) being mistakenly added in this pull
request**
These boxes should be checked by the submitter prior to merging:
- [ ] Tests have been written to cover the code changed/added as part of
this pull request
### Code review
These boxes should be checked by reviewers prior to merging:
- [ ] This pull request has a descriptive title and information useful
to a reviewer
- [ ] Potential security implications or infrastructural changes have
been considered, if relevant
GitOrigin-RevId: a1a78f8b752dbb61adcbefeacc7c73fb6ee96e6c
…iviz-data#33463) ## Description of the change didn't realize that the legacy checklist also used `FlashReadyDecisionComponent` which I added to have the `FlashDecisionCriteria` component. This PR just creates `LegacyFlashReadyDecisionComponent` to use in the legacy flashing checklist so we don't erroneously display the `FlashDecisionCriteria` component at the top of the legacy flashing checklist ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#33150 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 03662d7ed018d14c95b7ffbcd14dc510bf7e1256
…PD (Recidiviz/recidiviz-data#33930) ## Description of the change Adds an enum mapping for the PVPD admission reason to address this [error](Recidiviz/recidiviz-data#33914). ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Followup work: Recidiviz/recidiviz-data#33927 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 396a86a43736cf99f5824c6831f101c575182748
…/recidiviz-data#33899) ## Description of the change In re-import US_IA we encountered a case where we were failing import because a file contained ascii 0 ``` Error while reading data, error message: Bad character (ASCII 0) encountered.; line_number: 320424 byte_offset_to_start_of_line: 19827747 column_index: 5 column_name: "Suffix" column_type: STRING value: "\000\000" File: gs://recidiviz-staging-direct-ingest-state-us-ia-secondary/unprocessed_2024-09-12T16:55:53:674392_raw_IA_DOC_Names.csv ``` in the primary table the value was just imported as null. Since ascii is a subset of utf-8, we want to be able to load ascii into BQ without doing any normalization of the csv data, so we should preserve the ascii characters on import, then translate any values containing only ascii control characters to nulls in the transformation step. `singlePrimaryKey_input.csv` is showing as a binary file now but its the same as before with the addition of `\000\000,\n` ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33847 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: fad40c2d7dfaf18b2fb7589d02f93f8687889dd3
## Description of the change Adding plotting functions 1. Added a function called `plot_settings()` that helps us add details to our plots: titles, subtitles, y and x labels, max and min values (set to 0 as default) for the y axis, remove gridlines if needed, make x ticks be integer values only 2. Modified `add_legend()` so that it adds a legend to the plot with the option to customize the title, location, and labels. It automatically formats Here's an example use case: <img width="1608" alt="Screenshot 2024-09-20 at 3 24 43 PM" src="https://github.com/user-attachments/assets/1bb3dd5c-c039-4667-b9d1-4f55b5511a7b"> 3. Changed some of our default settings in `recidiviz.mplstyle`. The most relevant change is that I made the default chart a big smaller than it was (50% its original size). This can always be adjusted back to it's original size if we run `adjust_plot_scale(scale_factor=2.)`. This is what we agreed on our slack channel. 4. Modified `adjust_plot_scale()` so it always starts from the defaults set in `recidiviz.mplstyle`. ## Related issues Closes Recidiviz/recidiviz-data#26997 Closes Recidiviz/recidiviz-data#32747 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 15f994e1dea6223205111ec83c8313dd2af15d2f
## Description of the change This PR refactors the `state_task_deadline` ingest view query to simplify the entity for use in AZ DTP/TPR workflows. ### The current needs for this entity are: - The earliest possible release date on TPR or DTP for people who have been approved or tentatively approved for the program. These dates are stored in ACIS, not calculated by Recidiviz. - A way to differentiate between DTP and TPR release dates. - A ledger of changes to these dates over time for each person. ### This refactored view accomplishes those goals by: - Stores the documented DTP or TPR release date for each person in the `state_task_deadline.eligible_date` field. - Differentiates between dates for each of the two opportunities by setting `task_subtype = 'DRUG TRANSITION_RELEASE'` or `task_subtype = 'STANDARD TRANSITION RELEASE'` where applicable. - Tracks changes to release dates for either opportunity over time. - Stores a number of useful fields in `task_metadata`: - The first two concatenated components of an incarceration period external ID in AZ are `PERSON_ID-DOC_ID`. `DOC_ID` is included in `task_metadata` to be able to link to incarceration periods if needed. - `sentence_external_id` is the ID of the sentence that controls the incarceration stint (i.e. determines the release dates) - `sentence_group_external_id` is the ID of the sentence group that each row relates to. ### Other improvements made in this PR: - Combines DTP and TPR task deadline ingest views into one. - Adds a unit test to make sure that deduplication is happening as expected. Tests: - [x] run_mappings script passes - [x] ingest view query is deterministic - [x] sandbox ingest [pipeline](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-10-02_14_36_11-12102292123861520701;graphView=1?project=recidiviz-staging&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22))) succeeds - [x] there are `eligible_date` values in the future - [x] I confirmed that people with `eligible_date` values in the past either appear overdue in ACIS or have been released to supervision. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 4cc2211acb7ee878520397f3b950b28054d1eb2e
… full list (Recidiviz/recidiviz-data#33949) ## Description of the change The output was getting impossible to read! See latest post in #jc-tech-chat for what it looks like now. Also I was wrong, @nichelle-hall , this does not show agencies with 0 users! It shows users with 0 agencies, haha. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [X] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 31abfddc704fbb59b708815e7a7c1c09abaf38f2
…ted_spreadsheet_json` (Recidiviz/recidiviz-data#33936) ## Description of the change Matt encountered [a timeout issue](https://recidiviz.slack.com/archives/C04JL8A2ADB/p1727975782009529), reporting: "After I drop the file, it spins for a couple of minutes and then eventually errors out back to the bulk upload screen with no specific error message." I was able to replicate the issue locally. The upload timed out with the large file (1.6MB), but it successfully uploaded after splitting it into smaller sections. Upon checking the logs, I found `ERROR:root:('Connection aborted.', TimeoutError('The write operation timed out'))` in `SpreadsheetInterface.save_ingested_spreadsheet_json`. I experimented with different timeout durations, starting at 5 minutes (no success), then 10 minutes, also without success. Finally, at a 30-minute timeout, the bulk upload completed without errors. This PR implements that change. ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 2f7d9dc3534034ca52b62770a22bdcdd9214b5ec
…-data#33805) ## Description of the change This PR adds a missing metric column error by making sure we determine if a sheet is in the single page upload format if it has a metric, breakdown, or breakdown_category columns. Also FWIW @morden35 mentioned this edge case in a previous playtesting and I forgot to address it!! <img width="1668" alt="Screenshot 2024-09-30 at 3 52 27 PM" src="https://github.com/user-attachments/assets/968accc1-a989-4cfa-9235-8fdd29bbf5b9"> ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 162295a053a17bd98f6158b5538ff91f2f499f75
…ema (Recidiviz/recidiviz-data#33928) ## Description of the change This PR moves `agency_settings` from the Agency to the Source table in the database. Agency is an abstraction of Source, so the tables are the same. Because of this, when I ran pipenv run migrate-jc, the migration file came up empty. Why is this necessary? I’ll be manually creating sources to backfill reporting_agency for new agency dashboards. These sources won't be agencies; they’ll be vendors or CSG. To support this, I need to add a "homepage URL" setting for these sources, which requires moving agency_settings to Source. ## Related issues Recidiviz/recidiviz-data#33842 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: d4a90a3302bce602fb69ad7c881a2c8ba8e0d36f
…viz-data#33918) ## Description of the change Michigan added two columns to the `ADH_SHPERSON` raw data table on 10/3/24. Since we infer columns from raw data configs in MI, it is unclear what the columns were that they added. This PR adds two new columns `Unknown1` and `Unknown2` to the raw data config so that this file can successfully import. I tested import in a sandbox to view the file contents (`elise_us_mi_raw_data.ADH_SHPERSON`). The two new columns are always empty. Based on a search of MI raw data uses, it seems like the only fields we use from this file are `RecID` and `IsDeleted`, both of which appear unimpacted by this change. Those fields are used in ingest while hydrating assessments, so if anything happens to assessments once this newly-structured file is imported, we should investigate this table. Once @brendali121 is back or I find out who our current data contact is in MI, we should ask what these added columns were and rename the columns in this config to reflect the actual structure of the file. I made a ticket to do this at [Recidiviz/recidiviz-data#33917](Recidiviz/recidiviz-data#33917). ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33915 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 8ea78fdc85496b198aede0c9556732a614bbb594
…idiviz/recidiviz-data#33911) ## Description of the change Change opportunity names to match TES structure proposal. [Please see our diagram for more informations.](https://docs.google.com/presentation/d/1sv9YIc5bYpaC0JCiFHzaA8m1HF8UfEs-gWZgPG7Oyas/edit#slide=id.g2f922d8d846_0_0). I did not make any changes to the contents of the files. ``` python -m recidiviz.tools.load_views_to_sandbox \ --project_id recidiviz-staging\ --sandbox_dataset_prefix hsalas manual \ --dataset_ids_to_load task_eligibility_criteria_us_az,task_eligibility_spans_us_az,workflows_views\ --update_descendants False ``` ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 704070da5c9237e0b33f03c9138232e5a20835f2
## Description of the change I created two new TES with their respective `workflows_views` tables based on [our trusty diagram](https://docs.google.com/presentation/d/1sv9YIc5bYpaC0JCiFHzaA8m1HF8UfEs-gWZgPG7Oyas/edit#slide=id.g2f922d8d846_0_0). We still have to validate many of these numbers, but at least this could unblock Polaris work. - `overdue_for_acis_dtp_request`: this looks at people who are past their DTP date. We flag as almost eligible those who are within 6 months of such date. I created a `workflows_views` table called `overdue_for_acis_dtp_request_record` that pulls only eligible folks. - `overdue_for_acis_tpr_request`: this looks at people who are past their TPR date. We flag as almost eligible those who are within 6 months of such date. To not double count folks who are eligible for both, in this TES we screen out people who are also eligible for DTP release in the following six months. In other words, when eligible for both, we prioritize remove you from the TPR request and only surface you as DTP. I created a `workflows_views` table called `overdue_for_acis_tpr_request_record` that pulls only eligible folks. ### Sanity checking a. Number of people eligible for both opportunities: <img width="397" alt="Screenshot 2024-10-02 at 1 07 58 PM" src="https://github.com/user-attachments/assets/e8eb0c54-061d-48cc-8151-ad35fe488059"> ``` SELECT "OVERDUE_FOR_TPR" AS type, COUNT(*) AS count, FROM hsalas_task_eligibility_spans_us_az.overdue_for_acis_tpr_request_materialized WHERE is_eligible AND CURRENT_DATE BETWEEN start_date AND IFNULL(end_date, '9999-12-31') UNION ALL SELECT "OVERDUE_FOR_DTP" AS type, COUNT(*) AS count, FROM hsalas_task_eligibility_spans_us_az.overdue_for_acis_dtp_request_materialized WHERE is_eligible AND CURRENT_DATE BETWEEN start_date AND IFNULL(end_date, '9999-12-31') ``` b. Clients eligible and almost eligible are mutually exclusive between groups: ``` SELECT person_id, COUNT(*) AS count FROM ( SELECT *, FROM hsalas_task_eligibility_spans_us_az.overdue_for_acis_tpr_request_materialized WHERE (is_eligible OR is_almost_eligible) AND CURRENT_DATE BETWEEN start_date AND IFNULL(DATE_SUB(end_date, INTERVAL 1 DAY), '9999-12-31') UNION ALL SELECT *, FROM hsalas_task_eligibility_spans_us_az.overdue_for_acis_dtp_request_materialized WHERE (is_eligible OR is_almost_eligible) AND CURRENT_DATE BETWEEN start_date AND IFNULL(DATE_SUB(end_date, INTERVAL 1 DAY), '9999-12-31') ) GROUP BY 1 HAVING count != 1 ``` c. I uploaded it all into a sandbox (under `hsalas`) ``` python -m recidiviz.tools.load_views_to_sandbox \ --project_id recidiviz-staging\ --sandbox_dataset_prefix hsalas manual \ --dataset_ids_to_load task_eligibility_criteria_us_az,task_eligibility_spans_us_az,workflows_views,task_eligibility,validation_views\ --update_descendants False ``` ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 0f128ac7906b8d127f959504e6a8310c270ddf1e
…diviz/recidiviz-data#33948) ## Description of the change Ungate MO and PA secondary so we can begin testing there. Will ungate IA primary after [ecosystem updates](Recidiviz/recidiviz-data#29058) are complete ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#29135 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 8f82d818d82340587dd0552c30e339dc994a0f69
…viz-data#33959) ## Description of the change https://recidiviz.slack.com/archives/C028X32LRH7/p1728051312141939 ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 84709a33fb6ea3a2c63815799116a465c9e06c58
…sfer_to_minimum_facility (Recidiviz/recidiviz-data#33351) ## Description of the change Our name for this completion event has caused confusions at many levels, so we thought it was a good time to change it's name to make it clearer. By changing it to `transfer_to_minimum_facility` it both reflects what it's capturing for both ID (transfer to CRC without work-release) and ND (transfer to a minimum security facility). ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: e923321ee57266755ec2a34f649bcdb169cff239
…g sequencing (Recidiviz/recidiviz-data#33852) ## Description of the change in this PR, i made a few updates to the sequencing and behavior of raw data import DAG; - if a failure occurs during resource locks acquisition, we skip all downstream tasks - if we fail to acquire to resource locks because they are already held, we skip all downstream tasks but DONT fail -- in cases like colorado where we want the infra to be always paused or want to prevent import runs on purpose by holding onto a manual lock that overlaps with an import (like raw data pruning), we dont want to fail loudly. if this is unintended (we held on to a lock by accident), stale raw data validation should be a backstop. i also finally got rid of manually raising `AirflowSkipExceptions` which i am happy about -- i feel they make it quite difficult to introspect about things by just reading the DAG. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33849 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: ba43785cae82497c877b0163221857c301953b51
… consolidate blocking (Recidiviz/recidiviz-data#33893) ## Description of the change first a few (i think three) PRs to update to operations registration logic to make it handle more edge cases. this PR handles: - a common case that i previously missed: if a file has already been imported (i.e. has `file_processed_time`) we shouldnt re-import it (folks should have to deprecate the file). technically we wouldnt be duplicating data if we didnt do this since in the load step we delete data w/ the same `file_id` - validate that all of the chunks exist for chunked files that have already been grouped in the past and have failed ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Part of Recidiviz/recidiviz-data#33879 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 66c98fb863d2ccb09e5fada8cc66af2dc46b9b34
…d experiment environments (Recidiviz/recidiviz-data#33854) ## Description of the change Adds the necessary monitoring for alerting on experiment composer environments that may no longer be in use ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#28606 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 2423dc0e064b2fe166a0d59e52bca9da3088867a
… functions (Recidiviz/recidiviz-data#33881) ## Description of the change Updates our source table logic to require that callers are explicit about which project we're collecting source tables for, since the list of source tables differs slightly between projects. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Addresses some PR feedback from Recidiviz/recidiviz-data#33866 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: 8ece0540ce38c16832af71f31db2a84e33fcc68a
…iz-data#33957) ## Description of the change Some opportunity config fields depend on dict key order, but by default Flask sorts keys in response objects to improve cacheability. I have a more permanent fix scoped in Recidiviz/recidiviz-data#33956, but there are too many moving parts to shoot for today's RC. For this next week we can temporarily disable the sorting behavior. It's apparently only possible to do this for the entire server at once, but it's unlikely that we're relying on the sorting behavior elsewhere. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: b95d821709a5f3e8d8aaa6cbae3e3cde00497bc0
) ## Description of the change I added content to the following criteria which only had stubs: - `US_AZ_NO_DANGEROUS_CRIMES_AGAINST_CHILDREN_CONVICTION`. I also changed the name of this criteria so it matches the naming convention of other criteria with similar logic. I created some new criteria to replace old ones that weren't doing exactly what we wanted. I spoke to Shalin and these changes seem to be what we needed to be accurate. Specifically, the following list of criteria are used to take into account all prior convictions instead of just current ones: - `US_AZ_NO_VIOLENT_CONVICTION` - `US_AZ_NO_ARSON_CONVICTION` - `US_AZ_NO_SEXUAL_OFFENSE_CONVICTION` - `US_AZ_NO_VIOLENT_CONVICTION_UNLESS_ASSAULT_OR_AGGRAVATED_ASSAULT_OR_ROBBERY_CONVICTION`: this will replace the OR criteria group we had. It's a bit simpler and it covers edge cases the previous one did not cover. ### Sanity checking I uploaded it all into sandbox (under _hsalas) and got the following results: - These are the number of eligible people and how it all changes with our new changes. The DTP population increased: <img width="786" alt="Screenshot 2024-10-03 at 5 00 17 PM" src="https://github.com/user-attachments/assets/9aedcac2-82a9-47c6-a273-8255bcff0c27"> - These people became eligible after meeting their mandatory literacy, which is not being changed in this PR, which is good <img width="771" alt="Screenshot 2024-10-03 at 5 02 14 PM" src="https://github.com/user-attachments/assets/78fa4d85-6587-4a73-990f-fff67c5dd935"> ``` python -m recidiviz.tools.load_views_to_sandbox \ --sandbox_dataset_prefix hsalas auto \ --load_up_to_addresses task_eligibility.all_criteria,task_eligibility.all_tasks ``` ## Related issues Closes Recidiviz/recidiviz-data#33380 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: fba9e62432cdd2db453e18f02c48068936a8f841
…iews_to_sandbox (Recidiviz/recidiviz-data#33866) ## Description of the change Adds support for running `load_views_to_sandbox` with a collection of input source table overrides, so that we can load views on top of the output of sandbox pipeline runs. Tested on top of a set of sandbox datasets with the following commands: ``` python -m recidiviz.tools.load_views_to_sandbox \ --sandbox_dataset_prefix ageiduschek_for_aaron \ --input_source_table_dataset_overrides_json "{\"us_me_normalized_state\": \"zaaron_td_with_401_us_me_normalized_state\", \"dataflow_metrics\": \"zaaron_td_with_401_dataflow_metrics\"}" \ --prompt auto \ --load_changed_views_only ``` ^ This loads just the views in `normalized_state` and `dataflow_metrics_materialized` ``` python -m recidiviz.tools.load_views_to_sandbox \ --sandbox_dataset_prefix ageiduschek_for_aaron \ --input_source_table_dataset_overrides_json "{\"us_me_normalized_state\": \"zaaron_td_with_401_us_me_normalized_state\", \"dataflow_metrics\": \"zaaron_td_with_401_dataflow_metrics\"}" \ --prompt auto \ --load_up_to_datasets task_eligibility_spans_us_me \ --load_up_to_addresses workflows_views.client_record ``` ^ This loads a bunch of datasets, up to and including `client_record` ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes Recidiviz/recidiviz-data#33733 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [x] This pull request has a descriptive title and information useful to a reviewer - [x] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: bc713c0bfe422f96812eca7a5e01c9ed3e4770a0
…a#33950) ## Description of the change Update Pipfile alias commands to use docker compose v2 syntax. I was running into the following error while trying to run the local version of our JC backend using `pipenv run docker-jc` and somehow remembered that we are now using docker compose v2 Recidiviz-wide:  Things ran again for me using the alias w/ this update. Reference: https://docs.docker.com/compose/releases/migrate/#what-are-the-differences-between-compose-v1-and-compose-v2 ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Closes #XXXX ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant Co-authored-by: Mahmoud <mahmoud@Mahmouds-MacBook-Pro.local> GitOrigin-RevId: d19931fc22d5b5618fe4d0ea1317a1f89ad55809
…Recidiviz/recidiviz-data#33960) ## Description of the change I made the secondary text in our plots a bit lighter than black to follow Ian's suggestion. Specifically, the following objects will now be grey as default: - Axis labels - Axis ticks - Subtitles ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [ ] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [ ] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant GitOrigin-RevId: f2d5b936639ec0480fc1307134e57f6159f72155
…cidiviz/recidiviz-data#33929)
## Description of the change
This PR creates a view of all projected dates for an inferred group,
which combines data from the aggregated sentence projected dates and
aggregated sentence group projected dates for inferred groups.
The big thing to review here is the final test case dealing with
suspended sentences. If we have a critical date where all sentences are
suspended in a group BUT the state has provided a group level date then
I've elected to take that date. Let me know if you'd like different
logic!
## Type of change
> All pull requests must have at least one of the following labels
applied (otherwise the PR will fail):
| Label | Description |
|-----------------------------
|-----------------------------------------------------------------------------------------------------------
|
| Type: Bug | non-breaking change that fixes an issue |
| Type: Feature | non-breaking change that adds functionality |
| Type: Breaking Change | fix or feature that would cause existing
functionality to not work as expected |
| Type: Non-breaking refactor | change addresses some tech debt item or
prepares for a later change, but does not change functionality |
| Type: Configuration Change | adjusts configuration to achieve some end
related to functionality, development, performance, or security |
| Type: Dependency Upgrade | upgrades a project dependency - these
changes are not included in release notes |
## Related issues
Closes Recidiviz/recidiviz-data#33499
## Checklists
### Development
**This box MUST be checked by the submitter prior to merging**:
- [ ] **Double- and triple-checked that there is no Personally
Identifiable Information (PII) being mistakenly added in this pull
request**
These boxes should be checked by the submitter prior to merging:
- [ ] Tests have been written to cover the code changed/added as part of
this pull request
### Code review
These boxes should be checked by reviewers prior to merging:
- [ ] This pull request has a descriptive title and information useful
to a reviewer
- [ ] Potential security implications or infrastructural changes have
been considered, if relevant
GitOrigin-RevId: 28a96215e54da47b8ed9e10d13a3023e163c7243
…z-data#33978) ## Description of the change All K8s Airflow tasks started failing upon deployment of Recidiviz/recidiviz-data#33854 as the `google-cloud-orchestration-airflow` package was not installed in the image. This moves it from `dev-packages` to `packages` and adds a test to the Docker workflow to verify that it runs successfully. ## Type of change > All pull requests must have at least one of the following labels applied (otherwise the PR will fail): | Label | Description | |----------------------------- |----------------------------------------------------------------------------------------------------------- | | Type: Bug | non-breaking change that fixes an issue | | Type: Feature | non-breaking change that adds functionality | | Type: Breaking Change | fix or feature that would cause existing functionality to not work as expected | | Type: Non-breaking refactor | change addresses some tech debt item or prepares for a later change, but does not change functionality | | Type: Configuration Change | adjusts configuration to achieve some end related to functionality, development, performance, or security | | Type: Dependency Upgrade | upgrades a project dependency - these changes are not included in release notes | ## Related issues Recidiviz/recidiviz-data#33854 ## Checklists ### Development **This box MUST be checked by the submitter prior to merging**: - [x] **Double- and triple-checked that there is no Personally Identifiable Information (PII) being mistakenly added in this pull request** These boxes should be checked by the submitter prior to merging: - [x] Tests have been written to cover the code changed/added as part of this pull request ### Code review These boxes should be checked by reviewers prior to merging: - [ ] This pull request has a descriptive title and information useful to a reviewer - [ ] Potential security implications or infrastructural changes have been considered, if relevant --------- Co-authored-by: Helper Bot <helperbot@recidiviz.org> GitOrigin-RevId: fe9be45beaa5269c211d64dc6a34e2c40d9b97ed
…ecidiviz/recidiviz-data#33986) Bumps [moment-timezone](https://github.com/moment/moment-timezone) from 0.5.45 to 0.5.46. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/moment/moment-timezone/releases">moment-timezone's releases</a>.</em></p> <blockquote> <h2>Release 0.5.46</h2> <ul> <li>Updated data to IANA TZDB <code>2024b</code>. This only affects historical timestamps; no future timestamps have changed.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/moment/moment-timezone/blob/develop/changelog.md">moment-timezone's changelog</a>.</em></p> <blockquote> <h3><code>0.5.46</code> <em>2024-10-06</em></h3> <ul> <li>Updated data to IANA TZDB <code>2024b</code>. This only affects historical timestamps; no future timestamps have changed.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/moment/moment-timezone/commit/4b7ce20307ca9eb083ec1a63812f352ee52a1e0b"><code>4b7ce20</code></a> Build moment-timezone 0.5.46</li> <li><a href="https://github.com/moment/moment-timezone/commit/64a0288c5afe01b410e19a0e0153912e8b9b2a79"><code>64a0288</code></a> Bump version to 0.5.46</li> <li><a href="https://github.com/moment/moment-timezone/commit/d5f3c707cd95d42cb5b68956314ddf9896ce6461"><code>d5f3c70</code></a> Merge pull request <a href="https://redirect.github.com/moment/moment-timezone/issues/1121">Recidiviz/recidiviz-data#1121</a> from moment/automated/data-update</li> <li><a href="https://github.com/moment/moment-timezone/commit/1c6b26d8ee4081290c27aacc543c896b8efeed20"><code>1c6b26d</code></a> ci: Allow tests to be run manually on a branch</li> <li><a href="https://github.com/moment/moment-timezone/commit/5086b536c1f0601109e2dde281c7a647b333b831"><code>5086b53</code></a> Fix MET guess test for new data</li> <li><a href="https://github.com/moment/moment-timezone/commit/f51dc2eadb1e047115b07f331dd0f2bcf9933217"><code>f51dc2e</code></a> data: Add 2024b</li> <li><a href="https://github.com/moment/moment-timezone/commit/1deeb203691d48918c20623cfafec30c4ced2f89"><code>1deeb20</code></a> ci: Allow data update PRs to be created with failing tests</li> <li><a href="https://github.com/moment/moment-timezone/commit/db8f1658749e3d7c4b00a5c327211c7798996d1e"><code>db8f165</code></a> build(deps-dev): bump braces from 3.0.2 to 3.0.3 (<a href="https://redirect.github.com/moment/moment-timezone/issues/1109">Recidiviz/recidiviz-data#1109</a>)</li> <li><a href="https://github.com/moment/moment-timezone/commit/543eb57034ae3ced00b129971e9338603f7c02b0"><code>543eb57</code></a> Merge pull request <a href="https://redirect.github.com/moment/moment-timezone/issues/1105">Recidiviz/recidiviz-data#1105</a> from moment/dependabot/npm_and_yarn/ejs-3.1.10</li> <li><a href="https://github.com/moment/moment-timezone/commit/eac2df340b90fc457dd5b142b77ffa538863c9ff"><code>eac2df3</code></a> build(deps-dev): bump ejs from 3.1.9 to 3.1.10</li> <li>See full diff in <a href="https://github.com/moment/moment-timezone/compare/0.5.45...0.5.46">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: ab8eb64257a1d9ca2003ec6f9584b77964ad9235
…z/recidiviz-data#33988) Bumps [antd](https://github.com/ant-design/ant-design) from 4.24.15 to 4.24.16. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ant-design/ant-design/releases">antd's releases</a>.</em></p> <blockquote> <h2>4.24.16</h2> <ul> <li>🐞 Fix Select that scrollbar is not displayed when there are few options. <a href="https://redirect.github.com/ant-design/ant-design/pull/47050">Recidiviz/recidiviz-data#47050</a></li> <li>🐞 Fix Transfer cannot invert current page correctly. <a href="https://redirect.github.com/ant-design/ant-design/pull/47134">Recidiviz/recidiviz-data#47134</a> <a href="https://github.com/linxianxi"><code>@linxianxi</code></a></li> <li>🐞 Fix that clicking Form tooltip icon should not trigger Switch. <a href="https://redirect.github.com/ant-design/ant-design/pull/46159">Recidiviz/recidiviz-data#46159</a> <a href="https://github.com/Wxh16144"><code>@Wxh16144</code></a></li> <li>🐞 Fix Segmented <code>options</code> className being overrided by <code>className</code>. <a href="https://redirect.github.com/react-component/segmented/pull/175/">rc-segmentedRecidiviz/recidiviz-data#175</a> <a href="https://github.com/stoil-terziev"><code>@stoil-terziev</code></a></li> </ul> <hr /> <ul> <li>🐞 修复 Select 组件在选项较少时不显示滚动条的问题。<a href="https://redirect.github.com/ant-design/ant-design/pull/47050">Recidiviz/recidiviz-data#47050</a></li> <li>🐞 修复 Transfer 反选当页错误的问题。<a href="https://redirect.github.com/ant-design/ant-design/pull/47134">Recidiviz/recidiviz-data#47134</a> <a href="https://github.com/linxianxi"><code>@linxianxi</code></a></li> <li>🐞 修复点击 Form <code>tooltip</code> 图标会触发 Switch 切换的问题。<a href="https://redirect.github.com/ant-design/ant-design/pull/46159">Recidiviz/recidiviz-data#46159</a> <a href="https://github.com/Wxh16144"><code>@Wxh16144</code></a></li> <li>🐞 修复 Segmented <code>options</code> 内 <code>className</code> 会覆盖组件自带 <code>className</code> 的问题。<a href="https://redirect.github.com/react-component/segmented/pull/175/">rc-segmentedRecidiviz/recidiviz-data#175</a> <a href="https://github.com/stoil-terziev"><code>@stoil-terziev</code></a></li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ant-design/ant-design/blob/4.24.16/CHANGELOG.en-US.md">antd's changelog</a>.</em></p> <blockquote> <h2>4.24.16</h2> <p><code>2024-03-18</code></p> <ul> <li>🐞 Fix Select that scrollbar is not displayed when there are few options. <a href="https://redirect.github.com/ant-design/ant-design/pull/47050">Recidiviz/recidiviz-data#47050</a></li> <li>🐞 Fix Transfer cannot invert current page correctly. <a href="https://redirect.github.com/ant-design/ant-design/pull/47134">Recidiviz/recidiviz-data#47134</a> <a href="https://github.com/linxianxi"><code>@linxianxi</code></a></li> <li>🐞 Fix that clicking Form tooltip icon should not trigger Switch. <a href="https://redirect.github.com/ant-design/ant-design/pull/46159">Recidiviz/recidiviz-data#46159</a> <a href="https://github.com/Wxh16144"><code>@Wxh16144</code></a></li> <li>🐞 Fix Segmented <code>options</code> className being overrided by <code>className</code>. <a href="https://redirect.github.com/react-component/segmented/pull/175/">rc-segmentedRecidiviz/recidiviz-data#175</a> <a href="https://github.com/stoil-terziev"><code>@stoil-terziev</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ant-design/ant-design/commit/7c060247516925f48175d7f29cd43b626632665e"><code>7c06024</code></a> docs(:sparkles:): release 4.24.16 (<a href="https://redirect.github.com/ant-design/ant-design/issues/47932">Recidiviz/recidiviz-data#47932</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/426ae12231dc6ce20c01cd4ba1804eff52dd8b2d"><code>426ae12</code></a> chore: bump rc-* (<a href="https://redirect.github.com/ant-design/ant-design/issues/47935">Recidiviz/recidiviz-data#47935</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/6a0f811585730399e237f79df0d562ced3a0d353"><code>6a0f811</code></a> fix: 4.x Transfer selectInvert should be corrected (<a href="https://redirect.github.com/ant-design/ant-design/issues/47134">Recidiviz/recidiviz-data#47134</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/df63d1cfa7f946b546d0cc16f0f4a84ea5aec8ec"><code>df63d1c</code></a> demo: demo mock data address spelling error (<a href="https://redirect.github.com/ant-design/ant-design/issues/40432">Recidiviz/recidiviz-data#40432</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/e18bc84045ac0ff2b269aab093ab808f315c97d7"><code>e18bc84</code></a> fix: Select should show scrollbar when overflowed (<a href="https://redirect.github.com/ant-design/ant-design/issues/47050">Recidiviz/recidiviz-data#47050</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/a52e205cef7d51e4b4b27a560569497ba5b6f899"><code>a52e205</code></a> fix: Form label tooltip icon trigger Switch (<a href="https://redirect.github.com/ant-design/ant-design/issues/46159">Recidiviz/recidiviz-data#46159</a>)</li> <li><a href="https://github.com/ant-design/ant-design/commit/352fac8b3f6f2e40fdc5f53df32f74995a077dd5"><code>352fac8</code></a> ci: remove argos usage (<a href="https://redirect.github.com/ant-design/ant-design/issues/46208">Recidiviz/recidiviz-data#46208</a>)</li> <li>See full diff in <a href="https://github.com/ant-design/ant-design/compare/4.24.15...4.24.16">compare view</a></li> </ul> </details> <br /> <details> <summary>Most Recent Ignore Conditions Applied to This Pull Request</summary> | Dependency Name | Ignore Conditions | | --- | --- | | antd | [>= 5.a, < 6] | </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> GitOrigin-RevId: d5f8e20f48d40e65acc00e3a3f88dde314b733b1
Bumps [date-fns](https://github.com/date-fns/date-fns) from 3.6.0 to 4.1.0. - [Release notes](https://github.com/date-fns/date-fns/releases) - [Changelog](https://github.com/date-fns/date-fns/blob/main/CHANGELOG.md) - [Commits](date-fns/date-fns@v3.6.0...v4.1.0) --- updated-dependencies: - dependency-name: date-fns dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/frontends/admin-panel/date-fns-4.1.0
branch
from
f49530b to
d269e30
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps date-fns from 3.6.0 to 4.1.0.
Release notes
Sourced from date-fns's releases.
... (truncated)
Changelog
Sourced from date-fns's changelog.
... (truncated)
Commits
313b902Fix v4.1.0 change log entry26cd336Promote to v4.1.097b53b9Cover time zone edge cases59b7563Add missing time zone support to format, formatISO, formatISO9075, formatRela...0121164Prevent constructFrom from throwing an error on nullbd87ef5Update@date-fns/docs99b4e67Prepare v4.08df1706Rewrite the time zones doce351977Promote to v4.0.0-beta.18523656Fix scripts/test/types.shYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)