You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docling-parse v3.0.0 was released on 9 December 2024 and it contained a large number of breaking changes, namely to its syntax. These syntax changes broke SDG (and therefore some InstructLab logic in general). See relevant issue here: instructlab/instructlab#2765
Furthermore, it appears that the main docling package was updated ~7 hours afterward to use the new docling-parse v3.0.0 release. We can see that the v2.10.0docling release makes these changes effective.
Current Workaround
To temporarily workaround this issue, I created #434 to force docling-parse>=2.0.0,<3.0.0, and to force docling<=2.8.3. In other words, this change will temporarily ensure we don't use docling-parse's v3's breaking changes either through directly importing docling-parse or indirectly through docling.
Goals
We eventually want to migrate to the newer v3 syntax so that we can utilize newer versions and newer functionality, as more is added.
The text was updated successfully, but these errors were encountered:
One more point in favor of upgrading the docling dependency.
We want to integrate the docling-haystack package in instructlab to leverage its Haystack components within the RAG pipelines. However, a dependency conflict is currently preventing us from proceeding with the integration:
instructlab-sdg 0.6.2 depends on docling<=2.8.3 and >=2.4.2
docling-haystack 0.1.1 depends on docling<3.0.0 and >=2.9.0
Background / Context
docling-parse
v3.0.0 was released on 9 December 2024 and it contained a large number of breaking changes, namely to its syntax. These syntax changes broke SDG (and therefore some InstructLab logic in general). See relevant issue here: instructlab/instructlab#2765Furthermore, it appears that the main
docling
package was updated ~7 hours afterward to use the newdocling-parse
v3.0.0 release. We can see that the v2.10.0docling
release makes these changes effective.Current Workaround
To temporarily workaround this issue, I created #434 to force
docling-parse>=2.0.0,<3.0.0
, and to forcedocling<=2.8.3
. In other words, this change will temporarily ensure we don't usedocling-parse
's v3's breaking changes either through directly importingdocling-parse
or indirectly throughdocling
.Goals
We eventually want to migrate to the newer v3 syntax so that we can utilize newer versions and newer functionality, as more is added.
The text was updated successfully, but these errors were encountered: