<Exuma>
havenwood they require me to use a specific MD5 hash of a string they give me, not a random key. does that matter?
<havenwood>
Exuma: you *can* do that, but you'd want to use #digest not #hexdigest, to get 16 bytes
<Exuma>
ooooh
<Exuma>
havenwood so weird, im looking at their gem from 2014 and theyre using hexidigest. now that it hink about it, its probably just truncating it because i saw a GH issue about that (whereas now it raises)
<Exuma>
which is hilarious that their own gem doesnt do that correct
<havenwood>
Exuma: ooops!
<Exuma>
havenwood what is 'non-repudiation'? theyre making me jump through all these hoops to do this
<Exuma>
it seems stupid (it is for payment processing, similar to stripe token flow)
<havenwood>
Exuma: that bug is a pretty big security flow ¯\_(ツ)_/¯
<havenwood>
flaw*
ur5us has quit [Read error: Connection reset by peer]
ur5us has joined #ruby
<havenwood>
Exuma: bytes for hex characters is a small subset of bytes
<mad_al>
"if the key is to be derived from a password, you should rely on PBKDF2 functionality provided by OpenSSL::PKCS5."
<mad_al>
Might be a better option
<havenwood>
Exuma: they used just 16 numbers, 16 times - rather than 256 numbers, 16 times
<Exuma>
yeah, I'm not an expert at security but a lot of what I have to do for these payment processing gateways and whatnot seems extremely antiquated
<Exuma>
like they have 10 pages devoted to this stupid encryption mumbo jumbo before sending it over an SSL connection
<havenwood>
Exuma: hrmm
<Exuma>
they said its because of "non repudiation"
<Exuma>
and its funny because on their site, the password is on a different form submit than their username in the name of "security"
<Exuma>
and the whole page is unstyled html (like 20 lines of css)
<Exuma>
so Im like................. mmmmm ok, whatever you say
<havenwood>
Exuma: I'd call that "signing"
<havenwood>
But that's a super weird way to sign ¯\_(ツ)_/¯
<Exuma>
The interface requires that much of the data submitted is encrypted. This is in addition to SSL encryption that exists
<Exuma>
for all of the parameters. The purpose of this extra encryption is NOT to secure the data in transit (we trust SSL/TLS for that, and in fact the most
<Exuma>
sensitive data is not encrypted by anything else.) Instead, this extra encryption is used to establish non-repudiation for the transaction, and to
<Exuma>
protect SPI users from the potential that a response from the SPI might be ‘spoofed.’
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ruby
dsmythe_ has quit [Remote host closed the connection]
dsmythe has joined #ruby
<Exuma>
havenwood ok thanks ill look at thees
fphilipe_ has joined #ruby
Mia has quit [Read error: Connection reset by peer]
tdy1 has joined #ruby
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ruby
fphilipe_ has quit [Ping timeout: 268 seconds]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ruby
bambanx has joined #ruby
cnsvc has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
crankharder has joined #ruby
cnsvc has joined #ruby
haengma has quit [Remote host closed the connection]
jeremycw has quit [Ping timeout: 252 seconds]
djellemah has quit [Ping timeout: 245 seconds]
crankharder has quit [Ping timeout: 268 seconds]
bambanx has quit [Quit: Leaving]
brool has joined #ruby
giraffe has joined #ruby
tpendragon has joined #ruby
djellemah has joined #ruby
esrse has joined #ruby
regedit has joined #ruby
djellemah has quit [Client Quit]
braincrash has quit [Quit: bye bye]
braincrash has joined #ruby
Omnilord has quit [Quit: This computer has gone to sleep]
doodlebug has quit [Read error: Connection reset by peer]
Fusl has quit [Remote host closed the connection]
Fusl has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
<syndikate>
Is it a good practice to make use of lambdas and process in a big codebase? Apparently it's rails. I wanted to make some chained method calls look concise so I am declaring a lambda and passing it to one of the maps
<syndikate>
But I am not sure how generally it is perceived, the codebase I am on doesn't have any lambda/proc usage as such.
<syndikate>
Except for some builtin rails stuff
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
crankharder has joined #ruby
haxx0r76 has joined #ruby
tdy1 has quit [Ping timeout: 255 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
haxx0r has quit [Remote host closed the connection]
rhuang_ has quit [Ping timeout: 244 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
marz_d`ghostman has joined #ruby
ltd has joined #ruby
<marz_d`ghostman>
I have model say Customer, with initialize() parameters of (id, first_name, last_name, email, organization, phone, notes) but rubocop is saying I shouldn't have more than 5 parameters. What's the best way to refactor this?
<marz_d`ghostman>
Calls to the initialize/.new() gives the ABC error from rubocop
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
brool has quit [Ping timeout: 250 seconds]
rhuang_ has joined #ruby
fphilipe_ has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
rhuang_ has quit [Ping timeout: 258 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
cjohnson has quit [Quit: Lost terminal]
rhuang_ has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
rhuang_ has quit [Ping timeout: 244 seconds]
rhuang_ has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
orbyt_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
hagebake_ is now known as hagabaka
dellavg_ has joined #ruby
tdy1 has joined #ruby
haengma has joined #ruby
rhuang_ has quit [Ping timeout: 244 seconds]
kapilp has joined #ruby
hightower3 has quit [Ping timeout: 245 seconds]
haengma has quit [Ping timeout: 268 seconds]
jenrzzz has joined #ruby
jenrzzz has quit [Ping timeout: 245 seconds]
dsmythe has quit [Remote host closed the connection]
rhuang_ has joined #ruby
dsmythe has joined #ruby
cgfbee has quit [Remote host closed the connection]
rhuang_ has quit [Ping timeout: 246 seconds]
dellavg_ has quit [Ping timeout: 255 seconds]
houhouli_ has quit [Remote host closed the connection]
crankharder has quit [Ping timeout: 268 seconds]
UncleCid__ has quit [Read error: Connection reset by peer]
Exuma has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FancyEagle has joined #ruby
rhuang_ has joined #ruby
espinet has quit [Quit: espinet]
espinet has joined #ruby
espinet has quit [Client Quit]
rhuang_ has quit [Ping timeout: 268 seconds]
conta has joined #ruby
haxx0r76 has quit [Remote host closed the connection]
rhuang_ has joined #ruby
cgfbee has joined #ruby
rhuang_ has quit [Ping timeout: 246 seconds]
sauvin has joined #ruby
ur5us has quit [Remote host closed the connection]
ur5us has joined #ruby
FancyEagle has quit [Quit: Leaving]
FancyEagle has joined #ruby
<havenwood>
syndikate: I'm curious about the details of the lambda.
<havenwood>
syndikate: It may just be the first case in this codebase for this abstraction. Or maybe they're choosing to be more repetitive but explicit. I think it depends on the lambda.
FancyEagle has quit [Client Quit]
<havenwood>
marz_d`ghostman: Are they keyword arguments or regular arguments?
FancyEagle has joined #ruby
<havenwood>
marz_d`ghostman: Definitely use keyword arguments.
ur5us has quit [Ping timeout: 255 seconds]
aupadhye has joined #ruby
duderonomy has joined #ruby
<marz_d`ghostman>
havenwood: I'm using keyword arguments, hence: item_id: name:, etc., but it's more than 5 parameters, is there an idiomatic way for it in ruby?
<havenwood>
marz_d`ghostman: That is the idiomatic way. RuboCop has some rules that are like wishful thinking, that a domain never be so annoyingly complex.
<marz_d`ghostman>
havenwood: Ah I see, thanks I'll just ignore it then, including the ABC warning hehe
<havenwood>
marz_d`ghostman: You can always choose to set that data in a block or after initialization, but that's not _better_.
<marz_d`ghostman>
Out of topic, I've stumbled upon this language: Elixir, which is very ruby-like. Are you into that as well?
<marz_d`ghostman>
havenwood: Ah, nice. You're trying to integrate Elixir's power into Ruby, hehe
<marz_d`ghostman>
I'm not that very efficient with Ruby, but I've tried it and it's a bit challenging to think in a functional paradigm. I haven't delved deep into it, but I already like it as well haha
<havenwood>
syndikate: You could refactor `the_method` to avoid the `result_array`: activerecord_object.relations.map.with_index
<havenwood>
syndikate: or you can do it the other way around: activerecord_object.relations.each_with_index.map
<havenwood>
syndikate: I would probably extract `mainipulation_lambda` there to a constant.
vondruch has joined #ruby
<syndikate>
havenwood, yeah okay. I just opted for the latter for now but I think the first looks more concise. How and why a constant havenwood ?
haengma has joined #ruby
<havenwood>
syndikate: oh, that's the same method! i'm slow on the uptake...
<havenwood>
syndikate: The how is easy, just declare it outside the mthod: MANIPULATION_LAMBDA = ->(x,y) { #multline, same definition }.freeze
<havenwood>
syndikate: The why is to avoid creating the lambda each time you call the method. Instead of many lambda objects churning for many method calls, they can all use the single lambda constant that was instanciated only once.
<havenwood>
syndikate: A block handily never instanciates an object.
<syndikate>
Oh, okay. I thought so. I didn't get this part "A block handily never instanciates an object".
<syndikate>
al2o3-cr, havenwood I could do that. I changed that to this, this felt a little more concise for me, maybe coz I was taking some elixir lessons.
<syndikate>
I wasn't sure if I should go down this route actually, that's why I thought to ask :D
<havenwood>
syndikate: A `proc {` or `->{` proc or lambda creates a new instance of a Proc object. The reason for a block is to have a similar function but never allocate an object.
* al2o3-cr
can't believe he's still up watching netflix
haengma has quit [Remote host closed the connection]
<syndikate>
OH, okay. havenwood so even if I make it a constant and define it outside, would it still have the issue or allocation objects again?
reber has joined #ruby
<havenwood>
syndikate: A single proc or lambda is no big deal at all. The reason to make it constant is to just ensure there's only one of them, no unnecessary copies.
<havenwood>
syndikate: If the method is called a million times, no reason to create a million procs that you destroy each time the method call is over
<havenwood>
syndikate: You can just call a proc constant a million times. One proc, reused.
<syndikate>
Yeah okay. I will make it a constant outside the method at the class level so that one lambda is instantiated when the object is instantiated and will be called in the map
<syndikate>
Then again, is it okay if I go down this route in ruby code? I mean for me it makes the whole .map.with_index looks better havenwood
dsmythe has quit [Remote host closed the connection]
<havenwood>
syndikate: You can .map.with_index either way. The question then is whether to use a block, or a lambda constant. The block is appealing, unless you want to dry up that same block being reused. Then, a lambda constant is a nice way.
<havenwood>
syndikate: Do multiple methods share the block?
dsmythe has joined #ruby
<havenwood>
syndikate: If not, just use a block.
<syndikate>
havenwood, no it doesn't, but what am trying to do is reduce the number of methods with all this. Right now I could remove one method if I make this chained call concise with lambda and move the call upto the parent method
<syndikate>
I think am at borderline overdoing stuff
<havenwood>
syndikate: It looks like you're heading down the right path for refactoring. From what you've shown though, it should probably just be a block.
<havenwood>
syndikate: It doesn't look like there's a good reason to extract a lambda.
rhuang_ has joined #ruby
jenrzzz has joined #ruby
<syndikate>
Ah okay, gotcha. Yeah, the only reason for lambda is for the syntactic sugar of being able to call it like (&lambda_name)
hiroaki has quit [Ping timeout: 245 seconds]
<havenwood>
syndikate: The & will pass the lambda as a block, instead of as an argument
<havenwood>
syndikate: it also calls #to_proc (which just returns the lambda itself)
<havenwood>
syndikate: but it's why you can do: &:a_symbol
<havenwood>
syndikate: The block is the special form, where no object is allocated. That's the usual case.
<havenwood>
syndikate: The lambda is when you want to allocate an object. If you're reusing a block between many methods, you may want to do that to dry things up. Also, a lambda can be passed around as an argument. You can have multiple lambda arguments, etc.
rhuang_ has quit [Ping timeout: 244 seconds]
DTZUZO has joined #ruby
<havenwood>
You can only have one block.
FancyEagle has quit [Quit: Leaving]
<al2o3-cr>
syndikate: in ruby 2.7 you can do: activerecord_object.relations.map.with_index(&.:manipulation_method))
<al2o3-cr>
if you are using methods
i1nfusion has quit [Remote host closed the connection]
FancyEagle has joined #ruby
i1nfusion has joined #ruby
<al2o3-cr>
havenwood: is that syntax right?
<havenwood>
al2o3-cr: that'd be: the &method(:manipulation_method)
<al2o3-cr>
havenwood: no, i mean for ruby 2.7?
<havenwood>
al2o3-cr: the `.` in `.:` is only shorthand for `.method()`
<al2o3-cr>
havenwood: yeah, just looked wrong to me for a minute then
<havenwood>
al2o3-cr: (self).:<=>.(self) #=> 0
<havenwood>
but yeah, funny the `.` just means `.method`
<havenwood>
i thought it should mean `.public_method`, but a little more flexible this way
<marz_d`ghostman>
Is there a different scope for controllers in Rails? I have something initialized during bootup, but it appears it isn't when it comes to the controller.
<al2o3-cr>
havenwood: ah, yeah. didn't think of that.
<syndikate>
havenwood, bit detailed (sorry) but here is what exactly am doing - https://dpaste.de/AyQZ#L1
<havenwood>
marz_d`ghostman: Dunno why the initializer wouldn't seem to have run from a controller? What's the controller code that's not working as expected?
<marz_d`ghostman>
havenwood: So in initializer I have that code. Then under controller I tried to `puts` to test it's connection via Podio.connection.nil? and it is nil. I did the same thing under initializer where I `puts` the same thing and it isn't in there
<havenwood>
syndikate: You could actually put your lambda in a `def manipulation_lambda`, but unlike a constant, that would create a new lambda each time you called the method. If that doesn't make sense, I can show examples.
<havenwood>
syndikate: I do think you can get away with a block: .with_index { |x, y| x.abstracted_method(y) }
<havenwood>
&>> def double; -> n { n * 2 } end; [1, 2, 3].map &double # for example, a method works
<syndikate>
havenwood, yeah the block makes much more sense here. I was just going through the code again. The reason why I opted for lambda first of all is because I could do that &method here. I can't do that if defined a method as def method; end.
<syndikate>
But that's again defining a method which has a lambda inside it right? As you said this is gonna create a lambda every time - there is not advantage to this right?
nowhere_man has joined #ruby
<syndikate>
no*
<havenwood>
syndikate: right, you don't want to do that, typically - you want to reduce unnecessary object creation
<havenwood>
syndikate: anything you can declare up front and freeze, do it!
<syndikate>
Yeah I am changing to this, I can prevent a lambda creation here ^
<havenwood>
syndikate: +1
<havenwood>
syndikate: An advantage of extracting the lambda might be being able to name that operation. This is just what blocks are for though, so it's a good use here.
<syndikate>
Ah okay, but if I am abstracting it out to the model then the lambda has no much use case, right?
<havenwood>
syndikate: Usually blocks suffice nicely.
reber has quit [Remote host closed the connection]
rhuang_ has joined #ruby
FancyEagle has quit [Read error: Connection reset by peer]
nowhereman has joined #ruby
FancyEagle has joined #ruby
conta has quit [Read error: Connection reset by peer]
<havenwood>
marz_d`ghostman: Maybe a different thread is handling the connection?
cnsvc has quit [Ping timeout: 256 seconds]
dsmythe has quit [Ping timeout: 245 seconds]
<syndikate>
Yeah, so if I am not moving that abstraction to the model, i.e keeping that manipulation method definition in the current class itself maybe I could have a named lambda and re-use it. Now that I have moved it I guess a block is good enough. Is my understanding correct havenwood ?
rhuang_ has quit [Ping timeout: 246 seconds]
fphilipe_ has joined #ruby
FancyEagle has quit [Read error: Connection reset by peer]
<havenwood>
syndikate: A block is typically best. It's the common case that has a special syntax, a block with no need for a discrete object. The lambda is more of an edge case, where you would need to pass a block around or need more than one block, etc.
<havenwood>
syndikate: blocks are usually what you turn to first
kapilp has quit [Quit: Connection closed for inactivity]
<havenwood>
marz_d`ghostman: The problem is that when you initialize Podio, it sets itself up _only_ on the current thread.
<havenwood>
marz_d`ghostman: From a second thread, it's not setup.
<havenwood>
marz_d`ghostman: Assuming you're using a multithreaded webserver, like Puma.
conta has joined #ruby
<havenwood>
marz_d`ghostman: Podio is literally setting up its connection on the current Thread only.
<marz_d`ghostman>
havenwood: Ah, yeah, I'm using Puma
<havenwood>
marz_d`ghostman: It'd work if you were in single threaded mode, but with multiple threads the Podio setup isn't affecting any thread other than the one it was initialized on
<marz_d`ghostman>
havenwood: Is there a way for me to cascade that initialized Podio to every thread created to handle requests?
<syndikate>
Ah okay. So I should see it as more of a requirement for a first class citizen to be passed around.
<marz_d`ghostman>
havenwood: I just got it, so Puma creates a different thread for every request received.
<havenwood>
marz_d`ghostman: It uses a thread pool by default, so any thread in that pool might handle a request.
<marz_d`ghostman>
havenwood: Is there a way to cascade the initialized Podio out to the threads?
<havenwood>
marz_d`ghostman: Podio is actually using a Fiber-local variable, not even a Thread-local variable, but the issue is the same - only seeing it from the current Thread.
FancyEagle has quit [Ping timeout: 252 seconds]
<havenwood>
marz_d`ghostman: One way would be to switch the Podio gem over to a nice connection pool setup instead, but that might be more work than you want to do. An easy way would be to setup the connection when you find there isn't one.
<marz_d`ghostman>
havenwood: Wouldn't that be slow, given multiple requests. It will always try setting up the connection each time a request is received
jefffrails35 has quit [Remote host closed the connection]
ramfjord has joined #ruby
dhollin3 has joined #ruby
dhollinger has quit [Read error: Connection reset by peer]
alem0lars has quit [Ping timeout: 258 seconds]
Mia has joined #ruby
Mia has quit [Changing host]
Mia has joined #ruby
ramfjord has quit [Ping timeout: 246 seconds]
gloscombe has joined #ruby
NL3limin4t0r has quit [Quit: WeeChat 1.9.1]
alem0lars has joined #ruby
cnsvc has joined #ruby
crankharder has quit [Ping timeout: 258 seconds]
NL3limin4t0r has joined #ruby
jefffrails35 has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
crankharder has joined #ruby
hightower3 has joined #ruby
BH23 has joined #ruby
Cthulu201 has joined #ruby
cnsvc has joined #ruby
BH23 has quit [Remote host closed the connection]
rhuang_ has joined #ruby
Mia has quit [Read error: Connection reset by peer]
sphenxes has joined #ruby
rhuang_ has quit [Ping timeout: 246 seconds]
<marz_d`ghostman>
What's the best architecture for an app to constantly receive updates from another app? Does redis pub/sub a good fit?
conta has quit [Quit: conta]
jenrzzz has joined #ruby
RedSnarf has joined #ruby
jenrzzz has quit [Ping timeout: 245 seconds]
jefffrails35 has quit [Ping timeout: 252 seconds]
cnsvc has quit [Ping timeout: 256 seconds]
AJA4350 has joined #ruby
GodFather_ has joined #ruby
GodFather has joined #ruby
valadares has joined #ruby
octos has quit [Remote host closed the connection]
za1b1tsu has quit [Remote host closed the connection]
Omnilord has joined #ruby
regedit has quit [Quit: Connection closed for inactivity]
conta has joined #ruby
Cthulu201 has quit [Quit: Nowhere special. I always wanted to go there.]
funnel has quit [Ping timeout: 276 seconds]
funnel has joined #ruby
BH23 has joined #ruby
Cthulu201 has joined #ruby
RedSnarf has quit [Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org]
mrtyr has joined #ruby
mrtyr has quit [Client Quit]
cnsvc has joined #ruby
hightower3 has quit [Ping timeout: 255 seconds]
AJA4350 has quit [Ping timeout: 244 seconds]
BH23 has quit [Remote host closed the connection]
cd has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
Jonopoly has joined #ruby
laaron- has quit [Remote host closed the connection]
laaron has joined #ruby
AJA4350 has joined #ruby
yqt has joined #ruby
i1nfusion has quit [Remote host closed the connection]
Swyper has joined #ruby
i1nfusion has joined #ruby
Emmanuel_Chanel has quit [Ping timeout: 246 seconds]
jefffrails35 has joined #ruby
dviola has joined #ruby
vondruch has quit [Ping timeout: 258 seconds]
wald0 has joined #ruby
vondruch has joined #ruby
esrse has quit [Ping timeout: 258 seconds]
rhuang_ has joined #ruby
cnsvc has joined #ruby
za1b1tsu has joined #ruby
rhuang_ has quit [Ping timeout: 246 seconds]
griffindy has joined #ruby
jenrzzz has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
yqt has quit [Ping timeout: 255 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
jenrzzz has quit [Ping timeout: 255 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
agent_white has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
vondruch has quit [Quit: vondruch]
vondruch has joined #ruby
<z64>
marz_d`ghostman redis is indeed one way to do this over something like pub/sub. plenty of other options to weigh though that depends on your use case; there's also services like rabbitmq, or you could roll something simple with a local unix socket, etc.
nakuku has joined #ruby
<mnemon>
yeah, event queues like rabbitmq and kafka are pretty much made for that
<nakuku>
Hello, How do i get just the time zone name from a string? get_timezone("2012-02-01T18:00:00-09:00") => -09:00 or Alaska
alem0lars_ has joined #ruby
alem0lars has quit [Ping timeout: 244 seconds]
Emmanuel_Chanel has joined #ruby
cnsvc has joined #ruby
crankharder has quit [Quit: leaving]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
dviola has quit [Quit: WeeChat 2.4]
andikr has quit [Remote host closed the connection]
cnsvc has quit [Ping timeout: 256 seconds]
andikr has joined #ruby
SeepingN has joined #ruby
s00pcan has quit [Ping timeout: 246 seconds]
za1b1tsu has quit [Remote host closed the connection]
alem0lars_ has quit [Remote host closed the connection]
nakuku has quit [Remote host closed the connection]
dumptruckman_ is now known as dumptruckman
jefffrails35 has quit [Remote host closed the connection]
jefffrails35 has joined #ruby
conta has quit [Ping timeout: 246 seconds]
hightower3 has joined #ruby
jefffrails35 has quit [Read error: Connection reset by peer]
cnsvc has joined #ruby
rhuang_ has joined #ruby
dviola has joined #ruby
jeremycw has joined #ruby
dviola has quit [Quit: WeeChat 2.4]
rhuang_ has quit [Ping timeout: 268 seconds]
laaron has quit [Remote host closed the connection]
tdy1 has joined #ruby
laaron has joined #ruby
Dbugger has joined #ruby
tdy1 is now known as tdy
cthulchu has joined #ruby
cnsvc has quit [Ping timeout: 256 seconds]
apparition has joined #ruby
Omnilord has quit [Quit: This computer has gone to sleep]
dviola has joined #ruby
chromis has joined #ruby
valadares has quit [Quit: Leaving]
valadares has joined #ruby
polishdub has joined #ruby
valadares has quit [Client Quit]
<marz_d`ghostman>
z64: Ah kafka seems nice. I'm not that familiar with unix sockets though
octos has joined #ruby
tdy has quit [Ping timeout: 255 seconds]
yoshida has joined #ruby
yoshida has quit [Client Quit]
ellcs has quit [Ping timeout: 255 seconds]
dsmythe has joined #ruby
nima_m has joined #ruby
cnsvc has joined #ruby
wald0 has quit [Ping timeout: 258 seconds]
dsmythe has quit [Ping timeout: 250 seconds]
altious2 has joined #ruby
wald0 has joined #ruby
altious2 has quit [Remote host closed the connection]
dviola has quit [Quit: WeeChat 2.4]
dsmythe has joined #ruby
Exuma has joined #ruby
tdy has joined #ruby
GodFather has quit [Ping timeout: 246 seconds]
ovnimancer has quit [Quit: ovnimancer]
GodFather_ has quit [Ping timeout: 252 seconds]
tf2ftw2 has joined #ruby
tf2ftw2 has quit [Client Quit]
dhuey has joined #ruby
Exuma has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sidekiqfail>
does anybbody know why my sidekiq won't work?
sidekiqfail is now known as haxx0r
cnsvc has joined #ruby
Jello_Raptor has quit [Ping timeout: 255 seconds]
jenrzzz has joined #ruby
Jello_Raptor has joined #ruby
jenrzzz has quit [Ping timeout: 258 seconds]
doodlebug has joined #ruby
mikecmpbll has quit [Quit: inabit. zz.]
rippa has joined #ruby
fphilipe_ has quit [Ping timeout: 246 seconds]
AJA4351 has joined #ruby
AJA4350 has quit [Ping timeout: 255 seconds]
AJA4351 is now known as AJA4350
<havenwood>
side, okay then
<havenwood>
they left
rhuang_ has joined #ruby
dhollin3 is now known as dhollinger
<phaul>
they just changed name, now they are haxx0r
moei has joined #ruby
<havenwood>
phaul: ahh, i silence all the name noise - oops!
<havenwood>
haxx0r: What part of it doesn't work? Why are you making and calling a lambda?
lxsameer has quit [Ping timeout: 246 seconds]
<havenwood>
haxx0r: It'd be the same result if you just removed the lambda: top = Sms.otp_from_ref(ref)
<havenwood>
haxx0r: What's the lambda meant to be doing there? I'm confused.
ovnimancer has joined #ruby
agent_white has quit [Quit: bbl]
rhuang has joined #ruby
octos has quit [Remote host closed the connection]
rhuang_ has quit [Remote host closed the connection]
cnsvc has quit [Ping timeout: 256 seconds]
octos has joined #ruby
clemens3 has quit [Quit: WeeChat 1.6]
octos has quit [Remote host closed the connection]
kapilp has joined #ruby
andikr has quit [Remote host closed the connection]
<zxq2>
is there a TLS implementation written in ruby? it doesn't matter if it's minimal. obviously openssl is not a candidate since there are bindings.
doodlebug has quit [Ping timeout: 258 seconds]
<zxq2>
searched around, didn't see anything
doodleb86 has joined #ruby
jenrzzz has joined #ruby
duderonomy has joined #ruby
duderonomy has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
valadares has joined #ruby
tdy has joined #ruby
duderonomy has joined #ruby
gloscombe has quit [Quit: WeeChat 2.4]
tdy has quit [Read error: error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac]
tdy has joined #ruby
doodleb86 has quit [Read error: Connection reset by peer]
cnsvc has joined #ruby
<darix>
zxq2: why not use the openssl bindings?
<darix>
zxq2: I dont think there are production ready pure ruby implementations
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
zinefer has joined #ruby
<zinefer>
i am working inside a rails task (so there's no class) and i have defined a method that accepts a block ... everything works fine until i define a lamba or proc and pass that into the method as a block ... the proc gets called but it seems like all method calls inside that proc get a nil appended onto the end of the method arguments
<zinefer>
this is preventing me from calling any method that cares about how many arguments are passed to it
<zinefer>
my hunch is that nil is some reference to a non-existent self
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
dhuey has quit [Remote host closed the connection]
kapilp has quit [Quit: Connection closed for inactivity]
haengma has joined #ruby
haengma has quit [Ping timeout: 252 seconds]
lypsis has joined #ruby
lypsis has quit [Client Quit]
valadares has quit [Quit: Leaving]
lypsis has joined #ruby
<tf2ftw>
Is there a way to generate a Tempfile path without creating a Tempfile?
octos has joined #ruby
griffindy has joined #ruby
ovnimancer has joined #ruby
reber has joined #ruby
griffindy has quit [Read error: Connection reset by peer]
dsmythe has quit [Remote host closed the connection]
dsmythe has joined #ruby
espinet has quit [Quit: espinet]
AJA4350 has quit [Ping timeout: 245 seconds]
AJA4350 has joined #ruby
<adam12>
tf2ftw: Would you rather a normal File? Fairly sure the premise of Tempfile is that it's created when requested, since if not there could be a potential race condition if the new filename could be predicted.
<zinefer>
adam12: sorry for the slow reply, i went to lunch :( checking out your gist now
<tf2ftw>
I'm mostly interested in tapping into the System's temp source. That being said, I _could_ just create a Tempfile then close it right away but that's not my desire.
<adam12>
tf2ftw: If you just need some sort of random looking filename like Tempfile would produce, you could probably recreate it yourself by pairing Dir.tmpdir + $$ + something else?
<tf2ftw>
I was surprised to not see Tempdir.path or the like.. but happy to know about tmpdir now!
<adam12>
tf2ftw: Kinda surprised myself tbh, but there's probably a ton of legacy behind why it was placed where it was.
<phaul>
as a side note predictable temp file names are security hole. and $$ is predictable
<phaul>
depends on your needs, for a single user desktop and one user script it doesn't matter.
<adam12>
phaul: Good point.
doodleb32 has joined #ruby
<adam12>
I like knowing which pid created what, so adding another bit of entropy to the string wouldn't hurt. SecureRandom.alphanumeric(8) or something.
doodlebug has quit [Ping timeout: 245 seconds]
<tf2ftw>
My use case is someone uploads a CSV and the backend does some "magic" which eventually saves a zip containing the csv. I'm intercepting the uploaded file and replacing it with the zip after its temporarily created. Not sure if that makes sense but that's the situation.
kyrylo has joined #ruby
<tf2ftw>
I need the file to persist long enough to not be GCed during that process.
<tf2ftw>
Correct me if I'm wrong but the system will clean up the temp dir for me right?
<zinefer>
adam12: you are right, the error is only thrown when the activerecord is involved
<zinefer>
i thought of a way to solve this in a better way with just a loop over lunch so i don't think i am going to pursue this further, i very much appreciate your help though
<adam12>
zinefer: yw.
<adam12>
tf2ftw: I believe Ruby will prune Tempfile instances on exit.
<adam12>
tf2ftw: And of course, some OS's ship with a tmp cleaner.
<adam12>
tf2ftw: If you want to guarantee persistence, maybe look at storing it somewhere you can control and make the filename obtuse. Hash the file and split into a namespace, etc. Probably many ways to do it.
haengma has joined #ruby
<tf2ftw>
Ruby will GC once the Tempfile loses scope (which is nice) but doesn't help when returning as an object.
jenrzzz has quit [Ping timeout: 258 seconds]
nima_m has joined #ruby
gix has joined #ruby
rhuang has quit [Quit: WeeChat 2.4]
RiPuk has joined #ruby
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ruby
doodleb32 has quit [Read error: Connection reset by peer]
sgen has joined #ruby
altious has quit [Quit: Leaving]
altious has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
Nicmavr has quit [Ping timeout: 245 seconds]
Kestrel-029 has joined #ruby
fphilipe_ has joined #ruby
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
fphilipe_ has quit [Ping timeout: 258 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
Nicmavr has joined #ruby
Kestrel-029 has quit [Ping timeout: 245 seconds]
doodlebug has joined #ruby
doodlebug has quit [Excess Flood]
yqt has joined #ruby
haengma has quit [Remote host closed the connection]