<commit_before>
How do you add a new output-parse function when installing a new language+test_framework?
Adding it to the to the web server source and then rebuild the web server is not
going to work for the new start-points architecture...
Obvious options are
1) inside the manifest.json file (requires eval)
2) inside the image itself! - a plain .rb file in a known location
3) inside the start-point volume in colour_of.rb file next to manifest.json
   (means I would not need the unit_test_framework inside manifest.json)
I think 3 is the best option.
Eg contents of colour_of.rb
def colour_of(output)
    return :amber if /PHP Parse error:/.match(output)
    return :red   if /FAILURES!/.match(output)
    return :green if /OK \(/.match(output)
    return :amber
end
#-----
eval(IO.read('colour_of.rb'))
colour_of('FAILURES!')
....Or contents of colour_of.rb
lambda { |output|
    return :amber if /PHP Parse error:/.match(output)
    return :red   if /FAILURES!/.match(output)
    return :green if /OK \(/.match(output)
    return :amber
}
#-----
colour_of = eval(IO.read('colour_of.rb'))
colour_of.call('FAILURES!')

- - - - - - - - - - - - - - - - - - - - -

diff-dialog from test page should have fork button.

- - - - - - - - - - - - - - - - - - - - -

Need to add a cpu limit to running docker containers.
This will stop 100% rogue cpu process.

- - - - - - - - - - - - - - - - - - - - -

Add C# XUnit test framework.
http://xunit.github.io/

- - - - - - - - - - - - - - - - - - - - -

In cli, change terminology from volume to start-point ?<commit_msg>[ci skip] notes update<commit_after>
In the new start-points architecture how do you add a new
output-parse function when installing a new language+test_framework?
Inside the start-point volume add colour_of.rb file next to manifest.json
   (means I would not need the unit_test_framework inside manifest.json)
contents of colour_of.rb
#-----
lambda { |output|
    return :amber if /PHP Parse error:/.match(output)
    return :red   if /FAILURES!/.match(output)
    return :green if /OK \(/.match(output)
    return :amber
}
#-----
Then copy the output_of.rb file into the kata's folder (next to
the kata's manifest.json) when the kata is created
(to avoid dependency on navigating from kata back to language/start-point)
#-----
colour_of = eval(IO.read('colour_of.rb'))
colour_of.call('FAILURES!')

- - - - - - - - - - - - - - - - - - - - -

diff-dialog from test page should have fork button.

- - - - - - - - - - - - - - - - - - - - -

Need to add a cpu limit to running docker containers.
This will stop 100% rogue cpu process.

- - - - - - - - - - - - - - - - - - - - -

Add C# XUnit test framework.
http://xunit.github.io/

- - - - - - - - - - - - - - - - - - - - -

In cli, change terminology from volume to start-point ?
{'fraction_non_alphanumeric': 0.14679556032939492, 'fraction_numerical': 0.0035803795202291443, 'mean_word_length': 2.271662763466042, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 24, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2301114', 'n_tokens_mistral': 935, 'n_tokens_neox': 901, 'n_words': 314}