Evergreen ILS Website

Search in #evergreen

Channels | #evergreen index




Results

Result pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148

Results for 2013-06-11

11:22 tsbere My hate is more general ;)
11:23 bshum tsbere++
11:36 DPearl joined #evergreen
11:45 DPearl Help! I'm installing opensrf on a new machine and it is not starting up.  The srfsh test failed with "unable to bootstrap client".  It looks like the router is failing.
11:46 DPearl I have checked and rechecked the ejabber users, and they look fine.
11:47 DPearl The .srfsh.xml is fine.
11:47 phasefx if you grep your osrfsys.log for ERR, what's the first hit there?
14:09 bshum dbs: +1
14:10 bshum paxed: I'm not fully up to speed with the details, but I think the screen reader just works alongside the browser, so there's no clear indication whether they're using one or not vs. just using a browser.
14:10 paxed bshum: ah... right.
14:10 kmlussier Yup. I was using standard browsers in my own testing.
14:12 senator if dijit removes the aria-label attribute, can the problem be solved by adding it back to some <span> element surrounding the input widget?  or is there more to it than that?
14:13 * dbs looks at Driver/Pg/QueryParser.pm and wonders if line 311/312 is where the pain in apostrophe searching arrives
14:13 * bshum peruses
14:13 dbs this code could use some comments, and maybe some more expressive var names. $c looks pretty important, just have to figure out what it is
14:14 dbs a boolean for "is combined" I guess
14:15 akilsdonk_ kmlussier: it looks like all the new documentation has been processed into 2.4 now.
14:17 kmlussier senator: I don't know much about the code, but I wouldn't be surprised if the problem goes beyond the arial-label attribute.  2.2 catalogs didn't use the arial-label attribute, and, if autosuggest wasn't enabled, you could still identify the correct form elements by tabbing or using the JAWS commands. But that was just my uneducated gut feeling when I was testing.
14:18 kmlussier akilsdonk_++ Thanks! Of course, now that it's displaying, I now see I neglected to make some changes to the root file.
14:20 akilsdonk_ kmlussier: Yeah, I had to make a few changes too. :)  Thank you!
14:20 akilsdonk_ kmlussier++ dbs++ rsoulliere++  We have docs!
14:20 kmlussier http://www.nomensa.com/blog/2011/h​ow-do-you-detect-a-screen-reader/ tells us we can't detect screen readers.
14:55 eeevil hrm... maybe not
14:55 * eeevil thinks more
14:55 dbs Check line 583 of Driver/Pg/QueryParser.pm
14:55 tsbere dbs: Isn't that the *test* setup, where we don't have a DB to pull things from?
14:56 dbs tsbere: I dunno, I'm just trying to unravel this!
14:58 dbs so "config_metabib_class_ts_map" should bring us DB-based config?
14:59 dbs I have simple -> A, english_nostop -> C in my test config.metabib_class_ts_map table. Doesn't seem to be resulting in any english_nostop in the actual queries.
14:59 tsbere we *do* assume "just simple" if we don't have any info, so if something is broken on the "fetch from DB" side of things that would be the only thing we got...
15:00 dbs Sounds like something might be broken (quite consistently) then.
15:00 dbs As this has been confirmed on all sites running 2.4
15:24 eeevil ;)
15:24 eeevil thinking_of_the_future++
15:25 jeff_ isl-JBoyer++ welcome!
15:26 dbs eeevil: actually, note that all of my tests have been against the 'title' field
15:27 eeevil dbs: consider it noted
15:27 dbs hmm, and config.metabib_field_ts_map is devoid of rows on our test database
15:27 eeevil using_the_same_words_for_testing++

Results for 2013-06-10

