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

Work Intent: preserve disk I/O counters from disks.ini

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api, testing

Research direction

Start in api/src/store/state-parsers/slots.ts and compare the disk counter mapping with numErrors. Use the non-zero values in api/dev/states/disks.ini to add a regression assertion, then update the existing parser snapshot and run the focused API test suite. Done means the parsed GraphQL counters retain the fixture values instead of becoming zero.

Written by the indexing model from the issue text.

Description

Work intent

Fix the array slot state parser so GraphQL ArrayDisk.numReads and numWrites preserve the non-zero counters already present in disks.ini instead of forcing both fields to 0.

Evidence

  • api/src/store/state-parsers/slots.ts currently maps numErrors from the INI state but hard-codes numReads: 0 and numWrites: 0.
  • api/dev/states/disks.ini contains non-zero read/write counters for active disks.
  • The existing parser snapshot therefore asserts zeros even when its fixture contains non-zero counters.
  • Downstream user report: https://github.com/dinglebear-ai/unraid/issues/396

Planned change

  1. Add a regression assertion proving non-zero fixture counters survive parsing.
  2. Map numReads and numWrites through the same numeric parser used by numErrors.
  3. Update the existing parser snapshot and run the focused API test suite.

This is intentionally scoped to preserving the existing state-file data; it does not change the GraphQL schema or counter semantics.

Dominant language
TypeScript
Stars
113
Forks
23
Avg merge
1d 13h
Merged PRs (30d)
12

Getting set up

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 unraid/api

All issues in unraid/api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.