• Jim (unregistered) in reply to caffiend
    caffiend:
    MichaelWojcik:
    but Real Programmers who use the svn command-line client have a better chance of killing a hung client process or fixing a corrupted working copy (the most likely causes of the "Subversion keeps requesting cleanup" problem).

    Honestly mate, you've gotta be kidding. In terms of actual productivity, there is no way even the most proficient greybeard using the command-line client for "svn" (notice i didn't capitalize it this time) would be more productive than a mediocre engineer using a GUI. It's just not a winnable argument.

    With all due respect, bollocks! ;-) I'm no greybeard guru but I have used TortoiseSVN and the command line, and for the day in day out stuff I have a selection of aliases and scripts for the command line which certainly improve my productivity.

    To take one example, can TortoiseSVN run a merge and then automatically resolve most tree conflicts?

    I'm not saying that GUI tools don't have a place, but you write off the command line at your peril.

  • (cs) in reply to caffiend
    caffiend:
    Has anyone ever seen that Tortoise SVN 'Cleanup' command do anything useful?

    I'm pretty sure it's implementation is to roll a dice to decide whether to: a) further corrupt your working copy making the problem worse, b) crash, or c) tell you to run 'cleanup' again.

    Yes, but what that particular 'needs cleanup but will not cleanup' error is telling you is that you upgraded SVN before you tried to cleanup. New versions do not clear up the mess left by old versions.

    One of the other WTF side effects of upgrading SVN via the TortoiseSVN windows client is that the little icons in Windows vanish from the directories under SVN control until you go into one of the directories and do an 'upgrade'.

    So you fail to notice you upgraded without cleanup as all the evidence vanishes.

    And as you can see from the clarity of the message, they dont tell you WTF is going on.

    I escaped the trap by still having an older command-line version of SVN around which did the cleanup.

  • Valued Service (unregistered) in reply to Yazeran
    Yazeran:
    faoileag:
    From a developer point of view I really like the MySQL error message on dota2.com's website. It contains all the information one needs to debug the application: - name of method - name of attempted action - description of error - the value that caused the db error - and the column name which caused the db error. And the expletive is telling me that the original developer thought that this error would occur only rarely, if at all.

    Yep, in that you are correct, and sometimes 'cant happen' errors crop up no matter how hard you try to make sure that the code can never get there.

    I have experienced the same with a reservations system i designed some 5 years ago. Inside some stored procedures i had a 'trap' for the case where the end date was before the start date (something which the application should make sure could never happen). and the error message in that case was somewhat funny: 'Space time discontinuity error, you can not end before you start'. Imagine my surprise when it showed up in the logs sometimes regardless...

    Yazeran

    Plan: To go to mars one day with a hammer.

    Try having an error after a return statement, and then it hits because of stack corruption. That one, about landed me, in the hospital....

  • (cs) in reply to Indrek
    Indrek:
    It has failed you for the last time.
    You are in command now, Analyst Piett.
  • Norman Diamond (unregistered) in reply to mikedjames
    mikedjames:
    caffiend:
    Has anyone ever seen that Tortoise SVN 'Cleanup' command do anything useful?

    I'm pretty sure it's implementation is to roll a dice to decide whether to: a) further corrupt your working copy making the problem worse, b) crash, or c) tell you to run 'cleanup' again.

    Yes, but what that particular 'needs cleanup but will not cleanup' error is telling you is that you upgraded SVN before you tried to cleanup. New versions do not clear up the mess left by old versions.
    No it is not telling him that. YOU'RE the one telling him that.
    mikedjames:
    And as you can see from the clarity of the message, they dont tell you WTF is going on.
    See? You KNEW it wasn't telling him that.

Leave a comment on “Top Secret BSOD”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article