Redact password column from CSV import logging and error output by jacalata · Pull Request #1862 · tableau/server-client-python

jacalata · 2026-08-16T12:12:47Z

Summary

Fixes two paths in UserItem.CSVImport that could leak the password column from a user-import CSV file:

_validate_import_line_or_throw logged logger.info(f"Reading user {line[:4]}"). The intent was to avoid printing the password, but slicing four characters only obscures usernames shorter than four characters -- longer usernames leak part of the row, and if the layout ever changed the password itself could reach the log.
validate_file_for_import returned raw lines in its invalid_lines list when a row failed validation. Any caller that logged or surfaced those lines would expose the password unmasked.
The per-column debug log inside _validate_import_line_or_throw printed the PASS column value verbatim.

What changes

Row-level logs now include only the username (parsed by partition on the first comma) and are demoted to DEBUG.
invalid_lines entries pass through a new _redact_password_column helper that replaces column 1 with ***, preserving the line's original line ending.
The per-column DEBUG log masks the PASS column with ***.

The redaction helper uses the same naive str.split(",") parsing already used throughout the file. A password value containing commas is misaligned across columns; only the fragment landing in column 1 is masked. A test documents this limitation -- a proper CSV parser would be a larger change and is out of scope here.

Test plan

Four new tests in test/test_user_model.py covering: DEBUG log on a valid row (positive-and-negative assertion so a fix that only deletes the log line would fail), invalid-row path (both the returned invalid_lines and the logger output), embedded-comma limitation, and unit-level edges on _redact_password_column (LF, CRLF, no newline, empty password, trailing comma, single column).
Full test suite passes locally.

🤖 Generated with Claude Code

`UserItem.CSVImport.validate_file_for_import` and `_validate_import_line_or_throw` wrote the raw CSV line -- including the password column -- to any caller-supplied logger at INFO/DEBUG level, and the whole raw line was pushed into the `invalid_lines` list returned to callers when a row failed validation. Anyone using the sample logger config or forwarding logs to a centralized system would see clear-text passwords in the log stream. Changes: - `validate_file_for_import` logs only the username (column 0) at DEBUG, and calls a new `_redact_password_column` helper before appending an invalid row to the returned list. - `_validate_import_line_or_throw` masks the PASS column value as `***` before logging it. Other column values still logged as-is for debugging. - Both callers changed from INFO to DEBUG for these per-row messages; large imports were spamming operator-visible logs. - Two regression tests capture logs and returned invalid_lines to assert the secret never appears in either place, plus a positive assertion that a `***` masked value IS logged so a future refactor that just removes the log line entirely doesn't pass. Fixes #1829. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

github-actions · 2026-08-16T12:13:29Z

Coverage Report

