Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Thursday, October 6th, 2011

< Wednesday, October 5th, 2011Raw Log FileFriday, October 7th, 2011 >
#TimeNickMessage
#01:13:53Callender has quit IRC
#01:40:40Callender has joined #evergreen
#01:59:58Callender has quit IRC
#02:00:27Dmagick_ has quit IRC
#02:00:33phasefx has quit IRC
#02:00:39leed has quit IRC
#02:01:00mtate has quit IRC
#02:05:46youdonotexist has quit IRC
#03:21:59bjwebb has joined #evergreen
#03:54:12phasefx has joined #evergreen
#04:09:16Callender has joined #evergreen
#07:48:33wolf29 has joined #evergreen
#07:48:47wolf29Good Morning!
#07:49:21collum has joined #evergreen
#08:08:32Dmagick has joined #evergreen
#08:08:57Dmagick has joined #evergreen
#08:25:33mrpeters-isldbs++ thanks for the security patch
#08:30:01mrpeters-islone typo though -- should be ./configure --prefix=/openils --sysconfdir=/openils/conf i think not -sysconf/-prefix
#08:31:25wolf29Is this the right syntax to change the user on the staff-client? It is not working. perl Open-ILS/src/support-scripts/eg_db_config.pl --admin-user staff --admin-pass ssecret
#08:34:27mrpeters-islcan i compile oils_auth.so on one system, and distribute to all of my bricks with that one file or do i need to build from the tarball on every server?
#08:35:03adbowling-isl has joined #evergreen
#08:39:14tsberemrpeters-isl: If the bricks are all running identical configs you can probably skip a few steps
#08:40:53mrpeters-islyeah, they are
#08:41:06mrpeters-islso i figured i could just build it once and then distribute it
#08:49:20Dyrcona has joined #evergreen
#08:56:46mrpeters-islis there anything visible to the user saying they've been locked out after 10 attempts?
#08:56:54mrpeters-isli can still sit here and hammer away and just get a login failed
#08:56:54tsbereNope
#08:57:05mrpeters-islbest way of testing then?
#08:57:08tsbereGiving an indication would be telling an attacker they hit the limit
#08:57:14mrpeters-islyeah, agreed
#08:57:23tsbereI use srfsh and the login command.
#08:57:32tsbereFirst hit I use the correct password to make sure things let people in
#08:57:41tsbereThen I drop the last letter of the password for 10 attempts
#08:57:48tsbereThen I go back to the correct password. It should fail me.
#08:57:56tsbereThen I wait a couple of minutes and try again, it should let me in.
#08:58:04mrpeters-islew yeah i can't get in with a good user...thats not good
#08:58:59wolf29tsbere: is the system checking the IP from which the hammerings are coming?
#08:59:17tsberewolf29: No.
#08:59:45mrpeters-islah, know what...i bet the server i built this on has a different distro than my production server
#09:00:03wolf29tsbere: that would clear issues of a malicious user locking everybody - everywhere out of the system
#09:00:28tsberewolf29: But would make a botnet bruteforcing a lot easier.
#09:01:07tsbereBesides, the auth code doesn't know where the request came from. It could be internal, it could be TPac, it could be the HTTP translator, it could be some other service that happens to talk XMPP to the system, etc.
#09:02:09gmcharlt has joined #evergreen
#09:04:28wolf29hmmm if the users logging in were xmpp users, instead of entirely internal-to-eg users, wouldn't the botnet angle just be cut out? I am looking into XMPP (just for fun) This might just be a solution looking for a problem
#09:05:03tsbereThat would be a horror show due to how the system uses XMPP
#09:05:13tsbereAlso, I don't want to open XMPP auth up to the outside.
#09:05:42wolf29Yeah. That could be a mess
#09:06:37mrpeters-islyeah, i can't get this working :(
#09:06:48eeevilin the very early days, there was app-to-app auth/authz ... no EG-level users, but a layer between xmpp and EG
#09:06:56mrpeters-islpossible memcache has to be restarted too?
#09:07:23tsberememcache shouldn't be an issue
#09:07:48mrpeters-islhmm...i just get LOGIN_FAILED "stacktrace":"oils_auth.c:714"
#09:08:01mrpeters-islwith the old oils_auth.so it's success
#09:08:51eeevilbut the cost was too high, so we killed that in preference to telling the router about client domains and restricting app registration
#09:14:37tsbere has figured out how to make recall holds automatically drop into cataloging status :D
#09:26:36Dyrcona grumbles something about meetings.
#09:28:53mtate has joined #evergreen
#09:28:54sal_ has joined #evergreen
#09:30:49leed has joined #evergreen
#09:44:00dbs has joined #evergreen
#09:44:00dbs has joined #evergreen
#09:49:44yboston has joined #evergreen
#09:53:46mrpeters-islanyone ever tinkered with turning off the "did you mean?" suggestions in the OPAC?
#09:53:59mrpeters-islerr..."maybe you meant"
#09:54:59tsbereI haven't. You feel there is a need?
#09:55:18mrpeters-islapparently...i've been asked to turn it off for some strange reason
#09:55:37mrpeters-isli guess i could just hide the <span>&result.lowhits.did.you.mean; </span>
#09:55:45tsbereTell them you need to update to do so ;)
#09:56:00mrpeters-islhaha finally making progress on that front :)
#10:08:04dbsmrpeters-isl: we've added things to that section of the JSPAC; easy enough to turn it off too
#10:20:40dbstsbere++ # awesome staff client documentation
#10:21:43tsbereIn rigging up force and recall holds to be something other than aliases for "Regular Copy Hold" I am adding two new permissions. Anyone have objections to those permissions being checked based on the copy circ library instead of the pickup library?
#10:33:25jenny1 has joined #evergreen
#10:38:28AaronZ-PLSThinking about automatic updates in 2.1... How does that work in Windows 7 which has a phobia about letting people change files in %PROGRAMFILES% without administrative priviliges (ie: run as administrator)?
#10:39:24tsbereAaronZ-PLS: The installer changes the permissions of the install dir when installing automatic updating.
#10:40:07dbs ran into a "locked down" XP workstation that tried to prevent him from installing the 2.0 client in %PROGRAMFILES%, so he just installed into My Documents instead
#10:41:36AaronZ-PLStsbere:Intresting. I have been using a batch file and wget for our libraries (hackish, but it mostly works) and even whe I change the permissions, Windows 7 will not allow a non-administrative user to update the files in %PROGRAMFILES%\Evergreen Staff Client
#10:42:10tsbere hasn't had anyone report issues
#10:42:49tsbereOf course, the only win7 users I know that do regular updates ARE administrators, and the updater is supposed to ask for elevation when needed.
#10:43:12AaronZ-PLSme: Adds auto updates on Win 7 to the list of things to check after we install a 2.1 test VM
#10:43:41tsbereAaronZ-PLS: The permissions granted are "Everyone -> FullAccess", just so you know.
#10:44:07enhancin has joined #evergreen
#10:44:07dbsHeh, talk about yer security vulnerabilities :)
#10:44:59tsbere has less concern there as he isn't having the client elevate itself under normal circumstances, and in fact at that point the updater doesn't need to elevate itself to run
#10:44:59enhancinHas anyone else had issues with the Evergreen Client working correctly on Windows XP?
#10:45:17AaronZ-PLStsbere:I will have to play with that. Currently, you must right click on Evergreen and click on "Run as Administrator" or wget doesnt actually update anything. It just gets permission denied messages
#10:45:31enhancinMy boss can't get it to work correctly on XP, we couldn't figure it out forever until she installed it on win7 and it worked (I'm across the country on win7)
#10:45:45AaronZ-PLSenhancin: What version?
#10:45:49enhancin2.0.9
#10:46:01enhancinI can upgrade to 2.0.10 but it just came out
#10:46:04dbsenhancin: define "work correctly". Would it install?
#10:46:08tsbereWe have no problems with the 2.1/2.2ish client on XP. If we DID have issues, whoo boy, would I be dealing with fallout right now.
#10:46:11enhancinYeah it installs, I mean. Okay
#10:46:21enhancinSo we go into the cataloging, import a record, and then try to add the barcode to it and change it's 'location'
#10:46:39dbs2.0.x staff cients are working fine for us on XP
#10:47:51enhancinshe gets an error that says fancy_prompt.xul and TypeError: data.modal_xulG_stack[key] is undefined. I don't get this error here and then she gets a blank error message
#10:48:01enhancinthat's weird, I've had her reinstall it a couple of times
#10:48:20phasefxmodal_xulG_stack--
#10:48:37tsberephasefx: Not sure I agree with that.
#10:48:41tsberexulG--
#10:48:42tsbereIn general
#10:48:43tsbere:P
#10:48:47phasefxhaha
#10:49:16phasefxif remote xul would work in the long term, we could generate some with TT :)
#10:49:17enhancincould it by chance be other software on her system out of date
#10:49:40enhancindoes evergreen use anything else to do it's internet things?
#10:49:53tsberephasefx: There are ways to make it work. I would have made them work, but I can't get later versions of xulrunner to *start*, let alone load the client code. :(
#10:52:49phasefxenhancin: there's an error that the fancy prompt error is sadly obscuring
#10:53:33phasefxenhancin: if you could run the staff client with the -console (tacked onto the end of the target in the shortcut), we might be able to see more of what's happening
#10:53:43dbswell - it will be interesting to see where wolf29 goes with the Drupal front end thing
#10:57:16wolf29dbs: it should keep me out of trouble for a while
#10:57:32tsbereI predict "nowhere near far enough to not need a staff client" due to printing issues alone.
#10:58:10dbswolf29: once you get to the point of sketching out a plan, that would be good to share
#10:58:35enhancinphasefx: I found a bug online about it and it had me raise max_requests and max_children so we're testing it
#11:04:49phasefxtsbere: even if you hack support for remote xul back into later xulrunners, it's still not going to be very well supported, and will be less of a citizen than it is now. Parts of remote xul are broken even in supported versions
#11:05:30phasefx thinks we need to pull the plug, but.. lots of work however we do it
#11:05:32dbsas tsbere suggests, supporting the full range of printing options that the staff client currently supports will be... challenging. But there are a number of workflows that don't require printing capabilities, or that might be able to live with standard browser-based printing (hold / transit slips I guess)
#11:05:50tsberephasefx: I have two possible fixes. Both may even fix some of the issues we see already with remote xul. One by making remote xul no longer look to be remote at all.
#11:05:56dbsfor sure. Maybe agreement that we don't create any more XUL interfaces to start with?
#11:06:35phasefxyou have my vote, and I think ESI has already said as much internally
#11:07:15enhancinso that bug no worky. Let me get a pastebin full of the errors she's getting...one se
#11:07:43phasefxtsbere: I think that could buy us time (or we could stick with a pinned version of xulrunner)
#11:14:46enhancinnevermind, got it. I told her to reinstall evergreen last night but she did it just barely and now it works
#11:14:54enhancini love how people listen to the admin...
#11:25:51enhancin has quit IRC
#11:26:59kmlussier has joined #evergreen
#11:27:17jenny1 has left #evergreen
#11:40:16tsbereSo, I finally figured out why some hold types succeed when they should fail. <_<
#11:46:18dbs guesses javascript type coercion
#11:48:42tsbereindb hold permit doesn't check the item, status, or location holdable flags.
#11:51:46tsbereWell, ok, that appears to be *one* issue. With catalog-originating hold attempts.
#11:52:23mrpeters-isllooks like the 2.1 README may be missing the make -f Open-ILS/src/extras/Makefile.install install_pgsql_server_debs_90 step
#11:52:24dbsscript-based circulation FOREVAH
#11:52:48dbsmrpeters-isl: "Creating the Evergreen database:" ?
#11:53:13mrpeters-isloh i see, it' been moved
#11:53:29mrpeters-islused to be up towards the beginning
#11:53:47dbsyep. change happens.
#11:55:24dbsmade more sense to me to keep all of the database-related steps together
#11:59:18matt_carlson has joined #evergreen
#12:01:09kmlussier has quit IRC
#12:01:23mrpeters-islfair enough
#12:01:53mrpeters-isli had just gotten alarmed because i thought maybe they'd been moved into the earlier dependency install
#12:08:32tsbereOh, goody, the other interface I thought wasn't doing things right is just broken due to another bug I fixed not being committed yet. It does do things correctly now. :D
#12:14:44dbstsbere: pointers to said bug?
#12:16:00tsberedbs: https://bugs.launchpad.net/evergreen/+bug/863657
#12:16:43dbs will get back to a clean master dev env and try to reproduce
#12:16:59dbs(the bug, that is; I already have two kids, that's plenty)
#12:17:12tsberedbs++
#12:17:30Dyrconareminds me of xkcd....
#12:19:23DyrconaAre there any plans to add the "Add MFHD Record" link in the tpac record page as exists in rdetail.xml when used via the staff client?
#12:19:31Dyrcona tortures his native language.
#12:20:19DyrconaIf not, please do NOT consider this a request to have it added. I want to know because of my branch where I'm add the can_have_copies field to bib sources.
#12:22:30sal_ has quit IRC
#12:23:11dbsDyrcona: no, I think we're planning on just keeping the "Add MFHD Record" to the staff client menu in TPAC
#12:23:34dbshaving the button inline in the page itself was just an artifact of my very hastily/clumsily implemented hack
#12:38:24dbsso tsbere: to reproduce the bug, I should place just one hold for a patron in the staff client?
#12:38:42tsberedbs: Via the item status's "request item" menu, not the opac menus
#12:38:50Dyrconadbs: thanks. that means my branch is done. :)
#12:39:16dbstsbere: okay - will do. I tried the "Place Hold" button under the Patron's "Holds" tab
#12:39:40tsbereYea, that one works. For certain definitions of "works" when using indb, anyway.
#12:40:33dbs amused by cancelling the hold, and clicking "Refresh" but not being able to get the cancelled hold to disappear from the screen without cache clear / reload patron
#12:42:29dbsyay! 0 holds created!
#12:42:35dbsnow to apply tsbere's bug fix
#12:42:47tsberedbs: Take note, it likely created 1 hold
#12:42:54tsbereEven though it said 0
#12:44:48dbs wouldn't know how to check, as "Holds / transits" only shows items captured for a hold
#12:45:09dbs hates holds
#12:45:44tsberedbs: View In catalog -> View Holds or load the patron you are logged in as/placed the hold for and view holds?
#12:46:55dbsyup, view in catalog does the trick. so item status doesn't show us anything about targeted holds, we need to go back up to bib level and view from there. got it
#12:51:33tsberedbs: Note that the more I fight with them, the less I like holds myself.
#12:52:04tsbere doesn't think he started off with a positive view of them either
#12:52:26tsbereBut I have to live with a lot more holds stuff going on then you do, I guess.
#12:52:27dbsyay. it works
#12:52:50dbsyes. holds are fuzzy and we can mostly live with them that way
#12:54:29mrpeters-islis there anything sweeter in life than a git-cherry-pick that resolves with no conflicts? :)
#12:54:49dbstsbere: pushed to master
#12:55:10tsberemrpeters-isl: I say ^^ ;)
#12:55:15tsberedbs++
#13:01:56tlilleberg has joined #evergreen
#13:04:09collsk12 has joined #evergreen
#13:06:15collsk12Can anyone help me figure out why every time I edit the rdetail page to add queries for other tags, it completely breaks the book cover images? On every page?
#13:06:58collsk12And even after reverting to a backup file?
#13:08:39jenny2 has joined #evergreen
#13:09:16mrpeters-islcache?
#13:09:18phasefxcollsk12: won't help now, but when you test out skin changes, a useful thing to do is work with a test skin. cp -R default test
#13:09:59phasefxone gotcha with non-default skins is that they often have 'default' hard-coded in places, like for pulling in javascript files
#13:10:01dbsphasefx: followed up by deep sed magic to change all of the links to /default/js/blah to /newskin/js/blah
#13:10:06dbsjinx
#13:10:06phasefxdbs: exactly
#13:10:22dbs loves tpac
#13:10:56phasefxdifferent world
#13:11:03berick@love tpac
#13:11:03pinesol_greenberick: Error: "love" is not a valid command.
#13:11:12collsk12Anyway to revert the entire folder? I don't have any other modifications.
#13:11:20tsbereSo, should I call "force and recall holds don't do anything" a bug alongside the "you can place holds when using indb that shouldn't be allowed" or should I split those two into different branches?
#13:11:46jamesrfcan anyone tell me if a < 2.0.10 client will work ok on a 2.0.10 server?
#13:12:10tsbereFor the most part I think one will. But I am not positive.
#13:12:15phasefxjamesrf: if it's 2.0.x, it should
#13:12:15tsbereJust don't delete workstations from the DB ;)
#13:12:29jamesrfyeah i only imagine problems with registering workstations
#13:12:32dbsjamesrf: works for me
#13:12:42jamesrfbut presumably they would download a fresh staff client most of the time they do that
#13:12:54jamesrfdbs: thanks
#13:14:09agJohn has quit IRC
#13:17:21matt_carlson has quit IRC
#13:18:13matt_carlson has joined #evergreen
#13:20:27sal_ has joined #evergreen
#13:20:37collsk12So is there a fix for my situation?
#13:22:07phasefxcollsk12: I'd move mv default default.orig and copy the whole default/ folder from the install directory
#13:26:22collsk12And if that doesn't work?
#13:26:40matt_carlson has quit IRC
#13:28:09phasefxcollsk12: more targeted debugging
#13:28:49dbsit's always possible that there was a purely coincidental series of added content timeouts that disabled added content for a period of time
#13:28:53collsk12aka - Beat self in head with keyboard?
#13:29:42phasefxcollsk12: given what dbs said, you could use memdump/memcdump to check for the ac. key that disables added content. I forget what it's called exactly
#13:30:19phasefxhow far back does A/T go for hold ready for pickup notifications?
#13:30:26phasefx2.0? 1.6?
#13:30:38dbsac.no_lookup
#13:30:42phasefxdbs++
#13:31:30phasefxcollsk12: memcat --servers 127.0.0.1 ac.no_lookup
#13:32:06phasefxor just do memrm --servers 127.0.0.1 ac.no_lookup
#13:32:15phasefxit'll tell you whether it existed or not
#13:33:54bshumphasefx: I've been trying to follow changes in the staff client and at least up through 2.0.6 (the version we gave to our libs) the only major things to change was the addition of those security changes and some serials stuff. Since we're not using Serials yet, we haven't forced anybody to upgrade to the latest staff clients (or built one ourselves)
#13:34:25phasefxbshum: <nods>
#13:35:06dbsphasefx: 2.0 for sure
#13:35:19bshumWe used it in 1.6 too.
#13:35:39bshumWell... 1.6.0.2 I think.
#13:35:41bshum:)
#13:35:46phasefxnoticed that email notifications for holds are going out despite .email_notify = 'f'
#13:36:12phasefxor at least, templates are generated for such. I don't actually have outgoing email configured on my system
#13:36:14dbshah
#13:36:27bshumphasefx: That's interesting... cause that would explain an odd issue that was reported to us last week.
#13:36:44bshumSomeone showed us a list of holds where email notify was false and yet all the patrons in the book club reported receiving hold notifications.
#13:36:57bshumWe hadn't investigated that deep yet though.
#13:38:46dbs sent an email to bjwebb last night asking what we can do to integrate his work on automatic livecd / vm builds into the core of the project
#13:39:06dbsseems a shame to have a bunch of releases and to have to go back to manually building vms and such
#13:39:54collsk12Now I'm in deep! How do I fix the symlink stuff on these xmls?
#13:39:55dbsthe livecd / vm builds rely on packages generated by openSUSE's build service, which are controlled by bjwebb and haven't been refreshed since August 20th
#13:40:49dbs is hoping that the reins (and know-how!) can be shared, and that some of the nice enhancements tsbere has contributed like --create-database will help simplify things
#13:42:00Dyrconanew Milestones: 2.0.11, 2.1.1 ?
#13:42:14dbscollsk12: something like: "for i in 'advanced.xml authbrowse.xml cnbrowse.xml mresult.xml myopac.xml rdetail.xml rresult.xml' do; ln -sf index.xml $i; done" ?
#13:42:33dbsDyrcona: sounds good
#13:45:09tsberephasefx / bshum : Looks like a/t will send out an email notice so long as the patron has an email address. Period. I can't find any indication of it checking the email notify field. :(
#13:45:50berickA/T supports opt-in user preferences
#13:45:53phasefxtsbere: I think the patron may be able to opt out entirely of the A/T
#13:46:00DyrconaI will flag 2.0.10, 1.6.1.9 and 2.1.0 as released in Launchpad?
#13:46:05berick1.6 may not have them, though..
#13:46:29tsberephasefx: That doesn't help specific holds with the setting disabled, right?
#13:46:40phasefxtsbere: right
#13:46:56berick... and only tpac actually allows users to edit their A/T opt-in prefs ATM
#13:49:39ybostonhello everyone, quick question about running authority_control_fields.pl
#13:49:47ybostonshould this script be run as opensrf or is root OK? do I have to run it from a specific location (the $boostrap path is already set)? Thanks in advance.
#13:53:18dbsyboston: running it as opensrf will ensure that your environment is set appropriately
#13:53:34ybostondbs: thanks
#13:59:40collsk12 has quit IRC
#14:04:41collsk12 has joined #evergreen
#14:05:00jenny2 has quit IRC
#14:05:14collsk12Just an update: I'm still broken and I think I quit.
#14:06:09jenny1 has joined #evergreen
#14:10:20jenny1 has left #evergreen
#14:11:51phasefxcollsk12: you can grab the URL for a jacket image and test it. That should work or not work independently of any OPAC skin changes you did
#14:29:08collsk12phasefx: It doesn't look like the covers are being cached by the server, even though I can reach the covers through my network. What do you think?
#14:30:09phasefxcollsk12: what version of EG are you using, and are you trying to mix added content with local content (say with /openils/var/web/opac/extras/ac)
#14:30:16bshumsenator++ #acq miracle worker
#14:34:56collsk12I'm using 2.1 and I don't think I'm doing anything fancy like that. I also noticed that I don't have an "ac" folder.
#14:35:06senatorbshum++ # feedback means better bugfixes
#14:38:24kmlussier has joined #evergreen
#14:42:11phasefxcollsk12: that's good (not having that folder)
#14:42:56phasefxcollsk12: using OpenLibrary for added content?
#14:43:21collsk12I was...when it was working.
#14:52:53Callender has quit IRC
#14:53:30Callender has joined #evergreen
#14:57:31tsbere is considering opening a new bug or two on launchpad, but doesn't want them lost in the current flood
#14:58:12dbscollsk12: are you sure that openlibrary itself is still working? they've been known to go down :)
#14:58:44collsk12dbs: lol...I checked. I know how that can happen. But thanks for the suggestion.
#14:59:02dbshttp://images.concat.ca/opac/extras/ac/jacket/large/0309052823 works for me - adjust your hostname accordingly?
#14:59:26adbowling-isl has quit IRC
#15:00:43lisah_ has joined #evergreen
#15:06:07lisah_ has quit IRC
#15:25:50sal_ has quit IRC
#15:29:08dbs has quit IRC
#15:39:10dbs has joined #evergreen
#15:39:58dbssorry folks, our campus connection to the outside world died. back thanks to the miracle of tethering
#15:40:08dbs(I know, y'all missed me terribly)
#15:40:16collsk12Thank you room for the help today. I have to run. Hopefully I can figure this thing out and update you on what I get done. Thanks again!!
#15:40:19collsk12 has quit IRC
#15:51:11wolf29I am a quarter done counting up individual screens on the staff_client for the possible Drupal-based web-client. Going home to Hope Springs.
#15:51:41wolf29 has left #evergreen
#15:52:28tsbere suspects wolf29 won't ever finish
#16:22:54Dyrcona thinks it must be some kind of abuse of git to create a branch to track a change to 1 character in 1 file, but it works far better than remembering to edit the file every time before one builds.
#16:27:49wlayton__ has joined #evergreen
#16:31:56moodaepo wonders why one has to count individual screens for a drupal based client
#16:32:31dbwellstsbere: sorry for the delay in testing the grace_period extension branch. I finally got a chance to spend a few hours putting it through its paces, and have posted a potential fix here: https://bugs.launchpad.net/evergreen/+bug/787542 Please take a look whenever you get a chance, no hurry.
#16:33:45moodaepo was at the Nobel conference the last two days and missed all the hullabaloo!
#16:34:07tsberedbwells: My interpretation of things was "if your grace period runs out just before a closed date, well, you should have gotten your materials back sooner"
#16:34:23tsbereBecause the end of your grace period was eaten up by an open date
#16:36:24dbsmoodaepo: did you win?
#16:37:17moodaepodbs++ #funny man. Was attending this > http://gustavus.edu/events/nobelconference/2011/
#16:39:09tsberedbwells: Note that fines aren't charged on closed dates, so backdating to the previous day when dealing with bookdrops will take care of the last fine at that point.
#16:40:46kmlussier has quit IRC
#16:52:09collum has quit IRC
#16:55:09moodaepoIn the library settings editor I'm trying to check that the patron barcode starts with a "2" and it just doesn't seem to work. I am trying a basic regex ^2\d[0-9]
#16:56:39dbs2, followed by a digit, followed by any char in the 0-9 range
#16:56:56dbs^2\d{0-9} ?
#16:57:32dbs^2\d{0,9} # (thinking vim syntax)
#16:59:13moodaepoNo go with ^2\d{0-9}
#16:59:19tsbere^2[0-9].*
#16:59:38tsbereor ^2[0-9]{2}.*
#16:59:50tsbereFor "needs to have 3 digits at the start, the first being a 2"
#16:59:53tsbereI think
#17:01:03tsberemoodaepo: Also, that barcode regex thing? Until master it only applies to the *opac*
#17:01:42moodaepotsbere++ #I've been testing in the client
#17:02:09tsbereactually. I don't recall if I made it apply to the client at all, even in master.
#17:02:11tsbere goes to check
#17:03:25tsbereLooks like I did not make it apply anywhere you enter a barcode.
#17:03:50dbwellstsbere: I suppose I can see it both ways, but from my perspective, grace periods cover fine periods, so since closed days are not fine periods, they should be considered part of the grace whether they fall before, during, or after. It avoids needless fine generation and subsequent voiding, and is less prone to user error, since you only need to backdate into the closed date, not worrying about when the closed period actually began. Does that
#17:03:50dbwells make sense?
#17:03:54tsbereJust for "usernames can look like barcodes or usernames, if you have a regex for both"
#17:04:08tlilleberg has quit IRC
#17:05:39AaronZ-PLS has quit IRC
#17:05:43tsberedbwells: I think your proposed fix will make the day after the closed period an extra grace day, though.
#17:05:55tsberemaybe
#17:05:57tsbere hasn't tested
#17:06:00matt_carlson has joined #evergreen
#17:07:20dbsmoodaepo / bshum: I've updated downloads.php in place, not in git, to point to 2.1.0a / 2.0.10a / 1.6.1.9a versions of the tarballs due to a bug we found
#17:07:30dbsand updated http://evergreen-ils.org/blog/?p=687
#17:07:37bshumdbs: Alright.
#17:07:41moodaepodbs++
#17:07:48tsberedbwells: My view is "if you didn't get the item back by the end of the last grace day, even if the day after is a closed date, you are now liable for *all fines up until then*" either way. It was due thursday, had a single day of grace. Friday and saturday the library is closed. You return the item monday, your grace period was *over* friday.
#17:07:55dbsjust wanted to give you a heads-up that I was bad and didn't get it into git :(
#17:08:02bshumHeh
#17:08:36dbsif anyone has the chance to copy/paste the update from the blog post into a response to my security release mailing list posts to -general and -dev, that would be appreciated
#17:08:42dbsI have to hightail it out of here :(
#17:09:18dbs(or if you come up with something more eloquent than what I wrote, have at it! too rushed to be eloquent)
#17:09:20tsberedbwell: er, in the above, saturday and sunday were closed. Bah.
#17:09:45dbwellstsbere: right, if you return it on Monday, you are charged for Friday and Monday. The code still should do that. However, if you backdate into Sat or Sun, you should have no fines, right?
#17:10:07_bott_ has quit IRC
#17:10:38_bott_ has joined #evergreen
#17:10:41bshummoodaepo: I can add dbs' change to the git repo
#17:11:05bshumLeast... I think I can.
#17:11:43moodaepobshum: Sure go for it..just scp the file into your local repo and push into git
#17:12:01bshumFreaking vim
#17:12:29moodaepoI can copy/paste the blog update and send out an update to the list
#17:12:33moodaepo*lists
#17:13:03bshumAlright.
#17:13:50gmcharltdbs++
#17:15:40dbs has quit IRC
#17:21:49dbwellstsbere: I think my biggest concern here aside from loose backdating errors is that fine generator will dutifully generate a fine on Saturday (for Friday), and even if it is eventually voided by a proper backdate, this is bound to cause some consternation for certain patrons, particularly if the library is closed for some time and these imaginary fines pile up.
#17:25:40tsberedbwells: The current way the system works the fine(s) for the grace period will be generated the day after the grace period ends, whether the library is open or closed that day. But no fines are generated *for* a day the library is closed. So due thursday, grace period friday, backdated checkin in to sunday on monday would charge the patron for friday only.
#17:28:53dbwellstsbere: If a library is closed on Sat and Sun, backdating to Fri, Sat, or Sun should be identical as far as fines are concerned, shouldn't it?
#17:29:40tsberedbwells: IMO, no.
#17:29:52Dyrcona has quit IRC
#17:30:04tsberethe library was open friday. You didn't return it Friday. Thus ended your grace period.
#17:31:18dbwellsBackdating general assumes the best, i.e. that I returned it on Friday after the library closed.
#17:31:34tsbereThen backdate to friday, not sat or sun ;)
#17:32:15tsbere hits the road
#17:33:03dbwellsI think I will take this discussion to the list, as more opinions are needed. Thank you, tsbere
#17:44:08moodaepo@later tell dbs IMO in the future it might be better to just re-release the versions especially with such a short update period, maybe I'm just being picky about having "a" versions and thinking alpha : )
#17:44:08pinesol_greenmoodaepo: The operation succeeded.
#17:47:42gmcharltmoodaepo: that can invite confusion
#17:48:02gmcharltof the form, "will the real Evergreen-ILS-2.0.10.tar.gz please stand up"
#17:48:22rangicould do the -1 like debian and ubuntu
#17:48:27rangiinstead of the a ?
#17:48:48bshumBack to four point releases? Oh boy...
#17:48:56ranginot a point
#17:49:05bshumOh dash
#17:49:06moodaepogmcharlt: True but I think we've actually re-released versions before..within minutes/hours though.
#17:49:11bshumSilly tired eyes :(
#17:49:14rangi:)
#17:49:23rangi sows more confusion
#17:49:35bshummoodaepo: 2.1.0 was re-tarred at least once the night before "release"
#17:49:38moodaepoI'd +1 -1
#17:50:03gmcharltmoodaepo: a day != minutes, particularly in the case of a set of security releases that are meant to be installed ASAP
#17:51:17gmcharltat least for 2.1+, building releases is much closer to being fully automated thanks to some work by tsbere
#18:09:58matt_carlson has quit IRC
#18:13:16yboston has quit IRC
#18:55:46AaronZ-PLS has joined #evergreen
#18:57:39AaronZ-PLS has quit IRC
#19:52:44Callender has quit IRC
#20:10:45Callender has joined #evergreen
#20:40:29mrpeters-isl_ has joined #evergreen
#20:41:09mrpeters-isl_brute force patch question -- wouldnt a multi brick enviornment actually allow up to 10 attempts, per brick?
#20:41:50mrpeters-isl_because the lockout would only occur on a brick by brick basis?
#20:42:22tsbere@later tell dbwells I force-pushed a compromise option for grace period extension there. Left a note on the launchpad bug about it.
#20:42:22pinesol_greentsbere: The operation succeeded.
#20:42:58tsberemrpeters-isl_: The lockout count is stored in memcache. Unless you are running a memcache server for each brick they will share the info.
#20:43:24mrpeters-isl_aha...it doesn't seem to last long then
#20:43:41tsbereDefault of 90 seconds of no attempts before the count resets
#20:43:55tsbereYou can, of course, change that.
#20:43:58mrpeters-isl_ok, that's just about the timeframe it took me to switch bricks
#20:44:06mrpeters-isl_no no, all good...just wanted to clarify
#20:44:19mrpeters-isl_gmcharlt:++ for the update for multi-bricks
#21:14:06mrpeters-isl_ has quit IRC
#21:20:41atz_ has joined #evergreen
#21:24:27atz has quit IRC
#21:26:03Callender has quit IRC
#21:40:43Callender has joined #evergreen
#22:34:53Callender has quit IRC
#22:55:48Callender has joined #evergreen
#23:25:03Callender has quit IRC
#23:33:32youdonotexist has joined #evergreen
#23:40:53Callender has joined #evergreen
#23:43:34edoceo has quit IRC
#23:45:28Callender has quit IRC
< Wednesday, October 5th, 2011Raw Log FileFriday, October 7th, 2011 >