Chat Logs

  1. blueWB nevet, jreicher.
  2. liolocblue: Hey blue! does the sqlite db package support a turso libsql database url?
  3. bluelioloc: hey; I'm unsure; the sqlite generally delegates to the native adapter
  4. bluethe sqlite package*
  5. blueI could check it for you
  6. bluelioloc: "No. @primate/sqlite currently accepts only a local database path or ":memory:". Its underlying @rcompat/sqlite client wraps node:sqlite or bun:sqlite, neither of which supports Turso鈥檚 libsql:// remote URLs."
  7. liolocah ok thanks
  8. blueIf you need this capacity, consider submitting a task to primate or rcompat. if libsql is standardised, this should be in rcompat, if not, in primate. can't promise implementation, but will consider
  9. blueif libsql:// is standardised*
  10. bluehttps://repopack.com/project/rcompat
  11. blueguest roles can report/read tasks
  12. liolocah ok, I will probably make my own module for this
  13. blueok, up to you
  14. liolocYeah I need it for a project i'm working on right now
  15. bluelooks like something @primate/sqlite could benefit from if it doesn't mean pulling in deps
  16. bluebbiab
  17. liolocinitially for speed I'll use an external dep, but if it works well i'll have an ai create it without dependencies
  18. bluek
  19. dreamrealhey, the signin feature works!
  20. dreamrealwoot!
  21. bluedreamreal: signin?
  22. dreamrealthe url you posted for repopack has a title of "sign in" which nevet did NOT echo because it failed the rule for "no signin pages"
  23. dreamrealfound an rcompat bug
  24. blue`task report --project rcompat`
  25. blue`task report` will *probably* be removed in the future and I'll just make it possible to use --project with all task commands, but for now it's still limited to reading tasks
  26. dreamrealOKAY, massive UI refresh coming up
  27. dreamrealyeesh
  28. dreamrealnot a lot visually changes, which is good
  29. dreamrealbut it's been all morning :D
  30. bluedid you report it, dreamreal?
  31. blueI don't see anything
  32. dreamrealShould be... primate task #183?
  33. blueI thought you said rcompat
  34. blueI'll look at it
  35. dreamrealoh, I think it's an rcompat bug, but ... found it in primate, so... err.... I AM A GENIUS
  36. dreamrealor something
  37. blueright
  38. dreamrealhttps://bytecode.news/atlas
  39. bluewow, awesome sauce
  40. blueyou konw, dreamreal, the one thing that takes me the longest is this review-revision cycle. I need to tell the agents to look at it. This is actually something that repopack chat solves: it will allow you to set a session to `autonomous`; so its agent (who is attached to a task) will be informed if attention is needed, either rereviewing, or revising
  41. dreamreal*nod* MAKE THAT NOTE and use it.
  42. dreamreal"Dangit, every time I run into ___ on $otherplatform it annoys me, I bet it annoys others too, I have something that doesn't annoy me"
  43. blueya well, it's just that they should talk to each other and work together. they don't need my input at these stages; if they did, they owuld stop
  44. dreamrealSure
  45. dreamrealjust saying that this is how you communicate the awesome sauce to others
  46. dreamrealI have the workaround for the problem but would far prefer it be in primate/rcompat, obv
  47. dreamrealBBIAF
  48. dreamrealthe atlas is what found the bug, FTR
  49. bluercompat and primate are both getting patches soon
  50. bluehttps://repopack.com/project/rcompat/tasks/4
  51. bluejust need to give this out of the door first
  52. bluewith omarchy.. could be good to have
  53. dreamrealno worries, and no hurry
  54. blue+1
  55. bluedreamreal: primate 0.42.2 is out
  56. blue+ rcompat patch, but that's not your direct concern, likely
  57. bluehi phaleth
  58. bluenub is such a dumpster fire, it accidently published a -pre package and marked it as latest...
  59. bluehttps://repopack.com/project/primate/tasks/185
  60. blueridiculous broken vibe software...
  61. dreamrealblue: doing a general tag cleanup now, which should end up touching the UIs, will update when it gets there
  62. blueand I couldn't even hit ctrl+c or ctrl+d on it. that's how bad it is, phaleth
  63. dreamrealright now tags are split between content and factoids, that needs to be normalized
  64. blueok dreamreal
  65. dreamrealand thank you!
  66. blueyw
  67. phalethhi
  68. blue"Nub asks for CLI OTP because it implements registry uploads itself. On EOTP, it invokes a terminal prompt; it has no browser authentication flow and does not retain the prompted OTP across recursive packages. Pnpm uses its web-auth implementation, opens the browser, and polls npm鈥檚 completion URL."
  69. phalethblue: oh, really, so pnpm is still needed for publishing
  70. blueit's so bad, having to enter >20 times the OTP one after another
  71. blueoh man I was so happy to get rid of pnpm
  72. dreamrealtag normalization is a necessary thing in nevet, factoids and content have different taxonomies and they shouldn't :/ resolving them is dumb
  73. blueand now nub is just a dumpster fire
  74. phalethwell, if it's just publishing for which you need pnpm then I guess that's still not too bad outcome
  75. phalethI think I saw some issues regarding publishing on the nub issue tracker, but it seems like the author does not focus on that currently
  76. bluewe need flog
  77. bluelike, yesterday
  78. blueeverything sucks
  79. blueit's like, every time you want to mvoe a step forward, you move two steps back
  80. blueso for 0.42, I can still publish with pnpm
  81. bluebut we do need a solution for master
  82. blueI'll see if we can keep pnpm for publishing, but two package managers is annoyig
  83. phaleththere is also still bunx in a bunch of places
  84. bluein primate?
  85. phalethanyway, if you just put pnpm in package.json script, you can call it with nub
  86. phalethyeah, in primate
  87. phalethor npm even if you can't stop getting used to typing nub for some reason
  88. phalethnpm run publish
  89. bluehttps://repopack.com/project/primate/tasks/185
  90. bluethis smells
  91. blueno, npm can't publish workspaces, phaleth
  92. bluenot to my knowledge, anyway
  93. bluehive mind: "So Nub builds; pnpm packages and publishes. The browser authentication and registry interaction are handled by pnpm."
  94. phalethI mean npm run publish runs the publish script that executes pnpm
  95. phalethbut can as well type nub run publish to execute pnpm
  96. blueya
  97. phalethok, I see that clanker already wrote some long TS script there
  98. blueyeah there's going nowhere
  99. bluewe're either going back to pnpm+ts check until nub gets serious, or clanker will find a way
  100. bluebest solution is, we get rid of both, they're both bad
  101. phalethnot sure it's worth adding all that code, can just modify the script line in package.json to use pnpm
  102. phalethoh, so you got rid of pnpm-workspace.yml
  103. blueyes
  104. blueI moved to nub completely, with nub.lock
  105. bluenow I'm regretting it
  106. phalethyeah, I bet, I didn't want to do that
  107. dreamrealAh, the joys of committed development :D
  108. phalethI wasn't expecting a gotcha, but it's always better to be cautious
  109. blueI'm just sad everything is bad
  110. bluethis is why I end up writing my own stuff. not because I think it's good, but because other tools just suck
  111. bluethey don't do the basic things you expect them to do
  112. phalethwell, I recommend reverting primate#178 and in primate#185 package.json modify "publish": "nub publish -r --access=public", to publish": "pnpm -r --access=public publish",
  113. phalethand also in primate#185 get rid of all that clankered nonsense
  114. phalethalso no reason to be sad about software tools, it's just tools not always perfect
  115. blueI think I'll revert nub completely if pnpm can run TS checks
  116. blueand then we just move to flog when it's ready
  117. blueclanker is on it
  118. blueit's checking why pnpm didn't do TS checks earlier
  119. phaleththere was no flag like --noCheck or the update --no-check I could find
  120. phalethbut yeah, you may as well go back to pnpm fully, which means slower clankering I think
  121. phalethupdated*
  122. blueyeah, checking
  123. phalethdeployment of primate website does not have to be done using pnpm, so using pnpm 12 is ok
  124. blueI think the next codex limit will be dedicated to getting flog to do package manager stuff
  125. bluebecause the landscape is awful
  126. phalethwait, look, it's rustified already https://github.com/pnpm/pnpm
  127. nevetGitHub - pnpm/pnpm: Fast, disk space efficient package manager
  128. blueoh god no god save us
  129. bluedreamreal: we need help
  130. phalethheh
  131. bluestarted work on flog
  132. bluephaleth: we probably need to prepare flog.run soon :P
  133. phalethyou are really gonna create a flog project?
  134. bluealready did
  135. phalethI think repopack and also primate still need a lot of work
  136. phalethand you gonna use the zig rewrite from github?
  137. blueya, everything needs a lot of work, but blockers should be unblocked. I'm giving this one day
  138. blueno, I'm gonna go with go. I kinda lost faith in the zig project
  139. phalethok, there is a js runtime written in go that's kinda popular
  140. bluethere is?
  141. blue(note I'm limiting flog for now for pure package-manager stuff, not runtime)
  142. phalethanyway, I'd recommend giving primate more effort, primate#186 makes sense
  143. phalethah, ok, that's good
  144. phalethbut you can just finish primate#186 and move on
  145. blueyeah. this is a spike, phaleth. if it takes longer than a day or two, I'll give it up and go back to primate#186 or its follow-up
  146. blueI don't intend to spend a month on it
  147. blueI just wanna untangle this situation if I can. two package managers is annoying, undoing the nub work is annoying, pnpm is annoying too
  148. blueso let's see if we can find the golden path
  149. blueI have a few other nitpicks I've had with package managers along the years, would be a chance to fix them too
  150. dreamrealthe answer is to use rust like god intended! ... or go! ... or python! ... or whatever today's favorite language is
  151. dreamrealI can't keep up
  152. phalethwell, pnpm 12 is prolly not very slow after all
  153. bluephaleth: sent you an invite to flog project
  154. phalethok, thanks
  155. bluehttps://repopack.com/project/flog/tasks?status=open
  156. phaleththe runtime is called goja, here's some performance comparison table https://github.com/dop251/goja/issues/2#issuecomment-2763265666
  157. nevetBenchmarks and performance data? 路 Issue #2 路 dop251/goja
  158. bluenot bad, phaleth
  159. phalethyeah, but the runtime needs perf, look at where ladybird sits in the table
  160. phaleththey prolly managed to optimize something during the year since the table was put together but still
  161. bluewhat's the point of putting bun in that table?
  162. phalethactually 1.5 years already
  163. blueheh, deno is slower than node
  164. bluewhat a stupid table, sorry
  165. blueconflating runtimes and engines
  166. phalethheh, yeah, but I think that's ok
  167. phalethshows engines are faster, obviously, but also by how much
  168. blueI wonder why should a runtime add any overhead at all
  169. bluewell, any meningful overhead, anyway
  170. phalethit's cause of FFI
  171. phalethv8 is C++, but deno is Rust
  172. phalethand node is C++, but they prolly also have some bindings
  173. phalethjust so they can easily update v8
  174. blueso you're saying, always write your engine in the same language as the runtime?
  175. phalethno, C++ is a mess
  176. blueyessir
  177. phalethalso don't write your engine, too many problems with web standards
  178. bluedreamreal: do we need a js engine/runtime in java?
  179. dreamrealWe already have one, depending on what you mean by "in java"
  180. dreamrealwe have multiple, actually
  181. phalethjava has nashorn
  182. blueone that can compete with v8
  183. dreamrealand graal has a different one, and there's rhino, too, if memory serves
  184. phalethnashorn cannot compete with v8
  185. phalethyeah, rhino is like a predecessor to nashorn I think
  186. dreamrealgraal MIGHT be able to but I doubt it, using JS from within java isn't really "the way to do it"
  187. blueheh
  188. dreamrealOKAY! Now logs on pudl can be filtered to be ONLY conversation to cut out all the join/part/quit stuff
  189. dreamrealAnd now primate has the log filter in place too!
  190. dreamrealAight, I'm off for the day, seeya
  191. bluebyebye dreamreal, have a good one