Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jun 9, 2025

Remove the cap on mypy and pydantic, since newer mypy are needed with our newest transformer builds. And, tell mypy to ignore this HybridChunker arg it doesn't understand since it gets handled in a non-standard way by Docling.


This is an automatic backport of pull request #616 done by Mergify.

@mergify mergify bot added CI/CD Affects CI/CD configuration testing Relates to testing release-branch ci-failure labels Jun 9, 2025
@bbrowning
Copy link
Contributor

@Mergifyio rebase

@mergify
Copy link
Contributor Author

mergify bot commented Jun 9, 2025

rebase

✅ Branch has been successfully rebased

@bbrowning bbrowning force-pushed the mergify/bp/release-v0.8/pr-616 branch from 788f2c5 to bfbb959 Compare June 9, 2025 19:49
Copy link
Contributor

@booxter booxter left a comment

Choose a reason for hiding this comment

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

Fine; the warning issue in unit tests is fixed: #664

@bbrowning
Copy link
Contributor

@Mergifyio rebase

bbrowning added 2 commits June 9, 2025 20:22
Remove the cap on mypy and pydantic, since newer mypy are needed with
our newest transformer builds. And, tell mypy to ignore this
HybridChunker arg it doesn't understand since it gets handled in a
non-standard way by Docling.

Signed-off-by: Ben Browning <[email protected]>
(cherry picked from commit 91319df)
During out coverage tests, pytest complains about an unraisable
exception coming from Docling. Normally such an exception would be
entirely ignored and unraised, but pytest is erroring out when it sees
this exception. Docling behavior changed when it cannot find tesserocr
recently by adding a garbage collection method on the tesseract model
object, and if that fails to load properly it can throw this exception
during garbage collection. However, it's a harmless exception since it
failed to load anyway so we don't really care about it erroring out
during garbage collection.

Signed-off-by: Ben Browning <[email protected]>
(cherry picked from commit 2b971b3)
@mergify
Copy link
Contributor Author

mergify bot commented Jun 9, 2025

rebase

✅ Branch has been successfully rebased

@bbrowning bbrowning force-pushed the mergify/bp/release-v0.8/pr-616 branch from bfbb959 to c1bfc37 Compare June 9, 2025 20:22
@bbrowning bbrowning merged commit d2e3990 into release-v0.8 Jun 9, 2025
20 of 22 checks passed
@bbrowning bbrowning deleted the mergify/bp/release-v0.8/pr-616 branch June 9, 2025 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD Affects CI/CD configuration ci-failure one-approval release-branch testing Relates to testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants