1. 16 Apr, 2021 1 commit
  2. 15 Apr, 2021 1 commit
  3. 12 Apr, 2021 1 commit
    • Jeffrey I. Schiller's avatar
      Add hostname to buildserver/vars · e97f1470
      Jeffrey I. Schiller authored
      We run 9-15 buildservers simultaneously and have a status page that
      reports the /buildserver/vars foreach server. However it is hard to know
      which status is for which buildserver. So we add the buildserver
      hostname here.
      
      Change-Id: I46fc59626cccf668ab57a5f81581273f0358fd1e
      e97f1470
  4. 07 Apr, 2021 1 commit
  5. 22 Mar, 2021 1 commit
  6. 17 Mar, 2021 1 commit
  7. 16 Mar, 2021 3 commits
  8. 07 Mar, 2021 1 commit
    • Jeffrey I. Schiller's avatar
      Mitigate Chrome 89 change · b4557d64
      Jeffrey I. Schiller authored
      Chrome 89 implements RFC8285 by default. It implements a general
      mechanism for RTP header extensions. We do not use these....
      
      Unfortunately the WebRTC library we are using in the Companion does not
      understand the extension request in the WebRTC offer message and refuses
      the offer completely, resulting in WebRTC not working from Chrome
      89 (and presumably onward).
      
      This change removes the extension from the offer prior to sending it to
      the Companion, so WebRTC works again.
      
      We believe this is harmless, because we do not use audio or video over
      WebRTC and this extension has no impact on the data channel (which we do
      use).
      
      Change-Id: I68f4ebaa2099ca0b4bbc7b1abd0a565dbde1f4e6
      b4557d64
  9. 01 Mar, 2021 2 commits
  10. 27 Feb, 2021 1 commit
  11. 22 Feb, 2021 1 commit
  12. 01 Feb, 2021 3 commits
  13. 27 Jan, 2021 1 commit
  14. 26 Jan, 2021 1 commit
  15. 20 Jan, 2021 7 commits
  16. 13 Jan, 2021 1 commit
  17. 12 Jan, 2021 1 commit
  18. 05 Jan, 2021 1 commit
  19. 16 Dec, 2020 1 commit
  20. 04 Dec, 2020 1 commit
  21. 01 Dec, 2020 6 commits
  22. 30 Nov, 2020 1 commit
  23. 22 Nov, 2020 1 commit
    • Jeffrey I. Schiller's avatar
      Add Gallery Readonly Flag · b77b2a5d
      Jeffrey I. Schiller authored
      When set we do not display the “Send to Gallery” Button, only the “Login
      to Gallery” button. The Gallery itself enforces read only status, so if
      the button is enabled but the gallery is in read only (for this
      instance) then the user will receive an error when they attempt to send
      a project to the gallery. But it is better if we can just avoid the
      issue by not providing the button in the first place.
      
      Another implementation here could be to have the server side actually
      check in with the gallery itself to determine read-only status, but for
      now we provide it as a config flag so we do not have to work out the
      details of how and when the server would communicate with the Gallery as
      well as how to handle errors and time-outs etc.
      
      Change-Id: Ib6ca63ab2ca63636d7451762f782050dbffd9b3c
      b77b2a5d
  24. 17 Nov, 2020 1 commit
    • Jeffrey I. Schiller's avatar
      De-bounce the Publish to Gallery button · da2e2cbb
      Jeffrey I. Schiller authored
      Some people were double-clicking this button which results in two copies
      of the project being sent to the Gallery simultaneously. This results in
      two entries for the project appearing in the Gallery. Then when the
      author next goes to update it, the Gallery finds two copies and fails.
      
      We will be adding a uniqueness constraint to the Gallery database which
      will prevent this. However this will result in one of the two
      transactions failing. Depending on the exact timing of things this can
      still result in the end-user receiving an error.
      
      This change “de-bounces” the Publish button so while one button push is
      still being processed, a second is ignored silently.
      
      Change-Id: Idd7506773b5e2a27500250d82a1350602b634a77
      da2e2cbb