Skip to content

Conversation

@kylesferrazza
Copy link
Collaborator

This may be convenient, but became a performance issue.
Registrations can still be synced via the red Sync button for the course.

This may be convenient, but became a performance issue.
Registrations can still be synced via the red `Sync` button for the
course.
@kylesferrazza kylesferrazza requested a review from blerner October 5, 2020 22:47
@blerner
Copy link
Contributor

blerner commented Oct 5, 2020

This is certainly the band-aid we need for now. But it looks like we can do better:

  • maybe sync if hg_course.registrations.empty?
  • we have a last_sync time -- could we get a timestamp from bottlenose of the most recent registration or withdrawal, and compare, and show a "Out of sync!" alert if bottlenose_time > last_sync?

@kylesferrazza
Copy link
Collaborator Author

  • sync if hg_course.registrations.empty?
  • we have a last_sync time -- could we get a timestamp from bottlenose of the most recent registration or withdrawal, and compare, and show a "Out of sync!" alert if bottlenose_time > last_sync?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants