Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, May 17th, 2011

< Monday, May 16th, 2011Raw Log FileWednesday, May 18th, 2011 >
#TimeNickMessage
#00:23:36denials grabs 0535 for the authority indexes
#00:51:33denials likes 'git rebase -i' with 'fixup'
#02:24:15tater-laptop has quit IRC
#02:34:12tater-laptop has joined #evergreen
#02:55:01tater-laptop has quit IRC
#03:31:43bjwebbgah fire drills
#04:10:52bjwebb has quit IRC
#07:29:34Sally has joined #evergreen
#08:08:07sylvarat 3:3o? ouch
#08:17:40denialssylvar: adjust for UK timezone
#08:18:05tsbere has known places to do fire drills in the middle of the night intentionally, though
#08:21:07Dyrcona has joined #evergreen
#08:26:34sylvarAh, that's not too bad then.
#08:28:37tsberesylvar: I have a friend who has horror stories of college dorm fire drills. At 2 am.
#08:28:55sylvartsbere: now you have two
#08:29:07sylvarrah rah alma mater sis boom.
#08:29:09sylvarbah.
#08:30:04tsbereApparently they felt that during the day when the dorm was empty wasn't a good drill?
#08:30:52Sally has quit IRC
#08:31:00sylvarFrankly, the shenanigans that cause real fires are more likely at 2am. I knew some guys from a dorm floor that was diasporated (the ones who weren't evicted) after a dorm-furniture bonfire in the lounge.
#08:32:05sylvarLate-night boredom. Some folks write a replacement Minix kernel, some people set fire to stuff.
#08:32:55gmcharlt@quote add <sylvar> Late-night boredom. Some folks write a replacement Minix kernel, some people set fire to stuff.
#08:32:55pinesol_greengmcharlt: The operation succeeded. Quote #9 added.
#08:33:35tsbereHeh. That reminds me of a different horror story from my friend. 2:30 or so the night before the start of finals and someone's candle set their desk on fire.
#08:33:58ernieSimuro has joined #evergreen
#08:39:37sylvarHere, before the caffeine kicks in, let me give you a topic: A hypothetical fault-tolerant (specifically, "Server? WHAT server?"-tolerant) EG staff client loses its connection. It switches to offline mode and alerts the staff member (different background, popup, something). When the server comes back, it uploads the offline file, attempts to auto-process it, and tells the staff member about exceptions.
#08:39:57sylvarscuse
#08:39:58sylvarIt switches to offline mode and alerts the staff member (different background, popup, something). When the server comes back, it uploads the offline file, attempts to auto-process it, and tells the staff member about exceptions.
#08:41:13tsberesylvar: For various reasons, I feel that switching into and out of offline mode should be more manual. Also, if the issue is with just that computer they may want to stop using it.
#08:41:47tsbereI would personally dislike a computer auto-accepting transactions for offline mode when, say, the network died because the memory is corrupting itself.
#08:43:15sylvarGood idea. Could we usually test for that? (Server not responding to connections or pings. Traceroute dies one hop away. Offline! // Server not responding to connections or pings. Can't ping 127.0.0.1. Fail loud!)
#08:44:21sylvarMy inspiration for this: I was driving to work, listening to Pandora on my Chromebook over 3G. I get to the office, the Chromebook joins the wifi network, I manually turn off 3G data, and Pandora doesn't miss a beat.
#08:44:25sylvarLiterally.
#08:44:50tsbereIn theory, the staff client would act in a similar manner.
#08:44:50sylvarSON, I AM IMPRESS
#08:45:17tsbereChange networks and it should pick up right where it left off unless you were in the middle of something significant.
#08:45:33sylvarI like that.
#08:45:34tsbereand by singificant I mean "somehow uploading or downloading a few hundred megs"
#08:46:25asimon has joined #evergreen
#08:46:55asimonHello. I am attempting to load patrons with family group information. Is usr_grp_map the only table that pertains to family groups?
#08:47:34gmcharltyes
#08:47:43tsbereIsn't that permission groups?
#08:47:54tsbereOr are there multiple tables named that way in different schemas?
#08:48:49gmcharltasimon: pardon me - actor.usr.usrgroup
#08:49:49gmcharltpatrons that have the same usrgroup value are in the same family group
#08:50:20gmcharltthere's also a hack where a juvenile patron's ident_value2 can be interpreted as containing the name of a guardian, but I'd avoid that
#08:50:45sylvartsbere: I was gonna joke about a few hundred megs of config tables on startup, but I only measured about 630kB with wireshark
#08:50:54sylvarthose few seconds last forever
#08:52:31denialssylvar: play swirling romantic music at staff client startup; make the moment last
#08:52:56sylvardenials: hire Brian Eno for an Evergreen Sound
#08:53:24csharpsylvar: the "auto-switch" to offline would be cool, but only for libraries that opt to use it. Many of our libraries will not touch standalone and trust the ol' "scan into notepad/wordpad/Word" procedure *shudder*
#08:53:34asimongmcharlt: So actor.usr.usrgroup contains a unique group value for all the members of a group, but that value is not reflected anywhere else in the schema?
#08:54:04gmcharltcorrect
#08:54:29gmcharltalso, the lead member of a group should have actor.usr.master_account set to true
#08:56:09sylvarcsharp: As long as they don't have auto-spellcheck enabled... "Hey, why are our patrons all named ZIOIS something?" "Uh... I think that's 21015."
#08:56:28csharpheh
#08:57:27csharp prefers his library card number font to be Comic Sans
#08:57:28sylvarand now you can guess where I pick up my PINES holds :)
#09:00:54csharp did not guess, had to consult spreadsheet ;-)
#09:01:21gmcharltyou don't have them all memorized? ;)
#09:02:13sylvar used to have a dozen or so memorized (not PINES, a multitype consortium that no longer hosts an ILS)
#09:02:45tsbereSo, any chance of getting someone to look at a couple of branches of code? I want to make sure they are acceptable (or close to it, and only for master, not 2.1) before we actually start using them in production. And we want to finalize our production codebase by the end of the week for migration headache reduction.
#09:04:29csharp:-)
#09:15:39kmlussier has joined #evergreen
#09:28:48bjwebb has joined #evergreen
#09:28:49bjwebb has joined #evergreen
#09:29:27jenny has joined #evergreen
#10:18:34bshumAnyone around with a 2.0 system? Got something odd I'd like someone else to check on
#10:18:56bshumCatalogers have permission for update_volume set to depth of branch
#10:19:14bshumBut they seem to have the ability to edit volume labels regardless of where their actual working locations.
#10:19:58bshumIn holdings maintenance, if they pick another library within the consortium, highlight the row for volume and click "Edit Volume" from the options, it opens a little window that allows them to edit the label
#10:20:22bshumIf the permissions aren't set for allowing updates from a branch you don't work for, that seems like a bug in not respecting the permission.
#10:20:35jennybshum: I can check that for you in a moment
#10:20:44bshumIf someone else can confirm that behavior (I've tried it on our live and test environments, and a stock install of 2.0.6 as well)
#10:20:47bshumThen I'll file a bug
#10:20:53bshumjenny: Thanks, appreciate it :)
#10:23:22tsbereSo, eeevil, you around?
#10:23:25kmlussierbshum: one of our catalogers noticed this recently, but I haven't had a chance to look into it yet.
#10:25:39bjwebb has quit IRC
#10:25:52bshumkmlussier: Yeah it came up during our cataloging training, I guess our libraries using it so far haven't been poking at their fellow libraries.
#10:29:21eeeviltsbere: I'm looking at lazy_circ2+master now
#10:29:32tsbereeeevil++
#10:34:05jamesrf has quit IRC
#10:35:41dbs has joined #evergreen
#10:35:41dbs has joined #evergreen
#10:38:57lisppasteeeevil pasted "eyeballin' stuff" at http://paste.lisp.org/display/122061
#10:39:08eeeviltsbere: that's for you, sir
#10:41:02jennybshum: I tested the update_volume issue on our development server and it appears to be a bug. I was able to edit volumes at branches my catalog user was not registered to. This server is currently on 2.0.5. I don't have access to a 2.0.6 server at the moment. Permissions appear to work correctly on our 1.6.1 server (I was curious, so had to check)
#10:41:43bshumjenny: Thanks for checking. I've started writing up a bug ticket for Launchpad on it.
#10:41:57bshumAnd thanks for checking with 1.6.1 :)
#10:42:04bshumI don't have any of those around anymore
#10:42:22jennywe hope to get rid of ours this week :)
#10:42:55bshumAwesome, heh
#10:45:01tsbereeeevil: Yea. I apparently missed that, as my code says == but my installed version I was testing says !=
#10:46:07tsbereCorrection: One copy of my code says == (as in the committed copy). I apparently fixed that locally *after* commit, and forgot to commit the extra change. tsbere--
#10:47:04eeeviltsbere: in a scan of the diff, that was the only thing that stuck right out at me ... there are varying levels of error handling going on, and I think they deserve some commentary as to why some are more robust than others (or robustification, if indeed the commentary suggest that) ... that said, I'm inclined to push this into trunk sooner rather than later, if you don't mind going through and commenting up some of the js (the call sites for get_barcode
#10:47:42tsbereI can push that one fix and a pile of comments. Just have to write the comments.
#10:47:46eeevilgah ... need to stop writing so much on one line
#10:48:30eeevilnot sure if that got truncated. last sentence was: there are only a couple call sites and IMO that would greatly improve maintenance efforts by others
#10:48:44eeeviltsbere++
#10:51:21sfortin has joined #evergreen
#10:56:48AaronZ-PLS has quit IRC
#10:57:09wlayton has joined #evergreen
#10:57:28Dyrcona has left #evergreen
#10:57:35eeevilcrap ... gmcharlt, in d9a4c8382cb65b36f201f12a7b06b32a3fc953c8 I'm seeing:
#10:57:36eeevilcopy from Open-ILS/src/sql/Pg/upgrade/0431.schema.hold_retarget.sql
#10:57:37eeevilcopy to Open-ILS/src/sql/Pg/upgrade/0534.schema.fix_hold_permit_test.sql
#10:57:50eeevilgmcharlt: that's ... ungood, I think, no?
#10:58:16tsbereeeevil: Ironically, in re-reading, both versions of my end were wrong. the == was correct. barcode_object was missing a .ilsevent though.
#10:58:19MarkEIN has joined #evergreen
#10:59:29eeeviltsbere: ahh, ok ... that formulation was used elsewhere
#10:59:54tsbereWhich is why I noticed. Got to that for adding comments, went "wait, that doesn't look right based on what I just commented"
#10:59:59gmcharlteeevil: see where, precisely?
#11:00:26eeevilgmcharlt: well, I noticed when pulling master into my local lazy_circ2 a "removing blah" message
#11:01:08eeeviland then, in the diff for that commit, it looks like it's renaming the 0431 upgrade script and changing it a bit
#11:01:44eeevilbut ... 0431 is still in the working tree here, so I guess it's just more scary git messages (I hope, anyway)
#11:04:35eeevilgmcharlt: ah HA ... nevermind, I'm straighe
#11:04:38eeevilstraight
#11:05:16gmcharlt:)
#11:06:37gmcharltjust see an artifact of Git's similiarity detection, I imagine
#11:06:40tsbere prepares for a quick test to make sure his commenting didn't break anything
#11:07:25tsbereeeevil: To hopefully correct for that bit, I can git pull to ensure lazy_circ2 is more up to date against master as well. But that might make cherry-pick harder (but is fine if you just do merge)
#11:07:40eeevilgmcharlt: yes, that threw me off ... easing into this, though
#11:08:20eeeviltsbere: I'm just pulling your branch ... I've pulled master in locally too, all's well so far
#11:10:41Dyrcona_ has joined #evergreen
#11:11:22Dyrcona_I am trying to get the OpenSRF/OpenILS modules working for clients on my workstation, and I get the following error when I try to run a test program:
#11:11:23tsbereeeevil: Did a git pull anyway. And pushed.
#11:11:25Dyrcona_Could not create file parser context for file "/openils/conf/fm_IDL.xml": No such file or directory at /usr/local/share/perl/5.10.1/OpenILS/Utils/Fieldmapper.pm line 199
#11:12:54Dyrcona_ah, never mind: sudo ln -s /home/jason/openils /openils
#11:12:56dbsDyrcona_: /openils/conf/fm_IDL.xml exists and is readable by the user?
#11:12:59Dyrcona_fixed it.
#11:12:59dbsaha
#11:13:29yboston has joined #evergreen
#11:19:26collsk12 has joined #evergreen
#11:20:47eeeviltsbere: awesome, thanks
#11:21:06tsbere couldn't resist having fun with one comment, though
#11:23:04eeeviltsbere: as a git noob, I'll "let it sit for a bit" ... if you want to push a rebased branch with condensed commits, feel free. if not, I'll push this ... soonish
#11:23:33tsbereI can rebase it down to one commit if you want. Makes the core log easier to deal with.
#11:25:35eeevilI think the security commit is worth keeping separate, as documentation for other ... "that stuff is important!" ... the others I'm less concerned with as they're mainly cleanup from the first, no?
#11:26:42tsbereIf my security commit's log message was more than "Security checks, error checks, etc" maybe. I can add notes about the security stuff in the single-commits log message, though.
#11:27:52eeevilsince it's not a ginormous pile of code I'm happy to handle it how you like, really. your pref
#11:33:42tsbereeeevil: Well, the rebased version is in branch lazy_circ2_rebased. Don't care which you use.
#11:35:33tsbere figured it was "safer" to push the rebase to a new branch pub-side
#11:36:03eeevilindeed, thanks for that :)
#11:38:14tsberesince using git locally I do all my dev work in piles of branches that don't know about each other's changes (usually) anyway. Thus, I also don't usually have issues with merge conflicts with local version compared to pushed version. But I know others differ there.
#11:38:28wlayton has left #evergreen
#11:38:43youdonotexist_ has joined #evergreen
#11:40:28collsk12Good morning, all. Could anyone help me figure out why my book cover images stopped loading this morning? They were fine yesterday.
#11:40:49dbscollsk12: what added content provider?
#11:40:51tsbereadded content provider account expire? ;)
#11:41:22dbsopenlibrary - the default for Evergreen as of 2.0 - experienced an outage recently
#11:41:33collsk12That's the one!
#11:41:41dbshttp://blog.openlibrary.org/2011/05/16/openlibrary-org-is-currently-offline/
#11:41:52dbssounds like covers are currently affected
#11:42:24dbsnote that with the new code in trunk, covers wouldn't be affected (because we're not using covers.openlibrary.org by ISBN anymore)
#11:42:37ernieSimurojeff_: did you get to upload the PHP code for openSRF?
#11:42:43collsk12dbs: You rock! Thank you!
#11:43:42dbscollsk12: aww, you're sweet :) if you want to try http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/perlmods/lib/OpenILS/WWW/AddedContent/OpenLibrary.pm;h=2be38a0c6ebe9516ac32e4639b2d679bfc193758;hb=HEAD it should be a drop-in replacement for the current OpenLibrary.pm module
#11:44:34collsk12dbs: Are you a mind reader or something? I appreciate it.
#11:45:16dbs awaits jeff's code for added content by record ID so that we can do more fun stuff :)
#11:45:29collsk12Uh oh...
#11:45:33collsk12:)
#11:52:21moodaepoernieSimuro: I believe jeff is traveling today so maybe tomorrow.
#11:53:09collsk12Since you have been so helpful today, could you possibly explain to me why the little icons located next to the search refinement options, in the left column, disappeared too? This was a couple of days ago and I'm not quite sure how to get them back.
#11:53:33moodaepo also awaits jeff release code to do pulls from evergreen which he has locked up in one of his VMs
#11:54:10ernieSimuromoodaepos: Thanks I thought he was due back today will check tomorrow
#11:54:26moodaepocollsk12: Mind sharing a link to the opac?
#11:55:17tsbereeeevil: Any thoughts of looking at my sip_statcats branch today? Or recommendations for poking someone else about it?
#11:55:17collsk12Sorry, I don't have it in the DMZ yet. I just built the system last week and will probably go live this summer.
#11:56:45collsk12I have objects like the Author names, number of matches, etc. I just lost the icons.
#11:59:41dbscollsk12: if this is Evergreen 2.0, I don't think there are any icons on the left
#11:59:53dbsEvergreen 1.6 had little icons on the left
#12:00:33collsk12Oh...that could explain it. No biggie. Thanks again, dbs.
#12:01:34moodaepodbs: Would you know what time the governance meeting is today?
#12:01:56dbsmoodaepo: evergreen-ils.org/calendar would
#12:02:04moodaepoOh right
#12:02:16dbsoh, that didn't make the jump
#12:02:37moodaepoThere seems to be some major misunderstanding of the student funding I've been pushing for with the IMLS folks.
#12:02:50dbshttp://evergreen-ils.org/dokuwiki/doku.php?id=calendar:start works
#12:03:01dbsmoodaepo: yes, you're reading the governance mailing list?
#12:03:36gmcharltyep, I've been pointing moodaepo that way, given the misunderstanding that's going on
#12:03:37moodaepoHmm I used the link in the menu
#12:03:46moodaepoBut yea gmcharlt forwarded the mail to me
#12:08:20bshumHmm
#12:08:26bshumThose emails back and forth about OpenSRF
#12:08:33dbsmoodaepo: we used to have a redirect for the easy-to-remember evergreen-ils.org/calendar to the wiki page, that's all
#12:08:35bshumMakes me feel that maybe step 9 should be before step 8 for the instructions.
#12:08:59bshumcp opensrf examples before you register the ejabberd accounts?
#12:09:48moodaepodbs: Setting it up
#12:10:04dbsbshum: either way, you have a chicken and the egg scenario
#12:10:23bshumdbs: True. I'm thinking if there's any way to clean up the language there now.
#12:10:24dbsedit opensrf_core.xml to have accounts that don't exist yet?
#12:11:37dbsbshum: rather than refining language, writing a script to handle all of the configuration would probably be more efficient
#12:11:54bshumdbs: Well, sure :)
#12:13:47youdonotexist_ is now known as youdonotexist
#12:16:09dbsbshum: the one concession I would make is to add 'opensrf_core.xml file that you will edit in the next step' - for people who don't skim over all of the instructions before beginning at step 1, or are unable to use CTRL-F in their browser to find another reference to something mysterious, or who don't scan ahead to the next step
#12:16:49csharpyeah - I think the instructions are pretty clear about that as-is (though a language barrier may be at play here too ;-) )
#12:17:02csharpbshum answered just as I was typing my email
#12:17:16csharpbshum is a faster typist, as I now know ;-)
#12:17:46moodaepodbs: evergreen-ils.org/calendar is now setup
#12:17:54jamesrf has joined #evergreen
#12:17:58dbsmoodaepo++
#12:19:46bshumcsharp: Eh, faster isn't always better :(
#12:23:15dbsI closed off milestone 2.0.6 and added 2.0.7 for anybody interested in changing 13 bugs to "Fix released" :)
#12:24:27bshumThat's like... the fun part!
#12:24:36asimon has quit IRC
#12:54:37natschil has joined #evergreen
#12:58:06tsbere finds it interesting that GitHub thinks Evergreen is Javascript
#12:58:41Dyrcona_:)
#12:58:52Dyrcona_more lines of javascript than perl maybe?
#13:02:38AaronZ-PLS has joined #evergreen
#13:03:06moodaepo_ has joined #evergreen
#13:16:34jenny has quit IRC
#13:20:58eeeviltsbere: re sip_statcats, I won't have time today, and I'd like berick or another sip'r (dbs, senator, djfiander?) to look at it (berick, in particular, is on vacation ATM)
#13:23:22eeeviltsbere: I'm probably going to use your rebased branch, beat it around a bit for the upgrade script and such, and rebase again adding some more detail to the commit message. that is, assuming, that rebase -i will (can) retain your sign-off ... not sure, do you know?
#13:23:32eeevil(thats re lazy circ, obv)
#13:24:04tsbereeeevil: It will retain sign-off. Dunno about author, though.
#13:24:47gmcharltit will retain author as well
#13:25:58eeevilgmcharlt: even on squash?
#13:26:00tsbere rarely rebases someone else's commits
#13:26:54eeevilhrm... but ... gmcharlt, you warned against rebasing after a post-patch cleanup commit?
#13:28:07tsbereeeevil: He did that for the "stop merge conflicts from happening on the author's machine" I think.
#13:28:15gmcharltyes
#13:28:20tsbereAnd I won't be working on those branches again, and thus don'
#13:28:26tsbere*don't care about merge conflicts ;)
#13:28:29eeevilahh... righto
#13:28:31gmcharltthere's not necessarily a good reeason to squash, though
#13:28:51gmcharltif all you're doing is tacking on upgrade scripts and the like
#13:28:57eeevilno, there's not ... I'll just squash my own (if needed)
#13:29:28tsberegmcharlt: Well, he likely wants to wipe out the XXXX upgrade script as well. I could see that as a reason to squash.
#13:29:58gmcharltmaybe, or just do a git mv and commit the rename
#13:30:02eeevilgrabbing 0536
#13:30:11eeevilright
#13:30:22eeeviland other minor adjustments
#13:30:38tsbereLike replacing XXXX with 0536 inside the file? ;)
#13:31:06eeeviland in 002.schema.config.sql
#13:31:25tsbere knows that the XXXX in the upgrade script was missed once, he thinks by phasefx
#13:31:58tsbereHmmm.
#13:32:51tsbereWould having a different commit for the upgrade script help for future patches?
#13:33:19gmcharltit would
#13:34:05tsbere will try and remember to do that in the future
#13:34:31eeeviltsbere: there's a script for generating the boilerplate stuff .../Pg/make-db-patch.pl
#13:35:07tsbereeeevil: I rigged this up myself at one point: http://paste.lisp.org/display/121956
#13:37:12tsbereIsn't perfect, granted, but it is great for grabbing the exact defs for new stuff
#13:37:22moodaepo_dbs++ # software bounty
#13:37:54Dyrcona_where would i find the code that determines search relevance of results?
#13:38:25Dyrcona_ not finding what he's looking for.
#13:39:13eeeviltsbere: make-db-patch.pl does some other stuff that trunkish upgrades need to do, but yours could be easily modified or used within that
#13:39:55tsbereeeevil: Mine came around in part (less friendly) before make-db-patch.pl. Was considering submitting a patch to make-db-patch.pl to have it do some of what mine does.
#13:40:07moodaepo_ has quit IRC
#13:40:18gmcharlttsbere: go for it
#13:42:27Dyrcona_ thinks he found what he's looking for, unlike a certain Irish singer.
#13:48:36yboston has quit IRC
#13:53:42eeevilgmcharlt: when editing a cherry-picked commit message, do I need to uncomment the Author: line to retain that info?
#13:53:50eeevil(I assume no, but...)
#13:55:36eeevilwe'll find out.. :)
#13:55:53eeevilnope ... I assumed correctly
#14:01:12jenny has joined #evergreen
#14:01:52tsberegmcharlt / eeevil : Any thoughts? http://git.mvlcstaff.org/?p=tsbere/ILS.git;a=shortlog;h=refs/heads/mdp-improve
#14:03:14gmcharlttsbere: looks good; I'll test it now and push if it passes
#14:03:25tsbere has quit IRC
#14:03:41tsbere has joined #evergreen
#14:03:51tsbere dislikes random disconnects
#14:04:13gmcharltdid you catch what I just said to your, tsbere?
#14:04:33eeevilgmcharlt: so, pull caused conflict (same file edited) ... is there a way to restart the pull after solving the conflict and using git-add?
#14:04:43eeevilsomething like git merge --continue?
#14:04:59tsberegmcharlt: Last I saw was my own "Any thoughts?"
#14:05:11gmcharlt<gmcharlt> tsbere: looks good; I'll test it now and push if it passes
#14:06:46eeevilgmcharlt: or is the answer 'git commit -am "dummy message"' ?
#14:06:49senatoreeevil: if you've solved a conflict and git-add'd your changes, git commit next
#14:06:54gmcharlteeevil: one just fixes the merge conflicts, then does a commit -c
#14:07:34moodaepoWill importing a pg_dump from 8.3 to a 9.0 server be an issue?
#14:07:39eeevilgit commit next == git commit -c ?
#14:07:59senator-c is if you care about editing the commit message
#14:08:14eeevilmoodaepo: maybe not :) ... (use the 9.0 version of pg_dump if you can)
#14:08:16eeevilthanks
#14:08:37eeevilhrm.. fatal: cannot do a partial commit during a merge.
#14:08:45moodaepoeeevil: Will do..
#14:08:56senatoreeevil: you don't have everything added then, i think
#14:09:01gmcharlteeevil: have you resolved all of the merge conflicts?
#14:09:05eeevilgit status says I do
#14:09:19senatoreeevil: using colors? if so, everything's green no red?
#14:09:36eeevilsenator: no colors, but green, yes. wanna see? :)
#14:09:49eeevil(please? ;) )
#14:09:54senatorsure
#14:10:04senator moseys
#14:11:10dbsmoodaepo: I've been doing 8.3 -> 9.0, seems to be okay
#14:11:34dbseeevil: cmon, fire up a public VNC session so we can all see!
#14:11:45moodaepodbs: I'm considering a pg_dump not a pg_upgrade or pg_upgrade_cluster
#14:12:06eeevilscreen -S githatesme
#14:12:07dbsmoodaepo: yes, that's what I did. pg_dump from the 9.0 machine
#14:12:26senatorit was my bad for being unclear: 'next' wasn't supposed to be part of the actual command
#14:12:27moodaepoGood to know!
#14:14:03moodaepodbs: Did you use the 9.0 pg_dump as eeevil suggested or 8.3 one? I don't have 9.0 installed on the 8.3 server (might have to do that to be safe)
#14:14:08eeevildbs: I'm tracking your social branch, btw ... keeping that at state at http://git.esilibrary.com/?p=evergreen-equinox.git;a=shortlog;h=refs/heads/social so I can poke at it a bit :)
#14:15:03dbsmoodaepo: yes. pg_dump works over the network, doesn't need to be locally installed
#14:15:26moodaepoAh I didn't think of that...graci
#14:16:10dbseeevil: cool! I was planning on pushing that to git.evergreen-ils.org proper; I think it's the only branch that I care about on gitorious (and it's been pretty much untouched for ages, sigh)
#14:17:16eeeviler ... s/at state at/at master state at/ ... not much better, but at least contains all the words
#14:17:41dbshmm. where should the tiny little governance directory from ILS-Contrib live?
#14:19:49gmcharltminigov.git
#14:20:56eeevilDyrcona_: so does the (now main?) SIPServer repo at git.evergreen-ils.org now have fees/fines support?
#14:21:46Dyrcona_eeevil: yes in that all that's required on the SIPServer side is the fix to the configuration of the 37/38 message.
#14:21:58Dyrcona_the rest of it is on the OpenILS
#14:22:13eeevilrad
#14:24:37gmcharlttsbere: pushed your mdp change, along with a tweak
#14:25:41tsberegmcharlt++
#14:25:50Dyrcona_eeevil: I still have to work on your suggestions for the fee payment code.
#14:26:23tsbere sees an svn commit go by
#14:27:46gmcharltdbs: to answer your question seriously, just eg-governance.git ?
#14:28:06dbstsbere: using it while it's still open
#14:28:32dbsgmcharlt: almost wondering whether it should be a subset of Evergreen.git or Evergreen-Documentation.git
#14:28:38tsberedbs: Was more of a "wait, wha?" moment for me when reading the subject line
#14:29:02tsberedbs: Evergreen.git I think no. Maybe the docs, but probably still no.
#14:30:48dbsI don't really care, as long as we don't end up having dozens of top-level git repos
#14:31:40gmcharltwe could stick it under contrib
#14:31:43gmcharltcontrib/governance.git
#14:31:45tsberedbs: Awww, you don't want a list like this? http://git.kernel.org/
#14:32:01dbstsbere: heh, if we had that many contributors I would be cool with that
#14:32:05gmcharlt would the level of activity that such a list would imply
#14:32:46gmcharlts/would/would love/
#14:33:15dbsgovernance contribs to evergreen - that seems about right
#14:33:31gmcharlt will make it so
#14:34:27natschil has quit IRC
#14:36:50natschil has joined #evergreen
#14:37:27moodaepo_ has joined #evergreen
#14:46:35gmcharltdbs: http://git.evergreen-ils.org/?p=contrib/governance.git;a=summary
#14:47:15dbsgmcharlt++ # thanks!
#14:48:08tsbereHow many more things need to be pulled out of ILS-Contrib?
#14:48:49dbsconstrictor needs a home
#14:49:00gmcharltyep, once berick is back from vacation
#14:49:02tsbere notes some things haven't changed for years
#14:49:12gmcharltand some, like upei, that are empty
#14:49:29dbsservres (Syrup) will need a home, given that there's an RFP for it now :)
#14:49:54dbsmost of ILS-Contrib is a ghost town though
#14:50:17Dyrcona_ watches tumbleweeds roll by.
#14:51:07Dyrcona_i suggest syrup getting its own repo.
#14:53:38jenny has quit IRC
#14:53:40dbsWell, crap. Time to move off of launchpad. "Currently, only the HEAD branch of a given Git repository may be imported." lame.
#14:54:35eeevilgah
#14:55:07eeevildbs: blithly disregarding tsbere's concern, we could have a repo-per-branch and link to each ;)
#14:55:26tsbereWait, my concern?
#14:55:36tsbereWasn't it dbs's concern? :P
#14:56:03eeeviltsbere: it was, nm
#14:56:26dbsAlso, going to have to find out if we can either bulk-change bugs currently pointing at trunk to point at master, or get the Launchpadians to do it for us
#14:56:43dbshaving repos-per-branch sounds rather horrible to me
#14:56:52eeevildbs: it does, I was totally joking
#14:57:28dbs rips the hook out of his mouth
#14:57:48dbscan't believe the foot that's usually in there didn't protect me
#14:58:13tsbere just had a crazy idea to fool git-daemon into thinking we had a pile of repos with different heads for each. It should probably not even be attempted.
#15:09:03AaronZ-PLS has quit IRC
#15:09:12AaronZ-PLS has joined #evergreen
#15:18:43kmlussier has quit IRC
#15:31:02kmlussier has joined #evergreen
#15:37:06Dyrcona_ has quit IRC
#15:44:18collsk12Heading home for the night. Just wanted to say thanks again and have a great day.
#15:44:30collsk12 has quit IRC
#15:50:05eeevildbs: re your new indexes ... it doesn't look like the index on deleted was necessary ... could you confirm that that's true? (your pasted explain analyze didn't use that, just the restrictive value index, IIRC)
#15:56:29dbseeevil: it depends on how many matches you get for the restrictive value index
#15:57:04eeevildbs: ok ... you wouldn't want it on (id)where not deleted? (since that's the join condition
#15:57:31dbseeevil: if you want to refine it further, go ahead
#15:57:47eeevildbs: well, I don't have a big dataset loaded to test
#15:58:13eeeviljust looking for ways to make the index more generally useful ... may not be worth looking
#16:00:39dbseeevil: sure. sorry, sluggish context-switching from copyright concerns over wiki -> docs. If you have something concrete you want me to test with multiple conditions, I'll be happy to do so
#16:05:45Dyrcona has joined #evergreen
#16:18:40bgoble has joined #evergreen
#16:23:49csharp:q
#16:23:53csharpoops
#16:30:26natschil has quit IRC
#16:31:53Dyrcona:q!
#16:31:59Dyrconaheh. wrong window. :)
#16:32:06Dyrconaj/k
#16:32:26gmcharltZZ
#16:32:45natschil has joined #evergreen
#16:37:11Callender has quit IRC
#16:38:24natschil has quit IRC
#16:43:30natschil has joined #evergreen
#16:43:46bjwebb has joined #evergreen
#16:43:46bjwebb has joined #evergreen
#16:50:44dbs has quit IRC
#16:54:15sfortin has quit IRC
#16:58:32moodaepo_ has quit IRC
#16:59:05natschil has quit IRC
#17:01:40jenny has joined #evergreen
#17:05:16AaronZ-PLS has quit IRC
#17:12:15kmlussier has quit IRC
#17:32:15Dyrcona has quit IRC
#18:03:05jenny has left #evergreen
#18:36:23bjwebb has quit IRC
#18:52:32bshumLooks like we may be missing a permission called "MARK_ITEM_MISSING_PIECES"
#18:53:01bshumTrying to see if this has been addressed in a more recent version of 2.0. We're a bit behind.
#19:01:11tsberebshum: Did you want to learn how to push your git work to the Evergreen working repo (instead of uploading patch files)?
#19:01:25bshumtsbere: That sounds pretty intriguing.
#19:01:34bshumtsbere: I have a few moments, sure!
#19:01:44tsbereok
#19:02:03tsberestep 1: git remote add working git@git.evergreen-ils.org:working/Evergreen
#19:02:18tsbereThat adds the working repo as an easily targeted remote
#19:02:41bshumDoing that within the same directory I have Evergreen cloned to, I presume?
#19:02:46tsbereYea.
#19:03:00bshumOkay
#19:03:27tsbereThen, to be sure it works, git fetch remote
#19:04:14tsberesorry
#19:04:18tsberegit fetch working
#19:04:22tsbereor git fetch --all
#19:04:36tsbere had to answer the phone while typing
#19:04:47tsbereAnd even worse, it was a wrong number
#19:06:25bshumHeh
#19:06:31bshumOkay, fetch appears good
#19:06:46tsbereAhh, good
#19:07:43tsbereNext up, push! specifically, "git push working <localname>:user/USER/<remotename>" where <localname> gets replaced with your local branch name, <remotename> with the remote branch name, and USER with your git username.
#19:09:49bshumWhat would a local branch name be? Oh like "working" as defined by default in the short git instruction guide we have on the wiki?
#19:09:58bshumOr should I be making it more constructive
#19:10:31tsbereThe local branch name is "the name of the branch you did the work in"
#19:11:16bshumGotcha
#19:11:30tsbereThe remote branch name is the name you want the public to see
#19:12:30bshumHmm, are there recommendations on how to name a remote branch? :)
#19:12:37bshumFor public viewing
#19:12:53tsbereI usually try and make it related to the work that happened in it.
#19:13:07ernieSimuro has quit IRC
#19:13:16bshumAha, I see.
#19:13:16tsbereBeyond that, whatever you are comfortable with
#19:15:05bshumOh spooky
#19:15:09bshumI think it did something
#19:15:31tsberehttp://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/bshum@biblio.org/google-link-fix
#19:15:45bshumNeat.
#19:17:08bshumtsbere: Thanks for introducing me to this.
#19:17:10tsbereNow you can push to the working repo and share the branch names with people
#19:19:18tsbereThe bigger the change the better help I think it is, but this way if they pull from there you get flagged in git as the author ;)
#19:27:05tsberebshum: In regards to that permission, even the master branch doesn't have it in the seed scripts.
#19:27:18tsbereThere are a number missing, actually.
#19:27:29bshumtsbere: That's what I was afraid of.
#19:28:08bshumtsbere: At some point I think we patched our system locally to fix that feature but never noticed the missing permission since all of our HQ staff have the -1 everything perm
#19:30:35bshumThose are all initially created in the 950.data.seed-values.sql file, right?
#19:30:52bshumAnd fixes added via upgrade scripts between point releases
#19:30:57bshum?
#19:31:13tsbereyea.
#19:31:19bshumFun, fun
#19:31:50tsbereI just found a few that are missing
#19:32:27tsbereCREATE_PURCHASE_REQUEST MARK_ITEM_MISSING_PIECES UPDATE_HOLD_REQUEST_TIME UPDATE_PICKLIST UPDATE_WORKSTATION
#19:33:44tsbereThose are just ones I found via scanning for any permissions the perl layer asks about in a basic fashion and then asking for those that don't have an entry in 950.data.seed-values.sql, that doesn't include ones set elsewhere.
#19:34:09youdonotexist has quit IRC
#19:34:13tsbere should look into a quick automated script to indicate permissions checked for in various ways
#19:38:47tater-laptop has joined #evergreen
#19:40:54bshumOh well. Have to tackle that tomorrow morning I guess.
#19:41:04bshumThanks again for showing me more git goodness tsbere!
#19:41:12bshumHave a good night.
#19:41:15tsberenight
#20:04:37moodaepoAny preferences folks? > http://bethesignal.org/projects/irclog2html/style_tt.html || http://bethesignal.org/projects/irclog2html/style_simpletable.html
#20:07:15moodaepobshum and I have been looking at prettyfication and he found this script which prettyfies. It is not a bot so supy/pinsol_green will still be creating the raw logs. We think we can just set it up so supy creates the log files and this script copies it over prettyfied to the public location say every minute/5 minutes/whatever.
#20:07:23moodaepo goes to walk the dog
#20:09:31eeeevil has joined #evergreen
#20:31:04tsbere throws a branch out for review: http://git.mvlcstaff.org/?p=tsbere/ILS.git;a=shortlog;h=refs/heads/perms_check
#20:31:23tsbere may bring it up again tomorrow
#20:33:42eeeevilhave you seen the xlst that attempts to do that? (may not work anymore, haven't tested it recently)
#20:35:13tsbereDoes it scan the perl for allowed('permission' and allowed(['permission','permission'] entries?
#20:35:37tsbereMine isn't perfect (it doesn't understand perl, for example) but I tried to get the easy pickings
#20:36:38tsbereAlso, this is intended to find *missing* permissions. Not just list them.
#20:36:51tsbereBased on bshum bringing up one that he found was missing
#20:41:39eeeevilno, it was only intended to do the ILD-supplied permissions that permacrud adds
#20:42:08bgoble has quit IRC
#20:43:06eeeevilsince it understands xml, it may be useful to fold that in to your tool ... being native. but the IDL perms are much simpler to parse, too
#20:43:18eeeevil runs away to watch LOST
#20:48:33jeffdavis has quit IRC
#20:58:40eeeevil has quit IRC
#21:35:42pmplett has quit IRC
#21:36:28pmplett has joined #evergreen
#21:45:02phasefxevergreen=# \i 0536.schema.lazy_circ-barcode_lookup.sql
#21:45:02phasefxBEGIN
#21:45:02phasefxpsql:0536.schema.lazy_circ-barcode_lookup.sql:8: ERROR: syntax error at or near ":"
#21:45:05phasefxLINE 1: SELECT evergreen.update_deps_block_check('0536', :eg_version...
#22:10:13tsberephasefx: My understanding (limited as it is) of that is "there is a script that is supposed to call those for you now"
#22:10:21phasefxah
#22:10:28tsbere didn't even build the script with that stuff in it, actually
#22:10:39phasefxsuspected that, but didn't really pay attention when folks were talking about it
#22:12:20tsbereI think you can "psql -v eg_version=NULL blah"
#22:13:36phasefxopensrf@dev141:~/git/Evergreen/Open-ILS/src/sql/Pg/upgrade (masslnc)$ psql -d evergreen -U evergreen -v eg_version=NULL -f 0536.schema.lazy_circ-barcode_lookup.sql
#22:13:39phasefxBEGIN
#22:13:42phasefxpsql:0536.schema.lazy_circ-barcode_lookup.sql:8: ERROR: function evergreen.update_deps_block_check(unknown, unknown) does not exist
#22:13:45phasefxLINE 1: SELECT evergreen.update_deps_block_check('0536', NULL); ^
#22:13:47phasefxHINT: No function matches the given name and argument types. You might need to add explicit type casts.
#22:15:03phasefx is using another db built from seed data, so this isn't a roadblock for him
#22:24:23phasefxeww, scary. I was using a bare git push from master, and it complained about rel_2_1 (because that was behind some commits). I didn't expect a bare git push to try to push all branches for the remote
#22:25:36tsberephasefx: Yea....I dislike that. Default is to push anything you have local that the remote also has.
#22:28:39tsbere@later tell eeevil In regards to the new trunk/master/whatever way of doing DB upgrade scripts....would it be wise to make that method work before we start committing scripts using it? phasefx had issues, and I can't find any scripts that look to apply updates properly?
#22:28:39pinesol_greentsbere: The operation succeeded.
#22:53:17bshum@later tell moodaepo Hmm, that logs2html part is tricky. Apparently it dislikes the date scheme and will only accept YYYY-MM-DD.
#22:53:17pinesol_greenbshum: The operation succeeded.
#23:28:30pmplett is now known as pmpafk
#23:38:50tater-laptop has quit IRC
< Monday, May 16th, 2011Raw Log FileWednesday, May 18th, 2011 >