oxfuxxx has quit [Quit: can you please adjust your IRC quit message to be less transphobic?]
_ht has joined #ruby
bluedust has joined #ruby
constxd_ has quit [Ping timeout: 256 seconds]
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 268 seconds]
oxfuxxx has joined #ruby
Thanzex has quit [Read error: Connection reset by peer]
Thanzex has joined #ruby
oxfuxxx has quit [Ping timeout: 240 seconds]
jaredo has left #ruby [#ruby]
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 268 seconds]
Guest9014 has joined #ruby
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 268 seconds]
oxfuxxx has joined #ruby
teclator has joined #ruby
oxfuxxx has quit [Ping timeout: 240 seconds]
oxfuxxx has joined #ruby
Duneyrr has joined #ruby
oxfuxxx has quit [Ping timeout: 268 seconds]
Duneyrr has quit [Client Quit]
Duneyrr has joined #ruby
Duneyrr has left #ruby [#ruby]
Duneyrr has joined #ruby
Duneyrr has quit [Client Quit]
Duneyrr has joined #ruby
Duneyrr has quit [Changing host]
Duneyrr has joined #ruby
oxfuxxx has joined #ruby
oxfuxxx has quit [Ping timeout: 256 seconds]
ZAJDAN has joined #ruby
bluedust_ has joined #ruby
fef has joined #ruby
bluedust has quit [Ping timeout: 256 seconds]
factor7 has joined #ruby
factor has quit [Ping timeout: 250 seconds]
factor7 is now known as factor
ur5us has joined #ruby
<nakilon>
> every vendor's SDK has made a different choice. HTTParty, async-http, Excon, Patron, Faraday, net-http-persistent.
<nakilon>
and I use my own one ..D
Furai has quit [Quit: WeeChat 3.4]
Furai has joined #ruby
ur5us has quit [Ping timeout: 240 seconds]
entropie has quit [Quit: ""]
royo25 has joined #ruby
mixfix41 has joined #ruby
lunarkitty has quit [Quit: Connection closed for inactivity]
TomyWork has joined #ruby
typ1cal_c0ffxe3 has joined #ruby
typ1cal_c0ffxe3 has quit [Client Quit]
oxfuxxx has joined #ruby
typ1cal_c0ffxe3 has joined #ruby
jmcgnh has quit [Ping timeout: 250 seconds]
leonthemisfit has quit [Read error: Connection reset by peer]
oxfuxxx has quit [Ping timeout: 240 seconds]
jmcgnh has joined #ruby
typ1cal_c0ffxe3 has quit [Ping timeout: 250 seconds]
Duneyrr has quit [Ping timeout: 250 seconds]
Duneyrr has joined #ruby
shokohsc has quit [Ping timeout: 240 seconds]
mitt3ns has quit [Remote host closed the connection]
shokohsc has joined #ruby
Thanzex has quit [Read error: Connection reset by peer]
Thanzex has joined #ruby
bluedust has joined #ruby
bluedust_ has quit [Ping timeout: 240 seconds]
entropie has joined #ruby
bluedust_ has joined #ruby
entropie has quit [Ping timeout: 268 seconds]
entropie has joined #ruby
bluedust has quit [Ping timeout: 240 seconds]
bluedust_ has quit [Remote host closed the connection]
Bounga has joined #ruby
bluedust has joined #ruby
bluedust_ has joined #ruby
bluedust has quit [Ping timeout: 240 seconds]
duderonomy has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
perrierjouet has quit [Quit: WeeChat 3.4]
Duneyrr has quit [Ping timeout: 240 seconds]
constxd_ has joined #ruby
perrierjouet has joined #ruby
Bounga has quit [Ping timeout: 256 seconds]
perrierjouet has quit [Client Quit]
BSaboia has joined #ruby
perrierjouet has joined #ruby
cdown has joined #ruby
Sheilong has joined #ruby
BSaboia has quit [Quit: This computer has gone to sleep]
_whitelogger has joined #ruby
Starfoxxes has joined #ruby
isene has joined #ruby
Milos has joined #ruby
e2 has quit [Ping timeout: 256 seconds]
CrazyEddy has joined #ruby
szkl_ has quit [Ping timeout: 256 seconds]
Milos_ has quit [Ping timeout: 256 seconds]
CalimeroTeknik has quit [Ping timeout: 256 seconds]
szkl_ has joined #ruby
BSaboia has joined #ruby
nullheroes2 has joined #ruby
yxhuvud has quit [Quit: No Ping reply in 180 seconds.]
e2 has joined #ruby
CalimeroTeknik has joined #ruby
yxhuvud has joined #ruby
Guest9014 has quit [Ping timeout: 256 seconds]
Bounga has joined #ruby
weyhmueller has joined #ruby
Thanzex has quit [Read error: Connection reset by peer]
Thanzex has joined #ruby
oxfuxxx has joined #ruby
Duneyrr has joined #ruby
ZAJDAN has quit [Ping timeout: 240 seconds]
bluedust has joined #ruby
bluedust_ has quit [Ping timeout: 268 seconds]
fef has quit [Remote host closed the connection]
ZAJDAN has joined #ruby
oxfuxxx has quit [Ping timeout: 240 seconds]
<ox1eef>
Net::HTTP is my personal favorite, and since it is in the stdlib, it's worth learning well.
<ox1eef>
constxd_: no, they don't, only one is running at a given time, unless the threads are IO-bound, then they can run in parallel. It's a topic that could have its own book.
mdemo has quit [Ping timeout: 250 seconds]
mdemo has joined #ruby
<constxd_>
ox1eef: can ruby do real parallelism
<constxd_>
do you know if YARV / MRI do GC in a separate thread
bluedust has quit [Remote host closed the connection]
<adam12>
constxd_: This is a part of what Ractors are suppposed to solve.
Thanzex has quit [Read error: Connection reset by peer]
Thanzex has joined #ruby
drincruz- is now known as drincruz
Duneyrr has joined #ruby
taupiqueur has quit [Quit: taupiqueur]
random-jellyfish has joined #ruby
ZAJDAN has joined #ruby
random-jellyfish has quit [Ping timeout: 256 seconds]
gproto23 has joined #ruby
dostoyev1ky2 is now known as dostoyevsky2
Bounga has quit [Ping timeout: 250 seconds]
keinbock has left #ruby [WeeChat 1.9.1]
Thanzex has quit [Read error: Connection reset by peer]
Thanzex has joined #ruby
reset has quit [Quit: reset]
random-jellyfish has joined #ruby
<ccooke>
Hmm. How usable are Ractors now 3.1 is out?
<ccooke>
I did some playing Jan/Feb last year, but hit a number of issues
<havenwood>
ccooke: They're still experimental and unfinished.
<ccooke>
Shame. But it's a complex piece of work
bluedust has joined #ruby
hanzo has quit [Quit: Connection closed for inactivity]
<havenwood>
ccooke: Async Fibers are production ready and stable but Ractors keep changing and breaking anything I do with them.
<ccooke>
Aye
John_Ivan has quit [Read error: Connection reset by peer]
<havenwood>
Most recently, Ractors lost the ability to share lambdas, just a couple weeks before 3.1 release. >.> That's a key feature and it'll probably be back but so many mutability issues for now until more things get work to make them shareable.
<adam12>
I want to blog about this too. I'm tired of docs being second class in Ruby.
<adam12>
If everyone would start by turning off `--no-document` in their development envs, that would be great.
<yassernasc>
which are the good use-cases for ruby?
<havenwood>
yassernasc: Programming!
<havenwood>
yassernasc: It's a general purpose language, so general purpose cases. It's not appropriate for real time or systems programming, but for most things it works great.
ur5us has joined #ruby
Thanzex has quit [Read error: Connection reset by peer]
Guest39 has joined #ruby
Thanzex has joined #ruby
<yassernasc>
yeah, i love the ruby syntax and i want to code more using it
Guest39 has quit [Client Quit]
<yassernasc>
so, i was thinking to use ruby to backend with Sinatra + mongoid orm
<yassernasc>
but about not appropriate for real time.. it is like, using websockets isn't a good idea?
Duneyrr has quit [Read error: Connection reset by peer]
<havenwood>
yassernasc: Great for WebSockets. Don't use it to drive your car.
<havenwood>
yassernasc: I'd suggest Roda instead of Sinatra.
<havenwood>
nakilon: A few things. Roda is faster and uses less memory. The plugin system lets you compose the framework you need, and not get stuck with bloat. I've been so burned by namespace pollution with Sinatra and never happens in Roda.
<havenwood>
nakilon: If you have tons of routes, it's also preferable since the routing tree handles them efficiently. Sinatra may use finite automata like Rails now but for the longest time was just iterating through an Array of Regexp for route matches and it could slow to a crawl.
<havenwood>
nakilon: Basically, Roda is a fresh take on Sinatra with lessons learned and in practice it's just so lovely.
<havenwood>
Also, maintained by a member of Ruby core who made it about as lovely as it can be and maintains it alongside Sequel.
<havenwood>
adam12: Have you been tempted to port Roda apps to hanami-api? I'm curious.
<adam12>
havenwood: Not hanami-api, but more so hanami-router + hanami-controller.
<adam12>
tbh, I really miss having a router I can introspect. And when I introduce Roda on teams, they just struggle constantly with the Roda routing tree style of working.
<adam12>
I miss having classes too. Somewhere to stick random private methods that are relevant to that specific action.
<havenwood>
adam12: Yeah, I generate a routes.json but it's not ideal, for sure.
<adam12>
I have some fairly large apps I consult on, so I'm seeing the pain more than I think anyone else is.
<adam12>
I generate routes.json too on some projects. It does solve some issues, but there's a disconnect between the comment and the location in the tree.
<adam12>
And as per my rant earlier, documentation is often ignored. Moving a routing block doesnt' necessarily mean the person will update the comment about the route :(
<havenwood>
adam12: I've looked at hanami and appreciate the internals code quality but haven't had a chance to use it since I've gone Rails or Roda every time in Ruby land in recent years.
<adam12>
havenwood: It's moving faster than it has been, which is great. I'd like to contribute more but it's impossible with little ones (as you know)
<nakilon>
I had a very funny, disgusting and shameful encounter with hanami developer
<adam12>
I enjoy Roda+Sequel because Jeremy has a regular release cadence. I'm not stuck on my own forks for eternity.
<havenwood>
For small apps, Roda+Sequel has for sure been lovely.
<adam12>
Jeremy's ethics of OSS maintainership are a blessing when I'm just trying to get stuff done.
<adam12>
havenwood: I've flirted with my own framework, using hanami-router and hanami-controller, in the spirit of Merb. I spent some time on it last year, but it kinda dwindled.
<havenwood>
adam12: Nice
<adam12>
I'm in the camp of Rails, where a good framework is _extracted_.
<adam12>
havenwood: I've seen Utopia. Samuel has an interesting approach to APIs that doesnt' always jive with me.
<havenwood>
adam12: I wonder how Tipi does so well compared to Falcon. Good stuff.
<adam12>
havenwood: I haven't explored it yet. Tho interestingly, it's following a similar change in hanami for passing in request and response as individual args. A divergence of the Rack API.
<havenwood>
I guess it's just out of the box tuning and one configures more aggresively.
<havenwood>
Probably closes the gap to use `falcon serve --preload` but still, great performance.
<nakilon>
error: Async::Task [oid=0xc3c8] [ec=0xc3dc] [pid=50344] [2022-01-20 00:52:27 +0300] | RuntimeError: You want to finish 3 frames, but stack size is only -7
<ox1eef>
puma-dev is really nice, it makes it easy to serve personal web apps over the local network.
<nakilon>
also have stack size -161 lol
bluedust has joined #ruby
<nakilon>
looks like I can't just call byebug inside this async stuff ..\
bluedust_ has joined #ruby
<nakilon>
it just throws thousands of such errors
<nakilon>
starting with this one: Async::Task [oid=0xc3a0] [ec=0xc3b4] [pid=50344] [2022-01-20 00:52:27 +0300] | Errno::EIO: Input/output error - read
<nakilon>
how do I debug then?
bluedust has quit [Ping timeout: 250 seconds]
bluedust_ has quit [Remote host closed the connection]
<nakilon>
really, I have no clue how to debug and fix when this thing starts throwing thousands error for other reasons
<nakilon>
and am not sure where the error was really stopping my threads
Guest63 has joined #ruby
<Guest63>
Slm
Guest63 has quit [Client Quit]
oxfuxxx has quit [Ping timeout: 240 seconds]
Thanzex has quit [Read error: Connection reset by peer]
Thanzex7 has joined #ruby
<nakilon>
if I put the "abort" there instead of byebug to then just inspect the file artifacts nothing happens, no error in log, program is still going
<nakilon>
but if I after that do ^C I get back into bash with no backtrace and the process is still running in background
<nakilon>
I feel like once some async routine gets an error the whole stdout is fucked and is frozen
<nakilon>
I see that new and new routines are starting and ending but there is no output anymore while each of them had to puts a line
<nakilon>
and the error or whatever it is that has frozen by stdout isn't printed, the terminal is just stuck
<nakilon>
oh now it's printing, thousands of lines of backtraces
ZAJDAN1 has joined #ruby
<nakilon>
yeah I throw a Timeout in them and when it happened instead of printing it and crash it was accumulating a ton of backtraces to then spit out them as " 5m error: Async::Task ... | Timeout::Error: execution expired" for several minutes to finally abort yet not finishing the whole list of tasks as I understand from the
<nakilon>
progressbar gem
<nakilon>
I suppose it has to either go to the end or abort on the first fail, not this useless intermediate behaviour
ZAJDAN has quit [Ping timeout: 256 seconds]
<nakilon>
yeah it has processed something between 45 and 70 percents of tasks and now I'll have to start it over again two-three more times
<nakilon>
https://i.imgur.com/mAvihdu.png see this gap between ~45% and ~75% ? that's when the console was stuck and it was working silently to then finally abort and spit the backtraces; now it's stuck again... neither ensuring to go to the end, nor to print me the progress
<nakilon>
if you ask how do I know that it didn't try to execute all the tasks? I see that they didn't add anything to my cache