-
Notifications
You must be signed in to change notification settings - Fork 24
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
Class "Facades\Statamic\Fields\FieldsetRepository" not found at Fields.php:221 #87
Comments
I could never understand why these happen. That's a realtime facade, so it should just get created on the fly. 🤔 |
I do notice that there was apparently a similar error for Static Cache warming that’s long since been fixed. Not sure if that is at all instructive. statamic/cms#4082 |
Sometimes I get this instead: I’m putting it here because it seems to be related in that it’s not the same error, but it could be a similar source, since it’s something that makes zero sense. |
Could this be related to the multithreading with PHP 8? Like one thread gets ahead of something else? |
Could be |
I am experiencing the same with FieldsetRepository class, I submitted support ticket about this, apologies for duplicating concern. I have seen two variations for this on my Netlify builds:
and on Jan 11 deploy there was this
|
Hi everyone! Can confirm the issue exists only when using multiple workers, single worker |
I also just got a
|
Just a heads up I have been getting a lot of these errors when deploying to Laravel Vapor. Having this is in my Removing the warming of the stache solved the issue. |
Upgraded statamic, laravel versions to 3.3.* and 9.34 in staging and prod applications. It's working in staging but in prod, i'm facing this issue. Did any one explain what exctly is the reason and solution to this issue. |
I’ve been having a sporadic issue when building one of my sites on Netlify. I finally got it to happen locally so I have the full laravel log. It’s two errors, but they always seem to come together. The first one happens early in the build process, and the other happens toward the end. I assume the first one is what triggers the second problem. Initially I didn’t notice the first error because it doesn’t immediately cause the failure.
The text was updated successfully, but these errors were encountered: