4

1

At our company, we customize our hg setup, so we don't want to use the Kiln installer. We have a powershell script that everyone runs that sets up their local Mercurial config.

My plan was to modify this setup script to now configure Kiln. In doing so I kept running into an exception with kilnauth. At first I thought it was a conflict with mercurial_keyring, but after some trial and error, it seems to just be an issue with the kilnauth extention.

I can start a fresh VM (Windows7), install the latest Mercurial tools (1.8.2 and 2.0.3 of thg).

I then do a quick hg clone, and all is well with the world.

Now I download your extensions. I extract the zip, and modify the mercurial.ini so all it has in it kilnauth="path to kilnauth.py". I now try the same hg clone, and I get

hg clone https://<name>.kilnhg.com/Repo/Repositories/Test/zach-test
Cookie file C:\Users\zdrummond\_hgcookies\d41d8cd98f00b204e9800998ecf8427e exists, but could not be opened.
Continuing without cookie authentication.
http authorization required
realm: kiln
user: zdrummond@biaprotect.com
password:
Cookie file C:\Users\zdrummond\_hgcookies\d41d8cd98f00b204e9800998ecf8427e exists, but could not be opened.
Continuing without cookie authentication.
** unknown exception encountered, please report by visiting
**  http://mercurial.selenic.com/wiki/BugTracker
** Python 2.6.6 (r266:84297, Aug 24 2010, 18:46:32) [MSC v.1500 32 bit (Intel)]
** Mercurial Distributed SCM (version 1.8.2)
** Extensions loaded: fixfrozenexts, mq, kilnauth
Traceback (most recent call last):
  File "hg", line 36, in <module>
  File "mercurial\dispatch.pyo", line 16, in run
  File "mercurial\dispatch.pyo", line 36, in dispatch
  File "mercurial\dispatch.pyo", line 58, in _runcatch
  File "mercurial\dispatch.pyo", line 601, in _dispatch
  File "mercurial\dispatch.pyo", line 406, in runcommand
  File "mercurial\dispatch.pyo", line 655, in _runcommand
  File "mercurial\dispatch.pyo", line 609, in checkargs
  File "mercurial\dispatch.pyo", line 598, in <lambda>
  File "mercurial\util.pyo", line 433, in check
  File "mercurial\commands.pyo", line 825, in clone
  File "mercurial\hg.pyo", line 221, in clone
  File "mercurial\hg.pyo", line 94, in repository
  File "mercurial\httprepo.pyo", line 199, in instance
  File "mercurial\wireproto.pyo", line 68, in between
  File "mercurial\httprepo.pyo", line 137, in _call
  File "mercurial\httprepo.pyo", line 88, in _callstream
  File "C:\Users\zdrummond\Downloads\kiln_extensions\kilnauth.py", line 169, in open
    response = func(*args, **kwargs)
  File "urllib2.pyo", line 397, in open
  File "urllib2.pyo", line 510, in http_response
  File "urllib2.pyo", line 429, in error
  File "urllib2.pyo", line 369, in _call_chain
  File "urllib2.pyo", line 864, in http_error_401
  File "mercurial\url.pyo", line 692, in http_error_auth_reqed
  File "urllib2.pyo", line 842, in http_error_auth_reqed
  File "urllib2.pyo", line 852, in retry_http_basic_auth
  File "C:\Users\zdrummond\Downloads\kiln_extensions\kilnauth.py", line 171, in open
    cj.save(ignore_discard=True, ignore_expires=True)
  File "_MozillaCookieJar.pyo", line 116, in save
ValueError: a filename was not supplied (nor was the CookieJar instance initialised with one)

Now the interesting thing, is if I copy my _hgcookies directory from another machine with a normal install of kiln everything works. The file in there is named d41d8cd98f00b204e9800998ecf8427e

Should I just add this file to my setup script?

Fog Creek Case FC2044472

flag
I'm actually getting this issue with the standard KilnClient.exe install. – C. W. A. Apr 8 2011 at 2:09
I have the same, I e-mailed support already. – Bas Apr 8 2011 at 10:49
I am having same problem. The prompt says the cookie file exists but it does not. – unknown (google) Apr 8 2011 at 14:55
We're aware of this problem and working on a fix. – Kevin Gessner Apr 8 2011 at 15:07

2 Answers

2

I've reproduced and tracked down this problem, and I just checked in a fix. We're working on getting this out to all On Demand customers as soon as possible. I'm sorry for the trouble this has caused.

Update: This is fixed in Kiln 2.4.105, which will be released for all customers by Tuesday morning. You'll need to redownload and install the Client Tools from your Kiln account.

Updated Update: Kiln 2.4.105 is now available for all Kiln On Demand accounts.

link|flag
Any idea when the client tools will be fixed with this issue? – Dan Apr 11 2011 at 7:03
This workaround does not solve the problem for me. Like C.W.A. I have the problem with the standard KilnClient (which I downloaded today). – tigerstyle Apr 11 2011 at 15:44
I have the same issue today. The workaround didn't really work ! – capton siluvairajan Apr 11 2011 at 22:13
This worked for me on a fresh windows xp install. Just ignore the * failed to import extension nobranch and you're set. – unknown (yahoo) Apr 12 2011 at 3:42
It's funny, since today it works, I could do a push without any problems. – tigerstyle Apr 12 2011 at 10:36
show 5 more comments
0

hey guys

Im getting this now too with the current build of Kiln. Is the any update on this issue?

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.