1. 14 Jun, 2021 1 commit
  2. 07 Jun, 2021 1 commit
  3. 02 Jun, 2021 2 commits
  4. 24 May, 2021 2 commits
  5. 21 May, 2021 1 commit
  6. 20 May, 2021 1 commit
    • Arlo Breault's avatar
      Remove sync.Once from around logMetrics · 7ef49272
      Arlo Breault authored
      Follow up to 160ae2dd
      
      Analysis by @dcf,
      
      > I don't think the sync.Once around logMetrics is necessary anymore.
      Its original purpose was to inhibit logging on later file handles of
      metrics.log, if there were more than one opened. See 171c55a9 and #29734
      (comment 2593039) "Making a singleton *Metrics variable causes problems
      with how Convey does tests. It shouldn't be called more than once, but
      for now I'm using sync.Once on the logging at least so it's explicit."
      Commit ba4fe1a7 changed it so that metrics.log is opened in main, used
      to create a *log.Logger, and that same instance of *log.Logger is passed
      to both NewMetrics and NewBrokerContext. It's safe to share the same
      *log.Logger across multiple BrokerContext.
      7ef49272
  7. 19 May, 2021 1 commit
    • Arlo Breault's avatar
      Make promMetrics not a global · 160ae2dd
      Arlo Breault authored
      Doesn't seem like it needs to exist outside of the metrics struct.
      
      Also, the call to logMetrics is moved to the constructor.  A metrics
      instance is only created when a BrokerContext is created, which only
      happens at startup.  The sync of only doing that once is left for
      documentation purposes, since it doesn't hurt, but also seems redundant.
      160ae2dd
  8. 12 May, 2021 4 commits
  9. 26 Apr, 2021 3 commits
  10. 22 Apr, 2021 1 commit
  11. 01 Apr, 2021 1 commit
  12. 25 Mar, 2021 1 commit
  13. 19 Mar, 2021 3 commits
  14. 06 Mar, 2021 1 commit
  15. 02 Feb, 2021 1 commit
  16. 25 Jan, 2021 2 commits
  17. 12 Jan, 2021 1 commit
  18. 17 Dec, 2020 1 commit
  19. 16 Dec, 2020 1 commit
  20. 05 Dec, 2020 3 commits
  21. 04 Dec, 2020 1 commit
    • Cecylia Bocovich's avatar
      Create new smux session for each SOCKS connection · 114df695
      Cecylia Bocovich authored
      Each SOCKS connection has its own set of snowflakes and broker poll
      loop. Since the session manager was tied to a single set of snowflakes,
      this resulted in a bug where RedialPacketConn would sometimes try to
      pull snowflakes from a previously melted pool. The fix is to maintain
      separate smux sessions for each SOCKS connection, tied to its own
      snowflake pool.
      114df695
  22. 27 Nov, 2020 1 commit
  23. 23 Nov, 2020 1 commit
    • Cecylia Bocovich's avatar
      Remove for loop around broker.Negotiate · 665d76c5
      Cecylia Bocovich authored
      Instead of continuously polling the broker until the client receives a
      snowflake, fail back to the Connect() loop and try again to collect more
      peers after ReconnectTimeout.
      665d76c5
  24. 20 Nov, 2020 2 commits
  25. 18 Nov, 2020 2 commits
  26. 06 Nov, 2020 1 commit