Set up the development environment on Windows

[AllanEngland]

Mick has been trying to get this project running in developer mode on Windows. He has the following versions installed;

Docker Desktop	4.28.0
JDK		17
Node.js		v20.11.1
Quarkus		3.8.2
Yarn		1.22.22

Launching Quarkus from the pst-gui directory (inside intellij) generates some errors. Two docker containers are running, pressing d brings up the gui dev-ui, and w successfully launches the Polaris 'click to login' screen on a browser. However, clicking this link throws an internal server error with 'OIDC Server is not available'.

[pahjbo]

there should be more than two docker containers running - is the key cloak one running?

[mwapst]

there were two, the keycloak one... quay.io/keycloak/keycloak:23.0.6, and a test-containers... testcontainers/ryuk:0.6.0

[mwapst]

And, I think I have tracked down the blockage, I thought it might be down to resource issues so I set the following (case-sensitive) Windows environment variables, after which I managed to get a Polaris login screen ok by typing 'w' in the intellij console...

QUARKUS.OIDC.DEVUI.WEB-CLIENT-TIMEOUT=10S
QUARKUS.TRANSACTION-MANAGER.ENABLE-RECOVERY=TRUE
QUARKUS.VAULT.READ-TIMEOUT=10S
QUARKUS_DEVSERVICES_TIMEOUT=2M

and of course this one for the present

JAVA_HOME=C:\Program Files\Java\jdk-17

[AllanEngland]

I'm curious as to why the timeouts need to be so long, but at least you've got it working. The next stage is to start up the API service at the same time, then you can log in and explore.

[mwapst]

If anyone has any ideas about the following I’d love to hear from them, particularly if there are any notes somewhere for setting up a dev environment, minimum hardware specs, environment variables, running orders etc..

On a Windows machine in two separate command line windows I ran gradlew quarkusDev from the pst-gui and pst-api-service folders in that order. This gave me two pairs of containers in Docker…
• one testcontainers/ryuk:0.6.0 for each
• one postgres:14 for pst-api-service
• one quay.io/keycloak/keycloak:23.0.6 for pst-gui

As far as I can tell pst-gui fires up ok and settles down to wait for input, but pst-api-service generates quite a large log, mainly db and sql warnings after which it too settles down and waits. I can share these logs with anyone who has the time.
Starting pst-api-service also causes an immediate message in pst-gui log
• Invalid realm configuration (ACR-LOA map)

Once everything had settled down I typed ‘w’ in the pst-gui command line window and that fired up the browser page to let me login to Polaris which was fine although it then generated lots of Invalid realm messages in the pst-gui log.
Having logged into Polaris I could see one proposal, Observing the stars, and opening each section of it I could see data, but when I clicked Create a new proposal, lots of Invalid realm messages appeared in the pst-gui log, and then when I clicked the Create button to save my new proposal an error appeared in the pst-api-service log
• 551 ERROR [ObjectResource] (executor-thread-3) org.hibernate.TransientPropertyValueException: Not-null property references a transient value - transient instance must be saved before current operation

What do you think?

[pahjbo]

The invalid realm messages are curious, but otherwise I think that you might have everything running given that you can log in - we are still very much in a development phase, so that there will be errors and non-functioning parts even on the HEAD of the master branch.

[mwapst]

I think many of the problems are down to underpowered hardware. Both my MacBook Air (Monterey) and my Windows 11 machine have only 8G of memory, though both have lots of free disk space. If I reboot and run up Docker straight away without doing anything else (particularly not starting IntelliJ) then I can get pst-gui running fine, though getting there does seem to be platform specific. On the Mac, from the project folder, typing quarkus dev works while ./gradlew quarkusDev definitely doesn't, but it's the other way round on Windows. Maybe that's another resource issue.