You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7a322dd
Browse filesBrowse the repository at this point in the historyBrowse files
Three findings, all real:
- @blosc2.jit forwarded every decorator kwarg to blosc2.asarray() when the
traced function returned a NumPy array, so combining a storage kwarg with
an execution-tuning one -- @blosc2.jit(jit=False, cparams=...) -- raised
instead of returning an NDArray. Only storage kwargs go there now; the
function has already run, so there is nothing left to tune. The sibling
compute() call keeps taking all of them on purpose: compute() names
fp_accuracy while lazyudf() does not, so stripping them would drop it.
- The mandelbrot benchmark's header still said any non-None jit() kwarg
flips the return container. Only storage kwargs do.
- _fill_me_udata leaked np_data/np_typesizes on every allocation-failure
exit after the one that allocates them. All the exits now go through one
_free_me_udata_tables() helper, so a table added later cannot be missed by
some of them again.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments