Refactor: Restore MCP server, CLI debug commands, and FlowAnalyzer fu…#1
Merged
Refactor: Restore MCP server, CLI debug commands, and FlowAnalyzer fu…#1
Conversation
…nctionality - MCP Server: Uncommented main server logic in `mcp/server.py` to restore functionality of `alice mcp-server`. - CLI: Merged debug command handling from `main_original` into active `main` in `cli/main.py` to restore debug command operations. - FlowAnalyzer: Uncommented core analytical methods in `workflows/composition/flow_analyzer.py` to restore vision-based timeline analysis capabilities. - Verified that key mixins (`StatisticsMixin`, `FileOperationsMixin`) already use the `TYPE_CHECKING` pattern for attribute type hinting, so no changes were needed for that specific sub-task.
Applied various fixes to address YAML linting issues reported by GitHub Actions:
- Added '---' document starts to numerous YAML files.
- Removed trailing spaces and ensured final newlines in several config files.
- Corrected spacing within Helm template braces `{{...}}`.
- Addressed line length violations by reformatting or using block scalars.
- Adjusted indentation for navigation items in `mkdocs.yml` and list items in some Helm templates.
- Corrected bracket spacing in GitHub workflow files.
Note: Some ambiguous indentation errors reported by the linter were handled with best-effort corrections or deferred if the existing structure appeared standard. Modification attempts for newline issues in `.yamllint` and `docker-compose.yml` were unsuccessful with available tools and may require manual review.
- Replaced the non-existent `gaurav-nelson/bandit-action@v1` with the official `PyCQA/bandit-action@v1`. - Configured the new action with parameters derived from the previous manual bandit execution (targets, severity, confidence, skips). - Removed the redundant manual `Run Bandit` script block from the `security-scan` job to consolidate Bandit execution into a single step.
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
This commit includes targeted fixes for yamllint errors identified in the latest CI run: - Helm Templates: Indented initial Helm conditional blocks in various template files (serviceaccount, secret, configmap, database, networkpolicy) to resolve L2C3 syntax errors. Applied `|-` for certain multi-line `include` calls in `service.yaml` and `deployment.yaml`. - values.yaml: Adjusted indentation for `databaseAccess.enabled`. - deployment.yaml: Deferred direct fix for a suspect `replicas` indentation error, focused on `labels` formatting. - pooler-crd.yaml: Adjusted `schema:` block indentation. - tests.yml: Increased indentation for all `steps:` list items. Corrected Bandit action to PyCQA version. - release.yml: Further refactored long `echo` commands to fix line length issues. - security.yml: Corrected spacing for inline comments.
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
1 participant
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.
…nctionality
mcp/server.pyto restore functionality ofalice mcp-server.main_originalinto activemainincli/main.pyto restore debug command operations.workflows/composition/flow_analyzer.pyto restore vision-based timeline analysis capabilities.StatisticsMixin,FileOperationsMixin) already use theTYPE_CHECKINGpattern for attribute type hinting, so no changes were needed for that specific sub-task.Pull Request: January 2025 Feature Release
Summary
This PR represents a major feature release for AliceMultiverse, transforming it from a media organizer into a comprehensive AI creative workflow orchestrator.
Changes
🎯 Major Features
1. Prompt Management System
2. Advanced Transitions Suite (5 Effects)
3. Google Veo 3 Integration
📚 Documentation
🛠️ Technical Improvements
Testing
Unit Tests
Integration Tests
Manual Testing
Breaking Changes
None. All changes are additive.
Dependencies
New Dependencies
Updated Dependencies
Deployment Notes
FAL_KEYPerformance Impact
Security Considerations
Documentation
Added
/docs/user-guide/prompt-management-guide.md/docs/user-guide/veo3-video-generation-guide.md/docs/user-guide/[5 transition guides].md/docs/QUICK_REFERENCE_2025.md/docs/TROUBLESHOOTING.md/docs/DEPLOYMENT_CHECKLIST.mdUpdated
README.md- New features and examplesROADMAP.md- Completed items markedCHANGELOG.md- Full release detailsChecklist
Screenshots/Examples
Prompt Management
Veo 3 Generation
Transition Analysis
alice transitions matchcuts shot1.jpg shot2.jpg shot3.jpg # Found 3 match cuts with 87% confidenceRelated Issues
Additional Notes
This release represents 3 weeks of intensive development, adding professional-grade creative tools while maintaining the simplicity and personal nature of the project. All features have been tested in real workflows and are ready for daily use.
Ready for merge: ✅ All checks passed