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

[GITHUB ACTIONS] All PR's are failing if package.json contains a change #49997

Closed
1 task done
dvakatsiienko opened this issue May 18, 2023 · 2 comments
Closed
1 task done
Labels
examples Issue/PR related to examples locked

Comments

@dvakatsiienko
Copy link
Contributor

dvakatsiienko commented May 18, 2023

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.0
      npm: 9.6.6
      Yarn: 1.22.19
      pnpm: 7.24.3
    Relevant packages:
      next: 13.4.3-canary.2
      eslint-config-next: 13.4.3-canary.2
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.8.2

Which example does this report relate to?

Multiple: with-redux, with-algolia-react-instantsearch, with-storybook, app-dir-progressive-web-app and others

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

A Socket Security: Pull Request Alerts step fails for multiple PR's that include examples changes.

PR's with broken CI:

There are multiple different reasons of fail:

  • This pull request alert report failed to run. This can sometimes be due to an error with GitHub's API, Socket's API or a bug in the bot. You can try to re-run the report at any time.
  • This pull request alert report was aborted or timed out while running. You can try to re-run the report at any time.

Step re-runs does not work — the same issue is observed again and again.
I've tried to re-create PR but still same issue with Socket Security step.

My assumption is that the fail is initiated by presence of package updates in package.json. Because, for instance, in with-facebook-pixel example PR update the *Socket Security: Pull Request Alerts check passes, but there are no changes in package.json.

Expected Behavior

Step should pass without failing due to internal issues.

To Reproduce

Open a pull request with example update for examples directory.

@dvakatsiienko dvakatsiienko added the examples Issue/PR related to examples label May 18, 2023
@dvakatsiienko dvakatsiienko changed the title [GITHUB ACTIONS] Socket Security: Pull Request Alerts step blocks PR's CI test pass due to failure for unknown reason [GITHUB ACTIONS] Socket Security: Pull Request Alerts step blocks PR's CI test to pass due to a failure for an unknown reason May 18, 2023
@dvakatsiienko dvakatsiienko changed the title [GITHUB ACTIONS] Socket Security: Pull Request Alerts step blocks PR's CI test to pass due to a failure for an unknown reason [GITHUB ACTIONS] [EXAMPLES] All PR's are failing if package.json contains a change May 18, 2023
@dvakatsiienko dvakatsiienko changed the title [GITHUB ACTIONS] [EXAMPLES] All PR's are failing if package.json contains a change [GITHUB ACTIONS] All PR's are failing if package.json contains a change May 19, 2023
@balazsorban44
Copy link
Member

I'm closing it as per the comment put out by the github action: "This pull request alert report failed to run. This can sometimes be due to an error with GitHub's API, Socket's API or a bug in the bot. You can try to re-run the report at any time."

It's been a while and this did not show up as an issue. Will keep an eye for it.

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples locked
Projects
None yet
Development

No branches or pull requests

2 participants