AdminPage's fetchOswEvents silently swallows fetch errors, unlike the adjacent fetchEcosystems

[Jagadeeshftw]

Description

src/features/admin/pages/AdminPage.tsx defines two very similar list-loading functions right next to each other. fetchEcosystems correctly surfaces failures to the admin:

const fetchEcosystems = async () => {
  try {
    setIsLoading(true)
    setErrorMessage(null)
    const response = await getAdminEcosystems()
    setEcosystems(response.ecosystems || [])
    setEcosystemsVisibleCount(clampLimit(ECOSYSTEMS_PAGE_SIZE))
  } catch (error) {
    logger.error('Failed to fetch ecosystems:', error)
    setEcosystems([])
    setErrorMessage(error instanceof Error ? error.message : 'Failed to load ecosystems.')
  } finally {
    setIsLoading(false)
  }
}

but fetchOswEvents, called from the same useEffect on mount, does not:

const fetchOswEvents = async () => {
  try {
    setIsOswLoading(true)
    const res = await getAdminOpenSourceWeekEvents()
    setOswEvents(res.events || [])
    setOswVisibleCount(clampLimit(OSW_EVENTS_PAGE_SIZE))
  } catch (e) {
    setOswEvents([])
  } finally {
    setIsOswLoading(false)
  }
}

If getAdminOpenSourceWeekEvents() fails (network error, 500, auth expiry, etc.), the catch block silently resets oswEvents to an empty array with no logging and no errorMessage/toast — an admin sees an indistinguishable "no events" empty state instead of being told the request failed, and has no way to tell a real "zero events configured" state apart from "the fetch broke."

Requirements

• fetchOswEvents's catch block must log the error (matching fetchEcosystems's logger.error call) and surface a user-visible error state for the Open-Source Week events section.
• The error state must be distinguishable from a genuine empty list (see the related issue about handleCreateOsw/handleDeleteOswConfirmed reusing the wrong errorMessage state — this should use a dedicated OSW-scoped error state rather than reusing the ecosystems' errorMessage).

Suggested execution

1. Fork the repo and create a branch: git checkout -b fix/adminpage-osw-events-fetch-error-handling
2. Add an oswErrorMessage state (mirroring errorMessage) and set it in fetchOswEvents's catch block, alongside a logger.error call.
3. Render the OSW error state near the Open-Source Week events section, matching the ecosystems section's existing error banner pattern.
4. Add a test asserting a rejected getAdminOpenSourceWeekEvents() call surfaces a visible error rather than a silent empty list.

Example commit message

fix: surface fetchOswEvents failures instead of silently swallowing them

Acceptance criteria

• A failed Open-Source Week events fetch logs the error and shows a visible error message to the admin.
• The error state is visually distinguishable from a genuine empty events list.
• A test covers the failure path.

Security notes

None directly, but silently hiding fetch failures can mask backend/auth problems from admins, which is worth flagging in review.

Guidelines

• Minimum 95% test coverage
• Timeframe: 96 hours

[1nonlypiece]

Hi Maintainers 👋,

I’d like to apply for this issue.

I have hands-on experience with Next.js frontend development as well as Stellar smart contracts using Rust (Soroban). I’m comfortable working with Figma designs, integrating APIs/wallets on the frontend, and implementing, testing, and optimizing smart contracts on Stellar.

I can follow the project guidelines, communicate progress clearly, and deliver clean, well-tested code within the expected timeline.

Looking forward to contributing to the project 🚀
Thanks!

[grantfox-oss]

🦊 GrantFox — @1nonlypiece has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #888)
2. Your PR will be reviewed by the Grainlify maintainers

Good luck! Track your progress on GrantFox.

[Jagadeeshftw]

Assigned @1nonlypiece! Go ahead and open a PR referencing this issue (Closes #888) when ready. t.me/+vTbe0hOUKrFhNTJl