FIX: Workflow raises exception if result is numpy array

[daniel-ge]

Hi guys,

this is a first ugly workaround to resolve #270
Feel free to suggest a more generic approach, because this works only for numpy arrays and probably fail for xarray.

[satra]

@daniel-ge - thanks for bringing this up. perhaps something around the ability to retrieve a value through indexing would work for lists and arrays (numpy or xarray or dataframes for example).

let's not depend on numpy but some fundamental object construct that could tell us this is a different kind of object.

@djarecka - it would be good to look back on why the fix did not address this situation.

[djarecka]

@daniel-ge - thanks you for reporting and suggesting the changes. As @satra wrote, we try to avoid extra dependencies, but I did create another fix in #340. I believe this should fix the issue you experience, but will wait for your confirmation.

@satra - looks like the test I added before was not covering it, and this place was not fixed

[satra]

@djarecka - isn't this not fixed?

[djarecka]

yes, this should be fixed, but I will double check the test

[djarecka]

closing the PR, since #270 has been fixed. If you still experience problems please reopen the issue