While working on Deploy RestWS for D7 project issue JSON I needed a pretty print for the node.json and scanner done for Drush Issue Queue Commands Fix for the new json structure on d.o D7. Both issues as still open so help needed.

Doing some research I learned about the PHP context or more specific the HTTP stream context

As we all know Drupal 8 has lots of new stuff. One of these items is based on Dependency Injection and result in a new file stored at sites/defaults/files/php/service_container/service_container_prod.php/e7000f005xxx.php and created very early during the bootstrap of Drupal. But what is it's contents?

Who is calling my function so many times? With devel module and some probing using debug_backtrace and a nifty by ref variable it's a snap.

Drupal 8 is is code and feature wise an awesome new kid on the block. A few people did a lot of coding. But can do a lot people little? In this blog I hope to get one change into the issue queue and that's getting rid of the needs tests kitten killer.

I sometime need to check arrays for their values dispersed around. Just dumping the array is OK when interested in a particular key or value. But what about those big info arrays from hook_token_info, hook_menu etc. This is what I did.

If you have just changed code (for example deployed a new module or moved an existing one) read http://drupal.org/documentation/rebuild
Additional uncaught exception thrown while handling exception.
Original