| 06:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:05 |
|
kmlussier joined #evergreen |
| 07:05 |
kmlussier |
bshum++ |
| 07:05 |
kmlussier |
parts++ |
| 09:13 |
mmorgan |
Good morning! |
| 09:13 |
|
Stompro joined #evergreen |
| 09:22 |
|
rjackson_isl_hom joined #evergreen |
| 09:40 |
eby |
miker: / berick : going to test more next week but curious with your mention of setting workstation prefs as org unit settings. Does it act as a fall back default or as a forced preference? |
| 09:49 |
phasefx |
berick: do you want to talk SIP2M sometime today? I don't have an agenda, but we could determine/sanity-check next steps |
| 09:51 |
berick |
eby: it acts as fall back default. ignored in cases where a workstation setting value is already saved. |
| 09:52 |
berick |
best way to create is to save the value you want at a workstation, then copy the JSON from the value into the newly created org unit setting. |
| 09:59 |
pinesol |
Dyrcona: go with local git |
| 10:07 |
* Dyrcona |
wonders if we should add some instrumentation to pingest.pl (and possibly drop the .pl extension). |
| 10:16 |
Dyrcona |
Hmm. I guess rebasing from master to rel_3_7 is not a good idea. |
| 10:18 |
miker |
Dyrcona: do I feel my ears burning? ;) (if you're looking at what I think you're looking at, if you can test closer to master I think you'll have more success) |
| 10:18 |
Dyrcona |
Remote syntax in git can be annoying: orign/rel_3_7 for one command and origin[space]rel_3_7 for another. |
| 10:19 |
Dyrcona |
miker: I am. I plan to start testing with rel_3_7 today and an upgrade to rel_3_9 next week if that's OK. |
| 10:20 |
|
mdriscoll joined #evergreen |
| 10:20 |
Dyrcona |
I suppose the different syntax is what they call commitish (in the / case) and remote[space]branch in the latter. |
| 10:22 |
Dyrcona |
I should copy the database that I want to use so it won't get obliterated this weekend. |
| 10:23 |
* Dyrcona |
is tempted to test on Pg 14 since there was an update this morning... ;) |
| 10:43 |
miker |
Dyrcona: as far as order and timing goes, I'm just glad someone's looking at it, but just to note that deadlock+symspell branch was developed after 3.7 (recall, nocase browse) so starting with vanilla 3.8 or 3.9 (/not/ patched with this and then upgraded) may be less of a headache. I get that "with your data" testing isn't particularly feasible at scale for versions past what you're actually on, though. |
| 10:46 |
Dyrcona |
miker: Right. I previously made a 3.7 backport and only had had to change the db upgrade script. Looks the same still, but I'll see what happens. If it just blows up, I'll move to upgrading to 3.9 over the weekend. |
| 10:47 |
Dyrcona |
I'm going to compare the implementation of metabib.reingest_metabib_field_entries in the two db upgrades. I think we can delete the one from the WWW upgrade. |
| 10:51 |
Dyrcona |
Yeah, only difference is the check for reification. |
| 13:16 |
JBoyer |
I'm also basically out of pocket / on the bench / choose your own favorite game / sport related euphemism for unavailable for any real hacking at the fest. Additionally, if anyone wanted to take the reins / read the agenda for the dev meeting this afternoon I would be happy to just listen in and pop in should I have something worth saying. |
| 13:19 |
miker |
Dyrcona: huzzah! with that option it /should/ be as fast as before (insert-only into the unlogged table) and then at the end there'll be a pause while it shoves the changes in, in one go |
| 13:22 |
Dyrcona |
miker: We'll see. |
| 13:22 |
Dyrcona |
I also just tested a 3.7.3 to 3.9 db upgrade that I prepared for next week, and I got this error: psql:3.7.3-3.9-upgrade-db.sql:3509: ERROR: cannot drop type search.search_result because other objects depend on it |
| 13:22 |
Dyrcona |
DETAIL: function search.query_parser_fts(integer,integer,text,integer[],integer[],integer,integer,integer,boolean,boolean,integer) depends on type search.search_result |
| 13:22 |
Dyrcona |
I wonder if we have something old or custom hanging around? |
| 13:23 |
Dyrcona |
The suggestion in the error report was to use drop cascade. |
| 13:24 |
Dyrcona |
Looks like we won't be needing it. |
| 13:27 |
jeffdavis |
We have two versions of search.query_parser_fts in our environment and I've had to manually drop the second one for the upgrade scripts to work in testing. |
| 13:27 |
jeffdavis |
So yeah, probably an old version of that function sticking around on ancient EG installs. |
| 13:30 |
Dyrcona |
jeffdavis: Thanks. That's what this looks like. |
| 13:30 |
Dyrcona |
I'm using cascade on the type drop, and that appears to work. |
| 13:32 |
Dyrcona |
It's fun running upgrades over multiple version. :) |
| 02:33 |
|
akilsdonk joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-10_04:00:02/test.49.html> |
| 07:26 |
|
rfrasur joined #evergreen |
| 07:32 |
|
rjackson_isl_hom joined #evergreen |
| 07:38 |
|
collum joined #evergreen |
| 09:02 |
csharp_ |
screw it, I'll rewrite it in perl |
| 09:04 |
csharp_ |
do we use warnings and use strict, Barry? Yes, other Barry, we do. |
| 09:07 |
JBoyer |
-Wall -Werror |
| 09:08 |
JBoyer |
jeffdavis++ for looking into the http tests. |
| 09:09 |
JBoyer |
Not sure the nginx issue is an issue for most testing though, I don't know what benefit there would be to standing that proxy up just for the tests. |
| 09:19 |
|
mantis1 joined #evergreen |
| 09:29 |
* Dyrcona |
missed something. To the logs! |
| 09:31 |
Dyrcona |
JBoyer: Is it a nginx issue or is it the directories missing again? |
| 09:32 |
Dyrcona |
csharp_: You can also install Modern::Perl and 'use Modern::Perl;" to get use strict; use warnings; and some other useful things. |
| 09:32 |
Dyrcona |
The deb is libmodern-perl-perl |
| 09:33 |
|
mantis2 joined #evergreen |
| 09:33 |
Dyrcona |
JBoyer: IIRC, none of the other live tests require even Apache to be running, just OSRF services. |
| 09:34 |
* Dyrcona |
likes it when a program that I haven't used/touched in 3 years or so still works. |
| 09:36 |
JBoyer |
Dyrcona, I was referring to what jeffdavis said yesterday about one of the tests giving a false positive if nginx is running on the test machine. You might have to hit the logs if you're not running a bouncer. |
| 09:36 |
JBoyer |
And there are a couple http tests, but not many, no. |
| 09:52 |
Dyrcona |
JBoyer: OK. I was out yesterday. Also, I notice that image uploader test failed this morning. |
| 10:15 |
csharp_ |
Dyrcona: thanks - I'll check it out |
| 10:16 |
* csharp_ |
tries to rid his brain of Bowie's Modern Love |
| 10:17 |
berick |
hey csharp_, roam if you want to |
| 14:22 |
|
rfrasur joined #evergreen |
| 17:08 |
|
mmorgan left #evergreen |
| 17:31 |
|
jvwoolf left #evergreen |
| 18:00 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-10_16:00:03/test.49.html> |
| 18:56 |
pinesol |
News from commits: LP1950345-Format the Current Hold Groups table in bootstrap opac <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=1b466467109a9013dd3799d69be6e80c968ce433> |
| 19:56 |
pinesol |
News from commits: Hold Management page update <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2678ee1dfcc448968ba8e8ae7fd0da1bc69eeecf> |
| 06:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-09_04:00:02/test.49.html> |
| 07:28 |
|
collum joined #evergreen |
| 07:33 |
|
rjackson_isl_hom joined #evergreen |
| 07:48 |
|
rjackson_isl_hom joined #evergreen |
| 09:25 |
|
mantis1 joined #evergreen |
| 09:30 |
|
jvwoolf left #evergreen |
| 09:31 |
|
jvwoolf joined #evergreen |
| 09:58 |
mantis1 |
I upgraded one of our test servers from 3.6.5 to 3.9. Has anyone had weird spacing problems in the Boopac after an upgrade? I have no idea why it's spacing out so much like it is. There is a width=device-width element added in base.tt2, but it doesn't seem to make a difference if it's deleted or not. |
| 10:37 |
|
mantis2 joined #evergreen |
| 10:38 |
csharp_ |
mantis1: is it stock EG or did you apply customizations on top of the upgrade? |
| 10:39 |
csharp_ |
(or conversely, applied stock EG stuff on top of your customized stuff?) |
| 17:02 |
csharp_ |
I'm on at&t, which while not awesome either, at least it's not comcast :-) |
| 17:21 |
mmorgan |
not_comcast++ |
| 17:28 |
|
mmorgan left #evergreen |
| 18:01 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-09_16:00:02/test.49.html> |
| 20:14 |
jeffdavis |
the 34-lp1787968-cover-uploader.t live test is failing with a 404 on http://127.0.0.1/jacket-upload |
| 20:16 |
jeffdavis |
29-lp1817645-remoteauth-patron-api.t also does HTTP requests, but that test is actually being skipped right now because the test environment's version of LWP::Protocol::https is not >=6.0.7 |
| 20:19 |
jeffdavis |
and 24-offline-all-assets.t (which does a wget on https://localhost/eg/staff/offline-interface) technically isn't failing but I'm not sure the test is robust - in an environment with an nginx proxy, the test will pass if apache isn't running because the response is a 502 error and the test only checks for 404 |
| 20:20 |
jeffdavis |
I'm also not really sure that the wget output is being parsed properly |
| 20:22 |
jeffdavis |
in other words, none of the 3 live tests that do direct HTTP requests against the test server are really "working" |
| 20:23 |
jeffdavis |
something to fix at the hackfest maybe? |
| 02:50 |
|
berick joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-08_04:00:02/test.49.html> |
| 07:25 |
|
rjackson_isl_hom joined #evergreen |
| 07:49 |
|
collum joined #evergreen |
| 08:05 |
|
RFrasur joined #evergreen |
| 15:19 |
Dyrcona |
People do get uptight about the queue order, but it's just a guess at best. |
| 15:19 |
mmorgan |
We're not using a soft regarget interval. Maybe that would help. |
| 15:21 |
Dyrcona |
We've experimented with every half hour, every 15 minutes, etc. Then, it started running into itself and it ended up being 1/hour effectively. We skip the hours between midnight and 6:00 am to avoid the overnight jobs that run during those hours. |
| 15:22 |
Dyrcona |
The soft retarget interval might help. John Amundson could probably tell you better why we use it because it was his testing that made us decide on that value. I forget exactly why we ended up with that value. |
| 15:23 |
* mmorgan |
would thing you could end up with a LOT more holds being retargeted using a soft interval. |
| 15:25 |
Dyrcona |
Our "normal" retarget interval is 48 hours to keep things on pull lists a little bit longer. |
| 15:25 |
Dyrcona |
We'd typically see the running into itself happen for a day or so after an upgrade, then it just kept up (probably because of the soft interval), so we changed the schedule. |
| 17:09 |
|
mmorgan left #evergreen |
| 17:14 |
jeffdavis |
hm, that doesn't work for me unfortunately |
| 17:17 |
jeffdavis |
we're using skins, I wonder if that is causing trouble |
| 18:00 |
pinesol |
News from qatests: Failed Running perl live tests <http://testing.evergreen-ils.org/~live//archive/2022-06/2022-06-08_16:00:03/test.49.html> |
| 22:45 |
jeff |
jeffdavis: do you see the text-white class in the output html and it isn't working, or does that class not make it to the html seen by the browser? |
