Search in #evergreen

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 2024-02-13

15:08	Bmagic	carry it forward?
15:08	mmorgan	Yep!
15:08	Bmagic	#action mmorgan will explore moving LP stats to community site and automating same
15:09	Bmagic	#info sandbergja will see if gh actions can run the pgtap tests
15:09	Bmagic	skipping
15:09	Dyrcona	#info Dyrcona = Jason Stephenson, CW MARS
15:09	Bmagic	#info GalenCharlton will open LP bug with the official proposal for git commit message release-note

Results for 2024-02-09

11:34	Stompro	Hello Friday Morning Evergreen Channel. I recently tried out using the patron address print template to create our new account welcome letters that we mail out for online applications. And that worked great. But it does take over the functionality there. Is there any way to add arbitrary print templates right now, and trigger them somehow?
11:38	Dyrcona	Stompro: Action trigger?
11:40	Stompro	Is there a way for front line staff to trigger that to generate on demand? That is the nice thing about how the print address template is setup. And the fact that each workstation can have custom templates easily.
11:41	Stompro	Obviously there is, thinking about the email and sms test notices.
11:42	Dyrcona	There's a way to trigger when a new patron is created. Action triggers can also be triggered on demand, examples include printing/emailing/downloading bib information the OPAC, downloading circulation history, etc.
11:43	Stompro	This wouldn't be for all new patrons is the issue, just the ones that need a welcome letter printed, which is just a subset of them.
11:45	Dyrcona	You said it was for online account sign ups? If you can't find a hook for those, you could use the normal hook and add a filter that identifies only the online account sign ups.

Results for 2024-02-08

10:26	Dyrcona	Yeah, using the filenames works. I think I like that better.
10:27	jeff	Dyrcona: let me know when you settle on a VM naming scheme that IS a good idea. two hard problems...
10:29	Dyrcona	Place names from Middle Earth? Planets/systems from Star Wars or Star Trek? I've tended toward boring, utilitarian names like eg-vm1, eg-vm2, etc. At the University of KY, College of Engineering Computing Center, we named the servers and a few workstations for airplanes.
10:30	Dyrcona	I have named my local vms for Evergreen testing for the Debian/Ubuntu release: bullseye, bookworm, focal, jammy. That works because they're ephemeral and will almost never be upgraded to a new release.
10:31	Dyrcona	OK. I have a gist to update.
10:34	Dyrcona	ooh... Cool. Using the filenames lets me eliminate four uses of `cut` and delete the now redundant path when "reading" the upgrade script file.
10:34	stephengwills	I named my hosts after snow whites friends but then I needed an 8th server and the scheme broke. wa-wa.
10:43	Dyrcona	https://gist.github.com/Dyrcona/00bd6b6290b6fbbb579c7f93b360ab0d # I've shared it before. I'm sharing it again, now.
10:46	Dyrcona	Think I'll link it from the git repo to my bin instead of having he whole script in there.
10:53	Dyrcona	looks like a record ingest will be required going from 3.10.3 to main.
10:54	Dyrcona	Well, that'll be a nice test of Pg 16, won't it?
11:01		sandbergja joined #evergreen
11:05	Dyrcona	Ugh. Looks like I'm going to have reinstall OpenSRf as well as Evergreen. I may end up rebuilding the VM from scratch if things don't go well. -- The joy of sikipping releases!
11:29	Dyrcona	The clobber option isn't clobbering the upgrade script....

Results for 2024-02-06

10:39		kworstell-isl joined #evergreen
10:57		sandbergja joined #evergreen
11:14		Dyrcona joined #evergreen
11:36	* mmorgan	frequently encounters the off-by-one error lately that results in attempting to login to a test system as the user SNUB
12:00	jeff	if I shifted like that, that would end up being either "nub" or "snub", depending on how quickly I hit the first two.
12:01	mmorgan	:)
12:07	Dyrcona	There are only two hard problems in computer science: naming things, cache invalidation, and off by one errors.
12:10	Dyrcona	berick: Yeahp. Data integrity is not our strong point.... j/k, honsestly.
12:10	Dyrcona	Guess Aspen does need a patch after all.
12:11	Dyrcona	I am joking about the integrity thing. I can get what I need from the target_copy field.
12:11	Dyrcona	Guess I didn't waste my time writing this test program after all.
12:11	Dyrcona	berick++
12:17	Dyrcona	heh. "investigating" sounds more professional than "playing around with" :)
12:29		jihpringle joined #evergreen

Results for 2024-02-05

10:33		mantis joined #evergreen
10:36		jvwoolf joined #evergreen
10:55		sandbergja joined #evergreen
11:10	Dyrcona	sandbergja: Did you get a chance to test the 3.11.3 tarball on Friday?
11:14	sandbergja	Dyrcona: yes, I ran the automated tests. They all passed except a few of the e2e nightwatch ones (which also fail on the rel_3_11 branch). I don't think they should block the release
11:14	Dyrcona	sandbergja++
11:14	Dyrcona	Do you have an announcment ready to go? I could stage the files at almost any time today, though I do have a couple of meetings.
11:15	sandbergja	redavis is signed up for that, and has some things ready to go, I think

Results for 2024-02-02

