opensabre / opensabre/base-sysadmin
fix: 完整错误码快照同步时收敛已删除条目
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 4h 24m
- Merged PRs (30d)
- 11
Description
问题
应用上报“完整快照”时目前仅 upsert 当前条目，不会处理本次快照中已消失的旧错误码，目录会长期残留失效数据。
工作项
- 明确定义快照版本、owner/scope 与删除语义
- 对同一 owner 的缺失条目标记失效或安全删除
- 避免部分失败、乱序快照误删有效数据
- 增加审计与回滚/恢复策略
验收标准
- 删除应用错误码后再次完整同步，目录状态可正确收敛
- 公共错误码及其他应用条目不被误处理
- 并发和乱序场景有测试覆盖
依赖
- opensabre/opensabre-framework#35
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the complete-snapshot synchronization path and the dependency opensabre/opensabre-framework#35; the issue names no files or entry points. Define how snapshot versions, owner/scope, deletion, partial failures, and ordering interact before changing behavior. Done means stale entries converge safely, public and unrelated application codes remain intact, and concurrency and out-of-order cases have tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100