New project initialization times out on "get host name" in vcs/init request
#6447
Comments
mwu-tow
added
-tooling
|
Yes, could in theory happen if the FS is reaaaaaaly slow. That's why #5058 would be the best way to fix it. |
|
Michal says that he can reproduce the problem every time - that's a great opportunity to analyze it. Remote debugging on his computer? Or we could try "self profiling": launch the project manager with following options: connect the IDE to it (with |
|
@hubertp @JaroslavTulach
It seems that the option was renamed to |
Thanks for the log files. I unzipped, renamed I can see that following is blocked for 5s on
My conclusion: we need to make sure we can use |
|
Hmm, but this should be run in a separate thread and non-blocking 🤔
is. but config init is not apparently. |
JaroslavTulach
changed the title
vcs/init requestvcs/init request
During initialization JGit may attempt to resolve hostname. On some systems this can take more than desired triggering timeouts. This change does two things: - sets the default committer for changes, lack of which probably triggered the check - sets the default hostname to `localhost` (we don't care), in case something else in JGit still wants to resolve hostname Closes #6447.
During initialization JGit may attempt to resolve hostname. On some systems this can take more than desired triggering timeouts. This change does two things: - sets the default committer for changes, lack of which probably triggered the check - sets the default hostname to `localhost` (we don't care), in case something else in JGit still wants to resolve hostname Closes #6447.
During initialization JGit may attempt to resolve hostname. On some systems this can take more than desired triggering timeouts. This change does two things: - sets the default committer for changes, lack of which probably triggered the check - sets the default hostname to `localhost` (we don't care), in case something else in JGit still wants to resolve hostname Closes #6447. # Important Notes I wasn't able to reproduce this so relying on @mwu-tow since apparently he can repro it reliably.
github-project-automation
bot
moved this from 🌟 Q/A review
to 🟢 Accepted
in Issues Board
|
Hubert Plociniczak reports a new STANDUP for the provided date (2023-04-28): Progress: Debugging initialization issue encountered for vcs. Thanks to Jaroslav's insight we figured that hostname checking could potentially lead to delays on some odd machines. Added workaround to avoid making such requests by JGIT. Investigating #6395 but couldn't reproduce so far. Also having trouble with building IDE via Next Day: Next day I will be working on the #6395 task. Try to reproduce and debug the issue with CB creating a node that doesn't show up until restart. |
When I open IDE and create a new project this appears:
The log from the Language Server JSON WebSocket:
The log from the Project Manager:
I suspect that this has something to do with my local environment, as I've tested quite a number of nightlies from the last month and they display the same behavior, while previously they were working correctly. But now this happens every single time and I don't know what is the reason.
I've tried running IDE on a relatively fresh VM Windows environment and the same thing happens there. I don't see this on Linux though.
Logs come from
2023.1.1-nightly.2023.4.26build.The text was updated successfully, but these errors were encountered: