Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Lots of S3 files still breaks stuff

Aperta
  • Qualcosa non va?
#11,949 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
aws, laravel, php
Ambito
backend, performance

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
PHP
Stelle
4.9k
Fork
647
Merge medio
1g 8h
PR unite (30g)
100

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di statamic/cms

Tutte le issue di statamic/cms

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.