This message was deleted.
# epinio
a
This message was deleted.
m
It seems to exiting early. I’ve tried upping the timeout multiplier, but that didn’t make a difference. Any other timeouts I need to configure or something?
b
hi paul, it doesn't look like a timeout issue, it seems related to a wrong response decoding. Something is returning a non-JSON that failed the deserialization. You should check the log on the server, and/or the one in the CLI
to do that you can use the
TRACE_LEVEL
env var, put something like
20
m
Alright, running now
👍 1
b
you can change it in the kubernetes epinio Deployment for the server, and on your local env for the CLI
if you want you can use this command to patch the deployment:
Copy code
export TRACE_LEVEL=20 && kubectl patch deployment -n epinio epinio-server --patch '{"spec": {"template": {"spec": {"containers": [{"name": "epinio-server","env": [{"name":"TRACE_LEVEL", "value":"'"$TRACE_LEVEL"'"}]}]}}}}'
m
Ahh, also needs to be applied by epinio-server, now only applying to the CLI command. Applied that, running now.
These are the logs during the run. The error happens consistenly after ‘Compile server’. The message ‘Compiled with warnings’ never shows
b
hm, can you try to give the app a different name (just to create a new Epinio application, instead of updating the old one)?
m
Oh yeah, I’ll delete this one first
b
and if the source is public it will be nice to run the command to try it out 🙂
m
Yeah, it is public:
Copy code
epinio push --git <https://github.com/paales/graphcommerce-magento-graphcms,main> --git-provider github --name gcdemo --builder-image=<http://gcr.io/buildpacks/builder:v1|gcr.io/buildpacks/builder:v1>
Running without a previous application present doesn’t matter, same result.
👍 1
Now running with the default builder image:
Copy code
epinio push --git <https://github.com/paales/graphcommerce-magento-graphcms,main> --git-provider github --name gcdemo
b
hm..
m
Mmm
Odd
With the default image, it crashes on a different line.
b
yep, strange.. are you behind some proxy?
m
Yes we are
b
ah, that could be an issue
m
I think the API requests are going through cloudflare and proxy is enabled there. Let me check
b
you can set the
HTTPS_PROXY
env var to bypass it
it could work
m
Ohhh, so it might simply be a cloudflare timeout or something.
b
exactly, probably when the build start it tries to fetch the dependencies and packages, and failing for the proxy/timeout
m
Alright, let me check
b
try to add something like
--env HTTPS_PROXY=<http://username:password@proxy.example.com>
to the command
(you probably need some quotes)
m
Running now without the cloudflare proxy 🤞
🙌 1
This works!
🎉 1
Thanks so much @broad-dream-81849, you are a lifesaver 🫶
🫶 1
🛟 1
👍 1
b
awesome! You're very welcome 😄 waiting for more feedbacks!
m
Now on to the next part, hooking Epinio up to knative 😎
🤯 2