From 78c14bed0c1fe5db9eba6e4ed1719940fd5cbbc0 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:02:06 -0600 Subject: [PATCH 1/8] Update README.md --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 11bc5066..4175d5f8 100644 --- a/README.md +++ b/README.md @@ -17,3 +17,13 @@ Real-world use cases for Kōjō and instructions for getting Kōjō up and runni XDebug version greater than `xdebug-2.7.0alpha1` is required when trying to debug Kōjō. This version of XDebug resolves issues (https://bugs.xdebug.org/938) caused by the way the Kōjō forks using `pcntl`. If you are using PhpStorm and you have more concurrent Kōjō jobs running than the `Max. simultaneous connections` defined for your XDebug listener, Kōjō will appear to hang. To avoid this, increase your `Max. simultaneous connections` to the max value of `20` in PhpStorm's preferences under `Languages & Frameworks` > `PHP` > `Debug`, `External connections` section. + +## Kojo Hanging Doing Nothing? + +* Stop all local containers and rebuild them +* Run ps-auxf to see if any ports are still running kojo + If yes run kill -9 +* Run docker-compose exec redis redis-cli monitor to monitor +* Turn off the debugger. Sometime will will mess with Kojo +* Check your version of XDEBUG or build.sh (might need to upgrade) +* Checkout the debugging logs [Troubleshooting common PHP debugging issues - Help | PhpStorm](https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html#) From edda982aebe929b734039e1e5bd0c48746d662b3 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:03:59 -0600 Subject: [PATCH 2/8] Grammer Fix --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4175d5f8..9c156364 100644 --- a/README.md +++ b/README.md @@ -24,6 +24,6 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than * Run ps-auxf to see if any ports are still running kojo If yes run kill -9 * Run docker-compose exec redis redis-cli monitor to monitor -* Turn off the debugger. Sometime will will mess with Kojo +* Turn off the debugger. Sometimes this will mess with Kojo * Check your version of XDEBUG or build.sh (might need to upgrade) * Checkout the debugging logs [Troubleshooting common PHP debugging issues - Help | PhpStorm](https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html#) From eb05aeb9b14b5fde0b4596e3509d7a26ef51cd4c Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:04:39 -0600 Subject: [PATCH 3/8] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9c156364..97d82120 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than * Stop all local containers and rebuild them * Run ps-auxf to see if any ports are still running kojo - If yes run kill -9 + - If yes run kill -9 * Run docker-compose exec redis redis-cli monitor to monitor * Turn off the debugger. Sometimes this will mess with Kojo * Check your version of XDEBUG or build.sh (might need to upgrade) From 1479d959cf1b2244207161b16764de3112216f10 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:29:30 -0600 Subject: [PATCH 4/8] Update README.md Co-Authored-By: Alex Berryman --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 97d82120..a48d3d6b 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than ## Kojo Hanging Doing Nothing? * Stop all local containers and rebuild them -* Run ps-auxf to see if any ports are still running kojo +* Run `ps -auxf` to see if any processes are still running Kōjō with a title like `neighborhoods-kojo: /server[8]/root[22]/job[30]` - If yes run kill -9 * Run docker-compose exec redis redis-cli monitor to monitor * Turn off the debugger. Sometimes this will mess with Kojo From ed9e41f4e5c4e586d7df0b2ee243aabcb2ff6eee Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:29:47 -0600 Subject: [PATCH 5/8] Update README.md Co-Authored-By: Alex Berryman --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a48d3d6b..a82c3d8f 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than * Stop all local containers and rebuild them * Run `ps -auxf` to see if any processes are still running Kōjō with a title like `neighborhoods-kojo: /server[8]/root[22]/job[30]` - - If yes run kill -9 + - If yes run `pkill -9 -f kojo` to SIG_KILL all the processes containing the word `kojo` * Run docker-compose exec redis redis-cli monitor to monitor * Turn off the debugger. Sometimes this will mess with Kojo * Check your version of XDEBUG or build.sh (might need to upgrade) From 6a525abf5eb0154d2793506b9fa364eb133af673 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:30:04 -0600 Subject: [PATCH 6/8] Update README.md Co-Authored-By: Alex Berryman --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a82c3d8f..5e11ac2f 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,8 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than * Stop all local containers and rebuild them * Run `ps -auxf` to see if any processes are still running Kōjō with a title like `neighborhoods-kojo: /server[8]/root[22]/job[30]` - If yes run `pkill -9 -f kojo` to SIG_KILL all the processes containing the word `kojo` -* Run docker-compose exec redis redis-cli monitor to monitor +* Run `docker-compose exec redis redis-cli monitor` to see if Kōjō is creating any activity in redis. + * If nothing is streaming by like `"GET" "/neighborhoods/kojo/area_manager/job_state_changelog_processor.lock"` messages then something else is blocking the execution of Kōjō internals. This is typically due to a debugger. * Turn off the debugger. Sometimes this will mess with Kojo * Check your version of XDEBUG or build.sh (might need to upgrade) * Checkout the debugging logs [Troubleshooting common PHP debugging issues - Help | PhpStorm](https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html#) From 0e3e5c134a13cee4632f4a0786935654c59f3a80 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:30:17 -0600 Subject: [PATCH 7/8] Update README.md Co-Authored-By: Alex Berryman --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5e11ac2f..60952245 100644 --- a/README.md +++ b/README.md @@ -26,5 +26,5 @@ If you are using PhpStorm and you have more concurrent Kōjō jobs running than * Run `docker-compose exec redis redis-cli monitor` to see if Kōjō is creating any activity in redis. * If nothing is streaming by like `"GET" "/neighborhoods/kojo/area_manager/job_state_changelog_processor.lock"` messages then something else is blocking the execution of Kōjō internals. This is typically due to a debugger. * Turn off the debugger. Sometimes this will mess with Kojo -* Check your version of XDEBUG or build.sh (might need to upgrade) +* Check your version of XDebug (version before `2.7.0` won't work and `2.8.2` has seen some odd behavior. Recommend `2.9.2`) * Checkout the debugging logs [Troubleshooting common PHP debugging issues - Help | PhpStorm](https://www.jetbrains.com/help/phpstorm/troubleshooting-php-debugging.html#) From 050223b42e3637063258bdaec78c507e0a2ca3d4 Mon Sep 17 00:00:00 2001 From: Nathaniel Alvarado <31739570+Nat3Dogg@users.noreply.github.com> Date: Thu, 13 Feb 2020 12:30:43 -0600 Subject: [PATCH 8/8] Update README.md Co-Authored-By: Alex Berryman --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 60952245..68196b8a 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ XDebug version greater than `xdebug-2.7.0alpha1` is required when trying to debu If you are using PhpStorm and you have more concurrent Kōjō jobs running than the `Max. simultaneous connections` defined for your XDebug listener, Kōjō will appear to hang. To avoid this, increase your `Max. simultaneous connections` to the max value of `20` in PhpStorm's preferences under `Languages & Frameworks` > `PHP` > `Debug`, `External connections` section. -## Kojo Hanging Doing Nothing? +## Kōjō appears to be hanging during local development? * Stop all local containers and rebuild them * Run `ps -auxf` to see if any processes are still running Kōjō with a title like `neighborhoods-kojo: /server[8]/root[22]/job[30]`