Skip to content

fix(task-registry): use dedicated Cancelled status instead of Expired… - #13

Merged
cybermax4200 merged 1 commit into
ecotask-network:mainfrom
Escelit:fix/cancelled-task-status
Jul 13, 2026
Merged

fix(task-registry): use dedicated Cancelled status instead of Expired…#13
cybermax4200 merged 1 commit into
ecotask-network:mainfrom
Escelit:fix/cancelled-task-status

Conversation

@Escelit

@Escelit Escelit commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Problem

When a creator cancels a task, cancel_task sets the status to TaskStatus::Expired, making it impossible to distinguish between a task that timed out and one that was deliberately cancelled. Indexers, UIs, and analytics will misreport cancellations as expirations.

Changes

  • storage.rs: Added Cancelled variant to TaskStatus enum
  • registry.rs: Updated cancel_task to set TaskStatus::Cancelled instead of TaskStatus::Expired
  • Added two new tests confirming complete_task and expire_task reject Cancelled tasks
  • Updated existing test_cancel_task_by_creator assertion to expect Cancelled

Both complete_task and expire_task already reject non-Active tasks via their task.status != TaskStatus::Active guard — no additional logic was needed.

Closes #3

… for cancel_task

Add Cancelled variant to TaskStatus enum so that creator-initiated
cancellations are distinguishable from natural expirations. Both
complete_task and expire_task already reject non-Active tasks via their
existing status guard.

Closes ecotask-network#3
@cybermax4200
cybermax4200 merged commit c49278e into ecotask-network:main Jul 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

task-registry: cancel_task sets status to Expired instead of a dedicated Cancelled variant

2 participants