fix: Add comprehensive dependency conflict resolution and troubleshooting #465
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.
Problem
Issue #336 reports critical dependency conflicts affecting fine-tuning workflows:
The Conflict:
protobuf==4.xprotobuf>=5.xUser Impact:
Multiple users reported this issue blocking their fine-tuning work.
Solution
1. Created Comprehensive TROUBLESHOOTING.md
Protobuf Conflicts Section:
protobuf==4.25.3)Platform-Specific Issues:
grainpackage exclusion handling2. Updated pyproject.toml
Added protobuf version constraint:
"protobuf>=4.25.3,<6.0.0"This provides a compatible range while documenting that users needing specific stacks should use separate environments.
3. Updated README.md
Added link to troubleshooting guide in Contributing section.
Testing
✅ Validated Solutions:
protobuf==4.25.3with both TensorFlow and Transformers✅ Documentation Review:
Impact
Benefits
Community Validation
Related Issues
Resolves #336
Checklist: