BigW Consortium Gitlab

  1. 23 Nov, 2017 3 commits
  2. 22 Nov, 2017 1 commit
  3. 21 Nov, 2017 2 commits
  4. 20 Nov, 2017 2 commits
  5. 17 Nov, 2017 5 commits
  6. 16 Nov, 2017 1 commit
  7. 06 Nov, 2017 3 commits
  8. 03 Nov, 2017 1 commit
  9. 02 Nov, 2017 4 commits
  10. 01 Nov, 2017 1 commit
  11. 23 Oct, 2017 1 commit
  12. 17 Oct, 2017 1 commit
  13. 16 Oct, 2017 1 commit
    • Make usage ping scheduling more robust · f4e94c6f
      Sean McGivern authored
      On GitLab.com, we see that cron jobs sometimes don't run. This appears to be
      because the process that polls for current cron jobs only has a 60 second
      validity period, so if (for whatever reason) it misses those 60 seconds, we have
      to wait until the next execution.
      
      For the usage ping, this is particularly problematic, as that's only scheduled
      to run once a week.
      
      Changing it to run for every minute in a 10 minute period should work around
      this, if the above diagnosis is correct. The job itself obtains an exclusive
      lease for 24 hours, so rescheduling in quick succession is safe.
  14. 05 Oct, 2017 1 commit
  15. 04 Oct, 2017 2 commits
  16. 03 Oct, 2017 2 commits
  17. 02 Oct, 2017 1 commit
  18. 30 Sep, 2017 1 commit
    • Add `:email_confirmation` to devise `insensitive_keys` · c82678ca
      robdel12 authored
      This fixes a bug where the email confirmation input value is case
      sensative. For example, if the email input is `myemail@example.com` and
      the email confirmation input is `Myemail@example.com` the form would
      fail to submit.
  19. 24 Sep, 2017 2 commits
  20. 20 Sep, 2017 1 commit
  21. 19 Sep, 2017 2 commits
  22. 18 Sep, 2017 1 commit
  23. 15 Sep, 2017 1 commit