mirror of
https://github.com/Sea-Haven-Industries/open-swe.git
synced 2026-09-30 20:53:15 +00:00
5d033c7548
* fix: clearer Slack prompt for users who must sign in with GitHub The Slack gate labeled any mapped-but-tokenless user as having an "expired or revoked" authorization, keyed off whether a *mapping* row existed. Most blocked users are team members in the legacy hardcoded mapping who have simply never completed a dashboard GitHub login, so the message was misleading and steered them toward reconnecting Slack (which never creates a token). Base the prompt on whether an oauth_tokens *record* exists: - no record -> ask the user to sign in with GitHub and connect Slack - record but unusable -> ask the user to sign in with GitHub again Add has_access_token_record() to distinguish the two cases. * fix: guard token-record check so a store failure still prompts sign-in The has_access_token_record() lookup ran outside the defensive handling around token resolution. If the store read fails it would raise before posting the sign-in prompt and clearing the Slack assistant status. Wrap it like get_valid_access_token: on failure, default to the sign-in/connect prompt. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| admin.py | ||
| agent_overrides.py | ||
| analyzer_cron.py | ||
| enabled_repos.py | ||
| message_adapter.py | ||
| oauth.py | ||
| options.py | ||
| profiles.py | ||
| review_style_jobs.py | ||
| review_styles.py | ||
| routes.py | ||
| slack_oauth.py | ||
| team_settings.py | ||
| thread_api.py | ||
| user_mappings.py | ||