01:56 <rg_3[m]> headius: do you think the issue i opened about set_trace_func is solvable ?

01:57 <rg_3[m]> or have any time frame for it.. just curious to see if my lib could work on jruby, don't want to be pushy

01:57 <rg_3[m]> here's the issue; https://github.com/jruby/jruby/issues/6096

10:42 <headius[m]> chrisseaton: I believe that should work. It's just a github pages site.

10:42 <headius[m]> we'll have to look into it

10:43 <headius[m]> Oh, I could not see you added www

10:43 <headius[m]> I don't know if we support that URL, or it we care. https://jruby.org is the official site

11:52 <headius[m]> rg_3: I believe so but they're kind of low priority while we try to wrap up the JRuby 9.2.11 series. I believe enebo fixed at least the `c-call` issue for 9.2.11 but he'll have to confirm that

11:53 <headius[m]> chrisseaton enebo : I think the `www.jruby.org` issue is due to redirecting from www to the bare address, which causes problems for the github pages ssl

11:59 <headius[m]> enebo: I pinged you on one issue that could be included in 9.2.11 and fixed an access warning on the branch. Other access warnings need jruby-launcher to catch up with bash script, which I can work on later (sleep schedule's a bit messed up so I'll be back online later today US time)

17:52 <lopex> https://grep.app/

17:52 <lopex> wow this is fast

18:55 <enebo[m]> rg_3: yeah 9.3.0.0 we will try and address remaining issues we can for trace func and trace point fixes

18:55 <enebo[m]> I have implementation for thread methods but I discovered something ugly which makes me want to punt that for now

18:56 <enebo[m]> I also will fix return event to actually pass the return value as well (something else I examined after looking at more of these)

18:56 <enebo[m]> headius: I merged and cp'd that escapecgi PR

18:57 <headius[m]> ah was it against master?

18:57 <enebo[m]> The PR was yeah

18:57 <headius[m]> yeah that's annoying

18:57 <headius[m]> if they are against jruby-9.2 we can just merge to master

18:57 <headius[m]> using cp gets messy

18:58 <enebo[m]> the merge will still work since the code is the same but it may look weirder in git log output

18:58 <headius[m]> I merged jruby-9.2 to master and it looks ok

18:58 <headius[m]> my SecurityHelper change was not merged anyway

18:59 <headius[m]> feels like there's a better way to manage two active branches

18:59 <enebo[m]> in this case luckily it is a small number of changes

19:08 <headius[m]> yeah hopefully it stays that way

19:11 <headius[m]> enebo: this was fixed by the CGI thing so I marked it for .11

19:11 <headius[m]> https://github.com/jruby/jruby/issues/6093

19:11 <enebo[m]> yeah good

19:42 <headius[m]> enebo: I could not get that s3 hang to run successfully on 9.2.6.0

19:42 <headius[m]> either I'm doing something wrong or it regressed earlier

19:43 <enebo[m]> hmm kares may shed light

19:43 <headius[m]> I was able to connect in browser and add the bucket but no dice on uploading

19:43 <headius[m]> I'm trying 9.2.5 now

19:48 <headius[m]> I confirmed CRuby works ok

19:48 <headius[m]> 9.2.5 no

20:06 <headius[m]> 9.2.4 no, 9.2.0.0 no, 9.1.0.0 no

20:06 <headius[m]> I'm starting to wonder if this ever worked

20:23 <headius[m]> enebo: so regardless that would not get into 9.2.11... what's left

20:24 <enebo[m]> headius: I made and tested bits

20:24 <headius[m]> I love a tiny release

20:24 <headius[m]> commenter claims it worked on 9.1.13

20:24 <headius[m]> I am skeptical

20:29 <headius[m]> enebo: working on notes

20:29 <enebo[m]> headius: ok

20:29 <enebo[m]> finishing up some more website updates for new version

20:38 <headius[m]> enebo: https://gist.github.com/headius/33862e7367e9116cc48e5e9737629795

20:38 <headius[m]> the only two major items were the gems in jars and perf thing so that's it

20:39 <enebo[m]> headius: yeah seems reasonable...it was the reason for this extra point

20:39 <headius[m]> BTW anything you think would be likely to go in these notes should at least be a PR, because I'm basing this on closed issues and PRs

20:39 <enebo[m]> err reasons

20:39 <headius[m]> I usually do PR for anything that is a functionality change or semi-major fix

20:40 <headius[m]> kares: same recommendation for you but you already do PRs most of the time

20:40 <enebo[m]> ok rolling forward with these notes

20:44 <headius[m]> oops I missed a PR for the gems in jars thing

20:45 <enebo[m]> headius: you mean notewise or things are still broken?

20:45 <headius[m]> notewise

20:45 <enebo[m]> ah well we can correct on website and in tag

20:46 <headius[m]> oh and 6060 was marked for 9.3 but we had to fix it for gemjars

20:46 <headius[m]> I will fix everything

20:46 <headius[m]> I'm already there

20:47 <enebo[m]> the edit tag feature of github is nice and seemingly the only magic to make it display as markdown

20:47 <enebo[m]> ok

20:47 <headius[m]> yeah it's just metadata so I guess that's fine

20:47 <enebo[m]> I made a 9.3.1.0 milestone...we need to realyl evaluate which of these 73 open issues for 9.3.0.0 are actually going to make it

20:48 <headius[m]> getting 2.6 stuff working is top priority right now

20:48 <headius[m]> it's close but the branch is messy

20:48 <enebo[m]> it does remove and re-add the tag but it is the same commit so meh if someone is out of date for a minute :)

20:49 <enebo[m]> I will add 9.2.12.0-SNAPSHOT even though we are unlikely to run into that...fingers crossed

20:51 <headius[m]> does it really re-add the tag?

20:52 <headius[m]> I suppose it probably has to but hopefully there's never a moment when it's not visible

20:53 <headius[m]> I assumed since it says "Existing tag" with a checkmark this is just GH metadata

20:53 <enebo[m]> I guess pulling and seeing if it is actually the comment of the tag would tell you

20:54 <enebo[m]> I did it from GH itself since it did not work last time

20:54 <enebo[m]> well the markdown didn't

20:54 <travis-ci> jruby/jruby (jruby-9.2:612d7a0 by Thomas E. Enebo): The build was broken. https://travis-ci.org/jruby/jruby/builds/657473261 [100 min 17 sec]

20:55 <headius[m]> tag and site are fixed

20:55 <enebo[m]> nice

20:55 <headius[m]> tweet going out

21:00 <enebo[m]> huzzah

21:01 <headius[m]> it is tweeted

21:01 <headius[m]> and there was much rejoicing

21:02 <travis-ci> jruby/jruby (9.2.11.0:612d7a0 by Thomas E. Enebo): The build failed. https://travis-ci.org/jruby/jruby/builds/657473859 [99 min 57 sec]

21:03 <headius[m]> good one enebo

21:04 <headius[m]> need to fix whatever that is

21:21 <lopex> so many red pixels burnt

21:37 <headius[m]> global crisis of wasted red pixels reaches epic proportions

22:12 <headius[m]> klobuczek: thank you for working with us on that regression... we were way off in guessing

22:12 <headius[m]> this was a minor release so no zeitwerk but I have a branch that fixes most issues and mostly needs some cleaning up and concurrency fixes

22:12 <headius[m]> 9.3 will have it... has to have it really

22:56 <headius[m]> https://www.reddit.com/r/ruby/comments/fckozt/jruby_92110_released_embedded_gems_and_caller/

22:57 <headius[m]> enebo: couple suggestions for the issue list that will make release a little smoother...

22:57 <headius[m]> 1. generate in reverse chrono order... I think it's a better sequence because it will show issues *before* the PR that fixes them in the list, and folks waiting on older issues will see theirs first

22:58 <headius[m]> 2. generate as markdown... everywhere we're posting it is markdown now anyway, and the reddit post's markdown does not recognize the HTML version of that list

22:59 <headius[m]> I fixed it locally with a simple replace of `%r[<li><a href="(.*)">(.*)</a> - (.*)</li>]` with `* [$2]($1) - $3`

23:04 <headius[m]> enebo: also I just tested to see what would happen if we have a milestone the same name as the release/tag and there doesn't appear to be any sort of auto-linking

23:04 <headius[m]> not sure if it would do something at the time of making the release or not

23:04 <headius[m]> for now though seems like no reason to align tags and milestone names