PGRST104 error on deployment

[asontha]

Describe the bug
Seems to be working locally but when I deploy to fly.io using heroku container, running into the following error:

postgrest.exceptions.APIError: {'code': 'PGRST104', 'details': 'Failed to parse [("channel_id","Filters.EQ.<CHANNEL ID>")]', 'hint': None, 'message': 'Unexpected param or filter missing operator'}

this is the query I'm running:

namespace_query = supabase.table("channel-configuration").select("*").eq("channel_id", channel_id).execute()

Again this query is running fine locally.

Expected behavior
Runs query normally against DB table and returns the expected result.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MacOS 12.5

[asontha]

Figured it out. There seems to be an issue with using this supabase client with Python 3.11. I was able to fix this by setting my heroku deployment's python version to my local version which is 3.10.9

[J0]

Hey @asontha,

Do you mind letting us know what version of Supabase-py you are on?

[asontha]

supabase==1.0.0

[GaryAustin1]

I'm dropping this here as it seems related to this Python version change. It involves the PGRST104 error on a filter. I asked the OP to post here, but has not yet late in my day. Might help narrow down what is going on.

https://discord.com/channels/839993398554656828/1076162465638916116

[J0]

Gotcha,

thanks @asontha and @GaryAustin1 🙏

[asontha]

Any update here?

[anand2312]

The error message (saying "Filters.EQ.<CHANNEL ID>" where Filters.EQ is the name of the enum, which should be getting changed to just eq) and the Python version change fixing it makes me think it might be the switch to using StrEnum (new in Python 3.11) that is breaking here ; the fallback strenum library may not be working as expected. What do you think @J0 ?

[J0]

@anand2312 I've yet to test and probably won't have bandwidth to look into this till EoW - feel free to switch out the library if it's causing an error

[wellsilver]

bump

[J0]

Sorry, guess this slipped my mind. Transferring to postgrest-py