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

Duplicates

Open
  • Is something wrong?
#530 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
tooling

Research direction

Start by reproducing the duplicate lines with Slather 2.7.3 using the slather coverage --html --show command and the provided Xcode project and ignore configuration. Trace how local Swift packages and ignored paths are handled when building the HTML report, then identify which files or coverage entries are duplicated. Done means the report contains each source line once; the issue does not name tests or implementation files to begin from.

Written by the indexing model from the issue text.

Description

Hi,

I'm using Slather 2.7.3

I have quite a few ignore folders set in yml, I'm not able to set a single source folder.
However, I've getting duplicate lines in the html report...

I use the command slather coverage --html --show

And the yml is ...

xcodeproj: ./RUN.xcodeproj
scheme: RUN_iOS Test
output_directory: ../slather-html
ignore:
  - build/*
  - .git/*
  - .github/*
  - Player/*
  - ../../../Library/Developer/Xcode/DerivedData/*
  - RUN_iOS/*
  - RUN_iOS_UITests/*
  - RUN_iOS_UnitTests/*
  - RunSDK/.swiftpm/*
  - RunSDK/Sources/RunSDKUnitTests/*
  - RunSDK/Sources/RunSDK/Generated/*
  - ChannelsAPI/*
  - Console/*
  - distribution/*
  - LiveStats/*
  - NetworkClient/*

I've added lots of ignore, figuring there was some sort of circular dependency, but the duplicates occurs before I add them too.

Any suggestions?

Thanks,

Jules.
EDIT:
I see there's mention of modules, but I'm using local SPMs

Dominant language
Ruby
Stars
1.6k
Forks
239
Avg merge
10h 19m
Merged PRs (30d)
1

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 SlatherOrg/slather

All issues in SlatherOrg/slather

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.