Suppress categorical warning (fixes #3379)

[hzy46]

To fix #3379

[jameslamb]

I just added (fixes #3379) to the PR description. I try to do this whenever I open a PR that fixes another issue. PR titles become items in the release notes (e.g. https://github.com/microsoft/LightGBM/releases/tag/v3.3.1), and having the fixes #xxxx there makes it easy for users who want to learn more about a particular item in the release notes to click through to the underlying issue.

[jameslamb]

oh! Also @hzy46 please check your ~/.gitconfig. It looks like the commits you've pushed here aren't tied to your GitHub account.

Notice that your profile picture is not showing up:

See my suggestions in #3607 (comment) and uptake/pkgnet#284 (review) for how to fix this.

[shiyu1994]

According to get_params, both params and reference_params can be None. In this case they cannot be directly iterated in the _compare_params_for_warning method.

[hzy46]

Thanks shiyu. I also found this issue in the CI. Will add a check on this.

[hzy46]

Close this to use another PR.

[hzy46]

Thanks @jameslamb . I used a different PR. Now the author info issue should be addressed in #4768

[jameslamb]

I used a different PR. Now the author info issue should be addressed in

Thanks! It looks like you already did git reset, squashed the commits from this PR, and force-pushed them here so another PR wasn't necessary. I can see that the commit on this PR is tied to your user.

But we can review the new PR and keep this, no problem! Just letting you know in case you have this problem in the future.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.