Andrew Cooks

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/62653554-show-response-times-in-top-talk-talkers-view?utm_campaign=plugin&utm_content=tracker%2F10143345&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F10143345&utm_medium=issues&utm_source=github).

This is the current set of capabilities to get things working: `sudo setcap "cap_sys_admin,cap_sys_resource,cap_syslog,cap_sys_nice,cap_block_suspend,cap_net_bind_service,cap_net_raw,cap_net_admin+eip" server/jt-server` This is quite a lot! Plan: 1. This might be more than the minimum caps...

To comply with [Fedora packaging guidelines](https://fedoraproject.org/wiki/Packaging:JavaScript), dependencies like `d3.js` need to be installed system-wide, away from the rest of the web assets. However, some use cases require the js dependencies...

**Background** Most people think of throughput as the defining characteristic of any network transport, rather than delay and delay variation. JitterTrap currently lacks the ability to specify the maximum throughput....

**Background** The current Impairments, Measurements and Traps modules lack a mechanism to do repeatable test scenarios. A Test module is needed! **Task** Tests specify: - a tuple of impairment parameters...

**Background** Currently the Traps module does little more than change the colour of a virtual LED, but it could do so much more! The next, simple action to implement is...

JitterTrap is desperately lacking some tests. --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/18119156-lacks-tests?utm_campaign=plugin&utm_content=tracker%2F10143345&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F10143345&utm_medium=issues&utm_source=github).