AOSSIE-Org / AOSSIE-Org/OrgExplorer

[BUG]: Missing pagination safety guard in fetchContributors() and fetchIssues()

未關閉 適合新手
#103 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
bug
主要語言
JavaScript
星號
34
分支
92
平均合併
8 天 7 小時
30 天內合併 PR
12

描述

Bug Description

Both fetchContributors() and fetchIssues() iterate through paginated GitHub API responses using an unbounded loop:

js :
for (let page = 1; ; page++) { ... }

Steps to Reproduce :

1. Open services/github.js.
2. Navigate to fetchContributors() and fetchIssues().
3. Observe that both functions use an unbounded pagination loop without a maximum page limit or response validation.

Environment Details :

- OS: Windows 11
- Browser: Brave
- Node.js: 22.18.0

Impact :

Medium - Feature works but has issues

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

貢獻指南

開啟貢獻指南

研究方向

Start in services/github.js and inspect fetchContributors() and fetchIssues(), focusing on their paginated GitHub API loops and response handling. The issue is complete when both functions have a defined pagination safety limit and validate responses instead of iterating unboundedly.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
github, javascript
領域
api, backend
Issue 類型
缺陷
難度
2/5
預估耗時
1-3 小時
活躍度
冷清
描述清晰度
基本清楚
新手友好度
64/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。