Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[ BUG ] Legacy Uber Class is not logging operation IDs #1057

Closed
jshcodes opened this issue Oct 21, 2023 · 0 comments · Fixed by #1062
Closed

[ BUG ] Legacy Uber Class is not logging operation IDs #1057

jshcodes opened this issue Oct 21, 2023 · 0 comments · Fixed by #1062
Assignees
@jshcodes
Labels
bug 🐛 Something isn't working SDK usage General SDK usage issues and questions

Comments

@jshcodes
Copy link
Member

Describe the bug
When leveraging Debug Logging within the legacy version of the Uber Class (APIHarness), the operation ID is not being logged.

To Reproduce
Construct an instance of the legacy Uber class with debugging enabled. Call any operation. Payloads and responses are reported, but the operation ID is not.

Expected behavior
Operation ID should be logged in the legacy Uber class exactly as it is logged within the new Uber Class (and Service Classes).

Environment (please complete the following information):

  • OS: All Supported
  • Python: All Supported
  • FalconPy: v1.3.0 - v1.3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jshcodes jshcodes

Labels
bug 🐛 Something isn't working SDK usage General SDK usage issues and questions
Projects
None yet
Milestone
No milestone
1 participant
@jshcodes