1. 06 Jul, 2017 5 commits
  2. 29 Jun, 2017 1 commit
  3. 28 Jun, 2017 2 commits
  4. 26 Jun, 2017 4 commits
  5. 16 Jun, 2017 2 commits
  6. 08 Jun, 2017 1 commit
  7. 07 Jun, 2017 3 commits
  8. 06 Jun, 2017 1 commit
  9. 02 Jun, 2017 5 commits
  10. 01 Jun, 2017 2 commits
  11. 31 May, 2017 2 commits
  12. 30 May, 2017 4 commits
    • Leigh Stoller's avatar
      When the error is for a hidden form field, show that in the general · d0ee85be
      Leigh Stoller authored
      error location. This closes issue #292.
      d0ee85be
    • Leigh Stoller's avatar
      Rework how we store the sliver/slice status from the clusters: · e5d36e0d
      Leigh Stoller authored
      In the beginning, the number and size of experiments was small, and so
      storing the entire slice/sliver status blob as json in the web task was
      fine, even though we had to lock tables to prevent races between the
      event updates and the local polling.
      
      But lately the size of those json blobs is getting huge and the lock is
      bogging things down, including not being able to keep up with the number
      of events coming from all the clusters, we get really far behind.
      
      So I have moved the status blobs out of the per-instance web task and
      into new tables, once per slice and one per node (sliver). This keeps
      the blobs very small and thus the lock time very small. So now we can
      keep up with the event stream.
      
      If we grow big enough that this problem comes big enough, we can switch
      to innodb for the per-sliver table and do row locking instead of table
      locking, but I do not think that will happen
      e5d36e0d
    • Leigh Stoller's avatar
      Minor bug fix. · 8b2ddede
      Leigh Stoller authored
      8b2ddede
    • Leigh Stoller's avatar
      91f41f7c
  13. 23 May, 2017 2 commits
  14. 22 May, 2017 2 commits
  15. 18 May, 2017 3 commits
  16. 17 May, 2017 1 commit