Evergreen ILS Website

IRC log for #evergreen, 2021-04-21

| 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:01 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>
07:12 rjackson_isl_hom joined #evergreen
08:35 Dyrcona joined #evergreen
08:38 mmorgan joined #evergreen
08:51 mmorgan1 joined #evergreen
09:01 mantis joined #evergreen
09:09 dbwells joined #evergreen
09:14 rfrasur joined #evergreen
09:15 jvwoolf joined #evergreen
09:17 csharp Dyrcona: sorry - very distracted right now with family stuff - we do separate bricks, no NFS except to serve reports, vandelay and offline
09:19 Dyrcona Well, if you read the rest of my monologue yesterday, it was a custom IDL entry that came out different on each brick, even though the IDL file is identical on the bricks.
09:21 Dyrcona csharp++
10:14 rjackson_isl_hom joined #evergreen
11:02 rjackson_isl_hom joined #evergreen
11:23 jihpringle joined #evergreen
11:55 nfBurton joined #evergreen
12:37 mantis We just updated to version 3.5.4.  If the screen sits idle for an hour, does the user get logged out as a privacy caution?
12:37 mantis We were on 3.1.16 before the update when this didn't occur.  Wanted to confirm the functionality.
12:41 Dyrcona mantis: Staff client or patron OPAC?
12:42 mantis staff client
12:43 csharp mantis: check for auth.staff_timeout entries in actor.org_unit_setting
12:43 mantis oh thank you!
12:43 csharp a well-meaning local admin may have set it and not realized the effect
12:44 Dyrcona Yeah.
12:45 Dyrcona There's another setting that I was checking in the code, but it's only used by XUL.
12:45 Dyrcona Also, looks like a memory leak in open-ils.cstore because I have another cstore drone, doing nothing, that has grabbed about 5GB of RAM.
12:47 mantis Dyrcona: I'm looking up the table in our database.  Do you know what the value is in reference to?  Doesn't appear like a time at least to me,.
12:48 Dyrcona I'm guessing it's caused by the fine generator, because this utility server only runs the find generator, reshelving complete, thaw expired frozen holds, and some SQL scripts.
12:48 Dyrcona mantis: It's number of seconds.
12:48 mantis Ok thanks for confirming
12:48 mantis Is it possible to set it a null value?
12:48 Dyrcona Ours is 14400 (4 hours).
12:49 Dyrcona Well, you can delete the entry in the database, which is the same thing.
12:49 Dyrcona It's not possible to set a null value.
12:51 mantis Thank you so much!
12:51 mantis Dyrcona++
12:52 csharp mantis: it's possible for it to be "" (empty string) which the code should treat the same as null/undefined
12:53 mantis That's waht I meant!  Thank you!
12:54 sandbergja joined #evergreen
12:57 Dyrcona You can also delete the entry from actor.org_unit_setting, which is what I prefer to do.
13:38 jvwoolf joined #evergreen
13:56 Dyrcona Hm.. The sky is getting ominously dark outside. I suspect a storm is in the offing.
14:00 Dyrcona "Here come ol' flattop..."
14:01 Dyrcona Sometimes a bug is a typo is a bug.
14:02 Dyrcona "Come together, right now, over me..."
14:17 csharp not dark yet, but it's getting there
14:17 Dyrcona csharp++
14:26 mantis1 joined #evergreen
14:28 mantis1 joined #evergreen
14:51 * JBoyer sits in day 2 of snow in April, does not enjoy it.
14:52 Dyrcona :(
14:53 Dyrcona It's a light rain here.
14:53 mmorgan At least it won't stay around long.
14:58 sandbergja joined #evergreen
15:14 jvwoolf1 joined #evergreen
15:34 nfBurton Is there a way to validate my database against changes through upgrades since V3.0? Or do I have to work through it manually. I found a couple missing items today and was just wondering if there was a way to check it without doing it all manually
15:36 Dyrcona You could check the config.upgrade_log table.
15:36 nfBurton The upgrade deps blocks or whatever was set to true
15:36 nfBurton But that (View in this case) was missing
15:37 nfBurton So it said it ran it but the table didnt exist
15:37 nfBurton Which is my trepidation
15:38 Dyrcona There's no easy way to do what you want.
15:39 Dyrcona You could load the schema for the version that you're on in another database, dump the schemas as SQL and diff the files. This is likely to produce a lot of false positives, though.
15:42 Dyrcona You could ask over in #postgresql about comparing schemas. I'm sure one of the experts there will have a better method.
15:45 jeff There are various tools. I've played with some. Didn't like any.
15:45 jeff But the last time I evaluated that was several years ago.
15:45 Dyrcona nfburton: https://www.pgadmin.org/docs/pgad​min4/development/schema_diff.html
15:45 Dyrcona Looks like pgadmin4 has a tool for that.
15:46 nfBurton I don't usually use PGAdmin but this is a cool tool
15:47 nfBurton Dyrcona++
15:47 nfBurton I figured if anyone knew it'd be you! With all your PG testing
15:47 Dyrcona I used to use PgAdmin3 all the time. Then, I tried PgAdmin4 for a while. Now, I'm back to mosly using psql.
15:48 Dyrcona I just searched the web and that turned up. It's a new feature apparently.
15:48 nfBurton Yeah I use PSQL with DBeaver
15:49 Dyrcona pgadmin4 is available in the Pg community apt repos, or you can download a binary for Windows somewhere.
15:50 Dyrcona It runs  a local webserver, etc.
15:57 jihpringle joined #evergreen
16:05 mantis1 left #evergreen
16:06 jeff Hrm. For the first time in a long while, we had a query that was on its way to consuming all available memory on the database server. pg_cancel_backend did eventually take effect, but only after many tense minutes.
16:07 * jeff looks through irc logs and launchpad bugs
16:07 jeff i have vague memories of long-ago conversations about such things. :-)
16:11 Dyrcona Best to use pg_cancel_backend and wait. If you use pg_terminate_backend, you'll have to clean up the temp space yourself.
16:12 Dyrcona I've been involved in more than one such conversation.
16:19 jihpringle joined #evergreen
17:12 mmorgan left #evergreen
17:22 sandbergja joined #evergreen
17:28 sandbergja joined #evergreen
18:00 pinesol News from qatests: Testing Success <http://testing.evergreen-ils.org/~live>

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