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   1 member

  • Similar Content

    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180528, v1.0.4 add custom select statement option 180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen