adrian

Tracy Debugger

Recommended Posts

Hi @adrian

Just wondering if it's normal that even in full screen mode, the console output is so small? I can't resize also.

Thanks

Firefox58, Ubuntu 16.04, Tracy4.9.13, PW 3.0.91

image.thumb.png.e604d56ba637dd618ff2046d094cf550.png

Share this post


Link to post
Share on other sites
1 minute ago, mel47 said:

Just wondering if it's normal that even in full screen mode, the console output is so small? I can't resize also.

It does look like the initial resize hasn't worked properly - maybe I need to test Firefox. Try dragging the resize handle (between the code and results pane).

Also, if you click the Console panel icon (rather than hover) and then click the "large" up arrow at the top right. The large version will be kept unless you revert.

Let me know if you have trouble getting that to work.

Share this post


Link to post
Share on other sites

PS - don't forget ->each("title") when testing page selectors so it's easier to see what pages are matched.

  • Like 1

Share this post


Link to post
Share on other sites

ah, yeah, could move the console but not the output. Too late, should go to sleep I guess...

Thanks for ->each, didn't know. ;-)

Share this post


Link to post
Share on other sites
Just now, mel47 said:

ah, yeah, could move the console but not the output

Sorry, I have no idea what that means :)

Could you explain a little more, or do a screen recording please. I don't see an issue here on FF on Mac, but maybe there is something with the Linux version?

Share this post


Link to post
Share on other sites
5 minutes ago, mel47 said:

Thanks for ->each, didn't know. ;-)

Here's the info on each() 
https://processwire.com/blog/posts/processwire-core-updates-2.5.27/#new-each-method-added-to-all-processwire-arrays

On a related note, it's also worth reading about these related methods
https://processwire.com/talk/topic/5098-new-wirearray-api-additions-on-dev/

Share this post


Link to post
Share on other sites

Hi,

All of a sudden Tracy consum 100% CPU. If I disable or uninstall Tracy, the CPU consumption back to normal. Any idea what is the possible cause?

Gideon

Share this post


Link to post
Share on other sites
1 hour ago, Gideon So said:

All of a sudden Tracy consum 100% CPU. If I disable or uninstall Tracy, the CPU consumption back to normal. Any idea what is the possible cause?

Not sure, but let's go through a few things:

1) Is this a new thing on a version of Tracy that was fine before, or is it a new version of Tracy?

2) Same server / php version as before the issue?

3) What is the OS of the server?

4) Is it an issue on all pages of your site?

5) Does it make any difference to click the PW Info Panel > Clear Session & Cookies?

6) Does restarting apache help?

7) Does the debug bar actually load still?  Does it take a long time to load?

8) Are there any huge files in site/assets/logs ?

Let me know all that stuff and we'll go from there. 

  • Like 1

Share this post


Link to post
Share on other sites
36 minutes ago, adrian said:

Not sure, but let's go through a few things:

1) Is this a new thing on a version of Tracy that was fine before, or is it a new version of Tracy?

I was using an old version and then upgraded to the latest version but both versions cause the same problem.

2) Same server / php version as before the issue?

Yes.

3) What is the OS of the server?

Linux

4) Is it an issue on all pages of your site?

Yes.

5) Does it make any difference to click the PW Info Panel > Clear Session & Cookies?

Makes no difference.

6) Does restarting apache help?

Yes.

7) Does the debug bar actually load still?  Does it take a long time to load?

The debug loads pretty normal.

8) Are there any huge files in site/assets/logs ?

No.

Let me know all that stuff and we'll go from there. 

 

 

Share this post


Link to post
Share on other sites

Thanks for those details @Gideon So - here's some more :)

1) What Linux distro? Just wondering if there is any Debian session stuff going on

2) After restarting apache, does CPU stay low consistently, or does it start to climb again?

3) Can you narrow it down to a specific panel? Firstly check the Panel Selector to see if any are listed as high MB. But then, please try turning off all extra panels and enable one by one to see if there is one that is the trigger.

Thanks for helping out.

Share this post


Link to post
Share on other sites

Hi @adrian,

Is there a way to see actions executed in the Console and Snippets panels reflected in the Debug panel?

So if in the Console panel I execute some code that gets data from the database, is there a way I can I see PDO Queries, Selector Queries, Hooks Triggered, etc, for that?

Share this post


Link to post
Share on other sites
On 2018/2/25 at 12:09 AM, adrian said:

Thanks for those details @Gideon So - here's some more :)

1) What Linux distro? Just wondering if there is any Debian session stuff going on

Fedora 23

2) After restarting apache, does CPU stay low consistently, or does it start to climb again?

After restarting apache, the CPU stay low.

3) Can you narrow it down to a specific panel? Firstly check the Panel Selector to see if any are listed as high MB. But then, please try turning off all extra panels and enable one by one to see if there is one that is the trigger.

I got that. The Tracy Logs panel causes the problem.

Thanks for helping out.

 

Share this post


Link to post
Share on other sites
2 hours ago, Robin S said:

Is there a way to see actions executed in the Console and Snippets panels reflected in the Debug panel?

It should already do that. Here's an example showing a selector query in the Console Panel and the selector and resulting query in the Selector Queries section of the Debug panel that is on the AJAX bar. Does this work for you?

image.thumb.png.cdc4496bf2934e343a03d1dbb2e2ee76.png

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, Gideon So said:

I got that. The Tracy Logs panel causes the problem.

I have actually had this happen once before - it's why I implemented the "Delete All Logs" button. It seems that when a file gets huge, it can cause problems. Maybe I can make the reading of the log files more efficient - I'll take a look.

  • Like 1

Share this post


Link to post
Share on other sites
37 minutes ago, adrian said:

Does this work for you?

Yes it does, thanks. Silly me, I had the Debug panel open from the standard (non-AJAX) bar and for some reason was imagining it might update in real time. I didn't think to check the AJAX bar.

  • Like 1

Share this post


Link to post
Share on other sites
40 minutes ago, adrian said:

I have actually had this happen once before - it's why I implemented the "Delete All Logs" button. It seems that when a file gets huge, it can cause problems. Maybe I can make the reading of the log files more efficient - I'll take a look.

@adrian

Yes. After click on the delete all log button, it is fine now. Thanks a lot for supporting this useful module so well.

 

Gideon

  • Like 1

Share this post


Link to post
Share on other sites
15 minutes ago, Gideon So said:

@adrian

Yes. After click on the delete all log button, it is fine now. Thanks a lot for supporting this useful module so well.

Great! 

I just took a look at the Tracy log file scanner code and I am actually extending PW's core log file find() method which seems to have a lot of operations for chunking and limiting the number of lines read so at the moment I don't really know why it's not working efficiently. I'll keep it in mind to revisit at some point, but for now, this is definitely a good reminder for others to check this if things seem to be slowing down lots.

Share this post


Link to post
Share on other sites

Several nice improvements over the last few days:

1) Major improvements to panel zIndex behavior - this should make things much less annoying - no more trying to get your panel of interest to be on top of another one. Mousing over the panel icon should now always bring it to the top, but with already open panels, now they only get promoted to the top if you click somewhere on the panel. Before it was onmouseover which made it quit annoying at times. Also panel order is remembered when reloading the page.

2) Console panel will no longer disappear if you use the keyboard shortcut to run code without having clicked somewhere on the panel first - much friendlier.

3) ESC key to close all open panels - I am finding this really handy already. I don't think this interferes with any other use of the escape key, but let me know if anyone thinks this should be optional.

4) Add test email address option to the Mail Interceptor panel - this was mentioned in another thread, but added here in case anyone missed it. If no address is entered, it behaves how it always did - it prevents the email from being sent and instead captures and displays what would have been sent. If you add a test email address, in addition to it's normal behavior, it also sends the email to the test address (but still not the original recipients).

