Webhook recovery test counts recurring jobs that the shared host fires after its clock moves

Ouverte
#3,409 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
58/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
csharp
Domaine
backend, testing

Piste de recherche

Start with WebhookRecoveryTests.AQueueWhoseWakeUpWasLostIsSentInOrderByTheQueueJobAndKeptByRetention and WebhookFixture.HostAsync in the FluentCMS.Plugins.Webhooks.Tests project. Run the failing test alone, then with the full project, and trace how the host clock advance and recurring job runner affect RunDueJobsAsync. Done means the test passes in a full project run on main.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:testing plugin type:bug

Problem

WebhookRecoveryTests.AQueueWhoseWakeUpWasLostIsSentInOrderByTheQueueJobAndKeptByRetention fails when the whole FluentCMS.Plugins.Webhooks.Tests project runs. It fails on main as well (checked at 034616ae on Windows arm64, SQLite). It passes when run alone or with its class.

The test expects RunDueJobsAsync to run one job, the retention it enqueued, but it ran six. The other five were content.trash.purge, jobs.retention, idempotency.retention, activity.retention and webhooks.retention, all on the default queue. WebhookFixture.HostAsync moves the host's clock forward two days and pumps. The host's own job runner then fires the recurring jobs that became due, from its maintenance loop, after the pump has finished. They are still due when the test runs, so it counts them.

Proposal

Have HostAsync wait until the recurring jobs the clock move made due have fired and run, for example by firing them itself before it pumps. Or have the test count only the jobs it enqueued.

Acceptance

  • The test passes in a full run of the project, on main
Langage dominant
C#
Étoiles
567
Forks
107
Merge moyen
1 h 19 min
PR mergées (30 j)
353

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fluentcms/FluentCMS

Toutes les issues de fluentcms/FluentCMS

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.