-
Notifications
You must be signed in to change notification settings - Fork 55
LCORE-380: regenerated schema #275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tisnik
merged 1 commit into
lightspeed-core:main
from
tisnik:lcore-380-regenerated-schema
Jul 23, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
❓ Verification inconclusive
Clarify metrics response format & hard-code the correct media type
Prometheus/OpenMetrics scrapers expect the response to be served under the
text/plain; version=0.0.4(orapplication/openmetrics-text) content-type.Keeping it as a generic
text/plaincan break auto-discovery and disables content-negotiation.Consider also specifying a
503error response for parity with the other health endpoints.and optionally append:
"responses": { "200": { … }, + "503": { + "description": "Service Unavailable" + } }Clarify metrics response media type & add 503 response
Prometheus/OpenMetrics scrapers require the exposition format to be served under
text/plain; version=0.0.4(orapplication/openmetrics-text) rather than a generictext/plain. Without this, auto-discovery and content-negotiation may break. Also, for consistency with other health endpoints, add a503 Service Unavailableresponse.• File: docs/openapi.json
• Lines: ~596–618
"/metrics": { "get": { "tags": [ "metrics" ], "summary": "Metrics Endpoint Handler", "description": "Handle request to the /metrics endpoint.", "operationId": "metrics_endpoint_handler_metrics_get", "responses": { - "200": { - "description": "Successful Response", - "content": { - "text/plain": { - "schema": { - "type": "string" - } - } - } - } + "200": { + "description": "Successful Response", + "content": { + "text/plain; version=0.0.4": { + "schema": { + "type": "string" + } + } + } + }, + "503": { + "description": "Service Unavailable" + } } } }📝 Committable suggestion
🤖 Prompt for AI Agents