The view within sourcetree has to be manually updated by hitting F5 as of version 3.3.6.3829. I attempted to raise this as a bug on https://jira.atlassian.com/, but the form doesn't give me a correct option for version with 3.2 being the most up to date version available. If someone can point me to the correct place to raise this bug, it would be much appreciated.
This happened to me and the only way was to reinstall SourceTree 3.2.1, at least until the refresh bug gets fixed by Atlassian. I can't complain, it's a great tool and it's free, but this was annoying. I'm always a little apprehensive upgrading software I make, much less someone else's!
Here is the download page you can install older versions, I suggest 3.2.1, which works great! https://www.sourcetreeapp.com/download-archives
Following up: I'm on Windows and at least in my instance to get it to work all I did was:
Close SourceTree
Download 3.2.1 from the link above
Run the installer
Then I opened SourceTree and it reverted the version back by itself and I haven't had any issues since. I hope this helps!
The installer may be at fault. I found that my Source Tree short cuts didn't point to the correct "start in" folder. I thought correcting that has fixed the refresh problem, but I was wrong.
Related
So i updated from Netbeans 8.0.2 to 8.2 and now i have this very annoying bug : when i move the cursor down, the scrollbar won't auto scroll, so the cursor simply disappears ! I need to manually scroll to get the cursor visible again.
I'm on Mac Os 10.13.4. Anyone had this bug and could fix it ? Otherwise i'll have downgrade to get my things done properly again.
Thanks !
I don't know about MacOS but I have noticed that behavior on Linux too. It happens every time I type an accented character (e.g. á, é).
The solution I've found is adding env XMODIFIERS="" to the beginning of the command line in the .desktop file (the default is XMODIFIERS=#im=ibus on Ubuntu 20.04). Or simply starting it from the command line as XMODIFIERS="" netbeans
I'm posting this a little late because it's becoming increasingly difficult to find old versions of NetBeans after they moved from Oracle to Apache. So if you are stuck with a specific version and can't downgrade/upgrade, this answer might be helpful.
I checked NetBeans bugs and don't see an exact match for your problem, but there are plenty of similar ones. Note that bugs marked as RESOLVED haven't necessarily been applied to the released version of 8.2.
However, you could use a DEV version of NetBeans that would have the fixes applied, and as an added bonus you could also use JDK9 which you can't do on 8.2. That approach might be preferable to downgrading. Also note that the DEV version of NB could run concurrently with 8.2.
I'm trying to get VSCode working with my Unity projects, and every time I select the Project icon (the little fire at the bottom) I get the following error:
Error: Failed to connect to OmniSharp
Is anyone else getting this?
You need to download the most recent version of "mono". Open up terminal and pass in brew install mono. Then "Pick a project" and select the ..-csharp.sln file and you should be up and running.
Ok, made some progress and gotten a few Unity projects working. It seems that you need some prerequisites installed, a clean up of your Unity project folder, and possibly some hand editing of your .sln and .csproj files.
I posted a (possibly) better answer over on Reddit. Hope that's not breaking stack etiquitte.
http://www.reddit.com/r/Unity3D/comments/34d6gc/visual_studio_for_mac_help_us_vote_for_unity/
i get this on windows when my project directory has a space in it
i removed the space and removed the error
i expect it will be fixed soom
I have a completely different answer: it's the runtime that VSCode is using. It doesn't match up with what it thinks it needs. I have to remember that we're still in beta and that things are changing rapidly. I had my dnvm running beta 7, but VSCode (and OmniSharp, by extension) is looking for beta 6, so it was failing. I updated my runtime using this this post as a clue. Now I have VSCode 0.7.0 using the beta 6 runtime. I have no idea how to tell what it's looking for...I just guessed based on when they were both released. HTH
At present I cannot run it (SQL Developer 4.1) because it hangs on "Restoring Editors" while starting. I suppose I've done it by exiting it before by killing sql developer process because it was hanged on fetching objects to Schema Browser so long...
Maybe I would clean some temporary files but can't find any.
Any ideas?
Deleting files from c:\Users\MY_USER\AppData\Roaming\SQL Developer\SQL History
and c:\Users\MY_USER\AppData\Roaming\SQL Developer\System...
Really helped me to resolve the connection issues
Basing on this thread https://community.oracle.com/thread/2564842 I've created own solution.
Extract installation of current version SQL Developer (4.1.0.17.29)
At "c:\Users\MY_USER\AppData\Roaming\SQL Developer\"
I've changed directory name system4.1.0.17.29 to system4.1.0.17.28.
After running newly extracted SQL Developer (4.1.0.17.29) I was prompted to let copy configuration from version 4.1.0.17.28 to 4.1.0.17.29 ;)
Everything works great now. I suppose that running the same (broken) installation after decreasing version could also help.
Remove folders c:\Users\USERNAME\AppData\Roaming\SQL Developer\system4.1.3.20.78\system_cache*. SQLDeveloper will recreate it after launching.
Just execute sqldeveloper as administrator. It works fine!
In my case the problem was because of windows compatibility issue. So I've selected my windows version and it's stop from randomly crash after startup
Our setup:
Windows 10
Sqldeveloper Versions <= 20.4.0
We observed this problem as well. Even worse while working over a VPN connection. I followed a couple of hints with more or less no effect.
To move
C:\Users\<USER>\AppData\Roaming\SQL Developer
to a local directory by adding this line
AddVMOption -Dide.user.dir=c:\temp\sqldev-conf
in the \sqldeveloper\bin\sqldeveloper.conf file gave us some improvement, but the “IndexPreferencesTask” still got stuck several times on startup.
After some more hours on unsuccessful research, we moved back from JDK 11 to JDK 8.
This solved 99% of the problem. The “IndexPreferencesTask” still hangs on startup but for less than a second.
Sounds to me like a problem with JDK 11.
In my case when i changed Tools --> Preferences --> Environment -> Look and Feel to Windows it is solved.
Delete the History files from C:\Users\User\AppData\Roaming\sqldeveloper
Restart the PC
In my case, the solution was kind of weird. After battling to resolve this for 2 days, no luck. Suddenly, on my mac, I searched for sql developer, not sqldeveloper. It popped up a sqldeveloper application (not sure how that is different from what I have been trying to open ), clicked it and boom, it opened. My guess is that there is a copy of that app on my system that I should have been opening rather than trying to open the reinstalled app. Note: I reinstalled the app after it started misbehaving though.
Operating System: Windows 10
Oracle Sqldeveloper Ver: 17.4.0
The problem has been noticed sometime when any network security
patch was installed on your machine. Looks like the patch impacts
your cached data under your user profile folder.
As above Lakh, rtbf and others answered. Removing below folders
will resolve the issue.
C:\Users\<userId>\AppData\Roaming\SQL Developer\SqlHistory
C:\Users\<userId>\AppData\Roaming\SQL Developer\system17.4.0.355.2349
If any one find more approriate reason please feel free to
disagree with my answer.
I am having a small problem with plugins not staying installed with Coda 2.2 for Mac on OSX 10.6. Every time I close Coda and open it back up and then click on plugins half of them are gone even though the are in the plugins folder for the application. I have to close Coda and uninstall and reinstall the plugin then open it back up. That is only good until I close it then it starts all over again. Is there anything I can do or is there something I am overlooking that is causing this to happen?
-Thanks
I've been working with Panic support and we've discovered there's an issue with certain plugins. Most likely, it's only one that's problematic. For me, it was WVCPs plugin. Removing that from the plugin folder allows all other plugins to work fine.
I found it helpful looking at the Console app for messages from Coda and one by one dropped the plugins back into the plugins folder until I found the one that caused an error about incompatible architecture.
You can ignore the error about two plugins implementing the same class, that seems to be a mutual exclusion sort of warning but still allows the other plugins to work.
One other plugin had a different error but again, appears to work fine so probably it was just a warning.
This is probably your best solution until Panic push out an update, which I am assured is on the way.
Hope that helps!
I just upgraded my Xcode, now when I try to open my project, I get this error:
Project /Users/xxx/xxxx/xxxxx/xxxxxx/xxxxxxxx.xcodeproj cannot be opened: PBXContainerItemProxy (xxxxxxxxxxxxxxxxx) is missing a containerPortal key
I have searched the web and stackoverflow, but cannot get anything relevent to come up at all regarding this.
I do have Three20 as part of my project, I don't know if that matters. I just upgraded to xcode 4.4.1
Thanks for any insight.
-D
the project icon which we see i.e projectname.xcodeproj, is actually a directory, you do this
1. in terminal do cd yourproject.xcodeproj
2.ls
3.vi project.pbxproj
4. scroll down till /* Begin PBXContainerItemProxy section */
5.there you will see all sections check for the section which is missing a portal key edit it and save it :wq it will work
in image if you see the first section is missing container portal key.just pic it from other section and replace it..
it will work :D see this link
Now I should start with that I do not know the actual error, never seen it before, but I did find a reference to a "PBXContainerProxy"-error in this post (As soon as I add a project to XCode 4.0.2 it crashes) and thought you might try the solutions from there?
"Apparently this is due to the new version of XCodeProjects. I found a
work around by pre-compiling the library that was causing the issue
and then using the linker to link to the .a file. I also had to copy
the .a library into the DerivedData path.
The real solution was to remove the project and replace it with an
updated project for the new version of XCode."
Hope that helps somewhat :)
Never saw that error either, but if you're upgrading directly from XCode 3.X I'd suggest you to go to https://developer.apple.com/downloads/index.action?name=Xcode
and download/install a previous version of Xcode somewhere else. (You can have several different copies installed on your machine, just google it if you don't know how but just remember to use xcode-select to pick the one you want to use). Repeat with all the versions back to 4.0.1 until (hopefully) it works. I know it's tedious but it might help.
If it does, validate the project settings and try to open it with 4.4.1. That should work.
Good luck