Chat Logs

  1. liolochello ๐Ÿ‘‹
  2. bluehey lioloc :)
  3. bluelioloc: 151 moved automatically to revision because it has conflicts with its parent task 161
  4. blueyou can see in the ui it says "conflicts", that's when the parent branch and the task branch conflict
  5. liolocok will see about those
  6. blueawesome
  7. bluelioloc you can also join #primate if you want
  8. lioloc๐Ÿ‘
  9. bluejust so we're transparent about it, the public logging by nevet for this channel is authorised by me (channel owner) until indicated otherwise
  10. bluehi phaleth
  11. phalethhi blue
  12. phalethso you rolled up your sleeves and did something about SSE manually, blue?
  13. phalethyeah, you've been working on repopack manually today
  14. blueya
  15. phalethheh
  16. bluephaleth: https://repopack.com/project/repopack/tasks/500
  17. nevetRepopack ยท Sign in
  18. bluethis is for server agent to analyse
  19. blueI mean, we're currently at 255M, but I want to understand where those mbs are going
  20. blueSSE can technically be outsource to a nice event bus like rabbitmq
  21. blueoutsourced*
  22. blueit needn't be handled in memory, specifically
  23. phalethcurrently there is already over 50k lines of TS
  24. phalethyeah, it's better to use some queue based store
  25. blueperhaps a good abstraction here is @primate/events
  26. bluewe'll see. rabbitmq can be a backing store
  27. blueor events remain in core, but we create compatible adapters like we do for db stuff, so @primate/rabbitmq and so on
  28. bluethis is something to solve before GE
  29. blueGA*
  30. phalethok, rabbitmq container should be easy to setup