09:48 mmorgan1 tspindler: dbs: something related to the receipt templates makes sense. seems a likely place for a problem.
09:50 tspindler mmorgan1:dbs: Jim was also saying that it might be related to Windows and how it handles printing not releasing memory and not as much to do with Evergreen.  I'm not sure.  I don't  know enough tot say that.
09:51 tspindler pardon the emoticon, typo
09:51 paxed should perhaps rig a quick test that repeatedly calls the printing routines, and just closes the print window or something
10:23 kmlussier joined #evergreen
10:27 ericar joined #evergreen
10:28 Ruth joined #evergreen
11:34 pinesol_green csharp loves supybot plugins; virtualization; lasagna; logs; clarity; all y'all; upgrades; tpac; git; this venue; google; and not being evil
11:34 Ruth you're a very loving person
11:34 csharp @hates
11:34 pinesol_green csharp hates dojo_hold_policies_interface; SIP; when libraries purchase third party products without testing and blame Evergreen for it not working; reports; the fact that the Base Filters is unnecessarily greyed out when applying an Aggregate Filter and vice versa; and evil
11:34 mcooper joined #evergreen
11:44 acoomes joined #evergreen
11:51 Ruth @loves vacation

Results for 2013-06-07

11:35 bshum It's listed as March 19-22 on my calendar anyways.
11:36 berick huh, must have gotten pushed back
11:40 ThePoster60 joined #evergreen
11:42 bshum berick: I'm going to try out your new wrong shelf hold branch.  I remember trying it during the 2.4 cycle and having some weird network error crash.
11:43 bshum But that might have been something wonky with our test server.
11:43 bshum Good to get fresh eyes on it again.
11:43 * phasefx is testing it too
11:45 bshum Ah okay.  I probably wasn't going to get to all of it before today's cutoff, I just meant in general.
11:45 bshum phasefx++
11:46 phasefx this close > < I think
12:07 jihpringle joined #evergreen
12:12 krvmga joined #evergreen
12:13 krvmga i was looking at the sql generate for reports and found  a big section on relation under rel_cache. anyone know what/where rel_cache is?
12:22 jeff_ Dyrcona: you have build scripts for test instances somewhere -- or am i imagining things?
12:23 jeff_ Dyrcona: rephrased, do you have build scripts for building test evergreen systems available somewhere?
12:24 Dyrcona jeff_: I currently have this https://docs.google.com/document/d/1s8C1ZLSgHwv​DZOpinuHoku0ABbOjoHrs-iHBZPbCch0/edit#heading=h.b44ysgz2myvl
12:26 Dyrcona Whos is "Anonymous Chupacabra?" ;)
12:26 Dyrcona I should have used that as my /. handle.
21:05 pinesol_green rfrasur: NO!
21:05 rfrasur good to know
21:05 jcamins rfrasur: having fun with the bot?
21:05 rfrasur yep
21:06 rfrasur I tested some of them in a pm, but some don't work that way
21:10 rfrasur if people want to do something productive, just tell me to knock it off.
21:10 * rfrasur won't be offended.
21:11 jcamins @librarian
21:11 pinesol_green jcamins: Management:15, Cataloging:12, Acquisitions:14, Reference:12, Circulation:12, Systems:12, Research:10, Custodial:14
21:11 jcamins ^^ my favorite

Results for 2013-06-06

