Skip to content

fix: handle RuntimeError when checking if we can use pdf split mode #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 6, 2024

Conversation

awalker4
Copy link
Collaborator

@awalker4 awalker4 commented Aug 6, 2024

Certain environments, for instance the 3.10 ingest test, throw a RuntimeError: There is no current event loop in thread 'asyncio_0' when we try to check if we're able to use the splitting code. In this case, return False so we can fallback to non split mode.

Once this is merged, I can regenerate the client to publish 0.25.4.

Certain environments throw a `RuntimeError: There is no current event loop in thread 'asyncio_0'`
when we try to check if we're able to use the splitting code. In this case, return False so we can
fallback to non split mode.
@awalker4 awalker4 requested review from MthwRobinson and scanny August 6, 2024 18:58
@awalker4 awalker4 enabled auto-merge (squash) August 6, 2024 19:20
@awalker4 awalker4 requested a review from Coniferish August 6, 2024 19:24
Copy link
Contributor

@Coniferish Coniferish left a comment

Choose a reason for hiding this comment

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

Approving, but can we note in a comment in the pr or the code what environments (if we know) this error is raised in?

@awalker4 awalker4 merged commit f9cc36f into main Aug 6, 2024
7 checks passed
@awalker4 awalker4 deleted the fix/no-event-loop-error branch August 6, 2024 19:47
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.

2 participants