Grass roots developers always have a tough life. They have so many demanding bosses to serve, and work load piled high to finish, everyday. But that is not all.
After spending premium to buy latest IntelliJ 12, only a few honeymoon days with Darcula theme, then find out SVN is broken. When sync with SVN repository with JIRA SVN branch, a red flash error indicating there is malfunction in the engine:
“E170001: HTTP proxy authorization failed”
Open the hood and inspect inside, everything looks absolutely fine. Proxy settings, authenticated user and password all good. Can connect to JetBrains website and check the latest update, but just can’t connect to JIRA SVN repository on the internet.
Relunctantly back to TortoiseSVN to check-in and check-out codes. Just like the its name, it’s bloody slow and painful.
Googling and digging, try to understand why IntelliJ is not smart enough this time and new version causes so silly problem. However, only find out a lot “me too”, “me too” replies.
Having wasted a few more days in vain, then start suspecting that maybe it’s not IntelliJ’s fault, maybe it’s new version SVN client – SVNKit’s problem.
When more evidence and witness’s testimony above water, then hear “rumours” that I.T security and network just did a major change recently, fixing a lot holes, of course breaking a lot windows at same time. What they did – Proxy Authentication against a LDAP backend server, especially by Microsoft Active directory and network may caused the chaos. You have to guess hard.