ping @nicolas-grekas

I'm sorry about that, it's maybe to early in the morning for me, but what you describe is correct, which means there is no issue...
For the "greater issue", I'm not sure to understand. What means "inappropriately"?
Adding an arg to dump() is not possible because the function already handles several args. But anyway, can you first describe your use case or your expectations?

what you describe is correct, which means there is no issue...

There is an issue because not all inline dumps are properly suppressed when they should be / can be suppressed when we want them to be.

For the "greater issue", I'm not sure to understand.

When an inline dump (plain text) is done in a JSON response (for example), an entry for the request cannot be found in the Symfony web profiler.

What means "inappropriately"?

Plain text inline dump breaks the response. That's what I mean by "inappropriately".

Adding an arg to dump() is not possible because the function already handles several args.

Noted. Perhaps we can think of other ways then...

Is there anything we can/should do here? @nicolas-grekas says this is an expected behavior.

Should we better document it or close as "won't fix"?

When an inline dump (plain text) is done in a JSON response (for example), an entry for the request cannot be found in the Symfony web profiler.

Just to revive this issue, could you please provide a reproducer, starting with a 3.3 standard edition?

ping @teohhanhui

I am going to close here for now due to the lack of feedback. Please let us know when you have more information and we can consider to reopen.