Closed GoogleCodeExporter closed 9 years ago
I forgot to say that the older version of namebench works fine for me(1.0.3)
Original comment by woyta...@gmail.com
on 3 Jan 2010 at 10:45
I haven't a clue of why this is happening yet -- do you mind seeing if
namebench
1.1b1 has the same problem? I suspect it will, but I'd rather not chase after
the issue
if it's been fixed already.
If it's still broken, I'll compile a debug build that should display where the
problem
may lie.
By the way - What was the last status message in the window?
Original comment by thomas.r...@gmail.com
on 3 Jan 2010 at 11:16
namebench 1.1b1 has the same bug, but the line numbers are different then 1.0.5
File "libnamebench\tk.pyc", line 102, in run
File "libnamebench\base_ui.pyc", line 80, in PrepareNameServers
File "libnamebench\nameserver_list.pyc", line 303, in CheckHealth
File "libnamebench\nameserver_list.pyc", line 236, in InvokeSecondaryCache
File "libnamebench\nameserver_list.pyc", line 380, in _LoadSecondaryCache
File "genericpath.pyc", line 18, in exists
TypeError: stat() argument 1 must be encoded string without NULL bytes, not str
Last status message in the window just before the error message pop up is:
Checking
nameserver health
Original comment by woyta...@gmail.com
on 4 Jan 2010 at 6:15
I believe this error has to do with the encoding of the temporary path. As of
r578 - I have made this function
more resilient to failure, but I suspect you will run into issues further on
when it comes time to display the web
page. I will post another namebench 1.1 beta tonight, and will see if it fixes
this.
Original comment by tstromb...@google.com
on 4 Jan 2010 at 6:57
Do you mind trying again in namebench 1.1?
Original comment by thomas.r...@gmail.com
on 4 Jan 2010 at 10:21
namebench 1.1 works fine, thanks and keep up the good work.
Original comment by woyta...@gmail.com
on 5 Jan 2010 at 1:30
Original comment by tstromb...@google.com
on 5 Jan 2010 at 3:18
Original issue reported on code.google.com by
woyta...@gmail.com
on 3 Jan 2010 at 10:43