@leo Thanks again hazel teams for your work !

I saw that now-desktop releases are managed like that:

My electron-builder output looks like that:

Could you tell us mo

a) it should be easier to tag a migration failed if the process exited as non-0, with anything written to stdout, or both. At the moment, we just swallow it all...

b) add to the docs a couple of examples of setting refs to the output and dealing with it

The documentation needs the following improvements:

• Add tutorial on how to use libpull to send updates using Zephyr + nRF52840 + BLE;
• Finish documenting the API to fix the Travis build.

this should instead leverage env (currently using the env var PORT) in common with the actual HTTP listener so that when the workflow-manager chart template is customized with a different listening port the doctor wrapper continues to work

Steps to reproduce

1. First - Create Autofield Timestamp
2. Second - new point
3. Third - save Layer and Error

Traceback (most recent call last):
  File "C:/Users/USER/.qgis2/python/plugins\AutoFields\EventManager.py", line 185, in providerExpressionBasedUpdate
    self.expressionBasedUpdate( layer, dictProperties, feature.id() )
  File "C:/Users/USER/.qgis2/python/plugins\AutoFields\Event