Debugging with the Amazing Profiler

Hey @pasquale_pellicani ,

Thanks for this tip! Indeed, if you're using Apache instead of built-in Symfony web server that we're using in the screencast - you would need that symfony/apache-pack package that will bring an .htaccess file into your app.

Cheers!

Hi @Mahmut-A

1. What do you mean still exist?
2. Logging can be configured with monolog bundle

Can you provide more details what exactly you want to achieve?

Cheers

Hi Sadikoff,

1. I used composer remove debug command. But all debug package is still in composer.json file. I expected it will be removed from there. Also, debug bar is still seen on top of page. I want to disable it.
2. We ignore second question. thank you

Oh, I got it. That is a tricky moment debug is an installation alias, so once you installed debug pack, you should forget about it, and if you want to uninstall it, you should uninstall each package separately.

Cheers!

Hey @tomoguchi ,

How to remove? It's as easy as execute composer remove command. If you use Symfony Flex - it will also remove config files. If no, you will need to do it manually. But basically, you just need to drop the package from your composer.json file, for this you leverage the command I mentioned above: composer remove ... and then you need to disable the bundle in the config/bundles.php - just literally drop the related namespace from there. Then clean up any related config files in the config/ dir. I think that's all :)

Cheers!

hello @Victor does that also removes the generated files, setting and autowirings composer require some-bundle created?

Hey @tomoguchi ,

Yes, it has to remove those files too. Well, not the files you created manually but the files that were created by Symfony Flex recipe. But it will happen only if you have Symfony Flex enabled and allowed in your project.

Cheers!

Hey @John-S, this is indeed odd. To confirm, removing one dump() reduces the request time to ~2 seconds and adding a dump() increases to ~6 seconds? Do you see the dump output as expected in the profiler?

1 dump() 2 seconds.
2 dump() 4 seconds.
3 uses of dump() profiler line:
dump 6078.2 ms / 2 MiB
probably something with the settings but just not sure what.

Does it happen on every request? In particular when you don't change the code
Do you experiment the same behavior with a different Symfony app?
I believe you may have added by mistake a sleep() somewhere in your vendors. Try re-installing them

Cheers!

Hey John,

It depends on the data you're trying to dump. If you're dumping heavy objects, the serialization may really take long time. Also, sometimes it depends if you're using a virtualization tool like Docker or no. With virtualization tools numbers can be really much more increased.

But in short, that's OK, because you should use dump()/dd() features only in dev mode and never should use it on production.

Cheers!

Hey @John-S

To make composer install things under the require-dev key, you need to pass the --dev flag. You can also manually move the dependencies from one key to another in case you forgot to add the flag.

Cheers!

Hey @Mahmut-A

Can I ask why? You're the first one I know who doesn't like it - lol
Seriously, that debug toolbar is only loaded on the "dev" environment. You can remove it by deleting the bundle's entry in config/bundles.php

Cheers!

Hi,

the first reason is actually I wanted to test to remove a package from composer. so when I used composer remove command, composer.json did not delete this package. so I did not want to wrong thing to affect all symfony environment.
the second reason, I am building my project in web service apache. so I do not want show the debug to clients.

then, I understand that if any package is need to remove, I need to remove from config/bundle.php right?
thank you for your help

Ok, the bundle you want to remove is this one symfony/debug-bundle - I recommend not removing it because it only works on the "dev" environment, so your clients won't see it, also, it should be in the require-dev composer key and those dependencies should not be installed in your production server. You can do that by adding the flag composer install --no-dev

then, I understand that if any package is need to remove, I need to remove from config/bundle.php right?

That's true only for bundles

Cheers!

Hi MolloKhan,

Thank you.
I applied this command: composer install --no-dev but page gives below error:

Attempted to load class "DebugBundle" from namespace "Symfony\Bundle\DebugBundle".<br />Did you forget a "use" statement for another namespace?

because of that, ı added debug again by command composer require debug

When installing composer deps using the --no-dev flag your must run your application on the "prod" environment, otherwise it will try to load dev dependencies but those were not installed, hence, your error

Actually, how can we describe prod? Because my project under /var/www/html and it is working as a apache web.
I dont do in localhost.
Because of that, my expectation is when I do this —no-dev command, it should be disabled.

Thank you so much again for your kindly help

I mean the APP_ENV environment variable. That should be set to "prod" - I recommend you to watch this video, it will give you a better idea of Symfony environments https://symfonycasts.com/screencast/symfony-fundamentals/environments

Cheers!