-
Notifications
You must be signed in to change notification settings - Fork 99
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
Server Error #392
Comments
I raised a support ticket for this with information on how to reproduce the issue. Looks like the API is returning a 502. #1993524 |
Any updates regarding this @jamime? We have the same (or at least a similar) issue with the action just failing with For context: we are moving around a lot of packages internally in a monorepo using yarn workspaces. The actions seems really flaky and occasionally passes. but most of the time i get this error. |
@jamime @fbjaras are you able to use the Dependency Review API on the PRs where the Action fails? I'm guessing this is a server error, not something related to the Action, but it'd be good to have some confirmation before proceeding. |
Yes this also fails. I guess i should raise a support ticket for this as well then! |
I've created a new issue to track this: #398, closing this issue. Contributions are always welcome. If you'd like to work on this enhancement please see our contributor's guide, or ping me directly! |
I started to get same issue for some reason. I did nothing. No new deps or something. Just started to get error. |
@dzmitry-lahoda do you have a public repo where this behavior can be seen? Are you able to hit the API directly? |
https://github.com/ComposableFi/composable/actions/runs/5568024051/jobs/10172706662 It was success on 5 or 6 retry. Here is example debug enabled log I think I saw issue when I deleted many files (like 100+, may be 1000). Like big diff fails deps bot. |
@dzmitry-lahoda thanks for the extra details. I can see that the timeout is coming from the GitHub API and not the Action itself:
|
I am seeing the same error as #386 in that nested folders are not scanned.
The action exited with a success but no output.
But as you can see there was no output.
I re-ran the job by closing and re-opening the PR and now I get a server error but with no information.
I tried to reproduce this on a public repository but it works without a problem.
https://github.com/ChrisC-testorg/public-dependency-review/pull/1
Any ideas what could cause this, can we enable more logging to see what the server error is?
For context I'm trying to review all dependencies - so I'm copying the package files from different repositories. Is there another way to set the
basehead
to review all dependencies instead of just those that have changed - that would resolve this problem for me.The text was updated successfully, but these errors were encountered: