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

Receiving Error not ok -- AxiosError: Request failed with status code 502 #1163

Open
t3hchipmunk opened this issue Feb 19, 2024 · 4 comments

Comments

@t3hchipmunk
Copy link

Expected behavior

The theme will upload and activate

Actual behavior

I receive an error message not ok -- AxiosError: Request failed with status code 502 and a json string back.

Steps to reproduce behavior

Use the command stencil push

Environment

Stencil-cli version stencil --version: 7.3.1

Node version node -v: v18.15.0

NPM version npm -v: 9.5.0

OS: Windows 10.0.19045.0

I had been doing frequent pushes over the last week. Today was the first time I had any hiccups. I do have available the full verbose log of the process if it would help to make that available.

Thanks!

@t3hchipmunk
Copy link
Author

I meant to close this as the issue was on my end. I had made a change to my config.json that went against schema.json. I tried making what was supposed to be a string value into a bool value. The system will work during development, but when you push to BC, I assume, there is a validator that runs and fails. The message returned doesn't give much in the way of help, maybe that could be re-worked or the config.json is validated before push?

@jairo-bc
Copy link
Contributor

@t3hchipmunk which value of config.json is giving you an error?

@t3hchipmunk
Copy link
Author

In my case it was part of a theme, not the default config.json

@mayrars
Copy link

mayrars commented Jul 26, 2024

Same case I had an error in my cofig.json file @t3hchipmunk thanks!

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