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
issues with spirv version set to 1.4 then reverted to 1.0 much later (after it prevents compilation for some kernels)
cache optimizations PR merged in April
the only tag that points to (one of the only) commit in history that sufficiently cover dpex.kernel features needed for sklearn_numba_dpex, and does not suffer from blocking issues, is 0.21.0dev1
But it's a dev version, so there isn't a release published on intel conda channel for it. And it seems that uploads on dppy/label/dev expire after some time and 0.21.dev1 builds are not fetchable from there anymore.
Could it be please possible to release a 0.20.2 patch version, set on the same commit than 0.21.0dev1, and publish it in the intel conda channel ?
It would be nice to have patch releases right after important bugfixes so few tags can be stable, recent releases both include bugfixes but also ship new issues.
Thanks
The text was updated successfully, but these errors were encountered:
All issues are being adressed, now that #1158 is merged the latest commit on main is now usable again for me. I'll just close this ticket and wait for the 0.22.0 release that presumably will be stable, given current state on main. TY everyone.
Looking at
numba_dpex
commit history and tags and releases, and taking into account:dpctl.program._program.SyclProgramCompilationError
for some kernels for cpu target (latest updates) #1156the only tag that points to (one of the only) commit in history that sufficiently cover
dpex.kernel
features needed forsklearn_numba_dpex
, and does not suffer from blocking issues, is 0.21.0dev1But it's a dev version, so there isn't a release published on intel conda channel for it. And it seems that uploads on
dppy/label/dev
expire after some time and0.21.dev1
builds are not fetchable from there anymore.Could it be please possible to release a
0.20.2
patch version, set on the same commit than0.21.0dev1
, and publish it in the intel conda channel ?It would be nice to have patch releases right after important bugfixes so few tags can be stable, recent releases both include bugfixes but also ship new issues.
Thanks
The text was updated successfully, but these errors were encountered: