1/18/2024 0 Comments Bundler for gem 2.0.17When one program calls another one, we usually want to know where in the first program that the second was being called. While this specific problem isn’t that common, this general type of problem is. We can get a bit more specific if we assume we are shelling out searching for "\git”` however there’s still 195 entries, which is still quite a bit. It would take too long to go through all of them. 5210 references to the string git to be exact. I got a few hits but they were mostly di"git" strings, no smoking guns.Įxpanding the search to all directories gave me way too many hits. My first instinct was to grep their app for git calls: But we don’t know where the issue is happening, i.e. So we know why the issue is happening (no git repo on the dyno plus we’re running a git command). The error from git is telling us that we’re trying to run a git command with no git repository. git directory of your app since it only adds extra disk space and makes scaling, restarting, or migrating to other dyno types slower. One of the limiting factors is how fast we can transfer the zipped file (we call it a slug), so we recommend keeping the size of your repo low. One of the ways that we make scaling so fast is that we package your app in a zipped file and (roughly) all we have to do to get it to run is put it on a dyno and unpack it. But why was this only happening on Heroku? If you didn’t know where the message came from, a quick google would point git as being the source of the error. Fatal: Not a git repository (or any of the parent directories).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |