From b260a9972f97a8dec9f4f5074c7e6afcb2694309 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Mon, 20 Jul 2015 17:50:56 +0100 Subject: [PATCH] Timeouts are not necessarily cause for alarm --- doc/articles/troubleshooting.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 3445b5f8d..bc2aeb15f 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -174,7 +174,10 @@ To enable the swap you can use for example: Due to some intermittent issues on Travis and other systems, we introduced a degraded network mode which helps Composer finish successfully but disables a few optimizations. This is enabled automatically when an issue is first -detected. +detected. If you see this issue sporadically you probably don't have to worry +(a slow or overloaded network can also cause those time outs), but if it +appears repeatedly you might want to look at the options below to identify +and resolve it. If you have been pointed to this page, you want to check a few things: