I started up minecraft forge and it crashed. So I went back to the launcher, minecraft is working fine in vanilla, but it won't launch forge.
I've tried going into the files to see if there was a problem, but I didn't find any. I've tried downloading a newer version of forge, but it didn't work either. I've tried the same with java, no success.
I'm using minecraft forge version 1.15.2.
Does anyone have a suggestion on how to fix this issue?
StackOverflow is not the place for support, you should head over to the MinecraftForge forums where they have a specific place for support.
Related
I've been using Atom for years on my Mac. I know it has been end-of-lifed by its dev team. I haven't installed anything new on it like plugins for many months. After the latest MacOS update, I get this popup when trying to open it:
Does anyone know if there is a way to tell if my copy has somehow become corrupted, or if this is a false positive?
Many thanks!
OK I found out that github revoked the Apple code signing certificate and is now enforcing that. I found the answer on the Atom blog. So, I was able to download an older version and it works well.
thanks for the info, i think it's the best time to find alternatives on text editors since Atom has been officially sunset (Sublime text?)
If you want the current installation to continue working:
$ xattr -cr /Applications/Atom.app
I'm not sure what the security risks of this are.
You might consider the Pulsar fork of the Atom project: https://pulsar-edit.dev/
I can't fully vouch for it because I'm just starting to use it, but it looks and feels the same to me.
How can I find out if requesst was installed with [security] option?
I am having a very strange problem with python requests.get/post().
The line used to work just fine and it stopped working. I was wondering if requests was installed properly. Is there anyway to check if requests was installed with [security] option?
My apologies if this is something simple but I cannot seem to find an answer to this anywhere.
I've set up VSCode on my macbook, and used yeoman to scaffold a default website (without authentication). I can build the project fine, but when I run and try to browse to it I'm getting a 500 error.
There is no response data so I can't get any more information than that, and the fact that it's Kestrel server.
I've also tried browsing to /home and /home/index etc but nothing
I'm hoping this is something simple that other people have encountered, and that there's an easy fix...
Many thanks in advance
For anyone else who may run into this, frankly I'm not entirely sure what fixed the problem, but: * I uninstalled Xamarin, which I also had installed * I uninstalled mono * I uninstalled VSCode * I reinstalled everything EXCEPT Xamarin The only other thing I did, was that I assumed (since it isn't said anywhere) that .Net Next was included in VSCode, but I installed that separately So, not sure which of these steps fixed it, whether I didn't have .net next which was required, or perhaps there were mono conflicts between VSCode and Xamarin but maybe this will be useful for someone else
I have properly set up JAVA_HOME, MAVEN_HOME to point to jdk home and maven installation homedirectory, and have also added JAVA_HOME/bin and MAVEN_HOME/bin in the PATH. But still when I execute karaf.bat I don't see any output as mentioned in the quick start guide here. Instead I see blank screen infinitely running. Please help me.
I am on Windows 7 64 bit.
After doing some google search, found this mail archive, which says the downloaded karaf could be corrupt.
As guided I downloaded the fresh karaf zip from another mirror (other than previously downloaded mirror) and now after installation, I am able to successfully run karaf.bat
I encounted the same problem. Apparently Karaf didn't start as it was described in the tutorial. Even more confusing was the fact that the log showed normal. Java process was created, the log said nothing wrong but Karaf console was silent.
After I tried to debug the problem for a while, I've discovered that downloading the zip from a different mirror solved the problem.
WEIRD HAPPENING.. I am unable to debug meteor app , BREAKPOINTS doesn't work in chrome(can see the server side sources thou).. I have already wasted 2 days over it ..
I have already tried
Meteor: Debug on server side
Also tried similar options changing web-port and other options.
Also tried to reduce the node-inspector version, BUT breakpoints are not working for me..
any suggestions on how to debug this issue?
(Chrome browser, ubuntu, AMD machine, if that matters)
I have the same issue. The only workaround I've found is to put debugger; statements in my code. Those are respected and treated as breakpoints which stop the server for Node Inspector.
you can try observatory or read this article, maybe it'll helps
You are not alone. There is an issue posted to github about this, and it appears to be confirmed by several users.
I was able to get Node Inspector to work a while ago by downgrading to 1.10. It's not as nice as the new version but worked last time I used it. I honestly haven't needed it recently, but hopefully it'll still work.