You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 751887f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(knowledge): retry the Tin projection after a database refuses the extension (#8039)
* fix(knowledge): retry the Tin projection after a database refuses the extension
A script migration can now defer: `up` throws `ScriptMigrationDeferred`, the runner
logs it, leaves the name unrecorded and runs the remaining migrations. The Tin
projection defers when the database offers `tin` but refuses to create it, so the
upgrade after the extension is permitted installs it instead of skipping it forever.
* fix(db): keep a deferred Tin projection from failing a direct run
`db:push` runs the migration file directly, where a deferral has no
migration record to leave unwritten, so a refused extension aborted the
push. The direct entry point now adopts the projection where the database
allows it and logs the refusal otherwise, while the registered runner
still sees the deferral. Also covers continuation after a deferral with a
synthetic migration list, which the registry cannot express while the only
deferring migration is its last entry.
0 commit comments