WARNING: /data/users/ezyang/pytorch-tmp/BUILD.bazel:580:1: in hdrs attribute of cc_library rule //:aten_headers: Artifact 
'bazel-out/k8-fastbuild/bin/aten/src/ATen/Config.h' is duplicated (through '//:aten/src/ATen/Config.h' and '//:aten_src_AT
en_config'). Since this rule was created by the macro 'cc_library', the error might have been caused by the macro implemen
tation                 

Picking up from #15731, there are many places in numpy where we do something like:

try:
    something_which_throws_typeError
except TypeError:
    raise ValueError("a clearer explanation of what went wrong")

It would produce a marginally clearer error if we could change these to use traceback chaining. Our two options are either:

1. The inner error provides valuable infor

The documentation in the Joins section https://docs.dask.org/en/latest/dataframe-joins.html has code blocks but they aren't interactive and therefore not as useful.

I think the documentation would benefit from an interactive example with use of real data (or data from the demo API).

I had a quick rummage of the tutorial (h

Reporting a bug

• [x]

Well, Gumbel Distribution is magical. Basically, given a sequence of K logits, i.e., "\log a_1, \log a_2, ..., \log a_K" and K independent gumbel random variables, i.e., "g_1, g_2, ..., g_K". We have

\argmax_i \log a_i + g_i ~ Categorical({a_i / sum(a)})

This gives you a very simple way to sampl

Support DataFrame.select_dtypes

What happened:
xr.DataArray([1], coords=[('onecoord', [2])]).sel(onecoord=2).to_dataframe(name='name') raise an exception ValueError: no valid index for a 0-dimensional object

What you expected to happen:

the same behavior as: xr.DataArray([1], coords=[('onecoord', [2])]).to_dataframe(name='name')

Anything else we need to know?:

I see that the array after the select