benchmarkstt icon indicating copy to clipboard operation
benchmarkstt copied to clipboard

Open Source AI Benchmarking toolkit for benchmarking speech to text services

Results 15 benchmarkstt issues
Sort by recently updated
recently updated
newest added

Currently the HTML produced uses spans with classes for "insert" etc. but no CSS to actually style the spans and also no HTML to format the heading vs compared text....

enhancement

Are we going to re-add badges or other indicators for code coverage and test success as separate from build success in the future? E.g. coveralls would be nice for code...

enhancement

Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.11.5 to 7.23.2. Release notes Sourced from @​babel/traverse's releases. v7.23.2 (2023-10-11) NOTE: This release also re-publishes @babel/core, even if it does not appear in the linked release...

dependencies

Bumps [debug](https://github.com/debug-js/debug) from 4.1.1 to 4.3.4. Release notes Sourced from debug's releases. 4.3.4 What's Changed Add section about configuring JS console to show debug messages by @​gitname in debug-js/debug#866 Replace...

dependencies

With longer documents the diff output can become very long. Could this get split up into several lines? For example when I produced output in RST dialect and then tried...

A lot of details are not in the main documentation (e.g. the "dialect" for showing the worddiffs) but could be determined from PythonDoc. Also, PythonDoc would make it much easier...

Levenshtein should be a proper Differ class, not hacked into metrics. This PR does the necessary changes to achieve that. - [x] extend Dfifer interface to support `get_opcode_counts` and `get_error_rate`...

(related to #14 and #21 ) It seems like it would be a good idea, but needs some enthusiasm from all parties involved, developers and analysts/stakeholders. If developers are willing...

workflow

(related to #14 ) What reporting strategy do we want to use for this, looking for more input and volunteers to take this on. - What percentage of code coverage...

workflow

For now Python3 PEP8 will be followed, no decision has been made yet to enforce this (we should imho), dissent can be expressed here. (issue part of #14)