fix: update to support the open-telemetry status code spec change

[vi3k6i5]

fix: for open-telemetry status code spec change

Fixes #357 🦕

Open telemetry has changed their specs for status code. Since the open telemetry library for python is still in beta it doesn't make much sense to use/support older version of that library.

Couple of reference:

1. 'StatusCanonicalCode' is not part of 'opentelemetry.trace.status'
2. In memory exporter not resetting after test case ends

[larkee]

Is this compatible with older versions of OpenTelemetry?

Also, the py3.6 unit tests are failing.

[vi3k6i5]

Is this compatible with older versions of OpenTelemetry?

Don't think we should support any older versions of the library. As per the library doc the software is in Beta, and since they have changed their api, so not sure if we should support older versions?

Also, the py3.6 unit tests are failing.

Fixed the unit tests and system tests.

[larkee]

The emulator action is timing out while trying to resolve the dependencies. It seems to have an issue with opentelemetry-instrumentation == 0.22b0 in the constraints file. Using opentelemetry-instrumentation == 0.20b0 seems to resolve it but I don't know if this is a valid version..

[vi3k6i5]

The emulator action is timing out while trying to resolve the dependencies. It seems to have an issue with opentelemetry-instrumentation == 0.22b0 in the constraints file. Using opentelemetry-instrumentation == 0.20b0 seems to resolve it but I don't know if this is a valid version..

Thanks for the help, that fixed the issue. Thanks 👍

[snippet-bot]

No region tags are edited in this PR.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

• Refresh this comment