Add open-telemetry/sdk and open-telemetry/exporter-otlp as dev dependencies

Added additional dependencies that are pulled in by opentelemetry to the issue summary, but haven't done the evaluations for those yet.

Had no idea the dictionary scanned composer files..

Added additional dependency evaluations for the dependencies of the dependency.

The last submitted patch, 8: 3352389-6.patch, failed testing. View results →

Should fix both test failures.

Feel like this may be a dumb question but since this is a dev dependency is there any harm in using the beta tag of https://github.com/opentelemetry-php/exporter-otlp ?

Looking at the release notes in https://github.com/opentelemetry-php/exporter-otlp/releases/tag/1.0.0beta5, I like the suggestion of moving to the beta tag. And we should work on getting the pecl extension added to the test runner One thing I've noticed from running this locally is that it feels like the instrumentation seems to add lot of overhead. The release notes seem to bear that out. But switching to the C library should help.

Re-rolled and updated to beta.

Need reroll

Re-rolled.

For the CC.

Added to the dictionary.

I was a little concerned about the implications of php-http/guzzle7-adapter, but it seems to be fairly well maintained and someday might not even be needed as it appears to be a shim. +1 on these dev-dependency changes.

The last submitted patch, 21: 3352389.patch, failed testing. View results →

Fixing the metapackage.

The last submitted patch, 24: 3352389.patch, failed testing. View results →

Would be great to explore upcoming compatibility with PHP 8.3, ATM https://pecl.php.net/package/opentelemetry works fine

HEAD was broken, resetting status.

I haven't yet tried the opentelemetry pecl package, but yeah it might be useful, although we'd need to add it to drupalci/gitlabci environments to be able to use it.

All green!

Think a follow up should be opened for #26 too.

Opened 🌱 [PP-1] consider using the OpenTelemetry pecl package for core performance instrumentation Active .

I keep opening this one and hemming and hawing over it; but at the end of the day it's only a set of dev dependencies and we can just as easily remove them again, and now 10.1.0 is out the door I feel more confident in getting this into 10.2.0 early.

Committed and pushed faef0c760d to 11.x (10.2.x). Thanks!

I had no idea this was happening! 🤩🤯

Exciting to see where this goes next!

This broke subtree splits due to allow-plugins, I'll make a patch.

Maybe this.

Fix looks correct to me, same issue as #3294205: [Packaging broken!] Composer v2.2 prompts to authorize another plugin when stability=dev →

@catch also opened 📌 Write a test to ensure that composer plugins match in composer templates Active to prevent this happening again.

Committed #34.

Automatically closed - issue fixed for 2 weeks with no activity.