maybe_single throws an error when 0 rows are returned

[levity]

Bug report

Describe the bug

maybe_single is supposed to return None when the query returns no rows. But now it throws an APIError:

postgrest.exceptions.APIError: {'message': 'Missing response', 'code': '204', 'hint': 'Please check traceback of the code', 'details': "Postgrest couldn't retrieve response, please check traceback of the code. Please create an issue in `supabase-community/postgrest-py` if needed."}

To Reproduce

Run any query that returns 0 rows, e.g:

postgrestClientInstance.from_('my_table').select('*').eq('content', 'nonexistent').maybe_single().execute()

Expected behavior

should return APIResponse(data=None) as in previous versions

System information

• supabase 2.3.0
• postgrest 0.13.0
• PostgreSQL 15.1 (Ubuntu 15.1-1.pgdg20.04+1) on aarch64-unknown-linux-gnu, compiled by gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, 64-bit

[levity]

perhaps #289 is a clue

[tushar-balwani]

@levity Thanks for reporting this issue. again there is change of error message in postgrest. as @J0 suggested in #289 we need a robust solution for repeating problem. I am happy to apply this temp fix again for now and also open for suggestions to how we can make it dynamic.