🛠️ fix: Enhance Error Logging, Update Dependencies, and Optimize NLTK Setup #106
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.
Summary
I enhanced error logging with traceback throughout the application, updated dependencies for
unstructured
andlangchain
core packages, adjusted Dockerfiles to pre-download NLTK data and disable Unstructured analytics, and removed the version specification fromdocker-compose.yaml
.main.py
to aid in debugging and error tracking.unstructured
andlangchain
core packages to the latest versions inrequirements.txt
andrequirements.lite.txt
.Dockerfile
andDockerfile.lite
to download NLTK data during build time, preventingunstructured
from downloading packages at runtime.NLTK_DATA
environment variable to/app/nltk_data
in Dockerfiles for consistent NLTK data path.SCARF_NO_ANALYTICS=true
in Dockerfiles.docker-compose.yaml
to utilize the default version.Relevant GitHub references:
Change Type
Testing
I tested the changes by:
docker-compose.yaml
to ensure there are no Docker-related issues.Test Configuration:
Checklist