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

Automatic flush on exit

Open
#38 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
powershell
Domain
backend

Research direction

Start by comparing the current asynchronous send path with the synchronous “background” worker used for webGL in Unity. Investigate trap, Register-EngineEvent -SourceIdentifier Powershell.Exiting, and the Stop-Sentry call, including the linked PowerShell issue. Done means messages are sent asynchronously during execution while the process still attempts to flush them before exit without hanging.

Written by the indexing model from the issue text.

Description

.NET Improvement

We should find a way to send messages asynchronously while still actually trying to send them before the script exits.

  • trap only gets triggered for errors so that is not usable
  • Register-EngineEvent -SourceIdentifier Powershell.Exiting -Action {} gets stuck on Stop-Sentry call indefinitely. Also, it doesn't seem to work reliably

For now, I'm doing what we do in webGL in Unity, i.e. implement a synchronous "background" worker instead of an async one.

Dominant language
PowerShell
Stars
16
Forks
5
Avg merge
11h 24m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

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 getsentry/sentry-powershell

All issues in getsentry/sentry-powershell

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.