Hello @sgbaird ! 👋

Thanks for reporting this! Our Tokei tests have started failing as well.

It does seem like a problem on the Tokei side, hitting the API for the sparks-baird/mat_discover repository, I get the following response:

{"blanks":0,"code":0,"comments":0,"lines":0,"stats":[],"inaccurate":false}

Other users have also reported this problematic behaviour here: XAMPPRocky/tokei#881

Things appear to have been sorted upstream so going to close. If there's any recurrence in the near term please feel free to post here and we can reopen.

If anyone significantly in the future sees similar symptoms, it's probably better to open a new issue

Reopening as the upstream issue has recurred

I'm having the same problem. Examples:

Folks, please refrain from posting the "me too" types of comments as they just add unhelpful noise. The above thread already contains relevant information explaining that the issue is upstream.

Shields.io is not a system of record. It doesn't provide CI/pipeline capabilities, and it doesn't count lines of code either. We have to get the data from the relevant upstream endpoint, and we then display whatever data the upstream system of record provides. The upstream system in this case is Tokei, and they've been having this recurring issue for quite some time, as indicated above in the linked tokei issues. Tokei is the service responsible for counting lines of code, and for whatever reason it intermittently claims the count is 0, and thus 0 is displayed on the badges.

There's absolutely nothing we can do about this, so I'd encourage you to subscribe to those issues in the tokei repository if you're interested in receiving updates.

Folks, please refrain from posting the "me too" types of comments as they just add unhelpful noise. The above thread already contains relevant information explaining that the issue is upstream.

Shields.io is not a system of record. It doesn't provide CI/pipeline capabilities, and it doesn't count lines of code either. We have to get the data from the relevant upstream endpoint, and we then display whatever data the upstream system of record provides. The upstream system in this case is Tokei, and they've been having this recurring issue for quite some time, as indicated above in the linked tokei issues. Tokei is the service responsible for counting lines of code, and for whatever reason it intermittently claims the count is 0, and thus 0 is displayed on the badges.

There's absolutely nothing we can do about this, so I'd encourage you to subscribe to those issues in the tokei repository if you're interested in receiving updates.

I will, thanks.

Maybe a new shields badge using this service https://github.com/boyter/scc might help 😃

Hello. I wanted to say that I have a similar issue with the lines of code badge too. The badge always say "Invalid response data". I tried with many repositories and I also tried giving shields.io more permissions, but the message is still shown.

Here is the badge that I want to show:

The shield has the following URL: https://img.shields.io/tokei/lines/github/AleixMT/eChempad

Thank you for your response and for this wonderful project.

I think this is a duplicate of #9389 and the upstream issue is XAMPPRocky/tokei_rs#233

I think this is a duplicate of #9389 and the upstream issue is XAMPPRocky/tokei_rs#233

#9389 was created much later?

OK well #9389 is a duplicate of this.

The main point was I wanted to link to the upstream issue with tokei as this issue was bumped recently.