Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log file generates a warning when --reporter=log is used #233

Open
thombet opened this issue Apr 27, 2020 · 5 comments
Open

Log file generates a warning when --reporter=log is used #233

thombet opened this issue Apr 27, 2020 · 5 comments

Comments

@thombet
Copy link

thombet commented Apr 27, 2020

When I run kodi-addon-checker --branch leia --reporter=log there is a warning reported on the log file generated by the addon-checker:

WARN: Found non whitelisted file ending in filename ./plugin.video.imagotv/kodi-addon-checker-report.log
WARN: We found no problems and 1 warnings, please check the logfile.

I think it is wrong and this file should somehow be ignored.
It seems it was already reported in #156 but from what I see in the final answer the reporter closed the issue because he/she didn't use the argument reporter=loganymore which doesn't really fix the initial issue.

I didn't look in the code yet so I don't know how easy it could be fixed but could you first confirm if it is a bug or if it is somehow expected?

Thanks :)

@razzeee
Copy link
Member

razzeee commented Apr 27, 2020

Should be a bug, I think.

@anxdpanic
Copy link
Member

anxdpanic commented Apr 27, 2020

iirc it wasn't about using reporter=log at that time. I actually solved this locally/travis by not running kodi-addon-checker from within the add-on structure.
ie.
C:\addons\>kodi-addon-checker C:\addons\plugin.video.youtube\ --branch leia --reporter=log instead of
C:\addons\plugin.video.youtube\>kodi-addon-checker --branch leia --reporter=log
The log will be in C:\addons\ in the first example

@thombet
Copy link
Author

thombet commented Apr 27, 2020

I didn't think about this workaround @anxdpanic, thank you for the idea. I guess it can be used until the bug is fixed.

Thanks for confirming it @razzeee. I will probably try to submit a pull request to fix the issue at some point but since I don't know the code at all, any suggestion is welcome :)

@razzeee
Copy link
Member

razzeee commented Apr 28, 2020

On the other hand, it's probably correct, if you are building a pipeline which automatically creates your addons and will just zip that folder. @enen92

@thombet
Copy link
Author

thombet commented May 2, 2020

It turned out to be more complicated than expected especially because:

  • the issue is the same with the debug log so it had to be fixed too
  • I think the correct behavior is to ignore the files having the same name as the logs but not in the current folder

Anyway I submitted the PR #236 and added more info there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants