sqlite-web 0.7.2
gitea.db
action
Create
Query
access
access_token
action
action_artifact
action_run
action_run_index
action_run_job
action_runner
action_runner_token
action_schedule
action_schedule_spec
action_task
action_task_output
action_task_step
action_tasks_version
action_variable
app_state
attachment
auth_token
badge
branch
collaboration
comment
commit_status
commit_status_index
commit_status_summary
commit_sync_log
commit_sync_status
dbfs_data
dbfs_meta
deploy_key
email_address
email_hash
external_login_user
follow
gpg_key
gpg_key_import
hook_task
issue
issue_assignees
issue_content_history
issue_dependency
issue_index
issue_label
issue_pin
issue_user
issue_watch
label
language_stat
lfs_lock
lfs_meta_object
login_source
milestone
mirror
notice
notification
oauth2_application
oauth2_authorization_code
oauth2_grant
org_user
package
package_blob
package_blob_upload
package_cleanup_rule
package_file
package_property
package_version
project
project_board
project_issue
protected_branch
protected_tag
public_key
pull_auto_merge
pull_request
push_mirror
reaction
release
renamed_branch
repo_archiver
repo_hidden_file
repo_indexer_status
repo_license
repo_redirect
repo_topic
repo_transfer
repo_unit
repository
review
review_state
secret
session
sqlite_sequence
star
stopwatch
system_setting
task
team
team_invite
team_repo
team_unit
team_user
topic
tracked_time
two_factor
upload
user
user_badge
user_blocking
user_open_id
user_redirect
user_setting
version
watch
webauthn_credential
webhook
Toggle helper tables
Structure
Content
Query
Insert
Drop
Import
Export
Delete row 31177 from action
id
31177
user_id
5
op_type
5
act_user_id
5
repo_id
82
comment_id
0
is_deleted
0
ref_name
refs/heads/main
is_private
1
content
{"Commits":[{"Sha1":"601955837
{"Commits":[{"Sha1":"601955837eb8caa25a91a2c2da96d9a06f8ea455","Message":"fix(ticket): 通知投递补认领凭据与显式重试上限\n\n领取此前只看 PENDING/FAILED，且完成回写只按 status=\"SENDING\" 匹配：进程崩在 deliver() 里的那行\n会永远停在 SENDING，没有任何路径能把它捡回来。另有一处重试上限双份常数——领取查询没有上限，\n死信判定走的是 @repo/notification-delivery 的包默认 3，两边靠巧合对齐，改任一边即静默不一致。\n\n- notifications 表加 claim_owner / claim_expires_at（两后端各一份 schema 与迁移），领取写认领、\n 完成按 claimOwner 回写并清空，与其余两个消费仓的 claim 列同形。\n- 领取前先把预算烧完的行（含认领过期仍卡在 SENDING 的）扫成死信；领取查询新增「SENDING 且\n 认领已过期」一支，并显式限定 attempts \u003c NOTIFICATION_MAX_ATTEMPTS。\n- 重试上限收敛为一个常数，同时进领取查询、死信清扫和 decideNotificationFailure。\n- 迁移不建索引：本仓迁移红线把非 CONCURRENTLY 的 CREATE INDEX 判为高危 DDL（首版实测被 exit 1\n 拦下），过期 SENDING 那一支由既有 notifications_tenant_status_next_attempt_idx 的\n (tenant_id, status) 前缀服务；要加 (tenant_id, status, claim_expires_at) 须按\n expand→migrate→contract 单独提，不混在这条加列迁移里。\n- packages/notification-delivery：未知异常不再默认可重试（模板体检失败这类确定性错误重发多少次\n 都是同一个结果），并补 NotificationTemplateError 的消息分支——缺它时 lastError 会把模板错误\n 写成「供应商不可用」。与报价仓的同名包语义就此一致。\n\n验证：pnpm check 全绿（15 道静态门禁 + lint + typecheck，含 write-guard / dual-backend /\nmigrations / write-chain）；包单测 9/9。领取与清扫 SQL 在本机 Postgres 建临时库实跑：清扫只命中\n「预算烧完 + 认领过期」那一行，领取只取到「到期 PENDING」与「认领过期 SENDING」，正确跳过活认领、\n他租户与 next_attempt_at 未到的行，临时库跑完已删。\n\n未跑：两后端新增的认领回收验收用例（NestJS/Fastify 逐条镜像）属 check:runtime 级别，需 pgvector\n的真实库 + Redis + 附件基础设施，本机 PG 无 pgvector，未硬凑环境，故本次不声称该级证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:06:27-07:00"}],"HeadCommit":{"Sha1":"601955837eb8caa25a91a2c2da96d9a06f8ea455","Message":"fix(ticket): 通知投递补认领凭据与显式重试上限\n\n领取此前只看 PENDING/FAILED，且完成回写只按 status=\"SENDING\" 匹配：进程崩在 deliver() 里的那行\n会永远停在 SENDING，没有任何路径能把它捡回来。另有一处重试上限双份常数——领取查询没有上限，\n死信判定走的是 @repo/notification-delivery 的包默认 3，两边靠巧合对齐，改任一边即静默不一致。\n\n- notifications 表加 claim_owner / claim_expires_at（两后端各一份 schema 与迁移），领取写认领、\n 完成按 claimOwner 回写并清空，与其余两个消费仓的 claim 列同形。\n- 领取前先把预算烧完的行（含认领过期仍卡在 SENDING 的）扫成死信；领取查询新增「SENDING 且\n 认领已过期」一支，并显式限定 attempts \u003c NOTIFICATION_MAX_ATTEMPTS。\n- 重试上限收敛为一个常数，同时进领取查询、死信清扫和 decideNotificationFailure。\n- 迁移不建索引：本仓迁移红线把非 CONCURRENTLY 的 CREATE INDEX 判为高危 DDL（首版实测被 exit 1\n 拦下），过期 SENDING 那一支由既有 notifications_tenant_status_next_attempt_idx 的\n (tenant_id, status) 前缀服务；要加 (tenant_id, status, claim_expires_at) 须按\n expand→migrate→contract 单独提，不混在这条加列迁移里。\n- packages/notification-delivery：未知异常不再默认可重试（模板体检失败这类确定性错误重发多少次\n 都是同一个结果），并补 NotificationTemplateError 的消息分支——缺它时 lastError 会把模板错误\n 写成「供应商不可用」。与报价仓的同名包语义就此一致。\n\n验证：pnpm check 全绿（15 道静态门禁 + lint + typecheck，含 write-guard / dual-backend /\nmigrations / write-chain）；包单测 9/9。领取与清扫 SQL 在本机 Postgres 建临时库实跑：清扫只命中\n「预算烧完 + 认领过期」那一行，领取只取到「到期 PENDING」与「认领过期 SENDING」，正确跳过活认领、\n他租户与 next_attempt_at 未到的行，临时库跑完已删。\n\n未跑：两后端新增的认领回收验收用例（NestJS/Fastify 逐条镜像）属 check:runtime 级别，需 pgvector\n的真实库 + Redis + 附件基础设施，本机 PG 无 pgvector，未硬凑环境，故本次不声称该级证据。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"hillao@juhailaoluodeMacBook-Pro.local","AuthorName":"juhailaoluo pro","CommitterEmail":"hillao@juhailaoluodeMacBook-Pro.local","CommitterName":"juhailaoluo pro","Timestamp":"2026-09-18T16:06:27-07:00"},"CompareURL":"luoanwu/juhai-ai-work-order-system/compare/7c4b197f018b02f5ed675758af3f5be5dbd1de02...601955837eb8caa25a91a2c2da96d9a06f8ea455","Len":1}
...
created_unix
1789772841
Delete
Cancel