image.thumb.png.c5ca8b77081fe8643e813c5cdc658c7b.png

 

5) Various bug fixes - especially in the Request Info panel when viewing certain module settings pages. 


As always, thanks for any feedback on these new features!

  • Like 8

Share this post


Link to post
Share on other sites

Hey @adrian, thank you for your continous great work and efforts on this module. Is there any way we can support you with a little donation or something else? Would you even want that?

Tracy Debugger helped me so many times, and reduces my work and error finding, so I would like to give something back to thank you.

I know, that you invest much time in developing this.

  • Like 3

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, jmartsch said:

I would like to give something back to thank you.

Lots of us too! See a few posts starting from this one:

https://processwire.com/talk/topic/12208-tracy-debugger/?do=findComment&comment=126847

Let's start a donate to Adrian movement! :) And AOS fans should ask @tpr to implement a donation button as well!

Edited by szabesz
typo
  • Like 2

Share this post


Link to post
Share on other sites

Thanks for mentioning me/AOS but I don't think AOS is comparable to Tracy :) Anyway, I may implement such button sometime, mainly out of curiosity. I've been in a similar situation years ago with my portable launcher (yaP) but I postponed it until... still today :)

  • Like 2

Share this post


Link to post
Share on other sites

Hi @adrian

I have a hook to 'TemplateFile::render' which replaces template output. In the hook, I check whether it's the main template of the page like

if ($this->wire('page') === null || $this->wire('page')->template->name == 'admin') {
				return;
		}

		$template = $event->object;
		$options = $template->options;

		if(is_array($options) && array_key_exists('pageStack', $options)) {
			...........
		}
}

But when I run any code inside Console panel I get the output of entire page render. Is there a way how I can prevent this behavior? 

Share this post


Link to post
Share on other sites

Thanks guys for the donation request - stay tuned :)

@Zeka - I am sure we can figure something out. I am having trouble reproducing at the moment - could you perhaps provide a full code example that I could test?

  • Like 1

Share this post


Link to post
Share on other sites

@adrian

Here is the full code of the hook, not sure that it will be helpful to debug the issue. Currently, have to finish module and will upload it tomorrow. 

	public function hookAfterTemplateRender($event)
	{
		if ($this->wire('page') === null || $this->wire('page')->template->name == 'admin') {
				return;
		}

		$template = $event->object;
		$options = $template->options;

		if(is_array($options) && array_key_exists('pageStack', $options)) {
			$view = $this->wire($this->api_view_var);
			$layout = $this->wire($this->api_layout_var);
			$page = $this->wire('page');
			if($template->halt) {
				return;
			};

			if (is_file($this->getViewFile($page->template->name))) {
				$view->setFilename($this->getViewFile($page->template->name));
			} else {
				throw new WireException("View file for this page template does not exist");
			}

			$view_output = $view->render();

			if (isset($layout->template) && $layout->template !== 'none') {
				$layout->setFilename($this->getViewFile($this->layouts_dir . '/' . $layout->template));
				$layout->set($this->api_view_var, $view_output);
				$event->return = $layout->render();
			} elseif(isset($layout->template) && $layout->template === 'none') {
				$event->return = $view_output;
			}
		}
	}

 

Share this post


Link to post
Share on other sites

