fix: code quality and safety improvements

[saurabhhhcodes]

Summary by CodeRabbit

• Bug Fixes
  • Improved error visibility when repository language data cannot be retrieved.
  • Prevented language-fetching failures from occurring without a logged error.

[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]

📝 Walkthrough

Walkthrough

The repository language-fetching promise chain in #fetchDashboardData now catches errors and logs them with console.error.

Changes

Language fetch error handling

Layer / File(s)	Summary
Repository language-fetch handling server/modules/github/service.js	The per-repository language-fetching promise chain now catches errors and logs them with console.error.

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

Possibly related PRs

• kunalverma2512/CodeLens#309: Modifies the same language-fetching promise chain to catch and log errors.
• kunalverma2512/CodeLens#318: Applies the same error-logging change to the language-fetching promise chain.

Suggested reviewers: kunalverma2512

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request has no description and does not provide the required summary, motivation, testing, or checklist information.	Add the required sections and describe the change, motivation, testing performed, related issue, and applicable checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title relates to the added error logging but is broad and does not identify the specific change.
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

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Biome (2.5.5)

server/modules/github/service.js

File contains syntax errors that prevent linting: Line 179: expected ) but instead the file ends

---

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: Close the unmatched promise expression in the chain containing the
.catch(err => console.error(err)) callback by adding its corresponding closing
parenthesis before the statement ends, so server/modules/github/service.js
parses successfully.

🪄 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: a6cab797-126a-4423-bf3d-51c435b5f138

📥 Commits

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

📒 Files selected for processing (1)

• server/modules/github/service.js

[coderabbitai]

🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win

Close the enclosing promise expression.

Line 179 leaves an opening ( unmatched. Biome reports that the file ends while it expects ). The server cannot load this module until the expression has its matching closing delimiter.

🧰 Tools

🪛 Biome (2.5.5)

[error] 179-179: expected ) but instead the file ends

(parse)

🪛 GitHub Actions: Quality Gate / 0_Backend Lint & Test.txt

[error] 179-179: ESLint parsing error: Unexpected token. The 'npm run lint' command failed with exit code 1.

🪛 GitHub Actions: Quality Gate / Backend Lint & Test

[error] 179-179: ESLint parsing error: Unexpected token. The 'npm run lint' command failed with exit code 1.

🤖 Prompt for 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.

In `@server/modules/github/service.js` at line 179, Close the unmatched promise
expression in the chain containing the .catch(err => console.error(err))
callback by adding its corresponding closing parenthesis before the statement
ends, so server/modules/github/service.js parses successfully.

Source: Linters/SAST tools