09:32 pinesol_green Launchpad bug 1187035 in Evergreen "Remove obsolete OpenILS::Utils::Editor" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1187035 - Assigned to Jeff Godin (jgodin)
09:42 jeff_ berick: zero toes were harmed!
09:42 berick excellent
09:42 jeff_ all i had in mind was to clean up my commit message and test / get exactly the kind of eyes you put on it -- thanks for catching the $e->request bits
09:42 kivilahtio Hi all! Is there a guide on how to get logging statements to show in the open-ils.serials_stderr.log or opensrf logs?
09:42 kivilahtio I have read Dan Scott's articles about easing gently into OpenSRF and I get syntax errors! Also went through the opensrf.xml & opensrf_core.xml and found references to the unix_log files named <unix_log>open-ils.serial_unix.log</unix_log>
09:42 kivilahtio This should export the $logger-object to the package?      use OpenSRF::Utils::Logger qw/:logger/;
09:59 kivilahtio jeff_: yeah I kinda figured that out after the OpenSRF tutorial, but it didnät work before that either. I'll try
10:00 kivilahtio jeff_: do you have any idea about the open-ils.serials_stderr.log ?
10:00 kivilahtio can one push statements there?
10:00 jeff_ kivilahtio: i would expect this line to work, assuming that $obj exists and has an as_string method. have you tried logging just a basic scalar, or a fixed value, as a test? $logger->error("HELP I AM STUCK IN A SERIAL FACTORY"); or the like?
10:00 kivilahtio jeff_:  yes :)
10:01 jeff_ hrm. strange. perhaps the Serial.pm file which you are editing is not the Serial.pm file which is being loaded by the system? (going back to basics)
10:01 jeff_ (rather -- trying the simple things)
10:02 kivilahtio jeff_: yeah. but it should work and I'll try to work from there, thanks
10:02 phasefx we should expose a private API call for testing logging, if one doesn't already exist
10:03 jeff_ kivilahtio: good luck -- sorry, I'm out of ideas for the moment. also, I'm not certain on the stderr logs, though I would have expected warn() to hit them -- which is why I was wondering if the file you were editing was not the file being used by the system when starting services.
10:03 phasefx registered OpenSRF method, that is
10:04 kivilahtio phasefx: what do you mean? add it to the opensrf.xml ?
10:04 kivilahtio phasefx: or the opensrf_core.xml? I couldn't find any serials related entries there
10:04 phasefx kivilahtio: I mean, it would be neat to be able to use srfsh and just say something like  request open-ils.actor opensrf.log.error "testing 123"
10:04 kivilahtio phasefx: ah
10:05 phasefx not that such a thing would have necessarily been of help here
10:08 kivilahtio phasefx: I think i solved the osrfsh.log issue, still getting nothing in the serials_stderr.log
10:33 gmcharlt dbs++
10:33 jeff kivilahtio: when a service is started, it should try to open the stderr log file. if it fails, it will log at the error level, "server: unable to open STDERR log file: [...] " if it succeeds, it will log at the internal level (which you probably are not logging), "server: redirecting STDERR to [...]"
10:34 jeff kivilahtio: you might want to restart the service(s) and look for errors in the opensrf log mentioning STDERR -- also, verify that file ownership and permissions on the stderr files permit your user (likely opensrf) to write to them.
10:34 dbs paxed: I'm working on testing a commit for bug 1020625 atm
10:34 pinesol_green Launchpad bug 1020625 in Evergreen "TPAC unable to link to specific organization by shortname" (affected: 1, heat: 6) [Wishlist,Confirmed] https://launchpad.net/bugs/1020625
10:37 kivilahtio jeff: no errors with keywords serial and redir
10:37 kivilahtio write persmission for oser opensrf
11:55 rfrasur eeevil:I knew it could be done...but didn't know how.  Thanks :-).  Now I have some of the right words to say (in the future...when there's someone to say them to)
11:59 phasefx heh, I can't edit bug status in launchpad with my version of chromium
12:02 mllewellyn joined #evergreen
12:08 dbs paxed: testing 1187316 right now
12:09 Ruth joined #evergreen
12:10 dboyle joined #evergreen
12:10 paxed how do you handle the ssl cert for the staff client in automatic client installs?
12:19 pinesol_green Launchpad bug 1158218 in Evergreen "Improve db-seed-i18n.py to actually grab all strings for translation" (affected: 1, heat: 6) [Undecided,Triaged] https://launchpad.net/bugs/1158218
12:20 jihpringle joined #evergreen
12:20 paxed dbs: "so they be built" ??! :D
12:20 dbs that be right
12:24 dbs paxed: that one requires more testing, and I don't really have time. putting the whole thing on one line is known to work, and there are tests for it in tests/testSQL.py ; I'm loathe to add support for multiline parsing without corresponding tests
12:25 paxed ok, i guess i should write tests for it then too.
12:27 dbs added a comment correspondingly; in this case, it's just extending existing test data & expected output so it should be pretty easy to do
12:45 sseng_ How does a person add a predefine message in the drop down list for the "Apply Standing Penalty/Message" in the "Messages" tab of the staff client? Been trying to search around but not coming up with much.
12:45 stevenyvr2 joined #evergreen
12:47 ericar joined #evergreen
13:07 ldwhalen joined #evergreen
13:07 jdouma joined #evergreen
13:09 * dbs shakes head slowly at mutt and google's ssl certificates
13:11 paxed dbs: i'm adding some contrived test cases, not just examples lifted out of 950.*.sql
13:11 dbs paxed: cool, exercise it thoroughly :)
13:13 kyleonalaptop joined #evergreen
13:16 mjingle joined #evergreen
13:35 * kmlussier fears that August will come sooner than expected. :(
13:35 kmlussier rfrasur: I'll take whatever thoughts you want to send my way. :)
13:36 rfrasur kmlussier: Also, if there's something that doesn't require a vast amt of tech know-how, I'd be willing to TRY and help.
13:36 paxed dbs: the branch now has test cases too. dunno if it was ok to delete the remote branch and recreate it from my local one ...
13:37 rfrasur hmm, I suppose in this "room," I should say...barely any tech know-how
13:38 paxed (what's the best way to handle a case where your local repo doesn't have the same branch? i just created a branch, cherry-picked the changes from the remote one, hacked, amended commit, deleted the remote branch and pushed my local out as the same name branch...)
13:39 dbs paxed: okay with me
14:03 * rfrasur is Ruth Frasur, Evergreen Indiana
14:03 * rsoulliere is Robert Soulliere, Mohawk College
14:03 pinesol_green [evergreen|Dan Scott] Fix Latin-1 encoding that broke doc output - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=96c877e>
14:05 yboston we might be a small crowd today, but any meeting that Robert and Kathy attends is a success to me
14:05 yboston #topic Updates from Content Coordinators
14:05 yboston We will continue having the content corrdinators try out the "#topic" AND "#info" Meetbot commands for their reports
14:05 yboston So content coordinators, please use "#topic" for the first post/line of your report
14:05 yboston then use "#info" for every other chat post/line of your report.
14:05 yboston for example...
14:06 yboston #topic this is a test report first post/line
14:06 yboston #topic this is a test report first post/line
14:06 yboston #topic this is a test report first post/line
14:06 yboston #info this is a test report second post/line
14:06 yboston (sorry having pasting issues)
14:06 yboston who would like to go first..
14:07 kmlussier #topic DIG Release Coordinator Report
14:07 kmlussier #info Nothing to report in terms of release coordination.
14:08 kmlussier #info I did get some udpated 2.4 acq docs done, but have a few more to work on.
16:08 bshum Maybe its just me, but it looks like phasefx is committing from the future.  By just a few minutes but it's wigging me out man!
16:08 gmcharlt :)
16:09 * phasefx wiggles his chaos fingers
16:09 Dyrcona jeff_: Looks like we might be putting your RESTful API to the test, too.
16:10 gmcharlt bshum: there's a reason we never let phasefx drive at exactly 88 mph
16:10 jeff_ cool. in any context of NCIP, or unrelated?
16:10 Dyrcona jeff_: In context of NCIP.
17:19 gmcharlt Dyrcona: yeah, I think that's bug-worthy
17:22 phasefx berick: I'm going to push a branch with the Current Shelf Library column
17:23 phasefx well, first I'm going to make sure I didn't break master :)
17:24 rs233 Dyrcona: I think I found where A problem is where I added a line to the xml that was not exactly correct.. I believe the Server is runnin now will try some testing
17:25 Dyrcona rs233: Good luck!
17:25 berick phasefx++
17:25 rs233 I might be back tomorrow lol

