Ville Rantala

@jinchihe It is true that the Azure integration tests do not currently pass in the Google CI environment, but the workaround was to ignore them there (see [this line](https://github.com/kubeflow/fairing/blob/cd8b46020c7f7a8bef2aa71c7503fb2ab182a846/cloudbuild.yaml#L22)). If...

I am able to reproduce the same issue. Could it be the same root cause as in the issue discussed at https://github.com/kubeflow/fairing/issues/196#issuecomment-481526203?

@chaitanyak52 It looks like this kind of change makes the example work https://github.com/vjrantal/fairing/commit/7f58f994d628392d43f01476bd146237cc36c404. However, I am not sure if the intent is that user would not have to provide the...

@mingqxu I used a USB-connected camera. I did notice that others have run into this issue as well such as [here](https://devtalk.nvidia.com/default/topic/1022685/open-cv-camera-error-jetson-tx2/). I am not planning to try to make this...

@Shrunoti Could you try to run the `docker build` commands exactly as described at the bottom of section https://github.com/vjrantal/iot-edge-darknet-module#running-on-jetson-tx2-or-drive-px2? You should not have to manually run dpkg or apt-get, because...

@kjsingh44 It is expected that the root of the site returns "cannot get". The manifest you should use when adding your deployment to your Office is at http://ismstampery.azurewebsites.net/manifest-officeblock.xml. However, you...

@kjsingh44 When you add the add-in, you need to use the manifest URL, i.e., https://stampery1.azurewebsites.net/manifest-officeblock.xml and not the root of the site. You can read more from https://dev.office.com/docs/add-ins/overview/office-add-ins.

@kjsingh44 It might not be clear from the readme, but the implementation is currently intended to be used from Outlook and would not work as is on other Office environments...