Accept a custom scheduling strategy in ReplayRecordingOptions
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 54/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- csharp
调研方向
Start by reading ReplayRecordingOptions, RecordCluster, and RecordClusterEntry, then trace how the scheduler strategy name and seed are written into the artifact. Check the replay recording tests for coverage of scheduler metadata. Done means an optional strategy factory can wrap the runtime's seeded strategy before the first step and the artifact records the resulting strategy's name.
由索引模型根据 Issue 内容生成。
描述
ReplayRecordingOptions selects a built-in policy through ReplaySchedulingPolicy. A consumer which needs a custom ISimulationSchedulingStrategy must therefore assign SimulationScheduler.SchedulingStrategy inside the recorded callback. The artifact then names seeded-random as its strategy (scheduler.strategy, with its schedule seed), although every recorded decision came from the custom strategy. Exact replay still works, because it consumes the recorded decisions, but the artifact misdescribes the run that produced them.
Proposal. Add an optional strategy factory to ReplayRecordingOptions, for example Func<ISimulationSchedulingStrategy, ISimulationSchedulingStrategy>, which receives the runtime's seeded strategy so a custom strategy can delegate to it. Record the resulting strategy's Name in the artifact's scheduler section. RecordCluster and RecordClusterEntry would apply the factory before the first step.
Consumer. Clog's conformance kit (ReubenBond/clog#365) explores the schedules of small concurrent windows with WindowSchedulingStrategy. Inside a window it follows a choice vector, and outside every window it delegates to the seeded strategy. Today the driver swaps the strategy inside RecordCluster's callback.
- 主要语言
- C#
- 星标
- 0
- 派生
- 0
- 平均合并
- 2 小时 32 分钟
- 30 天内合并 PR
- 23
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
ReubenBond/Clockwork 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
ReubenBond/Clockwork#73 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
ReubenBond/Clockwork#70 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
ReubenBond/Clockwork#78 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 43/100
ReubenBond/Clockwork#76 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 58/100
ReubenBond/Clockwork#69 ·
维护者通常 1 天内回复
查看 ReubenBond/Clockwork 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
martin-stromberg/FinanceManager#562 ·
维护者通常 1 天内回复
-
:eyeglasses: status: needs review needs-area-label
难度 2/5 1-3 小时 新手友好度 70/100
gitextensions/gitextensions#13469 ·
维护者通常 2 天内回复
-
[Bug]: Threading.Analyzers 0.7.79 does not load on the .NET 10 SDK (CS9057), CHT rules silently off未关闭bug regression threading
难度 2/5 1-3 小时 新手友好度 74/100
CryptoHives/Foundation#362 ·
维护者通常 1 天内回复
-
bug need-triage
难度 2/5 1-3 小时 新手友好度 65/100
Fervent-Tempo/AF-Media-Bar#321 ·