Jump to content
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
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   1 member

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...