I have the following problem
WHen lunching FlashBuilder.exe (BURRITO): it crashes and creates an error log file such us:
hs_err_pid7084.log and following
But when I munch FlashBuilderC.exe : it opens a CMD dos window and flash builder starts.
I tried to reinstall it : no way.
Can one help me ?
I found a solution removeing some .metadatas in Eclips or similar but I cannot find it any more
Regards
It may be a little bit late for an answer, but you can try to do this:
Step 1:
Go to your User directory and navigate to your Flash Builder Files:
FOR WINDOWS:
C:\Users\[YOUR USER] \Adobe Flash Builder
4.5\.metadata\.plugins\org.eclipse.core.resources\
FOR OSX {FILES HIDDEN}:
[Flash Builder Workspace
Directory]\.metadata\org.eclipse.core.resources\
Step 2:
If there is a ".snap" file, delete it and then start "FlashBuilderC.exe" in Admin-Mode
FOR WINDOWS BY DEFAULT:
C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\
Step 3:
Close Flash Builder again and then open Flash Builder normally (should work again)
I hope this helps someone.
I've had this problem a couple of times. For the first time, deleting the .snap file worked. Not the second time, however.
I looked at the log file for the workspace located under the .metadata folder (inside your Flash Builder files, typically: c:\Users\[YOUR USER]\Adobe Flash Builder 4.5\), and found the following line towards the end:
!MESSAGE Job found still running after platform shutdown. Jobs
should be canceled by the plugin that scheduled them during shutdown:
I solved this by deleting the file workbench.xml in the org.eclipse.ui.workbench folder under the .plugins one, and then starting up the Flash Builder again.
The workspace at least opened, admittedly with a problematic project but at least I could fix it from there.
Try deleting:
C:\Users\[USERNAME]\Adobe Flash Builder 4.7\.metadata\.plugins\org.eclipse.ui.workbench
When this happens, I usuall just delete the metadata from my workspace and the reimport all the existing projects to workspace.
Run the following inside your workspace:
$ rm -rf .metadata
This was happening often enough for me that I ended up writing a batch file to fix the issue, using Marchar and fenomas's posts - thanks guys! (Note - ensure the Flash Builder process has been killed before running it)
cd C:\Users\[your name here]\Adobe Flash Builder 4.7\.metadata
del .lock
cd C:\Users\[your name here]\Adobe Flash Builder 4.7\.metadata\.plugins\org.eclipse.core.resources
del .snap
My eventual solution:
Rename the workspace folder. [My default was at C:\Users\jhouser\Adobe Flash Builder 4]
Start up Flash Builder. Behold! It starts! All the projects are now broken because the paths are now incorrect.
Shut down Flash Builder.
Rename the workspace folder back to what it was.
Start up Flash Builder.
I had the same experience as Apollo M. Deleting the .snap and .lock files didn't work for me.
I located the workbench.xml file (C:\Users[your name here]\Documents[your project directory].metadata.plugins\org.eclipse.ui.workbench) and deleted the individual entries under the "" tag.
Nice thing about this is that my workspace opened correctly, with no need to re-import my projects.
Related
Steps to reproduce are very easy.
Create a Dockerfile.
My Dockerfile has many more lines, but I have trimmed them so we can focus in the source of the problem.
Said that, these two lines alone (without anything more) show the problem.
FROM microsoft/iis
SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; $VerbosePreference = 'Continue'; "]
Run docker build . and you get hcsshim::PrepareLayer - failed failed in Win32: Función incorrecta. (0x1).
Windows 10 Pro 1909 (but it happened too in 1903)
Docker version: 2.1.0.5
Engine: 19.03.5
Machine: 0.16.2
I have found the solution to the problem.
Reading all the https://github.com/docker/for-win/issues/3884 bug, some have found a simple solution: rename C:\windows\system32\driver\cbfsconnect2017.sys so it isn't loaded the next boot.
Disabling that driver enables me to do a docker build for the first time in windows containers in almost a year.
In my case Box Sync was the one using that driver.
EDIT: #GustavoTM have found that pCloud raises the same problem.
EDIT2: #VonC have noticed that some people in the issue in GitHub has solved it deleting this other file: C:\Windows\System32\drivers\cbfs6.sys. I haven't tried that, but i put it if it helps others.
The good thing is that I don't need to uninstall Box, but only rename that file.
This is still an issue (still open) with Win10.
Looks like uninstalling cloud storage providers with file system filters like Dropbox, Box, etc. as a workaround is an option for some users.
Deinstall cloud storage providers or virus scanners; if you identify which one is not working please share in https://github.com/docker/for-win/issues/3884
In my case was the problem similar but the file cbfs6.sys was placed somewhere in the rest of uninstalled application Jungle disk, somewhere in the folder c:\Program files\Jungle disk .... It's part of Callback File System signed by EldoS Corporation.
The folder could be rename only and not delete directly. So I could delete its immediately after the PC restart, before running the Docker. So it could be delete during the Docker service restart too.
When I executed "p4 client" to make some changes in my workspace view on MacOS High Sierra for perforce, the changes were not saved and command "p4 client" at the prompt did not close (exit) when I closed the workspace-view file.
Can someone please tell me what I am missing/doing wrong?
Thanks
I resolved my issue by deleting the existing workspace view and created a new workspace view. In the new workspace view, I simply mapped the depot to /my_workspace_view/. Before, I mapped the depot to /my_workspace_view///...
In my configuration, p4 client <workspace_name> opened TextMate (a GUI app), and simply saving and closing the document left the terminal waiting for changes.
The trick was to save and quit TextMate, and the client was saved correctly.
After a while, using WebStorm, when I try to rename a folder or a file I get this error in the Rename pop up window.
java.io.IOException : com.intellij.openapi.vcs.VcsException: No administrative area found under /Users/[Name]/..../[ProjectName]
To fix the issue I have to use Invalidate Caches and restart... option but it is not very convenient.
Can anyone explain what is going on?
Just delete all of your .idea. folders and reopen IntelliJ.
I have been working with phpStorm and it had suddenly stopped showing suggestions for code completion. When i do Ctrl + space its behaving correctly by showing all the possible options in a drop down.
I have followed the below link and have did invalidate cache but still of no use.
PhpStorm code completion doesn't show core classes/extensions
My Setup is:
OS: Mac - 10.9.2 (Mavericks)
PHPStorm: 7.1.3
I just had the same problem, fixed it when I realized I mistakenly put PHPStorm in Power Save Mode. Click the little fellow on the bottom right of your PHPStorm window and switch that off
Indeed, the Power saving mode (File > Power Saving Mode) allow you to disable the code inspection functionnality.
However sometimes the PhpStorm code analysis failed and you lost your code completion. In this case you juste have to ask for a new code analysis (File > Synchronize [CTRL+ALT+Y]) or invalid the cache and force a restart (File > Invalid cache / Restart).
Hope that helps.
Invalidating the cache did not work for me, but this did:
Enable power save mode (File > Power Save Mode), then disable it.
If your are using a Linux distro (Ubuntu, Debian, Centos) etc, it is due to ibus.
Just change the Shortcut (run: ibus-setup and change to Super+Ctrl+Space for instance) and everything will be fine again.
Or (my favorite): uninstall ibus if you are not using it.
In a Debian/Ubuntu distro should be:
sudo apt-get remove ibus
Ctrl+Space autocompletion should be back.
It was power saving mode for me too. It's an option at the bottom of the File menu.
install a previous version
https://www.jetbrains.com/phpstorm/download/other.html
Worked for me after I tried everything.
I struggled with this for a few hours this morning. After invalidation of caches, a complete reinstall, etc.. nothing worked.
I closed phpstorm and removed the .idea folder in the filesystem. I then renamed the project folder and reopened it. Autocomplete was now working!
I noticed that phpstorm then created the old project directory in the background, even though I did not open it and put a .idea folder in it. Something is obviously corrupted here.
" ... stopped showing suggestions for code completion".
On mac you can invoke it by fn+ctrl+space.
Going to php-storm -> Settings -> Keymap -> Set Active Changelist you can see it is associated with ^+space.
on windows ctrl+space
I have been unable to overcome this error in Application Loader. I've quit, restarted, tried different computers - it's like the server is hung up on an op that I never initiated and it won't time out. Has anyone seen it before and beaten it?
Basically, you need to clear out the transport tokens. This can happen if you were to close out of Xcode while in the middle of submitting an app to iTunes Connect.
The token files now appear in the
Library/Caches/com.apple.amp.itmstransporter/UploadTokens/ subfolder of the given user's home directory. Which, honestly, is a better place for them anyway.
Delete any .token files in this directory.
--
If you are unable to find the .token files, this is because they are hidden in Finder. To hide/show hidden files in Finder, use the following Terminal command (TRUE = UNHIDE, FALSE = HIDE):
defaults write com.apple.finder AppleShowAllFiles TRUE;killall Finder
You need to clear out the transport tokens.
Open Terminal on your Mac, and paste:
rm /Users/<username>/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/*.token
That should clear the stuck token. After this, try uploading the build again.
It might be because Xcode crashed as you were uploading your app. Either, all you need to do is delete the token files:
Open Terminal on your Mac, and paste:
rm ~/.itmstransporter/UploadTokens/*.token
That should clear it. If it still doesn't work (at this point you should try re-uploading your app), run that command on Terminal again, or manually go to...
/Users/<username>/.itmstransporter/UploadTokens/
...and delete all the .token files.
Hope that helps!
token was in here
/Users/(user_name)/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/
Appreciated #WrightsCS 's answer It helps me to overcome Application Loader issue.
I would like to highlight one more thing here.
I proceed as per #WrightsCS answer and it resolved Application loader error:
Can not proceed with delivery: an existing transporter instance is currently uploading this package
But I found one more issue after removing all tokens from
/Users//.itmstransporter/UploadTokens/
I went to iTunesConnect and clicked on "My Apps", what I saw a message that "Can not connect... please contact Apple".
Here I don't know why it suddenly stops working!
I submitted the same build which was there on iTunesConnect for submission but it has shown as processing.
After submission of that build, iTunesConnect works fine! Also, I am able to see last uploaded build in a list for submission.
In my case (I am using OSX Catalina), I was not able to find the folder:
Library/Caches/com.apple.amp.itmstransporter/UploadTokens/
Under my user home directory (even when showing hidden files and folders)
but it seems my problem was a bit different and I just closed xCode completely (every xCode window opened) and reopened it again then I archived my project and uploaded it without any issues
maybe this could help someone else fix this issue
You need to clear out the upload tokens that are "stuck". To do this, open the tokens file found in /users//.itmstransporter/UploadTokens/. You should see one line of text at the top that refers to your current upload token. Simply delete this line and save the file. You should now be able to submit your app again.
Cheers