Fix uvicorn command in custom-server README#38
Merged
renardeinside merged 1 commit intodatabrickslabs:masterfrom Jun 18, 2025
Merged
Fix uvicorn command in custom-server README#38renardeinside merged 1 commit intodatabrickslabs:masterfrom
renardeinside merged 1 commit intodatabrickslabs:masterfrom
Conversation
The command had two issues: 1. Used 'custom-server' instead of 'custom_server' (Python modules use underscores) 2. Referenced ':mcp' instead of ':app' (the FastAPI instance is named 'app') 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
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
2 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.
The command had two issues:
🤖 Generated with Claude Code
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
README update.
How is this PR tested?
Only README.md is changed
Does this PR require documentation update?
No. The PR is itself a documentation update.
Release Notes
Is this a user-facing change?
Fixed bug in custom-server README.
How should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notes