catch 502 errors when bulk(+single?) deploying

Aperta
#1 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@leonstafford ci sta già lavorando.

Dal 1/4/2020.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

$ wp wp2static deploy
PHP Fatal error:  Uncaught GuzzleHttp\Exception\ServerException: Server error: `PUT https://api.cloudflare.com/client/v4/accounts/HASH/storage/kv/namespaces/HASH/bulk` resulted in a `502 Bad Gateway` response:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>clou (truncated...)
 in /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Stack trace:
#0 /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 /var/www/htdocs/wp-content/plugins/wp2static-addon- in /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113
Fatal error: Uncaught GuzzleHttp\Exception\ServerException: Server error: `PUT https://api.cloudflare.com/client/v4/accounts/HASH/storage/kv/namespaces/HASH/bulk` resulted in a `502 Bad Gateway` response:
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>clou (truncated...)
 in /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113
Stack trace:
#0 /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Middleware.php(65): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response))
#1 /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response))
#2 /var/www/htdocs/wp-content/plugins/wp2static-addon- in /var/www/htdocs/wp-content/plugins/wp2static-addon-cloudflare-workers/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113
Error: There has been a critical error on your website.Learn more about debugging in WordPress. There has been a critical error on your website.

Likely poor connection, possibly rate limit. Subsequent run fine

  • implement try/catch block
  • mark current 'processing' deployment job as 'failed'
  • WsLog error
Lingua principale
PHP
Stelle
27
Fork
16
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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 elementor/wp2static-addon-cloudflare-workers

Tutte le issue di elementor/wp2static-addon-cloudflare-workers

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.