merge: development into feature branch#303
Merged
ldyrmishiritech merged 23 commits intochore/optimize-docker-compose-v2from Feb 17, 2026
Merged
merge: development into feature branch#303ldyrmishiritech merged 23 commits intochore/optimize-docker-compose-v2from
ldyrmishiritech merged 23 commits intochore/optimize-docker-compose-v2from
Conversation
…and enhancing validation logic
…sist into edyrkaj/feat-ml-models-upload
…sist into edyrkaj/feat-ml-models-upload
…sist into edyrkaj/feat-ml-models-upload
…my values The previous .env.example contained placeholder values that looked like real credentials (e.g., OAIKEY, GOOGLEKEY). This creates two risks: 1. Developers might mistake them for working values and not change them 2. Real credentials could be accidentally committed if they follow the same pattern Changes: - Replace API key placeholders with clearly fake values (sk-xxx...) - Add descriptive comments indicating values must be replaced - Use consistent placeholder patterns (xxx..., your-...) - Disable optional services by default (USE_OPIK=FALSE) - Add section headers for better organization Fixes potential security issue where developers might commit real credentials following the same pattern as the placeholders.
…r and thread scoped RAG (#287)
…sist into edyrkaj/feat-ml-models-upload
…ronment and requirements files (#288)
…sist into edyrkaj/feat-ml-models-upload
## Description <!-- Provide a clear and concise description of your changes --> ## Type of Change <!-- Mark the relevant option with an 'x' --> - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 🏗️ Core implementation (refactoring, architectural changes) - [ ] 💡 Improvement (enhancement to existing functionality) - [ ] 📚 Documentation update - [ ] 🔧 Configuration change - [ ] 🧪 Test update ## Changes Made <!-- Describe the changes in detail --> - [ ] Change 1 - [ ] Change 2 - [ ] Change 3 ## Testing <!-- Describe the tests you ran to verify your changes --> - [ ] Unit tests - [ ] Integration tests - [ ] Manual testing - [ ] E2E tests (if applicable) ## Ritech Contribution Checklist - [ ] My code follows GenAssist's style guidelines (see [CONTRIBUTING.md](../CONTRIBUTING.md)) - [ ] I have performed a self-review of my code - [ ] I have made corresponding changes to the documentation - [ ] I have added tests that prove my fix/feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published - [ ] Multi-tenant considerations addressed (if applicable) ## Related Issues <!-- Link related issues using keywords (e.g., "Closes #123", "Fixes #456") --> Closes #<!-- issue number --> ## Screenshots (if applicable) <!-- Add screenshots to help explain your changes --> ## Additional Notes <!-- Add any other context about the PR here --> --- **Note**: This PR follows Ritech's contribution guidelines for GenAssist. For questions, refer to [CONTRIBUTING.md](../CONTRIBUTING.md) or contact the Ritech team.
Get table names, column names and data types.
…sist into edyrkaj/feat-ml-models-upload
## Description - Updated OpenAPI schema to include `original_filename` and `pkl_file_url` in file-related responses. - Refactored file upload process to utilize a new file manager service for improved file handling. - Added error handling for file manager initialization failures. - Introduced new utility function for downloading files in the frontend. - Updated ML model interfaces and components to support new file URL and filename fields. This commit improves the overall file management capabilities and enhances the user experience when handling file uploads and downloads. <!-- Provide a clear and concise description of your changes --> ## Type of Change <!-- Mark the relevant option with an 'x' --> - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [x] ✨ New feature (non-breaking change which adds functionality) - [x] 🏗️ Core implementation (refactoring, architectural changes) - [x] 💡 Improvement (enhancement to existing functionality) - [ ] 📚 Documentation update - [ ] 🔧 Configuration change - [ ] 🧪 Test update
## Description Retrieve a summary of the DB schema using a single SQL command. This summary includes the table names, column names and column data types. ## Type of Change - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 🏗️ Core implementation (refactoring, architectural changes) - [X] 💡 Improvement (enhancement to existing functionality) - [ ] 📚 Documentation update - [ ] 🔧 Configuration change - [ ] 🧪 Test update
…my values (#286) The current `.env.example` contains placeholder values that look like real credentials (e.g., `OAIKEY`, `GOOGLEKEY`). This creates two risks: 1. Developers might mistake them for working values and not change them 2. Real credentials could be accidentally committed if they follow the same pattern ## Changes - Replace API key placeholders with clearly fake values (`sk-xxx...`, `hf_xxx...`) - Add descriptive comments indicating values must be replaced - Use consistent placeholder patterns (`xxx...`, `your-...`) - Disable optional services by default (`USE_OPIK=FALSE`) - Add section headers for better organization ## Security Impact Fixes potential security issue where developers might commit real credentials following the same pattern as the placeholders. The new format makes it obvious these are dummy values that must be replaced. ## Testing - [x] Verified no actual secrets were used - [x] Placeholders follow industry standard patterns (OpenAI keys start with `sk-`, HuggingFace with `hf_`) - [x] Application will fail to authenticate with dummy values (expected behavior)
ldyrmishiritech
merged commit 5898107
into
chore/optimize-docker-compose-v2
6 checks passed
github-actions
bot
added
backend
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
4 participants
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.
Description
Type of Change
Changes Made
Testing
Ritech Contribution Checklist
Related Issues
Closes #
Screenshots (if applicable)
Additional Notes
Note: This PR follows Ritech's contribution guidelines for GenAssist. For questions, refer to CONTRIBUTING.md or contact the Ritech team.