Weird behavior from "indepth analysis language" and "recently used languages"

[stefanusgusega]

I just implemented this feature, and wondering why did my recently used languages not show any language and the percentage. Also, on in depth analysis of languages, why did the stats says 0 lines but there are percentage values. How do I fix this? Thank you.

[lowlighter]

Hi 👋 !

Could you run your workflow with debug: yes and post the logs here ?
I think the indepth mode just failed in your case for whatever reason, but with just the resulting output it's hard to tell why

---

Also, on in depth analysis of languages, why did the stats says 0 lines but there are percentage values?

It's because it make a raw estimation first from GitHub GraphQL API first.

Lines and accurate stats are computed by cloning you repos on the runner and iterating directly on the git logs of it, which is quite expensive in term of resources, but helps to provide more accurate stats along with new ones like the number of lines

[stefanusgusega]

For most used section, I think it's probably because you reached the maximum timeout (default is 15min but you can increase it to up 30min using plugin_languages_analysis_timeout option)

If I set to the 30 mins, will the line information appeared? What if I reached the maximum timeout again even if I already set it on 30 mins?

it's because your commits_authoring option is not properly set.

I've noticed this a few hours ago, thank you for clarifying this. Now, the runner is running with configured commits.authoring set to my username, my email, and my university email, and let's see if it will be fixed.

Thank you in advance!

[stefanusgusega]

The recent language section seems fixed. And, I have 2 questions.

1. As stated in this debug log, does this plugin skip private repositories? Because the repository that I quoted is exactly a private repository.

metrics/compute/stefanusgusega/plugins > languages > indepth > an error occured while processing stefanusgusega/KaryakuOrMaknart, skipping...

2. Does this plugin only scan repository that I created? Or, it considers my commit to other public repository? Because, I noticed that I think the debug log states only repository that I created.

Thank you in advance.

[lowlighter]

Sorry for the late reply

1. As stated in this debug log, does this plugin skip private repositories? Because the repository that I quoted is exactly a private repository.

It isn't supposed to skip private repository (unless the token used doesn't have access to it), but if there is any error during the processing it'll be skipped (like it seems to be in this case) to avoid making the whole indepth analysis failed. Also to avoid "code leaks", the action isn't very verbose on this kind of error so it's kind of hard to debug and cannot take a look at it myself

2. Does this plugin only scan repository that I created? Or, it considers my commit to other public repository? Because, I noticed that I think the debug log states only repository that I created.

If you have not explicitely configured repositories_affiliations to another constraint, yes it default to owner only, but you can extend it to collaborator, organization_member or the broadest one which is no constraints: ""

Additionally, repositories_forks are also ignored by default in case you were wondering, but can be opted-in too

Hope it helps 👍

[stefanusgusega]

It isn't supposed to skip private repository (unless the token used doesn't have access to it)

The token set for this metrics is stated below. Is this true? Or am I missed any permissions?

If you have not explicitely configured repositories_affiliations to another constraint, yes it default to owner only, but you can extend it to collaborator, organization_member or the broadest one which is no constraints: ""

Thank you for this clarification, maybe you should state this in this repository? Or is it explained before?

[lowlighter]

The token set for this metrics is stated below. Is this true? Or am I missed any permissions?

No repo is basically for everything that is private so it's sufficient permissions.
The languages plugin will be reworked soon to support additional features so it may be fixed without anything to do from your side in the future

Thank you for this clarification, maybe you should state this in this repository? Or is it explained before?

It's only specified in the plugin documentation, but I don't think it's mentioned in the "Getting started" guides.
Maybe it'd be a good idea to at least link core/base` plugins documentation in them