Tamas Gal

I could reproduce it by installing a version which I had not installed before while having `Revise` running. In this case `Revise 2.1.7` was installed and I downgraded to `2.1.2`:...

Any updates on this?

It'll not happen before March, so no hurry from my side 😉

Thanks Jim for the quick answer and detailed explanation. Unfortunately, calling `ak._connect._numba.register()` right after `import awkward as ak` does not help (`import numba` was done before importing `awkward`), it gives...

On my M1 Mac, I have `0.54.1`: ``` In [1]: import numba as nb n In [2]: nb.__version__ Out[2]: '0.54.1' ``` I updated Numba in our computing centre (CentOS 7)...

Yes, I confirm that `@nb.njit` works. So it's related to `nb.vectorize`. My initial thought was that some introspection in the type inference chokes on something in Awkward. `nb.vectorize` will presumable...

Yes! With e.g. `@nb.vectorize("int64(int64)")` it works, but I have to specify all cases. I will have a look if this works for the actual use-case.

Alright, I can live with explicit type annotations, at least I managed to cover all the expected cases. Do you want to close this for now or are you going...

With this settings, it works as expected: ``` let g:neoformat_tex_latexindent = { \ 'exe': 'latexindent', \ 'args': ['-l'], \ 'stdin': 1 \ } ```

Is there a workaround?