Fix missing activity data sync after first login#56
Open
diksha78dev wants to merge 1 commit into
Open
Conversation
|
@diksha78dev is attempting to deploy a commit to the clutch Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes the "No activity data yet" error that occurs when a new user runs insights commands immediately after logging in. The GitHub activity sync is now automatically triggered via a non-blocking background task upon first login, ensuring a seamless onboarding experience.
Related Issue
Closes #20
Type of Change
Changes Made
background_sync_githubhelper tobackend/app/routers/auth.pyBackgroundTasksto thegithub_callbackrouteuser.last_synced_atis emptyScreenshots / Terminal Output
N/A (Backend behavior change)
Checklist
CONTRIBUTING.mdand followed the assignment rules for this issue's labeldevelopNotes for Reviewer
The background task instantiates its own
SessionLocalto prevent SQLAlchemy session lifecycle conflicts since the main HTTP request context is closed by the time the background task executes.