1. TortoiseHg
  2. TortoiseHg
  3. thg
  4. Issues
Issue #1910 resolved

Crash when changing username and server

Alexander J. Summers
created an issue

On the "TortoiseHg Sync" window, I changed my username (by clicking the padlock icon), and then afterwards updated the server and directory details. I noticed that my username was back to the old one in the "Remote Repository" summary at the top, so I clicked the padlock again. At this point, I got the following message (and still do, every time I try to change my username there):

{{{

!python

Mercurial version (2.2.1). TortoiseHg version (2.4) Command: --nofork synch CWD: C:\Users\hel\Documents\chalice-fixes-boogie Encoding: cp1252 Extensions loaded: Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit (Intel)] Windows version: (6, 1, 7601, 2, 'Service Pack 1') Processor architecture: x86 ** Qt-4.7.4 PyQt-4.8.6 Traceback (most recent call last): File "tortoisehg\hgqt\sync.pyo", line 668, in secureclicked File "tortoisehg\hgqt\sync.pyo", line 1324, in init ValueError: invalid literal for int() with base 10: ''

}}}

Comments (7)

  1. Yuya Nishihara
    • changed status to open

    Could you provide the full URL which leads this crash? This bug will be fixed easily, but I cannot reproduce the same traceback.

    The full URL is stored in <repository>\.hg\hgrc file. If it contains user/password, please mask them by asterisks.

  2. Alexander J. Summers reporter

    (Reply via alex...@inf.ethz.ch):

    Hi there,

    Sure - the URL is https://*****************@bitbucket.org/stefanheule/boogie

    In case it matters, the URL I was trying to change it to was https://hg.codeplex.com/boogie

    Cheers, Alex

    -----Original Message----- From: Yuya Nishihara [mailto:issues-reply@bitbucket.org] Sent: Dienstag, 22. Mai 2012 15:10 To: Summers Alexander John Subject: Re: [tortoisehg/thg] Crash when changing username and server (issue #1910)

  3. Yuya Nishihara

    Oops, I happened to miss the reminder email from bitbucket.

    I guess this issue includes two separate bugs:

    • cannot change inlined username/password (security dialog just modifies [auth] section)
    • crash if hostname contains ':'
  4. Log in to comment