Bug configuring Cloud SQL instance? Error encountered while trying tutorial - google-cloud-sql

I'm following the tutorial at https://cloud.google.com/nodejs/getting-started/using-cloud-sql and hit an issue with the section "Configure the new Cloud SQL instance".
Basically, I can't click "Save" successfully when entering the "0.0.0.0/0" network configuration. Chrome's Javascript Console shows an error "Custom HTML/JavaScript blocked. See go/13687728."
What's going on?
I tried continuing with the tutorial but hit an issue at the "npm run-script init-cloudsql" step.
Thanks for the help / fix!

I found a work around that might get you moving:
Click Add Item, Enter details, then click Save. Do not add another until the done message appears.

Related

pgAdmin 4 v3.0 and v3.1 doesn't load (crashes) on Windows 10

I tried to google issue, but I couldn't really find any help or solution that would work. It is trying to load - loading box appear, but app doesn't appear after that.
There is no log in "%APPDATA%\pgAdmin\pgadmin4.log" file or any error. There is no process after it crashes. Version v2 works properly.
I'll provide any info, you need. I am kinda out of ideas how to log / fix this.
Have you tried running it as Administrator?
If not I would suggest try it once, I don't know the exact reason but sometimes it fails to load on Windows.
I faced the same issue, Here are the steps I followed,
1) Right click on pgAdmin4 icon
2) Select 'Run as administrator' option
3) Click Yes on confirmation dialog and check if pgAdmin4 starts properly.
If the above steps do not solve your problem then try reaching the developers via the mailing list.
https://www.pgadmin.org/support/list/

VSCODE - Marketplace returned 'ECONNREFUSED'. Please check the 'http.proxy' setting

I am new to Visual Studio. I just installed Visual Studio Code (VSCODE). First time, I opened it and trying to install the extension for powershell. But, when I go to the Extensions tab, it gave an error that the proxy settings were not configured.
The pop up gave an option to 'Open User Settings' and it opened an editor.
As per my understanding, I wrote the following two lines in the User Settings file.
Our internal proxy server requires user authentication. How and where will I put the user credentials. I think, I am getting the error because I have not specified the user details.
Found out how.
The proxy details should be given in the following format. I was using the wrong format earlier.
My settings file looked something similar to below.
// Place your settings in this file to overwrite the default settings
{
"http.proxy": "http://user#domain.local:Password456#10.201.10.200:8080",
"http.proxyStrictSSL": false
}
The domain user name was domain\user, and it was provided in the user FQDN format
Password456 is the login password for the user
10.201.10.200:8080 is the proxy server
Hope this would help someone at some point of time.
I solved this problem like #Tom Jacob Chirayil, but I had to do a little extra. Here are the steps I followed:
Find your proxy server first by going to http://wpad/wpad.dat. My company's configuration had a bunch of proxy servers, and the one that I used was at the very bottom, in this format:
return "PROXY subdomain.company.com:port";
Then click on the Open User Settings button, and add the following line to the settings.json file to the right, within the braces:
"http.proxy": "http://subdomain.company.com:port"
NB: I had to add http:// to the front of the proxy address that I pulled from wpad.dat.
Then save settings.json, restart VS Code. (IDK for sure if you have to restart VS Code or not.)
Just to add a point, it seems that the new release (1.5.1) came with this issue. People on Mac, Linux or Windows suffering with "econnrefused" error in VSCode.
The new version (1.5.2) will have a fix for this, until then, we can use the nightly version.
Source: https://github.com/Microsoft/vscode/issues/11774

Mule ESB, Launching project encountered an issue after the project was renamed

