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 20882 from action
id
20882
user_id
5
op_type
5
act_user_id
5
repo_id
72
comment_id
0
is_deleted
0
ref_name
refs/heads/feat/multi-role-assignment
is_private
0
content
{"Commits":[{"Sha1":"a3dd4914e
{"Commits":[{"Sha1":"a3dd4914eeaa83dc5ac32695829417bdf1faf44a","Message":"test(web): E2E 覆盖内部售后建单表单提交(C29 回潮回归锁)\n\n上一提交(bf77845)修了内部售后工作台建单表单静默无 POST 的 bug,但 E2E 此前\n只覆盖公开客户表单(public-after-sales-create)的提交,内部工作台表单\n(after-sales-create-card)提交路径长期零覆盖——正是这个盲区让 C29 二次复发\n逃过所有门禁。\n\n本回归锁在履约闭环用例末尾走内部表单真实提交:选订单→联动带出商品→填量与原因→\n点「提交售后申请」,用 waitForResponse 捕 POST /api/after-sales。C29 回潮的形态是\n「提交静默无请求」,届时 waitForResponse 超时即红。状态断言用 \u003c500 而非 pin 201:\n本用例前序公开售后已在同一交付订单消耗过退货额度,内部再建可能 201 或 409,\n两者都证明「客户端校验通过 + POST 真发出 + 服务端处理」这条链通畅。\n\n负向验证(本会话):撤掉 AfterSalesWorkbench 挂载预生成后重跑 check:ui,本断言在\nwaitForResponse 处超时判红(error-context 确认按钮 active、表单已填、无 response);\n恢复修复后 12/12 复绿。报告 status=passed,绑定 bf77845。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-05T17:46:57-07:00"}],"HeadCommit":{"Sha1":"a3dd4914eeaa83dc5ac32695829417bdf1faf44a","Message":"test(web): E2E 覆盖内部售后建单表单提交(C29 回潮回归锁)\n\n上一提交(bf77845)修了内部售后工作台建单表单静默无 POST 的 bug,但 E2E 此前\n只覆盖公开客户表单(public-after-sales-create)的提交,内部工作台表单\n(after-sales-create-card)提交路径长期零覆盖——正是这个盲区让 C29 二次复发\n逃过所有门禁。\n\n本回归锁在履约闭环用例末尾走内部表单真实提交:选订单→联动带出商品→填量与原因→\n点「提交售后申请」,用 waitForResponse 捕 POST /api/after-sales。C29 回潮的形态是\n「提交静默无请求」,届时 waitForResponse 超时即红。状态断言用 \u003c500 而非 pin 201:\n本用例前序公开售后已在同一交付订单消耗过退货额度,内部再建可能 201 或 409,\n两者都证明「客户端校验通过 + POST 真发出 + 服务端处理」这条链通畅。\n\n负向验证(本会话):撤掉 AfterSalesWorkbench 挂载预生成后重跑 check:ui,本断言在\nwaitForResponse 处超时判红(error-context 确认按钮 active、表单已填、无 response);\n恢复修复后 12/12 复绿。报告 status=passed,绑定 bf77845。\n\nCo-Authored-By: Claude Opus 5 \u003cnoreply@anthropic.com\u003e\n","AuthorEmail":"luoguoguo@gmail.com","AuthorName":"luoguoguo","CommitterEmail":"luoguoguo@gmail.com","CommitterName":"luoguoguo","Timestamp":"2026-08-05T17:46:57-07:00"},"CompareURL":"luoanwu/juhai-quotation-system/compare/bf778452d29f9965677f5d7eafdbd98843ef0ac6...a3dd4914eeaa83dc5ac32695829417bdf1faf44a","Len":1}
...
created_unix
1785977229
Delete
Cancel