Eventually the problems just come back though. **** One thing that we've discovered of note, every time we have this issue, if we run Git GUI within that git repo folder (simply just open git gui) then all of the problems with Atom and GitKraken disappear for a time. Honestly it's such a weird problem I don't even know who to submit the bug report to, and we haven't found anything in our searching. Our git ignore file is almost identical to the other magento sites that have no problems with Atom or Gitkraken. I thought, maybe repo size or history had something to do with it, so we tried initializing a fresh repo, added the files and made our first commit, and still the same problem. If you have this project open in another tool, such as an IDE, try closing that application and then relaunching GitKraken Client. How can I fix that That error usually indicates something is stopping GitKraken from opening the repo. If we remove the repo and open the project then it works with no issues. I receive a 'Could not find a compatible repository' for one of my repos. The problem with atom is definitely related to git. We could leave it sitting there for a couple of hours untouched and come back to it and all of a sudden we cannot open any files. Other time this does not occur, and that's when it opens fine in Atom.
We HAVE noticed a 1:1 correlation with GitKraken when this occurs - when we try to open the repo in gitkraken we get an error that it could not find any repo - even though it actually loads the repo just fine, albeit after a long delay. Sometimes when we open up the project in Atom it works, most of the time it doesnt.
It seems to hang on initializing git info (folders stay uncolored). What happens is we open the project in Atom and we cannot open any files. One main was that we work in almost daily is a Magento 1.9 site (although, we have other Magento 1.9 sites on git repos that have no problem with Atom). We have some projects with git in it that cause serious issues. I wasn't okay with that.We have recently tried switching from Sublime to Atom, and started using GitKraken also (we've mostly just been working with git in command line) Well, I guess that there is an even more extreme step, in that you could delete the repo and re-clone but you would lose all local branches, stashes, and unpushed commits.
Ok, if you are still having trouble and are CERTAIN that you do not need anything in your reflog, INCLUDING YOUR STASH, you can expire all of it now and clean up (garbage collect) the dangling refs: git reflog expire -expire=now -all To get my GitKraken working again, I need to go with the Nuclear Option. Those are temp files that should have been filled with data or deleted but were not, for. I also found some zero byte objects, which should not be. The corrupted lines in my log had loads of strange symbols and were like 4 time the length of the other lines. All of the lines should look very much the same (from-hash, to-hash, timestamp, user, message, and so on). git/logs/refs/remotes/*/* for any lines that look extremely unusual. A Solutionĭigging a little deeper I found that, apparently, something got corrupted in my reflog. Other tools (Giggle, gitg, git-gui, and the git CLI) all seemed to work just fine.
However, after about a minute, it would unload the repo and start trying to load it again, but just hang trying to load. It would keep presenting this "compatible repository" message even though it would load the repo and let me stage and browse commits. I just had this same issue with GitKraken.
0 kommentar(er)
