fix: resolve issue #1400 - Initialize lastSeenAt Date on Signal Creation

[sonusharma6-dsa]

Closes #1400

[coderabbitai]

Warning

Review limit reached

@sonusharma6-dsa, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 16 minutes and 53 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1a44793b-fa04-4ce4-90da-0fbe6c78762a

📥 Commits

Reviewing files that changed from the base of the PR and between e15a36c and ac6b95d.

📒 Files selected for processing (2)

• server/src/module/ats/__tests__/ats.service.test.ts
• server/src/module/signals/signals.service.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Hi @sonusharma6-dsa, thanks for contributing to InternHack! 🎉

I have automatically:

• 👤 Assigned this PR to you.
• 🏷️ Applied the gssoc:approved label.

Our workflows will now analyze your changes to classify:

• 📈 PR Difficulty: level:*
• 🧩 PR Type: type:*
• 🌟 PR Quality: quality:*

Tip

Ensure your PR description references the issue it resolves (e.g. Closes #123). This allows the bot to inherit any additional labels from that issue!

Happy coding! 🚀

[Sachinchaurasiya360]

Code Review — PR #1401: Initialize lastSeenAt on signal creation

Hi @sonusharma6-dsa, straightforward and correct fix.

---

✅ Looks good

Adding lastSeenAt: new Date() to both fundingSignal.create and the manual creation path ensures new signals don't have a null lastSeenAt. The fix is minimal and targeted — no unrelated changes, no risk of side effects.

One minor note: new Date() in a server-side context is fine since lastSeenAt will always represent the current server time, which is what you want for "when was this signal last seen in a scrape run".

Approved.