During the last weeks, I was working on various issues and problems related to SW development.
I found that quite often problem analysis was mostly chasing issues just on the surface
but not really attacking the deeper reasons of the problem and follow the consequences.
It's like the doc that stops your leg bleeding but doesn't see that it is broken.

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.

I run most of my reviews using Docker Desktop on Windows 10.
According to the recommendations, I clean up docker and downloaded repositories after tests:
Repos are simple but Docker is somewhat resistant to release the consumed disk space.

If one of your packages on OEX receives a review you don't get notified by OEX only on YOUR package.
​​​So @Evgeny Shvarov suggested publishing my monthly summary of reviews here in DC.
It reflects my experience with the status I found at the time of my review.

For several weeks I'm creating reviews on OEX.
So I'd like to explain to you the criteria that I apply to find my ratings.
Of course, each reviewer is an independent person and has his own criteria and his own opinion.
And that's good and important! As Winston Churchill once said:

"If 2 people always have the same opinion, then 1 of them is superfluous"

Some changes in IRIS configuration require a restart of IRIS.
This is no big issue as long as I have access to the server command line with sufficient privileges.

In a container, this is not always given.
Stopping IRIS from the terminal/session prompt is no problem.
But the restart after is.

Note1: container start-stop is no option as it might be removed by option --rm in docker run
Note2: the target is linux (manly in docker). Windows is excluded

GitHub

I'm almost running out of disk space so I want to move 1 DB to a different hard drive.
It's a rather simple but lengthy action during a shutdown of IRIS.
But is this somehow possible under runtime in a stand-alone installation?
I'm looking for kind of a "local drive failover"

note: Mirror or Shadow is not an option.

install and usage

Packed Pretty.xml installs routine ZPretty in any namespace.
calling $$Do^ZPretty(input,[filler],[newline]) returns a wrapped JSON string.
filler is the optional string for the indent, default = " "
newline is optional, default = $C(13,10)
input accepts: JSON_String, JSON_Stream, %DynamicAbstractObject

Environment:

• Windows 10
• Docker Desktop version v20.10.5