My computer version is Win7.
And what ever .py I debug, this pycharm will show me en error like this:
ValueError: bad marshal data (string ref out of range)
So what's wrong with pycharm, I tried to user newest version of pycharm but I helpless, the same error will show again.
I used to reinstall my win7 (becauser I have Shadow Mode software) and it work for a period.
Is there body have a good solution?
I don't think the problem is directly related to the pydev debugger in this case... my bet is that for some reason you're having corrupted .pyc files (don't know why thought).
Try cleaning your .pyc files from your pycharm installation and your own files and run it again (you may try running with pydev which has the same debugger backend if you want to see if you reproduce the issue there).
Related
I recently wanted to try to again update my IntelliJ IDEA because I had problems before (I still have problems hence this post). I've tried re-installing, fiddling with VM options, all what the internet says, but nothing provides any answers.
It starts when I click the .exe file of IntelliJ. It will briefly pop up in the task manager, use about 20% CPU for about 8 seconds and then disappear. It doesn't open later also. I've also tried to start it from the CLI, but that gives me this:
cli-output
I currently have IntelliJ 2019 since it's the only version that works, all the other versions I tried have the same problem. Does anyone know how I can resolve this (I'm running on Windows 10)?
I had the same issue on my windows 10. To fix it go to %USERPROFILE%\AppData\Roaming\JetBrains\IntelliJIdea2021.2\ folder and try to remove idea64.exe.jdk file, then run IntelliJ again.
P.s. I'm using JetBrains Toolbox, so all files that need to run IntelliJ will be placed into %USERPROFILE%\AppData\Roaming\JetBrains automatically after installation.
For the last 2-3 weeks, my VS Code terminal has been blank. Not sure when it exactly started or what might have changed to cause this.
I usually use GIT Bash as my default terminal in VS Code, but this happens even if i switch to CMD or Powershell.
I have already uninstalled/reinstalled VS Code (did not solve the issue).
I have also seen this issue online, but no real solution seems to be out there.
Is there some VS Code setting i can fiddle with to try and fix it?
Also, When i have VS Code open to a project, I do get a file put into my project folder named bash.exe.stackdump which some very odd numerical info dump. Nothing easy to decode.
Here's how I have solved this issue.
I unchecked the compatibility mode in VS Code properties where it says Run this program in compatibility mode for:
I'm trying to avoid having to restore my PC and get it back to where I was. I was recently going to delete a folder using Shift+Del, but without paying too close attention I hit Shift+Del on the modules folder in C:\ProgramFiles\WindowsPowerShell\Modules.
I had re-imported PowerShellGet, PackageManagement, as well as Pester.
I thought I was in the clear but I keep running into issues, I have to always Re-Import PowershellGet. Then I get another error.
Get-PSRepository : The term 'PackageManagement\Get-PackageSource' is not recognized as the name of a cmdlet, function, script file.
Even after doing Import-PackageManagement I still get that error.
If I do (Get-Module -List Available -Name PackageManagement).Exportedcmdlets it shows that Get-PackageSource is there.
I'm really not sure what I need to do to fix this.
I have uninstalled and reintalled WMF 5.1, but the issue persists.
I am running Windows 8.1
PowerShell is an open source project. You can download the modules from github. That link also describes how to get from PowerShell Gallery, which may work for you.
Main PowerShell repo
PackageManagement (aka Oneget)
The issue seems to be with PackageManagement, 1.1.4.0. I deleted that reimported PackageManagement based on what i read here. https://github.com/OneGet/oneget/issues/195
It seems to be working now.
After a crash of QtCreator it won't open any project anymore.
If I try to open a project (that worked perfectly well before the crash) the QtCreator seems to ignore me (I tried several ways of opening a project through the QtCreator).
If I open the QtCreator directly via a *.pro file it opens the project file as plain text without any syntax-highlighting.
If I try creating a new project it tells me "No valid kits found". None of the solutions I found to this problem helped me, though.
To fix the problem I've tried:
restarting the Computer ;-)
cloning the auto-detected compiler settings and verified each path
I'm using QtCreator 3.0.0 with MinGW 4.8 32bit based on Qt 5.2.0 (all precompiled)
I would like to avoid a reinstallation of QtCreator, if possible.
Solution:
I fixed the problem by myself - I figured out one of my config files got corrupted; see full answer below.
I tracked the issue down by myself:
In the FAQ I found the entry how to reset all QtCreator settings. After doing this the QtCreator worked again.
I wrote I didn't want to reinstall the QtCreator (because of the settings), so I restored the old config from the bin and tried deleting the corrupted config file only.
When I finally deleted QtProject/qtcreator/mimetypes/modifiedmimetypes.xml QtCreator worked again. I remember messing with the mimetypes prior to the crash, so I guess that's it.
I've got an MSI based install that I've wrapped in an EXE file as per my installation packaging software (which is Wise Package Studio 7.0 SP2).
I've made many changes to the install, and every time I've tested them, they've worked just fine... up until now.
I changed some text on a dialog box for when the installation finishes and now it seems that no matter how/where I run the installation from, it won't take my "new" version. It continues to "think" it's already installed and even shows an older iteration of my dialog text at then end of the removal/repair/modify.
It's almost like it's cached that MSI/EXE somewhere and instead of running the one I've recompiled (and fixed the message/made changes) it continues to run the "old" one from somewhere.
Any idea what to check for/what could be going on here? Is there windows folder I need to go check? I'm on XP SP2.
Try running on a different machine, this will definitely rule out any local caching.
Check that the changes you have made are actually in the MSI. (use Orca to do this.)
Okay, so I tried this using an XP VM and taking a snapshot before installing. Looks like somehow the previous install was corrupt and was somehow caching itself on the original test computer I was working with.
By going to a clean and fresh PC, my changes were there and the script worked as expected. Now, I don't know what happened to cause the installation to cache like that somewhere on the PC, but at least I found a resolution.
I'll update this question with the location of the cached files if I can track them down...
To remove any cached Windows Installer information, you can use MSIZAP. My guess is that you haven't changed the package code so windows sees it as the same version of the installer (I'm not sure about WISE, but InstallShield is usually configured to automatically change the package code each time you rebuild.)
As far as the location of the cached files, this is configurable so have a hunt around in WISE and you should find it.