I have pgAdmin v4 installed, my default browser is Firefox, but I would like to open pgAdmin as a standalone app on Chrome. I fixed that problem following the procedure described in various Stackoverflow answers such as Launch pgAdmin 4 as a standalone app using chrome browser commands and pgAdmin 4 v3.1 How can I use another browser? (Win 7), i.e. configuring the "Browser command" option of pgAdmin to use Chrome.
That worked till sometime ago, but with the latest versions (at least 4.24 an 4.25) there is a problem: when I launch pgAdmin it still opens the default browser and not Chrome, as I configured. However, if I right click on the icon of the system tray and select "New pgAdmin 4 window..." it correctly opens Chrome.
I thought it was just me, but I found that there is at least another user with the same problem.
As pointed out by a developer of EnterpriseDB (the company behind pgAdmin) in this answer, that is a bug in the QT library that happens on Windows platform; it has already been reported and developers are working on that.
Related
I am trying to find away to analyze the memory consumption in a NodeJS application. I am trying to use Chrome dev-tool on top of node inspector. It's quite basic to start and I am listening on default 9229 port as suggested here.
After connecting to the port from chrome, I can see the consoles and files under Node but I am unable to run memory snapshots. It's just disabled.
Opened the inspect screen and clicked on the inspect.
Then I see these options completely disabled.
On hover of record button, I see a message "Another profiler is already active" which I don't have a clue to.
What could be the underlying issue here?
System specifications
Chrome - 83.0.4103.97
OS - Windows 10
Node - 8.9.4
Any help is appreciated!
Finally after trying out different versions, new Microsoft edge, I found out that it's an issue with version incompatibility.
I tried with Node 9.11.1 and it didn't work.
But at end switched to 12.16.1 and it works there. For now I assume chrome/chromium dev-tools supports higher versions of NodeJS.
I also found that the platform needs to be the same.
That is to say, if you run nodejs on Linux, you also need to run Chrome on Linux.
I'm new to PostgreSQL, just installed it along with pgAdmin4. After installation when I clicked on the pgAdmin4 it start in the browser of IE. But I want that in my chrome browser so I searched for it. Most of the people have mentioned or shared a picture of pgAdmin 4 configuration like this.
They mentioned it like right click the icon in the Windows System Tray and select Configure but the pgAdmin is not showing in the system tray of window 8.1. Or may be I'm misunderstanding about the system tray. Because in windows 8.1 pgAdmin 4 directly opens in browser.
The browser issues is fixed by change by default browser to chrome but I'm still unable to find this configuration setting. Can anyone help me to understand or get this screen?
pgAdmin 4 is a web server, so when you click pgAdmin 4 on the start menu, it starts the web server in the background, then opens a browser to connect to it.
The web server running in the background should have added a small icon to the system tray in the lower right corner.
On my Window 7 it looks like this:
I have developed a chrome extension that i have tested successfully in two different computers (Linux and Windows systems) with Chrome version 76.0. The first line of this extension is a console.log("test") which is obviously showing in the developer console every time i start chrome. The problem I face now is that when testing the extension in a MAC computer (which should not make a difference?) with Chrome 76.0, it is installed successfully but it never starts. Not a single log is shown (yes, i checked that logs are being shown) and it is not working at all. No error are shown in the console and no errors in the extension settings tab. I have no idea what is going on here.
Finally, I was able to make the Cypress release edX fullstack run in Windows7 Professional. (It works even in Windows7 Professional!; I was told that it must be in Windows7 Enterprise or Windows8)
It is running fine in IE and Firefox and displays the login page or "Welcome to Open edX! with http://preview.localhost as intended. However, the chrome browser displays "ERR_CONNECTION_REFUSED" error message.
I would really appreciate if anyone can guide me to debug this problem.
Blessings,
(a debtor)<><
Chrome has a (sort-of) built-in dns prefecth this (is supposed to) allow to improve page load performance.
To workaround this, you can force the IP in the name bar and your page will display.
Follow-up: can it be disabled ?
There was a time it could but the chrome team made a change early this year (https://chromium.googlesource.com/chromium/src/+/eabf1f5baba38d46921acd6edda594f942f7d6a1) so the option is no more available under chrome://flags/ (was called "Built-in Asynchronous DNS") If you still have a version before January 2015, you might still see this option and can disable it.
In the announcement, it is said it can still be called from command line so running with option --disable-async-dns
I have Chrome for Mac on my mini-mac running OS 1 10.6.8 and starting to learn how to write Chrome extensions.
Followed the sample tutorial for the browser-action pop-up.
Does NOT pop-up on my mini-mac, but the same code works just fine on my Macbook Pro running OS X 10.9.2
The only obvious difference is that my mini-mac cannot be upgraded to Mavericks, etc. nor to Java 7.x, however, there are other published extensions that I am able to load that work just fine on both Macs and both OS X.
I have not found any answers surfing -- any help is appreciated.
Chrome extensions do not depend on OS X Mavericks, and they do not require Java 7, and as you have mentioned, others are working well on your Mac Mini. (They run on my Mac Mini too.)
You can check to see if you have developer mode enabled by going to chrome://extensions and making sure the "Developer Mode" checkbox near the top of the page is enabled.
Another potential problem is if you are running a very old version of chrome, say older than about 6 months.
See if other tutorial apps work. It might be good to start with this one:
https://developer.chrome.com/apps/first_app