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

TypeError: Converting circular structure to JSON #2056

Open
remidebette opened this issue Feb 3, 2025 · 3 comments
Open

TypeError: Converting circular structure to JSON #2056

remidebette opened this issue Feb 3, 2025 · 3 comments

Comments

@remidebette
Copy link

Hi,

In the context of using github action runners in kubernetes sith scalesets, we recently saw this error happening at checkout.

What is the meaning of the error?

Error: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'TLSSocket'
    --- property '_httpMessage' closes the circle
Error: Process completed with exit code 1.
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.
Image
@remidebette
Copy link
Author

remidebette commented Feb 10, 2025

Also,
If it helps, in the Post step, we see this

env: can't execute '/__e/node20/bin/node': No such file or directory
Error: Error: failed to run script step: command terminated with non-zero exit code: error executing command [sh -e /__w/_temp/f3[5](https://github.com/....EDITED...)1d450-e79e-11ef-bdc3-07b71b06c61b.sh], exit code 127
Error: Process completed with exit code 1.
Error: Executing the custom container implementation failed. Please contact your self hosted runner administrator.

@Hongjia-Jia
Copy link

Hi @remidebette , Is there any updates? I met the same issue.

@remidebette
Copy link
Author

remidebette commented Mar 5, 2025

For us it was a corrupted node on our on premisses kubernetes cluster that was prematurely killing the pods.
Getting it out and recycling it solved the issue.

But the logs here clearly don't handle this use case and don't help in finding the culprit node

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

2 participants