Results for 2013-06-05

08:57 Callender joined #evergreen
08:59 tfaile joined #evergreen
09:01 mmorgan1 joined #evergreen
09:02 dbs bshum: don't sigh about acquisitions testing, please... we're going to try seriously adopting acq after we upgrade to 2.4, and I'm sure all the basic stuff works flawlessly. _flawlessly_.
09:02 * dbs still needs to test that basic stuff, is crossing fingers.
09:15 kmlussier dbs: acq has come a long way in the past year. I hope your testing goes well!
09:24 jeff___ joined #evergreen
09:25 Simon21 joined #evergreen
09:25 pmurray_away joined #evergreen
09:41 Dyrcona The 404 is likely 'cause I missed something that needs to be configured.
09:42 rjackson-isl we have a book mobile in offline mode due to poor connectivity and wondered if this would help...
09:42 jeff_ the offline patron list downloads a list of barred/lost/expired/penalized patron barcodes, and it depends on offline-blocked-list.pl being run (usually via cron) to generate the list.
09:43 rjackson-isl ok - I will see if I can get that going in test jeff_ ++
09:43 bshum Yeah, for some reason Indiana's list.txt is empty.
09:43 shadowsp1r joined #evergreen
09:45 Dyrcona jeff_++ # I should have known that.
09:47 dbs kmlussier: thanks for the reassurance :)
09:48 kmlussier dbs: What tools did you use when testing accessibility in tpac?
09:49 tater joined #evergreen
09:54 kmlussier dbs: nm, I found it.
09:54 bshum dbs: I only sigh about testing new acq "features".  It's hard to test expected behavior sometimes :(
09:54 bshum But I agree with kmlussier that acq has come a very long way from when we first started using them back in 2.0 days.
09:54 mllewellyn joined #evergreen
10:15 kmlussier Should https://bugs.launchpad.net/evergreen/+bug/1155278 be backported since it is an accessibility issue? Looks like it was only committed to 2.4.
10:15 pinesol_green` Launchpad bug 1155278 in Evergreen "TPAC: Accessibility audit compliance" (affected: 3, heat: 14) [Undecided,Fix released]
12:20 kyleonalaptop joined #evergreen
12:21 mllewellyn joined #evergreen
12:23 ldwhalen joined #evergreen
12:25 eeevil paxed: it looks ok to me, but I haven't tested it
12:25 paxed the material() sees only the full 007 field, not the one character from pos 1
12:30 eeevil this won't address that, but start_pos is 0-based
12:30 paxed yes, and i'm looking for the 2nd character.
12:50 eeevil what does the following return for you? SELECT biblio.marc21_extract_fixed_field( $bibid, 'material'); -- replace $bibid with an appropriate bib id
12:51 eeevil to purge material, UPDATE metabib.record_attr SET attrs = attrs - 'material';
12:51 paxed that returns just one char, correctly
12:52 eeevil cool. so, I guess, purge and then reingest a couple records. then search for "material(x)" (no quotes, replace "x") to test
12:52 paxed # UPDATE metabib.record_attr SET attrs = attrs - 'material';
12:52 paxed ERROR:  Unexpected end of string
12:53 eeevil maybe got smartquotes from cut/paste?
15:07 * rfrasur prefers analog legos
15:08 eeevil paxed: so, there's already a sophisticated 007 parser. what, in particular, are you trying to accomplish? SMD filtering, I believe?
15:09 paxed eeevil: it started as a learning experience, now i'm just trying to get this working. SMD? what 007 parser?
15:10 kmlussier dbs: Have you loaded the fixes from https://bugs.launchpad.net/evergreen/+bug/1155278 to your production server? I was using your catalog for comparison when testing a problem here, but then remembered you're not on 2.4 yet.
15:10 pinesol_green` Launchpad bug 1155278 in Evergreen "TPAC: Accessibility audit compliance" (affected: 3, heat: 14) [Undecided,Fix released]
15:11 * kmlussier wonders if there are any production systems using both 2.4 and auto suggest.
15:11 eeevil 007/01 (second character in 007) is described as the SMD field for ... well ... it looks like all record types. http://www.oclc.org/bibforma​ts/en/0xx/field007table.html (easier to read, IMO, than the LOC version)
15:11 kmlussier Ooh! Looks like SC LENDS is.
15:12 paxed eeevil: well, i usually read the marc21 format in finnish, so i wouldn't know/remember what "SMD" stands for.
15:12 dbs kmlussier: our test server ( http://laurentian-test.concat.ca ) has that loaded - and I think I did apply it to our production server, but can't recall for sure
15:13 kmlussier dbs: Ok, I'll look there too. Thanks!
15:13 eeevil paxed: gotcha, fair enough. so, you were looking for the 007/01 on a particular record type originally, what was that type?
15:14 dbs kmlussier: IIRC, autosuggest is a massive pain for accessibility; at least in our implementation, where Dojo dijits don't even make ARIA a viable option
15:14 fparks joined #evergreen
15:15 eeevil paxed: ok, so, where 007/00 = c, correct?
15:15 paxed eeevil: so what filter gets the 007/01?  yes
15:16 dbs kmlussier: http://www-test.concat.ca/ is closer to stock than our LU skin
15:16 kmlussier Yes, that's what I'm finding. C/W MARS modified their searchbar.tt2 based on your changes, but it still seems to be problematic in IE and Chrome. I'm not sure if was the problem with the way we patched it or if further work is needed.
15:17 * kmlussier hasn't even looked at advanced search yet. :P
15:17 dbs kmlussier: I couldn't easily fix the problem that autosuggest introduces, so I didn't
15:21 kmlussier dbs: This morning, I used Chrome's accessibility add-on and had no trouble. It may just be a JAWS issue, but, then again, JAWS has a big share of the market.
15:21 dbs kmlussier: yeah, understood. I can't recall if I checked the recent Dojo version to see if that issue had been addressed
15:23 paxed eeevil: ok, now how do i do a filter for any type of record, or do i have to make a different filter name for each type of record?
15:23 kmlussier dbs: Thanks for the info. So it sounds like disabling java or using Firefox are some workarounds for the time being. I'll test try some tests with java disabled.
15:23 eeevil dbs: I believe ARIA is surfaced much better in modern dojo's
15:25 eeevil paxed: the values in 007/01 overlap across record types ("a" means different things based on 007/00), so the short answer is "yes, a filter per type". that being said, what you've been trying to do /should/ work, so figuring out why it's not would be good, because then you could do it with a single filter on 007/00 with a length of 2
15:26 paxed eeevil: com_smd should show in metabib.record_attr attrs, right?

Results for 2013-06-04

10:59 _zerick_ joined #evergreen
11:00 tspindler joined #evergreen
11:04 Dyrcona dbs: mens health doesn't match men's health on my catalog, either.
11:04 bshum Well, I just tested that search on MVLC and SCLEND's catalogs and neither returned expected results
11:05 bshum Oh, heh
11:05 dbs Looks like your thinking that new QP might be playing a role might be a reasonable theory. I'm seeing the same difference on our 2.4 test server vs our 2.3 production server
11:06 dbs Is SCLENDs on 2.4?
11:06 dbs I assume MVLC is.
11:06 gmcharlt dbs: yes
11:08 * bshum goes off to file a bug
11:08 paxed is it enough to insert into config.record_attr_definition and reingest, or do i have to do something else to get a new filter working?
11:33 paxed huh. okay, that works. it just didn't work like i expected it to.
11:34 paxed adding that filter, it seems to consider the whole 007 field, not the 007/1
11:46 Ruth joined #evergreen
11:57 jeff_ drat. the perils of comparing json as strings?
11:57 jeff_ #   Failed test at t/09-Utils-JSON.t line 105.
11:57 jeff_ #          got: '{"__p":{"foo":"bar"},"__c":"osrfException"}'
11:57 jeff_ #     expected: '{"__c":"osrfException","__p":{"foo":"bar"}}'
11:57 jeff_ (of course, run the test again and all's well)
11:59 Ruth I had the same problem with roofing nails this morning.
12:02 mcooper joined #evergreen
12:05 pinesol_green [evergreen|Simon Hieu Mai] LP#1053074: Editimg MARC Fixed Fields jumps cursor to marc record - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=717a126>
12:25 ldwhalen joined #evergreen
12:35 paxed yeah, figured
12:39 mjingle joined #evergreen
12:55 jeff_ tests+-
13:09 mcarlson joined #evergreen
13:11 mtcarlson joined #evergreen
13:13 dbs jeff_: maybe set $json->canonical(true) to ensure the keys are ordered
13:14 dbs assuming that json::xs is in play
13:15 * dbs hasn't been able to get that test to fail
13:15 jeff_ yeah. it might be a perl 5.18 thing. i'm seeing similar with some XML tests for RPC::XML
13:16 jeff_ or, might be that i've fallen back to the pure perl json backend. i should check.
13:16 dbs mmm, yeah, perl 5.16 here
13:16 jeff_ and dbs++ for $json->canonical(true) -- i thought there was an option for that but had not gone looking.
13:17 StephenGWills joined #evergreen
17:05 mjingle joined #evergreen
20:20 serflog joined #evergreen
20:20 Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged. | Large pastes at http://paste.evergreen-ils.org
20:21 bshum awitter++ mrpeters++
20:36 b_bonner joined #evergreen
20:43 mtcarlson joined #evergreen
20:46 mcarlson joined #evergreen
22:03 ktomita-mac joined #evergreen
22:16 ldwhalen joined #evergreen
22:17 kmlussier joined #evergreen
22:20 * bshum sighs loudly at acquisitions and EDI testing :(
23:00 pinesol_green [evergreen|Pranjal Prabhash] Standalone Mode Staff Client Shortcuts - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=b55da92>
23:00 pinesol_green [evergreen|Ben Shum] Added release note for standalone mode shortcuts - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=2060027>
23:04 bshum Calling 0794

Results for 2013-06-03

11:51 dboyle joined #evergreen
11:53 tsbere b_bonner: Dunno if it has anything to do with your error.....but why the subselect? The where and limit clauses should, in theory, work on the update statement directly
11:53 jdouma joined #evergreen
11:56 b_bonner tsbere: subselect was just wanting to limit the query to the bib id's that actually have this 856 condition and the limit was just a remnant of me doing smaller scale tests.
11:57 jeff_ b_bonner: sounds like your error is related to an existing issue with one or more bibs. doing a straight-up reingest of the bib without changing a thing in the marc record would likely trigger the same error.
11:57 tsbere b_bonner: The where clause checking position would work on the update statement itself to do the same limit, though
11:58 jeff_ b_bonner: you could add RAISE DEBUG statements (or their perl equiv) to the relevant functions in the db to surface the ID of the record(s) causing the issue.
12:16 paxed yeah, just noticed that
12:16 phasefx gathered at login time
12:18 b_bonner jeff_ tsbere: sorry for delay getting back to this. I'll attempt to figure out which ID's are throwing the errors.  Does this mean that these ids probably aren't indexed properly now?
12:19 jeff_ eeevil: thanks. in that case, it would be good to test the effective client_min_messages for DBI, and ensure that whatever chosen could be logged without tripping up dbd::pg.
12:19 eeevil b_bonner: it might mean that your update isn't doing what you expect. or it might mean that you've changed settings on some index defs
12:20 eeevil jeff_: of course, it might be fine today. I ran into that long ago
12:20 jeff_ eeevil: good to know that it might be an issue, even if it turns out not to be.
12:32 jeff_ b_bonner: but you can use full_rec to find the records to change.
12:32 * jeff_ nods
12:32 b_bonner jeff_ eeevil: oh, sure. position wasn't that bad actually.
12:34 bshum Testing logger:  i’m
12:40 jeff_ @later tell berick i'm interested in your thoughts on bug 1187035 removing OpenILS::Utils::Editor -- you're the usual author on Editor/CStoreEditor
12:40 pinesol_green jeff_: The operation succeeded.
12:40 jeff_ bug 1187035

Result pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148