Thanks @Zeka - yeah a bit challenging because of missing methods (and not enough time right now to futz with it). If you want to send me a copy of the module before you post it publicly, I can test and get a fix in place for the Console panel.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By thomasaull
      Some time ago I created a site profile for creation of a REST API with ProcessWire. Since I kept struggeling with updating stuff between different projects which use this, I decided to convert it into a module. It is now ready for testing: https://github.com/thomasaull/RestApi
      Additionally I added a few small features:
      automatic creation of JWT Secret at module install routes can be flagged as auth: false, which makes them publicly accessible even though JWT Auth is activated in module settings To check things out, download and install the module and check the folder /site/api for examples.
      If you find any bugs or can think of improvements, please let me know!
    • By kongondo
      Sites Manager
       
      16 September 2018:
      FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A  RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX.
       
      ################
       
      Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites.
       
      Single/Stand-alone Sites
      Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site.
      Multiple Sites
      Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1.
      Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process.
      The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration.
       
      The module will:
      Install a ProcessWire site in your named directory, applying chmod values as specified
      Move the directory to your webroot
      Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour
      For multi sites, update sites.json (used by index.config.php to get array of installed sites)
       
      For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire.
      Download from GitHub: Sites Manager (Beta Release)
      Features
      Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage
      Please see the documentation.
      Technicalities/Issues
      Only Superusers can use the module.
      ProcessWire 2.7 - 3.x compatible
      Currently using ProcessWire 2.7 installer (install.php)
      For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file?
      Not tested with sub-directory installs (for instance localhost/pw/my-site-here/)
      Currently not doing the extra/experimental database stuff (database charset and engine)
      Future Possibilities
      Install specified modules along with the ProcessWire install
      Profile previews?
      Credits
      @ryan: for the ProcessWire installer
      @abdus: for the index.config.php reading from JSON idea
      @swampmusic: for the challenge
      Video Demo
      Demo  showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server.
       
      Screens
      1

      2

       
       
    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. Unpublished and hidden pages are indicated in the dropdowns with similar styling to that used in Page List. If the option to include uneditable pages is selected then those pages are indicated by italics with a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. If the current user is allowed to add new pages under the parent page an "Add New" link is shown at the bottom of the breadcrumb dropdown. If the currently edited page has children or the user may add children, a caret at the end of the breadcrumbs reveals a dropdown of up to the first 25 children and/or an "Add New" link. Overriding the listed siblings for a page
      If you want to override the siblings that are listed in the dropdowns you can hook the BreadcrumbDropdowns::getSiblingsmethod and change the returned PageArray. For most use cases this won't be necessary.
      Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour (excl vat).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Ken Muldrew
      I'm trying to get a short routine to run once per day that will look at some pages and send a reminder email when that customer's subscription (yearly) is about to expire. When I run the code in a template then it works without issue, but inside my lazycron service routine, I get an "Error: Uncaught Error: Call to a member function get() on null" as if the database cannot be found. My autoload module is just the sample HelloWorld module included with ProcessWire, editted to perform this task. The whole of it is included below (I've stripped out the code that generates the email because it never gets past $pages->find):
       
      <?php namespace ProcessWire;
      /**
       * ProcessWire 'LazyCronLoad'  module
       *
       */
      class LazyCronLoad extends WireData implements Module {
          public static function getModuleInfo() {
              return array(
                  'title' => 'LazyCronLoad', 
                  'version' => 1, 
                  'summary' => 'Just loads a lazy cron callback.',
                  'singular' => true, 
                  'autoload' => true, 
                  );
          }
          public function init() {
              // initialize the hook in the AutoLoad module
              $this->addHook('LazyCron::everyDay', $this, 'myHook');
              
          }
          public function myHook(HookEvent $e) {
              // called once per day
              wire('log')->save('user_activities',' lazy cron service routine');
                  $transport_pages = $pages->find("template=aggregate-entry, aggregate_type.title='Transport'");
                  foreach ($transport_pages as $page) {
                      if (($page->purchase_date + 30325800 < time()) && ($page->purchase_date + 30412600 > time())) { // between 351 and 352 days
                          wire('log')->save('user_activities', $page->id . ' email reminder sent');
                          // send email
                  }
              }
          }        
          
      }
      The first wire('log') shows up but the second one doesn't (the purchase_date condition is met (as demonstrated by running the code in a template close in time to when the lazycron routine executes)). The error log gives the Uncaught Error shown above. 
      I think this is a beginner's mistake with something obvious being missed and would be grateful for any assistance in fixing it.