Re: Problem: Google Code SSL certificates - FIXED

2009-12-09 Thread Nitin Madnani
I am a relatively new user of Versions and am seeing these popups
every few minutes on my Mac running snow leopard. Help!

Nitin

On Nov 26, 12:57 pm, Dirk Stoop d...@madebysofa.com wrote:
 Hi everyone,

 This problem has been fixed by google.  On thanksgiving nonetheless,
 so I know who I'm giving thanks to ;)

 If anyone still gets those dialogs (which seems pretty unlikely to me,
 but you never know), please drop a line here or at google's support
 page linked in my previous post.

 Cheers and happy thxgiving,
 - Dirk

 the Versions team

 On Nov 24, 11:48 pm, Dirk Stoop d...@madebysofa.com wrote:



  Yet more info:

  Please 'star' this issue at Google Code if you're experiencing the
  problem in Versions:http://code.google.com/p/support/issues/detail?id=3312

  The more votes, the more likely they'll be able to give it a higher
  priority.

  Thank you all for your patience,
  - Dirk

  the Versions team

  On Nov 24, 9:57 pm, Stratification stratificat...@gmail.com wrote:

   That sounds very much like what I'm seeing and would really explain
   its intermittent nature. Thanks for the update, here's to hoping
   there's a reasonable fix on the horizon (or Google gets their act
   together).

   Aaron

   On Nov 24, 11:59 am, Dirk Stoop d...@madebysofa.com wrote:

Some more info:

It seems that people using the command line client, or other
Subversion clients are also running into this problem (minus the modal
dialogs of course).

   http://groups.google.com/group/google-code-hosting/browse_thread/thre..

Apparently Google Code is sending one of two SSL certificates back (at
random) on every new connection to an https Google Code URL.  One of
these certs is signed by Thawte, one by Google themselves.  Every time
there's a mismatch between a previously acceptedcertificatefor a
particular URL and one that's being used on a new connection, SVN
chokes and asks the user to accept the newcertificate.

Everything seems to point out that this is a problem with Google Code,
not with Versions or Subversion in general.  We're still looking for a
workaround and ideally for a solution.

Like Nick said, turning of working copy badges will help, because
every time those are refreshed a new connection is made.  It won't
make the problem go away completely, but you'll see a lot fewer
dialogs.

Importing the *.googlecode.comcertificatethat Google signed
themselves in your Keychain will not fix the problem, at least it
doesn't for me; I still get the dialog asking me to accept the
   certificate, the difference is that the dialog claims thecertificate
is set to be trusted (which I just did in Keychain Access) instead of
untrusted.

If anyone here knows someone at or close to Google Code, please ask
them to take a look at this thread.  Any help we can get to clear this
up would be appreciated. :)

Cheers,
- Dirk

the Versions team

--

You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.




Re: Problem: Google Code SSL certificates - Reopened

2009-12-09 Thread Dirk Stoop
The ticket at Google is filled with comments from people who have
started seeing those dialogs again, they're working on it..

On Dec 9, 2:45 am, Nitin Madnani nmadn...@gmail.com wrote:
 I am a relatively new user of Versions and am seeing these popups
 every few minutes on my Mac running snow leopard. Help!

 Nitin

 On Nov 26, 12:57 pm, Dirk Stoop d...@madebysofa.com wrote:



  Hi everyone,

  This problem has been fixed by google.  On thanksgiving nonetheless,
  so I know who I'm giving thanks to ;)

  If anyone still gets those dialogs (which seems pretty unlikely to me,
  but you never know), please drop a line here or at google's support
  page linked in my previous post.

  Cheers and happy thxgiving,
  - Dirk

  the Versions team

  On Nov 24, 11:48 pm, Dirk Stoop d...@madebysofa.com wrote:

   Yet more info:

   Please 'star' this issue at Google Code if you're experiencing the
   problem in Versions:http://code.google.com/p/support/issues/detail?id=3312

   The more votes, the more likely they'll be able to give it a higher
   priority.

   Thank you all for your patience,
   - Dirk

   the Versions team

   On Nov 24, 9:57 pm, Stratification stratificat...@gmail.com wrote:

That sounds very much like what I'm seeing and would really explain
its intermittent nature. Thanks for the update, here's to hoping
there's a reasonable fix on the horizon (or Google gets their act
together).

Aaron

On Nov 24, 11:59 am, Dirk Stoop d...@madebysofa.com wrote:

 Some more info:

 It seems that people using the command line client, or other
 Subversion clients are also running into this problem (minus the modal
 dialogs of course).

http://groups.google.com/group/google-code-hosting/browse_thread/thre..

 Apparently Google Code is sending one of two SSL certificates back (at
 random) on every new connection to an https Google Code URL.  One of
 these certs is signed by Thawte, one by Google themselves.  Every time
 there's a mismatch between a previously acceptedcertificatefor a
 particular URL and one that's being used on a new connection, SVN
 chokes and asks the user to accept the newcertificate.

 Everything seems to point out that this is a problem with Google Code,
 not with Versions or Subversion in general.  We're still looking for a
 workaround and ideally for a solution.

 Like Nick said, turning of working copy badges will help, because
 every time those are refreshed a new connection is made.  It won't
 make the problem go away completely, but you'll see a lot fewer
 dialogs.

 Importing the *.googlecode.comcertificatethat Google signed
 themselves in your Keychain will not fix the problem, at least it
 doesn't for me; I still get the dialog asking me to accept the
