hublot issueshttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues2017-11-17T14:45:37Zhttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/71CI: change image used2017-11-17T14:45:37ZTom JORQUERACI: change image used`.gitlab-ci.yaml` still uses a custom node+chromium image. This should be unnecessary with the switch to puppeteer.
Switch to a more standard node image`.gitlab-ci.yaml` still uses a custom node+chromium image. This should be unnecessary with the switch to puppeteer.
Switch to a more standard node imagehttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/70Remove proxy2017-11-14T16:00:55ZTom JORQUERARemove proxyDue to #67 we introduced a proxy in 0ce9822 (tagged with `proxy`).
This is an ugly workaround, and should be removed when #67 is fixed.
To test that everything work without proxy, do the following in `config.json`:
- set `client.proxified` to `false`
- set `client.gstreamerURL` to `wss://:hublot_kaldi-gstreamer_1:80/client/ws/speech?content-type=audio/x-matroska,+rate=(int)48000,+channels=(int)` (or whatever is the correct SSL ws URL)
- set `client.reco.host` to `hublot_recommender_1`
- set `client.reco.port` to `8080`
Everything should work as before, assuming SSL is on (note that every `http://` url in `live-reco.js` is assumed to have been changed to `https://` due solving #67).
Does it works? Congrats'!
You can now clean up to remove the proxy:
- [ ] in `app.js` remove `const proxy = ...` and `proxy.create()`
- [ ] in `config.json`, remove the `client.proxified` option and the `proxy` section
- [ ] in `config.json` ensure `client.gstreamerURL`, `client.reco.host` and `client.reco.port` are set to their correct un-proxified values
- [ ] remove `lib/proxy.js`, it is no longer useful
- [ ] in `live-reco.js` you can remove `proxifiedConnectionHandler` and the test in `createConnection`, as they should be no longer useful
- [ ] in `package.json`, you can now remove the `sockjs-client`, `webstomp-client`, `ws` and `xmlhttprequest` dependencies, assuming they are still not used anywhere else (remember to update `yarn.lock`)Due to #67 we introduced a proxy in 0ce9822 (tagged with `proxy`).
This is an ugly workaround, and should be removed when #67 is fixed.
To test that everything work without proxy, do the following in `config.json`:
- set `client.proxified` to `false`
- set `client.gstreamerURL` to `wss://:hublot_kaldi-gstreamer_1:80/client/ws/speech?content-type=audio/x-matroska,+rate=(int)48000,+channels=(int)` (or whatever is the correct SSL ws URL)
- set `client.reco.host` to `hublot_recommender_1`
- set `client.reco.port` to `8080`
Everything should work as before, assuming SSL is on (note that every `http://` url in `live-reco.js` is assumed to have been changed to `https://` due solving #67).
Does it works? Congrats'!
You can now clean up to remove the proxy:
- [ ] in `app.js` remove `const proxy = ...` and `proxy.create()`
- [ ] in `config.json`, remove the `client.proxified` option and the `proxy` section
- [ ] in `config.json` ensure `client.gstreamerURL`, `client.reco.host` and `client.reco.port` are set to their correct un-proxified values
- [ ] remove `lib/proxy.js`, it is no longer useful
- [ ] in `live-reco.js` you can remove `proxifiedConnectionHandler` and the test in `createConnection`, as they should be no longer useful
- [ ] in `package.json`, you can now remove the `sockjs-client`, `webstomp-client`, `ws` and `xmlhttprequest` dependencies, assuming they are still not used anywhere else (remember to update `yarn.lock`)https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/68Webserver does not free port when killing hublot2017-11-10T15:09:27ZTom JORQUERAWebserver does not free port when killing hublothttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/67Secure endpoints (recommander + kaldi)2017-11-14T15:30:45ZTom JORQUERASecure endpoints (recommander + kaldi)These services should expose their endpoint with SSLThese services should expose their endpoint with SSLhttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/63Docker creates anonymous containers when running hublot with `docker-compose`2017-10-24T14:55:38ZTom JORQUERADocker creates anonymous containers when running hublot with `docker-compose`https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/53Function helper get element scope2017-10-13T12:37:42ZYoann HOUPERTFunction helper get element scopehttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/51Use general OpenPaaS file API for storage2017-10-02T14:49:59ZTom JORQUERAUse general OpenPaaS file API for storageDeprecate ad-hoc storage API from dedicated OpenPaaS fork and replace it by general OpenPaaS file API.Deprecate ad-hoc storage API from dedicated OpenPaaS fork and replace it by general OpenPaaS file API.https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/47Add README and documentation2017-11-10T14:50:02ZTom JORQUERAAdd README and documentationSprint 2017-10-24https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/44Recommendations rework2017-10-02T14:56:13ZTom JORQUERARecommendations reworkRecommendations need to be improve:
- which recommendations sources?Recommendations need to be improve:
- which recommendations sources?https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/43UX - access to transcripts/summaries2017-10-02T14:56:23ZTom JORQUERAUX - access to transcripts/summariesUsers must have a way to access stored transcripts and summaries.
(OpenPaaS module?)Users must have a way to access stored transcripts and summaries.
(OpenPaaS module?)https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/42UX - Allow users to enable/disable Hublot2017-10-02T14:56:31ZTom JORQUERAUX - Allow users to enable/disable HublotUsers must be able control how and if hublot records them.Users must be able control how and if hublot records them.https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/41Define Hublin internal API2017-10-02T14:56:43ZTom JORQUERADefine Hublin internal APIDefine (and implement) an internal Hublin API to facilitate hublot integrationDefine (and implement) an internal Hublin API to facilitate hublot integrationhttps://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/40Selenium scaling2017-10-02T14:56:53ZTom JORQUERASelenium scalingHow to scale our use of Selenium? (Selenium Grid?)How to scale our use of Selenium? (Selenium Grid?)https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/39STT service scaling2017-10-02T14:57:00ZTom JORQUERASTT service scalingHow to scale our use of the STT service?How to scale our use of the STT service?https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/22hublot require allowing to run insecure content2017-09-27T09:05:09ZTom JORQUERAhublot require allowing to run insecure contentDue to the fact that some of the external services do not expose secured (aka https, wss) end points, we need to configure our browser runner to allow access to insecure content.
This should not cause a problem in practice, but is still bad. We should ensure
that this will not be needed in the future, by adding a secure endpoint to all external services.Due to the fact that some of the external services do not expose secured (aka https, wss) end points, we need to configure our browser runner to allow access to insecure content.
This should not cause a problem in practice, but is still bad. We should ensure
that this will not be needed in the future, by adding a secure endpoint to all external services.https://ci.linagora.com/linagora/lgs/labs/hublot/-/issues/18Refactor client architecture/loading2017-09-27T09:05:08ZTom JORQUERARefactor client architecture/loading