After I installed Mirasvit Profiler by the composer, I can't run Magento setup.
Here is exception when I try to run bin/magento list

[UnexpectedValueException] Could not parse version constraint 100.*.*: Invalid version string "100.*.*"

Fatal error appears function phpinfo() is used, function phpinfo() is used in the library for establishing a connection via SFTP. Library uses phpinfo() to check PHP settings.
for example phpseclib\Crypt\RSA
function __construct() { $this->configFile = dirname(__FILE__) . '/../openssl.cnf'; if (!defined('CRYPT_RSA_MODE')) { switch (true) { .... case extension_loaded('openssl') && file_exists($this->configFile): ... ob_start(); @phpinfo(); $content = ob_get_contents(); ob_end_clean();

After installing and trying to enable mirasvit profile, I initially got an error that it couldn't find symfony/yaml, so I ran

composer require symfony/yaml

After installing yaml I was able to enable the profile.

However now I'm getting the following error. I've tried increasing memory etc. but nothing seems to be working.

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /www/website/vendor/symfony/yaml/Parser.php on line 508

Any idea how to resolve this error?

Running Magento 2.2

some extension (Magme WebForms Pro 2) use an iframe to post form data and get json back. unfortunately, Mirasvit_Profiler then appends its profiling block to the result, breaking the javascript execution.

could the extension check if a response header with content-type "application/json" is set and then not output the block?

Hello,

I'm trying this profiler with Magento 2.4.3. It works to generate files in var/profiler when I run CLI commands, however, if I load my website with the web browser it does not generate profiler reports. Is there something else that needs to be done, or does this extension need to be modified to work on Magento 2.4.3? Thanks.

Hi,

Is there a way to also catch the ajax requests? They are handled on a "different" page and I think they're not shown.

In the past we used aoeprofiler, there you could easily see what happened since all was nicely stored in database and you could look into each request afterwards.

Might be a good idea to do something similar unless I'm missing something? :)

It seems this module has been updated a few times but the most recent release is from 2017, meaning composer users, and even users on your own demo site, dont see the flamegraph feature from #37

Проблема

• Не работает профайлер

Шаги к воспроизведению

• При вводе в консоль php -f bin/magento module:enable Mirasvit_Profiler работает модуль включается.
• при php -f bin/magento mirasvit:profiler:enable выводит Status: Disabled. При входе в страницу профайлера ничего не выводится http://prntscr.com/iat76o.

Дополнительно

There seems to be some kind of hole that causes lot of memory leaking on php bin/magento CLI usage on custom scripts or even Mirasvit_ElasticSearch usage having the Mirasvit_Profiler installed on the store.

Wasted some hours of the team for debugging custom products importer, downgrading the store and plugins. We've finally figured out, that without any warning the reason of 20MB being added to memory through each loop element comes from the module-profiler 👎 :(

I'm trying to install on a M2.2.2 EE customised version. After running composer require the magento cli command stops working and whatever command I try I can only see a phpinfo() interrupted output

$_SERVER['DOCUMENT_ROOT'] => 
$_SERVER['REQUEST_TIME_FLOAT'] => 1515767401.4869
$_SERVER['REQUEST_TIME'] => 1515767401
$_SERVER['argv'] => Array
(
    [0] => bin/magento
    [1] => module:enable
    [2] => Mirasvit_Profiler
)

$_SERVER['argc'] => 3
$_SERVER['MAGE_PROFILER_STAT'] =>  

Any idea what can be the problem? thanks

Background

Whilst deploying static content with php bin/magento setup:static-content:deploy we get an error about not being able to find /path/to/magento/pub/static/base/Magento/base/default/css///maxcdn.bootstrapcdn.com/font-awesome/4.5.0/css/font-awesome.min.css

fixed this by removing the call to font-awesome from the css and inserting with xml in the layout files.

please fix this in your repo

Lately I run into this already several times (never had it in the past):

[mywebsite@web report]$ cat 205592336724 a:4:{i:0;s:384:"Warning: file_get_contents(/home/mywebsite/domains/mywebsite.nl/public_html/var/view_preprocessed/html/vendor/mirasvit/module-profiler/src/Profiler/view/base/web/css/module.css): failed to open stream: No such file or directory in /home/mywebsite/domains/mywebsite.nl/public_html/var/view_preprocessed/html/vendor/mirasvit/module-profiler/src/Profiler/view/base/templates/root.phtml on line 1";i:1;s:3667:"#0 [internal function]: Magento\Framework\App\ErrorHandler->handler(2, 'file_get_conten...', '/home/mywebsite/d...', 1, Array) #1 /home/mywebsite/domains/mywebsite.nl/public_html/var/view_preprocessed/html/vendor/mirasvit/module-profiler/src/Profiler/view/base/templates/root.phtml(1): file_get_contents('/home/mywebsite/d...') #2 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/View/Result/Page.php(312): include('/home/mywebsite/d...') #3 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/View/Result/Page.php(245): Magento\Framework\View\Result\Page->renderPage() #4 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/View/Result/Layout.php(164): Magento\Framework\View\Result\Page->render(Object(Magento\Framework\App\Response\Http\Interceptor)) #5 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Interceptor.php(74): Magento\Framework\View\Result\Layout->renderResult(Object(Magento\Framework\App\Response\Http\Interceptor)) #6 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Chain/Chain.php(70): Magento\Framework\View\Result\Page\Interceptor->___callParent('renderResult', Array) #7 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Chain/Chain.php(63): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'renderResult', Object(Magento\Framework\View\Result\Page\Interceptor), Array, 'result-varnish-...') #8 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/module-page-cache/Model/Controller/Result/VarnishPlugin.php(74): Magento\Framework\Interception\Chain\Chain->Magento\Framework\Interception\Chain\{closure}(Object(Magento\Framework\App\Response\Http\Interceptor)) #9 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Chain/Chain.php(67): Magento\PageCache\Model\Controller\Result\VarnishPlugin->aroundRenderResult(Object(Magento\Framework\View\Result\Page\Interceptor), Object(Closure), Object(Magento\Framework\App\Response\Http\Interceptor)) #10 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\Interception\Chain\Chain->invokeNext('Magento\\Framewo...', 'renderResult', Object(Magento\Framework\View\Result\Page\Interceptor), Array, 'result-builtin-...') #11 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/module-page-cache/Model/Controller/Result/BuiltinPlugin.php(67): Magento\Framework\View\Result\Page\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Response\Http\Interceptor)) #12 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/Interception/Interceptor.php(142): Magento\PageCache\Model\Controller\Result\BuiltinPlugin->aroundRenderResult(Object(Magento\Framework\View\Result\Page\Interceptor), Object(Closure), Object(Magento\Framework\App\Response\Http\Interceptor)) #13 /home/mywebsite/domains/mywebsite.nl/public_html/var/generation/Magento/Framework/View/Result/Page/Interceptor.php(26): Magento\Framework\View\Result\Page\Interceptor->___callPlugins('renderResult', Array, Array) #14 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/App/Http.php(139): Magento\Framework\View\Result\Page\Interceptor->renderResult(Object(Magento\Framework\App\Response\Http\Interceptor)) #15 /home/mywebsite/domains/mywebsite.nl/public_html/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http->launch() #16 /home/mywebsite/domains/mywebsite.nl/public_html/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http)) #17 {main}";s:3:"url";s:24:"/profiler/profile/index/";s:11:"script_name";s:10:"/index.php";}[mywebsite@web report]$

following these links in the readme shows "There has been an error processing your request"

http://profiler.m2.mirasvit.com/profiler/profile/index/
http://profiler.m2.mirasvit.com/

We are using Magento 2.2 (on Windows with Wamp PHP 7.0.10) but the problem also start to happen recently on a Magento 2.1 install it was working fine before.

When the profiler is enable at the bottom of the page we see:

Fatal error: Uncaught Exception: Warning: file_put_contents(C:/www/magento2rendy/var/profiler/2017-09-28 11:58:07.081800.meta): failed to open stream: Invalid argument in C:\www\magento2rendy\vendor\mirasvit\module-profiler\src\Profiler\Model\Storage.php on line 48 in C:\www\magento2rendy\vendor\magento\framework\App\ErrorHandler.php on line 61

Our /var/profiler/ folder is empty.

Same when we use the command bin/magento mirasvit:profiler:enable:

Fatal error: Uncaught Exception: Warning: file_put_contents(C:/www/magento2rendy/var/profiler/2017-09-28 11:54:55.613000.meta): failed to open stream: Invalid argument in C:\www\magento2rendy\vendor\mirasvit\module-profiler\src\Profiler\Model\Storage.php on line 48 in C:\www\magento2rendy\vendor\magento\framework\App\ErrorHandler.php:61 Stack trace: #0 [internal function]: Magento\Framework\App\ErrorHandler->handler(2, 'file_put_conten...', 'C:\\www\\magento2...', 48, Array) #1 C:\www\magento2rendy\vendor\mirasvit\module-profiler\src\Profiler\Model\Storage.php(48): file_put_contents('C:/www/magento2...', 'RESPONSE_CODE: ...') #2 C:\www\magento2rendy\vendor\mirasvit\module-profiler\src\Profiler\Model\Driver\Output\Html.php(39): Mirasvit\Profiler\Model\Storage->dump() #3 C:\www\magento2rendy\vendor\magento\framework\Profiler\Driver\Standard.php(195): Mirasvit\Profiler\Model\Driver\Output\Html->display(Object(Magento\Framework\Profiler\Driver\Standard\Stat)) #4 [internal function]: Magento\Framework\Profiler\Driver\Standard- in C:\www\magento2rendy\vendor\magento\framework\App\ErrorHandler.php on line 61

And then profiler is not shown.

Can you help us solve this issue?

what i observed on your demo is when i load any url very first time it come up with many queries (81) in following example but for second onwards requests it just make 4 DB calls how is this possible?

When running this command:
php -f bin/magento setup:di:compile

I get this error:
[Exception]
Warning: ltrim() expects parameter 1 to be string, array given in /data/web/magento2/setup/src/Magento/Setup/Module/Di/Compiler/Config/Chain/B
ackslashTrim.php on line 61

Tracing it back, it is because the profile is set to enabled.
(vendor/magento/framework/App/ObjectManagerFactory.php -> line 150 it sets:
'parameters' => ['backendPrefixes' => ['Zend_Cache_Backend_', 'Cm_Cache_Backend_']],)

And that is because:
(vendor/magento/framework/Profiler.php -> function enable is called)

This is logical.. So to avoid this issue, I decided to disable profiling:
php -f bin/magento mirasvit:profiler:disable

Same error.

Next step, really disable the extension:
php bin/magento module:disable Mirasvit_Profiler
To be sure:
php bin/magento setup:upgrade
php bin/magento cache:clean

Still the same error.

Then.. Added a debug_print_backtrace(); in here:
vendor/magento/framework/Profiler.php -> public static function enable() (line 182)

#0 Magento\Framework\Profiler::enable() called at [,vendor/magento/framework/Profiler.php:139]
#1 Magento\Framework\Profiler::add(Magento\Framework\Profiler\Driver\Standard Object ([_stat] => Magento\Framework\Profiler\Driver\Standard\Stat Object ([_timers] => Array ()),[_outputs] => Array ([0] => Mirasvit\Profiler\Model\Driver\Output\Html Object ()))) called at [,vendor/magento/framework/Profiler.php:337]
#2 Magento\Framework\Profiler::applyConfig(Array ([driverConfigs] => Array ([0] => Array ([output] => Mirasvit\Profiler\Model\Driver\Output\Html,[stat] => Magento\Framework\Profiler\Driver\Standard\Stat Object ([_timers] => Array ()),[baseDir] => /Users/jw/Projects/Bluedesk/design-online)),[driverFactory] => Magento\Framework\Profiler\Driver\Factory Object ([_defaultDriverType] => standard,[_defaultDriverPrefix] => Magento\Framework\Profiler\Driver),[tagFilters] => Array (),[baseDir] => /Users/jw/Projects/Bluedesk/design-online), /Users/jw/Projects/Bluedesk/design-online, ) called at [,vendor/mirasvit/module-profiler/registration.php:10]
#3 require(,vendor/mirasvit/module-profiler/registration.php) called at [,vendor/composer/autoload_real.php:71]
#4 composerRequirec39cd91b2232e2cae3e4179f9ac543ea(753fed6dc1b400d43e296cf7746c8785, ,vendor/composer/../mirasvit/module-profiler/registration.php) called at [,vendor/composer/autoload_real.php:61]
#5 ComposerAutoloaderInitc39cd91b2232e2cae3e4179f9ac543ea::getLoader() called at [,vendor/autoload.php:7]
#6 include(,vendor/autoload.php) called at [,app/autoload.php:30]
#7 require_once(,app/autoload.php) called at [,app/bootstrap.php:30]
#8 require(,app/bootstrap.php) called at [,bin/magento:14]

Conclusion, profiling is switched on, while the extension is disabled and even disabled from Magento configuration.

Current solution is to really remove the extension to prevent the profiler to be enable.
But I assume that should not be needed.

1 exception(s):
Exception #0 (Exception): Warning: file_get_contents(/html/var/profiler//.prof): failed to open stream: No such file or directory in /html/vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php on line 63

Use this command

php -d memory_limit=10G bin/magento mirasvit:profiler:enable

to enable the profiler and getting the this issue:

PHP Fatal error:  Uncaught Error: Class 'Symfony\Component\Yaml\Dumper' not found in /var/www/html/vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php:48
Stack trace:
#0 /var/www/html/vendor/mirasvit/module-profiler/src/Profiler/Model/Driver/Output/Html.php(39): Mirasvit\Profiler\Model\Storage->dump()
#1 /var/www/html/vendor/magento/framework/Profiler/Driver/Standard.php(195): Mirasvit\Profiler\Model\Driver\Output\Html->display(Object(Magento\Framework\Profiler\Driver\Standard\Stat))
#2 [internal function]: Magento\Framework\Profiler\Driver\Standard->display()
#3 {main}
  thrown in /var/www/html/vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php on line 48

Why issue are coming ?

After installing the module I get errors when trying to use any of the bin/magento commands, for example [InvalidArgumentException] There are no commands defined in the "setup" namespace.

I have tried clearing the cache and code generation directories, but this has no effect. If I remove the module I no longer get the errors.

The site is running Magento 2 CE 2.1.2. In composer.json I'm requiring "mirasvit/module-profiler": "dev-master" from the https://github.com/mirasvit/module-profiler repository.

If I run php bin/magento list I get a bit more useful info:

We're sorry, an error occurred. Try clearing the cache and code generation directories. By default, they are: var/cache, var/di, var/generation, and var/page_cache.

[Zend\ServiceManager\Exception\ServiceNotCreatedException]
  An abstract factory could not create an instance of magentosetupconsolecommandconfigsetcommand(alias: Magento\Setup\Console\Command\ConfigSetCommand).

[Zend\ServiceManager\Exception\ServiceNotCreatedException]
  An exception was raised while creating "Magento\Setup\Console\Command\ConfigSetCommand"; no instance returned

[Magento\Framework\Exception\FileSystemException]
  Cannot read contents from file "/var/www/strax/vendor/mirasvit/module-profiler/etc/module.xml" Warning!file_get_contents(/var/www/strax/vendor/mirasvit/module-profiler/etc/module.xml): failed to open stream: No such file or directory

Is this a bug, or am I doing something wrong perhaps?

Hello,

I've installed the module in my project. The project is based on Magento 2.1.7.

I've had a toolbar of the profiler, but when i'm viewing a page of result or list of results - i'm seeing a blank page.

In system.log:

[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'header.panel.wrapper' element cannot be added as child to 'header.container', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'head.components' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'requirejs-config' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'translate-config' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'translate' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'js_cookies' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'global_notices' element cannot be added as child to 'after.body.start', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'skip_to_content.target' element cannot be added as child to 'main.content', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'header-wrapper' element cannot be added as child to 'header.container', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'navigation.sections' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'top.container' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'breadcrumbs' element cannot be added as child to 'page.top', because the latter doesn't exist [] []
[2017-10-06 09:56:14] main.CRITICAL: Broken reference: the 'page.main.title' element cannot be added as child to 'columns.top', because the latter doesn't exist []

Does anyone of you have the same problem?

Fatal error: Uncaught exception 'Magento\Framework\Exception\LocalizedException' with message 'Area code is not set' in /code/dev/magento2/vendor/magento/framework/App/State.php:139 Stack trace:
#0 /code/dev/magento2/vendor/magento/framework/View/Element/Template.php(216): Magento\Framework\App\State->getAreaCode()
#1 /code/dev/magento2/vendor/magento/framework/View/Element/Template.php(202): Magento\Framework\View\Element\Template->getArea()
#2 /code/dev/magento2/vendor/magento/framework/View/Element/Template.php(279): Magento\Framework\View\Element\Template->getTemplateFile()
#3 /code/dev/magento2/vendor/magento/framework/View/Element/AbstractBlock.php(657): Magento\Framework\View\Element\Template->_toHtml()
#4 /code/dev/magento2/vendor/mirasvit/module-profiler/src/Profiler/Model/Driver/Output/Html.php(44): Magento\Framework\View\Element\AbstractBlock->toHtml()
#5 /code/dev/magento2/vendor/magento/framework/Profiler/Driver/Standard.php(195): Mirasvit\Profiler\Model\Driver\Output in /code/dev/magento2/vendor/magento/framework/App/State.php on line 139

Hello Good afternoon my friend

I installed your module and the following error is displayed as image

http://pasteboard.co/1evLeTJ1.png

Fatal error: Uncaught exception 'Exception' with message 'Warning: Invalid argument supplied for foreach() in /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/mirasvit/module-profiler/src/Profiler/Block/Tab/Sql.php on line 49' in /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/magento/framework/App/ErrorHandler.php:61 Stack trace: #0 /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/mirasvit/module-profiler/src/Profiler/Block/Tab/Sql.php(49): Magento\Framework\App\ErrorHandler->handler(2, 'Invalid argumen...', '/home/ubuntu/pu...', 49, Array) #1 /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/mirasvit/module-profiler/src/Profiler/view/base/templates/tab/sql.phtml(6): Mirasvit\Profiler\Block\Tab\Sql->getSlowQueries() #2 /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/magento/framework/View/TemplateEngine/Php.php(59): include('/home/ubuntu/pu...') #3 /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/magento/framework/View/Element/Template.php(255): Magento\Framework\View\TemplateEngine\Php->render(Object( in /home/ubuntu/public_html/magento-2.0.0-dev17/vendor/magento/framework/App/ErrorHandler.php on line 61

I had the following conversation on a Magento chat.

Paul [3:30 PM]
I'm having trouble running di-compile, the .ser files generated in var/di causing errors
Running into the following error: http://cloud.h-o.nl/hl2k

Someone else [3:34 PM]
Upgraded to 2.1.2 in composer, worked perfectly, also with di-compile

Paul [3:35 PM]
Hmm
The exception is super unclear
Even if I suppress the statement it seems to be working just fine..
@mhauri Have you also tested with mode set to production and having ran setup:di:compile
This is causing the problems.. http://cloud.h-o.nl/hlKw

Someone else [3:43 PM]
Did you tried to remove all files in var/di and run again

Paul [3:43 PM]
Yeah, multiple times
I had installed a third party profiler, deleting now.
It seems that when a new profiler driver is added it also enabled the profiler, although it isn't actually requested to be enabled.

It seems to be enabled here: \Magento\Framework\Profiler::add(). So i guess it should do some checks if it should actually add the driver.

Hello good afternoon

About Magento 2.3 Support

As images we see that error is displayed when trying to install your module, can you help me

Dependency resolution completed in 0.193 seconds
Your requirements could not be resolved to an installable set of packages.

	  Problem 1
		- mirasvit/module-profiler 1.0.0 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.1 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.2 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.3 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.4 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.5 requires magento/framework 100.*.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 100.0.19, 100.1.10, 100.1.11, 100.0.20, 100.1.12, 100.1.13, 100.1.14, 100.1.15, 100.1.16].
		- mirasvit/module-profiler 1.0.6 requires magento/framework 100.*|101.* -> satisfiable by magento/framework[100.0.2, 100.0.3, 100.0.4, 100.0.5, 100.0.6, 100.0.7, 100.0.8, 100.0.9, 100.1.0, 100.0.10, 100.0.11, 100.1.1, 100.0.12, 100.1.2, 100.1.3, 100.0.13, 100.1.4, 100.0.14, 100.1.5, 100.0.15, 100.1.6, 100.1.7, 100.0.16, 100.0.17, 100.1.8, 100.1.9, 100.0.18, 101.0.0, 100.0.19, 101.0.1, 100.1.10, 100.1.11, 101.0.2, 100.0.20, 100.1.12, 101.0.3, 100.1.13, 101.0.4, 101.0.5, 100.1.14, 100.1.15, 101.0.6, 100.1.16, 101.0.7].
		- magento/framework 101.0.7 requires php ~7.0.13|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.16 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.6 requires php ~7.0.13|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.15 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.14 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.5 requires php ~7.0.13|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.4 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.13 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.3 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.12 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.20 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.2 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.11 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.10 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.1 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.19 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 101.0.0 requires php 7.0.2|7.0.4|~7.0.6|~7.1.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.18 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.9 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.8 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.17 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.16 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.7 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.6 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.15 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.5 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.14 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.4 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.13 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.3 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.2 requires php ~5.6.5|7.0.2|7.0.4|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.12 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.1 requires php ~5.6.0|7.0.2|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.11 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.10 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.1.0 requires php ~5.6.0|7.0.2|~7.0.6 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.9 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.8 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.7 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.6 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.5 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.4 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.3 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- magento/framework 100.0.2 requires php ~5.5.0|~5.6.0|~7.0.0 -> your PHP version (7.2.14) does not satisfy that requirement.
		- Installation request for mirasvit/module-profiler ^1.0 -> satisfiable by mirasvit/module-profiler[1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6].

Display profiler only if cookie is exists (like allowed-ips)

Facing that error when adding comment to order

2017/06/19 09:59:11 [error] 32488#32488: *93318 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Zend_Controller_Plugin_Abstract::setResponse() must be an instance of Zend_Controller_Response_Abstract, instance of Magento\Framework\HTTP\PhpEnvironment\Response given, called in /var/www/example/www/production/releases/20170602144729/vendor/magento/framework/Profiler/Driver/Standard/Output/Firebug.php on line 61 and defined in /var/www/example/www/production/releases/20170602144729/vendor/magento/zendframework1/library/Zend/Controller/Plugin/Abstract.php:70
Stack trace:
#0 /var/www/example/www/production/releases/20170602144729/vendor/magento/framework/Profiler/Driver/Standard/Output/Firebug.php(61): Zend_Controller_Plugin_Abstract->setResponse(Object(Magento\Framework\HTTP\PhpEnvironment\Response))
#1 /var/www/example/www/production/releases/20170602144729/vendor/magento/framework/Profiler/Driver/Standard.php(195): Magento\Framework\Profiler\Driver\Standard\Output\Firebug->display(Object(Magento\Framework\P" while reading response header from upstream, client: 10.99.0.19, server: www.example.de, request: "POST /adm_n/sales/order/addComment/order_id/17466/key/8af67ddd1762355fdc42ae9f292211daa5a23da0b2dd1519aef2d567d00f2566/?isAjax=true HTTP/1.0", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "www.example.de", referrer: "https://www.example.de/adm_n/sales/order/view/order_id/17466/key/37f07c7afffa913886c27d4db73964b59b266cecab2b464af9a2fa77f6fffe48/"

Magento: 2.1.7 + PHP7

No screenshots or content in "Screenshots - Magento 2 Code Profiler and Database Profiler" section of readme

With composer install, I can't see module in module list ( bin/magento module:status )

I tried to do composer remove mirasvit/module-profiler , then reinstall...

It's like magento 2 doesnt recognize profiler .

Magento 2 version : ver 2.2.6 (luma, not a single module)
OS : Ubuntu...

Error appears on installation on M2.2.2 with docker.

• docker-compose exec --user www-data magento.ts.mirasvit.com /bin/sh -c ' cd /var/www/html; composer require mirasvit/module-profiler:dev-master#4ec3c2590b45ab139a3e147de6b2276fcdbca78a || exit 1; bin/magento module:enable --all; bin/magento setup:upgrade; if [ -f "/var/www/html/vendor/mirasvit/module-profiler/codeception/tests/acceptance.suite.yml.travis" ]; then cp /var/www/html/vendor/mirasvit/module-profiler/codeception/tests/acceptance.suite.yml.travis /var/www/html/vendor/mirasvit/module-profiler/codeception/tests/acceptance.suite.yml; cd /var/www/html/vendor/mirasvit/module-profiler/codeception/; composer install;
  fi; '
  ./composer.json has been updated
  Loading composer repositories with package information
  Updating dependencies (including require-dev)
  Your requirements could not be resolved to an installable set of packages.

  Problem 1

  • symfony/yaml v4.0.2 requires php ^7.1.3 -> your PHP version (7.0.25) does not satisfy that requirement.
  • symfony/yaml v4.0.1 requires php ^7.1.3 -> your PHP version (7.0.25) does not satisfy that requirement.
  • symfony/yaml v4.0.0 requires php ^7.1.3 -> your PHP version (7.0.25) does not satisfy that requirement.
  • Conclusion: remove symfony/console v2.8.32
  • Conclusion: don't install symfony/console v2.8.32
  • symfony/yaml v3.4.0 conflicts with symfony/console[v2.8.32].
  • symfony/yaml v3.4.1 conflicts with symfony/console[v2.8.32].
  • symfony/yaml v3.4.2 conflicts with symfony/console[v2.8.32].
  • Installation request for symfony/console (locked at v2.8.32, required as ~2.3, !=2.7.0) -> satisfiable by symfony/console[v2.8.32].
  • Installation request for mirasvit/module-profiler dev-master#4ec3c2590b45ab139a3e147de6b2276fcdbca78a -> satisfiable by mirasvit/module-profiler[dev-master].
  • Conclusion: don't install symfony/dependency-injection v3.4.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2
  • Conclusion: remove symfony/dependency-injection v3.4.1|install symfony/yaml v3.4.0|install symfony/yaml v3.4.1|install symfony/yaml v3.4.2

Hi, there's an error with this module when running unit tests:

running 1.0.6 and under tab "Performance" it is empty after the php and database time

on chrome console it says

• d3 is not defined
  and
• require.js:166 Uncaught Error: Script error for: jquery

it seems it cant load jquery.

I have made the following changes to the enble command:

file: ../magento2ce/vendor/mirasvit/module-profiler/src/Profiler/Console/Command/EnableCommand.php

line 42: $this->appState->setAreaCode(\Magento\Framework\App\Area::AREA_FRONTEND);

Running: Magento ver. 2.2.0-dev

https://github.com/madalinoprea/magneto-debug

Hello,
we have some API intergration with another platform. When we enable profiler on magento then comunication to /index.php/rest/V1 give us wrong answer(because profiler paste code to response) .

Is there any posibility to disable profiler to REST url ?

Проблема

• Ошибки после установки профайлера:
  I try to install Mirasvit Module Profiler and i cant to get work. After install and allow my IP, i have error 500 or empty/blank page or something like this:

There has been an error processing your request
Warning: file_get_contents(/opt/bitnami/apps/magento/htdocs/var/view_preprocessed/pub/static/vendor/mirasvit/module-profiler/src/Profiler/view/base/web/css/module.css): failed to open stream: No such file or directory in /opt/bitnami/apps/magento/htdocs/var/view_preprocessed/pub/static/vendor/mirasvit/module-profiler/src/Profiler/view/base/templates/root.phtml on line 1
Error log record number: 464823309575

I try to fix creating directory and copy the missed files but didn't succes. I get same error.

Magento 2.2.2-3 on google cloud server with varnish trought appache. I really need this extension for find some bootleneck on appache and varnish redirections when cache loads

Шаги к воспроизведению

Доступы

#NDZ-932-78221

Дополнительно

After the upgrade to Magento 2.2 the follow error is generated when the extension is enabled:

PHP Fatal error: Uncaught Error: Class 'Symfony\Component\Yaml\Dumper' not found in vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php:48
Stack trace:
#0 vendor/mirasvit/module-profiler/src/Profiler/Model/Driver/Output/Html.php(39): Mirasvit\Profiler\Model\Storage->dump()
#1 vendor/magento/framework/Profiler/Driver/Standard.php(195): Mirasvit\Profiler\Model\Driver\Output\Html->display(Object(Magento\Framework\Profiler\Driver\Standard\Stat))
#2 [internal function]: Magento\Framework\Profiler\Driver\Standard->display()
#3 {main}
thrown in vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php on line 48

Command: bin/magento mirasvit:profiler:enable

Error:
PHP Parse error: syntax error, unexpected '->' (T_OBJECT_OPERATOR) in vendor/mirasvit/module-profiler/src/Profiler/Model/Storage.php on line 42

My PHP Version: 5.6.31

Hi,

I am facing this issue while enabling this profiler module.
please help to get this issue resolve.

C:\wamp64\www\MyProjects\Magento22Comp>php -f bin/magento mirasvit:profiler:enable
Status: Enabled

Fatal error: Uncaught Exception: Warning: file_put_contents(C:/wamp64/www/MyProjects/Magento22Comp/var/profiler/2017-11-19 09:29:24.274500.meta): fail
\wamp64\www\MyProjects\Magento22Comp\vendor\mirasvit\module-profiler\src\Profiler\Model\Storage.php on line 48 in C:\wamp64\www\MyProjects\Magento22Co
1
Stack trace:
#0 [internal function]: Magento\Framework\App\ErrorHandler->handler(2, 'file_put_conten...', 'C:\\wamp64\\www\\M...', 48, Array)
#1 C:\wamp64\www\MyProjects\Magento22Comp\vendor\mirasvit\module-profiler\src\Profiler\Model\Storage.php(48): file_put_contents('C:/wamp64/www/M...',
#2 C:\wamp64\www\MyProjects\Magento22Comp\vendor\mirasvit\module-profiler\src\Profiler\Model\Driver\Output\Html.php(39): Mirasvit\Profiler\Model\Stora
#3 C:\wamp64\www\MyProjects\Magento22Comp\vendor\magento\framework\Profiler\Driver\Standard.php(195): Mirasvit\Profiler\Model\Driver\Output\Html->disp
mp\vendor\magento\framework\App\ErrorHandler.php on line 61

for more clarification, i already executed below command and package is available. But still getting above error.
composer require symphony/yaml
Magenot Version 2.2.0

Regards,
Nitin

I am using Magento 2.2. After composer remove mirasvit/module-profiler command get on frontend:

Autoload error
Cannot create standard driver output, class "Magento\Framework\Profiler\Driver\Standard\Output\Mirasvit\Profiler\Model\Driver\Output\Html" doesn't exist.

It is possible for this configuration to be null, and is directly passed into an explode function

As of php8.1 this is no longer accepted