Would be nice to have the support corner again to talk with the WRC folks. 

Benefits? Healthcare? comp band? remote possible? 

while you can (clumsily) script terminal sessions, it might be easier to connect to your db via odbc and use isql, or maybe even use the newer python capabilities to get your data out via a python script

a really good analysis is also to look at the split times of everybody (=how long between submitting part 1 and part 2).  the api gives us the data. 

Please note that 12 characters is very much not a secure password, regardless of the characterset. https://www.explainxkcd.com/wiki/index.php/936:_Password_Strength

any other restrictions on the code we should be aware of?

How are you protected in this setup against two instances coming up and writing into the same db? I.e. due to flaky network?

For next time, this might be helpfull: 

https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic…

In windows it just triggers the service restart (which you can also do from the service.msc terminal), in linux it restarts the daemon. 

Neither of which will be helpful if apache is properly frozen, in that case you'll have to kill it manually first.

I think this " OAuth authorization is much more robust and recommended for production use." should be emphasized a bit more :) This might lead to people getting the idea that rolling their own encryption related code is an acceptable idea :/

typo: zuauthenticat -> zauthenticate

It's a proprietary compiler compiling into a proprietary bytecode. So no llvm support, and certainly no in depth documentation of it ;)

Even just doing a read access is significantly slower with the %DynamicArray types. I ran into that during the Advent of Code puzzles and had to fall back to $LB lists and arrays. consider a simple loop to go through 100k items:

Class fkh2019.Bench Extends %RegisteredObject
{

ClassMethod listtest()
{
    
    #; let's build a long list
    s mylist=""
    for i=1:1:100000{
        s mylist=mylist_$LB(i)
    }
    s start=$P($ZTS,",",2)
    Set P=0
    While $LISTNEXT(mylist,P,value) {
        s disgard=value
    }
    s end=$P($ZTS,",",2)
    return end-start
}

ClassMethod dyntest()
{
    #; let's build a long list
    s mylist=[]
    for i=1:1:100000{
        d mylist.%Push(i)
        
    }

    s start=$P($ZTS,",",2)
    Set it=mylist.%GetIterator()
    While it.%GetNext(.key,.value) {
        s disgard=value
    }
    s end=$P($ZTS,",",2)
    return end-start
}

ClassMethod runtests()
{
    s t1=..listtest()
    s t2=..dyntest()
    w "list access took ",t1, " seconds",!
    w "dyn array access took ",t2, " seconds",!
}

}

The %DynamicArray takes about 15x longer:

IRISAPP>d ##class(fkh2019.Bench).runtests()
list access took .005273 seconds
dyn array access took .082946 seconds

Thanks, it was a lot of fun! Good coding everybody and a happy new year to you all!

Anything using process memory usually falls over really quick as soon as you try and start using it for real use cases. Even increasing bbsiz is only a temporary band-aid in most cases.

keep in mind, pruning the images doesn't actually make the docker image (Docker.raw) shrink again. To achieve that you'll have to 'reset docker' (which will recreate that image) 

Looks like a nice wrapper around https://irisdocs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCM_healthmon ?

I would suggest it makes much more sense to do logging to globals that are mapped into a DB that isn't being journaled in the first place. That way you don't have to add additional complexity of suspending a transaction (which is a great source for bugs...) Thanks, Fab