[pyrefly] Share invalidation queueing lifecycle - #4384
Conversation
Consolidate the duplicated asynchronous invalidation transaction flow while keeping ordinary and configuration-specific completion behavior in their callers.
|
Hi @lyydsheep! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
Fixes #4300
Summary
.scratchplanning files are intentionally not included in this PR.Validation
cargo test -p pyrefly lsp_interaction::configuration— 22 passedcargo test -p pyrefly lsp_interaction::diagnostic— 37 passed, 1 existing ignoredcargo test -p pyrefly lsp_interaction::file_watcher— 3 passedcargo test -p pyrefly lsp_interaction::cross_file_invalidation_project_mode— 3 passedcargo test -p pyrefly lsp_interaction::did_change— 3 passedpython3 test.py --no-test --no-tensor-shapes --no-conformance --no-jsonschema— passed; one pre-existing Clippy warning incrates/pyrefly_config/src/error_kind.rs