Bump http-status from 1.7.4 to 2.0.0 in /frontends/admin-panel#118
Closed
dependabot[bot] wants to merge 10000 commits intomainfrom
Closed
Bump http-status from 1.7.4 to 2.0.0 in /frontends/admin-panel#118dependabot[bot] wants to merge 10000 commits intomainfrom
dependabot[bot] wants to merge 10000 commits intomainfrom
Conversation
… from their parole release date (Recidiviz/recidiviz-data#34014) ## Description of the change Create criteria query to exclude clients who are a month away from their parole release date. I uploaded it to a sandbox under `_hsalas`. The population eligible went down by 6%.  ## Related issues Closes Recidiviz/recidiviz-data#33681 ## 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: 2fd37e2b38dc92b60728f899918ab6c7d657c7e7
…z/recidiviz-data#34091) ## Description of the change This has been on my to-do list for a while! Previously if we returned a 500 error it would come through to the FE like this: ``` <!doctype html> <html lang=en> <title>500 Internal Server Error</title> <h1>Internal Server Error</h1> <p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p> ``` which our FE error handling couldn't parse. This changes it to: ``` { "code": 500, "name": "Internal Server Error", "description": "The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application." } ``` This should make future Sentry errors caused by BE issues slightly more easy to understand (vs https://recidiviz-inc.sentry.io/issues/4905596524/?project=5385222&referrer=github_integration) ## 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#27054 ## 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: e54727b95c483bcd5d7d4ea9c28b508a8c9960e6
Recidiviz/recidiviz-data#34085) ## Description of the change Back when we introduced the `UnionAllBigQueryViewBuilder`, the idea was that `UnionAllBigQueryViewBuilder` views would only really be convenience views that union a bunch of similar data together for ease of querying, but which would not actually be referenced meaningfully downstream. At the time that we added `task_eligibility.all_tasks`, the default for `auto` mode on `load_views_to_sandbox` was to load EVERYTHING downstream of the changed views. This meant that every time someone used `auto` mode after changing a TES view, we'd materialize ALL the tasks in their sandbox. In order to prevent this, we added an option where we would, by default, filter `UnionAllBigQueryViewBuilder` views to only include parents that were changed in the sandbox run. Fast forward, and a few things have happened: 1) For a while we weren't enforcing that no views queried directly from `UnionAllBigQueryViewBuilder` so there are a number of places where we do query from these views and do analysis over, for example, all tasks. 2) We converted some critical views (`person_events`, `person_spans`) to `UnionAllBigQueryViewBuilder` views. 3) We use `UnionAllBigQueryViewBuilder` to build up `normalized_state` tables. While we eventually hope to remove direct references to the `all_person_events`, etc views via our `aggregated_metrics` optimization work and we have filed Recidiviz/recidiviz-data#29650 to remove some of the `all_tasks` direct references, it will certainly could lead to confusing results if any of these views to be filtered down to only parent views that have been touched. This PR: 1) Removes the `filter_union_all` functionality from the `load_views_to_sandbox` script 2) Replaces with a non-skippable warning about loading expensive views without a `--state_code_filter` set 3) Makes the `--state_code_filter` flag optional (bugfix) I ran the following: ``` python -m recidiviz.tools.load_views_to_sandbox \ --sandbox_dataset_prefix ageiduschek --prompt auto \ --load_changed_views_only ``` And it showed me the following warning: ```⚠️ This selection of views includes the following views that are relatively expensive to materialize: * aggregated_metrics.justice_involved_district_metrics_workflows_user_assignment_sessions * aggregated_metrics.justice_involved_facility_metrics_workflows_user_assignment_sessions * aggregated_metrics.justice_involved_state_metrics_workflows_user_assignment_sessions * aggregated_metrics.supervision_officer_aggregated_metrics * aggregated_metrics.supervision_officer_assignment_event_aggregated_metrics * aggregated_metrics.supervision_officer_assignment_span_aggregated_metrics * aggregated_metrics.supervision_officer_caseload_count_spans * aggregated_metrics.supervision_officer_metrics_person_assignment_sessions * aggregated_metrics.supervision_officer_misc_aggregated_metrics * aggregated_metrics.supervision_officer_period_event_aggregated_metrics * aggregated_metrics.supervision_officer_period_span_aggregated_metrics * observations__person_event.all_person_events * observations__person_span.all_person_spans * observations__workflows_user_event.all_workflows_user_events * observations__workflows_user_span.all_workflows_user_spans * task_eligibility.all_tasks * task_eligibility_criteria_us_az.all_state_specific_criteria * task_eligibility_spans_us_az.all_tasks⚠️ Are you sure you want to continue loading views without a `--state_code_filter` set? [y/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 Part of Recidiviz/recidiviz-data#26138 ## 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: 0a551ca78049ab28da2be6c77f8486caabdc21ac
…diviz/recidiviz-data#34081) ## Description of the change Once Recidiviz/looker#641 is merged, the legacy `analyst_data.person_events`, etc views will no longer be referenced anywhere and can be 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 Closes Recidiviz/recidiviz-data#32921 ## 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: 6bbf05052dcef0b00f3853b0b444e2c2b6fd65c4
…/recidiviz-data#34093) ## Description of the change uncovered during US_MO secondary re-import. checked the raw data tables in bq and these columns are forever null past these dates + checked the most recent version of the files and they did not contain these columns. ## 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#34002 ## 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: b6297a95cad7ac25bf278c35344a0db7e89d6c8d
…e_query for generate_person_assignments_with_attributes (Recidiviz/recidiviz-data#34103) ## Description of the change Fix query error in Workflows Impact explore: `Unrecognized name: location_id; Did you mean location_name?` Related to changes introduced in Recidiviz/recidiviz-data#33751 where we now have `location_detail_id` and `location_name` in `person_caseload_location_sessions` instead of `location_id`. Associated with this autogenerated Looker PR: Recidiviz/looker#643 ## 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: 73766e8d3e5d29dedbd99fe5cdf32a355da7bda7
…ta#34090) ## Description of the change Add X-Content-Type-Options Header per pen-test recommendation: Recidiviz/recidiviz-dashboards#6195 ## 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 Contributes to Recidiviz/recidiviz-dashboards#6195 ## 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: 92ba7753c5c9079c347783378efba718b463e492
…idiviz/recidiviz-data#34097) ## Description of the change expand accepted enum values for `LBAKRDTA_TAK017` in order to unblock re-import, re-using the TODO from the `file_description` to add more details ## 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#34002 ## 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: da8730656c24821dcaa9daa070a48f0d39bfa69f
…diviz/recidiviz-data#34054) ## Description of the change Lets production preview apps access case_triage endpoints. CORS was blocking the opportunity config endpoint and breaking workflows. ## 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: e9cd9d0b14cd14d3d82e9937d9699edd8c21e869
## Description of the change > [US_ND] Bug bash fixes to opp record ## 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: 08941ea377c5143cd8745160eb1006470bf06391
…recidiviz-data#34013) ## Description of the change In order to filter the eligibility criteria for community opportunities, we need info about whether an offense is a sex or violent offense. Updated the offense query to pull offense data from `normalized_state.state_charge` and determine whether or not it has has an attribute based on what percentage of times it is tagged as true/false. For Idaho there were only a couple of offense that had differing tags, and even those were overwhelmingly tagged one way. I used `is_violent` and `is_sex_offense` instead of their respective `_uniform` values because we want this data to be state-specific ## 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 https://github.com/Recidiviz/recidiviz-data/issues/34035 ## 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: 1974010200325768f13cffcd780ca011ebf49698
…tes (Recidiviz/recidiviz-data#34092) ## Description of the change Recidiviz/recidiviz-data#33659 restructured the `state_sentence_group_length` ingest view so that it only pulled dates that we were certain were at the group level. This PR fills in a few more fields on the `state_sentence_group_length` entity using what we now understand about sentence groups in AZ. - The sentence group level is dictated by "episodes" in AZ - Episodes can be comprised of many sentences - Every episode has exactly one "ruling offense" that dictates the amount of time a person actually spends incarcerated This PR hydrates date fields on `state_sentence_group_length` with the same dates that are used to hydrate `state_sentence_length`, but it only uses dates associated with the ruling offense for each episode. Tests: - [x] Ingest view query is deterministic - [x] Successful sandbox pipeline [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-10-10_06_16_26-12605968276981795314;graphView=0?project=recidiviz-staging&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22))). ## 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#34082 ## 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: 3fdaadf256a00433a1057cb5166ce2290d63c0fa
## Description of the change There are a number of dates before 1900 and after 2100 that we do not want to see as viable release dates in the state_sentence_length view. Anna's [review](Recidiviz/recidiviz-data#34092 (comment)) of Recidiviz/recidiviz-data#34092 pointed out that the way I was filtering the dates removed the entire row with any malformed date, rather than nulling out the date itself, which was my original intention. This PR updates `state_sentence_length` to `NULL` out dates that fall outside of the range we want to see, rather than removing the rows they are in from the results altogether. Ran a test pipeline to be extra sure this wouldn't break anything [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-10-10_08_02_25-2854898854446169253;graphView=1?project=recidiviz-staging&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22)))! ## 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: ffa81de30fee0eb7e36fd0ee93ce8cf8d05f1b1d
…iviz-data#34111) ## Description of the change In testing the new raw data import DAG, we are encountering a bottleneck in writing KPO task output to XCom, where the sidecar container dies before we are able to push the entire task output. For now, naively increase concurrent task count to decrease the amount of data we are pushing to xcom per task in order to overcome this immediate bottleneck and facilitate testing. We should adjust this later to a sane number/explore alternatives to overcoming this bottleneck after we finish addressing all the other issues coming along with the US_MO reimport ## 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#34002 ## 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: 2c6847ccfe857ac3fb642ce6e2b6a315775950d6
…iz-data#34110) ## Description of the change A previous PR closed Recidiviz/recidiviz-data#32921 but I hadn't cleaned up all the TODOs. This migrates a number of TODOs to reference the overall epic for optimizing aggregated_metrics and adds clustering on state_code to observation-level tables. ## 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#32921 ## 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: fc1faae91b61714a94dfab8c24329aaafbc3e42e
…iz-data#34087) ## Description of the change This PR uses product roster role types and auth0 sign up/log-in events to define a sessions view representing periods of time over which primary Insights users (i.e., supervisors) were registered with access to the Insights tool. This view will be used to define span observations that will ladder up to a "registered Insights primary users" metric and form the basis for Insights MAUs (see [design doc](https://www.notion.so/recidiviz/Design-Doc-Insights-Impact-Analysis-Metrics-1157889f4d198053a571ed6cce339657) for more) Changes of note: - We previously had a view called `workflows_user_product_roster_archive_sessions` -- I converted this into a generic `product_roster_archive_sessions` view to avoid too much repeated logic, and added flags for `has_workflows_access` and `has_insights_access` which can be used to filter downstream views - Created a view of Insights signup dates (identifies first auth0 signup/login event during which a user had access to insights), mirroring `workflows_user_signups` - Created a shared function to generate primary user registration sessions for a given product surface, mostly reusing logic from `workflows_primary_user_registration_sessions` that uses a combination of product roster archive sessions and signups to construct sessions of time over which a supervisor was registered for the Workflows/Insights tool. See sandbox: `mayukas_34045_analyst_data`. The query below shows 57 insights primary users currently registered in MI, 21 in TN, 6 in IX, and 1 in CA ``` SELECT state_code, COUNT(DISTINCT insights_user_email_address) FROM `recidiviz-123.mayukas_34045_analyst_data.insights_primary_user_registration_sessions_materialized` WHERE end_date_exclusive is null GROUP BY 1 ORDER BY 2 desc ``` ## 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 Advances Recidiviz/recidiviz-data#34045 ## 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 --------- Co-authored-by: mayukas <mayuka@stanford.edu> Co-authored-by: Dana Hoffman <1130694+danawillow@users.noreply.github.com> GitOrigin-RevId: e1ed4f63e4ff7aece43b104f8c48b153f1a2c5d2
…roduct_roster (Recidiviz/recidiviz-data#34116) ## Description of the change Yesterday I learned that when you materialize a NULL array, BQ converts it into an empty array, which means `COALESCE(user_override.roles, roster.roles)` doesn't actually do what we want 🙃 Since all users should have roles, we can assume that if `user_override.roles` is empty, that's because it was NULL before it materialized, so this change should be safe. This reduces the number of users in this view with empty roles from 48 down to 9 (those 9 are users who had overrides and then were removed with roster sync, and should probably just be removed entirely but that's a different problem) Sandbox at `recidiviz-123.dana_roster` ## 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: dd45cf75178157f76003258efaa8a93214bc242e
…iz/recidiviz-data#34118) ## Description of the change In TX a person is assigned a single US_TX_SID for their entire life but their US_TX_TDCJ ID changes throughout time (after every stint with TDCJ I believe) Also makes sure to get rid of "null" external ID values Successful pipeline [here](https://console.cloud.google.com/dataflow/jobs/us-west1/2024-10-10_14_57_02-7553778682716155388;graphView=0?project=recidiviz-staging&pageState=(%22dfTime%22:(%22l%22:%22dfJobMaxTime%22))) ## 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: a2815f7d5f5eddb8a40a1f529a84bbcb86a5ffc8
## Description of the change Adds raw data documentation & general AZ docs ## 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#34036 ## 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: - [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 --------- Co-authored-by: Anna Geiduschek <anna@recidiviz.org> GitOrigin-RevId: 6a231d5535a471ef2007a388a739dee335aaacbc
## Description of the change Seems like standard variation! Went from 227 to 170, which is barely out of stable range, and we'd already bumped the threshold for incarceration periods aggregated by discharge date. ## 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#34030, Recidiviz/recidiviz-data#34031 ## 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: e2a57c7531f33281a22236f26cd6dc83ff752986
…views (Recidiviz/recidiviz-data#34130) ## Description of the change We're seeing some pretty serious cost regressions after cutting Looker dashboards over to use the new unioned `all_person_events` etc views from the legacy `person_events`. The main difference we can find is that the old views were clustered on state_code and event/span. This introduces that clustering to the new views and also requires that ALL `UnionAllBigQueryViewBuilder` views have clustering. ## 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 https://recidiviz.pagerduty.com/incidents/Q38P7KSZCCWTPG ## 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: 34fc4b025165787868789b79e320ed0d251ff9e4
…ard API response (Recidiviz/recidiviz-data#34077) ## Description of the change The v2 agency dashboard response now looks like this! ``` { "agency": { "county_geoid": "0500000US36061", "county_name": "New York County", "id": 147, "is_dashboard_enabled": null, "jurisdictions": { "excluded": [ "0600000US3602950716", "0500000US36081" ], "included": [ "0500000US36061", "0400000US36" ] }, "name": "Law Enforcement", "settings": [], "state_abbreviation": "NY", "state_geoid": "0400000US36", "state_name": "New York", "systems": [ "LAW_ENFORCEMENT" ] }, ``` The major changes are that 1) We don't use FIPS, rather GEOID. 2) We include the state abbreviation and the state name 2) We include jurisdiction GEOIDs ## Related issues Closes Recidiviz/recidiviz-data#34076 ## 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: 8c3b5c384989fa50c3c6c7f4e84396f507cc0fae
…ecidiviz/recidiviz-data#34106) ## Description of the change Now that the action strategies are part of the Insights Configuration, we are adding fields for them to the `AddConfigForm` on the admin panel. This PR adds these fields to the form via an `ActionStrategyFormItem` component for each action strategy that displays two inputs, one for the prompt copy, and one for the body copy. Alongside the inputs are live markdown components that preview the rendered markdown and update as you edit the input. The updated action strategy copy is then saved to the db as a json object when the configuration is added/updated. ## 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#34022 ## 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: Jen <jovergaag@gmail.com> GitOrigin-RevId: bf018a8f55621dc9af974621089e80eff66cecf9
## Description of the change Creating yamls for new supervision data tables sent ## 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: 42620efd672ac23dc7fc143238b512634cfcf28a
…ecidiviz/recidiviz-data#34074) ## Description of the change Add README ~and comment~ for ~duplicated~ TIG elements as a follow up to this PR: Recidiviz/justice-countsRecidiviz/recidiviz-data#1541 ## 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#34057 ## 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: fd4f3b11b65f47d3ad030a362dde43b004d2172e
…sments (Recidiviz/recidiviz-data#34126) ## Description of the change Adding new creation date column to ClientData and adding raw data config for Assessments sandbox [here](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1srecidiviz-staging!2ssanty_yam_us_tx_raw_data) ## 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: 30a48645de9bf83f118e8135839b8c0b58a5fee9
…ta#34120) ## Description of the change Fixes the `export_csg_files` script to not crash on the `state_sentence_inferred_group` which is not defined in the SQLAlchemy schema because it's a normalization-only entity. Confirmed that the following query no-longer crashes ``` python -m recidiviz.tools.export_csg_files --project-id recidiviz-123 --dry-run True --target-bucket recidiviz-123-partner-data-export-csg --start-date 2024-08-30 --state-code us_mo ``` ## 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#34039 ## 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: 6306acde3477bbd9822b11486417dcf85f77b2e7
…diviz-data#34121) ## Description of the change We had a whole convoluted class hierarchy to handle building queries based on the tables defined in our SQLAlchemy schemas. A lot of this complexity stemmed from the fact that the schema for the STATE schema changed between CloudSQL and BQ - association tables did not have `state_code` values but were added as we imported to BQ. A few things have now changed: 1) My fix in Recidiviz/recidiviz-data#34120 eliminated the last usage of `BigQuerySchemaTableRegionFilteredQueryBuilder`. As a result, the only actual subclass of `SchemaTableRegionFilteredQueryBuilder` that was being instantiated in our codebase (outside of tests) was `FederatedSchemaTableRegionFilteredQueryBuilder`, which we use for the CloudSQL to BQ refresh. 2) We don't actually "filter" data by state code for any schema when we're loading from CloudSQL, so all of the state code filtering logic was not being used. 3) None of the schemas we're loading of have association tables missing the `state_code` column that need to be joined to other tables to hydrate. This PR: 1) Condenses all the remaining relevant query building logic in `recidiviz/persistence/database/schema_table_region_filtered_query_builder.py` into a single `FederatedCloudSQLTableQueryBuilder` class 2) Condenses all remaining relevant tests into a single test case 3) Moves the class to the `bq_refresh` package since it's only used there. Ran the following to confirm this did not break existing functionality: ``` python -m recidiviz.tools.postgres.load_postgres_to_bq_sandbox \ --project_id recidiviz-staging \ --sandbox_dataset_prefix ageiduschek \ --schema CASE_TRIAGE python -m recidiviz.tools.postgres.load_postgres_to_bq_sandbox \ --project_id recidiviz-staging \ --sandbox_dataset_prefix ageiduschek \ --schema OPERATIONS ``` ## 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#34039 ## 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: 453b522ae69c94126f50bcd6fa3fa4adfe7756a9
…-panel (Recidiviz/recidiviz-data#34151) Bumps @recidiviz/design-system from 5.7.0 to 5.8.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: 3a459d72a1846b27f23e550c1aeaa75e3dacba8f
…types/prototype-app (Recidiviz/recidiviz-data#34153) Bumps @recidiviz/design-system from 5.7.0 to 5.8.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: abefc59862829b023523db4832ad88fd9037cb6c
…cidiviz-data#31746) ## Description of the change I created a function (`upload_assigments_to_gbq`) to upload randomized assignments to BQ. I also created tests to ensure the right schema gets uploaded to BQ. These are meant to be used in the notebooks where we perform the randomization. Specifically: - It appends a pandas df to `manually_updated_source_tables.experiment_assignments_large` in both staging and prod. - It automatically creates a timestamp in the column `upload_datetime` for each upload. ## Related issues Closes Recidiviz/recidiviz-data#31117 ## 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 --------- Co-authored-by: Anna Geiduschek <anna@recidiviz.org> GitOrigin-RevId: dd667dfb42387d956c7e7fdf00617db771a0ea60
…ecidiviz/recidiviz-data#34592) Adds a outliers_views.supervision_officer_metrics_view table to BQ with the export data column, following the pattern of the other insights archive views. GitOrigin-RevId: 5743b32e946eb2d6c63305804fd350b30e30b6d6
…ison Agencies (Recidiviz/recidiviz-data#34608) This PR adds population data from census data for prisons agencies. This is the last ask for CSG as part of sprint 2! I tested that the response matched[ the outlined response](https://docs.google.com/document/d/1SldHzkvMk-wdBwBamajgJjNrj4_bc3GUdLy-oXHZ-Uo/edit?pli=1&tab=t.0#heading=h.p07ennn8h997) locally. ## Related issues Closes Recidiviz/recidiviz-data#33022 ## 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: 062364ce4364a426210d4764aa8641397f2cf426
) ## Description of the change Validation tasks have occasionally been failing due to `OOMKilled` errors ## 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 PagerDutyRecidiviz/recidiviz-data#7409 ## 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: 950aba575d6e37ae604143c8d1ff33b6f1544967
…diviz-data#34639) ## Description of the change Add a new source for location metadata so that we capture a few new locations that have cropped up in state staff ingest. Fixes this validation: Recidiviz/recidiviz-data#33671 Tested with compare views to confirm that this change only adds new locations but doesn't change any existing locations: ``` python -m recidiviz.tools.calculator.compare_views \ --dataset_original reference_views \ --dataset_new brenda_scratch \ --view_id us_pa_location_metadata_materialized \ --output_dataset_prefix zbrenda_pa_meta \ --grouping_columns state_code ``` ## 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: 395945e5d850283dc887d23070cc13e8a184d2f9
…34621) ## Description of the change Lower validation thresholds ## 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: fd1c3d821059af2a6bb228a635f50463417996d6
…tiontype (Recidiviz/recidiviz-data#34687) ## Description of the change Fixes error for Could not parse SPECIALTY COURTS when building <enum 'StateSupervisionViolatedConditionType' by mapping to INTERNAL_UNKNOWN ## 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#34683 ## 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: f84467a658742f5839e4a3f5b820f4311107e990
…a#34692) ## Description of the change sftp branch boolean logic previously looked like -- ``` acquire_permission_branch, _ = create_branch_by_bool( pause_ingest_queues, # branch if true -- new raw data infra acquire_resource_locks, # branch if false -- legacy raw data infra is_raw_data_dag_enabled_in_primary(state_code), ) ``` meaning we were doing the exact opposite of what we wanted 🤦 🤦 🤦; this PR fixes this bug by flipping them ## 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 n/a ## 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: 4e29fd69b670f40390c01b8ebb230ac033ca1940
## Description of the change ### Overview: This PR refactors state staff ingest in PA to allow for a new type of staff external ID (PosNoIds) since PA switched to a new database for staff information and new staff people may not be assigned EmpNums anymore. Therefore, this PR adds in `supervision_staff_v2` and `supervision_staff_periods_v2` to replace the original staff ingest views (supervision_staff, `supervision_staff_location_periods`, `supervision_staff_role_periods`, `supervision_staff_caseload_periods`, `supervision_staff_supervisor_periods`). #### **I tried to comment each CTE a ton and but here is also a video walkthrough of this PR:** https://drive.google.com/drive/folders/1jLNVZB718cDIBSCNpodDKRn4yQc1CwG9 ### Additional context: In PA, there are three different sources for staff information: - RECIDIVIZ_REFERENCE_staff_roster: which is the manually compiled roster that PA research provides us from time to time. This includes all staff information for current staff including staff names, employee numbers, position numbers, location codes, role descriptions, and supervisor information. - dbo_RelAgentHistory: which is the supervision officer assignment table that includes staff names, employee numbers, position numbers, and location codes for all supervising officers assigned to a client and those supervising officers' supervisors. - dbo_PRS_FACT_PAROLEE_CNTC_SUMRY: which is the supervision contacts table that includes staff employee numbers, role description, location codes, and names. Across these two sources, there are two different types of id numbers: - Employee numbers, which should be unique to an individual staff person - Position numbers, which are unique to a specific job opening/position, and therefore is attached with multiple staff people over time. Given that employee number is sometimes missing in the data, and may not exist in the future since it's not a part of PA's new staff database, this PR refactors state staff ingest to ingest state staff external ids based on both the original employee numbers (EmpNums) and a new id we'll construct and call position number ids (PosNoIds) that takes the structure of `<position number>-<staff last name><staff first initial>`. Test documentation: https://www.notion.so/recidiviz/Testing-for-State-Staff-387ffa3611684698a2a1089ffafd2149 ## 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: 1a047491d2fbce2e78bbc21f338d241001390f17
…cidiviz/recidiviz-data#34392) ## Description of the change Adds configurations for 3 new metrics in the insights explore: - distinct registered users - distinct logged in users - logins mirroring the same 3 metrics on the Workflows explore. See associated LookML autogenerated PR here: Recidiviz/looker#660 ## 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: mayukas <mayuka@stanford.edu> GitOrigin-RevId: 496fa1ed82a6b2ee25cf640bf3ab322a6af60889
…ics (Recidiviz/recidiviz-data#34699) ## Description of the change The changes I made to how the gender and race fields and filters get defined in [this PR](Recidiviz/recidiviz-data#34414) means we need to define the `demographic_attribute_field_filters_with_suggestions` dictionary in the insights metrics LookML generator to avoid errors when [these Liquid conditions](https://github.com/Recidiviz/recidiviz-data/blob/496fa1ed82a6b2ee25cf640bf3ab322a6af60889/recidiviz/tools/looker/aggregated_metrics/custom_metrics_lookml_utils.py#L905-L916) get evaluated. ## 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: 2c0a3b12f5f0e8b9dbe3de3758c75f348500eb35
…ERENCE_field_supervisor_list (Recidiviz/recidiviz-data#34659) ## Description of the change This table isn't referenced by any views so nothing else should need to 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 Recidiviz/recidiviz-data#34445 ## 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: 43a1f7a7b4bce0cf0bc0d58968f409e8e2a1b770
…cidiviz-data#34689) ## Description of the change [US_ME] add logixal_delete_ind to the analyst_data view ## Related issues Closes Recidiviz/recidiviz-data#34669 ## 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: 1a3673ed34639d2e7adcdcc0bc807baeb50073f9
…3864) ## Description of the change Hydrating incarceration incidents so that we can use incident information to power classification level downgrade tool ## 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#33656 ## 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: 2ae964a63a67b5210ad1c676d3ddb0fe6eace289
…ies_for_file_tag (Recidiviz/recidiviz-data#34701) ## Description of the change Raw data migrations are not being applied in the new raw data import infra because in the check ``` filtered_migrations = [ migration for migration in migrations_shared_filter_keys if not migration.update_datetime_filters or data_update_datetime in migration.update_datetime_filters ] ``` `date_update_datetime` is tz aware and the `update_datetime_filters` list is not so the condition was never true We can convert the `file.update_datetime` to non tz aware to unblock import, but in the future we should convert all existing migrations to being timezone aware and validate any datetime in `update_datetime_filters` is tz aware. ## 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#34696 ## 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: c8c098a9ec3172929231b4d50cb0972f1c5e8f24
…date has passed (Recidiviz/recidiviz-data#34693) ## Description of the change [US_AZ] Constrain incarceration_past_acis_tpr_date to 100 days after date has passed. I uploaded it all to a sandbox (hsalas) and the number of eligible people was lowered considerably, as expected. We are passing all of our validations.  ``` python -m recidiviz.tools.load_views_to_sandbox \ --project_id recidiviz-staging\ --sandbox_dataset_prefix hsalas \ --state_code_filter US_AZ manual \ --dataset_ids_to_load task_eligibility_criteria_us_az,task_eligibility_spans_us_az,task_eligibility,validation_views\ --update_descendants False ``` I also checked who we were now ineligible due to this change, and we are screening out people who's `acis_tpr_date `range is from 2012-11-17 to 2024-07-23. I think this confirms that we are doing the right thing, since every single date in this range is past the 100 day mark.  ## Related issues Closes Recidiviz/recidiviz-data#34620 ## 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: a090f01a9c2eb5e7c6a3c0855b029cf470271f85
…#34708) ## Description of the change Recidiviz/recidiviz-data#34678 accidentally used the wrong [delimiter](https://github.com/Recidiviz/recidiviz-data/blob/main/recidiviz/calculator/query/state/views/reference/ingested_product_users.py#L86) for experiment roles. This PR fixes that. ## 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: b0671141439843be656e06cec9a75b35a4802afb
…Recidiviz/recidiviz-data#34535) ## Description of the change This PR adds a metadata blob to AZ resident records with important dates to display in their profiles. Tested by loading views to BQ. You can see the new metadata blobs via ``` SELECT * FROM `recidiviz-staging.kesich_workflows_views.resident_record_materialized` WHERE state_code = "US_AZ" ``` ## 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#34533 ## 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~ BQ change ### 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: 02aa573e4b66c885055561aef66eb4857f3924d2
…ecidiviz/recidiviz-data#34686) ## Description of the change We were seeing an error importing the supervision_client_events into postgres trying to write null data into a non-nullable field. This changes the two officer id columns to be nullable. PS - I'm not sure why these docs changed, but the pre-commit hook updated them so I'm going with it... [Logs](https://console.cloud.google.com/logs/query;query=resource.type%20%3D%20%22cloud_run_revision%22%20httpRequest.requestUrl%20%3D%20%22https:%2F%2Fapplication-data-import-qqec6jbn6a-uc.a.run.app%2Fimport%2Finsights%2FUS_TN%2Fsupervision_client_events.json%22;cursorTimestamp=2024-10-31T13:25:23.256979Z;startTime=2024-10-24T18:20:42.798Z;endTime=2024-10-31T18:20:42.798Z?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#34685 ## 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: b12446e83bbd50294bed48008d568f718f9d603a
…diviz-data#34419) ## Description of the change Opportunity record queries for Work Release and Institutional Worker Status (aka 309) opportunities. Uses `resident_metadata` for both records, and makes some small changes: - Show the location name instead of ID. - Dedup location using compartment sub sessions - Dedup violations info using end date exclusive clause instead of end date clause Sandbox: ``` select * from `recidiviz-staging.dallen_ar_workflows_views.us_ar_work_release_record_materialized` ``` ``` select * from `recidiviz-staging.dallen_ar_workflows_views.us_ar_institutional_worker_status_record_materialized` ``` ## 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: c63ad16db20d868123f9e3d8c997453da0caa3df
…Recidiviz/recidiviz-data#34705) ## Description of the change Add the `is_surfaceable` attribute to the Workflows person status spans. Use the new attribute in the new `usage_reports_aggregated_metrics_configurations.py` (naming suggestions welcome), which will be fully fleshed out in Recidiviz/recidiviz-data#34080. ## Related issues Closes Recidiviz/recidiviz-data#34602 ## 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: 01a4849f4ba8b9f82005615d585808e4ee7b64d1
…iz/recidiviz-data#34630) ## Description of the change Updates how we manage the Insights Config - reduces number of columns shown in the configs table - Adds a "View" page to view config details - Adds routing to navigate to the view page - Moves management of each config to the view page ## 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#34023 ## 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: 43d96df3bdea6fe2311e83e7376c2e728cbbb0bd
…iz-data#34724) ## Description of the change The `us_mo_restrictive_housing_record` view does not properly filter down to MO-only rows in all places. In one place it makes a state-specific assumption about the structure of a raw text field for incarceration incidents. We newly hydrated incidents in IX with this most recent release and those incidents are causing this query to crash: ``` google.api_core.exceptions.BadRequest: 400 GET https://bigquery.googleapis.com/bigquery/v2/projects/recidiviz-staging/queries/a40dd590-4278-48f9-90b6-a952dfab2ecd?maxResults=0&location=US&prettyPrint=false: Bad int64 value: B - IN A CRC OR MINIMUM CUSTODY ... ``` This change updates the view to filter down to only MO rows everywhere, so we don't crash on data from other states. I was able to reproduce the error before, but now generating and running the view succeeds. ## 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 N/A - View updating is failing in staging ## 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: 0eb378c1295b7917cb262593174dcc46cada051d
…iviz/recidiviz-data#34733) Bumps [http-status](https://github.com/adaltas/node-http-status) from 1.7.4 to 1.8.1. <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> <h2><a href="https://github.com/adaltas/node-http-status/compare/v1.7.4...v1.8.0">1.8.1</a> (2024-10-21)</h2> <ul> <li>Revert changes introduced by 1.8.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/adaltas/node-http-status/commit/a1001e0f17aa911f0cca992b0f2f4f908cf49978"><code>a1001e0</code></a> chore(release): 1.8.1</li> <li>See full diff in <a href="https://github.com/adaltas/node-http-status/compare/v1.7.4...v1.8.1">compare view</a></li> </ul> </details> <br /> <details> <summary>Most Recent Ignore Conditions Applied to This Pull Request</summary> | Dependency Name | Ignore Conditions | | --- | --- | | http-status | [>= 2.a, < 3] | </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: 6524d6664433d8fd2bb4fcb863fb44981a296d31
Bumps [http-status](https://github.com/adaltas/node-http-status) from 1.7.4 to 2.0.0. - [Changelog](https://github.com/adaltas/node-http-status/blob/master/CHANGELOG.md) - [Commits](adaltas/node-http-status@v1.7.4...v2.0.0) --- updated-dependencies: - dependency-name: http-status 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/http-status-2.0.0
branch
from
fef725c to
4a8b5c0
Compare
Contributor
Author
|
Superseded by #132. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/frontends/admin-panel/http-status-2.0.0
branch
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 http-status from 1.7.4 to 2.0.0.
Changelog
Sourced from http-status's changelog.
Commits
b962963chore(release): 2.0.0f44a8abbuild: latest dependencies7d5d18fdocs: overall organisation60ced7adocs: express sample cleanupdb7c73edocs: covert api sample to ts42de852ci: publish with node 22b9a3c53ci: test with node 16, 20 and 224e62032ci: build before publish6d6191ffeat: named exportfc24d8ddocs: rephrase readme and use esm for exampleYou 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)