I am trying to set up the Divio app on Win10 Pro.
I can launch the application, log in, select the workspace folder for my project, so the required dependencies should be fine.
However when I click on "Set up my project", then a new window is opened with a text "Preparing logs...", and an animated "hour-glass" appears next to the "Open Shell" button in the lower-left corner, but that's it. Everything hangs up at this point, and I can't figure out what's wrong. Restarted the computer and the app several times, but with same results.
Any ideas how to work out what is going wrong?
The Divio app is an Electron application, and uses Chromium for the interface.
You can invoke its Inspector as you would in Chrome itself, using command-option-i on Macintosh and control-shift-i on Linux and Windows.
The Inspector's Console tab will show any errors, and this will help understand what is happening internally. Typically, they will be errors related to the operating system in some way.
Related
I mainly run Cypress and Chrome through WSL2, whenever I try and make any of the windows that open full screen a part of them always displays on my second monitor.
Is there anything I can change in a config file or something to fix it?
I don't know if it's related but the cursor on the WSL2 GUI programs is huge. Is this something that can be fixed too?
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 built a simple app using electron, electron-forge, and Vue.
When I run my app via "electron-forge start" it works great.
When i try and compile my app with "electron-forge make" it compiles, but the app itself does not complete the back end scripts, some promise or return is not resolving.
I've determined the problem is not on the front end (vue) but something going on with node.
I've been able to get SOME debugging by setting up manual break points in the code and sending it to "mainWindow.webContents.send" and leaving the dev console on in chromium.
However, this is really taking shots in the dark. Is there any way to display the node console from a compiled electron app? this would make debugging 1000 times easier, but I can't seem to find a solution, all references are about the chromium debug console, which is not useful here.
If you are using windows machine select the "exe" file and drag it to command prompt, then press enter.
If you are using MAC machine right click ".app" file select "Show Package Contents". Open MacOs folder inside the Contents folder, then drag the executable file and put it on terminal.
Basically put the executable on terminal and run the application you can see nodeJs console messages in it.
When apps crash, Windows used to popup a dialog box saying {Program} has stopped working with a Close button. I no longer see this dialog box on Windows 10. How do I get it back?
I thought perhaps I messed up some registry setting, so I downloaded a Windows 10 VM from Microsoft, crashed a program in the VM and I still didn't get a dialog box. So there must have been some change to Windows.
I tried tweaking the AeDebug registry key, but still couldn't get the dialog box back.
The reason I like the dialog box is because it tells me right away that some program has a problem that I can investigate further.
As described here, you need to set the Windows Error Reporting setting DontShowUI=0 with the Registry Editor or Group Policy Editor.
sounds a little dumb when i tell that but, when app stops working for me i usually press the left mouse button a lot in the windows (of the app) until it will display the message to end the process
I wanted to develop my own watchface for my Gear S2. I found some good documentation on downloading and using the Tizen IDE. All is well, but I'm finding the tweak css/html5-run/upload-switch faces-view-wash-rinse-repeat to be very tedious and time-consuming.
I know I can point my browser (Chrome) to my development workspace and load the index.html up and I surmise that I could tweak what I have, which came from the template to work in the browser if I made the sizes in the css static vs dynamic (absolute vs percentages). But is there a better way? Scouring the Internets Googles have yielded nothing too helpful yet.
moderators: this might be OT for this particular SO. If that's the case, I apologize. A nudge in the right direction would be greatly appreciated, if so.
So, I was able to make a little progress on this myself. I am using Chrome in developer mode, which almost works perfectly when using the developer device emulator. To toggle the device emulator, open developer mode (windows: ctrl+shift+I, OS X: cmd+option+i) and when the tool window opens up, look for the little device button next to the element button in the upper left corner of the developer tools window. When the device emulator open, switch the resolution to 320x320 (top of the window next to "screen").
Now, open your index.html file for your project in Chrome, and you can at least muck around with your css styling.
Now to get around the whole issue of reloading your clock with the default clock in the Java emulator for Tizen, I was able to get my changes to automatically assert when running the new code. The way I did it, though I'm not sure if all of these steps were necessary was:
In the emulated watch:
1. set the screen timeout to 15 mins.
2. set the watch face to your development watch face
In the IDE:
1. when ready, use the button for smart launch (it's the blue button just to the left of the bug button in the tizen web IDE). This is in the Tizen SDK version 2.3.1 build 20150721-1440.
At the time of running your code -- making sure both your emulated watch is running too:
1. In the IDE, click the smart launch button
2. Click over to your emulated watch and make sure it's in focus.
It should update the watch face with your latest changes in realtime. This worked for me, so YMMV, but at least I didn't have to reload the watch face after asserting the latest version.