Currently, the Import button on the Import Account Screen Errors is enabled but Errors when no string/file is presented.

Should disable that button on empty strings/file.

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

Expected Behaviour

Better support for Traefik

Current Behaviour

• Android 新手文档
• iOS 新手文档

子文档

• Demo 工程运行新手文档
• TensorFlow Lite 组件新手文档
• NCNN 组件新手文档
• MNN 组件新手文档

Expected Behavior

Per wiki "Getting Started With a Raspberry Pi 3 and the Bosch XDK": "The sensors from the XDK should now be visible in the Sensors & Devices app in the web user interface."

Actual Behavior

After last step in wiki (bin/Linux/armv7l/macchina), got the following result:
bin/Linux/armv7l/macchina: error while loading shared libraries: libPocoOSP.so.2: cannot open shar

Thank you for this awesome tool! This is not a bug report, but something like question or maybe feature request. It sometimes required to change build process, sometimes webextension-toolbox-config.js works like a charm, but unfortunately not always. Sometimes I need to change built-in webpack config and I wonder can I somehow do 'eject' (like at create-react-app) and have webpack config in my pro

The dup runtime test fails with:

$ make TARGET=dup run                                                                                                                                                                                   
make[1]: Entering directory '/share/src/nanovms/master01/contgen'                                                                                            

The staticServer in superfly/fly is a handy way to serve a static site without another backend. This package would make a great new home for it.

Current behavior (how does the issue manifest):
The examples that demonstrate how to use the rules action within a flogo app.json are not documented.

Expected behavior:
Document the usage of the samples via a README in the corresponding samples directory