subbu has quit [Ping timeout: 252 seconds]
razetime has joined #jruby
subbu has joined #jruby
subbu has quit [Ping timeout: 256 seconds]
razetime has quit [Ping timeout: 268 seconds]
razetime has joined #jruby
razetime has quit [Ping timeout: 260 seconds]
subbu has joined #jruby
razetime has joined #jruby
ahorek[m] has quit [Quit: You have been kicked for being idle]
<enebo[m]> jimtng: Not sure if you saw but I fixed that issue on friday.
<headius> enebo: okay now I am having the Maven XML files differ on my M1 machine as well. Can you tell me what version of Maven you are running? All the systems I develop on have this issue now
<headius> Something must be different that's changed the ordering it generates on my machines
<enebo[m]> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
<enebo[m]> Ah I am using my own installed copy I dl'd separate from FC
<enebo[m]> What version are you using?
<headius> 3.8.6 on the mac
<headius> I don't have the fedora machine handy
<enebo[m]> I can get 3.8.6 and see if I match up with you
<headius> It's been super frustrating because I have to constantly ignore those diffs so if we can get on the same page it would be a big help
<headius> Ok
<enebo[m]> I think this is a bit odd but if we can be in agreement it will be ok for a while :)
<headius> I mean the plugin needs to be fixed but that's a tall order right now
<enebo[m]> yeah
<enebo[m]> modified: core/pom.xml
<enebo[m]> modified: lib/pom.xml
<enebo[m]> yeah groupId and artifactId swapped
<enebo[m]> So I can commit this and we should both be on the same arbitrary order :)
<enebo[m]> I pushed it
<enebo[m]> hopefully neither of us sees these out of date until we update maven or something like that
<headius> Thank goodness
<lavamind> o/ jcharaoui on github
<lavamind> headius, I've got a patch for mipsel as well, if you're interested
<lavamind> I've got jffi building and testing on all supported debian arches now
<lavamind> riscv64 as well
* lavamind afk for lunch
razetime has quit [Remote host closed the connection]
ahorek[m] has joined #jruby
<headius> enebo: I saw what you wrote in the stringio kwargs issue
<headius> you are mostly concerned with it using the keywords annotation I assume
<headius> the existing keywords = true will have to continue to work through 9.4 and I don't think it will conflict with the rework, but that rework will mostly be a 9.5 thing
<enebo[m]> so can 9.3 use this gem?
<headius> it's possible but you have to explicitly activate it
<headius> so a bundle exec might
<enebo[m]> ok then the annotation will be an issue for that
<headius> I'm not positive though... classloading and such may pick up the built-in version always
<headius> yeah it could be a problem
<enebo[m]> I wondered if we could maybe change this to be ruby for they kwargs handling methods and forward to Java code
<headius> we could do a 9.3.x that adds it as a no-op
<headius> or something equivalent to 2.6 kwargs if something could be flipped on
<enebo[m]> yeah that's a possibility
<enebo[m]> fwiw using newer StringIO on 2.6 impl is perhaps not supportable anyways?
<enebo[m]> Or perhaps it depends on whether they support it
<headius> I'm not sure how much the encoding changes inside stringio so we might be able to do it a simple way
<headius> yeah MRI should be having this issue to some extent
<headius> I assume the gem supports previous versions even though it can't easily be activated
<enebo[m]> lunch
<headius> yeah I don't think this should be too tough to add but our initialize is not using the extract_mode_enc logic from IO and so that's a diff
subbu has quit [Ping timeout: 252 seconds]
<enebo[m]> yum
<enebo[m]> encoding
<headius> I think we can do this in a 9.3 compat way if that is necessary
subbu has joined #jruby
subbu has quit [Ping timeout: 252 seconds]
subbu has joined #jruby
Francesco[m]1 has left #jruby [#jruby]