ByteCode.News
Submit RSS Atom Sign in

Back to the channels

#java

  1. * zimal joined #java
  2. * PyR3X joined #java
  3. * fizzie joined #java
  4. * hassoon joined #java
  5. * hwpplayer1 joined #java
  6. * m joined #java
  7. * hugdru joined #java
  8. * ChaiTRex joined #java
  9. * Tomte joined #java
  10. NeXeN yes, i just had a eureka moment!
  11. NeXeN stupid and as silly as it sounds, it actually works. a very complex thing i've been building from a vision for months (man maybe year and a half now) and it can make a boolean value upper or lower case, as designed!
  12. NeXeN man that's why i love coding, fsck them llms they make you lazy
  13. NeXeN small accomplishments give me energy
  14. jreicher Umm, huh?
  15. NeXeN working on a gui app and just testing. doing simple stuff
  16. NeXeN but you know, it's nice after putting a lot of effort into a thing, even a simple accomplishment makes things fun
  17. jreicher Oh I absolutely know the feeling. It's one of the reasons I like using Emacs. Tiny tweaks have a big impact, and always feel simple in a way. But I'm curious what the thing is you're working on.
  18. * hugdru joined #java
  19. NeXeN oh, it's a library
  20. NeXeN lets you provision a pipeline. has a schema code generator (not an llm, think boilerplate reduction) and a gui that lets you essentially do some of the design work visually instead of with json or xml, though you could i guess
  21. NeXeN the code schema is used to enforce type safety across the pipeline no matter the language. there will be a TS library so can pass via protobuf or classic serialization
  22. NeXeN but to get to the point where i can simply drag and drop a thing and see that it's type safe and doing it's thing is kinda cool. i had doubts if i had the stamina to stay with a personal project
  23. deebo isn't protobuf typed already?
  24. NeXeN yeah that's why i wanna use it
  25. NeXeN i have become a fan, but it's not always straightforward you know....most people just serialize
  26. deebo protobuf could be interesting to use instead of json over rest for internal data
  27. deebo think netflix does it like that
  28. NeXeN it's definitely more efficient. but i'm supporting jackson and gson as well just because
  29. deebo apis would have to be more explicit about errors etc as well which would be beneficial
  30. NeXeN yeah
  31. NeXeN i mean you know, i can build tools to inspect protobuf as easy as json. but i'm hoping to keep it at a lower layer where i don't ever have to think about it
  32. deebo our end user apps log all http traffic currently (even most bodies) for debugging etc, would be easier to filter protobuf too, http json has too many gotchas and "non-trivial" parsing to do that
  33. NeXeN oh yeah no joke!
  34. NeXeN hrmm you gave me an idea
  35. deebo maybe time to let claude prototype something :)
  36. NeXeN i have built a filter to filter out pii in logs, i bet it could be adapted to do a similar thing
  37. deebo we use zalandos logbook, it can easily do header and property filtering, like "password": "hunter2" -> "password": "xxx"
  38. NeXeN yeah. i dunno why you gotta log everything, but it sure is handy in a pinch
  39. deebo but what it couldn't do (well), was when given a massive blob of data, like {"id": 5, ... hundreds of nested props ... }, we couldn't just log: {"id":5}, since that's the only important bit
  40. deebo we use MDC with user session ids etc, so it's really easy to see what an user did that lead to an error, or check their claims of some problem that supposedly happened to them
  41. deebo RUM could achieve the same, IF everyone agreed to third party scripts etc, but they don't :)
  42. * five618480339176 joined #java
  43. NeXeN couldn't you change from a full dump of the req/resp body just filter with something simple to parse the stream and just extract top level keys and full parse just for things i dunno diagnostic, like /id or /status and such and drop the rest, just keep what you need?
  44. NeXeN maybe you could even populate the mdc at the gateway/filter layer with userId, sessionId, etc and the extracted entity's id?
  45. NeXeN then you don't really need the raw request, i mean ...you know to figure out what they did
  46. NeXeN maybe you got plenty of space. you know that's always a thing
  47. deebo that would mean reading the streams going in and out into a buffer, trying (and sometimes failing) to parse into json, filter via code and then output to logs
  48. NeXeN yeah, probably better to just rely on the route bindings instead
  49. deebo we tried it but it didn't really work, would probably be easier with protobuf
  50. NeXeN selective field extraction is cheap
  51. NeXeN i like protobuf. i'm trying to push it into my personal projects. you know it sucks doing that at work....using a new shiny toy just because
  52. * hwpplayer1 joined #java
  53. * pebble joined #java
  54. * Etoxiuq joined #java
  55. * nimaje joined #java
  56. * hwpplayer1 joined #java
  57. * Cae2 joined #java
  58. * marcel joined #java
  59. * Afroboy joined #java
  60. * mixfix41 joined #java
  61. * MikeBux joined #java
  62. * evilscreww joined #java
  63. * hugdru joined #java
  64. * acidjnk joined #java
  65. * fgarcia_ joined #java
  66. * fgarcia joined #java
  67. * Afroboy joined #java
  68. * Adrian35 joined #java
  69. * yeahitsme joined #java
  70. * GreenResponse joined #java
  71. * Munnu joined #java
  72. * Hobbyboy joined #java
  73. hassoon 'morning
  74. * metalmaniac joined #java
  75. * ne555 joined #java
  76. * onu joined #java
  77. * mrcrabs827769651 joined #java
  78. * jreicher joined #java
  79. jreicher javabot is napping on the job again.
  80. * tkjay joined #java
  81. * Artea joined #java
  82. * ChaiTRex joined #java
  83. dreamreal I dunno why it's so inconsistent lately, I don't think anything's changed in the code
  84. jreicher I thought it was "consistent" in its behaviour of not reconnecting? Maybe the change is in external factors causing more frequent disconnections?
  85. dreamreal No clue, not watching the logs
  86. dreamreal not my server, not my bot :/
  87. * iusr joined #java
  88. * hiredman joined #java
  89. Para libera servers don't allow immediate authentication either, so if the bot's too quick to authenticate, it can fail
  90. * iusr joined #java
  91. * iusr joined #java
  92. * iusr joined #java
  93. * jamezp joined #java
  94. * iusr joined #java
  95. * hugdru joined #java
  96. * Adrian35 joined #java
  97. * iusr joined #java
  98. * acidsys joined #java
  99. * B_fd joined #java
  100. * sa02irc joined #java
  101. * hugdru joined #java
  102. hassoon 'afternoon
  103. sbalmos what isn't "immediate authentication" about authenticating on connect with SASL?
  104. * hwpplayer1 joined #java
  105. * Nav94 joined #java
  106. * m joined #java
  107. * dgregory joined #java
  108. * dostoyevsky2 joined #java
  109. * lockdown joined #java
  110. * fstd joined #java
  111. * zimal joined #java
  112. * genpaku joined #java
  113. * zimal joined #java
  114. * benjwadams joined #java
  115. * handicraftsman joined #java
  116. * benjwadams left #java
  117. * hwpplayer1 joined #java
  118. * CodeGeek joined #java
  119. * lockdown joined #java
  120. * LtHummus_ joined #java
  121. * hwpplayer1 joined #java
  122. * Adrian35 joined #java
  123. * dostoyevsky2 joined #java
  124. * dostoyevsky2 joined #java
  125. * dostoyevsky2 joined #java
  126. * dostoyevsky2 joined #java
  127. * mindCrime joined #java
  128. * deavmi joined #java
  129. NeXeN * NeXeN shrugs
  130. jreicher Para: what do you mean? I'm still learning about how IRC works but I thought only nickserv auth mattered, and if the nick is still in use you can use REGAIN. (That's how I have my IRC client setup for when I have a network glitch; it reconnects ASAP)
  131. nimaje you should use SASL auth with a client certificat if the irc network supports it, like libera does https://libera.chat/guides/certfp
  132. nevet Login With a Certificate (CertFP)
  133. * fwumo joined #java
  134. * metalmaniac joined #java
  135. NeXeN some people don't use sasl, and you auth a moment later. i dunno i think the bot might have other troubles
  136. NeXeN but also the network kicked my znc off, which hasn't happened before. like two days ago
  137. * acidjnk joined #java
  138. * victori joined #java
  139. * kusanagi_ joined #java
  140. * iusr joined #java
  141. * cheeser joined #java