I unfortunately added Git-LFS support to my primary app repository last week… and now my side app that doesn’t use LFS does deploy fine, but my main app that I really would like to use Codex on doesn’t. I suspect it’s because of the LFS… but there’s no way to find out, as basically the test build under Environment Setup → Advanced just fails at this step:
Starting test
Configuring container
Downloading repo
And just says “An unexpected error occurred”.
Would be nice to know for sure if it’s the LFS support that’s the problem, before I go to the effort of de-LFS-ing my repo!.. 
(PS: Another Rails repo I have worked fine eventually after some fiddling)
Update: I’m now no longer sure the problem was specifically with LFS support. When I cloned the project locally it failed.
Either way, I removed the LFS support (was only for a handful of really epic tests with large audio files), and I have managed to clone the repo locally.
Suggested feature: when the repo fails to clone, display the error message to the user.
1 Like
I’m having LFS issues as well it just says the environment cannot connect to Github. "batch response: “proxyconnect tcp: dial tcp 172.24.0.3:8080: connect: no route to host”
It just sees the LFS pointers. I have the LFS_TOKEN updated in the secrets variable and I also have the “./setup.sh” in the setupscript environment. At this point I’m not sure of the error at all.
1 Like