Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, September 6th, 2011

< Monday, September 5th, 2011Raw Log FileWednesday, September 7th, 2011 >
#TimeNickMessage
#00:20:07Faizphasefx i am downloading prepacked version from evergreen site available for download
#00:44:09Faizevergreen-setup-rel_2_0_9_2.exe
#00:57:12Faizi have installed the evergreen client 2.0.9 it registers and gives error Error in props2object in message catalog in bindings.xml: Internalerror: allocation size overflow I have installed it from the evergreen site download link it was the pre-packed installer evergreen-setup-rel_2_0_9_2.exe
#00:58:43Faizi have installed the evergreen client 2.0.9 it registers and gives error "Error in props2object in message catalog in bindings.xml: Internalerror: allocation size overflow" I have installed it from the evergreen site download link it was the pre-packed installer evergreen-setup-rel_2_0_9_2.exe
#01:00:21jamesrf has quit IRC
#01:00:23Faizi have installed the evergreen client 2.0.9 it registers and gives error "Error in props2object in message catalog in bindings.xml: Internalerror: allocation size overflow" I have installed it from the evergreen site download link it was the pre-packed installer----- evergreen-setup-rel_2_0_9.exe
#01:02:09jamesrf has joined #evergreen
#01:11:49tater has joined #evergreen
#01:11:51mtate has quit IRC
#01:31:14youdonotexist has quit IRC
#01:39:55phasefxFaiz: what language/locale are you selecting with the staff client? en-US?
#02:03:22Faizhi phasefx Yes english US and windows 7
#02:03:50Faizi am installing the client evergreen-setup-rel_2_0_9.exe on windows 7
#02:23:31Faizi have installed the evergreen client 2.0.9 it registers and gives error "Error in props2object in message catalog in bindings.xml: Internalerror: allocation size overflow" I have installed it from the evergreen site download link it was the pre-packed installer----- evergreen-setup-rel_2_0_9.exe on windows 7 with english as language
#02:26:30phasefxFaiz: you should try your client against the 2.0.9 demo server listed here: http://evergreen-ils.org/dokuwiki/doku.php?id=community_servers see if it works for that server
#02:28:33Faizsame error
#02:28:56Faizi downloaded and installed but same error
#02:31:46phasefxyou used the server 75.101.133.94 with the login staff and password demo123?
#02:32:25Faizno i used that installer
#02:32:38Faizok if i use that login it works fine
#02:33:46Faizit means i have problem in my server
#02:35:39phasefxcompare this file, http://75.101.133.94/xul/server/locale/en-US/offline.properties with the one produced by your server
#02:35:58phasefxif identical, try the other .property files in that en-US/ directory
#02:43:22Faizyeah they are ok
#02:43:44Faizwhat do i do with .property file
#02:45:34Faizi have compared the two files mentioned they are same
#02:47:14phasefx.property files get used by the code that's breaking for you; so if your files are different, or if apache is mangling them in some way when serving them, that could account for the message catalog error
#02:48:32phasefxFaiz: I fear I must get some sleep; but I'll check my scrollback later. If you find any more clues, I suggest sharing them on the mailing list
#02:50:08Faizok
#02:51:18phasefxincidentally, I've never seen that error before
#02:56:11Faizniether did i
#02:56:44Faizwhere should i start diging now
#03:46:44artunit_ has joined #evergreen
#03:49:41artunit has quit IRC
#03:49:51artunit_ is now known as artunit
#04:03:37Callender has quit IRC
#04:42:24Faiz has quit IRC
#05:12:29Callender has joined #evergreen
#07:32:13bott-otr has quit IRC
#08:12:29dmoses has joined #evergreen
#08:12:41adbowling-isl has joined #evergreen
#08:18:39sfortin has joined #evergreen
#08:19:35dmoses has quit IRC
#08:29:00AaronZ-PLS has joined #evergreen
#08:34:34Faiz has joined #evergreen
#08:35:07Faizi have installed the evergreen client 2.0.9 it registers and gives error "Error in props2object in message catalog in bindings.xml: Internalerror: allocation size overflow" I have installed it from the evergreen site download link it was the pre-packed installer----- evergreen-setup-rel_2_0_9.exe on windows 7 with english as language
#08:35:47Faizi have also chkd the demo server and it resulted that my server end is faulty
#08:45:55Meliss has joined #evergreen
#08:49:17plux has joined #evergreen
#09:09:29natschil has joined #evergreen
#09:11:29natschil has joined #evergreen
#09:16:47natschil has quit IRC
#09:16:50Dyrcona has joined #evergreen
#09:18:04natschil has joined #evergreen
#09:18:13akilsdonk has joined #evergreen
#09:18:41natschil has quit IRC
#09:19:31natschil has joined #evergreen
#09:21:33natschil has joined #evergreen
#09:23:45natschil has joined #evergreen
#09:25:39natschil has quit IRC
#09:26:02natschil has joined #evergreen
#09:26:35natschil has joined #evergreen
#09:27:07jenny1 has joined #evergreen
#09:28:51jamesrf has quit IRC
#09:31:00jamesrf has joined #evergreen
#09:33:00natschil has quit IRC
#09:36:52dbs has joined #evergreen
#09:36:52dbs has joined #evergreen
#09:42:40kmlussier has joined #evergreen
#09:43:51tater has quit IRC
#09:44:06mtate has joined #evergreen
#09:46:52IRCReaderBOT has joined #evergreen
#09:47:48Faiz has quit IRC
#10:08:42collum has joined #evergreen
#10:11:03sal_ has joined #evergreen
#10:27:49gmcharlt has quit IRC
#10:31:25bott-otr has joined #evergreen
#10:34:06kmlussier has quit IRC
#10:34:29kmlussier has joined #evergreen
#10:45:43gmcharlt has joined #evergreen
#10:55:08yboston has joined #evergreen
#10:57:28bott-otr has quit IRC
#11:06:32gdunbar has joined #evergreen
#11:11:56matt_carlson has joined #evergreen
#11:13:43youdonotexist has joined #evergreen
#11:16:55tsberehmmm
#11:17:18tsbereWhat happens if I have a reporter datatype of "id' on a field that is not guaranteed to be unique when looking at that single data source?
#11:22:43gdunbartsbere: nothing good (says eeevil)
#11:25:50tsbere swaps it to "link" then
#11:26:46dbsphasefx: huh, can't find the evergreen trademark / logo info on the web site or wiki
#11:27:23dbsphasefx: specifically, the usage criteria
#11:29:07phasefxhrmm
#11:30:27phasefxI think this is the right end-point: http://www.georgialibraries.org/lib/pines/evergreenlogo/
#11:31:14collsk12 has joined #evergreen
#11:31:52dbsphasefx++
#11:31:59dbsyeah, search was doing nothing for me
#11:32:22dbsI think the logo / trademark is being transferred to SFC, but for now I'll link to that
#11:34:02DyrconaIs there a pull request meeting today?
#11:34:18dbsSupposed to be
#11:36:02phasefxdbs: oh man, I so thought that email was spam *8)
#11:36:09dbsheh
#11:37:47phasefxso the trademark/etc. are being transferred directly to the SFC? I thought we formed some legal entity that itself joined the SFC?
#11:38:19dbsphasefx: no, SFC is the legal entity
#11:38:44dbsof which the Evergreen project is a member organization, represented by the Evergreen Oversight Board
#11:38:57phasefxah, okay
#11:39:25phasefxtells you how mushy my brain is
#11:39:43dbsSo the Evergreen Oversight Board will need to draft some form of logo/trademark guidelines if GPLS transfers the logo/trademark to the SFC
#11:40:22dbs(probably s/GPLS/SFC under the advisement of the Evergreen Oversight Board/ or whatever)
#11:42:21dbs has been very un-devvy for the past few weeks owing to beginning of school deadlines :(
#11:42:32dbsso much ldap, so little time
#11:46:30collsk12 has joined #evergreen
#11:47:08jrodge01 has joined #evergreen
#11:50:58collsk12Odd question: I recently imported a MARC record into a brand new installation of Evergreen 2.1. After a great deal of struggle, I have the title showing up on the OPAC; however, when I use the "Holdings Maintenance" it still shows the example branches, even though I've already removed them.
#11:51:20mrpeters-islcollsk12: have you re-run autogen since deleting them?
#11:51:29collsk12Yes
#11:52:13mrpeters-islhave you made sure they don't exist in actor.org_unit?
#11:52:46mrpeters-islSELECT * FROM actor.org_unit WHERE shortname = 'BR-1'; -- that should be a good check
#11:53:02mrpeters-islor maybe it's BR1
#11:53:19mrpeters-islyeah, BR1
#11:53:37collsk12I've checked. Just the ones I've added show up.
#11:53:48phasefxalso, the staff client doesn't get its org info from the file autogen produces, but from an opensrf method. may need to restart perl services to eliminate caching
#11:54:08collsk12phasefx: Let me try that.
#11:58:10collsk12Nah, still there. The OPAC searches are also acting strangely. I have to manually select the library I want to search. Otherwise, I just get a spinning mouse cursor with no results.
#11:59:22dbssounds kind of like org_unit depths and org_unit_types are mismatched
#11:59:25phasefxmay want to sanity check org depths/types and ...
#11:59:56dbs also doesn't know if the version of 2.1 collsk12 is running needs cache-generator.sh still
#12:00:03phasefxhttp://evergreen-ils.org/dokuwiki/doku.php?id=scratchpad:random_magic_spells#finding_mis-matched_depths_with_org_units_and_org_unit_types
#12:04:55collsk12No results came back from the query and it's still showing this record as belonging to SYS2 and circulating in SYS2, yet it's available at CLMC.
#12:05:47collsk12What's cache-generator.sh?
#12:11:46artunit_ has joined #evergreen
#12:12:27matt_carlson has quit IRC
#12:13:19dbscollsk12: it was a temporary replacement for autogen.sh; you would call "cache-generator.sh -u". we're back to autogen.sh now I think.
#12:13:31dbspull requests? or no
#12:13:38artunit has quit IRC
#12:13:53artunit_ is now known as artunit
#12:15:04collsk12dbs: Ah...thanks. There is a cache-generator.sh in bin folder. Should I run it, or is that a bad idea?
#12:15:23dbsI would try it, just to see.
#12:18:19jrodge01I'm having some trouble with the installation.
#12:18:28collsk12dbs: No dice :(
#12:18:57tsberedbs: I think we should do pull requests. But I dunno if enough people are paying attention to IRC.
#12:19:32dbstsbere: I would like to, but the fire being applied to me for LDAP synchonizing here suggests I won't be able to pay attention either
#12:24:27collsk12jrodge01: What kind of trouble are you having?
#12:27:14dbwellscollsk12: I just pushed a branch which may fix what you are seeing. It is for 2.0, but I suspect if affects 2.1 as well. Here is the one simple commit: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=de74179598ecc00bcf0629382929dfeb9481757e
#12:28:51collsk12dbwells: Now that's service!! :) I'll check it out. Thank you.
#12:30:17dbwellscollsk12: Well, it might seem like it, but really just coincidence :) To test, apply the fix, then re-run autogen.sh. You may also need to clear the client cache, not sure.
#12:30:41collsk12OK...thanks again.
#12:31:30dbwellscollsk12: I am out for a bit, but will check the scrollback this afternoon to see how it went.
#12:32:03collsk12OK...enjoy. I'll update you in a few.
#12:44:39jrodge01collsk12: I have trouble starting OpenSRF. When I do, I get an error with Jabber saying I couldn't authenticate. I can type the error if needed.
#12:45:49eeevilre pull requests, it looks like tomorrow at noon won't conflict with any other community meetings. this being a short week in the US making today feel like monday for some of us, shall I put out a suggestion on -dev to coordinate for that?
#12:46:07gmcharlt+1
#12:49:28collsk12jrodge01: OK. How far along did you get? Did you register your Jabber users? And, if so, did you modify the conf files to reflect the passwords you registered?
#12:51:09Dyrconaeeevil: tomorrow works for me.
#12:54:39jrodge01collsk12: I believe so. I followed the installation instructions here: http://open-ils.org/dokuwiki/doku.php?id=opensrf:1.6:install
#12:55:04jrodge01collsk12: Up until "Starting OpenSRF"
#12:58:10akilsdonk has quit IRC
#12:59:16jrodge01collsk12: If you have any advice, please share. I have to step out for a bit, but will check back. If not, I'll go through the installation instructions one more time.
#13:04:25collsk12I would double check your conf files. If they look good, I would "unregister" your users and re-register them. I've had that work for me before. Keep in mind I am not a developer, nor do I play one on tv.
#13:08:57sal_jrodge01: why are you using the 1.6 install instructions?
#13:09:08sal_Which version of Evergreen are you planning to run?
#13:10:13sal_jrodge01: (Not sure how much difference there is, but opensrf is up to version 2.0.1; install directions here: http://open-ils.org/dokuwiki/doku.php?id=opensrf:2.0:install)
#13:27:09tsbereAnyone have opinions on how I did this? http://git.mvlcstaff.org/?p=tsbere/ILS.git;a=shortlog;h=refs/heads/extra_idl
#13:27:40tsbereWell, beyond "apparently should throw some of it further down the file so it doesn't show up as a *core* source" that I am discovering happens.
#13:35:35collsk12dbwells: Applied the fix and re-ran autogen. Restarted the client and all looks good. Thanks for the fix!
#13:45:26jrodge01 has quit IRC
#13:54:33matt_carlson has joined #evergreen
#14:05:16matt_carlson has quit IRC
#14:26:02collsk12 has quit IRC
#14:39:10adbowling-isl has quit IRC
#14:39:52adbowling-isl has joined #evergreen
#14:41:25natschil has joined #evergreen
#14:48:53eeeviltsbere: it shows up as a core source because of reporter:core="true", fwiw
#14:49:10tsbereeeevil: I literally just noticed that and was removing it from my new ones. <_<
#14:49:59tsbere is having issues with one of the two new ones, but has at least one more thing to try before trying to dig out errors
#14:51:02eeeviltsbere: I'm not a fan of a magic number when "unknown" (aka NULL) is a reasonable answer ... any reason to coalesce there?
#14:51:33tsbereeeevil: On which piece?
#14:51:33eeevilalso, may want to use the all_circulation view to account for aged circs
#14:51:52eeevilthe rlc <class>
#14:52:14eeevilsorry, was just looking at the last commit
#14:52:15tsbereand yea, I realized I wasn't using all_circulation. Am more concerned with getting it to work, then I will make that one behave.
#14:53:34tsbereas for the magic number.....what happens if I try and say the age of a null is greater than X?
#14:54:28eeevilNULL > X -> false
#14:54:34eeevilNULL < X -> false
#14:55:05eeevilif it hasn't circ'd, it doesn't have a last circ date :)
#14:55:17tsbereThat particular one is intended for use with a weeding report (with the commented out form of it for us). They want "never circulated" copies to show up in such reports.
#14:56:16eeevilso, the semantics are more like "created or last circ'd", yes?
#14:56:37eeevilI mean, you don't want to include brand new copies in a "haven't circed in 10 years" report, right?
#14:57:19tsbereThe way they talk? Some of them might.
#14:57:26eeevilso, a created_or_circulated timestamptz column seems reasonable, assuming I'm right ;)
#14:57:44tsbere is trying to figure out why the reporter thinks asset.copy has a last_circ column right now
#14:59:10eeevilsounds like a virtual field for holding the id of the most recent circ
#14:59:24eeevilmissing oils_persist:virtual="true" maybe?
#14:59:32eeevilyep
#14:59:48eeevilnope
#15:00:10tsbereWhile I am in the file anyway
#15:00:24eeevilahh... because it's a has_a relationship
#15:00:27tsbere moves to all_circulation view and changes magic number of year 1 to the copy creation date
#15:01:10eeevilmight_have is probably what you want (even though it will always be there in your view)
#15:01:38tsbereok
#15:02:38jamesrf has quit IRC
#15:02:48tsbereThe other new one appeared to work right away for me. Ran a couple tests, moved on. <_<
#15:04:40tsbereYou see any issues with it while I test some of the changes to the last circ one?
#15:06:07jamesrf has joined #evergreen
#15:06:15eeevilthe other one is interesting ... it's a point in time only report ... the WHERE clause may need to grow, but it's probably "close enough" since the data it's using will be constantly changing anyway
#15:06:52tsbereIt is supposed to be a point in time report
#15:06:58eeevilright
#15:07:07eeeviljust observing the obvious ;)
#15:07:19tsbereThere is a similarish one next to it in the IDL that does things very differently.
#15:11:00tsbereOh, hey, cool, an error message I understand........because postgresql is a PITA sometimes. <_<
#15:13:25eeevilthat other one is meant to be a relatively performant approximation. how fast does your new one run on large datasets? (I may be able to test that soon, btw)
#15:13:59tsbereI can run both queries and compare them on the same large dataset if you want
#15:15:22eeevilif you include a definition of large, I'd love to see that, actually (hold count, bib count, copy count, hold-copy-map size) ... and, obv, it only needs to be fast when there's a where-clause supplied, like, for bib id, or pickup lib in yours.
#15:15:31eeevilI wouldn't expect the baseline to be fast ;)
#15:16:06tsbereMine just spit out 37323 rows in 13924 ms. The one that was already there is still running.
#15:16:16tsbereSans where clauses
#15:16:33eeevillike: SELECT * FROM ( ... that big view ... ) WHERE bib_id = xxx;
#15:16:43eeeviltsbere: right, but with a param...
#15:16:46tsbereThe one already in the IDL returned 21663 rows in 66670 ms
#15:17:11eeevilthe old one is used with a param from within the UI
#15:17:17tsbereWell yea.
#15:17:35tsbereBut how do you expect me to pick a bib number with holds unless I grab a list of bibs with holds? ;)
#15:17:42eeevilheh
#15:19:05akilsdonk has joined #evergreen
#15:19:28tsbereAlso, the two give me very different results on a lot of holds for copy count
#15:21:06tsberedoing the "SELECT * FROM ( blah ) WHERE id = x" for a specific X (and with an alias on the blah) mine is actually much faster, though. Let me find one with a bigger hold count, though. I randomly grabbed one with a single hold, period.
#15:23:20tsbereRunning on the exact same dataset, mine returned 37 rows for a bib with 442 holds and 43 copies everywhere in 10,834ms. The one from the IDL sees the same number of holds and copies but due to lack of pickup library returned one row, but took 64,254ms to do so.
#15:28:07tsbere wasn't really expecting his to be faster, due to trying to return more info
#15:31:36tsbereeeevil: I think the one in the IDL is hindered by all the subselects going on.
#15:36:08berick thinks the EG git server might need NTP
#15:36:35senator thinks every server needs ntp
#15:36:41berickwell, yeah ;)
#15:36:43dbs curses the barbarians that force YY-MM-DD date format even in civilized locales like en-CA
#15:37:29dbs"Why is this person's account expired? It's not Oct 2011 yet!"
#15:37:48berick(checks to see if the commit author's machine was not the source of the future timestamp)
#15:38:18dbscommit time vs. authoring time?
#15:39:22bericknote to committers, plz install NTP :)
#15:39:59tsbereberick: I think at one point I installed NTP on the git server already
#15:41:04bericktsbere: indeed, I take back my comment about the server.
#15:41:13berick'twas a client-side issue
#15:41:24kmlussier has quit IRC
#15:41:29phasefx has chaos powers across time and space
#15:41:47kmlussier has joined #evergreen
#15:42:08tsbereeeevil: Would you like me to take a crack at re-writing the hold ratio query that was already there?
#15:42:56dbs religiously types "date --set '1972-01-01'" before committing anything
#15:43:45eeeviltsbere: sorry, stepped away. sure, go for it. I'll look for some time to test it on another large dataset soon
#15:45:43tsbereeeevil: For the record, the dataset I was running on has 902196 bibs, 3267915 copies, 55232 active holds
#15:46:04tsbere(excluding deleted bibs and copies)
#15:55:35eeeviltsbere: thanks. I should be able to test on something comparable ... are you building a test script, btw? (np if not)
#15:56:04tsbereI have not built a test script. I keep running things via pgadmin
#16:05:12Meliss has quit IRC
#16:24:06tsbereeeevil: http://paste.lisp.org/display/124516
#16:27:30adbowling-isl has quit IRC
#16:28:20dbs has quit IRC
#16:28:49kmlussier_ has joined #evergreen
#16:29:54eeevilarg! can't force-push to working... bah
#16:30:34kmlussier has quit IRC
#16:30:46kmlussier_ is now known as kmlussier
#16:31:24eeevilgrabbing 0615
#16:31:55tsbereeeevil: You should be able to force-push to working. Unless it is someone else's collab?
#16:32:22eeeviltsbere: it is
#16:32:40eeevilit's fine, though. was just going to push an amended commit msg
#16:32:45eeeviland then merge
#16:32:48eeevilso... no biggy
#16:35:38collum has quit IRC
#16:39:24plux has quit IRC
#16:42:59tsbereeeevil: You have any opinions on potential accuracy versus speed where both options are a massive improvement on the original?
#16:45:02eeeviltsbere: if the semantics of the new version are as correct or more so than the original, then I have no problem replacing it ... but I haven't looked very closely at that. Is that what you mean?
#16:45:52tsbereeeevil: I came up with two replacements. The slower one uses the hold copy maps and I think gets more accurate copy counts on a number of hold types. The faster one should return things identically to the original.
#16:47:35eeeviltsbere: using the hold-copy-map has the drawback of missing "new" copies (not yet placed on the potentials list) .... the one without can overestimate the copy count, of course (and is more work to maintain, as the definition of holdability changes)
#16:49:17tsbereso one can overestimate copy counts and is potentially more work to maintain. The other can underestimate copy counts but automatically obtains new holdable information from the perl layer.
#16:49:22eeevilsince it's meant to be an approximation for immediate use in a UI, I'd tend toward faster if it's close enough
#16:49:58tsbereSome of the records I see go by have hundreds of potential copies in the non-maps version and <10 in the maps version
#16:50:01eeevilor, that's an important use case ... not the only one, of course
#16:51:12tsbereand I see a few metarecord related holds that result in a reversal. The non-maps version reports a smaller number than the maps version, because the non-maps version doesn't take into account the other format records and their copies.
#16:51:12eeevilhrm... that amount of a discrepancy is a concern
#16:51:33eeevilright, I'd expect that for M-type
#16:52:13tsbereThe "hundreds without the hold copy maps, only a few with" happens when all of the holds are part holds, copy holds, and volume holds, it seems.
#16:52:40eeevilahh... /that/ sounds like an improvement, then
#16:53:25eeevilhow big is your hold-copy-map?
#16:53:53tsbere947886
#16:54:10bgoble has joined #evergreen
#16:59:46tsbereeeevil: So do you think the slower version using the hold copy map table is the better choice (given that even it is significantly faster than what is there now)?
#17:04:50eeeviltsbere: well, the times you're getting don't jibe with what's in use at a production site, so I'll need to look closer, but I'd like to test all variants for sure
#17:05:46eeevilwhich I'll have to do later ... COMMUTE TIME! :)
#17:06:17eeevilbiab
#17:06:26natschil has quit IRC
#17:06:37tsbere is using a copy of MVLC's production database that tends to get less CPU and memory than the actual production DB
#17:07:00tsbereProduction data (as of Sunday morning) though
#17:23:39akilsdonk has quit IRC
#17:30:46Dyrcona has quit IRC
#17:36:31kmlussier has quit IRC
#17:37:56artunit_ has joined #evergreen
#17:39:23artunit has quit IRC
#17:39:33artunit_ is now known as artunit
#17:52:19bott-otr has joined #evergreen
#17:57:07jenny1 has left #evergreen
#18:01:35sal_ has quit IRC
#18:12:28sfortin has quit IRC
#18:25:39yboston has quit IRC
#18:32:59matt_carlson has joined #evergreen
#18:53:15_bott_ has quit IRC
#18:54:02_bott_ has joined #evergreen
#19:00:07matt_carlson has quit IRC
#19:17:40youdonotexist has quit IRC
#19:23:13bott-otr has quit IRC
#19:26:40bott-otr has joined #evergreen
#20:25:54jtgorman has joined #evergreen
#20:31:38bott-otr has quit IRC
#20:32:53bott-otr has joined #evergreen
#20:37:16bott-otr has quit IRC
#20:48:04jtgorman has quit IRC
#21:00:05bgoble has quit IRC
#21:26:25_bott_ has quit IRC
#21:56:12gdunbar has quit IRC
#21:56:12leed has quit IRC
#21:58:12gdunbar has joined #evergreen
#21:58:12leed has joined #evergreen
#22:59:29youdonotexist has joined #evergreen
< Monday, September 5th, 2011Raw Log FileWednesday, September 7th, 2011 >