issue_comments

@Hoeze let's reopen this when you have a reproducible example. Thanks.

Thank you very much for trying to help :)

It's no big problem at the moment, as it only comes up when I'm debugging. If this should really get a big problem I'll try to publish a test script here.

Sorry, I'm stumped.

```

X.variable._data array([[ 3478., 9079., 51928., ..., 34312., 11081., 79157.], [ 6976., 14495., 64495., ..., 30606., 12816., 157080.], [ 4260., 10066., 47271., ..., 47332., 14947., 118562.], ..., [ 12976., 9201., 31295., ..., 22093., 8846., 96991.], [ 7033., 8238., 22521., ..., 20476., 9051., 67057.], [ 13566., 10308., 28916., ..., 15529., 7426., 84852.]], dtype=float32) type(X.variable._data) <class 'numpy.ndarray'> idx array([ 705, 753, 342, 398, 688, 661, 630, 624, 668, 669, 631, 430, 54, 828, 478, 912, 772, 78, 627, 164, 557, 393, 1019, 559, 440, 290, 226, 299, 870, 718, 603, 947, 800, 483, 66, 453, 485, 919, 671, 213, 877, 126, 684, 600, 146, 1008, 496, 1028, 196, 51, 749, 971, 779, 232, 918, 608, 72, 707, 58, 1014, 1043, 370, 185, 818, 378, 315, [... i deleted here ...] 81, 145, 1053, 839, 466, 901, 1017, 48, 521, 162, 773, 170, 846, 1091, 1361, 1257, 1249, 1163, 1166, 634, 907, 1349, 432, 304, 1417, 1343, 424, 520, 1206, 1370, 23, 1477, 1047, 1407, 1314, 69, 1197, 1443, 261, 1479, 539, 675, 47, 619, 455, 1224, 513, 667, 894], dtype=int32) type(idx) <class 'numpy.ndarray'>

```

Oops, I meant X.variable._data On Wed, Jul 4, 2018 at 4:01 AM Hoeze notifications@github.com wrote:

There is no X._data, but X.values is a simple ndarray.

I pickled X and idx: unit_test.zip https://github.com/pydata/xarray/files/2162950/unit_test.zip

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/2263#issuecomment-402445256, or mute the thread https://github.com/notifications/unsubscribe-auth/ABKS1r9A8Prx620-TFC33-3fo2w9pqJ0ks5uDKBugaJpZM4U_wV4 .

There is no X._data, but X.values is a simple ndarray.

I pickled X and idx: unit_test.zip

Can you share what X and X._data look like?

My guess is that this is a bug of some sort in a lower level library like NumPy or TensorFlow. This sort of error is basically impossible to trigger unless you are using the CPython C-API directly, which we don't do in xarray. Xarray itself is pure Python.

I tried to, but I'm not sure whats the root cause of this problem. This problem occures as part of my Tensorflow input pipeline (it's called by a py_func) and it's hard to reproduce without Tensorflow.

Maybe this helps?

It might also be possible that this is some problem with python itself or some multithreading issue. I just found this issue which exactly describes my problem: https://github.com/ContinuumIO/anaconda-issues/issues/8737

There's also the hint that this problem only occurs in debug mode. I'm always running my unit tests in debug mode, that's why I did not realize this.

Having that said, it's maybe not worth to change this in xarray and wait for a python solution to this. However, since two brackets would solve this issue, it might not be too invasive to simply fix this one line :)

Thanks for the report!

I'm afraid I don't fully understand the problem. Do you think that you can come up with a minimal bug report example?