nextRunAt returns a new Date() even when it is non-recurring and should return null

[dbleier]

Pulse v1.6.7
when querying pulse.jobs()

pulse/src/job/index.ts

Line 217 in d338d77

nextRunAt: nextRunAt || new Date(),

There is a comment that this should not happen with non-recurring jobs

The retrieved job

{
  _id: {...},
  name: "schedule integration - 678980fd73095d1fc73c3036",
  data: {
    user: {...},
    body: {...},
  },
  priority: 0,
  shouldSaveResult: false,
  attempts: 0,
  backoff: null,
  lastModifiedBy: null,
  lockedAt: null,
  lastRunAt: "2025-01-16T21:59:00.000Z",
  finishedCount: 1,
  lastFinishedAt: "2025-01-16T21:59:00.008Z",
  runCount: 1,
  type: "normal",
  nextRunAt: "2025-01-16T22:00:43.448Z",
}

[dbleier]

I see the test for this has been commented out. Any idea when this will be restored?
https://github.com/pulsecron/pulse/blame/d338d771fede966f73de9a50d221d8946d132ae7/test/unit/pulse.spec.ts#L222-L232

[dbleier]

@code-xhyun what was the reason for removing this fix? And what is the reason for creating a new Date if nextRunAt is null? Is there any expected timeline when this will be fixed?

I had thought about submitting a PR for the fix, but when I saw the test commented out, I figured the fix is not as straightforward as it seems.

[code-xhyun]

Due to personal circumstances, I had difficulty managing the project. Starting this month, I plan to gradually resume overseeing it. I have also applied to renew the documentation site domain, and it is expected to be restored soon