![]() I can follow the libgit2 code, but I haven’t been able to figure out understand why a regex would be (seemly randomly) failing. Let me know if there’s any other information I can provide, or generally if anyone has any ideas. Take a fresh clone of the repository to a new local directory. Perhaps we could patch nodegit so that we can specify the diff driver to use for diff.patches()? Otherwise I’m not sure how to work around this. How to troubleshoot slow performance Perform a git gc on the repository. publishing my findings to the community via peer-reviewed research papers, git repositories, and public forums.I’m only seeing this under electron, so maybe nodegit is doing something funny when compiled for electron?.Reasons why I’m filing a nodegit issue instead of a libgit2 issue: Useful command for going back that far: git reset -hard HEAD~35 Here are some notes I took while trying to figure this out: master (as of this writing): f8f7adce9fc50a11a764d57815602dcb818d1816 Regcomp # The function that actually returns the error.įor some reason git_diff_driver_builtin is using a regex to determine the diff driver to use, and that regex is failing for whatever reason.Įven weirder, it doesn’t fail for every commit, but a lot of them. ![]() I’m not terribly familiar with debugging C programs on linux, but I was able to piece together this stack trace: GitPatch::ConvenientFromDiffWorker::Execute Which, instead of logging the files changed in that commit as I would expect, it outputs this instead: Repo is open. Return (repo, tree, new git.DiffOptions()) The easiest way to reproduce the problem is to grab a clone of the sources for git itself: Īnd then run some variation of this script under electron: var git = require("nodegit") just pure nodejs not electron, or Windows or OSX) the problem doesn’t happen. On Linux (64-bit, haven’t tested 32-bit specifically on the latest releases of Debian and Ubuntu).Running under electron (only tested v1.2.3).Before you can open or clone an Azure DevOps Git repository in GitKraken, you will need to first set up the. Using nodegit (tested a whole mess of versions, mainly v0.13.2 and v0.15.1) Authenticating Your Git Repo with Azure DevOps.I’ve only been able to get this to happen in this situation: However, this isn’t for every commit, and it’s not for every platform either. When trying to get diffs for certain commits, I’m getting the error “Invalid collation character” returned from nodegit. I’m not 100% sure whether this is a nodegit or a libgit2 issue, so apologies in advanced if this isn’t nodegit’s fault.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |