golemcloud / golemcloud/golem

Golem standalone server doesn't catch SIGINT

Open
#1,603 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug cli
Dominant language
Rust
Stars
1.5k
Forks
212
Avg merge
2d 10h
Merged PRs (30d)
119

Description

A running instance of the Golem standalone server doesn't seem to catch SIGINT termination signal (e.g. pressing Ctrl+C in the running terminal window or using kill -INT <pid>).

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.

Research direction

Locate the Golem standalone server entry point and its shutdown or signal-handling code, then reproduce the issue with Ctrl+C or kill -INT <pid>. Trace how SIGINT is handled and identify an existing test or test location for server termination. Done means a running standalone server responds to SIGINT and exits cleanly.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.