Hi everyone, I've been working with our senior sysadmin guy here, trying to understand some other troubles that I'm having in implementing Go modules in conjunction with VSCode using the gopls extension. As I mentioned in a previous post (https://groups.google.com/g/golang-nuts/c/2Xcfb4f7ans) I've had a bit of a rough time with modules in general. One of the latest troubles has been that every time I do a tiny little push up to our git (GitLab self-hosted) server, we would see 112 "pre-auth" and disconnect errors on the server log. I am using SSH with a key to work with the remote.
Now, that was when I had all 137 modules in the file tree using VSCode. And, interestingly enough, we would get those errors even if I did the push on the command line, *IF* VSCode was open. If I closed VSCode I could push without a hiccup. With that in mind, and in trying to make VSCode easier to work with anyway, I split my project up, using a (new and) separate workspace for each subsystem. This resulted in 7 separate workspaces. What we find with this setup, is that the smaller workspaces open and operate without trouble while the two bigger workspaces (with 40 modules in each) result in about 15 "pre-auth" errors each. So it seems like "something" has a limit of 25 connections, after which we run into troubles, and then perhaps gopls tries again and again when it runs into errors? I don't know. It could explain the high loads I was seeing for 10+ minutes though. And the git server logs are reporting that it's my client that is closing the connection, not the server. For example: Mar 1 14:30:58 gl sshd[16970]: Received disconnect from 142.104.201.220 port 57724:11: disconnected by user We realize that there are "a lot of moving parts" with me working @ home, what with VPN's, proxies, firewalls and all that. But is there a built-in limit in gopls? I also wonder if your proposed solution to the gopls "working with multiple modules <https://github.com/golang/tools/blob/master/gopls/doc/workspace.md>" problem addresses this, or if gopls still checks everything? I'm hoping I can get back to work with this setup, unless I always have problems with the two bigger subsystems, in which case I need to split them up into smaller pieces as well. cheers, Paul -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CALq%2B6%3DFFCzRC1ZgO6Y--EJ8MmCKV5%2BSrKdLn1S8RxHqvQyCtvg%40mail.gmail.com.
