feat(generator): wire production AI image runtime - #67
Open
JuhaoChen666 wants to merge 6 commits into
Open
Conversation
|
@JuhaoChen666 is attempting to deploy a commit to the KurodaKayn's projects Team on Vercel. A member of the Team first needs to authorize it. |
![fennoai[bot]](https://avatars.githubusercontent.com/in/1924301?s=60&v=4){kind=small}
| _ = sqlDB.Close() | ||
| return nil, fmt.Errorf("app: initialize database tables: %w", err) | ||
| } | ||
| if err := InitRiver(ctx, cfg.DSN); err != nil { |
There was a problem hiding this comment.
River migrations are run against cfg.DB.DSN here, but the River client is configured from cfg.Queue.DatabaseURL in InitTask/newQueue. If queue.databaseURL points at a separate Postgres database, startup migrates the app DB and then starts the queue against an unmigrated DB, leaving the river_* tables missing where River actually runs. Please migrate the queue database URL, or enforce that both DSNs must be the same.
JuhaoChen666
force-pushed
the
feat/generator-runtime
branch
from
August 3, 2026 06:47
76fa56f to
a03fac7
Compare
The example placed qiniu under qna, which strict configuration decoding rejects. Move qiniu to the top level and cover loading the checked-in example configuration. This makes the startup template usable and resolves the reported configuration failure.
The configured QNA transport needs regression coverage for both generation modes. Verify endpoint selection, authorization, model parameters, references, and response decoding. This protects text-to-image and reference-image request compatibility.
The task queue requires River tables before workers and outbox dispatch can run. Create a temporary pgx pool and apply pending River migrations after application tables. Startup now prepares the complete database schema for queued generation jobs.
Generation routes need configured queue, image provider, and asset dependencies in production. Build the PostgreSQL workspace, QNA executor, task manager, and upload manager from application config. The thin server entry point now starts a usable asynchronous image generation pipeline.
JuhaoChen666
force-pushed
the
feat/generator-runtime
branch
from
August 3, 2026 09:14
7e8e089 to
39e5f79
Compare
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.
Feature Description
config.yamlas the local default while allowingHOLONIC_ASSET_CONFIGto select another configuration file.qiniunesting so strict configuration decoding succeeds.Implementation Approach
InitServerFromConfigwhile keepingmainminimal.Testing
go test ./... -count=1go test -tags=integration ./internal/router -run 'TestProject.*PostgreSQL' -count=1/Users/lx/go/bin/gopls check $(rg --files core-api -g '*.go' | sort)Follow-ups
RunReader.issue