AirbyteTracedException while customizing parse_response_error_message

Connector Questions & Issues
1

we built a custom http api source connector using python.while trying to customise parse_response_error_message function for handling failed request we are getting the following error :-
raise TypeError(\nTypeError: The view function did not return a valid response. The return type must be a string, dict, list, tuple with headers or status, Response instance, or WSGI callable, but it was a AirbyteTracedException.
our response content is a string “Supplier: A supplier with the value Cementsssssssss already exists. You must provide a unique value. (POZ-2130307)”.
Code snippet

def parse_response_error_message(cls, response: requests.Response) -> Optional[str]:

 try:

            x = {"Error": response.text}
            # convert into JSON:
            y = json.dumps(x)

            return y
except requests.exceptions.JSONDecodeError:
            return None

Based on above error message can you please guide as we want to resolve the issue and customise the messages in case of failures.

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hello Pravesh sahu, it’s been a while without an update from us. Are you still having problems or did you find a solution?

4

Still having problems on this part

5

It looks like you are trying to return a JSON-formatted string, so one solution could be to update the return statement to return the response.text directly instead of wrapping it in a dictionary and then converting it to JSON.

Try updating your function as follows:

def parse_response_error_message(cls, response: requests.Response) -> Optional[str]: try: return response.text except requests.exceptions.JSONDecodeError: return None

By returning the response.text directly, the function should return a string which is a valid response and should resolve the error you are encountering.

6

could you elaborate more about this not able do get.

7

Hey Pravesh, sorry for the delay in response here.

Are you not able to return the response.text? What does your current parse_response_error function look like now?