Telemetry batching and throttling (#412)

* Refactored for new batched worker provider

* Skipp callbacks with no telemetry

* Process messages for that remote-clock before any others to avoid race conditions

* Fixing bugs

* Added explanatory comments. Make max batch size and throttle rate configuration

* Removed TODO comment in lieu of a followup ticket

* Make batch configuration explicit in the example

* Tell Istanbul to ignore serialized functions

* Fixing linting errors

example/index.js

@@ -8,7 +8,9 @@ const config = {
     "yamcsUserEndpoint": "http://localhost:9000/yamcs-proxy/api/user/",
     "yamcsInstance": "myproject",
     "yamcsProcessor": "realtime",
-    "yamcsFolder": "myproject"
+    "yamcsFolder": "myproject",
+    "throttleRate": 1000,
+    "maxBatchSize": 15
 };
 const STATUS_STYLES = {
     "NO_STATUS": {

src/openmct-yamcs.js

@@ -57,9 +57,12 @@ export default function install(configuration) {
         openmct.telemetry.addProvider(historicalTelemetryProvider);
 
         const realtimeTelemetryProvider = new RealtimeProvider(
+            openmct,
             configuration.yamcsWebsocketEndpoint,
             configuration.yamcsInstance,
-            configuration.yamcsProcessor
+            configuration.yamcsProcessor,
+            configuration.throttleRate,
+            configuration.maxBatchSize
         );
         openmct.telemetry.addProvider(realtimeTelemetryProvider);
         realtimeTelemetryProvider.connect();

src/providers/limit-provider.js

@@ -100,7 +100,7 @@ export default class LimitProvider {
         const limits = domainObject.configuration.limits;
 
         return {
-            limits: async () => limits
+            limits: () => Promise.resolve(limits)
         };
     }