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

Sentry support for fizzy desktop framework

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
zig

Research direction

Start by reviewing the project's build setup and crash-handling entry points; the issue names no files or tests. The request is for an opt-in crash-reporting feature with minidump generation and optional upload, but it leaves the implementation and cross-platform scope open. Done would require agreed behavior and a working, opt-in solution; clarify the preferred approach with maintainers first.

Written by the indexing model from the issue text.

Description

I have a similar DVUI based project which allows optional building and linking of sentry's native SDK for generating minidumps when the program crashes, and optionally configuring it to upload them to a remote endpoint for (ideally opt-in) developer analysis.

It would be cool imo to have this as an opt-in feature for fizzy if people are using it to build apps. At least, I would want this and I intend to port my app to the fizzy framework in the future

Minidumps are not locked in to sentry, anyone can do minidump analysis, although it is not an easy subject especially cross platform

Potential alternatives:

Dominant language
Zig
Stars
1.5k
Forks
40
Avg merge
5h 35m
Merged PRs (30d)
151

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 fizzyedit/fizzy

All issues in fizzyedit/fizzy

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.