certificate, the difference is that the dialog claims thecertificate
 is set to be trusted (which I just did in Keychain Access) instead of
 untrusted.

 If anyone here knows someone at or close to Google Code, please ask
 them to take a look at this thread.  Any help we can get to clear this
 up would be appreciated. :)

 Cheers,
 - Dirk

 the Versions team

--

You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.




Re: Terrible user experience using Versions and Snow Leopard

2009-12-09 Thread jangro
This apr_pool_cleanup_kill issue is making me nuts.  I get it
literally every few minutes.

I'm glad to see that you're fixing it, but would also like to hear an
ETA.
I may just go on vacation until then and I need to know when to come
back to work.  :)



On Dec 4, 10:56 am, Dirk Stoop d...@madebysofa.com wrote:
 The next update will fix several issues, but the particular fix I was
 talking about only relates to the crash logs that have
 apr_pool_cleanup_kill in their traceback.

 - Dirk

 On Dec 3, 5:26 pm, Marijn Huizendveld marijn.huizendv...@gmail.com
 wrote:



  On Dec 3, 2009, at 5:17 PM, Dirk Stoop wrote:

   the next update

  Will that only fix this specific issue or other things as well?

   to Versions,

   Thanks for your patience,
   - Dirk

   the Versions team

   On Dec 3, 3:13 pm, misterniall niall.br...@gmail.com wrote:
   You aren't the only one.  I have at least 30 of them

   here is an example of mine:

   Process:         Versions [1599]
   Path:            /Applications/Versions.app/Contents/MacOS/Versions
   Identifier:      Versions
   Version:         ??? (???)
   Code Type:       X86 (Native)
   Parent Process:  Versions [424]

   Date/Time:       2009-11-19 16:33:42.839 -0330
   OS Version:      Mac OS X 10.6.2 (10C540)
   Report Version:  6

   Interval Since Last Report:          4201 sec
   Crashes Since Last Report:           1
   Per-App Crashes Since Last Report:   1
   Anonymous UUID:                      F7C53458-E942-4CBE-
   B7B1-21971F46D79B

   Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
   Exception Codes: KERN_INVALID_ADDRESS at 0x73722f83
   Crashed Thread:  0

   Application Specific Information:
   *** multi-threaded process forked ***

   Thread 0 Crashed:
   0   libapr.dylib                        0x002d928d apr_pool_cleanup_kill 
   +

   --

   You received this message because you are subscribed to the Google Groups 
   Versions group.
   To post to this group, send email to versi...@googlegroups.com.
   To unsubscribe from this group, send email to 
   versions+unsubscr...@googlegroups.com.
   For more options, visit this group 
   athttp://groups.google.com/group/versions?hl=en.

--

You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.




Re: Terrible user experience using Versions and Snow Leopard

2009-12-09 Thread Dirk Stoop
Shortest vacation ever, sorry ;)

ETA is later this week.  We have a bigger update in the works, but
since that one needs a little more love before it's ready for
primetime, we've decided to release a small update that primarily
takes care of this issue in between.

All the best,
- Dirk

the Versions team

On Dec 9, 2:58 pm, jangro sjan...@gmail.com wrote:
 This apr_pool_cleanup_kill issue is making me nuts.  I get it
 literally every few minutes.

 I'm glad to see that you're fixing it, but would also like to hear an
 ETA.
 I may just go on vacation until then and I need to know when to come
 back to work.  :)

 On Dec 4, 10:56 am, Dirk Stoop d...@madebysofa.com wrote:



  The next update will fix several issues, but the particular fix I was
  talking about only relates to the crash logs that have
  apr_pool_cleanup_kill in their traceback.

  - Dirk

  On Dec 3, 5:26 pm, Marijn Huizendveld marijn.huizendv...@gmail.com
  wrote:

   On Dec 3, 2009, at 5:17 PM, Dirk Stoop wrote:

the next update

   Will that only fix this specific issue or other things as well?

to Versions,

Thanks for your patience,
- Dirk

the Versions team

On Dec 3, 3:13 pm, misterniall niall.br...@gmail.com wrote:
You aren't the only one.  I have at least 30 of them

here is an example of mine:

Process:         Versions [1599]
Path:            /Applications/Versions.app/Contents/MacOS/Versions
Identifier:      Versions
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  Versions [424]

Date/Time:       2009-11-19 16:33:42.839 -0330
OS Version:      Mac OS X 10.6.2 (10C540)
Report Version:  6

Interval Since Last Report:          4201 sec
Crashes Since Last Report:           1
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      F7C53458-E942-4CBE-
B7B1-21971F46D79B

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x73722f83
Crashed Thread:  0

Application Specific Information:
*** multi-threaded process forked ***

Thread 0 Crashed:
0   libapr.dylib                        0x002d928d 
apr_pool_cleanup_kill +

--

You received this message because you are subscribed to the Google 
Groups Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group 
athttp://groups.google.com/group/versions?hl=en.

--

You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versi...@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.