Sublime Text 2 packages won't install - package

I installed package control in Sublime Text 2, that worked fine.
I tried installing Xdebug first. The bar at the bottom was indicating that it was "installing" Xdebug. It went on for a long time and then stopped. When I checked, nothing had been downloaded or installed.
I manually placed the Xdebug package and it showed up on the list.
But I can't actually install any package via the package control.
I'm running this on Debian 7, in my home directory without sudo. Still, it's my home folder so rights shouldn't be a problem.
I tried running as root but that just doesn't seem like a good solution to me.
So, nothing gets downloaded and installed and there are no error messages. Can anybody help me determine the cause of this and how to fix it?
EDIT: opened the console, tried installing SublimeLinter, and I'm being told an HTTP 502 error occurred, which is a "bad gateway" error. I googled this and most I get are technical explanations and the fact that "a piece of equipment might be failing". Not very helpful.

Github is currently experiencing a service outage (https://status.github.com/) which prevents the Sublime Text Package Control from downloading packages from Github.

Related

How can I enable my C extension on VScode

I’ve downloaded .C file in my VSCode and I’ve installed it but it refused open
I was expecting it to open but it to run but it’s showing platform package installation failed every time I install it and try to run a program
i also faced the same problem however taking help from a video tutorial while installing the packages helped me out. please refer to the link given below
do not forget to first delete all the packages that u have installed on your own as it might cause problem while following the instructions of the video
https://www.youtube.com/watch?v=9xCskNFVt2c

PimCore X Not Loading

I've been following the guide found here, https://unixcop.com/how-to-install-pimcore-on-ubuntu-20-04/, to install the PimCore X version from scratch on a fresh server.
However, after going through all of the steps and firing up the initial home page, I get the profiler complaining about a number of 404 errors for resources that it cannot find within the /_wdt/ folder, with the profiler never loading.
The admin section of PimCore cannot be loaded either, it comes up with a big 404 error, so I'm guessing that the router isn't working properly. Looking into the log files for both PimCore and Apache, there isn't anything useful to be found.
I've tried to install PimCore several times, each with the same result.
Any help would be gratefully received.
It turns out that the .htaccess file within the /public/ folder wasn't being installed with the fresh install. The .htaccess file contents can be found here, https://pimcore.com/docs/pimcore/current/Development_Documentation/Installation_and_Upgrade/System_Setup_and_Hosting/Apache_Configuration.html
Best way to install Pimcore are using docker.
You can read it on github page https://github.com/pimcore/skeleton
All that you need is install docker.
You can do it from this link https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-20-04

Hot reload stopped working after adjusting environment for work requirements

I started a new developer role a few days ago and made some environmental changes to adapt for work. Since then, my hot reload/fast refresh has just stopped working entirely. Changes don't show up even if I refresh the page manually. Only shows changes when I stop the dev server and restart it with 'npm run dev'. The triangle indicator at the bottom right should be active, showing active reload of the window (this no longer shows up consistently either, and if it does the page gets reloaded, but alas the proposed changes aren't visible)
Context:
It has this effect on all NextJS and react applications of mine. Even running a basic project template off the NextJS examples page shows no hot reload working.
I researched this issue and it seems wrong imports (e.g. importing components using lowercase or files in the pages directory being capitalized) can cause this, but I combed through the code and can't spot any issues (of course, I could be missing it but my codebase is over 300 files).
Service workers in the background can cause issues, but I cleared my browser of all of them to be sure and it still doesn't fix it.
I installed ngrok for tunneling for work purposes and docker-compose to handle the work dev. environment.
Made sure I'm using the latest Next version. Even deleted node_modules and ran npm install. Deleted .next and the out folder and still no luck.
Anybody have any ideas or clues to what I should try next? Is it related to the stuff I installed for work? Something related to VS code or WSL2? Seems so puzzling it kind of just happened overnight. Thanks for any insight or advice!
System information
OS: Windows (WSL2 virtualization for VS code)
Browser: Chrome
Version of Next.js: 10.0.3
Version of Node.js: 14.8.0
Deployment: npm run dev for development work; amplify publish for AWS hosting
The problem is with WSL2. I use WSL2 inside VS Code; which is a big performance upgrade in the Linux environment. The problem is WSL2 is actually in a 'virtualization' and thus cannot send information from VS Code AND the browser (localhost:3000) at the same time.
It's a big issue they are working on and there is no fix yet for it. That's why fast refresh doesn't work because localhost is not receiving the changes being made. Either proxy through or revert back to WSL1 https://github.com/microsoft/WSL/issues/4769
Solution provide by OP on question section
Add a .env file or a .env.local file to your root and put this line on it:
WATCHPACK_POLLING=true
Now, restart your server.
Thanks I encounter the same issue with WSL2. I just switch to windows terminal and it works.
If you run Poweshell as administrator and run
wsl.exe -l -v
This will give you th eversion of wsl your distros run on.
I am personally using Ubuntu, and this is the output
Ubuntu Running 2
docker-desktop Stopped 2
docker-desktop-data Stopped 2
To switch to wsl 1,
Run
wsl.exe --set-version Ubuntu 1
and if you wanna switch back,
run,
wsl.exe --set-version Ubuntu 2.
This worked for me.
In my react projects, I just add in my .env file at the root project folder the values
FAST_REFRESH=false
CHOKIDAR_USEPOLLING=true
and it works! enjoy!
The problem is with WSL2. I use WSL2 inside VS Code. But React JS and Next JS projects don't auto-reload. So, add a .env or .env.local (recommended) file to your root and put these lines on it:
WATCHPACK_POLLING=true
CHOKIDAR_USEPOLLING=true
Now, restart your server.

Drupal error "CKEditor is already installed" when trying to install

I installed CKEditor, but for some reason, when I opened the configuration, Drupal says: "CKEditor not installed."
I deleted the folder from sites\modules\ckeditor, then tried to install a different version. On trying to install, it still said "CKEditor is already installed", even though I'd deleted it (and checked it was no longer in the list of modules).
I guess there might be some trouble with the database.
How do I solve this?
Im idiot. Cause I opened by mistake a different FTP, user and was looking at different folder all/sites/modules.....in this folder I deleted everything, but of course the web I was working on had different module folder :-(. So it kept telling me CKEDITOR was installed why I couldn see it... I ll shoot myself soon. Sorry.

Codename One plugin uninstalled / reinstalled, still bug with a skin

A user has tried to install a new skin for the simulator and things did not work, see screenshot:
He uninstalled / reinstalled the CodenameOne plugin but the preview remains bugged as indicated on the screenshot above. Is there some hidden config files he should delete elsewhere?
Skins are installed in this directory: C:\Users\UserName\.codenameone, some of them might have been corrupted during addition.
You can try removing all before re-installing CN1 plugin to see if it solves the problem. Particularly the skins with recent Date modified.
This happens if you pick a corrupt skin file, we made several attempts at fixing it which apparently still didn't resolve the issue.
To workaround it in Windows launch the resedit tool and type into find: "JavaSEPort".
Delete everything you find in that search and it should restore you to the default state.

Resources