Time |
Nick |
Message |
03:41 |
|
bgillap joined #evergreen |
04:07 |
|
Bmagic joined #evergreen |
04:07 |
|
dluch joined #evergreen |
06:58 |
|
rjackson_isl_hom joined #evergreen |
07:49 |
|
collum joined #evergreen |
07:52 |
|
RFrasur joined #evergreen |
08:29 |
|
Dyrcona joined #evergreen |
08:33 |
Dyrcona |
Right. So, I'm going to debug OpenSRF on both Ubuntu 20.04 and Ubuntu 22.04 to see if I can figure what exactly has changed. My trouble so far has been figuring out where to put a break point so that I don't spend an hour stepping through unrelated code. |
08:39 |
|
mantis joined #evergreen |
08:40 |
|
mmorgan joined #evergreen |
09:08 |
Dyrcona |
OK. I'm getting somewhere. On Ubuntu 20.04 doing "request math add 2,2" returns an error message with a code of 503. |
09:14 |
Dyrcona |
Also, gdb on Ubuntu 22.04 steps through a lot more useless code than on Ubunu 20.04. |
09:21 |
Dyrcona |
print atts[0] |
09:21 |
Dyrcona |
value has been optimized out |
09:21 |
Dyrcona |
Not useful..... |
09:28 |
Dyrcona |
Looks like I'll have to disable optimization, but I wonder if this is a gcc as crazy as that sounds. |
09:28 |
Dyrcona |
s/(gcc)/\1 bug/ |
09:33 |
Dyrcona |
Grr. Can't override it on the configure command line. I have to either manually edit the Makefiles or edit configure.ac. |
09:43 |
Dyrcona |
All right. It's not really "optimized out" although disabling optimization did help. |
09:44 |
Dyrcona |
so, when we're getting an error response on 22.04, the message only has the type="cancel" attribute. On 20.04, it has that attr and code=503! So, the bug is in the error message creation somewhere. |
09:52 |
Dyrcona |
x/128s confirms it.... :) |
10:01 |
Dyrcona |
So, how do I debug the router? |
10:08 |
Dyrcona |
Wait a minute. Is this service-unavailable message coming from Ejabberd? |
10:13 |
Dyrcona |
That's what it looks like, so it's a change in Ejabberd 21.12. |
10:29 |
Dyrcona |
So, it works on Ejabberd 21.01 that ships with Debian Bullseye. |
10:30 |
Dyrcona |
If it is an Ejabberd change it happened last year, but I don't see anything in the release notes about error codes, and the #ejabberd channel is less frequented and quieter than this one. |
11:22 |
Dyrcona |
oof. Better dust off the O'Reilly erlang book..... :) |
11:25 |
Dyrcona |
I think I've tracked it down erlang-p1-xmpp changes, and possibly RFC 6120. Error codes are gone. |
12:03 |
|
jihpringle joined #evergreen |
12:24 |
mantis |
Having an issue at one library where staff gets randomly logged out. Doesn't use extensions in their web browser and they are on ver 100.0.4896.127 for chrome. |
12:24 |
Dyrcona |
Since error codes are going away, should we continue to log them or just not bother looking for them? |
12:25 |
Dyrcona |
mantis: Are you sure it is random and not after so many minutes every time? They could have an org unit setting for staff client timeout that is too short. |
12:28 |
Dyrcona |
Also, it looks like session_transport.c is going to need changes in at least 7 places. |
12:34 |
|
collum joined #evergreen |
12:34 |
mantis |
Yeah we don't have a short log out period |
12:35 |
mantis |
It's about 480 minutes of inactivity that produces a log out |
12:37 |
Dyrcona |
I'd double check the actor.org_unit_settings for the library and all of its branches, etc. |
12:38 |
Dyrcona |
Maybe there is something clearing the cookies after so many minutes? |
12:39 |
|
collum joined #evergreen |
12:40 |
Dyrcona |
480 minutes == 28800 seconds == 8 hours, so it looks like an ou setting is still most likely to me. |
12:41 |
Dyrcona |
Also, should someone walk away from a workstation and leave it logged in for 8 hours? |
12:50 |
Dyrcona |
Back to our XMPP issue. From what I can tell the XMPP standard never defined error codes. That looks like possibly an Ejabberd extension. Neither RFC 3920 nor 6120 say anything about errors having a code attribute. |
12:59 |
gmcharlt |
calling out bug 1971745; curious of anybody else on 3.7+ who has OUs with hold shelfs having hundreds of holds are running into this |
12:59 |
pinesol |
Launchpad bug 1971745 in Evergreen "Holds shelf list can fail to retrieve results" [Undecided,New] https://launchpad.net/bugs/1971745 |
13:01 |
dluch |
DIG Meeting starts in an hour, here in IRC! |
13:08 |
|
mantis joined #evergreen |
13:11 |
Dyrcona |
OK. I've definitively tracked it down to changes from erlang-p1-xmpp 1.4.4 to erlang-p1-xmpp 1.5.6. The older library included a numeric code in the errors, though I can't find anything about that in the RFCs. |
13:11 |
Dyrcona |
Should this be discussed at the next developers' meeting? |
13:25 |
Dyrcona |
https://github.com/processone/xmpp/commit/6fc29dce5ef566b9dd6245f0b3619913756a1739 |
13:51 |
jeff |
gmcharlt: we rarely use that interface, but I can try testing here to see if we run into the issue (we might not due to the s2s particular you mentioned) |
13:51 |
jeff |
amusingly, the "atomic works" is probably the exact opposite of what our 1.x holdshelf experience was. :-) |
14:00 |
dluch |
#startmeeting 2022-05-05 - Documentation Interest Group Meeting |
14:00 |
pinesol |
Meeting started Thu May 5 14:00:09 2022 US/Eastern. The chair is dluch. Information about MeetBot at http://wiki.debian.org/MeetBot. |
14:00 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
14:00 |
pinesol |
The meeting name has been set to '2022_05_05___documentation_interest_group_meeting' |
14:00 |
dluch |
#topic Agenda |
14:00 |
dluch |
#info The agenda can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20220505-agenda |
14:00 |
dluch |
#info The agenda and minutes from the March meeting can be found here: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meetings:20220203-agenda |
14:00 |
dluch |
Welcome everyone! Today's meeting will be business, followed by collaboration and working on documentation, if there's time. |
14:01 |
dluch |
#topic Helpful Information: Documentation contributions and collaboration |
14:01 |
dluch |
#info You can find the Documentation Needs List at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:documentation_needs |
14:01 |
dluch |
#info DIG Roles can be found at https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:digparticipants |
14:01 |
dluch |
#topic Introductions |
14:01 |
dluch |
Please paste "#info <username> is <name>, <affiliation>" to identify who you are and what organization, if any, you represent. |
14:01 |
dluch |
#info dluch is Debbie Luchenbill, MOBIUS |
14:01 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative |
14:02 |
dluch |
I'm going to give folks another minute or so, but if it's just you and me, jihpringle, I don't think we need to meet, lol (unless you want to) |
14:03 |
mantis |
#info mantis is Gina Monti, Bibliomation (will somewhat be around for this meeting) |
14:03 |
jweston |
#info jweston is Jennifer Weston, Equinox |
14:04 |
dluch |
Thank you all for coming! If you come in later, feel free to introduce yourself when you arrive. |
14:04 |
dluch |
#topic Old and Ongoing Business |
14:04 |
dluch |
#info Check-in - How's everyone doing? |
14:05 |
mantis |
Doing pretty good with conference planning |
14:05 |
jihpringle |
we may finally be done with winter, so pretty good! |
14:05 |
dluch |
We have been having lots of rain and I definitely didn't expect to have my furnace on at the beginning of May |
14:05 |
jweston |
more crazy days! and weather wise -- summer is here in NC |
14:05 |
dluch |
mantis: awesome! |
14:06 |
dluch |
I think wild weather is going to be the norm now |
14:06 |
dluch |
#info Previous Action Items |
14:07 |
dluch |
I think these will probably be quick. |
14:07 |
dluch |
I'll take them in order... |
14:07 |
dluch |
1. alynn26 and Bmagic will investigate some possible options for adding pdf generating to our documentation site |
14:07 |
dluch |
Bmagic is off today, so I'll carry this one again. |
14:07 |
dluch |
#action Bmagic will investigate some possible options for adding pdf generating to our documentation site. |
14:08 |
dluch |
2. alynn26 will look into Evergreen's Antora CSS to see why anything that is a heading 4 ==== or lower is not rendering properly formatted in Antora. Example: "Sort By Geographic Proximity" at https://docs.evergreen-ils.org/eg/docs/latest/opac/using_the_public_access_catalog.html#_viewing_a_record |
14:08 |
dluch |
I think that, probably, someone else needs to take on this action item. Any volunteers? |
14:08 |
jweston |
dluch: I'll take it |
14:08 |
dluch |
jweston++ |
14:09 |
dluch |
#action jweston will look into Evergreen's Antora CSS to see why anything that is a heading 4 ==== or lower is not rendering properly formatted in Antora. Example: "Sort By Geographic Proximity" at https://docs.evergreen-ils.org/eg/docs/latest/opac/using_the_public_access_catalog.html#_viewing_a_record |
14:09 |
dluch |
3. dluch will get the October and February recordings processed and posted. |
14:09 |
dluch |
Ugh, I did not get to this after the last meeting, after all. I should finally be able to after I have next week off. |
14:09 |
dluch |
#action dluch will get the October and February recordings processed and posted. |
14:10 |
dluch |
4. jihpringle will blurb some completed documentation and send it out to General for review |
14:10 |
jihpringle |
have not done this yet |
14:10 |
dluch |
jihpringle? I don't think she's had time to do this yet? |
14:10 |
jihpringle |
when we talked about it I was super clear about what we wanted to do, and now less so |
14:10 |
jihpringle |
I think I need to watch the recording :) |
14:11 |
dluch |
jihpringle++ should we carry it or try and redefine after I get the recordings done? |
14:11 |
dluch |
:-) |
14:11 |
jihpringle |
lets re-visit it after the recordings are done |
14:11 |
dluch |
Sounds good! |
14:11 |
dluch |
5. dluch will get in touch with the core committers group to get mantis, Bmagic, and alynn26 set up as documentation committers |
14:12 |
dluch |
This was done before the end of the last meeting! Thanks, Dyrcona! |
14:12 |
dluch |
Dyrcona++ |
14:12 |
mantis |
Dyrcona++ |
14:12 |
jweston |
Dyrcona++ |
14:12 |
jihpringle |
Dyrcona++ |
14:12 |
dluch |
#info Docs organization: Progress |
14:13 |
dluch |
How are things going? Things have been nuts here so I haven't done anything. |
14:13 |
jweston |
same here -- suggestion to have a call sometime before con to prioritize what we want to work on during hackaway |
14:13 |
dluch |
Seems like things have been pretty busy for everyone? |
14:13 |
jihpringle |
yes, I'm not sure what happened to April :) |
14:14 |
dluch |
jweston: good idea |
14:14 |
dluch |
jihpringle: Right?!?! |
14:14 |
jihpringle |
yes, +1 to jweston's suggestion |
14:14 |
jweston |
April lasted approximately 3 days and now it's May |
14:14 |
dluch |
#action DIG will have a call prior to the conference to talk about the hackfest priorities |
14:15 |
dluch |
LOL, so true, jweston! |
14:15 |
jihpringle |
can we pick a date today or soon? My calendar is already filling up between now and the conference |
14:15 |
dluch |
So, we weren't going to have a June Zoom meeting because of the conference. Do we want to use that day? |
14:15 |
dluch |
June 2 |
14:16 |
jweston |
+1 to June 2 |
14:16 |
jihpringle |
+1 to June 2 |
14:16 |
jihpringle |
(I still have it blocked off for the original DIG meeting) |
14:17 |
dluch |
Cool, let's plan on then, then. :-) I'll get something scheduled and sent out later today |
14:18 |
dluch |
#info DIG call will be on June 2 at 1 p.m. CT / 2 p.m. ET |
14:18 |
dluch |
And that leads into... |
14:18 |
dluch |
#info Conference docs-related presentation(s) |
14:18 |
dluch |
There's been a lot of action here in the last couple of months. Several docs presentations have been combined into a pre-conference. Presenters, want to talk about anything? |
14:19 |
mantis |
Originally we wanted to do separate presentations but with the need of pre-conference ideas, we decided to make one big one for the pre-conference |
14:19 |
mantis |
I think we're going over an intro to DIG, what contributing looks like, and how to contribute |
14:19 |
mantis |
Just off the top of my head |
14:19 |
jihpringle |
yes, and talk about the doc re-org as well |
14:19 |
dluch |
mantis++ |
14:20 |
jihpringle |
I think we're at the stage of needing to have a call among the presenters and figure out who is going to do what |
14:20 |
dluch |
jihpringle++ |
14:20 |
jihpringle |
if there's anything DIG related anyone wants us to cover, let us know |
14:21 |
jweston |
I'm not part of the presentation group -- and you're all marvelous! (if there is anything I can contribute, just let me know) |
14:21 |
dluch |
Do you want me to plan that call or will one of you? |
14:21 |
mantis |
I think we can pick a date and time among ourselves |
14:21 |
dluch |
+1 jweston! |
14:21 |
mantis |
We're already discussing via the email chain anyway |
14:21 |
mantis |
Unless anyone feels differently |
14:21 |
dluch |
Okay, cool |
14:22 |
jihpringle |
agreed |
14:23 |
jihpringle |
I think the presentation is part here's how DIG works, here's the cool things we're doing, and now that you know these things come join us :) |
14:23 |
jweston |
jihpringle++ great description |
14:23 |
dluch |
Also conferencey, for any new folks reading this later, the documentation Hackfest is at the same time as the developer Hackfest, and you can go between. Most of it will be very casual, but we will have some documentation priorities, as mentioned above, and experienced folks there to help answer questions. |
14:23 |
dluch |
jihpring++ |
14:24 |
dluch |
Also jihpringle++ |
14:24 |
dluch |
That's all I have for old or ongoing business to discuss. Anything I missed that someone would like to talk about? |
14:24 |
jihpringle |
will people still be able to sign up for the hackfest on the Monday of the conference? |
14:24 |
mantis |
yes |
14:25 |
jihpringle |
awesome, than we can plug that as part of the session as well |
14:25 |
jweston |
also for future folks reading this, the Hackfest is free |
14:25 |
dluch |
Yes! |
14:25 |
jihpringle |
maybe we should be sending an email out to the list in the next few weeks |
14:25 |
dluch |
That's a good idea |
14:25 |
jihpringle |
reminding people that the hackfest includes docs and is free |
14:26 |
jweston |
+1 to email promo |
14:26 |
jihpringle |
I can commit to doing that |
14:26 |
dluch |
Thanks! |
14:26 |
dluch |
jihpringle++ |
14:27 |
jihpringle |
might make sense to wait until the schedule is released and then plug the pre-conference session and the hackfest in one go |
14:27 |
dluch |
Sounds reasonable to me |
14:27 |
jihpringle |
I'll keep an eye out and then send out the plug |
14:28 |
jweston |
jihpringle++ |
14:28 |
dluch |
#topic New Business |
14:28 |
dluch |
#info Documentation to send for review |
14:28 |
dluch |
I'm thinking that perhaps this is a good topic for discussion during the Hackfest. Sound okay? |
14:29 |
jihpringle |
works for me |
14:30 |
dluch |
Is there any other new business we need to discuss? |
14:31 |
jihpringle |
is there anything we want to talk about with 3.9 being released? |
14:32 |
jihpringle |
we don't have a test server yet so I haven't had a chance to look at it, but based on the release notes there's at least a few changes that affect docs |
14:32 |
jihpringle |
like action triggers now being in angular |
14:32 |
dluch |
I also have not had a chance to look at it yet. Good point, though. Definitely some things that will require changes and new screenshots |
14:33 |
jihpringle |
might just be that we need to update the re-org spreadsheet with the doc needs from 3.9 |
14:33 |
jweston |
good stuff! until we've had a chance to test it post-release, should we delay this topic to June call? |
14:33 |
dluch |
jihpringle: That's probably the best way |
14:33 |
jihpringle |
do we want to plan to make this a discussion topic for the hackaway? |
14:33 |
jweston |
+1 to hackaway topic |
14:34 |
dluch |
+2 |
14:34 |
dluch |
oops, lol |
14:34 |
dluch |
+1 |
14:34 |
jihpringle |
and maybe we use the 3.9 changes for our pre-conference session demos |
14:34 |
dluch |
I'll add that to the agenda |
14:34 |
mantis |
+1 |
14:34 |
dluch |
+1 |
14:35 |
mantis |
I was considering just being in the room and doing some of the update projects |
14:35 |
dluch |
That works |
14:35 |
mantis |
Especially since I'll be committing some stuff for the first few times |
14:35 |
jweston |
mantis++ committing stuff |
14:35 |
dluch |
mantis++ |
14:35 |
jihpringle |
mantis++ |
14:36 |
mantis |
power courses through me |
14:36 |
dluch |
Any other new business? |
14:36 |
dluch |
LOL |
14:37 |
dluch |
Hearing none, and knowing we're all super-busy, I'm going to call the meeting. (Feel free to stick around and collaborate, though!) |
14:37 |
dluch |
#info Our next meeting will be June 2 on Zoom, then the Hackfest. And then July 7, on IRC. |
14:37 |
dluch |
Thanks for being here, everyone! |
14:37 |
jweston |
dluch++ thanks for leading |
14:38 |
jihpringle |
dluch++ |
14:38 |
dluch |
jihpringle++ |
14:38 |
dluch |
mantis++ |
14:38 |
dluch |
jweston++ |
14:38 |
dluch |
#endmeeting |
14:38 |
pinesol |
Meeting ended Thu May 5 14:38:17 2022 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
14:38 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-05-05-14.00.html |
14:38 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-05-05-14.00.txt |
14:38 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-05-05-14.00.log.html |
14:38 |
jweston |
dluch++ jihpringl++ mantis++ DIG girl power! |
14:38 |
dluch |
Oh, yeah!! :-D |
14:38 |
Dyrcona |
dluch++ jihpringle++ mantis++ jweston++ dig++ |
14:39 |
mantis |
-Voltron music- |
14:39 |
dluch |
hahaha |
15:00 |
pinesol |
News from commits: LP#1965579: stop gap for negative bills in OPAC <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=8e0b1657e19636ffd3c906e5e7f9c83801c7ccb6> |
15:18 |
|
jvwoolf joined #evergreen |
15:31 |
pinesol |
News from commits: clear miscellaneous.adoc for next release <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=1d25efcefd23e3ed3eae3f1905fc0cea5ff02bc2> |
15:45 |
|
collum joined #evergreen |
17:11 |
|
mmorgan left #evergreen |
18:12 |
|
rjackson_isl_hom joined #evergreen |
18:33 |
|
jvwoolf left #evergreen |
18:57 |
|
jihpringle joined #evergreen |