I have a flow running within a project named 'dm' that was created by someone else.
This flow works well.
I Right click and hit "Copy", and then I hit "Paste", and chose the project name 'dm_1'. All looks well
So I try to run the new project, I right click on the flow and hit "Run As - Mule Application"
Immediately I get the following error:
Launching dm_1 has encountered a problem.
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft or post a message in the MuleSoft Community Forums (http:/forum.mulesoft.org) with a detailed description of how you encountered the problem
DETAILS:
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft Support or post a message on the MuleSoft community forums (http://forum.mulesoft.org) with a detailed description of how you encountered the problem.
Project referenced by launch does not exist.
So how do I fix this problem.
I do not see anything within the xml that would suggest there is a project name that needs to be changed as well, with the possible exception of the following line:
<mulexml:schema-validation-filter schemaLocations="C:\Users\xxx\AnypointStudio\workspace\dm\src\main\resources\p.xsd" returnResult="false" doc:name="Schema Validation"/>
Where do I look to change the project name
try adding a new flow to the same project. Then right click on the new flow and run it. This will cause the entire project to run.

Google Chrome developer tools disabled

My Google Chrome developer tools are disabled. I'm not sure how it happened. I was using them in the morning then went to use them in the afternoon and the F12 button wouldn't do anything. Same with ctrl+shift+i.
If I navigate the 'Tools' menu, I can see the 'developer tools' link, but it is grayed out and disabled. Does anyone have any idea how to re-enable them? I uninstalled/re-installed chrome twice but no help.
Delete the DeveloperToolsDisabled registry key in Software\Policies\Chromium\DeveloperToolsDisabled
https://chromeenterprise.google/policies/#DeveloperToolsAvailability
I found it named slightly differently (Win7):
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\DeveloperToolsDisabled
I set it to zero and restarted Chrome --> all is well. No idea how it got set.
Update 5/30/2014: This value was set again, there must be some security policy against this flag where I work. I deleted the key completely and will report back if it appears again.
Update 6/13/2014: Definitely we've got a security policy that is setting this key daily. As a workaround I've created a file, "fix_developer_options.reg" with the following contents and put it on my Desktop:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"DeveloperToolsDisabled"=dword:00000000
This file, when double-clicked, will automatically make this setting in the registry. After that, you need to restart Chrome to get the change. (One step better would be to have this executed when you log in.)
Update 3/4/2018:
In Windows 10 this setting has moved under HKEY_CURRENT_USER as #DGinzberg mentions below in the comments. I found it here on a new computer:
[HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome]
check policies - type chrome://policy/ in url bar. if DeveloperToolsDisabled is set to true, update the registry entry
I just came across a similar issue on my university's website where I could not open the dev tools. Dev tools were opening on other websites in adjacent tabs but not on this site.
Solution:
What worked for me was that I clicked on the address bar of the browser and pressed F12. And it worked. It did not work afterward when I un-selected the address bar and tried again. But worked again when I did it by selecting the address bar.
Hope it would help someone.
Found another issue with the Dev Tools not opening/ working
If the Block access to a list of URLs Enabled
and "file", "" is in it
or
file:// is not in the whitlist of url, the DEV Tools wont open either :)
Maybe that helps someone
Open regedit (Registry Editor) and find the DeveloperToolsAvailability key by first going to this path:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\
... then click Chrome and select DeveloperToolsAvailability from the list on the right. Double click it and change it from 2 to either 1 or 0. Click OK and close regedit, then close Chrome and re-open it. Chrome dev tools should now be enabled.
However, depending on your system, you may instead have the DeveloperToolsDisabled key in that same path. If so, delete that.
If you are using a Google Workspace account and have Google Admin Console permissions, you can follow the below steps to enable the Developer mode of Chrome browser for the entire organization or just an OU.
Log into the Google Admin console (admin.google.com).
Navigate to Device>Chrome>Settings (https://admin.google.com/ac/chrome/settings/user).
On the left, select the proper organization unit which contains the user/s you want to change the configuration for.
Update the "Developer Tool" settings with “Always allow use of built-in developer tools”.
SAVE changes.

how to fix source not found message for coldfusion eclipse remote debugging?

I have eclipse with coldfusion builder installed, and I set up the various screens - RDS and coldfusion debug settings in preferences, project properties and set the server up there.
It seems like it is almost working, the RDS screens work, and I can start debugging, but when it hits my breakpoint I get a blank source page that says 'Source not found.' with a button for 'Edit source lookup path'.
If I click the button, it shows my workspace tree, not much I can do with that, but I can add a path so I tried adding a path to the root of my project on the web server. When I ok that, for an instant I see some code appear in the source viewer, then it disappears and I have the source not found message again. If I click edit, my path is not there... ??
I am not sure what fixed it exactly, but I just went through all the different settings screens and re-defined all the debugging paths, etc. and it finally started working.