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

Deprecation Warning and Parse Error with reviewdog in GitHub Actions #70

Open
stkhr opened this issue Dec 16, 2024 · 3 comments
Open

Deprecation Warning and Parse Error with reviewdog in GitHub Actions #70

stkhr opened this issue Dec 16, 2024 · 3 comments

Comments

@stkhr
Copy link

stkhr commented Dec 16, 2024

When running GitHub Actions, the following warning and error were detected in the logs:

time=2024-12-16T02:24:56.955Z level=WARN msg="reviewdog: -fail-on-error is deprecated. Use -fail-level=any, or -fail-level=error for github-[pr-]check reporter instead. See also https://github.com/reviewdog/reviewdog/blob/master/CHANGELOG.md"
reviewdog: parse error: EOF

screenshot-2024-12-16 13 57 32

Steps to Reproduce:

  1. Trigger the GitHub Actions workflow that uses reviewdog.
  2. Observe the logs for the warning and error messages.

Request:

Could you confirm whether this is a known issue or provide guidance on how to resolve it? Additionally, if this is not expected behavior, would you consider fixing the parse error in a future release?

@marcincuber
Copy link

I am seeing this issues as well reviewdog: parse error: EOF not sure how to fix it.

@nayuta
Copy link
Contributor

nayuta commented Dec 22, 2024

@stkhr @marcincuber I created a PR for the reviewdog changes. However, the parse error is not related to it. Could you give me any other information like targets?

@stkhr
Copy link
Author

stkhr commented Dec 22, 2024

@nayuta
Thank you for your quick response and for creating the PR to address the reviewdog changes. I really appreciate it!

Regarding the EOF parse error, I investigated further and found that the issue seems to be specific to my environment. When testing in a different environment, the EOF error did not occur. I will fix EOF error myself.

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

No branches or pull requests

3 participants