00:52
_whitelogger has joined #jruby
02:30
lucasb has quit [Quit: Connection closed for inactivity]
04:20
travis-ci has joined #jruby
04:20
travis-ci has left #jruby [#jruby]
04:51
travis-ci has joined #jruby
04:51
travis-ci has left #jruby [#jruby]
05:19
drbobbeaty has joined #jruby
05:23
travis-ci has joined #jruby
05:23
travis-ci has left #jruby [#jruby]
05:26
Osho has quit [Ping timeout: 245 seconds]
05:30
travis-ci has joined #jruby
05:30
travis-ci has left #jruby [#jruby]
05:33
Osho has joined #jruby
05:54
travis-ci has joined #jruby
05:54
travis-ci has left #jruby [#jruby]
05:54
drbobbeaty has quit [Ping timeout: 264 seconds]
07:03
rusk has joined #jruby
07:50
shellac has joined #jruby
08:12
whitingjr has quit [Ping timeout: 268 seconds]
08:12
shellac has quit [Quit: Computer has gone to sleep.]
08:45
shellac has joined #jruby
08:53
whitingjr has joined #jruby
09:19
shellac has quit [Ping timeout: 250 seconds]
10:17
<
kares[m] >
and I thought the AR-JDBC suite is enough of a guard against driver regressions
10:17
<
kares[m] >
anyhow, to update to latest I have pushed jdbc-sqlite3 today ... we're at 3.28.0 now
10:18
<
kares[m] >
guess I'll check how a jruby build is doing
10:18
<
kares[m] >
esp. since jeremyevans mentioned regressions for previous jdbc-sqlite3
10:54
drbobbeaty has joined #jruby
10:55
<
kares[m] >
all green
11:04
whitingjr has quit [Ping timeout: 258 seconds]
11:58
whitingjr has joined #jruby
12:07
whitingjr has quit [Quit: Leaving.]
12:08
whitingjr has joined #jruby
13:17
<
kares[m] >
btw. also pushed postres and mariadb jdbc driver updates recently
13:18
<
kares[m] >
not sure what to do about mysql's official one ... somehow not sure about looking into the details that might have changed and what that means for AR-JDBC
13:35
shellac has joined #jruby
14:16
<
jeremyevans >
kares[m]: Probably a good idea to always test Sequel before release, since Sequel in general is going to test more of a database's features than AR
14:18
<
kares[m] >
that makes sense, thanks. will try to do that properly with jdbc-mysql if I manage to get to it
15:32
whitingjr has quit [Ping timeout: 245 seconds]
16:03
xardion has quit [Remote host closed the connection]
16:03
xardion has joined #jruby
16:09
rusk has quit [Remote host closed the connection]
16:48
shellac has quit [Ping timeout: 250 seconds]
16:50
sagax has joined #jruby
17:36
<
headius[m] >
kares: jeremyevans I'm glad we had this hooked up so we found it almost immediately
17:37
shellac has joined #jruby
18:01
travis-ci has joined #jruby
18:01
travis-ci has left #jruby [#jruby]
18:17
snickers has joined #jruby
18:22
<
sagax >
how to run ruby code with jruby?
18:27
<
havenwood >
sagax: use jruby in place of where you would use ruby
18:28
<
havenwood >
sagax: i found it easy to get started with jruby. give it a try!
18:28
<
sagax >
i will try install jruby with rvm
18:29
<
sagax >
it's true that jruby not have GIL? and threads in jruby it's real thread without block?
18:31
<
kares[m] >
yep, that is correct - no GIL in JRuby
18:32
<
sagax >
threads in jruby without block? - it's part true to?
18:32
<
sagax >
or jruby have another some like as blocks
18:33
<
kares[m] >
threads will block just like in ruby e.g. if you use a mutex
18:33
<
kares[m] >
or when they wait for IO
18:34
<
kares[m] >
but they won't block each other out when executing ruby code
18:34
<
kares[m] >
you maybe should read some good posts about what GIL means
18:36
<
kares[m] >
the second example (Ruby Operations) will benefit from a GIL free Ruby -> get faster under JRuby
18:43
shellac has quit [Quit: Computer has gone to sleep.]
19:06
<
sagax >
link to multi-threading has broken :(
19:10
travis-ci has joined #jruby
19:10
travis-ci has left #jruby [#jruby]
19:20
sagax has quit [Ping timeout: 272 seconds]
19:34
<
headius[m] >
sagax: thanks for pointing that out
19:36
<
headius[m] >
we need more recent articles :-D
19:38
<
headius[m] >
sagax: I removed that link and added a new one about building a Sinatra + Roda + Sequel web app with JRuby
19:39
<
headius[m] >
do you have other questions about multithreading in JRuby?
19:45
travis-ci has joined #jruby
19:45
travis-ci has left #jruby [#jruby]
19:46
travis-ci has joined #jruby
19:46
travis-ci has left #jruby [#jruby]
19:51
sagax has joined #jruby
20:04
<
headius[m] >
enebo: ok...that is the green build even though it isn't green
20:04
<
headius[m] >
somehow travis is returning something wacky for localhost within the last hour
20:05
<
headius[m] >
that has four tags for autoload in rubyspec and two excludes in MRI...all related to edge cases of concurrent autoload
20:05
<
enebo[m] >
I wonder if MRI is doing the same thing now with that change
20:05
<
enebo[m] >
oh it is ruby/spec
20:05
<
headius[m] >
this is a couple dozen fewer tags than master
20:06
<
enebo[m] >
ah boo ruby/spec has not run in days
20:06
<
enebo[m] >
so I am curious to see if they start failing although we may be using different image too
20:06
<
headius[m] >
slow dev cycle on MRI this summer
20:07
<
headius[m] >
well I restarted the job and it did the same thing, but I'll try making a fully new push (merge master) and let it go
20:07
<
enebo[m] >
sounds good though. you only have a couple of tags and if those are very hard to trigger we should have a lot less issues than we had
20:08
<
headius[m] >
yeah I will double check that zeitwerk is still green and introduce that as a suite
20:08
<
enebo[m] >
I do think people who use JRuby already fret a bit about concurrent loading
20:08
<
headius[m] >
I don't know of any major outstanding issues but I know we didn't behave quite right
20:08
<
enebo[m] >
but zeitwerk if green and enabled by default on 6 should also reduce a lot of potential for reports on conc loading
20:09
<
enebo[m] >
of course it is not currently enabled but one step at a time
20:16
<
headius[m] >
hmm there's one zeitwerk regression, I'll look into that
20:16
<
headius[m] >
it had dozens of failures before this work though
20:18
<
sagax >
i install jruby with rvm
20:18
<
sagax >
but i don't have jruby in command line
20:18
<
sagax >
my distro - openSUSE, if it's matter
20:26
<
havenwood >
sagax: rvm use jruby
20:27
<
havenwood >
sagax: then check: ruby -v
20:27
<
havenwood >
sagax: ruby -e "p RUBY_ENGINE" #>> "jruby"
20:48
<
headius[m] >
same failure in latest build...beats me
20:48
<
headius[m] >
I'm going to restart one on master and see if it happens there
20:49
travis-ci has joined #jruby
20:49
travis-ci has left #jruby [#jruby]
21:08
snickers has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:17
lucasb has joined #jruby
21:37
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
22:22
shellac has joined #jruby
22:30
travis-ci has joined #jruby
22:30
travis-ci has left #jruby [#jruby]
23:00
nirvdrum has joined #jruby
23:10
<
headius[m] >
enebo ^
23:11
<
headius[m] >
My confidence level isn't super high but it's green
23:11
drbobbeaty has joined #jruby
23:13
shellac has quit [Quit: Computer has gone to sleep.]
23:14
shellac has joined #jruby
23:27
shellac has quit [Quit: Computer has gone to sleep.]
23:28
shellac has joined #jruby
23:28
shellac has quit [Client Quit]