Evergreen ILS Website

IRC log for #evergreen, 2017-05-15

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

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

Time Nick Message
04:30 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
07:13 rjackson_isl joined #evergreen
08:40 mmorgan joined #evergreen
09:13 maryj joined #evergreen
09:31 kmlussier joined #evergreen
09:32 yboston joined #evergreen
09:36 rlefaive joined #evergreen
09:40 kmlussier Good morning #evergreen. Happy Feedback Fest Week!
09:46 mmorgan Good Morning!
09:50 Dyrcona joined #evergreen
09:56 rlefaive joined #evergreen
09:59 yboston joined #evergreen
10:05 mmorgan1 joined #evergreen
10:27 mmorgan joined #evergreen
10:44 Dyrcona Is there an easy way to check if the fine generator is actually doing anything?
10:44 Dyrcona It has been running on my training server since 9:27 am last Wednesday.
10:50 * mmorgan always looks for recent rows in money.billing
10:50 Dyrcona mmorgan: I'll try that, thanks.
10:50 Dyrcona Dunno why I didn't think of it.
10:50 mmorgan Monday...
10:55 yboston joined #evergreen
10:55 Dyrcona Yes, Monday.
10:56 Dyrcona It is still doing stuff, but slowly.
10:56 cesardv joined #evergreen
10:57 Dyrcona Parallel is set to 1.
10:57 Dyrcona Maybe I'll change that for next time.
11:07 Dyrcona Yeah, no doubt, it's Monday.... ;)
11:07 dbwells Dyrcona: on the bright side, just think of all the money you are making :)
11:07 Dyrcona Heh!
11:07 Dyrcona There is that. :)
11:15 sandbergja joined #evergreen
11:15 Christineb joined #evergreen
11:36 Dyrcona Yes, Monday: So why would stderr log claim that search is not connected to the network, when I see the listener and drones running and osrf_control --diagnostic says everything is OK?
11:38 miker Dyrcona: because the router couldn't send to it at some point (or, more likely, it took too long to respond to the router's connect request) and the router dropped it from the registration list
11:39 miker you can use osrf_ctl's rereg command to tell it to remind the router about itself. or just restart the service, of course
11:40 Dyrcona OK. I'll try restarting it.
11:41 Dyrcona Lovely. I think the load is too high on my training server.
11:42 Dyrcona timed out waiting on open-ils.search pid=12574 to die
11:43 Dyrcona Heh. Killed the fine generator and load went up.
11:47 Dyrcona cstore, search, and storage all hung up. Too much going on in the database, I guess.
12:13 jihpringle joined #evergreen
12:23 khuckins joined #evergreen
13:15 collum joined #evergreen
13:52 csharp joined #evergreen
14:13 berick grabbing 1038
14:23 pinesol_green [evergreen|Chris Sharp] LP#1170514 - Upgrade script for vandelay.auto_overlay_bib_record - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f9ee99c>
14:23 pinesol_green [evergreen|Bill Erickson] LP#1170514 Stamping vandelay bib-overlay resync SQL - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=020d548>
14:29 yboston joined #evergreen
14:43 abowling joined #evergreen
14:44 abowling i've got a hold where current_copy is null, presumably because it was removed from circulation. question: will i "break" anything if i manually set cancel_time in the db?
14:45 Dyrcona abowling: If you also set cancel reason, then I think you're OK.
14:47 abowling Dyrcona: thanks!
14:47 abowling Dyrcona++
14:48 Dyrcona I was just looking for some code to double check, but I can't find any.
14:52 Dyrcona abowling: I found some that sets cancel_time, cancel_cause, and cancel_note.
14:53 Dyrcona I confused cancel_reason from a po with cancel_cause.
15:11 berick I'm curious why bugs w/ pullrequests that previously targeted 2.next now target 3.next instead of 3.alpha.  shouldn't all pullrequest bugs target the next viable release by default?
15:12 bshum berick: I think that happened cause 2.next was renamed to 3.next
15:12 bshum Instead of naming it 3.alpha, and 3.alpha was made a new milestone
15:12 Dyrcona That, and 3.alpha didn't exist at the time.
15:13 bshum In the past, we used to do that, but stopped cause we ended up shuffling too many bugs from release to release due to lack of interest/time/review/code/whatnot
15:13 Dyrcona Could be the person assigned doesn't know if it will be done in time for the alpha. :)
15:13 berick Dyrcona: it has a pullrequest
15:13 bshum So the .next was intended to be the future, till it was worked on enough to move it into an actual present.
15:13 Dyrcona Oh, right. Sorry. :)
15:13 Dyrcona I guess the pullrequest bugs could be retargeted.
15:14 bshum But likely people didn't know that, and we should move any pullrequest stuff to the correct milestones
15:14 bshum When I reviewed things, I would move them from .next to .current to match.
15:14 berick i keep stumbling on my own pullreqs that I thought were in the mix, but then I see they're 3.next.  and now I'm not sure if it's cool to retarget them.
15:15 bshum I'd retarget without too much hesitation.
15:15 bshum Anything in .next is fair game to me if it's ready for real review, put a real target on it.
15:15 Dyrcona Yeah, I think it is OK.
15:15 Dyrcona gmcharlt would be the ultimate authority, though.
15:15 Dyrcona Being release manager.
15:15 * bshum defers to gmcharlt :)
15:17 rlefaive joined #evergreen
15:49 rlefaive joined #evergreen
16:04 gmcharlt bshum: Dyrcona: berick: yeah, if there is enough for a pullrequest, retargeting from 3.next to 3.0-alpha is fine
16:05 gmcharlt plans that are concrete enough where one is sure that there will be code in time for slush also justifies a specific target
16:06 berick great, thanks gmcharlt
16:06 gmcharlt what's not on, IMO, is a wishlist where there's no specific plans in place being targetted for 3.0-alpha
16:06 berick agreed, makes sense
16:07 Dyrcona gmcharlt: That's what I was thinking. Thanks!
16:14 khuckins joined #evergreen
16:27 Jillianne joined #evergreen
16:30 pinesol_green News from qatests: Test Success <http://testing.evergreen-ils.org/~live>
16:52 * gmcharlt grabs 1039 in the name of non-boring popcorn flavors everywhere!
17:00 pinesol_green [evergreen|Jeff Davis] LP#1552861: use correct datatype for vandelay.default_match_set org setting - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3434400>
17:00 pinesol_green [evergreen|Galen Charlton] LP#1552861: add upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=a4d2abb>
17:00 pinesol_green [evergreen|Galen Charlton] LP#1552861: stamp database update - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e6bd3d8>
17:04 pinesol_green [evergreen|Jason Boyer] LP1689576: Fix ALARM -> ALRM Typo - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3268144>
17:07 mmorgan left #evergreen
19:32 pinesol_green [evergreen|Chris Sharp] LP#1177794 - remove "Keep" field from Vandelay Import Item Attributes. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=263b839>
19:32 pinesol_green [evergreen|Chris Sharp] LP#117794 - Remove references to "Keep" field in Vandelay docs. - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7570423>
22:13 khuckins joined #evergreen
22:20 genpaku joined #evergreen
22:44 ohiojoe joined #evergreen
22:46 ohiojoe joined #evergreen
22:46 ohiojoe joined #evergreen

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