Repository navigation
feat(backend): implement async job flow and real gRPC integration - #27
Merged
Merged
Conversation
…bağlantısı ve iyileştirmeler
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
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.
July 21-22-23 Updates: API Gateway Async Job Flow, Real gRPC .
Description
Summary
/enhanceand/enhance/batchnow run a real async job flow instead of a fake 202 response: QUEUED → RUNNING → COMPLETED/FAILED in Redis, result is queried viaGET /enhance/{job_id}./healthand/modelsare now wired to realHealth/ListModelsgRPC calls (static mock removed).UNAVAILABLE./metrics, route-based upload size limit (413), graceful shutdown (Redis/gRPC won't close on SIGINT/SIGTERM until background jobs finish).api/openapi.yamlgenerated;JobStatuscomment incommon.protoupdated to match the async model.govulncheck.Out of Scope
services/ml/inference_server(Python gRPC server) is not included in this PR and has not been written yet — since the gateway currently has no counterpart,/health,/models, and jobs will return "unreachable/failed". This is expected.Test Plan
go build ./...,gofmt -l .,go vet ./...— clean/enhance→ 202 → job recorded, 404 for non-existent job, 413 for files over 25MB, correct error message when gRPC is absent for/health+/models, CORS with allowed/denied origin