File	Stmts	Miss	Cover	Missing
tableauserverclient
__init__.py	5	0	100%
config.py	15	0	100%
datetime_helpers.py	25	1	1	96%
exponential_backoff.py	20	0	100%
filesys_helpers.py	31	0	100%
namespace.py	25	3	3	88%
tableauserverclient/bin
__init__.py	2	0	100%
_version.py	358	212	212	41%
tableauserverclient/helpers
__init__.py	1	0	100%
logging.py	2	0	100%
strings.py	31	1	1	97%
tableauserverclient/models
__init__.py	46	0	100%
collection_item.py	41	7	7	83%
column_item.py	55	32	32	42%
connection_credentials.py	35	11	11	69%
connection_item.py	113	13	13	88%
custom_view_item.py	144	21	21	85%
data_acceleration_report_item.py	54	1	1	98%
data_alert_item.py	158	4	4	97%
data_freshness_policy_item.py	155	15	15	90%
database_item.py	207	36	36	83%
datasource_item.py	300	12	12	96%
dqw_item.py	104	5	5	95%
exceptions.py	4	0	100%
extensions_item.py	132	4	4	97%
extract_item.py	44	4	4	91%
favorites_item.py	69	8	8	88%
fileupload_item.py	19	0	100%
flow_item.py	149	10	10	93%
flow_run_item.py	71	0	100%
group_item.py	89	6	6	93%
groupset_item.py	49	7	7	86%
interval_item.py	182	32	32	82%
job_item.py	192	10	10	95%
linked_tasks_item.py	79	1	1	99%
location_item.py	29	2	2	93%
metric_item.py	129	13	13	90%
oidc_item.py	63	3	3	95%
pagination_item.py	34	1	1	97%
permissions_item.py	111	12	12	89%
project_item.py	207	31	31	85%
property_decorators.py	100	18	18	82%
reference_item.py	26	2	2	92%
revision_item.py	59	1	1	98%
schedule_item.py	209	6	6	97%
server_info_item.py	37	7	7	81%
site_item.py	636	13	13	98%
subscription_item.py	101	2	2	98%
table_item.py	119	18	18	85%
tableau_auth.py	61	25	25	59%
tableau_types.py	27	1	1	96%
tag_item.py	15	0	100%
target.py	6	0	100%
task_item.py	56	2	2	96%
user_item.py	368	17	17	95%
view_item.py	220	16	16	93%
virtual_connection_item.py	64	8	8	88%
webhook_item.py	69	1	1	99%
workbook_item.py	362	16	16	96%
tableauserverclient/server
__init__.py	9	0	100%
exceptions.py	4	0	100%
filter.py	29	1	1	97%
pager.py	33	1	1	97%
query.py	143	15	15	90%
request_factory.py	1345	194	194	86%
request_options.py	386	5	5	99%
server.py	249	25	25	90%
sort.py	6	0	100%
tableauserverclient/server/endpoint
__init__.py	35	0	100%
auth_endpoint.py	73	10	10	86%
custom_views_endpoint.py	152	12	12	92%
data_acceleration_report_endpoint.py	21	0	100%
data_alert_endpoint.py	94	23	23	76%
databases_endpoint.py	111	30	30	73%
datasources_endpoint.py	323	33	33	90%
default_permissions_endpoint.py	44	3	3	93%
dqw_endpoint.py	45	16	16	64%
endpoint.py	260	25	25	90%
exceptions.py	79	6	6	92%
extensions_endpoint.py	31	0	100%
favorites_endpoint.py	94	22	22	77%
fileuploads_endpoint.py	51	0	100%
flow_runs_endpoint.py	62	9	9	85%
flow_task_endpoint.py	21	2	2	90%
flows_endpoint.py	198	47	47	76%
groups_endpoint.py	126	9	9	93%
groupsets_endpoint.py	72	7	7	90%
jobs_endpoint.py	68	9	9	87%
linked_tasks_endpoint.py	37	0	100%
metadata_endpoint.py	88	14	14	84%
metrics_endpoint.py	55	6	6	89%
oidc_endpoint.py	42	1	1	98%
permissions_endpoint.py	44	3	3	93%
projects_endpoint.py	178	24	24	87%
resource_tagger.py	127	35	35	72%
schedules_endpoint.py	119	11	11	91%
server_info_endpoint.py	36	10	10	72%
sites_endpoint.py	130	27	27	79%
subscriptions_endpoint.py	56	14	14	75%
tables_endpoint.py	110	36	36	67%
tasks_endpoint.py	63	6	6	90%
users_endpoint.py	170	7	7	96%
views_endpoint.py	150	9	9	94%
virtual_connections_endpoint.py	113	10	10	91%
webhooks_endpoint.py	54	9	9	83%
workbooks_endpoint.py	338	22	22	93%
TOTAL	12188	1419	88%

Copilot

Pull request overview

This PR hardens UserItem.CSVImport to prevent accidental disclosure of the CSV password column via logging and error/invalid-line output, addressing security issue #1829.

Changes:

