Please be sure to disable or uninstall the stable version of GitLens first. Fork is massively almost overwhelmingly superior in both of these aspects. ENV GitLens Version: v11.6.0 Git Version: git version 2.27.0.windows.1 VSCode Version: 1.60.1 OS Version: Windows 1902 Steps to Reproduce: open a large project type some 'scope. You can install the GitLens insiders edition from here. after disabling (set to 0) and with set to 15000. If that doesn't completely resolve the issue, can you try to see if the issue is still reproducible in the GitLens insiders edition? I'm guessing it is because both are adding decorations into the editor, but I'm not sure how they actually are interacting badly.Ĭould you please try again after disabling/uninstalling the Bracket Pair Colorizer extension to see if you still see an issue? So I think there is some interaction between GitLens and the Bracket Pair Colorizer extension which causes some a performance issue (it might account for all of the visible issue). This value must be between 0 and 60 minutes, and it will fetch all visible remotes for the repository. Those WASM calls aren't coming from GitLens, but from the Bracket Pair Colorizer extension (which by the way should no longer be needed since bracket colorization is built into VS Code because of the performance issues that couldn't be fixed in that extension - you can read the details on this on the VS Code Blog)Īdditionally, I also see the built-in Git extension doing a lot more work (though nothing that should cause delays like the above) in the GitLens trace. General Auto-Fetch Set the number of minutes between auto-fetches. There are 3 calls to WASM functions, which are each taking about 1.4s - I don't see those same WASM calls without GitLens, though I'm not sure I can rely on the wasm-function matching on both sides. Download the free Git client for Windows, Mac & Linux GitKraken Git GUI is free for use with public repositories. Since I upgraded to Big Sur, everything seems really slow on Gitkraken (checkout, pull/push. Digging into them I can't really identify what GitLens is doing to cause issues, but a couple of things stand out in the trace: GitKraken is very slow since macOS Big Sur update. What Jon and his team do is always build native and. To unlock all features for the integration, consider upgrading to a paid GitKraken license. The GitLab Self-Managed Issues integration is view-only for free users. GitKraken Git GUI makes it easy to work with your GitLab Self-Managed Issues. Write(2, "/lib64/ld-linux-x86-64.so.2: No "., 55/lib64/ld-linux-x86-64.so.Thank you for the traces. GitKraken is a web-based application built on Electron, which is why it is slow. GitKraken Client GitLab Self-Managed Issues Integration. Openat(AT_FDCWD, "/lib64/ld-linux-x86-64.so.2", O_RDONLY) = -1 ENOENT (No such file or directory) Qemu doesn’t seem the way to go either as I know it will be incredibly slow as Gitkraken can be quite intensive, really want to get it to work for Nano as I now have a development machine 90% there! faccessat(AT_FDCWD, "/etc/qemu-binfmt/x86_64/lib64/ld-linux-x86-64.so.2", F_OK) = -1 ENOENT (No such file or directory) Looked to see if I could download arm64 compiled binaries from the Gitkraken website but couldnt find anything matching. GitKraken Client v8.3 introduces a new ARM64 compatible version, offering native support for Apple Silicon architectures, as used in Macs with M1 chips. GitKraken Client will use Git instead of the Nodegit library for actions like fetch and commits, plus deliver some performance improvements. Generate commit messages from any staged changes by connecting with an OpenAI API key. I got past this one with: “sudo apt install binfmt-support qemu qemu-user-static” - but it still wont launch as it says it is unable to find the library: lib64/ld-linux-x86-64.so.2 - tried various things but still not able to get past it (strace below). Experiment 1: AI Generated Commit Messages. I am trying to install Gitkraken on my Jetson nano and came across the same error, as you say it seems snap is fetching the wrong binaries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |