Sylvain L.

Thanks for the explanations. But IMO you'd better fork the whole library and make it a new composer dependency to avoid side effects of the current hack.

Yes you're right I've forgotten namespace conflict... Anyway, PR Imagine is the only viable solution. The current hack simply breaks box-dependent Imagine's features.

I cannot imagine why this is not fixed yet as this issue just makes impossible to specify an error for an invalid path (404) or method (405).

> you can reference responses, which is more or less what is being requested here: > > ```yaml > paths: > /my_endpoint: > get: > responses: > 404: > $ref:...

@mikkeschiren Why do you want SPX "trace" to be processed by monitoring / tracing tools such as zipkin or jaeger ? What use cases do you want to support with...

> I already have one converter from SPX full profile to FlameGraph and third-party profiling system for more flexible visualization and profile comparison. It's not so difficult to convert from...

There is already a discussion about pprof here https://github.com/NoiseByNorthwest/php-spx/discussions/179 In my understanding it could be a bit complex to support due to a dependency to protobuf. I may be wrong.

@AlexNDRmac I think that the ability to specify tags, described here https://github.com/NoiseByNorthwest/php-spx/issues/173#issuecomment-895512411 would cover that.

@morozov It seems to be in fact not (directly) related to the addition of `current_schemas(false)`. Here are the execution flow differences between 3.3.x & 3.4.x 3.3.x ``` AbstractSchemaManager::createSchema() AbstractSchemaManager::listTables() AbstractSchemaManager::listTableNames()...

This is a good idea, but there is some overlap with the "color by category" feature. Maybe this later feature can also be improved ? For instance to make the...