Evergreen ILS Website

IRC log for #evergreen, 2018-03-01

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
00:19 beanjammin joined #evergreen
00:49 yar joined #evergreen
07:21 rjackson_isl joined #evergreen
08:18 rlefaive joined #evergreen
08:32 rlefaive_ joined #evergreen
08:37 ngf42 joined #evergreen
08:39 rlefaive joined #evergreen
08:40 mmorgan joined #evergreen
08:50 kmlussier joined #evergreen
08:51 Dyrcona joined #evergreen
08:53 kmlussier Looks like it was a late night! dbwells++
09:00 rlefaive joined #evergreen
09:03 JBoyer dbwells++
09:06 agoben joined #evergreen
09:12 rlefaive joined #evergreen
09:14 yboston joined #evergreen
09:17 Dyrcona So, I'm still stumped why I get "save attempt: Transaction begin error" whenever I try to save an authority on my test vm.
09:18 Dyrcona I even upped the pcrud keep alive to 15 seconds, but based on what I saw while doing tail -f, the error comes before the pcrud timeout.
09:26 Dyrcona Nothing happens in the postgres logs, either.
09:27 JBoyer It seems extremely unlikely but anything of note in the ejabberd logs?
09:27 * Dyrcona checks.
09:27 JBoyer I've found something helpful in there maybe once or twice. :/
09:30 Dyrcona Nothing unusual just "Accepted legacy authentication...." and "Close session..." messages.
09:30 miker Dyrcona: is the authority record linked to a bunch of bibs?
09:30 Dyrcona Yeah, I have, too, usually after cranking the logging to 11.
09:30 Dyrcona miker: Yes, 11 bibs or so.
09:31 Dyrcona So, my test environment is just too slow?
09:31 miker that's my thought, yes. if you force a reingest of those 11 records, how long does it take cumulatively?
09:32 miker **cough**queued ingest**cough**
09:32 JBoyer Ideally it will fail outright on one of them because of busted marc pre-is_marc_valid. Seems unlikely though.
09:33 Dyrcona Well, it worked in production where the hardware is more robust. I'll drop it for now.
09:33 JBoyer (Ideally, because 11 is not that many.)
09:33 rlefaive joined #evergreen
09:33 Dyrcona Thought, it failed at least once in production, too.
09:33 Dyrcona s/Thought/Though/
09:38 Dyrcona I find it amusing that PyXMPP seems to have trouble with legacy authentication on Ubuntu 16.04, but OpenSRF doesn't.
09:38 * Dyrcona imagines it will only be worse on Ubuntu 18.04.
09:39 Christineb joined #evergreen
09:40 rlefaive joined #evergreen
09:42 beanjammin joined #evergreen
09:43 JBoyer I thought someone said it was gone in 18? Or maybe just more of a hassle to re-enable?
09:45 rlefaive joined #evergreen
09:45 Dyrcona JBoyer: Yes, something like that. :)
09:46 jvwoolf joined #evergreen
09:47 * Dyrcona attempts to set up Syrup mostly from scratch.
09:54 rlefaive joined #evergreen
09:57 Dyrcona Hoo boy: This version of Django requires Python 3.4, but you're trying to install it on Python 2.7.
09:57 Dyrcona I imagine that Syrup is not gonna work with Python 3.x....
10:00 Dyrcona Looks like I can get by with pyhon-django from packages, though. We'll give that a shot.
10:02 Dyrcona No babel-django package. That might pose a problem.
10:03 Dyrcona There is. Wonder what I messed up in my previous apt search?
10:04 Dyrcona Oh. Duh... django-babel not babel-django. :)
10:08 rlefaive joined #evergreen
10:13 Dyrcona Interesting packages I stumble across while finding the ones I need: PHP parser writteng in Python using ply....
10:16 JBoyer I occasionally still install aptitude just so I can use / to search. (I know there's a command to do it, but it's significantly longer than '/'!)
10:16 dwgreen joined #evergreen
10:16 JBoyer Actually, I bet that's one of the more secure PHP parsers. ;)
10:18 pinesol_green [evergreen|Kathy Lussier] Docs: minor file name change for release notes entry - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7d7736e>
10:19 Dyrcona heh.
10:19 Dyrcona This looks like a showstopper: No local packages or download links found for Pyz3950
10:20 littlet joined #evergreen
10:21 Dyrcona Ok. package index says PyZ3950 exists, but easy_install says it doesn't.
10:23 beanjammin joined #evergreen
10:27 rlefaive joined #evergreen
10:28 Dyrcona pip says it can't find it, either.
10:30 Dyrcona Well, there's always the github repo... :)
10:45 Dyrcona Such confidence in the README: "This might work:"
10:45 bshum Dyrcona: At least it's honest?  :)
10:48 JBoyer Reminds me of the RT install instructions. "Run this command repeatedly until this other command stops giving errors. If that doesn't work search for some of the words in the errors in your package manager."
10:49 JBoyer (I finally got it installed. Then I gave up on it for other reasons.)
10:50 Dyrcona :)
10:53 JBoyer (not because I used it. I still want to but other things are higher on the list than changing helpdesks)
10:54 Dyrcona Hm... If I copy a working Syrup installation folder, I wonder what steps I can skip? Ditto for the database.
11:12 pinesol_green [evergreen|Jason Stephenson] LP#1748466: Fix http -> https /eg/staff rewrite on Apache 2.4. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ba4c864>
11:15 Dyrcona bshum++
11:15 bshum Dyrcona++
11:15 bshum Now I don't have to type out the full https every time :D
11:15 bshum Or risk the error page, anyways
11:20 beanjammin joined #evergreen
11:34 rlefaive joined #evergreen
11:39 remingtron berick: In the Hatch install instructions, seems like the steps under "Install Chrome Extension" can be replaced with "Get it from the Chrome web store", right?
11:41 berick remingtron: the code's been updated already.  i see the downloads page has not..
11:41 berick so..
11:42 berick i'll rebuild the docs and push to the site
11:42 remingtron berick: thanks!
11:45 berick https://evergreen-ils.org/documen​tation/install/INSTALL_Hatch.html updated
11:45 berick thanks for the heads up, remingtron
11:46 remingtron berick++
12:03 JBoyer remingtron++
12:03 JBoyer berick++
12:03 JBoyer Any strong feelings about re-ordering the instructions so all Win and all Linux steps are together? I'm willing to do it if there aren't any objections,
12:05 berick JBoyer: yeah, good idea
12:05 JBoyer I'll take a look at it
12:22 dbs remingtron: any interest in http://git.evergreen-ils.org/?p=wor​king/Evergreen.git;a=commit;h=56771​01cb7fd51584357240ce61ee8ee15cc684e (user/dbs/link_to_optional_developer_additions)
12:25 ohiojoe joined #evergreen
12:26 remingtron dbs: looks good to me. Do you want my signoff, or is verbal signoff enough?
12:36 khuckins joined #evergreen
13:10 jihpringle joined #evergreen
13:39 yboston_ joined #evergreen
13:42 rlefaive joined #evergreen
13:47 dbwells Question for holds experts: is there any typical process where a hold becomes suspended other than a user suspending it?
13:51 ohiojoe hi everyone, just a quick reminder that there is a DIG meeting in 10 minutes
13:51 sandbergja joined #evergreen
13:51 mmorgan dbwells: In our consortium, holds only become suspended by a user (patron or staff member) almost always the patron.
13:52 dbwells mmorgan: thank you
13:56 jlundgren joined #evergreen
13:56 Dyrcona dbwells: There is not automatic process to suspend holds, AFAIK.
13:56 Dyrcona s/not/no/
13:57 Dyrcona It's always a user-driver action.
13:59 dbwells Dyrcona: Okay, thanks.  I have staff asking why certain holds are suspended, and my answer to them is going to be along the lines of "Who can know the ways of the patron?", but I wanted a little assurance.
13:59 jeff calling 1106
13:59 Dyrcona Always fun when it's suspended after the copy goes in transit.
14:00 ohiojoe #startmeeting 2018-03-01 – Documentation Interest Group Meeting
14:00 pinesol_green Meeting started Thu Mar  1 14:00:41 2018 US/Eastern.  The chair is ohiojoe. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00 pinesol_green The meeting name has been set to '2018_03_01___documentatio​n_interest_group_meeting'
14:00 ohiojoe #topic agenda
14:00 ohiojoe #link https://wiki.evergreen-ils.org/doku.php?id=​evergreen-docs:dig_meeting_20180301-agenda
14:00 ohiojoe #topic Introductions: please paste "#info <username> is <name> <affiliation>" to identify who you are and what organization, if any, you represent
14:00 dbwells We used to use transits between different collection desks, but at this point, we're transit free.  Feels good!
14:01 ohiojoe #info ohiojoe is Joe Knueven, Germantown Public Library, Consortium of Ohio Libraries
14:01 jihpringle #info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka)
14:01 kmlussier #info kmlussier is Kathy Lussier, MassLNC
14:01 dluch joined #evergreen
14:01 sandbergja #info sandbergja is Jane Sandberg, Linn-Benton Community College
14:02 abneiman #info abneiman is Andrea Buntz Neiman, Equinox
14:02 dluch #info dluch is Debbie Luchenbill, MOBIUS
14:02 ohiojoe #topic Old Business
14:02 dluch (I'm only here for about 25 minutes, though, because of another meeting)
14:02 ohiojoe #topic Previous action items
14:03 jlundgren #info jlundgren is jeanette lundgren, CW MARS
14:03 ohiojoe I can start this off by saying that I barely got 13 done in time for it to be relevant, my apologies
14:03 Christineb #info ChristineB is Christine Burns BC Libraries Cooperative / SItka
14:04 Christineb my old action item #1 is not complete
14:04 Christineb I've dropped the ball on the status of the web team
14:05 sandbergja ohiojoe: I think that it should be fine; this way it's fresh in peoples' minds.  Did we get enough responses to set a date for the doc hack days?
14:05 rlefaive joined #evergreen
14:05 alynn26 joined #evergreen
14:06 sandbergja I still need to do #9
14:07 ohiojoe We're up to 8 responses on next week and they're still coming in as of a few minutes ago.  I was thinking I would leave it open through early tommorow morning and then call it
14:07 ohiojoe right now Tues March 6th and Thurs March 8th are tied
14:08 kmlussier #link https://doodle.com/poll/5pz9vxkddqgez4gh
14:09 ohiojoe We're only up to 6 responses for April, but I'm less worried about it since it's a few weeks away..
14:09 ohiojoe thank you Kathy :-)
14:09 alynn26 #info alynn26 is Lynn Floyd, Anderson County Library, SCLENDS
14:09 pinesol_green [evergreen|Dan Wells] LP#1748924 Enhanced Billing Timestamp Support - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=73a8eaa>
14:09 pinesol_green [evergreen|Dan Wells] LP#1748924 Upgrade script for expanding billing timestamps - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=ec2cb1a>
14:09 pinesol_green [evergreen|Dan Wells] LP#1748924 Add release notes - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=341ac34>
14:09 pinesol_green [evergreen|Dan Wells] LP#1748924 Disable materialized summary updates in upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2eb265e>
14:09 pinesol_green [evergreen|Jeff Godin] LP#1748924 Stamping upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=425bc5e>
14:12 ohiojoe I'm still behind on 4, 7 & 10 as regards action items..
14:12 jihpringle I'm still working on 11 and 12
14:13 * kmlussier needs to defer #3 until next time. Sorry! I keep forgetting about it.
14:13 alynn26 I've only heard good things about the redesign of the docs.   It's been usefull as we are upgrading to 3.0 I can just share a section.
14:13 jihpringle with #12 dluch let me know that we can probably put a DIG handout in the conference packets
14:14 jihpringle we'll need to mail them copies in advance
14:14 dluch Yep!
14:14 kmlussier alynn26: Yay!
14:14 jihpringle dluch++
14:14 jihpringle I'm planning on finishing the draft today and then could send it out to the DIG mailing list for edits
14:15 ohiojoe excellent..  I'd be willing to print and mail them if need be
14:15 jihpringle ohiojoe: great, I was just about to ask
14:16 jihpringle I figure it'll be easier if they're mailed within the US
14:16 ohiojoe oh yeah..  cheaper at least, if nothing else
14:16 jihpringle and no chance of things getting delayed at the border
14:17 jihpringle do we want/can we put the EG logo on the handout?
14:17 dluch I don't see why we couldn't, since DIG is an "official" group in the community
14:17 alynn26 I would say yes.
14:18 jihpringle is there someone with the logo handy that could add it to the draft?
14:18 kmlussier Yes, please do add the logo.
14:18 alynn26 I can add it, or send you a link to it.
14:18 kmlussier They're also available here - https://evergreen-ils.org/trademark-policy/
14:19 abneiman kmlussier beat me to it
14:19 jihpringle perfect, I'll grab it from there and add it
14:19 jihpringle thanks :)
14:19 kmlussier abneiman: Ha! Better luck next time!
14:19 ohiojoe so, that is all encompassed in #12, so I can leave it as is..
14:21 ohiojoe #action ohiojoe will snail mail DIG handouts to the 2018 conference hosts for inclusion in the conference packets
14:22 ohiojoe with that, do we have anything more to say about the previous action items?  including the ones directed at all of us?
14:22 Christineb we have 144 people subscribed to the Evergreen Youtube Channel
14:23 dluch Nice!
14:23 Christineb I think that probably covers #6 :)
14:26 ohiojoe_ joined #evergreen
14:26 ohiojoe_ sorry about that, my little corner of Ohio just lost power for 10 seconds
14:26 kmlussier :)
14:28 dluch * dluch waves and is off to the next meeting
14:29 * alynn26 wondering if Ohiojoe has lost power again.
14:29 ohiojoe_ ok, I think I'm back...
14:29 ohiojoe_ am I back?
14:29 Christineb yes you are back
14:30 ohiojoe_ yes!
14:30 alynn26 looks like it for right now.
14:30 Christineb :)
14:30 ohiojoe_ lol
14:30 ohiojoe_ anyway, were we done with previous action items?
14:30 alynn26 yes
14:30 ohiojoe_ ok, moving along
14:30 ohiojoe_ #topic Ongoing Business
14:30 ohiojoe_ #topic Progress on documenting new features in Evergreen 3.0 (and previous) and the Web client Web Client docs
14:32 Christineb Sitka is upgrading in May so we are getting ready to do a lot of doc work and videos
14:33 alynn26 Same here.  I know a have a the Library Settings Editor edited.  Just not quite ready to commit yet.
14:34 dbwells remingtron isn't at this meeting, but he is working with two of our student workers to complete some of the web client docs, so you should see some results of that soon.
14:34 alynn26 Also working on the Receipts and making sure those are correct with the edits from PINES.
14:37 ohiojoe_ excellent to hear so much going on   :-)
14:39 ohiojoe_ any other discussion here?
14:40 alynn26 no
14:40 ohiojoe_ #topic Progress on documentation launchpad bugs
14:40 ohiojoe_ #link https://bugs.launchpad.net/evergr​een/+bugs?field.tag=documentation
14:41 ohiojoe_ #link https://bugs.launchpad.net/evergreen/+bug/1642023
14:41 pinesol_green Launchpad bug 1642023 in Evergreen "Docs: Web Client Print / Receipt Templates" [Medium,Triaged]
14:41 ohiojoe_ #link https://bugs.launchpad.net/evergreen/+bug/1494736
14:41 pinesol_green Launchpad bug 1494736 in Evergreen "Docs: Self Check docs additions" [Undecided,New]
14:41 ohiojoe_ #link https://bugs.launchpad.net/evergreen/+bug/1744358
14:41 pinesol_green Launchpad bug 1744358 in Evergreen "Fix and improve Action Trigger Reactor docs" [Undecided,Confirmed]
14:41 ohiojoe_ #link https://bugs.launchpad.net/evergreen/+bug/1426120
14:41 pinesol_green Launchpad bug 1426120 in Evergreen "Documentation: Best-hold selection Sort Order options" [Undecided,New] - Assigned to Josh Stompro (u-launchpad-stompro-org)
14:43 alynn26 I'm working on bug 164202
14:43 pinesol_green Launchpad bug 164167 in git-core (Ubuntu) "duplicate for #164202 git-core fails to install" [High,Fix released] https://launchpad.net/bugs/164167
14:43 alynn26 its bug 1642023
14:44 pinesol_green Launchpad bug 1642023 in Evergreen "Docs: Web Client Print / Receipt Templates" [Medium,Triaged] https://launchpad.net/bugs/1642023
14:44 alynn26 Hopefully i'll have it finished next week.
14:45 ohiojoe_ alynn26++
14:46 alynn26 I just finished all of my receipts templates.
14:49 ohiojoe_ anything else here?
14:50 ohiojoe_ #topic New Business
14:50 ohiojoe_ does anyone have any new business to bring up?  (feels so strange getting through a full agenda..)
14:50 jihpringle yes, our participants page
14:51 jihpringle https://wiki.evergreen-ils.org/doku.p​hp?id=evergreen-docs:digparticipants
14:51 jihpringle I think it's a bit out of date
14:52 ohiojoe_ I remember stumbling across it back when I was a going to offer to facilitate..   it could really use some updating
14:53 alynn26 Maybe we send it out to the dig list for everyone to check and update.
14:53 kmlussier At this point, I think we only have the facilitator, release coordinator, and conversion coordinator roles.
14:53 kmlussier Jane is the release coordinator now. I can update that.
14:53 jihpringle if we send it out to the DIG list should we be removing anyone who doesn't respond from the participants list?
14:54 kmlussier I don't think we had much success with the other roles.
14:55 remingtron remingtron: I vote for only moving participants who explicitly "retire" from DIG, like yboston did.
14:55 ohiojoe_ I was thinking we could either remove them, or move them into a sort of "former active participants" area at the bottom
14:55 remingtron #info remingtron is Remington Steed, Hekman Library (Calvin College)
14:55 remingtron ohiojoe_: there is exactly such a section already
14:56 alynn26 I like the moving idea.
14:56 ohiojoe_ I've gotta remember to scroll down all the way..  lol
14:56 abneiman +1 to moving them to inactibe
14:56 ohiojoe_ so, move those who don't respond into past participants?
14:57 jihpringle sounds good to me
14:57 ohiojoe_ ok, unless someone else wants to, I'll send out said emails and take a stab at updating the page..
14:57 khuckins_ joined #evergreen
14:58 jihpringle ohiojoe++
14:58 ohiojoe_ while we're still here, do we know if the list of members with access to edit the main Git repo is up to date?
14:58 kmlussier One of the git admins would know.
14:58 kmlussier That would be gmcharlt, dbs or Dyrcona .
14:59 ohiojoe_ ok, I'll ask them..
14:59 gmcharlt ohiojoe_: docs?
14:59 ohiojoe_ #action ohiojoe will update the DIG participants page and make an effort to contact listed active members in the process
15:00 ohiojoe_ gmcharlt:  yeah, the official docs in the main Git repository
15:00 ohiojoe_ with that, thank you everyone
15:00 ohiojoe_ #end meeting
15:00 ohiojoe_ #endmeeting
15:01 kmlussier Adding a note that in addition to the wiki page, the list of participants needs to be updated in the official docs too - http://docs.evergreen-ils.​org/3.0/attributions.html
15:01 gmcharlt ohiojoe_: the following folks have access (in addition to all of the core committers): rsoulliere, ysuarez, Hilary Caws-Elwitt, akilsdonk, rsteed, stompro, sandbergja, snf jpresley
15:01 gmcharlt s/snf/and/
15:02 ohiojoe_ hmm..  it appears that my power outage quirk is making ending the meeeting difficult..  lets see if dropping out and coming back in would help
15:02 ohiojoe_ gmcharlt:  thank you   :-)
15:02 kmlussier ohiojoe_: I think if you change your nick back to ohiojoe, it would work.
15:02 kmlussier Type /nick ohiojoe
15:03 ohiojoe ahh
15:03 ohiojoe #endmeeting
15:03 pinesol_green Meeting ended Thu Mar  1 15:03:12 2018 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
15:03 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2018/evergreen.2018-03-01-14.00.html
15:03 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2018/evergreen.2018-03-01-14.00.txt
15:03 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2018/evergreen.2018-03-01-14.00.log.html
15:03 ohiojoe kmlussier++
15:04 ohiojoe I'm still a relative novice at channel commands
15:09 kmlussier ohiojoe: Yeah, it takes some time to get used to.
15:10 JBoyer dbwells, I wanted to reply sooner but didn't want to interrupt the meeting. I think the placement and phrasing of the Suspend Hold? option confuses some patrons and they just assume it's another thing in the list of 'Yes,' options that they usually have checked above. (email, phone, etc.)
15:11 dbwells JBoyer: Yes, that's a good point.
15:11 JBoyer We've heard of at least one case like that since upgrading, local staff eventually figured it out but the patron managed to suspend 5-6 holds in a row
15:12 kmlussier A while ago, I had some ideas on improving the layout out of the Place Hold page to make it easier for patrons to understand. I should dust off those ideas at some point.
15:12 JBoyer kmlussier++
15:12 JBoyer ux++
15:13 * kmlussier almost wants to work on it now, but has other work to catch up on. :(
15:13 kmlussier other_work--
15:14 JBoyer Here's one that's tons of fun: Has anyone else run into web client workstation registrations just "going away" in the middle of doing something? As in, you are logged in, registering a user, say, and then click Save and are punted to the "register your workstation" page...
15:14 JBoyer I feel that. I had Some Ideas yesterday about Inventory. Instead I did not do that.
15:15 * JBoyer vanishes to re-register said workstation...
15:15 jeff JBoyer: and i suppose it's not something you can reproduce in a predictable fashion?
15:23 JBoyer I feel like I have a very reproducible test case: Open a new tab to do some reference help, clear your history after helping user, return to web client, fall over.
15:23 * JBoyer puts head in hands
15:23 mmorgan joined #evergreen
15:25 bshum That... hmm
15:28 JBoyer That would be something I'd like to see Hatch possibly used for. Always storing workstations if it's installed and available and always queried for that if it's available and the browser is fairly "bare"
15:28 bshum That just makes me question what a "workstation" is when the application can be web accessed from whatever
15:28 JBoyer It is helpful to have a name to go with a system, and to prevent anyone from logging in just anywhere.
15:29 JBoyer But this can't go on forever in any case.
15:30 bshum Well, you mean if you were to check which workstation was in the log that performed an action and it was named something funky that didn't match your expectations?
15:30 bshum Leading you to conclude the account had been used to setup a workstation somewhere unexpected
15:30 bshum But in that case, I'd already be suspecting the account in question to be compromised
15:30 bshum So what is a "workstation" good for?
15:31 bshum as opposed to just tracking more details about the user accountwho's performing the action
15:31 Dyrcona Well, the workstation_ou is used to determine where things happen.
15:31 Dyrcona So, if we eliminated the notion of workstation, we'd need another way to figure out where things are circulated, etc.
15:33 bshum True, now I'm trying to remember how it works in Koha... I think you choose which library you log in as when you sign on
15:33 JBoyer bshum, what I meant was if the browser doesn't have any workstations registered but hatch is available, always query hatch and ask if there are any workstations stored there. Then populate the local list from that.
15:34 Dyrcona And, users would complain that they have to choose every time and is there a way we can store that, hence workstation....
15:34 JBoyer If hatch isn't installed or doesn't return anything, behave as usual today (dump them on the reg screen on login)
15:35 Dyrcona JBoyer: I think bshum got that point. He's musing publicly on something he mentioned to me in private. :)
15:35 JBoyer Ah. Couldn't tell if I just did a poor job the first time.
15:36 bshum JBoyer: I got what you were saying, I just haven't done any Hatch toying so I'm thinking from the "what if I don't have Hatch" perspective :D
15:36 JBoyer But this isn't a new existential crisis, xulrunner was just a web browser, albeit and old, ugly one. :)
15:36 JBoyer Then clear your cache at your own risk. ;)
15:37 bshum Just have to use different browsers for stuff :)
15:37 bshum This one, this is for Evergreen.  Put a shortcut that's called Evergreen, they'll get it...
15:37 bshum :D
15:37 bshum This one, this is for Reference
15:38 Dyrcona Oh, but that's "too hard/incovenient/whatever."
15:38 JBoyer We already have places doing that. Firefox is what they like, Chrome is their staff client.
15:39 Dyrcona Has anyone tried master in either browser lately? I've opened bugs.
15:39 kmlussier I've been working on a server with master of this morning. In Chrome.
15:39 JBoyer I'm planning to install it the middle of next week.
15:39 kmlussier master *as of* this morning.
15:40 Dyrcona I couldn't even login with Firefox 58.0.2.
15:40 Dyrcona Offline didn't work for me at all, since last week.
15:41 kmlussier Can you log in here? - https://mlnc3.noblenet.org/
15:41 kmlussier admin / evergreen123
15:42 * berick can login to noblenet fwiw
15:42 Dyrcona Nope.
15:42 Dyrcona berick: With Firefox?
15:43 Dyrcona Maybe it's a Firefox on Ubuntu thing.
15:43 berick ah, chrome
15:43 * Dyrcona goes back to figuring out Syrup.
15:43 kmlussier I logged in with Firefox 58.0.1
15:44 Dyrcona Well, I've not been able to login with 58.0.2 on any server running master since Monday, at least.
15:44 bshum Hmm, websocket failure for me on Firefox 58.0.2
15:44 berick yeah, same here, had to do the FF-special step through SSL warnings
15:44 kmlussier Maybe I should update my Firefox and try again.
15:45 berick click through -> https://mlnc3.noblenet.org:7682/
15:45 berick chrome doesn't make you do that
15:45 bshum berick: Ah, the joys of SSL exception handling
15:45 Dyrcona Oh, that's right.
15:46 kmlussier Oh, that's right. I never fixed that SSL issue.
15:46 Dyrcona The "joys" of web development..... Not!
15:47 * Dyrcona really returns to mucking about with Syrup.
15:48 * berick is excited about all the new billing work
15:49 kmlussier Yes, me too!
15:49 JBoyer How lovely. We have an "enterprise-y" install of FF 52.5 that can't be upgraded and barfs on trying to connect to the IndexedDB, so after logging in it immediately dies. (I'm able to get to the login page and past it on noblenet, then my browser croaks on the workstations page.)
15:50 JBoyer Doesn't seem to like upup either.
15:50 csharp ick
15:50 * csharp read "barfs" as "bar FS" - a new type of *nix filesystem
15:51 JBoyer This is why some of my stuff comes from home, especially Hatch work. (our Java install doesn't put any registry keys in place and isn't detected. *crying face emoji* )
15:51 JBoyer csharp++
15:52 khuckins__ joined #evergreen
15:52 Dyrcona csharp: barfs... a lesser btrfs which is a lesser zfs.
15:52 csharp heh
15:52 JBoyer Given how common silly names are across the OSS world I'm surprised there's not more than one barfs to choose from, except that FS work is crazy hard.
15:53 Dyrcona They need tonic indexes in postgres.
15:53 berick and juice
15:53 JBoyer berick++
15:53 Dyrcona :)
15:54 csharp with my mind on my DB and my DB on my mind
15:54 berick laid back
15:54 JBoyer I'm thinking neither of those options would actually speed up retrieval, only slow things down. (but you don't care so much!)
15:55 * JBoyer would like to do something with ridin' dirty and dirty cache pages but gives up.
16:36 jlundgren left #evergreen
16:39 yboston joined #evergreen
16:49 mmorgan1 joined #evergreen
16:50 Stompro Do the 2.12 release notes work for anyone else?  They look messed up to me.  https://evergreen-ils.org/documentat​ion/release/RELEASE_NOTES_2_12.html
16:51 khuckins__ I'm seeing plain xml
16:52 bshum Yeah that doesn't look right...
16:52 bshum One of the levels is wrong in the source doc
16:53 bshum Well a couple of levels
16:54 Stompro I remember it being fine a few months ago.. and the release notes in the official docs look fine.
16:55 bshum Stompro: Well they change every time someone adds the point release
16:55 bshum So maybe when 2.12.10 was made, something went wrong.
16:55 bshum Or...
16:55 bshum Something else is wrong
16:55 bshum I'm checking a git blame now on the rows that are borked
16:56 bshum Specifically, lines 466 and 482
16:58 bshum Could be that those have been broken awhile actually, lol
17:01 bshum Yeah, the broken generation is from 2.12.2 time; so several releases back
17:01 csharp @blame git blame
17:01 pinesol_green csharp: git blame is why we can never have nice things!
17:01 bshum Not sure why the currently generated file is borked
17:01 bshum But I can put a new file into place over it
17:06 bshum Stompro: Refresh and it should be fine now.
17:06 Stompro Looks good bshum++
17:07 mmorgan1 left #evergreen
17:10 dbs JBoyer: did anyone suggest incognito mode for the Reference workflow, to avoid clearing historyÉ
17:14 bshum So, for that level issue, looks like it's complaining cause it wants it to be ^^^ instead of +++ for those lines.  It'll still generate fine as that level, but it's just warns and complains.  Not a dealbreaker I guess I'll leave it alone :)
17:14 * bshum wanders
17:14 dbs bshum++
17:14 dbs @later tell remingtron I can push it myself, wasn't sure if DIG was being more rigorous about doc commits these days
17:14 pinesol_green dbs: The operation succeeded.
17:15 khuckins_ joined #evergreen
17:18 pinesol_green [evergreen|Dan Scott] Link to the Optional: Developer Additions step - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7a78bdf>
17:23 Bmagic When Evergreen calculates the due date for a circulation during checkout, where does it incorporate the timezone? I am seeing due dates that are a whole day off. It's still 23:59:59 but a day later. The recorded timzone for the due_date is -05 but the recorded timezone on xact_start is -06. What could make the due date record in a different timezone from the transaction start?
17:25 berick Bmagic: bug 1635737
17:25 pinesol_green Launchpad bug 1635737 in OpenSRF "Daylight savings incorrect due dates" [Wishlist,Confirmed] https://launchpad.net/bugs/1635737
17:25 Bmagic I looked at that and I don't think that is related
17:26 Bmagic All application servers and database servers are reporting EST timezone when issuing "date" in bash. postgresql.conf is configured to "localtime"
17:27 berick Bmagic: ah, well, if the date falls on the other side of the DST crossover it gets the other "timezone"
17:27 csharp yeah, seems like it would have to be DST-related
17:27 Bmagic oh boy!
17:27 csharp (March 11)
17:27 csharp always sneaks up on us
17:28 berick Bmagic: that's not by itself a bad thing, but can be confusing
17:28 Bmagic and the result is that it's due a day later?
17:29 berick the day later issue sounds a whole lot like the bug I posted
17:30 Bmagic so that bug is strictly 3.0.3?
17:30 csharp must be "today at 23:59 + loan duration" where that pushes it into the next day (00:59)
17:30 csharp or something like that
17:31 berick Bmagic: "Evergreen 2.11, affects all versions.
17:32 Bmagic I am not seeing the hours off. I am seeing exactly 1 day
17:32 Bmagic with the time still 23:59:59
17:33 Bmagic the due date is calculated upon insert with a trigger in the database? Funny though, even when checking something out with a specific due date, it still adds one day
17:35 berick the trigger bumps it out to the end of the due day, IIRC, for day-granular circ intervals
17:37 tji joined #evergreen
17:37 Bmagic it looks up lib.timezone and coalesce with CURRENT_SETTING('timezone')
17:39 berick oh, huh, it's smarter than I thought.
17:39 * berick shuts up now
17:41 Bmagic I don't see lib.timezone anywhere, config.global_flag and config.org_unit_setting
17:43 Bmagic I am starting to think that this is really DST
17:44 Bmagic I believe the database is correct and the staff client is wrong
17:44 berick config.org_unit_setting_type has lib.timezone on my dev machine
17:45 Bmagic berick - I see it on another DB running 3.x - not on the DB running 2.12.x
17:47 berick oh
17:47 berick gotcha
17:47 Bmagic berick: sorry, I was looking at a different bug 1750916
17:47 pinesol_green Launchpad bug 1750916 in Evergreen "3.0.3 due date in different time zones" [Undecided,New] https://launchpad.net/bugs/1750916
17:48 berick ah
17:53 csharp has anyone experimented with redis over memcached?
17:54 * csharp was pointed to https://www.infoworld.com/article/3063161/nos​ql/why-redis-beats-memcached-for-caching.html and is intrigued
19:20 tji left #evergreen
23:12 jeffdavis joined #evergreen
23:12 ejk joined #evergreen
23:14 eby joined #evergreen
23:15 troy__ joined #evergreen
23:17 Glen joined #evergreen
23:29 sard joined #evergreen
23:29 kipd joined #evergreen

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat