Proxy support

9 views
Skip to first unread message

Fredrik Orderud

unread,
Oct 24, 2011, 7:44:32 AM10/24/11
to Vercue
Vercue seems to have problems with SVN sources behind a HTTP(S) proxy.
Instead of showing the log, Vercue displays a grey "-" circle for all
my sources behind a proxy. The same sources works perfectly fine in
TortoiseSVN.

Is this a known issue?

Adrian Aisemberg

unread,
Oct 24, 2011, 8:01:13 AM10/24/11
to ver...@googlegroups.com
Hi Fredrik,

Can you please send me the logs to my private email?

The logs are located under %appdata%\Vercue\Logs.

Thanks,
Adrian



Adrian Aisemberg
vercue.com

Fredrik Orderud

unread,
Oct 24, 2011, 10:34:21 AM10/24/11
to Vercue
You will find relevant sections from the log below. <repo-name> is the
source & repository name, and <server-name> is the server DNS name.

--
24/10/2011 13:25:44 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [HH.N] Pause
for 1000 milliseconds
24/10/2011 13:25:45 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [HH.N] Source
'<repo-name>' is in cycle = True
24/10/2011 13:25:45 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.MB] Checking '<repo-name>' for updates...
24/10/2011 13:25:45 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=Updating
24/10/2011 13:25:45 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [UG.GetLog]
No ping to <server-name>
24/10/2011 13:25:45 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=PingStatus
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [SvnLog.KE]
GetFileNameForSource(Source=<repo-name> (C:\Repositories\<repo-name>)
[https://<server-name>/<repo-name>/])
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [SvnLog.KE]
BinarySerialize(fileName=C:\Users\100030120\AppData\Roaming\Vercue
\cache\9ed12651-98dd-48a0-a660-35d3c1ba6368.cache)
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=SVNStatusChanged
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=PingStatus
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.CC] No ping to <server-name>
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=PingStatus
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG]
[SvnSource.OnStatusChanged] StatusChangedReason=Updating
24/10/2011 13:25:46 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [HH.N] Pause
for 1000 milliseconds
...
24/10/2011 13:27:39 [v2.3.0.322] [VC_Q_CYCLE ] [DEBUG] [HH.N] Source
'<repo-name>' is in cycle = False
--

It seems like the problem is related to Vercue not being able to ping
repositories behind a HTTP(S) proxy. I'm also unable to ping the
server from my command-line, but that doesn't stop TortoiseSVN from
functioning.

Adrian Aisemberg

unread,
Oct 24, 2011, 10:38:35 AM10/24/11
to ver...@googlegroups.com
Did you set a proxy in TortoiseSVN's settings (Under "Network") or in the Windows settings (Internet Options) ?

Thanks,
Adrian



Adrian Aisemberg
vercue.com



Fredrik Orderud

unread,
Oct 24, 2011, 5:24:19 PM10/24/11
to Vercue
I've configured proxy settings in both TortoiseSVN (hardcoded proxy IP
& port) and the Windows control panel internet properties (automatic
proxy configuration script). Both TortoiseSVN and internet explorer
are perfectly able to connect to the SVN repository in question.

Adrian Aisemberg

unread,
Oct 24, 2011, 5:54:17 PM10/24/11
to ver...@googlegroups.com
Hi,

Thanks for the update.
There is a hidden tweak in the configuration file that allows Vercue to skip checking for ping replies.

Please close the app and open the config file in a text editor:
%appdata%\vercue\config.xml

Search for IgnoreNoPing and set the value to true.
Start the app again and see if it helps.

Thanks,
Adrian



Adrian Aisemberg
vercue.com



Fredrik Orderud

unread,
Oct 25, 2011, 5:42:09 AM10/25/11
to Vercue
Thank you! Setting "IgnoreNoPing" to "True" solved my problem. :-)

You should probably consider making this default, since many firewalls
and proxy servers are configured to block ping requests.

Thanks,
Fredrik

Adrian Aisemberg

unread,
Oct 25, 2011, 5:56:06 AM10/25/11
to ver...@googlegroups.com
Thanks for the update.

The motivation behind this feature is because trying to perform SVN operations is a much more resource consuming operation rather than a simple ping. If a server has no ping-back then there is no point in trying to perform the SVN operation.

Your case shows that the ping feature is not fully sync'ed with the proxy settings.
The IgnoreNoPing feature is currently a hidden tweak and once it becomes stable - I'll add it to the options dialog.

Thanks,
Adrian



Adrian Aisemberg
vercue.com
Reply all
Reply to author
Forward
0 new messages