-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
panic in fold subst #17080
Comments
Narrowing down the code a little bit, it seems to be caused by this: https://github.com/zed-industries/zed/blob/3bc1a41fd46028700b2900661800b293a88d202b^/crates/collab/src/db/queries/channels.rs#L577-L600. |
Potentially #17017, which is just surfaced by my PR |
I'm getting panics from chalk as well since a couple of days ago, but a different error. They happen very frequently, almost every time I request code completion while working on https://github.com/holochain/holochain.
|
Any updates on this? I've had to revert to an older version for https://github.com/xmtp/libxmtp |
@lnicola Thank you! Just switched over now. Will let you know if I run into the same issue with the new version. |
Hello, |
Thanks! It looks like it's working on the code above, thank you! |
It's not only on nightly, the fix is released with the weekly release. If you can try to upgrade to last version and use |
This is a serious regression in nightly and it's important to fix it before the next release.
Since Friday last week, I (and one other colleague) have been getting panics from rust-analyzer when working on https://github.com/zed/zed.
The full log is here: https://gist.github.com/ConradIrwin/823575d9f9279844c9b61b8eb7571829, but the salient piece seem to be:
Although it seems like the panic is in chalk, and chalk was recently updated, the crash from Friday was on the prior version: https://gist.github.com/ConradIrwin/4af43965942a9f5e98d173528b5f2fee .
Running
"/Users/conrad/Library/Application Support/Zed/languages/rust-analyzer/rust-analyzer-2024-04-15" analysis-stats .
reproduces the crash:The text was updated successfully, but these errors were encountered: