Evergreen ILS Website

IRC log for #evergreen, 2020-10-07

| 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
06:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:15 rjackson_isl_hom joined #evergreen
07:59 mantis1 joined #evergreen
08:22 collum joined #evergreen
08:23 rfrasur joined #evergreen
08:31 rfrasur just as a continuation gmcharlt++ Bmagic++ dluch++ abneiman++ DIG++ # I'm extraordinarily happy with the docs being accessible.  And yo, Antora *chef's kiss*
08:32 rfrasur (though it's broke right now - don't even care cuz I already saw it previously)
08:32 Dyrcona joined #evergreen
08:47 mmorgan joined #evergreen
09:04 abneiman @rfrasur thanks for the heads up about the breakage
09:04 pinesol abneiman: well, that's what you get for not being a shell script
09:04 * abneiman sighs
09:04 abneiman slack has ruined me
09:05 abneiman rfrasur: thanks fo rthe heads up about the breakage
09:05 rfrasur Oh, I just figured that there was some work going on with it.
09:05 abneiman NOW WITH TYPOS
09:05 * abneiman goes to refill the coffee
09:05 rfrasur abneiman++ # it's Monday.  Let's all get through this together.
09:05 * rfrasur checks.
09:05 rfrasur Yes.  Monday.
09:05 abneiman actual LOL
09:06 abneiman the Mondayest Wednesday
09:06 rfrasur Oh yeah.
09:06 * rfrasur grins large, flips off the universe, and carries on.
09:09 miker joined #evergreen
09:11 Dyrcona :)
09:12 Bmagic rfrasur: it was broke yesterday morning too. Something is up with the nightly build process.. Fixing
09:12 rfrasur Hey!  miker gets voice from tolkien.freenode.net. I ain't complaining about ChanServ but tolkien.freenode.net is cool.
09:13 rfrasur Bmagic, cool.  I wasn't passive aggressive complaining.  I sincerely think y'all are awesome.  And then noticed it was broken and figured it was (as it is) just a temp thing.
09:13 Dyrcona rfrasur: The freenode servers are all named for authors.
09:13 rfrasur Dyrcona, but not all of us get voice granted by them.
09:14 rfrasur At least not so explicitly.
09:14 Dyrcona My screen says it was granted by tepper. I think that means you're connected to tolkien, and I'm connected to tepper. :)
09:16 rfrasur Oh, that tracks.  I am connected to tolkien.  Good call.  Not sure why this matters to me this morning.  I suspect it has something to do with the first rushes of caffeine.
09:16 Bmagic rfrasur: I didn't take it that way but now that you suggested it, I do! :) just jokes
09:16 Bmagic @coffee rfrasur
09:16 * pinesol brews and pours a cup of Panama Elida Natural, and sends it sliding down the bar to rfrasur
09:17 Bmagic we have lift off: https://eg-docs.georgialibraries.org/eg/
09:17 Dyrcona rfrasur: S'allright. It's Monday. :)
09:17 rfrasur Bmagic: Hah!  It's cool.  Language is layered and flexible.  We give it in one way and it is generally received in another with all the subtleties and nuance we did or did not intend.
09:17 rfrasur Bmagic++
09:18 rfrasur Antora lives!!!!! I wish I could hug it.  I also think I should drink some water to go with that coffee.  And use smaller portions next time.  Dang.
09:18 Bmagic This is one of my favorite docs: https://eg-docs.georgialibraries.org/eg/​docs/latest/cataloging/introduction.html
09:18 alynn26 joined #evergreen
09:18 * rfrasur laughs.  Well...that is a page.
09:18 rfrasur With a header.
09:18 Bmagic Cataloging needs no introduction
09:19 rfrasur Very concise...and uh...easy on the server in terms of character storage.
09:19 Bmagic And now folks, INTRODUCING........<cough>
09:19 * rfrasur chuckles.
09:20 rfrasur "We came, we saw, we described and organized using controlled vocabulary and shared schema."
09:20 Bmagic nobody noticed the right-hand side topic nav yet. It wasn't there during the conference. I put that in later in the summer
09:20 mmorgan rfrasur++
09:21 rfrasur lol, Bmagic, it was noticed.  I didn't know it wasn't there before.
09:21 Bmagic I for one, love it
09:21 rfrasur In fact, I used it yesterday.
09:21 rfrasur I do, too.  Lots
09:21 Bmagic It sorta removes the need for the :toc: at the top
09:22 rfrasur Yeah, but the TOC is a nice legacy feature for people who expect such a thing.
09:22 rfrasur Oh, I did have a question though.
09:22 Bmagic not sure on the accessibility of the topic nav
09:22 rfrasur https://eg-docs.georgialibrari​es.org/eg/docs/3.6/index.html
09:23 Bmagic having the toc is good
09:23 rfrasur There is a "topic manual" for acquisitions that is unlinked.
09:23 Bmagic oh yeah, topic manuals
09:23 Bmagic that work is unfinished
09:23 rfrasur Is it more extensive than what's in the Acq "chapter?"
09:24 Bmagic you can see it in the repo docs/topics/
09:24 rfrasur has a decision been made to not link it until it's done?
09:26 rfrasur Oh, super unfinished. Makes sense now that I look at it.
09:27 Bmagic https://docs.antora.org/antor​a/2.3/organize-content-files/
09:28 rfrasur ++
09:28 Bmagic https://docs.antora.org/anto​ra/2.3/standard-directories/
09:29 * csharp was about to say "wow, I feel a connection to Tolkein too!" then read up to see that those are freenode server names
09:30 csharp also, literally connected to tolkein
09:30 Bmagic lol
09:30 csharp er... tolkien
09:32 rfrasur Bmagic, that's very helpful (now that I have significantly more context).  Thank you.
09:32 Bmagic i before e except after c. Or unless the word has french roots... Or unless it's just that one word. Or unless..... ummmm, let's stop using English
09:32 rfrasur English has let us all down in many ways.  (what a lovely, loaded statement)
09:33 rfrasur (why yes, I did just proclaim my own statement "lovely."  Good grief.)
09:33 Bmagic One of my best friends is a red coat.
09:33 * mmorgan searches catalog for 'tolkein' and gets 5 hits :-/
09:34 rfrasur Hmm, I know some fine "English" people.  I think I was actually spawned from some (not necessarily of the "fine" variety). Also, I have a red coat.
09:35 rfrasur And yet, the language...is it even?  I dunno.  An interesting rabbit hole to go down at another point.
09:35 rfrasur (point on "the" timeline, that is)
09:40 Dyrcona Who says time is a line? I understand it is actually crystals.
09:45 Bmagic I'm in a crystal, living in an alternate state which forked off Nov. 2016
09:46 Bmagic We've done such a great job combating Global warming, it's now a Global cooling crisis... Ah! what can y ou do
09:47 Dyrcona :)
09:48 rfrasur Time is not a line.
09:48 rfrasur But it's a nice construct that allows us to say "later."
09:49 Dyrcona I'm starting to think the universe is a side effect of Emacs. :)
09:49 rfrasur Bmagic, I fully support your experience in your forked reality.  May it endure with stability and longevity.
09:49 rfrasur Dyrcona++
09:50 Bmagic lol! the universe is here because* of Emacs. Sort of like the chicken and the egg. Hilarious! Dyrcona++
09:50 jvwoolf joined #evergreen
09:53 Bmagic rfrasur: back on the topcs manual. I'm not entirely sure what remingtron was trying to construct there. I'm not seeing documentation about the notion of a "topics" folder. This doc helps a lot: https://docs.antora.org/antora/2.3/page/page-id/
09:56 Bmagic it looks like Antora 2.3 dropped "topic", you can see it referenced in 2.2 https://docs.antora.org/antora/2.2/page/page-id/
09:59 rfrasur Bmagic, I get it VERY conceptually, but not practically.  That's not because it's not clearly written or sensical.  It's because I don't have the necessary competency for it at this point.  Perhaps in a few months or a year or "later."  At a point, I'll pick at it more.  Right now, I'm more of a library administrator than even someone that could be considered legitimate IT support.
10:00 Bmagic I wonder if remingtron's commit message could help
10:02 Bmagic this is what he wrote: This is a first draft at structuring a topic manual in Antora (mostly reusing files from the main "docs" component).
10:02 rfrasur Okay, so it's mostly an artifact of a possibility?
10:03 Bmagic I think the deal was: we had* "topic manuals" before, and he was trying to re-create the same thing in Antora
10:04 Bmagic Though, the folder "topics" is ignored by Antora
10:04 Bmagic I think at the next DIG meeting, we need to discuss what we want/need
10:04 rfrasur Bmagic++
10:05 rfrasur My thought exactly.  Though as someone that contributes next to nothing to DIG, I don't think my opinion matters much.  I appreciate you having a similar idea as someone who DOES contribute.
10:08 alynn26 all thoughts matter with DIG, even if you only contribute ideas.
10:08 alynn26 rfrasur, ^^
10:08 rfrasur fair point.
10:29 Bmagic thoughts++
10:29 Bmagic computers++ humans++ humans++ # gotta keep those computers from taking over karma
10:32 * rfrasur chuckles some more.
10:33 rfrasur We are but organic computers.
10:36 Dyrcona 42
10:37 rfrasur 2.3.7
10:43 Bmagic so true
10:44 Bmagic in other words: ! == 1
10:45 Bmagic $_ == 1;
10:49 rfrasur lol, nice.
10:50 rfrasur Kinda feel like we might be entering into a Borg religion or something.
10:50 * rfrasur looks around uncertainly.
10:51 Bmagic that's just what a human would* say
10:51 Bmagic @decide rfrasur is a spy or rfrasur is a not a spy
10:51 pinesol Bmagic: go with rfrasur is a not a spy
10:52 rfrasur @decide Bmagic is a spy or Bmagic is not a spy
10:52 pinesol rfrasur: go with Bmagic is a spy
10:52 Bmagic you lucked out this time. Next time you may not be so lucky!
10:52 rfrasur pinesol, duh
10:52 alynn26 Only bmagic is always a spy.
10:52 pinesol rfrasur: Fire BAD! Reading GOOD!
10:53 Bmagic haha, that's what "they" want you to think
10:53 Bmagic a double, double, and double back mind game that Dyrcona started
10:53 Bmagic propagated like DNS
10:53 rfrasur We are all pawns, either knowingly or unknowingly.  It is only in recognizing our conscious or unconscious duplicity that we can POTENTIALLY stand in opposition to it.
10:54 * berick backs away slowly
10:54 Bmagic see, you're already assimilating
10:54 Bmagic excellent
10:54 berick kidding, I'm listening, may I subscribe to your newsletter
10:54 * rfrasur is fully assimilated.
10:54 rfrasur But the coffee here is adequate.
10:55 Bmagic berick++
10:55 jeff @who is sus
10:55 pinesol pinesol is sus.
10:55 Bmagic we are all open on port 53
10:55 * mmorgan wonders what's IN the coffee this morning ;-)
10:55 rfrasur It's cool, berick.  You serve the collective well in your role(s).  Thank you.
10:56 rfrasur mmorgan, pumpkin spice
10:56 mmorgan That would explain it :)
10:56 rfrasur for real.
10:57 rfrasur Also, berick, those filters -> in the vein of "chef's kiss." Nice.
10:58 Bmagic berick: keep port 53 open to the Evergreen community
10:59 berick rfrasur: oh good!
11:00 berick pretty sure my firewall is just a slice of swiss cheese
11:00 rfrasur cheese++ swiss_cheese++ all_cheese++
11:01 rfrasur firewall++ # with some mild reservation as opposed to mild cheddar with is only + instead of ++
11:01 rfrasur s/with/which
11:01 Bmagic lol
11:02 * mmorgan puts berick's firewall between 2 slices of bread with some tuna and tosses it in a cast iron pan
11:02 Bmagic berick: would you say it's more of a waterwall?
11:02 rfrasur mmorgan++
11:02 * Bmagic is reminded of Magic the Gathering all of a sudden. Oh why can't it be 1993 again
11:03 Dyrcona @decide ementhaler or raclette
11:03 pinesol Dyrcona: go with ementhaler
11:03 * rfrasur ponders 1993.
11:03 rfrasur Bmagic, do you mean as it happened as a potential fork point?
11:03 Dyrcona Bmagic: 1975 was a better year. :)
11:03 rfrasur lol, Dyrcona.  Bmagic wasn't born then.
11:06 berick Bmagic: fittingly, the opening lines of wonderwall are told from the perspective of a firewall ;).  "Today is gonna be the day That they're gonna throw it back to you"
11:06 Bmagic you're right. 1983 was when I began
11:07 Dyrcona rfrasur: It was an old joke: http://irc.evergreen-ils.org/​evergreen/2017-03-02#i_293050
11:07 rfrasur berick++ 1983++
11:07 Dyrcona I didn't think it was that old, though....
11:07 Bmagic or, when I was programmed I mean
11:07 Dyrcona Personally, 1983 was OK. It was the year we moved to Kentucky.
11:07 rfrasur Dyrcona++ # old like 1975.
11:08 rfrasur Bmagic, you were at least partially programmed significantly before 1983 (the wonders of DNA are wondrous).
11:09 Bmagic Dyrcona: lol, awesome memory. I can't believe we've been here before
11:09 rfrasur crystalline time.
11:09 Bmagic berick++ # looping back to your firewall joke
11:10 Bmagic even crystal history repeats itself
11:10 rfrasur Oh, it must.
11:12 rfrasur mmorgan, I added pumpkin spice to yogurt/granola, too.  It's crazy up in here.
11:12 JBoyer jeff++
11:12 * JBoyer was getting some serious Among Us vibes
11:13 rfrasur JBoyer, you never REALLY know who you're talking to in IRC.
11:13 Bmagic we're friends on Evergreen
11:14 rfrasur Now that I've used the phrase "duct tape and bailing wire" in a training, I think it's time to have it on a t-shirt.
11:16 Bmagic rfrasur++ # speaking of 1975
11:17 Bmagic There are some "benefits" of being raised by a dad who was born in 1944: I've heard that before, lol
11:17 rfrasur Hmm, def some added historical elements to his "toolbag o' experience."
11:18 rfrasur OMG, I forgot I related open source ILS to IKEA furniture.
11:19 rfrasur If there's a pasture, I think I might should be put out to it.
11:19 Bmagic haha, I can DIG it
11:20 rfrasur Bmagic++ # Hah!
11:20 * Bmagic drops the mic
11:20 * rfrasur passes the hat for tips.  That was legit.
11:20 mmorgan rfrasur: Hurry up before someone builds a high rise on it!
11:21 Dyrcona JBoyer: You mind a correction on your email to the dev list? EOL for Pg 9.6 is 2021-11-11, so is 9.5.
11:21 berick Dyrcona: phew, that startled me
11:21 rfrasur mmorgan, I want to hurry up....but my knees, and my brain...ugh.
11:22 Dyrcona I've bookmarked this https://www.postgresql.org/support/versioning/
11:23 Bmagic ROTFLSHTIHMHOTWVHTTWGCATHS​SAMMRIMRTIWDBIWSL-Rolling On The Floor Laughing So Hard That I Hit My Head On The wall Very Hard That The Wall Got Cracks And The House Started Shaking And My Mom Ran Into My Room Thinking I was Dead But I Was Still Laughing
11:23 Dyrcona Um.....
11:23 * rfrasur laughs.  Oh man.  I mean, dead laughing has to be good, right?
11:24 Dyrcona Well, guess I was wrong about 9.5, but details....
11:24 Dyrcona I once thought my brother was making a commotion, but it turned out to be an earthquake.
11:24 rfrasur LOL!!
11:25 rfrasur I mean...he could be telekinetic.
11:25 Bmagic JBoyer: phew, I was starting to get worried about the Nov 2020 date on 9.6. We are still upgrading some our servers to 9.6. LOL
11:25 * rfrasur is listening to The Institute by Stephen King. Telekinesis figures fairly prominently.
11:25 Dyrcona Hm... so, maybe I should add Pg 13 to my development db server.....
11:26 Bmagic <jack_black>MF Mindbullets!</jack_black>
11:26 rfrasur I <3 jack_black.  That's all.
11:26 Bmagic also the name of my WoW character
11:26 rfrasur MF Mindbullets?
11:26 Bmagic Mindbullet
11:27 rfrasur 1983++
11:27 Bmagic lol
11:33 pinesol [evergreen|Chris Burton] LP1895398 Bootstrap OPAC Follow Up #1 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=443359b>
11:33 pinesol [evergreen|Chris Burton] LP1895398 Bootstrap OPAC Follow Up #2 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=81957a7>
11:33 pinesol [evergreen|Galen Charlton] LP#1895398: (follow-up) show outline when the login link has focus - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=95cb9a9>
11:41 pinesol [evergreen|Galen Charlton] stamp release notes for 3.6-beta2 - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=f47a9ee>
11:41 pinesol [evergreen|Galen Charlton] move 3.6-beta2 update to 3.6-rc - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=3fed458>
11:41 pinesol [evergreen|Galen Charlton] Translation updates - newpot - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=fbb21df>
11:45 pinesol [evergreen|Galen Charlton] update Czech translation for Angular staff client - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=e07ca51>
12:05 jihpringle joined #evergreen
12:22 JBoyer Dyrcona++
12:23 JBoyer I looked *directly at* the correct date and yet that's what I sent immediately before going to lunch...
12:29 khuckins joined #evergreen
12:44 Dyrcona Kind of like looking directly at the sun. JBoyer++
12:44 Christineb joined #evergreen
12:50 Dyrcona Unusual: Sixty-three updates to install, but not a kernel update among them.
12:52 sandbergja joined #evergreen
13:30 * Dyrcona restores a dump from Sunday to a Pg 13 database instance.
14:34 jihpringle joined #evergreen
14:37 jtm-lis left #evergreen
14:48 csharp gmcharlt: JBoyer: mmorgan: am I able to push bugfixes to rel_3_6, or should I wait?  (Specifically looking at bug 1893463
14:48 csharp )
14:48 pinesol Launchpad bug 1893463 in Evergreen "Interrupting and re-running recurring reports can cause duplicated schedule entries" [Undecided,New] https://launchpad.net/bugs/1893463
14:49 JBoyer I'm mid-build on the rc, so I won't be pulling anything, should be fine.
14:49 csharp ok awesome
14:49 JBoyer (finally done with translation, may be finished soon...)
14:50 JBoyer ALSO, csharp++ for testing that one.
14:52 csharp calling 1241
14:58 pinesol [evergreen|Jason Boyer] LP1893463: Prevent duplicated report outputs - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7ae38e7>
14:58 pinesol [evergreen|Chris Sharp] LP1893463: stamp upgrade script - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=7c0d5ee>
14:58 csharp how do we indicate that an upgrade script should be done outside the normal BEGIN; COMMIT;?
14:59 csharp this one will almost certainly require de-duping report.schedule rows before applying the index
15:00 sandbergja joined #evergreen
15:06 JBoyer I think some of them use DO to check for the condition and if there's an issue it will RAISE NOTICE some instructions for the admin. I didn't think about that when putting the patch together.
15:08 Dyrcona There's no convention on that as far as I know. I usually put them outside the transaction in the upgrade script with a comment to note why it has to be separate.
15:09 csharp I guess another approach might be to de-dupe the data in a non-destructive way within the upgrade script?
15:10 Dyrcona I'm not sure messing data causes issues for transactions.
15:10 csharp ah - yeah, I remember that now
15:10 Dyrcona Are you concerned about how long it takes?
15:11 csharp no - for PINES (almost certainly the largest since we haven't tended to that table, the dedupe took seconds
15:11 Dyrcona It usually becomes an issue when multiple upgrades touch the same table. If an earlier upgrade updates or inserts to a table, and a later upgrade alters the table, then boom!
15:11 csharp yeah
15:12 csharp I'm squeamish about tinkering with data in upgrade scripts in general - just interested in avoiding pain
15:13 csharp maybe just RAISE a NOTICE with a suggested approach to dedupes and add release notes?
15:13 Dyrcona Do the duplicates prevent creation of the index?
15:13 csharp yes
15:13 Dyrcona They'll need to be fixed in the upgrade script in my opinion.
15:13 csharp ok
15:14 Dyrcona But, do get other opinions. I'm not always right. ;)
15:14 csharp I'll say that I've had to manually dedupe tables to accommodate upgrade scripts in the past, as I'm sure we all have
15:15 Dyrcona Yeah, a couple of times.
15:16 Dyrcona If we can avoid making the user do that, i.e. the upgrade can do it for them, then that's the direction I would go.
15:17 csharp yeah - looking into an approach now
15:17 Dyrcona csharp++
15:33 jihpringle joined #evergreen
15:40 csharp ok, I have a solution that I just tested - pushed it here: https://git.evergreen-ils.org/?p=working/Ev​ergreen.git;a=shortlog;h=refs/heads/user/cs​harp/lp1893463_upgrade_script_improvements - if someone wants to sign-off
15:40 csharp or I could just shove it in :-)
15:42 csharp JBoyer++ # buildin'
15:43 yar joined #evergreen
15:52 mantis1 left #evergreen
16:00 JBoyer csharp++ teaching me about DISTINCT ON () today. I'm +1 for that change.
16:19 Dyrcona Does the create index work inside the transaction?
16:19 csharp yes
16:19 Dyrcona The individual updates work for me, and we have duplicate entries.
16:19 csharp JBoyer: I learned it earlier today from a blog post about deduping in postgres
16:20 Dyrcona Let me try it again in a transaction, just to satisfy myself. :)
16:22 Dyrcona csharp: I get this with the update as-is: ERROR:  cannot CREATE INDEX "schedule" because it has pending trigger events
16:22 csharp argh
16:22 csharp I guess it has to happen outside the transation then?
16:23 Dyrcona Yeah, looks like.
16:24 Dyrcona It works for me that way.
16:24 csharp https://pastebin.com/21EF47jN - worked fine for me - not sure what factors are different between yours and mine
16:24 Dyrcona Well, I have about 10x as many rows.
16:26 jeff Dyrcona: do you have triggers on reporter.schedule?
16:27 Dyrcona Here's what my reporter.schedule looks like: https://pastebin.com/kAzPqwfa
16:27 Dyrcona Before applying the update.
16:28 csharp we have a couple more indexes - I think suggested by miker after a past upgrade to deal with something I don't remember
16:29 jeff does SET CONSTRAINTS ALL IMMEDIATE make it work inside the transaction for you, Dyrcona?
16:29 Dyrcona I'm also running this on Pg 12. Let me switch to 9.6.
16:29 Dyrcona jeff: It probably would. :)
16:30 jeff Other than actual triggers (which you don't seem to have), I think FK constraints (especially DEFERRABLE ones) can trigger that Can't CREATE INDEX "foo" because it has pending trigger events
16:31 Dyrcona It works on Pg 9.6, so it's related to the version. I'll try on Pg 10, also.
16:32 Dyrcona Yeahp.
16:32 csharp huh
16:32 * Dyrcona put Emacs SQL mode through its paces today.
16:33 jeff ah, I think this thread touches on what we're seeing: https://www.postgresql.org/message-id/5af9d5d6ce2​c3fa1d86aa755fe880044f0b1f098.camel%40cybertec.at
16:33 Dyrcona It blows up on Pg 10.
16:33 jeff (and confirms that SET CONSTRAINTS ALL IMMEDIATE should help)
16:35 jeff (and arguably it's a bug/regression introduced by a bugfix, but the thread appears to have died without anyone proposing a fix)
16:36 Dyrcona jeff: Yeah, that's it, and I can confirm that adding SET CONSTRAINTS ALL IMMEDIATE; in the transaction fixes it for me. (Also make it run a little slower, but that's to be expected.)
16:36 jeff Dyrcona: have you triged with SET CONSTRAINTS ALL IMMEDIATE inside the transaction, either just after the BEGIN or just before the CREATE for the index?
16:36 jeff Dyrcona: ah, good!
16:38 csharp where would you add SET CONSTRAINTS ALL IMMEDIATE? just before the COMMIT somewhere?
16:38 Dyrcona I added just after the BEGIN;
16:38 Dyrcona It'll probably have to go at the top of the combined upgrade script.
16:40 Dyrcona It has to go inside the transaction or it doesn't work, and you get a message to that effect.
16:40 csharp works for me on my test
16:40 jeff I think it can come late in the transaction-- it appearing before the CREATE for the index should be sufficient, but should be tested. I think the effect of setting it late in the transaction is that it "flushes" the pending checks before returning from the SET.
16:40 csharp I'll update the working branch with that
16:42 csharp ok, same git location, force-pushed the single commit with the fix
16:45 Dyrcona berick++ jeffdavis++ # For helping me understand something in a different venue.
16:46 Dyrcona jeff++ csharp++
16:47 Dyrcona csharp: I'm going to try it with the upgrade log update included this time. to see what happens. I have Pg 11 that I haven't tried, yet. :)
16:48 Dyrcona Pg 13 isn't ready yet. Still restoring.
16:48 csharp just to keep the bug up to date: https://bugs.launchpad.net/eve​rgreen/+bug/1893463/comments/4
16:48 pinesol Launchpad bug 1893463 in Evergreen "Interrupting and re-running recurring reports can cause duplicated schedule entries" [Undecided,New]
16:50 Dyrcona Yeah, that works for me. I'll add a sign off. jeff, do you want to look at it before it goes in?
16:54 Dyrcona https://bugs.launchpad.net/eve​rgreen/+bug/1893463/comments/5
16:54 pinesol Launchpad bug 1893463 in Evergreen "Interrupting and re-running recurring reports can cause duplicated schedule entries" [Undecided,New]
17:02 csharp Dyrcona++
17:03 Dyrcona My work here is done, for today.
17:20 jihpringle joined #evergreen
17:28 mmorgan left #evergreen
17:43 gmcharlt https://evergreen-ils.org/e​vergreen-3-6-rc-available/
17:48 csharp gmcharlt++
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
18:04 JBoyer joined #evergreen
20:42 Dyrcona joined #evergreen
20:42 Dyrcona @dunno add Your computer account is overdrawn. Please reauthorize.
20:42 pinesol Dyrcona: The operation succeeded.  Dunno #68 added.
22:20 sandbergja joined #evergreen
22:42 sandbergja joined #evergreen
23:41 mrisher joined #evergreen
23:43 sandbergja joined #evergreen

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