acmego - check for existing instances

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

The issue does not name files or tests. Start by locating the acmego command entry point and reproducing the behavior with multiple acmego instances, then investigate how the command could detect an existing instance. Done means the existing-instance case is reported or prevented without causing the described gofmt text doubling.

Written by the indexing model from the issue text.

Description

acmego doesn't report exisiting acmego instances, which can cause weird behaviour (gofmt text doubling). Maybe there should be a lock file? Or just a pidof-like check?

Dominant language
Go
Stars
377
Forks
109
PR merge metrics
No merged PRs in 30d

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 9fans/go

All issues in 9fans/go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.