ByteCode.NewsSubmit
Use quotes for an exact word.

Subscribe

RSSPodcast
Log in

Chat Logs

  1. * skillbot quit (Remote host closed the connection)
  2. * skillnews quit (Remote host closed the connection)
  3. * skillnews joined #primate
  4. * skillbot joined #primate
  5. bluecool, jreicher
  6. bluedreamreal: the two primate bugs posted, would you be comfortable waiting for 0.43, or do they necessitate a 0.42 backport?
  7. blueI'm agnostic, so up to you
  8. blueactually I'm slightly gnostic there: I do prefer not having to deal with pnpm by means of a backport, but it's not a blocker for me
  9. dreamrealI've got workarounds, feel free to wait
  10. dreamrealnot a rush, just filed the issues so you'd know
  11. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  12. * nevet joined #primate
  13. dreamrealblue: I've got a spin-up process for nevet, going to try it on our private network later today
  14. dreamrealmoving to the full dockerized install kinda made that a little difficult thanks to using the console for initial configuration, but the pudl UI provides a console *endpoint* so I can use that
  15. bluenice, dreamreal
  16. dreamrealblue: I'm going to try to spin it up under the name "gholem" :D
  17. dreamrealit's basically going to be the gitlab watcher for mattermost
  18. bluedreamreal: you know, I'm gonna need someone to battletest repopack, just saying :P
  19. dreamrealThis is part of getting close to that, this is all initialization stuff, like "how the heck DO you run this now?"
  20. bluetrue. also consider that repopack both manages the repo (via tasks etc.) *and* deploys it. the change can be gradual
  21. bluebut I'm gonna hold off recommending a move until it gets release primitives
  22. blueI must be content with it myself
  23. bluethere is no way around that
  24. dreamrealWell, streampack requires intervention on configuration, unfortunately, so the spin-up isn't trivial
  25. blueintervention on configuration?
  26. dreamrealIt's getting there: right now it's a bunch of y/n questions with only a few details like email addresses and server names/ports
  27. blueright
  28. bluebtw, dreamreal, what honestly scares me, is that repopack has been moved to the new ai-based idea for a month, and I'm already at task 670. that's an incredible turnaround
  29. blueI'm a bit reserved of optimising it too much, myself, because my pro 100 would run out like nothing :/
  30. bluebut it will be necessary, again, no way around it
  31. blueI can't be going around with like 5 tmux sessions and countless opencode windows, it gets more and more confusing
  32. dreamrealyeah, it's fast, it's potentially expensive, but it highlights the value of ideation
  33. blueit's *too* fast
  34. dreamrealIs it?
  35. dreamrealI mean, it might be outracing your funding, but...
  36. dreamrealI'm fixing search now - i was searching for "emergent" but got "emerges" instead because of the stemming, and I didn't have a good way to clarify the matching :D
  37. blueI told you, my current pace drains pro 100 in roughly 1.2d, accounting for a normal sleep/work cycle. pro 100 runs for 7d. the resets, on which it is dangerous to rely, cut it to roughly 3.5d on average. pro 200 is doubled; at my *current* pace, I would be nearly exhausting pro 200 every single time. any boost on that pace is potentially fatal
  38. bluesorry, pro 200 is quadrupled*
  39. blueand I'm already economical. most work is done by sol 5.6; sol 6 only does reviews; sol 6.1 is rarely used at all
  40. dreamrealI hear you. But note that sol is not always necessary.
  41. bluetell that to me who tried to reason with terra and got "continuing with this" every single time, necessitating me babysitting it every 5 minutes with "continue"
  42. dreamrealheh
  43. bluethe problem as I see it, is that repopack is going to minimise overhead and maximise agent runtime, which is going to be highly effective and potentially burn through limits to no end
  44. bluewhich yes, leaves more for ideation, which is good, but also means you need more power
  45. blueand yes, I remember your search tokenises, which kinda amazed me, I thought you did ai
  46. bluebut it predates I believe
  47. blueor was consciously chosen conservatively
  48. bluepredates ai*
  49. dreamrealthe libraries I was using use stemming, it's heuristic, no AI
  50. dreamrealin fact, search doesn't use AI *at all* although !define now has a fallback to AI if the dictionary services fail
  51. blue*nod*
  52. blueI'm currently toying with the idea of repopacking reducing test time for offering optimise containers
  53. bluea lot of the test time primate has is spent of spinning postgres and oracle containers and what not
  54. bluespent on*
  55. dreamreal*nod*
  56. dreamrealsqlite, buddy! *grin*
  57. dreamrealI despise sqlite
  58. dreamrealthat was a funny
  59. blueyes, well, *all* adapters need testing
  60. dreamrealincidentally, the streampack bot on our private network is going to be called 'gholem' :D
  61. blueprivate network?
  62. dreamrealYeah, I have an internal network for work, not visible externally
  63. bluefair enough
  64. blueI have decided flog won't also have runtime capabilities, I won't make everything out of it, like bun. it'll remain mostly a package *manager*
  65. bluethe runtime will be another tool
  66. bluedreamreal: btw, nevet is so nice. it's offering everything I need from a bot currently
  67. dreamrealheh, I'm glad to hear that :D
  68. dreamrealI'm adding external entrypoints now, so you can overrride the banner and add external jars without having to build them into the system
  69. dreamrealso THEORETICALLY you could have your OWN module, on ts own repo, drop it into a directory, and have streampack pick it up
  70. blueawesome
  71. bluedreamreal: every task I solve, I can three new ones. this is BRUTAL
  72. blueI create*
  73. dreamrealYes, it's almost like development. And this is how development ALWAYS went, but the machines can wear blinders a lot less well than humans can. As humans we say "I'll fix that when I need to!" and we shim in functionality, but the machine's going "you said to do it, not fake it..."
  74. blueyup
  75. * nevet joined #primate
  76. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  77. * nevet joined #primate
  78. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  79. * nevet joined #primate
  80. * blue!~blue@user/blue changed the topic to: https://primate.run | this channel is publicly logged at https://bytecode.news/logs/irc/libera/primate and mirrored to Primate discord, channel #irc
  81. dreamrealokay, search is fixed!
  82. bluenice
  83. dreamrealAND - this will be good for repopack - I have extensions exposed outside the docker image, so a repopack service/operation doesn't have to be part of the main build any more
  84. dreamrealThere's no reason they couldn't be part of the main build but the main build's pretty giant already, and it's grown way past what it should be
  85. dreamrealnew modules should be really rare now
  86. dreamrealand I may move some of the modules *out* - like hangman, 21, etc., a lot of those really aren't core, they just were part of the core to prove out features and stuck around
  87. * phaleth joined #primate
  88. bluehi phaleth
  89. bluedreamreal: WOW!
  90. blueamazing
  91. phalethhi blue
  92. bluephaleth: btw https://repopack.com/project/repopack/jobs/1
  93. blue272 jobs x 7mb x 4 -> 7.6 gb
  94. bluehence -> https://repopack.com/project/repopack/tasks/674?tasks=status%3Dopen
  95. * skillnews quit (Remote host closed the connection)
  96. * skillbot quit (Remote host closed the connection)
  97. * skillbot joined #primate
  98. * skillnews joined #primate
  99. phalethyeah, I was wondering if those artifacts get cleaned up
  100. phaleththe goal is to be able to rebuild them, not to store them indefinitely
  101. blue674 will clean up old jobs
  102. bluewith a retention policy
  103. blueprobably "keep last x jobs", or, "remove jobs older than 30 days", or both
  104. phalethok
  105. blueI think last 10 or 20 jobs, and remove anything older than 30 days, is ok
  106. bluewe will also introduce a storage limit for free accounts
  107. bluemaybe 1gb or less
  108. bluepaying accounts can be get more
  109. bluecan get*
  110. phaleth256 MB
  111. bluestorage, not RAM
  112. blueor did oyu mean storage?
  113. phalethyeah, storage
  114. bluebut we currently have 130gb available on this vps. if it's 1gb, it would be up to 130 accounts
  115. phalethand also single container app with max 256 MB RAM
  116. blueif 256, up to 520
  117. bluewell we gotta also limit the number of apps per account
  118. blueand also the number of concurrently running jobs
  119. phalethjust give them a way to clear artifacts
  120. phalethvia cli
  121. phaleth256 MB is alot
  122. bluenah, should be automatic. the only thing that we need is a whitelist, to freeze builds that you need to keep
  123. blueI mean we can let people delete jobs. I'm not sure runs, but jobs you can delete and it deletes all runs + their artifacts
  124. bluebut letting people deleting runs sounds like wasting time on bookkeeping
  125. phalethyeah, but it's better to have both, maybe somebody will build a lot of crap and then realize they have to wait a month for it to be cleaned
  126. bluedelete*
  127. bluefair enough. but remember, that also means they could instead of clogging the cpu
  128. blues/of/be/
  129. bluelike then you can script it 24/7, build -> delete -> build -> delete
  130. bluethat's a form of abuse as well
  131. phalethwait, the builds should happen in podman containers with resource limits
  132. blueyes
  133. phalethincluding CPU limits
  134. bluethat's already the case now
  135. bluebut CPU limits should be measure across an entire account, monthly
  136. blueand you don't want someone to waste all his CPU time on the first day
  137. blueanyway, I think that's a product decision that we can discuss later
  138. bluebut free accounts will need to be limited
  139. phalethand for build the container should take max 2 GB RAM, cause if anybody tries to build some rust crap they should not be able to
  140. blueyes
  141. bluewell if you're a paying customer, you can build rust, why not
  142. blueyou can also build v8, which is a waste of time and takes forever, but who cares if you're paying for it
  143. phalethyeah
  144. blueI think that also, if we have people like dreamreal, who to my knowledge doesn't pay for gh actions atm, we should try to keep under the free tier, otherwise people won't switch
  145. bluethe idea of the free tier is a bit that you lose money on those users, but also you draw them in
  146. blueso once they see how great the service is, they can pay for cases where they generate money, so it's a trickle down effect
  147. bluethe worst cases are that the customer doesn't generate income, but needs to pay, in those cases they might switch back to gh
  148. blueor aws or google
  149. phalethyou need different kind of accounts, but those 256 MB RAM I meant for randoms
  150. blueyes
  151. phalethyou can offer people perks
  152. bluethat's something we need to get into place before launch, definitely
  153. bluebut also need more servers, anyway. preferably dedi
  154. phalethmaking it a game is a good idea
  155. blueI'd like to start with around 100 euro worth of dedi/vps servers a month, I think that's a good start in terms of offered powered
  156. phalethdedis are too expensive, we should be fine with VPSes
  157. blueyeah, whatever's the best
  158. blue10-20 vps should be also fine by me
  159. phalethall what I'm trying to do is to avoid dedis
  160. bluefair
  161. blueI don't mind just doing a lot of vps
  162. phalethyeah, the question is when can repopack orchestrate
  163. phalethand when the current tasks are done
  164. bluein the future
  165. bluerepopack can already do a lot. in fact more than I ever wanted fly to be able to do for primate
  166. phalethI hope flog is complete and repopack can use flog
  167. blueshould be, yes. there's a benchmark task open, I can show you in a bit
  168. phaleththat just means more optimizations and they are a waste of time at certain point
  169. phalethI've filed a bug against flog today
  170. blueI can see it, will do
  171. phalethand also the trust me bro script still does not work
  172. bluethat's by design
  173. phalethand then you should consider having releases also for windows and that's it
  174. blueI told you, flog needs release primitives
  175. bluerepopack doesn't have them yet
  176. phalethI think that will require a powershell trust me bro script
  177. bluepossibly, yes
  178. phalethyeah, I know, so those release primitives, whatever task on repopack that is are the blocker for flog
  179. blueyes
  180. phalethcause flog is a way to get people engaged
  181. blueI know
  182. phalethkinda like primate
  183. blueand that is also a blocker for primate 0.43
  184. bluea chain of blockers, so to speak
  185. blueto my knowledge dreamreal also needs release primitives
  186. blueI think we should have them this week, god willing
  187. phalethok, how much clanker time is left?
  188. blueit refreshed earlier today.. let me see
  189. blue54%
  190. bluephaleth: https://repopack.com/project/flog/jobs/2?run=3
  191. blueclick View on summary.md :P
  192. phalethyeah, looks great, but I've tried this one earlier and it's not working correctly https://repopack.com/project/flog/jobs/1?run=47 I was getting missing tsc error
  193. phalethnot sure if that's related
  194. bluemaybe you can report
  195. bluethe roblem
  196. phalethbut that job looks weird, is that one already on master?
  197. blueno, that job is being run manually by clanker
  198. blueI will switch to `trigger:master` when the task is merged
  199. phalethwhich task?
  200. blue68/69
  201. bluetechnically this job should serve as a review gate. but we don't have the ability to make jobs a review gate, yet
  202. phalethnot sure how clanker was able to trigger job 47 from a task
  203. phalethI'll add note to flog#69
  204. phalethnow it will not know how I got the primate.tar.gz :)
  205. * phaleth quit (Quit: phaleth)
  206. bluedreamreal: https://repopack.com/project/primate/tasks/216
  207. bluefeedback please