Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Lots of S3 files still breaks stuff

Abierto
  • ¿Algo no está bien?
#11,949 6 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
aws, laravel, php
Área
backend, performance

Línea de trabajo

Start by reproducing the hang on staging after clearing the cache and stache, then opening an asset container in the control panel. Read the related issues #7317 and #8626 and the linked eloquent-driver pull request #218 for context. Done means the asset container loads without the site hanging or requiring a server restart.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

assets
Bug description

I've been wrestling with this for the past few months unable to identify what is actually going on. For some context, I maintain 10+ production Statamic sites and I've only experienced this on one, and the only thing that stands out about that one as far as I can tell is it has a large number of assets in s3. Roughly 7.5GB of images across ~16,500 files (spread across hundreds of top level directories).

My working theory is this is related to some "background task" that is running and initializing something (stache? metadata files? no idea really) - I tried asking about this in discord but didn't get any replies.

The best example of what happens here is when I deploy to our staging server, which wipes the cache/stache etc and I navigate to an asset container in the control panel, the whole site hangs. Sometimes it resolves after a few minutes, sometimes it leads to what I assume is thrashing and I have to force stop the EC2 (even that takes about 5 minutes so whatever is happening is so intense an EC2 "force stop" can't even execute).

If it does resolve on our staging server, the site appears to be pretty snappy from that point on so it really seems like some sort of secret initialization process. Another interesting data point is that this is far less of an issue on our production server is which significantly higher resourced (but also like 10x higher resourced than any of our other Statamic sites).

This may be related to these:

How to reproduce

See above.

Logs
Environment
Environment
Application Name: <redacted>
Laravel Version: 11.45.1
PHP Version: 8.3.10
Composer Version: 2.7.7
Environment: production
Debug Mode: OFF
URL: <redacted>
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: mysql
Logs: stack / single
Mail: ses
Queue: sync
Session: file

Statamic
Addons: 4
Sites: 1
Stache Watcher: Disabled
Static Caching: half
Version: 5.58.1 PRO

Statamic Addons
alt-design/alt-redirect: 1.3.3
aryehraber/statamic-logbook: 3.3.0
jacksleight/statamic-bard-texs
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Lenguaje dominante
PHP
Estrellas
4.9k
Forks
647
Merge medio
1 d 9 h
PR fusionados (30 d)
102

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de statamic/cms

Todos los issues de statamic/cms

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.