09:34	Dyrcona	I'm running it manually now.
09:36	Dyrcona	Grr. Insert can have only 1 ON COnFLICT clause. I'd actually like to do something different depending on which constraint triggers.
09:36	Dyrcona	Totally unrelated to offline blocklist, of course.
09:39	Dyrcona	This mean that I can't really test this update in its entirety. I'm updating some information related to users and my test database doesn't have all of the users from production.
09:40	Dyrcona	i suppose I could do the insert/update with a select statement or add a where exists....
09:46	Dyrcona	No? "and exists (select 1 from actor.usr where id = <user_id>) didn't help.
09:46	Dyrcona	Oh, duh....
09:47		redavis joined #evergreen
09:47	Dyrcona	Bmagic: Looks like offline-blocklist finished and the output is 18MB.
09:49	Dyrcona	Maybe the AND EXISTS will work if I remove the rule from the constraint...
09:51	Dyrcona	Nope. Do update requires inference specification or constraint name. Guess I can't really test the update, though it "worked" for the ones that existed, so it's good. Hopefully all of the users exist in production.
10:01	berick	hey, Ubuntu, how about I pay you not to advertise Ubuntu Pro at me? bleh.
10:01	berick	maybe time to mix up the ol' desktop OS
10:02	Dyrcona	berick: Have you considered Arch? I use it on my personal laptop.
12:38	pinesol	Launchpad bug 1901726 in Evergreen "Required Fields Based on Hold Notification Preferences Too Strict" [Medium,Confirmed] https://launchpad.net/bugs/1901726
13:01	abneiman	sandbergja++ redavis++ mmorgan++ Bmagic++ # rmaking point releases happen
13:02	mmorgan	abneiman++
13:32	sandbergja	The 3.12.1 tarball finished building. I'm going to try installing it and running the tests
13:40		jihpringle joined #evergreen
13:44	sandbergja	So far, the perl unit tests, perl live tests, pgtap, and angularjs unit tests have passed. Waiting on angular unit and e2e tests, OPAC js tests, and C tests.
13:47	sandbergja	I <3 tests, but dang, that is a lot of testing frameworks
13:47	sandbergja	I think two of them are my fault hahaha
13:47	Dyrcona	sandbergja++
13:48	Dyrcona	Well, we need more tests, and maybe fewer frameworks.
13:48	sandbergja	+1
13:49	Dyrcona	I suppose we can drop 1 of the frameworks, or at least 1 set of tests, when AngularJS is finally gone.
13:49	sandbergja	Oh, one test question that I've been meaning to ask forever. What is the distinction between pgtap regression tests and just regular pgtap tests?
13:51	Dyrcona	The regression tests are, I think, meant to check that certain database changes have not been undone.
13:52	Dyrcona	I added a regression test to my branch for Lp 1835953 to make sure that the columns have the not null constraint.
13:52	pinesol	Launchpad bug 1835953 in Evergreen "Circulation auto renewal remaining should not be nullable" [Medium,In progress] https://launchpad.net/bugs/1835953
13:53	sandbergja	Dyrcona++
13:54	sandbergja	I like that example!
13:58	Dyrcona	That branch makes a few updates to the pgtap tests and the sample data load.
14:08	sandbergja	3.12.1 tarball tested and it passed!
14:09	sandbergja	I've uploaded the release directory here: https://drive.google.com/drive/folders/1PVlPVhJ8UtUUH7Yu1JRSsJkr1TOo0Fgv?usp=drive_link -- gmcharlt: could you please upload it to lupin?
14:21	sandbergja	I pushed my working branch to tags/rel_3_12_1. I also added the upgrade script to the rel_3_12 and main branches. Does that seem as it should be?
14:21	Dyrcona	Yes, that sounds right. Let me have a look.
14:22	sandbergja	Dyrcona++
14:22	Dyrcona	Looks good to me. I can copy the files to Lupin if gmcharlt hasn't gotten to it, yet.
16:00	Bmagic	I've not done any release work today
16:01	Dyrcona	Bmagic: I'm talking about last time.
16:02	Bmagic	on point releases, I believe we skip down to Translations, Part 2: update_pofiles steps. new pot would be applied to the main branch of the evergreen release series. AKA rel_3_12. And not* against tags/rel_3_12_1. At least that's the way I understand it. Please feel free to correct me!
16:03	Dyrcona	Don't know if I'll finish testing this today. We'll see.
16:03	Dyrcona	Bmagic: newpot was done the previous two times on 3.11, so I did it again.
16:03	Dyrcona	The commits are there anyway.
16:04	Bmagic	ok, that's fine. It's ok if it's done against the point release tags branch, though I believe the design intension was to have new pot run ahead of time, at some frequency, independent of the point release cycle
16:04	Dyrcona	Should I test with OpenSRF main or 3.2.4?
16:05	Bmagic	I'm not sure it matters today if you use main opensrf or 3.2.4. Is there a commit difference between them?
16:06	Dyrcona	Yeah, I'm going with main because I already installed the prerequisites.
16:06	Dyrcona	I did that reflexively before I started working on release building.
16:16	Dyrcona	I fixed the syntax and regenerated the HTML. I'll have to update the tarball.
16:16	Dyrcona	No, you don't have a point release assigned to you. I don't think we're using the spreadsheet this time.
16:18	Dyrcona	oof. I just realized that I've been using markdown link syntax when I've been writing release notes lately. I'll have to fix those, I think.
16:22	Dyrcona	I'm not going to be able to test this today.
16:25	pinesol	News from commits: Fix syntax in 3.11 release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2d50b18103dcf0480467bfcab5b3ce2f173a7f38>
16:27	Dyrcona	i can probably test the db upgrade scripts without too much setup.
16:29	Dyrcona	nah, I'll have to test this later.
16:30	Dyrcona	I pushed the tag branch and copied the files to lupin where I can get them later to test.
16:30	Dyrcona	I'll have to see if I can test this tomorrow some time, but I've got stuff to do.
16:34	Dyrcona	I've put the release files here: https://drive.google.com/drive/folders/1Eys7BQV4TdDcgs8QtXy6XJ46QC8CMbyK?usp=sharing
16:35	Dyrcona	If anyone else wants to test. Also, let me know if you can't access that or the contents. It should be shared with anyone who has the link.
16:35	sandbergja	Dyrcona++
16:35	sandbergja	I can run the automated tests on that tarball this afternoon
16:36	Dyrcona	sandbergja++
16:53	sandbergja	It would be nice if we could make the perl live tests and nightwatch e2e tests faster too. I suspect that's a barrier to people running them regularly.
17:06		jihpringle joined #evergreen
17:09		mmorgan left #evergreen
17:16	sandbergja	all tests are passing for that 3.11.3 tarball, except for 3 of the nightwatch tests (for vandelay, holdings view, and acq providers). I didn't see anything obviously amiss with those screens, fwiw. It is not specific to the tarball. I get the same failures after installing rel_3_11 from source.
17:16	sandbergja	I think we should investigate them, but I don't think they need to block the release or anything.
17:17	sandbergja	abneiman++ redavis++ Bmagic++ Dyrcona++ mmorgan++ # thanks for helping with these releases!
17:38		book` joined #evergreen
19:27		jihpringle joined #evergreen

Results for 2024-02-01

15:15	berick	mmorgan: i only meant we don't systematically apply pcrud perms to every pcrud-accessible class in the IDL, esp. if pcrud was not initially used to manage the class.
15:46		adam_reid joined #evergreen
15:55	adam_reid	hey all! I've been looking at the actor.verify_passwd() function in the evergreen DB, am I understanding it correctly that I should be able to pass in (usr.id, type, password) and get a true false result? I'm playing with a little custom tool and want to require users to verfiy beforehand
15:58	berick	adam_reid: yes, but it's a little more complicated with 'main' passwords
16:00		sandbergja joined #evergreen
16:00	berick	adam_reid: select * from actor.verify_passwd(1, 'main', md5((select salt from actor.passwd where usr = 1) \|\| md5('demo123')));
16:01	berick	that's my test system where admin has password demo123
16:01	adam_reid	amazing, I had the feeling I was missing the use of md5, I'll try with you example. Thanks berick!
16:06	adam_reid	Fantastic, that worked berick!
16:06		mantis1 left #evergreen

Results for 2024-01-30

10:51	Bmagic	nothing formal
10:51	Dyrcona	OK. cool.
10:51	Dyrcona	How many I can attend depends on my schedule. I've been busy with Aspen stuff lately.
10:52	Dyrcona	My rebased branch works and all tests pass, including the ones I modified. I'm having a good day so far. :)
10:55	Dyrcona	Think I'll look for something to review on my own this afternoon.
10:59		sandbergja joined #evergreen
11:09		jvwoolf joined #evergreen
14:46	pinesol	News from commits: LP1998413 - Holdings Editor Batch Actions restore prefix/suffix option <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=230e7a23422b9e0b4ab587244079bad858c9eb17>
14:47	Dyrcona	pinesol I think you're a conspiracy theorist.
14:47	pinesol	Dyrcona: http://images.cryhavok.org/d/1291-1/Computer+Rage.gif
14:52	* Dyrcona	sometimes to assign bugs to himself when testing.
14:53	* Dyrcona	also sometimes forgets to type words in IRC. I think my brain gets ahead of my fingers.
15:00		kworstell_isl joined #evergreen
15:05	sandbergja	nfaber: I've had a lot of luck using the docker containers from BMagic on my M1 macbook: https://hub.docker.com/r/mobiusoffice/evergreen-ils

Results for 2024-01-29

15:51	* Dyrcona	decided to go with the STAFF_LOGIN version.
16:19	sandbergja	Dyrcona++
16:41	Dyrcona	2 files changed, 6953 insertions(+), 7122 deletions(-)
16:48	Dyrcona	Perl tests pass.
16:48	Dyrcona	I'll check some of the Angular interfaces tomorrow.
16:57		mantis1 left #evergreen
19:53		jihpringle22 joined #evergreen

Results for 2024-01-26

10:26	Dyrcona	berick: It gets crazier because the backend sends just the workstation id to the AngularJS client, and the client appears to use what the back end sends it. I would suspect a change in a dependency except it works with a stock release on the same data.
10:27	Dyrcona	No database errors either.
10:30	Dyrcona	I've got 47 commits to bisect... Dunno if I want to go all the way back to start since it apparently worked last week.
10:32	Dyrcona	I should test this on a more recent release with similar patches.
10:33	Dyrcona	I have two available.
10:43	Dyrcona	OK. it works on a more recent Evergreen release, but that one may not have all of the patches or may have one that's missing. I can't rule out that we dropped something.
10:49	Dyrcona	Guess I'll bisect everything.

Results for 2024-01-25

13:59	Dyrcona	yes.
14:00	Dyrcona	I might give xmllint a whirl later. I think I'm going to put this aside for a bit and work on something more important.
14:02	Dyrcona	The indentation doesn't respect the vim/Emacs settings at the bottom. I have also noted that the Emacs on this Ubuntu 20.04 laptop is ignoring the settings. We've got mostly tabs, but some spaces mixed in.
14:04	Dyrcona	I suspect the file may be too large for Emacs to care about the settings at the bottom. If they were at the top, it would probably work. I may move the comment just to test that theory. They're also some "unsafe" variables, so I may need to check if I've allowed them to be changed in my Emacs config....Software....
14:22		jvwoolf joined #evergreen
14:43		jihpringle joined #evergreen
14:57		kmlussier1 joined #evergreen

Results for 2024-01-24

10:24	Dyrcona	Stompro++ # For most of the performance improvements.
10:25	Bmagic	I was tracking that thread
10:25	Dyrcona	Mostly for items, yes.
10:26	Bmagic	this execution is sans items. At least I think it is. I didn't pass any arguments to marc_export. My command: cat records.txt \| marc_export > test.mrc
10:27	Dyrcona	Well, use your own extractor if it is faster. Also, "Patches welcome!"
10:27	pinesol	News from commits: LP1839364 Move login page error message; add ARIA <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=8a92c0619f366e1854575d686c3619d5d559f694>
10:27	pinesol	News from commits: LP#1945003: (follow-up) redo lint fixups <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=4fdaf17cf6a91a6f7e3a8bcf1864aef526ffeed8>

Results for 2024-01-23

09:10		kworstell-isl joined #evergreen
09:42		dguarrac joined #evergreen
09:50		kworstell-isl joined #evergreen
10:30	csharp_	Bmagic: do y'all still have tools for LibraryIQ export that are shareable somewhere? the vendor has an outdated link to the mobius_evergreen repo...
10:31	csharp_	we have a library interested in testing
10:31	Bmagic	yep! Let me get the link
10:32	Bmagic	csharp_: https://github.com/mcoia/evergreen-libraryiq-export
10:38	csharp_	Bmagic++ # muchas gracias
15:17	Bmagic	I've decided (based on the strength of recent new installation of Evergreen 3.11.1 on PG15 for a new group of academics) that we upgrade to PG15 for anyone going to 3.11 and greater
15:18	Dyrcona	I wish more folks would actually look at new Pg versions. I'm playing with pg 16 and production data, now, but have no idea if it is really ready for prime time.
15:19	Bmagic	We have two production consortia on pg15. Been 6 weeks or so. So far it's just fine
15:19	Dyrcona	Also, i don't know that pg versions should really cause bad character issues in the data. We could check the release notes again. I know that we have had to adjust the creations of some indexes and update tests because of Pg changes with character set handling in the past.
15:20	Bmagic	the character issue may not be related. I was sort of guessing, because the PG version was something we changed between then and now. But records get added all the time too, so....
15:20	Dyrcona	Those were mainly related to stripping accents in name search.
15:22	Dyrcona	We get wide character and other warnings during export all the time. The best is when some UTF-16 sneaks, usually copy and paste from a browser. It always seems to happen when someone copy/pastes a description from Amazon.

Results for 2024-01-19

09:40	Dyrcona	"Pg16" sounds like a movie rating, not the name of a virtual machine.
09:44	Dyrcona	git: "Please tell me who you are."
09:48	csharp_	Dyrcona++
09:51	Dyrcona	git fetch --all shows some interesting things to test later.
10:17	Dyrcona	live_t/37-carousels.t (Wstat: 65280 Tests: 2 Failed: 1)
10:24	Dyrcona	huh. This time it worked....
10:30	berick	conf deadline... i'd be happy to talk about redis, but I think people would rather hear from someone else at this point.
10:30	berick	maybe a short on some rust stuff i'm doing

Results for 2024-01-18

11:48	jeff	using Hatch?
11:48	berick	yeah
11:49	* Dyrcona	mumbles something about editors and indentation being adjusted automagically.
11:50	jeff	In the newly opened tab, before reloading the page, window.document.documentElement.getAttribute("hatch-is-open") returns null.
11:51	jeff	reloading the page causes it to return the expected value.
11:51	jeff	(and workstation fetching from Hatch works, as evidenced by the workstation appearing in the top nav)
11:52	jeff	might be something Windows-only. I've tested on 2+ machines running Windows 10 with Hatch 0.3.3
11:53	jeff	Evergreen 3.10 and 3.12. I can reproduce on demo.evergreencatalog.com
11:53	jeff	Haven't tried to reproduce on Linux or macOS, mostly because we don't use Hatch on those anywhere currently.
11:58	jeff	interesting. it also happens when I right-click and "Open link in new window". That new window opens in the foreground, so that seems to rule out something related to background tabs or page visibility api.
12:06		jihpringle joined #evergreen
12:09	jeff	no report in console of the new window/tab loading the Hatch relay content script.
12:23		kworstell-isl joined #evergreen
13:52	jeff	(where "break it" is: no workstation name after the username in the top right corner; redirected to the register workstation page)
13:53		dguarrac joined #evergreen
13:55	Stompro	jeff++ thanks for tracking this down
13:58	jeff	things that this seems to have had nothing to do with: background tabs, preloading/prefetch, memory/energy saving, angular routing, Chrome updates, and field tests. :-)
14:12	berick	jeff: hm, turns out I can reproduce in main, but not in KCLS-tweaked EG 3.9
14:12	* berick	tries 3.11
14:15	jeff	reproduced on Debian 11 with Chrome Stable against 3.12 (demo.evergreencatalog.com) just now.

Results for 2024-01-12

10:51	nfaber	Nice to meet you all!
10:54		collum joined #evergreen
11:10	redavis	Welcome nfaber!!
11:18	mantis1	nfaber: this is a test ping! yay
11:22	Dyrcona	redavis: I assume from yesterday's conversation that the Evergreen community Aspen discussions are still ongoing. I found some email saying the fourth Monday of the month. How does one connect?
11:25	Dyrcona	I also think it might be useful to summarize the patches needed for forthcoming Aspen/Evergreen features. Not sure if the General mailing list or either Aspen Evergreen group would be the proper venue. Probably all 3.
11:28	redavis	Dyrcona, the community Evergreen Aspen meetings are going to be bimonthly. Here is the feature/issue list we have. https://docs.google.com/spreadsheets/d/17ZTGQ9wHuhqL3HvrSZUDU0-AP7culAzDk3B4brKk7c4/edit?usp=sharing

Results for 2024-01-09

09:03		Dyrcona joined #evergreen
09:13		dguarrac joined #evergreen
09:28		mantis1 joined #evergreen
09:38	* Dyrcona	prepares to switch his main test database from pg 15 to pg 16.
09:58		sleary joined #evergreen
10:02		Rogan joined #evergreen
10:05		jihpringle joined #evergreen
15:03	abneiman	#info abneiman = Andrea Buntz Neiman, Equinox
15:03	mmorgan	Dyrcona++
15:03	Bmagic	#action mmorgan will explore moving LP stats to community site and automating same
15:03	Bmagic	#info sandbergja will see if gh actions can run the pgtap tests
15:04	sandbergja	no progress on pgtap in github actions
15:04		collum joined #evergreen
15:04	Bmagic	#action sandbergja will see if gh actions can run the pgtap tests
15:04	Bmagic	#info Dyrcona will summarize release coordination discussion and followup on the development mailing list.
15:04	Dyrcona	#info Done!
15:04	Bmagic	suhweet
15:08	pinesol	Launchpad bug 2047707 in OpenSRF "track browser and tab for staff interface logging" [Wishlist,New]
15:08	GalenCharlton	upshot of that one: will help us deal with runaway pcrud explosions and general load monitoring
15:09	Bmagic	interesting!
15:10	Bmagic	I have a VM setup to test the redis branch(es), I really need to get back to that
15:10	eeevil	GalenCharlton: since the agenda is otherwise thin, I have a question about that!
15:10	GalenCharlton	eeevil: go for it
15:11	eeevil	do you imagine being able to make it a hard client requirement (think: soft API key) or just (for now) some extra info a client /should/ pass so we can know who's who?
15:15	Bmagic	There's a bug somewhere having to do with closing the tab, causing the pcrud wall-o-requests
15:15	GalenCharlton	ayup
15:16	GalenCharlton	and while I _also_ have some thoughts on ameliorating that from the Angular and AngularJS code, the ability to detect that a specific browser is spamming requests and doing a block (or even just a forced WS connection reset) would be very useful
15:17	Bmagic	coolio! Anyone here want to chime in on testing redis and/or adding comments on the tab-tracking proposal bug
15:18	Bmagic	I suppose we can move on now
15:18	Bmagic	#topic Documentation
15:18	Bmagic	dluch won't make it today. abneiman, any update?

Results for 2024-01-05

10:01	Dyrcona	@blame 3a9279694aff88c4b7909fec00b50faea92212cd
10:01	pinesol	Dyrcona: 3a9279694aff88c4b7909fec00b50faea92212cd typed Google into Google; broke the Internet.
10:02	Dyrcona	So, if you encounter that configure error, it means you need to upgrade OpenSRF.
10:03	* Dyrcona	fires up a local vm to run pgtap tests on Pg 16.
10:04	Dyrcona	BTW, You can check the lib version with autotools. Not that we've been versioning libraries "correctly" either.
10:07	Dyrcona	Did I mention before that I find Github's new 2FA requirements to be annoying? Well, if I didn't, I do, and if I did, I still do.
10:14	Dyrcona	Hmm... Make a Pg 16 branch now, or test Pg 16 first?
10:16	Dyrcona	Upgrade an existing VM or wipe it out and start over?
10:16		briank joined #evergreen
10:20		sandbergja joined #evergreen
11:11	Dyrcona	my session was still logged in as far as I could tell.
11:33	Dyrcona	The Redis code has not been merged to OpenSRF main, yet?
11:33	berick	negatory
11:34	Dyrcona	If I want to test redis on a fresh install which branch should I use?
11:34	berick	collab/berick/lp2017941-opensrf-on-redis-v3
11:35	Stompro	Bmagic, I like the look of that schemaspy.org project, the relationship diagrams are nice, and it would make schema comments visible.
11:35	Dyrcona	berick++
11:39	berick	may be what you're thinking of
11:40	Dyrcona	OK.
11:40	Dyrcona	That is probably what I'm thinking of. I'll just the working branch.
11:40	Dyrcona	I plan to test Pg 16 and redis on this vm. I have redis installed elsewhere, too.
11:42	Dyrcona	I guess I have to time to build the base vm right now.
11:42		redavis joined #evergreen
11:52	csharp_	Dyrcona: re 2FA, I'm facing that issue with our local GitLab install after a recent version upgrade :-/
14:36	* pinesol	grabs a bottle of Smirnoff Ice Passionfruit and sends it sliding down the bar to gmcharlt
14:38	kmlussier	That last one sounds promising. "... infused with a sweet tart flavor for total island vibes." Maybe gmcharlt will share.
14:55		briank joined #evergreen
15:08	Dyrcona	OK. Here gotes the big test: eg_db_config on Pg 16.
15:10	bshum	Oooh cookies. Thanks kmlussier!
15:12	Dyrcona	bshum++
15:12	Dyrcona	kmlussier++
15:13	Dyrcona	And, it just works.
15:15	Dyrcona	pgtap tests succeed.
15:21	kmlussier	bshum: I knew you would like those! :)
15:24	berick	Dyrcona: arg, good catch
15:24	berick	re: hosts
15:32		jihpringle joined #evergreen
15:33	Dyrcona	I bet I accidentally edited the .example file after copying.
15:34	Dyrcona	Yeah. That's what happened. The files are identical.
15:34	Dyrcona	Perl tests succeed, too.
15:35	Dyrcona	Think I'll switch from Pg 15 to Pg 16 as the main database on my test server.
15:38	Dyrcona	Maybe next week. I should read the release notes again for any gotchas.
17:05		mmorgan left #evergreen
17:15		kmlussier left #evergreen

Results for 2024-01-04

09:02		dguarrac joined #evergreen
09:14		mantis1 joined #evergreen
09:16	Dyrcona	I've noticed that with psql 16, \df+ <function> no longer shows the function definition.
09:22	Dyrcona	I had to use \ef <function> to open it in a test editor, which gives you the SQL used to create the function.
09:24	Dyrcona	Interesting... psql 10 gives an error when doing \df+ on a pg 15 database. I wonder if \df+ from psql 16 works on a Pg 16 database. It probably does.
09:25	* Dyrcona	loads a dump into pg 16 to see what happens.
09:26	Dyrcona	Heh... "Talk Soup" by Weird Al just started playing.... :)
09:26	mantis1	talksoup++
09:27	Dyrcona	"Listen to me! Listen to me! Listen to me!" :P
09:30	* Dyrcona	updates a script for pg 16 on the test db server.
09:32	Dyrcona	Whee! Just copy, paste, and edit 3 lines.
09:35	JBoyer	Dyrcona, so long as you specify enough params to uniq-ify it, \sf should show you the function source
09:35	JBoyer	(similar to \df+ I mean)
09:35	Dyrcona	JBoyer: OK. I was going to check with psql 16 on a pg 16 database because I think its an issue client server mismatch and not a change in features.
09:36	JBoyer	Oh, I see what you mean. Yeah, the queries backing that feature may have changed / broken / been removed in psql 16.
09:36	Dyrcona	Now that I have used it, I think I prefer \ef, at least when I'm running psql locally and talking to a remote server.
09:37	Dyrcona	I also plan to finally get around to adding Pg 16 support for Evergreen, so this will be a good first test.
09:43	Dyrcona	I suppose it is a good sign that pg_restore has not produced any output to the screen.
09:43		smayo joined #evergreen
09:51		BDorsey_ joined #evergreen
12:28		jvwoolf joined #evergreen
12:55		sleary joined #evergreen
13:28		smayo joined #evergreen
13:38	csharp_	Dyrcona: I tested out all but one of the LP scripts you shared and with a couple of Python 3-ish changes, they appear to work
13:39	csharp_	the release.py one is untested since it appears to make changes and I wanted to get my head around it first
13:39	csharp_	smayo may do some work on things too - we're still in research mode to make sense of the release process
13:47		jvwoolf joined #evergreen
13:58		dguarrac_ joined #evergreen
14:11		mdriscoll joined #evergreen
14:20		mdriscoll joined #evergreen
14:25	mdriscoll	I want to copy some patrons from a production system to a test system and I need their password to work. I have the password hash but not sure how to do the insert so the password works and isn't set to literally 'd41d8cd98f00b...' Any ideas?
14:31		mdriscoll joined #evergreen
14:34	jeff	mdriscoll: that looks like the start of the md5 hash of an empty string. you'll probably want to take a look at the actor.passwd table.
14:36	jeff	mdriscoll: if you copy a user's row from actor.usr and actor.passwd (and actor.usr_address, actor.card, etc), then the copied user on the test system should end up with the same password as on the source system.
14:39	mdriscoll	jeff: thanks. I think actor.passwd is the part I was missing.
14:41	jeff	mdriscoll: depending on how empty your test system db is, you may need to worry about conflicts, renumbering ids, etc. Even if you don't, consider that if you manually insert ID values, you'll want to either bump sequences or know that eventually you'll run into an error when some future insert gets that manually-inserted value from its default sequence.
14:42	jeff	(depending on what kind of a test system this is, and how long it will be around, and other things, you may not care)
14:48	mdriscoll	jeff: I'm altering a script I use for loading patrons where I usually set the password and let the database trigger crypt the plain text. I let the database create the new ids but duly noted about bumping sequences.
15:01		mmorgan1 joined #evergreen
15:10		smayo joined #evergreen

Results for 2024-01-03

11:01	Rogan	btw, I'm not in that cage match - if your editor works for you then power to you :)
11:01	Rogan	heh
11:02	berick	by the same token, a couple of git checkout commands are gravy compared to the rest of the eg/osrf install docs.
11:03	Rogan	and I've made use of berick's ansible scripts to automate it when wanting to just throw something up quick(ish) for testing
11:05	berick	but tarballs have pre-compiled / pre-downloaded stuff, so it's more than just a checkout, of course.
11:18	csharp_	mantis1: just a quick warning about virtualbox (or any VM running on a PC/laptop) - make sure the RAM is sufficient to run a VM that takes 4GB RAM minimum, and probably 2 CPUs
11:20	csharp_	mantis1: at GPLS we used to repurpose older servers or even PCs to run as a dedicated VM host, but that might be a rabbit hole
12:16	mantis1	but it's good now: https://docs.google.com/forms/d/e/1FAIpQLSfjPGS3IZYkJxNZslkYaUYfwX24QxXRktrDvALM6E1jQZfGhQ/viewform?usp=sf_link
12:19	berick	mantis1: thanks!
12:22	csharp_	mantis1++
12:24	bshum	mantis1: I'll be curious if 4 GB of RAM Is sufficient for a small test VM. I feel like I was bumping up on problems last time I sized something that small, and it worked better with 6-8
12:25	bshum	Might just be my tricky memory.
12:25	mantis1	berick++
12:25	mantis1	bshum: we did allocate more ram out I believe but I'll send an update on specs and how this goes
12:25	csharp_	bshum: you're probably right, but I'm guessing the RAM on a typical laptop/PC is maybe 8GB? and Windows is a hog
12:26	csharp_	(assuming we're talking about Windows 10/11 prolly?)
12:26	bshum	csharp_: Oh certainly. Windows :P
12:26	Dyrcona	With KVM on a Linux host 4GB is enough for basic testing. If you really want to do something with it, you'll need more RAM.
12:26	bshum	@karma Microsoft
12:26	pinesol	bshum: Microsoft has neutral karma.
12:29	csharp_	given Microsoft's relatively recent tolerance and sometimes support of open source software, they don't get as much negative karma from me as they used to :-)
15:11		mantis1 left #evergreen
15:28		Stompro joined #evergreen
15:35	JBoyer	Looking forward to the forthcoming gaming soundtrack from Character Limit Break
15:46	pinesol	News from commits: LP#2044141 (follow-up) tweaks to OPAC tests GitHub action <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=631c7be752a7c9f5d5b91e26d24be949d0c7a4ea>
15:46	pinesol	News from commits: LP2044141: Run javascript unit tests in github actions <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=514ad0c2c1b845d501a820d0d28b4fe2caede1e7>
16:16	pinesol	News from commits: LP#2046970 Poorly Cropped Reports Icon <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=db508c9037a44cc08dcf0a9f1ef102a70fe3542d>
17:15		jihpringle joined #evergreen
17:16		mmorgan left #evergreen

Results for 2024-01-02

14:12	Dyrcona	berick++ I was just getting there.
14:17	Dyrcona	I should probably rename Evergreen\Utils\Session to Evergreen\Utils\AuthSession in case I ever implement OpenSRF\Session.
14:18	Dyrcona	or maybe rename it to Evergreen\AuthSession... I'm still figuring out the API.
14:30	Dyrcona	I also question how useful this code is going to be for its original purpose: Testing changes to Aspen. My Fieldmapper is a lot more sophisticated than what Aspen does.
14:31	Dyrcona	hah!
14:31	Dyrcona	The song that's starting now: "Watch out! You might get what you're after..." Burning Down the House by Talking Heads.
14:31	berick	heh

Results for 2023-12-28

10:07	* mmorgan	would love to see item templates moved to the database - maybe to that very table!
10:08	Dyrcona	I thought they were in user settings? That's bib templates, isn't it?
10:26	Dyrcona	Is there a standard for the miscellaneous.adoc file under RELEASE_NOTES_NEXT?
10:32	Dyrcona	Hmm.. I could add a PgTap regression test or something like that. Might as well.
10:40	Dyrcona	Apparently, one can only check if a column constraint exists and not its definition?
10:42	mmorgan	Dyrcona: Yes, item templates are in user settings in a big blob per user. Tough to manage. Bib templates moved to the db would be good also. That's bug 1131238.
10:42	pinesol	Launchpad bug 1131238 in Evergreen "Move MARC templates into the database" [Wishlist,Triaged] https://launchpad.net/bugs/1131238
10:43	Dyrcona	mmorgan: I remember that bug. :)
10:44	Dyrcona	I guess I'll give up on a regression test since it won't be easy to do what I want. I'll just specify that one should check the table definition before and after applying the patch.
10:59		smayo joined #evergreen
11:08	Dyrcona	We should take some time to go through the bugs to find those that are "lost." I'm just looking at the ones with patches right now, and I see a few that might need some attention.
11:39	Dyrcona	Some bugs have had folks assigned to them for a long time, and I wonder if the bugs are still being looked at.

Results for 2023-12-27

09:55		dguarrac_ joined #evergreen
11:03		sandbergja joined #evergreen
14:03		sandbergja joined #evergreen
14:10	Dyrcona	So, I think I found a bug in SuperCat while testing my changes. I don't think I wrote this bug, either. It looks like there is insufficient fleshing for stat cat entries.
14:12	Dyrcona	/opac/extras/supercat/retrieve/marcxml/acp/<copy_id> Gives an internal server error and the error message indicates that the stat cat entries are not fleshed: Can't locate object method "opac_visible" via package "3" (perhaps you forgot to load "3"?)
14:12	Dyrcona	And, yeahp. They aren't fleshed properly.
14:23	Dyrcona	Then, I sometimes wonder if I get the URI correct because some of these are producing 500 errors with nothing useful in the logs.
14:49		Rogan joined #evergreen
14:51	Dyrcona	Yeah. Guess I'lll have to Lp that. Adding asce => [qw/stat_cat/] to the "flesh" list in two places fixes it.
14:51	mmorgan	Dyrcona++
14:55	Dyrcona	It's hard to test your own changes when you encounter other bugs. :)
14:56	Dyrcona	This means my feature branch will likely need a rebase before it can be merged if the bug fix goes in first.
15:18	Dyrcona	Yeah, I made my local fix based on my feature branch and I get a conflict cherry-picking the change to a clean branch base on main. :)
15:27	Dyrcona	Well, that's interesting. The stat cats are empty even though it doesn't crash. Guess it needs more work.

Results for 2023-12-15

11:16		sleary_ joined #evergreen
11:25		jihpringle joined #evergreen
11:42		jvwoolf joined #evergreen
12:05	Bmagic	does it make sense to anyone that a text message would make it to the cell phone using the test feature in the my account opac for one account but not another account. Using the same phone number and carrier on both accounts?
12:06	jvwoolf	Same sending address for both?
12:06	Bmagic	yep, same server
12:07	Bmagic	I can see the process all the way through, and the mail logs in one case is "Sent" and the other is "Service Unavailable"
12:27	kmlussier	I am very much looking forward to the day when we no longer send our texts that way. NOBLE has been looking at other options for the past couple of months.
12:27	jeff	That answer doesn't help you solve the problem, but hopefully it helps confirm that there may be no clear reason other than you're hitting rate limits and spam filters and intentional brownouts/deegredations of the target service.
12:31	jeff	we spend on average a little over $0.01/message to not have to worry about it.
12:38	Bmagic	ok, it was a differenting sending address. haha. The two accounts were attached to two different org units, and the test template walks up the org tree to find an accosiated email address, and found one that isn't allowed to sen through our relay. Mystery solved
12:38	Bmagic	phew, I was losing my mind
12:39	jeff	phew. next time, keep the above in mind also. :-)
12:40	jeff	my understanding is that time of day can also influence carrier SMTP to SMS gateways.

Results for 2023-12-14

10:00		jvwoolf joined #evergreen
10:00		sleary joined #evergreen
10:12		sandbergja joined #evergreen
10:16	csharp_	Bmagic> Dyrcona: Just testing my tarball, and I got this while building the old concerto set: psql:assets_concerto.sql:58: ERROR: update or delete on table "record_entry" violates foreign key constraint "browse_entry_def_map_source_fkey" on table "browse_entry_def_map"
10:16	csharp_	terranm saw that same error yesterday - currently trying to reproduce it
10:18	csharp_	and.... no, I can't reproduce it on 3.12.0
10:18	csharp_	(from git, not tarball, if that matters)
10:21	Bmagic	csharp_++
10:22	Bmagic	I don't think the build process messes with the concerto set, but, of course, the base schema build is there in the rel_11 branch. I would think that if there was an issue with the schema, the enhanced concerto would have the problem too
10:36		redavis_reboot joined #evergreen
16:22	adam_reid	ok, thats fair, so does Evergreen need to be aware of the page earlier in the process?
16:22	jeff	just the tt2 bits, or Evergreen variables/functions also?
16:23	jeff	do you have the tt2 source somewhere? that would answer some of the questions. it sounds like public data?
16:23	adam_reid	I'm not 100% the difference, I think just the tt2 bits
16:24	adam_reid	no source anywhere yet, to test the idea I basically just made a blank test page, I assumed it would resolve but didn't expect to be asked to login by default
16:24	jeff	which path did you put it at?
16:25	adam_reid	at the time /openils/var/templates_custom/opac/test.tt2
16:26	adam_reid	I figured if the simple test worked I would start to see what was possible, the page was essentially blank, once logged in everything worked fine, pulled in a few carousels and they worked
16:26	adam_reid	just didn't want users to need to log in
16:30	terranm	I'm not 100% certain, but you may need to add it into EGCatLoader.pm to route
16:31	terranm	Example - https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=fc361eeb6759c7af074b14f8faa9b9c4d37bbb77
16:34	adam_reid	interesting... right, seems that addition would've required a similar setup, looks like a great place to start looking, THANKS terranm
16:39	jeff	depending on your needs, you can drop a tt2 file in a place outside of the opac dir, like (using your example above) /openils/var/templates_custom/local/test.tt2
16:40	jeff	(without needing to define a route, etc)
16:41	terranm	jeff++
16:44	* JBoyer	Eg tarballs rebuilt, uploaded, and updated.
16:44	adam_reid	interesting, thanks jeff. I'll play around with that too!

Results for 2023-12-13

09:26	Dyrcona	sandbergja++
09:28	* Dyrcona	ponders how much the PHP Evergreen objects should resemble their Perl counterparts.... There are two ways I could implement property access, and one is similar to the Perl way, the other is more like public property access. I could do both.
09:30	jmurray-isl	For some reason, the concept of "PHP Evergreen objects" leaves a bad taste.
09:32	Dyrcona	jmurray-isl: I have reasons for implementing Evergreen client code with PHP, mainly to do with testing Aspen code changes. I'm going a bit farther than I might actually need to go and implementing actual classes for a client, fieldmapper, requests, objects, and probably another to represent class metadata.
09:38	pinesol	News from commits: Docs: release notes for 3.11.2 <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=82d206eebd22b89a9ea002cb58188adf1c84169d>
09:39	jmurray-isl	Dyrcona: I get it. It's mostly just the principle for me.
09:41	Dyrcona	jmurray-isl++
09:46	jmurray-isl	Indeed.
09:47	Dyrcona	CLI programming in PHP is a different thing, and it's easier/better in some ways.
09:48	jmurray-isl	Agreed. My initial work with VuFind was pre-Zend. The cli harvest scripts were much easier to troubleshoot.
09:51	Dyrcona	I kind of like using the interactive mode (aka REPL) for testing code. The only problem is having to restart when I change a class definition. (In Lisp, I can just reload the file and it will replace the existing code definitions.)
09:54	sandbergja	Dyrcona: 3.10.4 release notes pushed
09:56	Dyrcona	sandbergja++
09:56	mmorgan	sandbergja++
11:28	Dyrcona	Looks like just --disabled-password.
11:28		mantis1 joined #evergreen
11:30	Dyrcona	yeah, i know... I should script this with ansible.
11:40	kmlussier	Dyrcona: On the other hand, it's always good to have an opportunity to test the steps in the README.
11:46	Dyrcona	Oof. have to start over. I started installing prerequisites for the wrong branch.
11:53	Dyrcona	Maybe another burrito will help?
11:58		jihpringle joined #evergreen
14:08	pinesol	News from commits: Docs: final updates to 3.12 release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=807fb5cf59f4ba65a4d668cfbf87627fbf36ebb9>
14:10		jvwoolf joined #evergreen
14:14	jmurray-isl	win 2
14:16	Dyrcona	Live tests are failing. Guess I'll need to figure out what I did wrong.
14:18	Dyrcona	heh. --load-all-sample might help. :)
14:23	Dyrcona	yeah, that's much better.
14:33		jihpringle joined #evergreen
16:09	pinesol	News from commits: LP2046362 Button type for staff portal catalog search <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=533b9e5bcc11dc99bd5a0d1393bb8a46934c7d18>
16:09	pinesol	News from commits: Forward port 3.10.3 to 3.10.4 db upgrade script <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=b6d73efaac01e2604d6871d1bcf704b4fcb41f14>
16:18		smayo joined #evergreen
16:20	Bmagic	Dyrcona: Just testing my tarball, and I got this while building the old concerto set: psql:assets_concerto.sql:58: ERROR: update or delete on table "record_entry" violates foreign key constraint "browse_entry_def_map_source_fkey" on table "browse_entry_def_map"
16:21	Bmagic	oops, Dyrcona's not here
16:27	Bmagic	enhanced concerto loaded ok though
16:27	Bmagic	not sure if that's "ok" but I've put the tarball on the web server (I think that the concerto issue isn't related to the tarball)

Results for 2023-12-12

15:10	mmorgan	No updates this month due to release business, but I'm fine with keeping it as an action item.
15:10	Dyrcona	#action mmorgan will explore moving LP stats to community site and automating same
15:10	Dyrcona	OK. Carrying it forward.
15:11	Dyrcona	#info sandbergja will investigate getting more tests into gh actions
15:11	sandbergja	bug 2044141 adds the OPAC js tests to run in github actions
15:11	pinesol	Launchpad bug 2044141 in Evergreen "Run OPAC javascript unit tests in github actions" [Undecided,New] https://launchpad.net/bugs/2044141
15:11	Dyrcona	Awesome sauce.
15:11	sandbergja	I'm interested in seeing if gh actions can run the pgtap tests next
15:12	Dyrcona	#info bug 2044141 adds the OPAC js tests to run in github actions
15:12	sandbergja	I'm okay keeping this item assigned to me
15:12	Dyrcona	I was just about to ask.
15:12	Dyrcona	#action sandbergja will see if gh actions can run the pgtap tests
15:13	Dyrcona	Ok. Unless anyone has anything else to say about previous action items, I'll move on to
15:13	Dyrcona	#topic OpenSRF Releases
15:13	Dyrcona	#info OpenSRF 3.2.4 and 3.3.0-beta released 2023-12-05
15:13		smayo joined #evergreen
15:14	Dyrcona	I would post a link to the email, but I think that got trickier recently.
15:14	JBoyer	I'm planning to take a look at the beta for some testing soon
15:15	Dyrcona	I've been using the main branch on most of my test systems so far, so I guess I'm using the beta now... I'll check and make sure.
15:16	Dyrcona	i added to the next topic before the meeting, so if you haven't yet, you might want to reload the agenda in your browser.
15:16	Dyrcona	#topic Evergreen Releases
15:16	Dyrcona	#info Evergreen 3.12 release candidate available 2023-12-06
16:08	Dyrcona	Two would be all of them, woudn't it?
16:08	JBoyer	I'm not sure voting will do much unless a "yes" vote is taken as volunteering to take part
16:09	JBoyer	and yes, it's just 3.10.4 and 3.11.2 tomorrow
16:09	Dyrcona	jeff: That's possible already. I've done it for test releases.
16:09	JBoyer	(or whenever)
16:09	jeff	Dyrcona: good! it's possible that no "ensuring" is needed.
16:09	Dyrcona	I'll volunteer to build and upload 3.10.whatever, if we can get other roles fileld.

Results for 2023-12-11

15:05		jvwoolf joined #evergreen
15:22		jvwoolf joined #evergreen
16:09		jvwoolf left #evergreen
16:20	Dyrcona	Sure. I'll just "steal" the CurlWrapper PHP class from Aspen, then make "simple" OSRFGatewayClient and EvergreenFieldmapper classes so I can write programs to test alternate back end calls for Aspen with PHP....Now, I'm thinking I need an OSRFRequest class, possibly an OSRFSession class, and more!
16:57		mmorgan1 left #evergreen
16:58		kmlussier joined #evergreen
18:48		jihpringle joined #evergreen