Skip to content

Correct the ingest failure-check guidance on the Python best practices page - #486

Merged
g-despot merged 1 commit into
mainfrom
docs/fix-ingest-has-errors-prose
Jul 30, 2026
Merged

Correct the ingest failure-check guidance on the Python best practices page#486
g-despot merged 1 commit into
mainfrom
docs/fix-ingest-has-errors-prose

Conversation

@g-despot

@g-despot g-despot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #484, which merged one commit before its review fix landed.

Points readers at result.errors as the failure check for data.ingest(). One line, prose only.

@orca-security-eu orca-security-eu Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed SAST high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

The ingest() path reports failures through its return value rather than a batching context, so name result.errors as the check to use.
@g-despot
g-despot force-pushed the docs/fix-ingest-has-errors-prose branch from bb94d29 to 1f923c0 Compare July 30, 2026 09:09
@g-despot
g-despot merged commit b8dd619 into main Jul 30, 2026
13 checks passed
@g-despot
g-despot deleted the docs/fix-ingest-has-errors-prose branch July 30, 2026 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant