Accept a custom scheduling strategy in ReplayRecordingOptions

Abierto
#77 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
54/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
0
Forks
0
Merge medio
2 h 32 min
PR fusionados (30 d)
23

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ReubenBond/Clockwork

Todos los issues de ReubenBond/Clockwork

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.