better handling for stuck tasks: clear hanging tasks and avoid running tasks that were scheduled for a long time ago

[vkarpov15]

No description provided.

[Copilot]

Pull Request Overview

This PR improves task handling by implementing better timeout mechanisms to prevent stuck tasks. It introduces two new timeout features: scheduling timeouts for tasks that wait too long to start, and execution timeouts for tasks that run too long.

• Adds schedulingTimeoutAt and timeoutAt fields to handle different types of task timeouts
• Implements automatic expiration of timed-out tasks with new status types (timed_out, scheduling_timed_out)
• Refactors repeating task logic into a shared helper function

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.

File	Description
src/taskSchema.js	Core implementation of timeout handling, new schema fields, and refactored task execution logic
test/task.test.js	Comprehensive test coverage for timeout scenarios and repeating task behavior
package.json	Added ESLint dependencies for code quality
eslint.config.js	ESLint configuration for the project

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Magic number 10 * 60 * 1000 (10 minutes) is repeated multiple times. Consider extracting this into a named constant like DEFAULT_SCHEDULING_TIMEOUT_MS to improve maintainability.

[Copilot]

Same magic number 10 * 60 * 1000 (10 minutes) should be extracted into a constant. Consider creating DEFAULT_EXECUTION_TIMEOUT_MS for consistency.

[Copilot]

Another instance of the magic number 10 * 60 * 1000. This should use the same constant as the other timeout values.

Suggested change

	schedulingTimeoutAt: scheduledAt.valueOf() + 10 * 60 * 1000,
	schedulingTimeoutAt: scheduledAt.valueOf() + time.TEN_MINUTES_MS,

[Copilot]

Fourth occurrence of the magic number. All instances of 10 * 60 * 1000 should reference the same constant.