-
Notifications
You must be signed in to change notification settings - Fork 10
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
Latest compiled component path not found. #2131
Comments
@marvinroman Can we get your help on this ticket please? @jobara any additional context you can provide here perhaps? Thanks! |
@marvinroman and @SantiagoG-Colab, this was generated from a Flare error report. Best to follow the link in the description for all the details. The report highlights
This is an issue on the dev deploy. It appears to be occurring frequently and around the time the database is reset nightly. It looks like things started on Feb 2. On Feb 1 there were a bunch of PRs merged, many of which are related to dependency updates. (see: https://github.com/accessibility-exchange/platform/commits/dev/?since=2024-02-01&until=2024-02-01 ) |
I was able to duplicate locally, by pulling the latest dev version and running |
Here are the errors that were output locally during the refresh.
|
Based on the comments above I'd assume that the initial confirm language dialog is trying to run on the 503 page that is shown when in maintenance mode. And it would seem that the resources needed for that aren't available yet. We should look into preventing that dialog when the site is in maintenance mode. |
May have been resolved by #2134. Should confirm if Flare errors have stopped after that PR has been merged to dev. |
This issue still occurs after #2134 PR was merged. |
I'm also getting this issue and have updated to the latest packages. This seems to be directly linked to Vite as when I have Vite dev mode or built assets, everything works and my tests pass. |
@jobara out of interest, what packages have you got installed? Thanks! |
@chrispage1 I'm starting to think that my changes in the linked PR did in fact work, as we haven't experienced this error for the past two days. If that's correct the relevant change is likely to pre-render the maintenance mode page. See Laravel's Pre-rendering the maintenance mode view docs. php artisan down --render="errors::503" This would probably fit with the Vite theory in that some assets aren't available during maintenance mode. But the pre-rendering should solve that issue. I'm not sure where you're experiencing the error. Possibly the same as us with maintenance mode, or maybe you had missed building the assets. Another thing would also be to look at the view cache. |
This issue wasn't reported for a couple of days but has come back. As it was before. |
This might be related to livewire/livewire#7934 |
@jobara Is this on Marvin's or Jure's domain? |
@chrispage1 you can see the packages in the composer.json file. |
@SantiagoG-Colab yes, this is part of the work that @marvinroman was looking into. We had hoped that the PR #2134 would have resolved this too, but it doesn't seem to have. Given the timing it appears to have something to do with the nightly database reset for the dev deploy. |
@jobara when I was frantically googling this issue I didn't realise this issue was on an entirely different project. I've been experiencing this using Livewire core itself but haven't had any issues in a while. |
I moved the internal health check to move to just check database connection. This should check 3 things in the pods.
This should be sufficient for just health checks that are trying to determine if the pod should be able to handle requests. The external Node Ping check will still be checking for full page rendering . |
I did some testing of maintenance mode on a local development environment and reviewed the file created When I tried to pre-render the template with the command ERROR Failed to enter maintenance mode: Vite manifest not found at: public/build/manifest.json (View: resources/views/partials/head.blade.php) (View: resources/views/partials/head.blade.php) (View: resources/views/partials/head.blade.php) (View: resources/views/partials/head.blade.php). This fails to put the site into maintenance mode. It doesn't seem to trigger any error logs though. When using the normal maintenance mode it will use the framework to render maintenance mode. // Allow framework to handle request if no prerendered template...
if (! isset($data['template'])) {
return;
} |
I think we are missing the |
Exception
Latest compiled component path not found.
🎯 Livewire\Mechanisms\ExtendBlade\DeterministicBladeKeys::generate
📄 /vendor/livewire/livewire/src/Mechanisms/ExtendBlade/DeterministicBladeKeys.php
Open in Flare
The text was updated successfully, but these errors were encountered: