--server-profiling-path does nothing

[JaroslavTulach]

I'd like to profile/log what is happening during startup. Running:

enso$ ./built-distribution/enso-engine-0.0.0-*/enso-0.0.0-dev/bin/enso \
  --run ~/enso/projects/Empty/ \
  --server-profiling-path start.npss \ 
  --server-profiling-events-log-path start.log \
  --server-profiling-time 10

however doesn't generate start.npss neither start.log files. What's wrong? Answer: the profiling options only work with --server argument! Why? They are helpful for understanding what's happening during startup in general. They would work with --run as well as --repl!

[enso-bot]

Dmitry Bushev reports a new STANDUP for yesterday (2023-11-07):

Progress: Started working on the task. Implemented the profiling logic in the runner. Removed profiling from the language server startup logic. Started testing It should be finished by 2023-11-08.

Next Day: Next day I will be working on the #8156 task. Continue working on the task

[enso-bot]

Dmitry Bushev reports a new STANDUP for today (2023-11-08):

Progress: Continue working on the task. Had to recover the language server profiling logic as the collection of profiling events was not working if started in the runner. Updated the runner logic. Tested manually. Created the PR It should be finished by 2023-11-08.

Next Day: Next day I will be working on the #8156 task. Continue working on the task

[JaroslavTulach]

There still seems to be:

    --server-profiling-events-log-path <file>   The path to the runtime
                                                events log file.

I also tried:

./built-distribution/enso-engine-0.0.0-dev-linux-amd64/enso-0.0.0-dev/bin/enso --profiling-path x.npss --run ~/hi.enso

and no x.npss file was created. Reopening - I'd say that --profiling-path parameter still does nothing. Tested on 6be94a8

What can be done? Either using --profiling-path without --profiling-time shall be forbidden or there should be a shutdown code that makes sure the dump is saved when the JVM exists.