Flare 12 "Retrieving source control status" (git) hangs

[skwpt]

I came to the office ridiculously early today to make headway on a deadline. When I tried to open my project, The "Retrieving source control status" window processed for around 25 minutes until I finally just closed it.

Has anyone else seen this behavior? Its the first time I have seen it since successfully binding to Git in Flare 12 about a week ago.

[Nita Beck]

Just a guess... Was the remote Git server down? If you temporarily disconnect from your network and then start up the project, does the project load then? That might point to the remote server being down and Flare just keeps trying to ping it. I repeat, just a guess...

[skwpt]

Just a guess... Was the remote Git server down?

I did wonder about that. After I closed the "Retrieving..." message and did some stuff in Flare, I successfully pushed the changes to the remote repos. At least I assume I did. That dialog always goes by too fast, and I haven't yet discovered any git logs.

If it happens again, I will disconnect from the network and see how Flare behaves, thanks.

[M_Mercer2015]

I started experiencing this with Flare 12 too. It takes forever and then eventually works. I don't recall having this problem with Flare 11.

Update: It wasn't our server. It appears to have been our virus software. The next time it happens this will be the first thing I check.

[kgmarie]

Mine does this as well with Subversion. Haven't been able to find out how to fix it yet...

[kirinawust]

8 years ago ... Did you find a solution?
I am having the same problem with Flare 2023 r2.

Thx in advance

[Gareth Power]

I had this happen with Subversion - the dialog was hanging indefinitely - and the cause turned out to be an invalid SourceControlDatabaseRoot property in the .flprj file.
I have no idea how this property got a bad value. Very strange.

[Psider]

I thought I'd add to this. Using TFS GIT, some projects worked fine and others would be extremely slow to check the status, and take 20+ minutes to commit a single change.

I found that the projects that were slow didn't have a [remote "origin"] fetch = +refs/xxxx section in the config file.

Opening the repository using GIT GUI added this section and the slowness disappeared.

Mine looked like the following, but I assume it could vary depending on how your server is configured.

And I can't guarantee this was the only change that opening the repository in GIT GUI made, so I would recommend going the long way around rather than trying to shortcut the process by editing the config file.

Code: Select all

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*

(Oh, and this happened after we had a server name change and I changed the name using the Manager Remotes dialog box - I made a post asking if this was safe to do, if you wanted more info. Again, I'm unsure why some projects were fine after changing the name and some weren't.)