This is a strange one. The other day my Subversion commits have suddenly stopped working in terms of uploading to the repository.
I ctrl-shift-A, use the commit and get the window for commiting the files I've highlighted and the -m message window. Enter a message... All good.
When I hit Commit however, I get the Subversion Commit - "Transmitting File data" window and the barber pole but the window never comes back with either a dialogue box for the password for the user or anything at all. I end up having to quite Textmate in order to kill it and then doing a command line svn cleanup on the files that I was trying to upload.
Handling svn through the command line with svn ci file.rhtml -m "blah de blah" works fine however.
Does anyone have any idea of what may be causing this and how to correct it ? I've gotten so used to the svn budle it's really cramping my style now...
thanks ! Daryl. PS> OSX 10.4.11, Textmate Version 1.5.7 (1436), svn, version 1.4.5 (r25188)
On 2 Dec 2007, at 18:15, Daryl Manning wrote:
[...] Does anyone have any idea of what may be causing this and how to correct it ? I've gotten so used to the svn budle it's really cramping my style now...
No idea, but try open Console and see if there is any output. The command should redirect stderr to /dev/console.
Thanks Allan... Got to admit, this one has got me bit stumped... Looks some sort of errant bundle problem...
===== Tuesday, 4December , 2007 2:08:05 AM Europe/London ===== 2007-12-04 02:09:36.074 CommitWindow[27318] *** -[NSBundle load]: Error loading code /Users/daryl/Library/InputManagers/Smart Crash Reports/Smart Crash Reports.bundle/Contents/MacOS/Smart Crash Reports for bundle /Users/daryl/Library/InputManagers/Smart Crash Reports/ Smart Crash Reports.bundle, error code 2 (link edit error code 0, error number 0 ()) 2007-12-04 02:09:36.076 CommitWindow[27318] *** -[NSBundle load]: Error loading code /Users/daryl/Library/InputManagers/CPNoteBook/ CPNoteBook.bundle/Contents/MacOS/CPNoteBook for bundle /Users/daryl/ Library/InputManagers/CPNoteBook/CPNoteBook.bundle, error code 2 (link edit error code 0, error number 0 ())
Anyone have an idea of how to get rid of these errors ? I've never seen them before but they definitely appear to be affecting the subversion bundle commit...
Right now I have to close textmate, do a command line svn cleanup of all the directories I was about to commit and then just handle the commits via the command line.
All help greatly appreciated... thanks ! Daryl.
On 3-Dec-07, at 1:15 PM, Allan Odgaard wrote:
On 2 Dec 2007, at 18:15, Daryl Manning wrote:
[...] Does anyone have any idea of what may be causing this and how to correct it ? I've gotten so used to the svn budle it's really cramping my style now...
No idea, but try open Console and see if there is any output. The command should redirect stderr to /dev/console.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Done... stops the error messages in the Console (and conincidentally in the R statistical package I was getting on startup... =] ) but the Commit window still just infinite barber poles and never comes back.
Should I use ethereal or netstat to see what is going on a this point ? Are there any other options open for diagnosing what is going wrong here ? Subversion itself works fine when I do command line commits so it definitely seems to be an issue with the Subversion bundle in Textmate (as awesome as it's been up till now).
Any ideas ? (and once again, thanks for all the help... ). ciao ! Daryl.
On 4-Dec-07, at 2:51 AM, Allan Odgaard wrote:
On 4 Dec 2007, at 03:14, Daryl Manning wrote:
[...] Anyone have an idea of how to get rid of these errors ?
Try move/rename/trash /Users/daryl/Library/InputManagers
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 4 Dec 2007, at 11:48, Daryl Manning wrote:
[...] the Commit window still just infinite barber poles and never comes back.
Should I use ethereal or netstat to see what is going on a this point ?
If you are experienced enough with those to decipher svn traffic.
Otherwise I think you’ll have to add some debug log statement to the actual command, to figure out exactly how it calls svn and why that might fail on your system.
The debug log statement sounds like a good bet to start. Can you let me know where I'd add that in the bundle code (or walk me through it if you've got a mo) ? I have to admit this is the first time I've had to roll up my sleeves and figure out something being wrong with textmate. It's been flawless up till now. In fact, I'm not even sure it's a problem with textmate. COuld be something else I've done.
thanks ! Daryl.
On 5-Dec-07, at 10:04 PM, Allan Odgaard wrote:
On 4 Dec 2007, at 11:48, Daryl Manning wrote:
[...] the Commit window still just infinite barber poles and never comes back.
Should I use ethereal or netstat to see what is going on a this point ?
If you are experienced enough with those to decipher svn traffic.
Otherwise I think you’ll have to add some debug log statement to the actual command, to figure out exactly how it calls svn and why that might fail on your system.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 16 Dec 2007, at 04:56, Daryl Manning wrote:
The debug log statement sounds like a good bet to start. Can you let me know where I'd add that in the bundle code (or walk me through it if you've got a mo) ? I have to admit this is the first time I've had to roll up my sleeves and figure out something being wrong with textmate. It's been flawless up till now. In fact, I'm not even sure it's a problem with textmate. COuld be something else I've done.
Basically look in Subversion.tmbundle/Support -- most stuff happens by means of running some Ruby scripts. But if you’re not vaguely familiar with Ruby, having you try debug the problem by editing these, might not be feasible.
First off... happy holidays !... =]
I tried using another GUI app to do the same thing (svnX) and it failed the same way but with a message. I get a : svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/projects/!svn/act/a4e9a336-2842-0410-9799- b128348ad9fe': authorization failed (http://domain_removed.com)
when I attempt this, so if it is like the textmate problem (even if the CLI commands work and give me a prompt) it looks like the credentials have either been cached and are failing (not likely since I just nuked the .subversion/auth directories to see if that worked) or... for some weird reason, the authorization prompt is not causing textmate to prompt me for the username/pass (which it used to do before). Since svnx is also doing this, it *might* be something weird on the server (they moved to global write and giving me w access, but the command line client works fine).
I've updated to subversion 1.4.6 in case that had anything to do with it and I'm using http:// authorization on textdrive.
Is there anything there that you can think of ? (or is there any way to explicitly force the --username svn swtich).
Anyhow, all help appreciated.
thanks and ciao ! Daryl.
On 20-Dec-07, at 4:43 AM, Allan Odgaard wrote:
On 16 Dec 2007, at 04:56, Daryl Manning wrote:
The debug log statement sounds like a good bet to start. Can you let me know where I'd add that in the bundle code (or walk me through it if you've got a mo) ? I have to admit this is the first time I've had to roll up my sleeves and figure out something being wrong with textmate. It's been flawless up till now. In fact, I'm not even sure it's a problem with textmate. COuld be something else I've done.
Basically look in Subversion.tmbundle/Support -- most stuff happens by means of running some Ruby scripts. But if you’re not vaguely familiar with Ruby, having you try debug the problem by editing these, might not be feasible.
Got it working... nuking the authorization directory and then setting
[auth] store-auth-creds = yes
in the command line client .subversion/config
then used the command line client to do a checkin.
*Then* used textmate to svn ci (commit) a file... Yayy ! Works... =]
Just wanted to thank everyone that nudged me towards figuring it out...
happy holidays ! Daryl.
On 25-Dec-07, at 7:47 PM, Daryl Manning wrote:
First off... happy holidays !... =]
I tried using another GUI app to do the same thing (svnX) and it failed the same way but with a message. I get a : svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/projects/!svn/act/a4e9a336-2842-0410-9799- b128348ad9fe': authorization failed (http://domain_removed.com)
when I attempt this, so if it is like the textmate problem (even if the CLI commands work and give me a prompt) it looks like the credentials have either been cached and are failing (not likely since I just nuked the .subversion/auth directories to see if that worked) or... for some weird reason, the authorization prompt is not causing textmate to prompt me for the username/pass (which it used to do before). Since svnx is also doing this, it *might* be something weird on the server (they moved to global write and giving me w access, but the command line client works fine).
I've updated to subversion 1.4.6 in case that had anything to do with it and I'm using http:// authorization on textdrive.
Is there anything there that you can think of ? (or is there any way to explicitly force the --username svn swtich).
Anyhow, all help appreciated.
thanks and ciao ! Daryl.
On 20-Dec-07, at 4:43 AM, Allan Odgaard wrote:
On 16 Dec 2007, at 04:56, Daryl Manning wrote:
The debug log statement sounds like a good bet to start. Can you let me know where I'd add that in the bundle code (or walk me through it if you've got a mo) ? I have to admit this is the first time I've had to roll up my sleeves and figure out something being wrong with textmate. It's been flawless up till now. In fact, I'm not even sure it's a problem with textmate. COuld be something else I've done.
Basically look in Subversion.tmbundle/Support -- most stuff happens by means of running some Ruby scripts. But if you’re not vaguely familiar with Ruby, having you try debug the problem by editing these, might not be feasible.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Dec 3, 2007, at 9:51 PM, Allan Odgaard wrote:
On 4 Dec 2007, at 03:14, Daryl Manning wrote:
[...] Anyone have an idea of how to get rid of these errors ?
Try move/rename/trash /Users/daryl/Library/InputManagers
I think each and every Cocoa application reads this directory on startup, so if you haven't already, you might also want to restart TextMate.
--- Rob McBroom http://www.skurfer.com/ I didn't "switch" to Apple... my OS did.
I did this but the problem of the commit window not giving me the option of providing the password for the repository to check in the file changes persists (the barberpole progress bar never goes away and I have to quite sbuversion and then svn cleanup the files to be able to try again).
I also tried a few other commands (like Diff Revisions and while it allows me to select from the various revisions and then hit ok it goes off with the same sort of barber pole and never comes back with the two files diffed).
The only thing I can think of that has changed is that while my user account is the only one with w access to the repository, the read has been changed to global (via http://domain.com/svn... ).
Does anyone think that might have caused a problem ? It seems strange because the command line svn commands issued from the terminal (well, iTerm) work fine
Absolutely stumped and console is not giving me any messages when the Commit window goes into infinite progress mode. Is there something like a TM_SVN_LOGIN environment varialbe I need to set or that may be hidden in the Preference file somewhere ?
Any help appreciated... Either diagnosing or solving... kind of a puzzler.
thanks, Daryl.
On 4-Dec-07, at 2:51 AM, Allan Odgaard wrote:
On 4 Dec 2007, at 03:14, Daryl Manning wrote:
[...] Anyone have an idea of how to get rid of these errors ?
Try move/rename/trash /Users/daryl/Library/InputManagers
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Removing the files under my user directory that corresponded to the bad Bundles had no effect on the svn commit transfer. Unfortunately, it still tries to commit without ever getting an account prompt. There is no info written into the Console.
Anyone else run across a similar problem ? Command line svn works fine.
all help appreciated thanks, Daryl.
On 3-Dec-07, at 1:15 PM, Allan Odgaard wrote:
On 2 Dec 2007, at 18:15, Daryl Manning wrote:
[...] Does anyone have any idea of what may be causing this and how to correct it ? I've gotten so used to the svn budle it's really cramping my style now...
No idea, but try open Console and see if there is any output. The command should redirect stderr to /dev/console.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Allan Odgaard -
Daryl Manning -
Rob McBroom