Skip to content
This repository has been archived by the owner on Jan 2, 2021. It is now read-only.

Fix debouncer for 0 delay #662

Merged
merged 2 commits into from
Jun 23, 2020
Merged

Conversation

pepeiborra
Copy link
Collaborator

The indirection caused by async (sleep 0 >> fire) was causing non-deterministic ordering of progress done messages and diagnostics, which makes the code actions benchmark experiment fail randomly.

The indirection caused by `async (sleep 0 >> fire)` was causing the progress done messages to be sent before diagnostics, causing the code actions benchmark experiment to fail randomly.
Copy link
Collaborator

@cocreature cocreature left a comment

Choose a reason for hiding this comment

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

Nice, thank you!

@cocreature cocreature merged commit 8a9b814 into haskell:master Jun 23, 2020
pepeiborra added a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* fix debouncer for 0 delay

The indirection caused by `async (sleep 0 >> fire)` was causing the progress done messages to be sent before diagnostics, causing the code actions benchmark experiment to fail randomly.

* fix exception masking
pepeiborra added a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* fix debouncer for 0 delay

The indirection caused by `async (sleep 0 >> fire)` was causing the progress done messages to be sent before diagnostics, causing the code actions benchmark experiment to fail randomly.

* fix exception masking
pepeiborra added a commit to pepeiborra/ide that referenced this pull request Dec 29, 2020
* fix debouncer for 0 delay

The indirection caused by `async (sleep 0 >> fire)` was causing the progress done messages to be sent before diagnostics, causing the code actions benchmark experiment to fail randomly.

* fix exception masking
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants