autoinstall | Continuously go-installs all packages in GOPATH

In your build.js file replace the target option with web instead of electron.

UPDATE: I actually found a better solution to your problem as you may need to use the right target at some time in your application. See below:

The issue is that nodeIntegration isn't enabled on your BrowserWindow although you specified it in the options. This is because contextIsolation is on by default and those two options cannot work together. Adding contextIsolation: false inside webPreferences when building your window should also fix your issue while keeping the parcel target to electron.

This error message...

From the "Creating an installation response/answer file" section on this page: https://www.codemadness.org/openbsd-autoinstall.html:

The installer supports loading responses to the installation/upgrade questions from a simple text file. We can do a regular installation and copy the answers from the saved file to make an automated version of it.

Do a test installation, at the end of the installation or upgrade when asked the question:

Enable the restricted repository and the security updates:

Not sure if your core logic really represents 'application' data, or product data, but I'll keep the proc name as 'getProductData'. Here's what it does:

• First, in the 'monthYears' CTE, I get the product-add-date for the application and create month and year bins that spread from the add date to the present date. This is the only 'looping' I do. Otherwise, the healthier approach is to use set-theoretical operations available in SQL Server, which are much more efficient.
• Then, in the 'productInstalls' CTE, I take your logic, omit the month and year filters, and instead group by month and year to get them all at once.
• I do the same for your application installs logic in the 'applicationInstalls' CTE.
• Finally, I join it all together by year and month in the core query.

Here's the code:

Your driver installation is fine, but your GPU is 11 years old and does not support some of the more recent features of the OpenCL standard. The geekbench error message -40 means that the image size geekbench uses for one of its benchmarks is not supported by your GPU. This causes the benchmark to crash. Maybe an older version of geekbench still works.

A common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux. While it is possible to work around this issue by passing --no-sandbox flag when creating your WebDriver session, such a configuration is unsupported and highly discouraged. You need to configure your environment to run Chrome as a regular user instead.

This error message...

After long research I figured it out myself. Posting my solution in case anyone is dealing with the same problem.

1. Setting the passenger log level. You can put passenger_log_level 7 in your nginx configuration /etc/nginx/conf.d/phusion-passenger.conf (for Plesk)
   
   

2. I started the app as a standalone passenger server and got the actual application stdout output. Example: cd in your node app root-folder and run passenger start --startup-file lib/startup.js --nodejs /opt/plesk/node/12/bin/node --log-level 3 --app-type node.

At this point I saw the module Probot couldn't be found in my above mentioned startup script. So I dug a little deeper how a probot app is actually started and stumbled upon the probot run command. By default a probot app isn't run with node ./lib/index.js but probot run ./lib/index.js.

1. Using a custom passenger app start command. I added the nginx option passenger_app_start_command "/opt/plesk/node/12/bin/npm start"; to set the custom start command to use the probot run command defined in the package.json start script instead of the default node ./lib/startup.js from passenger

I learned a lot about these tools and hope this will save someones weekend :D

I'm facing the very same issue. By using the shell during the installation process, I see that no users are created, hence we cannot log in after the reboot. I don't know why, either a bug in subiquity or a lack of documentation about how to use it properly. Neverteless, I was able to create an user using this trick in my autoinstall file: