refactor: handle repeated livewire request exceptions #702
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
https://app.clickup.com/t/86dqmbkz9
Created a JS handler to watch for failed livewire requests. When the failure count reaches 10 failed requests in a row (per component), the page will reload which will force the component to reload. There are a few possible reasons a livewire request could fail:
10 repeatedly failed attempts to update a component seemed like a safe number. The Price Ticker is updated every 30 seconds so it would take ~5 minutes for this to trigger. However, the delegate monitor polls every second (ish) so that could take 10-20 seconds before triggering a page reload.
To test:
resources/views/livewire/price-ticker.blade.php
30s
to1s
app/Http/Livewire/PriceTicker.php
public string $price;
to the properties$this->price = md5((string) now()->unix());
to the mount methodChecklist