Fix multiple issues with embedding storage and export#15
Merged
caufieldjh merged 8 commits intoMar 6, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request improves the robustness and flexibility of the embedding generation and export utilities, especially when working with CurateGPT and DuckDB backends. It addresses inconsistencies in backend result formats, enhances error handling, and expands test coverage to ensure reliable CSV export and embedding workflows. Additionally, it introduces integration test support and refines the CI workflow to better handle optional, external-service-dependent tests.
Enhancements to embedding export and generation:
_normalize_store_resulthelper to handle different result shapes returned by CurateGPT backends (dicts and tuples), ensuring consistent document extraction for CSV export.export_embeddings_to_csvto infer field names from document data if the backend returns empty field names, preventing export failures and ensuring all relevant fields are included. Also, now uses the "duckdb" backend explicitly. [1] [2]Testing improvements:
Continuous Integration and configuration:
Minor code and logging improvements:
These changes make the embedding utilities more reliable and adaptable to backend changes, and ensure that both local and CI testing are robust and maintainable.