Thomas Rückstieß

Proposal for new schema schema: ``` js { $count: 100, field: { $count: 50, $prob: 0.5, $type: 'number', $array: true, $category: true, $hist: [ {v: 1, c: 34}, {v: 2,...

Hi @Mogztter I don't think we need a mongo shell plugin for this library anymore now that the new mongo shell (mongosh) can import npm modules natively. I just tested...

Looks like a problem with the `progress` module (that renders the progress bar) on Windows. Other projects had similar issues with the same error message. This one seems to indicate...

I'm having the same issue, too. I've got around this like so: ``` js var d3 = window.d3 = require('d3'); require('d3-flextree'); ``` Perhaps you could make the module a function...

there could be a "diverged" stop criterion as well. the problem would then be a special case of the whole stopping mechanism and shouldn't be handled by the minimizer explicitly....

Thanks, I like the linecache idea, that sounds like the way to go.

Some notes: use [namedtuples](https://docs.python.org/2/library/collections.html#collections.namedtuple) to only store the fields needed, which are: - `line_no` (use linecache to get back line for click event) - `datetime` (x-axis value) - `duration` (possibly,...

Depends on new mloginfo sub-commands interface in #224.

Pushed mloginfo command structure to 1.2, because the interface is changing too much and breaking existing scripts. As that's a dependency, it has to be moved to 1.2 as well.

Yes, we should follow the same pattern as the index filters, that distinguish a query by: - namespace - query shape - sort shape - projection It's very easy to...