You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
api.ts hardcodes cache: "no-store" inside request(), so no fetch through this module can ever use Next.js ISR/fetch caching #189
cache: "no-store" is hardcoded with no per-call override, so fetchBounties, fetchMilestones, fetchMaintenancePools, and fetchReputationByUsername — used by /issues, /milestones, and /reputation/[handle], none of which are dashboards — are
unconditionally opted out of Next.js's fetch caching and ISR, forcing a full server round
trip to mergefi-backend on every single request to those pages, even for content that
changes relatively slowly (a bounty's title/description, a milestone's name).
This is a broader, lower-level root cause than dashboard-specific fetch parallelization —
it's baked into the one shared helper every Server Component fetcher calls through, so no
call site can opt into a revalidate window even if it wanted to.
Suggested fix: accept an optional revalidate/cache override in request()'s init
parameter (defaulting to no-store for safety) so pages that can tolerate slightly stale
data can opt into { next: { revalidate: 30 } } instead of forcing no-store everywhere.
@Abulbayty has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hello, I’m confident that my skills and experience make me a strong fit for this task. I’m ready to deliver quality results, and I’d appreciate the opportunity to handle it.
@Binismail77 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hello, I’d like to contribute to this issue. I have experience building and debugging full-stack applications, so I’m confident I can investigate the problem, implement the fix, and test the complete flow.
@naobadiah01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hello, I am a fullstack developer with years of experience building web3 and web3 applications, I have reviewed the issue and the project, please assign me this issue. ETA 1hr
Congratulations, @Temi-suwa18! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @Temi-suwa18: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
😎 @Temi-suwa18: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
Activity
Sajjadd-dev commentedon Aug 24, 2026
@Sajjadd-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Sajjadd-dev to this issue.
Abulbayty commentedon Aug 24, 2026
@Abulbayty has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Abulbayty to this issue.
Adewumi99 commentedon Aug 24, 2026
@Adewumi99 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Adewumi99 to this issue.
dee-john commentedon Aug 24, 2026
@dee-john has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @dee-john to this issue.
Isihaq123 commentedon Aug 24, 2026
@Isihaq123 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Isihaq123 to this issue.
Binismail77 commentedon Aug 24, 2026
@Binismail77 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Binismail77 to this issue.
naobadiah01 commentedon Aug 24, 2026
@naobadiah01 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @naobadiah01 to this issue.
doctorlight0 commentedon Aug 24, 2026
@doctorlight0 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @doctorlight0 to this issue.
Temi-suwa18 commentedon Aug 24, 2026
@Temi-suwa18 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Temi-suwa18 to this issue.
drips-wave commentedon Aug 24, 2026
Congratulations, @Temi-suwa18! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @Temi-suwa18: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
drips-wave commentedon Aug 24, 2026
This issue has been completed by @Temi-suwa18 as part of the Stellar Wave Program's 8th Wave 🥳
😎 @Temi-suwa18: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
fix(MergeFi#628): wrap fetchers in React cache() to deduplicate per-r…