ByteCode.News
RSS
SubmitLog in

Community

Chat Logs

Sunday, March 22, 2026

  1. * phaleth joined #primate
  2. phalethtime to say farewell to the edge runtime https://images4.imagebam.com/95/eb/b9/ME1BIGIR_o.png it's memory consumption started at 137M over a day and half ago
  3. bluephaleth: lol
  4. bluephaleth: https://github.com/primate-run/primate/issues/262
  5. nevetProposal: Introduce `p.uuid()` as a first-class Pema type 路 Issue #262 路 primate-run/primate
  6. phalethI think mysql supports uuids and turns them into 16 byte long binaries
  7. phalethwhich it can then easily compare and so use as primary keys
  8. phalethnot sure why it's a 12-byte length for MongoDB, sounds odd
  9. phalethah, it's not UUID, it's some mongo objectid thing
  10. phalethin any case, having database compare strings/texts is a horrible idea
  11. phalethand also ordered is always much much better, that's already there in the proposal
  12. blueyes, phaleth
  13. bluethis mostly closes a gap I've been annoyed with for a while
  14. blueand mongo ObjectId is some proprietary nonsense, but it's the most effective way to do primary indexing in mongo
  15. blueI'm incling to say that p.uuid (datatype: "uuid") will map to that, while the bespoke types "uuid_v4" and "uuid_v7" will use uuids,which mongo db cannot effectively index, so perhaps we'll add a warning for that in the mongodb driver
  16. blue"uuid" as a datatype should mean, "use the best UUID approximation you have". sqlite doesn't have one, it's just TEXT. so it's logical that for mongodb, that would be ObjectId.
  17. bluephaleth: do you mean this?
  18. bluehttps://dev.mysql.com/doc/refman/8.4/en/miscellaneous-functions.html#function_uuid-to-bin
  19. phalethyeah, if uuid is used as primary key, mysql and all the other dbs that support uuids should automatically sort records by that primary key after insertion
  20. phalethI guess then for mongodb you will have to make an exception
  21. phalethbut overall the idea sounds good
  22. bluephaleth: https://github.com/primate-run/primate/issues/262#issuecomment-4106146943
  23. nevetProposal: Introduce `p.uuid()` as a first-class Pema type 路 Issue #262 路 primate-run/primate
  24. bluethat's a follow-up with your mysql idea
  25. blueclanker also ack'd, so looks good
  26. bluephaleth: can I restart the vps? arch has linux 6.19 out
  27. phalethyeah, sure
  28. phalethbye bye blue
  29. * blue joined #primate
  30. bluephaleth: well, it's restarted, but primate.run is dead :(
  31. blueoh, now it's working
  32. blueI guess it took the haproxy podman container some time to boot up
  33. phalethsystemd is prolly slow
  34. blueya
  35. phalethhaproxy is on the host OS
  36. blueit's a podman container though, right?
  37. phalethhaproxy is installed on archlinux host OS directly
  38. phalethnot a container
  39. blueoh, gotcha
  40. blueI thought it used to be an nspawn container
  41. phalethit used to be, yeah
  42. blueis it easier to have it on host?
  43. phalethit's just a bit more convenient
  44. phaleththere is less NAT translations happening when haproxy is not in container
  45. phaleththe reason I've put haproxy into container was that I used to do custom builds
  46. phalethbut the archlinux build of haproxy has everything needed
  47. phalethso there is no reason to slow things down anymore
  48. phalethand also of course archlinux or whoever maintains the haproxy package makes sure it's up to date
  49. bluegotcha
  50. bluemakes sense
  51. phalethhaproxy's setup is mostly about it's configuration (haproxy.cfg) and that one is exactly the same as it used to be
  52. blueya
  53. bluein the future I do intend for servers to regularly update and restart, but that's a load-balancing issue
  54. blueyou shortly reroute all machines on server 1 to server 2 (assuming you got redundancy on server 2), update server 1, put them back, then update server 2
  55. phalethheh, ok
  56. * jreicher joined #primate