-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential stable point release tools issues #56726
Comments
Just the go-to def fix is at https://github.com/Xanewok/rust/commits/1.31-stable-gotodef (one commit ahead of current rust/stable branch), confirmed locally that it works. (RLS is checked out with a branch that points to patched rls-analysis: https://github.com/rust-dev-tools/rls-analysis/tree/1.31-stable-src-prefix-fix) |
This pulls a specific commit from rust-dev-tools/rls-analysis as opposed to the one from crates.io (Xanewok@c3277af#diff-5d9bf57935c52008319cccc88d4d737dR1813). Will that be a problem? |
cc @rust-lang/dev-tools, should this be Also, I'm not too familiar with RLS, what would be the steps to backport the changes to stable? |
For the 2nd point (go to definition) we'd have to merge Xanewok@c3277af (updates I think I'm confused as to what exactly version is on stable due to edition (do stable and beta point to the same release with nightly being only couple of days younger now?), so I'm not exactly sure what and how we should backport changes also including the fix for hover infinite loop regression. |
I've published the rls-analysis branch as Thanks @Xanewok for doing all the real work! |
@nrc don't worry about the rust PR, I'll just include the changes in the stable one. |
Also cherry-picked rust-lang/rls#1170 inside the |
Uh, are those issues fixed on beta? |
It doesn't seem like it; rust-lang/rls@77ff073 is the last commit on beta, while the infinite hover fix (rust-lang/rls@bfa1371) is just one PR further. In this case, could we just bump RLS a few commits ahead on beta channel? However I think goto-def should work, since I believe the |
Beta backport of a fix that already was backported to stable, see rust-lang#56726 and rust-lang/rls#1170 for the underlying RLS issue. Also includes the fix for rust-lang/rls#1154 (respecting target-dir specified in .cargo/config for RLS artifacts).
Ah, curses I was planning on updating beta to most recent RLS at some point before the uplift, but just uplifting that fix is fine too. Thanks for doing it @Xanewok ! |
The first is probably not worth making a point release just for that. The second is probably worth a point release, but doesn't have a fix yet. @Xanewok is investigating.
The other major tools issues are with rustup which won't need a point release.
cc @rust-lang/release
The text was updated successfully, but these errors were encountered: