Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When events.json can't be loaded, the countdown later says "No upcoming events" and a filter click erases the error message

Open
#21 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@tanujb03 is already working on this.

Since Oct 10, 2026.

  • #22 by @tanujb03 — open

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start with how the page handles a failed events.json load, then how the countdown's 60-second refresh and the filter buttons read the events list. Reproduce by serving the folder with that file returning 500 or missing, then check the README.md "How it's supposed to work" section. Done means the error message stays visible, the countdown never says "No upcoming events" after a failed load, and filters keep the message. PR #22 is already open against this issue, so check it first.

Written by the indexing model from the issue text.

Description

bug good first issue

Related to #4, but this is a different input path.

#4 asked that "the page still works if it fails to load" and PR #12 added the "Events could not be loaded right now." message. That message is only shown once, right at the failed load; the countdown and the filter buttons keep running afterwards as if the events list were simply empty.

What I did

  1. Checked out main (72ad265) and served the folder over HTTP, with events.json unavailable (I tried both a server that answers 500 for that file and the file deleted, so 404).
  2. Opened the page. The Events list shows "Events could not be loaded right now." and the countdown is blank.
  3. Clicked a filter button (e.g. Workshops, or All).
  4. On a second run, left the page open for over a minute instead of clicking.

What I expected
The README says: "The countdown under the heading is for the next event that hasn't happened yet. If there are none, it says so." (README.md, "How it's supposed to work"). When the events could not be loaded, nobody knows whether there are any, so the page should not claim there are none, and the error message should stay visible.

What happened instead

  • After about 60 seconds (the countdown's refresh interval) the countdown changes from blank to "No upcoming events".
  • Clicking any filter button, including All, replaces the error message with an empty list, so the Events section is just blank.

Checked in headless Edge with a real 61 s wait: list "Events could not be loaded right now." and blank countdown after the failed load; "No upcoming events" after the tick; empty list after clicking Workshops and after clicking All.

Environment
main @ 72ad265, Edge (headless), Windows 11, static files served over HTTP.

I'd like to work on the fix for this.

Dominant language
JavaScript
Stars
0
Forks
4
Avg merge
1d 3h
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from techcsispit/campus-landing

All issues in techcsispit/campus-landing

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.