aboutsummaryrefslogtreecommitdiff
path: root/crates/syntax/src/ast/generated
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-05-23 12:12:45 +0100
committerGitHub <[email protected]>2021-05-23 12:12:45 +0100
commit57eedd906688d6cfa332bd40bca5234043e7293e (patch)
treeec24c448fb866396aa345641a9eb819f0d34c0ad /crates/syntax/src/ast/generated
parent0ec4ce1e9bceb2d7b0833de2ab59e2cd583e01ec (diff)
parentdaedcc2b77187486fde13a2813809b06b2385ac0 (diff)
parent9f9c4bf3de79ea22bd122574654d5f9f2066c3f9 (diff)
Merge #8936 #8939
8936: fix: Improve nightly downloads with better local state management r=matklad a=SomeoneToIgnore When any nightly is downloaded, we store its GitHub release id in the local cache and never invalidate that cache. Due to this, it was possible to do the following sequence: * have the nightly locally * downgrade the extension to any stable version * observe that despite the `"rust-analyzer.updates.channel": "nightly",` setting, no nightly updates are happening * on the next day, the actual update happens (given the new nightly is released) Since it's impossible to install nightly version directly through the VSCode marketplace, any fiddling with dev version results in the same situation: one have to wait for the next nightly release to happen in order to restore the nightly. This PR * invalidates the cache eagerly during bootstrap if the current plugin is not nightly * enforces the release id check for nightly versions only * fixes the `ctx.globalStoragePath` deprecated API usage Hopefully, it also helps mysterious non-updated plugins that we encounter from time to time, but hard to tell for sure. 8939: internal: disable debug symbols due to failing windows build r=matklad a=matklad bors r+ 🤖 Co-authored-by: Kirill Bulatov <[email protected]> Co-authored-by: Aleksey Kladov <[email protected]>