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

gameserver.cpp: catch(...) at protobuf/JSON parse site blocks reporting the real error

Open Beginner friendly
  • Is something wrong?
#30 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp
Domain
backend

Research direction

Read AGENTS.md's CPP-MINGW-ADDENDUM, then inspect src/runtime/server/gameserver.cpp around line 1281 and the nearby protobuf/JSON parse call. Identify the exception type thrown there, replace the ellipsis catch with a typed catch, and verify the downstream Warning reports the exception reason through e.what().

Written by the indexing model from the issue text.

Description

Found while auditing log message quality in src/runtime/server/gameserver.cpp (repo-wide log audit).

Around line 1281 there's a catch (...) (ellipsis catch), which is a Hard Stop violation per AGENTS.md's CPP-MINGW-ADDENDUM ("Catch ... (ellipsis catch). Every catch block must name the type."). The adjacent Warning at line ~1282 currently can't report the actual parse error because the exception type is erased by the catch-all.

Fix direction: name the actual exception type being thrown at that call site (likely a nlohmann::json parse exception or similar, based on surrounding code) and catch that specifically, so the Warning can include e.what(). Not fixed as part of the log-audit commit since changing a catch clause is a structural code change, not a message-content edit — but the log line downstream of it can't be properly fixed (per this audit's own Rule 9 — error paths must log the error code/reason) until this is addressed.

Dominant language
C
Stars
2
Forks
2
Avg merge
3h 8m
Merged PRs (30d)
2

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 EchoTools/nevr-runtime

All issues in EchoTools/nevr-runtime

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.