Surya
@mvanbeusekom bumping this up, as this PR would really help fixing a hole in the ecosystem, in terms of compatibility.
- Does this mean, We pull latest main and build or testing against the latest release of ray? - Why not use the same cron setup that we have right...
I created this PR. But it adds the compatibility test in the cron https://github.com/Eventual-Inc/Daft/pull/1656
@jaychia could you give some comment on this, so that I can close this up?
Thank you so much for building such an incredible library.
Hey @type-checker !! Thank you so much for the detailed issue. Appreciate that very much. Bug 1 and 2. We just merged a fix yesterday. We'll be doing a release...
Wow! that is surprising. This is what I was seeing in the nextjs repo, when initializing. ``` next.js (oxen) oxen add . 🐂 oxen added 23340 files (135.0 MB) in...
Hi @type-checker This helped with identifying the issue. we have done a lot of optimisations for both `add` and `push`. So these issues should be cleared in the upcoming release.
Hi! @type-checker We've made a [new release](https://github.com/Oxen-AI/Oxen/releases/tag/v0.36.1) with the updates. This should fix `add` and `push` being slow in the nextjs repo issue.
Hi @type-checker !! thanks for this detailed issue. I am looking at this issue with clone and am looking to reproduce this locally today. I'll keep you updated on the...