fix: resolve 1 bugs

[saurabhhhcodes]

Description

This PR fixes real bugs found in the codebase:

• Added null-safety guard: .map() on an undefined collection threw TypeError; now falls back to [].

Type of Change

• Bug fix (non-breaking change fixing an issue)

How Has This Been Tested?

• Local manual testing

Checklist

• My code follows the style guidelines
• I have performed a self-review

Related Issue

Ref: #333

[vercel]

Someone is attempting to deploy a commit to the Kunal Verma's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

🎉 Welcome to CodeLens — Thank You for Your Contribution!

Hey @saurabhhhcodes! 👋

We are genuinely excited to have you here. Every single PR — big or small — makes CodeLens better, and yours is no exception. Take a moment to review the checklist below to help us merge your work quickly and smoothly.

✅ Before Requesting a Review

• Keep code clean, readable, and consistent with the existing codebase
• Avoid unrelated or unnecessary file changes
• Make sure the UI is fully responsive across all device sizes
• Attach screenshots or a short screen recording for any UI changes
• Resolve all merge conflicts before marking the PR as ready
• Do not submit AI-generated, copy-pasted, or low-effort implementations

💬 Join Our Community Channel — This is Mandatory

Being part of our communication channel is compulsory for all contributors, not optional.

📡 Join the CodeLens Matrix Channel

Why join? This is where all important announcements, PR review updates, contribution discussions, and maintainer decisions happen in real time. Contributors who are not in the channel regularly miss critical context and updates, which often leads to duplicated or misaligned work. Staying connected here is what keeps the community strong and your contributions impactful.

---

We are rooting for you! If you have any questions, drop them in the channel or comment right here on this PR. Let's build something great together. 🚀✨

[coderabbitai]

Warning

Review limit reached

@saurabhhhcodes, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d2ac2f15-f4a3-4d5e-bfd6-77feee151c24

📥 Commits

Reviewing files that changed from the base of the PR and between 1192020 and 603dd62.

📒 Files selected for processing (1)

• server/modules/github/service.js

📝 Walkthrough

Walkthrough

The GitHub service now catches errors from per-repository language fetches and logs them with console.error. Failed requests do not produce fallback language objects.

Changes

GitHub language fetch

Layer / File(s)	Summary
Handle language fetch failures server/modules/github/service.js	The language-fetch promise now logs rejection errors with console.error and returns no fallback language object.

Estimated code review effort: 2 (Simple) | ~5 minutes

Possibly related PRs

• kunalverma2512/CodeLens#309: Modifies the same language-fetch error handling in server/modules/github/service.js.

Suggested reviewers: kunalverma2512

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description and does not provide the required summary, motivation, testing details, or checklist information.	Add a description using the repository template, including the changes, motivation, testing and verification details, related issue, checklist, and additional notes.
Title check	❓ Inconclusive	The title indicates a bug fix but does not identify the promise rejection handling change.	Use a specific title such as "fix: handle GitHub language fetch errors".

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@server/modules/github/service.js`:
- Line 179: Complete the outer Promise.all expression surrounding the mapping
callback by adding the missing closing parenthesis after the catch chain in the
affected flow. Keep the existing err handling and callback structure unchanged
so server/modules/github/service.js parses and loads correctly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 727b82a0-127f-4713-a94f-2f652028afd0

📥 Commits

Reviewing files that changed from the base of the PR and between 7ad67ff and 1192020.

📒 Files selected for processing (1)

• server/modules/github/service.js