Restrict row-level import logs to username-only and emit them at DEBUG level.
Redact the password column (PASS) when returning invalid_lines, and mask the PASS value in per-column DEBUG logs.
Add regression/unit tests covering log redaction behavior and helper edge cases; document the embedded-comma limitation; update changelog.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
tableauserverclient/models/user_item.py	Adds password redaction helper and updates CSV import logging/invalid-line handling to avoid password disclosure.
test/test_user_model.py	Adds regression tests ensuring passwords do not appear in DEBUG logs or invalid row output; adds unit tests for redaction helper behavior.
CHANGELOG.md	Documents the security fix for CSV import password logging/output behavior (Fixes #1829).

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

The original _redact_password_column stripped only \n before splitting on commas, so on a CRLF-terminated 2-column line ("user,pass\r\n") the \r rode with the password field, was thrown away when that field became "***", and the returned line silently downgraded to LF. Now the exact trailing sequence (\r\n, \n, or none) is preserved and reattached after the redaction. Adds a regression test for the CRLF-with-password-as-last-field case. Also corrects the CHANGELOG: the pre-fix code logged the first four characters of each raw row at INFO (not DEBUG), which is why the downgrade to DEBUG matters in addition to the redaction.

jacalata · 2026-08-18T04:36:58Z

22934d4 addresses both Copilot findings:

_redact_password_column now preserves the exact trailing sequence (\r\n, \n, or none) after redaction. Split-and-rejoin no longer downgrades CRLF to LF when the password is the last field.
Regression test "user,pass\r\n" -> "user,***\r\n" added to test_redact_password_column_helper.

CHANGELOG updated separately: the pre-fix code logged the first four characters of each raw row at INFO, not DEBUG, so the entry now describes both the row-level INFO→DEBUG downgrade and the password-column redaction.

…-privacy # Conflicts: # tableauserverclient/models/user_item.py # test/test_user_model.py

Inadvertently pulled the password-column mask (safe_value = "***" if column == PASS else value) into this PR while restructuring the validation loop for the warn-on-unknown-auth change. The mask is #1862's core content and shouldn't sneak in through the site-role decompose PR -- reviewers on either PR would see mysterious overlap. #1862's full feature (log mask + INFO->DEBUG downgrade + _redact_password_column helper for invalid_lines sanitization) stays where it belongs, on jac/csv-import-privacy. The `column = ColumnType(i)` local rename stays because it's used by the log line's `{column.name}` format and by the AUTH branch's comparison; that's plain cleanup and doesn't overlap with #1862.

@deprecated

… _evaluate_site_role (#1812) * fix: CSVImport AUTH column, case-insensitive validation, username preservation; add find_by_name Fixes for UserItem.CSVImport (issue #1809): - MAX=8 (was 7=AUTH index): 8-column lines with auth type no longer rejected as "too many columns" - create_user_from_line no longer lowercases the whole line before splitting — username case is preserved - _validate_import_line_or_throw normalizes license/admin/publisher to lowercase and auth to canonical form before comparison, so 'Viewer', 'Creator', 'SAML', 'tableauidwithmfa' etc. are all accepted - Add TableauIDWithMFA to valid auth values in validation (was missing) - 5 new tests covering each fix Add QuerysetEndpoint.find_by_name(name) (issue #1810): - Thin wrapper over .filter(name=name) returning a list - Available on all content-item endpoints (workbooks, datasources, views, users, projects, groups) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: add auth column to create_users_csv, fix create_from_file extension check and debug prints - create_users_csv was producing 7-column CSV, silently dropping auth_setting; bulk_add roundtrip would lose auth type - create_from_file extension check used filepath.find("csv") which evaluates as falsy only when "csv" is at index 0, letting all other paths through; fixed to "csv" not in filepath - remove two debug print() calls left in create_from_file Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * refactor: extract _decompose_site_role into CSVImport, symmetrical with _evaluate_site_role Moves the ad-hoc site role → (license, admin_level, publish) logic from create_users_csv into UserItem.CSVImport._decompose_site_role, making it the explicit inverse of _evaluate_site_role. Also fixes pre-existing bugs in the decomposition: - ExplorerCanPublish was emitted as license="ExplorerCanPublish" (not a valid CSV license value); now correctly "Explorer" with publish=1 - SiteAdministrator (legacy role) was emitting license="" via str.replace; now maps to ("Explorer", "Site", "1") - Non-admin roles now emit admin_level="None" (explicit CSV spec value) rather than "" (empty string); both are accepted by the server but "None" is consistent with the spec and _evaluate_site_role input Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix: decompose unsupported site roles to license="Invalid" not "Unlicensed" Legacy values in UserItem.Roles (UnlicensedWithPublish, ViewerWithPublish, Guest, SupportUser) have never been accepted by the server-side CSV license parser (workgroup: CsvLicenseRoleTypeConverter). The initial _decompose_site_role default of ("Unlicensed", "None", "0") silently coerced these to a valid but semantically wrong Unlicensed user, replacing an old server-side per-row rejection with silent success. Default to license="Invalid" instead so the server continues to reject rows with USER_CSV_INVALID_LICENSE, preserving the pre-refactor observable behavior for callers who inspect job results for per-row failures. Batch resilience is unaffected: bad rows fail, good rows succeed, no client-side throw takes down the whole bulk_add call. Follow-up: deprecate UnlicensedWithPublish/ViewerWithPublish from UserItem.Roles (never worked on any code path); see forthcoming issue. * docs: clarify _decompose_site_role's asymmetric legacy-role handling The role map handles legacy UserItem.Roles values in two ways depending on whether the server has a modern equivalent. SiteAdministrator, Publisher, Interactor, and ReadOnly map to their current-model equivalents; UnlicensedWithPublish, ViewerWithPublish, Guest, and SupportUser fall to license="Invalid" so the server rejects the row. Reviewers otherwise read the code and see "why does Publisher get mapped but Guest doesn't?" - the answer is server behavior, not arbitrary choice. Docstring now says so. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: accept "1"/"0" and "true"/"false" for publisher, add round-trip test Two related changes to make `_evaluate_site_role` and `_decompose_site_role` a real inverse pair: - `_evaluate_site_role` now accepts "1", "true", and "yes" for the publisher column (and, symmetrically, treats anything else as "no"). Previously only "yes" was accepted, which meant `_decompose_site_role` emitting "1" for Creator/ExplorerCanPublish would round-trip as Explorer. The set of publisher values mirrors what `_valid_attributes[publisher]` already documents as legal (["yes", "true", "1", "no", "false", "0"]), so this brings the two code paths in agreement. - Added a parametrized `test_decompose_then_evaluate_round_trips` covering every entry in `_role_map` plus the two documented label asymmetries (ServerAdministrator -> SiteAdministrator on the way back; legacy roles Publisher/Interactor/ReadOnly/SiteAdministrator folded into their modern equivalents). If either function drifts, a specific input names the broken case rather than the whole loop dying on the first mismatch. - `_decompose_site_role` docstring updated with a Round-trip note naming the two intentional asymmetries so readers do not have to reason about them from the mapping table. Full suite still passes: 884 passed, 1 skipped. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Address fresh-eyes review nits before un-drafting - Strip five non-ASCII characters (arrow + em-dashes) from docstrings and comments; project convention is ASCII-only. - create_user_from_line now passes an unknown auth value through unchanged (previously silently .get'd to None). _validate_import_ line_or_throw on the same input raises, so the two entry points no longer disagree on what counts as valid. Not addressed here (per fresh-eyes review, non-blocking): - Deprecated create_from_file's "csv" substring check remains loose (matches report.csv.bak, rejects USERS.CSV); pre-existing on a @deprecated method, out of scope for this refactor. - PR body test-plan checkbox that's actually complete: tick before un-drafting. 59 user tests pass. * Warn (don't raise) on unknown auth values during CSV import Post-merge follow-up on #1811 -- the strict behavior it introduced (create_user_from_line raises ValueError on any auth value not in _AUTH_CANONICAL) would block CSV imports against newer servers as soon as Tableau ships an auth type TSC's hardcoded list doesn't yet know about. This is the same category of stale-list problem the _set_values enum-guard bypass exists to avoid on the server-parse path. Both entry points now warn and pass the value through: - create_user_from_line: unknown values raise a UserWarning naming the value and known set, then get assigned to auth_setting as-is. If the value really is a typo, the server rejects the row when the request posts -- a slightly-later error, but the import stays possible against forward-compatible servers. - _validate_import_line_or_throw: same shape. Skips the allowlist check for the AUTH column when the value isn't in _AUTH_CANONICAL, so validate_file_for_import doesn't return the row as invalid. Server-version-aware validation would be the cleaner long-term fix here (and for the enum-guard bypass in _set_values); noted for planning, not filing an issue. Tests updated: two former "raises ValueError" cases now assert pytest.warns(UserWarning) and confirm the raw value round-trips onto UserItem.auth_setting. * Strip password-mask line: it belongs to #1862, not this PR Inadvertently pulled the password-column mask (safe_value = "***" if column == PASS else value) into this PR while restructuring the validation loop for the warn-on-unknown-auth change. The mask is #1862's core content and shouldn't sneak in through the site-role decompose PR -- reviewers on either PR would see mysterious overlap. #1862's full feature (log mask + INFO->DEBUG downgrade + _redact_password_column helper for invalid_lines sanitization) stays where it belongs, on jac/csv-import-privacy. The `column = ColumnType(i)` local rename stays because it's used by the log line's `{column.name}` format and by the AUTH branch's comparison; that's plain cleanup and doesn't overlap with #1862. --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

…-privacy # Conflicts: # CHANGELOG.md # tableauserverclient/models/user_item.py

Belt-and-braces: today PASS has an empty allowlist so the validator returns early, but if a future PR adds password-format checks (length, complexity, banned-chars) the raw password would leak via ValueError("Invalid value {item} for {column_type}"). Skip the call entirely for PASS so the invariant doesn't rely on the allowlist staying empty. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Copilot

🟡 Changes recommended

Comma-containing passwords can still leak fragments, and a regression test codifies that leakage.

1 open finding

CSV splitting leaks comma-containing passwords · New

2 resolved since last review

_redact_password_column can fail to preserve CRLF endings when the password column is the last…
Add a CRLF test where the password is the last field (e.g. "user,pass\r\n"); this is the case where…

🧠 Review effort: Lite

Co-authored-by: bcantoni <58372+bcantoni@users.noreply.github.com>

Copilot

🟡 Changes recommended

Unresolved issues may alter invalid-row data and leak password fragments from malformed CSV input.

1 open finding

Malformed CSV logs password fragments from parsed fields · New

1 resolved since last review

CSV splitting leaks comma-containing passwords

🧠 Review effort: Lite

Update password logging to mask sensitive data correctly. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

bcantoni

@jacalata this is worth another quick review from you after I accepted a few copilot suggested fixes

Copilot

🟡 Changes recommended

Passwords may still leak in quoted fields, and invalid-line formatting is not preserved.

1 open finding

Quoted passwords leak when delimiter whitespace is present · New

1 resolved since last review

Malformed CSV logs password fragments from parsed fields

🧠 Review effort: Lite

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot

🔵 Needs a closer look

Comma-containing passwords can still leak fragments through validation errors and redacted invalid-line output.

0 open findings

1 resolved since last review

Quoted passwords leak when delimiter whitespace is present

🧠 Review effort: Lite

Copilot

🟡 Changes recommended

Password data can still leak through malformed rows and quoted passwords containing newlines.

1 open finding

Physical-line parsing leaks passwords split across CSV records · New

🧠 Review effort: Lite

            line: str = csv_file.readline()
            while line and line != "":
+                # Log only the username (column 0); the rest of the line contains the password (column 1) and other PII.
+                username = line.partition(",")[0].strip()


_validate_import_line_or_throw assigned `column` twice in the loop body (leftover from the redaction diff). Also had its own inline PASS-boundary check (`column.value < PASS.value`) duplicating the same boundary logic _redact_password_column derives independently via `ColumnType.PASS.value`. Factor both into one _is_sensitive_column helper so there's a single source of truth for "is this column sensitive enough to mask."

Copilot

🔵 Needs a closer look

Unresolved moderate findings could still expose password fragments or abort malformed-row imports.

1 open issue

Physical-line parsing leaks passwords split across CSV records

1 previously missed issue

In code that hasn't changed since last review

Malformed rows can expose password fragments

tableauserverclient/models/user_item.py:584

This only masks the second parsed CSV field. A syntactically valid but malformed import row with an unquoted comma in its password, such as u,secret,tail,foo,site,yes,email, is returned as u,***,tail,..., so invalid_lines still exposes a password fragment (and later validation errors can expose shifted fragments too). Since this helper is used only for rejected rows, ambiguous rows should be replaced with a safe placeholder rather than returning the remaining parsed fields.

_{Review effort: Lite}

jacalata requested a lite review from Copilot August 17, 2026 18:50

Copilot started reviewing on behalf of jacalata August 17, 2026 18:50

View session

Copilot AI reviewed Aug 17, 2026

View reviewed changes

Comment thread tableauserverclient/models/user_item.py Outdated

Comment thread test/test_user_model.py

Merge remote-tracking branch 'origin/development' into jac/csv-import…

1c35529

…-privacy # Conflicts: # tableauserverclient/models/user_item.py # test/test_user_model.py

jacalata and others added 3 commits September 9, 2026 17:06

Merge remote-tracking branch 'origin/development' into jac/csv-import…

12ee04c

…-privacy # Conflicts: # CHANGELOG.md # tableauserverclient/models/user_item.py

Merge branch 'development' into jac/csv-import-privacy

5298991

Copilot AI lite review requested due to automatic review settings October 14, 2026 05:28

Copilot started reviewing on behalf of jacalata October 14, 2026 05:28

View session

bcantoni approved these changes Oct 14, 2026

View reviewed changes

Copilot AI reviewed Oct 14, 2026

View reviewed changes

Comment thread tableauserverclient/models/user_item.py Outdated

Copilot started work on behalf of bcantoni October 14, 2026 05:33

View session

Fix CSV-aware user password redaction

9d3e9f9

Co-authored-by: bcantoni <58372+bcantoni@users.noreply.github.com>

Copilot AI lite review requested due to automatic review settings October 14, 2026 05:36

Copilot started reviewing on behalf of jacalata October 14, 2026 05:36

View session

Copilot finished work on behalf of bcantoni October 14, 2026 05:37

Copilot AI requested a review from bcantoni October 14, 2026 05:37

Copilot AI reviewed Oct 14, 2026

View reviewed changes

Comment thread tableauserverclient/models/user_item.py Outdated

Refactor password logging for UserItem

3615baf

Update password logging to mask sensitive data correctly. Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot AI lite review requested due to automatic review settings October 14, 2026 05:46

Copilot started reviewing on behalf of jacalata October 14, 2026 05:46

View session

bcantoni approved these changes Oct 14, 2026

View reviewed changes

Copilot AI reviewed Oct 14, 2026

View reviewed changes

Comment thread tableauserverclient/models/user_item.py Outdated

Fix CSV parsing by skipping initial spaces

33361af

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot AI lite review requested due to automatic review settings October 15, 2026 22:24

Copilot started reviewing on behalf of jacalata October 15, 2026 22:24

View session

Merge branch 'development' into jac/csv-import-privacy

371e4af

Copilot AI reviewed Oct 15, 2026

View reviewed changes

Copilot AI lite review requested due to automatic review settings October 15, 2026 22:26

Copilot started reviewing on behalf of jacalata October 15, 2026 22:27

View session

Copilot AI reviewed Oct 15, 2026

View reviewed changes

Comment thread tableauserverclient/models/user_item.py

Comment on lines 539 to +542

line: str = csv_file.readline()

while line and line != "":

# Log only the username (column 0); the rest of the line contains the password (column 1) and other PII.

username = line.partition(",")[0].strip()

Copilot AI lite review requested due to automatic review settings October 19, 2026 22:03

Copilot started reviewing on behalf of jacalata October 19, 2026 22:04

View session

Copilot AI reviewed Oct 19, 2026

View reviewed changes

Navigation Menu

Repository navigation

Redact password column from CSV import logging and error output - #1862

Redact password column from CSV import logging and error output#1862
jacalata wants to merge 11 commits into
developmentfrom
jac/csv-import-privacy

jacalata commented Aug 16, 2026

Uh oh!

github-actions Bot commented Aug 16, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

jacalata commented Aug 18, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

bcantoni left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

jacalata commented Aug 16, 2026

Summary

What changes

Test plan

Uh oh!

github-actions Bot commented Aug 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

jacalata commented Aug 18, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

bcantoni left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🔵 Needs a closer look

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🟡 Changes recommended

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🔵 Needs a closer look

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

github-actions Bot commented Aug 16, 2026 •

edited

Loading