fix: update Supabase token retrieval to remove unnecessary await

[suysoftware]

The get_user method in the SDK is defined as a regular def function, not an async def. For this reason, trying to call it with await results in a TypeError: object is not awaitable error.

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 1b44f15 in 1 minute and 12 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. py/core/providers/auth/supabase.py:77

• Draft comment:
  Inconsistent handling of get_user: decode_token now calls it synchronously, while user() still awaits it. Verify if get_user is sync; if so, update both places for consistency.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_yysxCF2JQorTcrH2

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Ensure consistency in using await for get_user. Other methods (e.g., user()) await this call, so confirm if get_user is sync. If it’s async, removing await is a bug.

Suggested change

	auth_response = self.supabase.auth.get_user(token)
	auth_response = await self.supabase.auth.get_user(token)

[NolanTrem]

@suysoftware can you confirm if this is a valid comment? Just want to verify that everything is working for you and then I will merge. Thanks!