1. 15 Jan, 2014 1 commit
  2. 14 Jan, 2014 1 commit
  3. 07 Jan, 2014 1 commit
  4. 05 Dec, 2013 1 commit
  5. 08 Nov, 2013 1 commit
  6. 01 Nov, 2013 1 commit
    • Remove label from forum posts by global staff · c4cdb457
      The motivation for this change is performance. The forums UI code gets
      the list of users for each role and renders the staff label based on
      those lists. The list for the staff role is expensive to compute because
      there is no index on the is_staff attribute, and we cannot create one
      because the User model is built into django.
      
      Users with is_staff=True are still assigned the Moderator role upon
      enrolling in a course, so this change will have no practical effect
      except that a user who is granted staff privileges after enrolling in a
      course will have to be made a Moderator in order for their posts to be
      labeled.
      
      Additionally, the UI did not use the list of users with the Student
      role, so that list has been removed as well.
      Greg Price committed
  7. 28 Oct, 2013 4 commits
    • Improve performance of forum views · e6ecb6ec
      Avoid recomputing course module information for every thread, which
      should dramatically improve the performance of high-percentile latency
      queries.
      
      JIRA: FOR-250
      Greg Price committed
    • Remove an unnecessary global · a7d769df
      The _DISCUSSIONINFO global was originally used as a cache, but has since
      lost that capability and is therefore just harmful. This is a precursor
      to more refactoring that will improve the performance of the forums and
      may itself provide some performance improvement because it separates the
      computation done by two functions that each previously computed the
      entirety of _DISCUSSIONINFO.
      Greg Price committed
    • Add forum utility code unit test coverage · 545701d5
      This is in preparation for significant refactoring of the code in
      question.
      Greg Price committed
    • Improve forum error handling · 7abaecd8
      CommentClientError now has sane subclasses that are meaningfully
      distinct, and each subclass is handled appropriately. Errors raised by
      the requests library are no longer handled by turning them into
      CommentClientErrors, since there is no meaningful handling we can do,
      and this way we will get more visibility into why errors are occurring.
      Also, HTTP status codes from the comments service indicating client
      error are correctly passed through to the client.
      Greg Price committed
  8. 11 Oct, 2013 1 commit
    • Use HTTP header for comments service auth · 62cc9e77
      Previously, authentication was done using a URL parameter, which would
      appear in various logs. Now, authentication is done more appropriately
      with an HTTP header. Note that this requires cs_comments_service commit
      cf39aabdd160176ebf206ca19d3ee030161a0b47 or later.
      Greg Price committed
  9. 10 Oct, 2013 1 commit
  10. 23 Aug, 2013 2 commits
  11. 19 Jun, 2013 1 commit
  12. 20 May, 2013 1 commit
  13. 16 May, 2013 5 commits
  14. 06 May, 2013 2 commits
  15. 26 Apr, 2013 1 commit
  16. 22 Apr, 2013 1 commit
  17. 18 Apr, 2013 1 commit
  18. 11 Apr, 2013 2 commits
  19. 27 Mar, 2013 1 commit
  20. 20 Mar, 2013 2 commits
  21. 06 Mar, 2013 2 commits
  22. 06 Feb, 2013 1 commit
  23. 05 Feb, 2013 2 commits
  24. 29 Jan, 2013 4 commits