Skip to content

Conversation

@kratos2377
Copy link
Contributor

Part of #11467

Updated some of the core dependencies to their latest version.

I have tested the change by running rerun as both desktop and web application. The examples are working fine.

@Wumpf @emilk Please take a look at the PR when you have time and let me know if any other validation is also required.

Copy link
Member

@emilk emilk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to commit a new Cargo.lock too

js-sys = "0.3.77"
jsonwebtoken = { version = "9.3", default-features = false }
lance = { version = "0.38.2", default-features = false } # When you update this, also update the list of features enabled for `datafusion` (~50 lines up)
lance = { version = "0.39.0", default-features = false } # When you update this, also update the list of features enabled for `datafusion` (~50 lines up)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you remember to follow this instruction?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@emilk Added cargo.lock and there is no difference b/w the datafusion feature set in v0.39.0 and v0.38.0
v0.39.0 -> https://github.com/lance-format/lance/blob/ab5fdb362eda381bab5cb559cee94de8b3d63c6d/Cargo.toml#L106

v0.38.0 -> https://github.com/lance-format/lance/blob/v0.38.0/Cargo.toml#L99-L107

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Lance datafusion update isn't ready yet, so no surprise on these updates to the lock.

@emilk emilk added dependencies concerning crates, pip packages etc exclude from changelog PRs with this won't show up in CHANGELOG.md labels Nov 26, 2025
@emilk emilk marked this pull request as draft November 27, 2025 08:35
@emilk
Copy link
Member

emilk commented Nov 27, 2025

Looks like a lot of crates no longer compile. Please make sure pixi run rs-check works!

@kratos2377 kratos2377 marked this pull request as ready for review November 27, 2025 11:45
@kratos2377 kratos2377 marked this pull request as draft November 27, 2025 14:17
js-sys = "0.3.77"
jsonwebtoken = { version = "9.3", default-features = false }
lance = { version = "0.38.2", default-features = false } # When you update this, also update the list of features enabled for `datafusion` (~50 lines up)
lance = { version = "0.39.0", default-features = false } # When you update this, also update the list of features enabled for `datafusion` (~50 lines up)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timsaucer is there any reason not to update lance right now?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any blocker here, but we would want to update our platform repo in lock step.

@kratos2377
Copy link
Contributor Author

@emilk I have reverted a lot of deps back to their previous version or to a different version because there were lot of conflicts in crates. the command pixi run rs-check is still giving some errors though. Just wanted to confirm if the command nextest is valid or not. This is the recent result after my changes

Screenshot from 2025-11-27 22-13-11

@kratos2377 kratos2377 marked this pull request as ready for review November 28, 2025 14:19
@kratos2377
Copy link
Contributor Author

@emilk All the checks seems to be passing now in CI/CD , is there anything else you want me to validate ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies concerning crates, pip packages etc exclude from changelog PRs with this won't show up in CHANGELOG.md

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants