since the last week I am facing troubles entering into my google cloud sql settings in Google Cloud Platform portal. it hangs.
Might be someone faced the same issue, please help !
Thanks in advance!
It looks like there's a problem with our Russian translation which is causing this. It should be fixed soon, but as a temporary workaround you can switch to English in the Cloud Console settings.
Thanks to all, switching to English has solved the problem
Related
I have Live-Server extension installed in my VSCode.
I was trying to run the live-server but a pop-up appeared as below:
This is a reminder to make sure that you have not forgotten to attach 'c\Users\HP\AppData\Local\Temp\ritwickdey.LiveServer-unresponsive.cpuprofile.txt' to an existing performance issue.
I couldn't find much recourses to understand what the issue was or what action I should take about it.
BTW: Live Server is not loading the browser-page by its own, but at port:5500 its running.
Please Help.
after researching i found this blog, where i got to know that its because of performance issue
https://www.nicoespeon.com/en/2019/11/fix-vscode-extension-performance-issue/
first thing bundle your vsCode extensions:https://code.visualstudio.com/api/working-with-extensions/bundling-extension
if that solves the issue then great if not then add this extension to vsCode
https://marketplace.visualstudio.com/items?itemName=nicoespeon.abracadabra
hope the first link will provide complete solution.
Happy Learning
I have to upgrade one of my SDK while doing so after replacing SDK with new upgraded files it is working fine but when trying to push the same on remote that time I am facing the problem. In commit, it is taking only modified files only and some files are showing out of source control. Also, don't know what is the meaning of the (!) symbol. Can someone help with this? Please forgive me for bad English. Thanks in advance.
I'm new to Moodle 3.7!
I was trying to get it installed in the AMP stack that already comes with the Mac (except for the MySQL 8.0.12 which I installed separately). It all went okay so far, except for a few Issues I stumbled upon and got them fixed until I face this persistent "Error reading from database" error at the end of the installation process. If I'm not mistaken, I'm supposed to be greeted with my first admin screen to change my password and whatnot.
I've searched for an entire day so far only to find my efforts were in vain. I suspect it is some issue emerging from "dml_read_exception".
Thank you in advance for your anticipated support.
After hours of research and digging into the code, I realized that I had erased the default prefix for database set by moodle, "mdl_". Apparently, this is important.
I'm really not very well versed with databases so not very good at its terminologies.
It would be appreciative if anyone explains how it works and why it affected my installation process. Thank you.
I've seen variants of this question around, but I'm looking for a definitive answer if anyone has one...
We are running a Cloud SQL Postgres instance, and are stuck on restarting the DB after having an export crash out with an unspecified error.
For several hours now our DB has been out of action saying it's restarting.
The options to export, restart, all of that good stuff, are greyed out and unavailable.
There doesn't seem to be a way to force a restart either through the console, or via gcloud command.
Most of the replies I've seen to this question seem to end up with the poster being helped out by Google support. Don't get me wrong, I'd very much appreciate that, but I'd also like to know if there's a way of doing this myself?
Any help greatly appreciated.
Currently, the 'force restart' option is not available for 'PostgreSQL' instance.
There may be several reasons behind the 'stuck' stage of an SQL instance. Not every time, 'force restart' option wouldn't resolves the root/actual cause.
However, if you still think this option needs to be included in the 'PostgreSQL' instance, I strongly recommend opening a 'Feature Request' through the issue tracker. While opening the 'Feature Request', try to include a bit more details about your use case scenario(with or without an example) as well.
As the title says, the debug console in VS Code is double-spacing for me. I'm using the OSX edition. Seems to work fine for others from what I've seen. Have tried it with multiple programs and it always double spaces.
I can't seem to find any setting to change this behaviour. Anyone able to help?
Thanks.
JT
After searching and testing I came to github where I filed a bug for this. It seems that it was known already under a different issue ID already, see https://github.com/Microsoft/vscode/issues/17526 for details.