IRC log for #evergreen, 2022-02-21

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

Time	Nick	Message
06:01	pinesol	News from qatests: Failed Installing Evergreen database pre-requisites <http://testing.evergreen-ils.org/~live//archive/2022-02/2022-02-21_04:00:02/test.39.html>
07:15		rjackson_isl_hom joined #evergreen
07:34		collum joined #evergreen
08:24		rfrasur joined #evergreen
08:41	csharp_	Exception: Unsupported GitPython version. (why the git commit announcement plugin is failing)
08:41	csharp_	stupid upgrades
09:50	Bmagic	that one has been stinging me lately
10:14	csharp_	@git log
10:14	pinesol	csharp_: (git log <short name> [count]) -- Display the last commits on the named repository. [count] defaults to 1 if unspecified.
10:14	csharp_	@git log master 4
10:14	pinesol	csharp_: No configured repository named master.
10:14	csharp_	hmmm
10:16	csharp_	fd9a16d3f41
10:17	csharp_	still barfing
10:18	csharp_	raise BadName(name)
10:18	csharp_	@who gives love a BadName(name)
10:18	pinesol	dluch gives love a BadName(name.
10:19	csharp_	I think this is a Git API issue
10:19	csharp_	apparently running a nearly 10-year-old plugin with no updates in the past 8 years doesn't always work
10:20	jeff	The most recent commit announcement in #evergreen-feeds seems to have taken place yesterday, which would be after the upgrade of lupin, right?
10:21	csharp_	yes, actually
10:21	csharp_	hmm
10:21	jeff	do we want them announced here also?
10:21	csharp_	yes
10:22	jeff	@announce add commits
10:22	pinesol	jeff: The operation succeeded.
10:22	jeff	@announce list
10:22	pinesol	jeff: commits and qatests
10:22	csharp_	huh
10:22	csharp_	well, the Git supybot plugin is very out of date, looks like
10:23	jeff	however...
10:23	csharp_	so the hash snarfing we're normally able to do won't work until that's fixed
10:23	jeff	@latestbugs
10:23	pinesol	jeff: 01:25 PM, February 21, 2022: [1961593] Postgresql 9.6 should be removed from installation scripts <https://bugs.launchpad.net/bugs/1961593>
10:23	jeff	@qatests
10:23	pinesol	jeff: 10:23 AM, February 21, 2022: Failed Installing Evergreen database pre-requisites <http://testing.evergreen-ils.org/~live//archive/2022-02/2022-02-21_04:00:02/test.39.html>
10:23	jeff	@commits
10:23	pinesol	jeff: Error: Couldn't get RSS feed.
10:23	jeff	so, something's still not quite right.
10:23	jeff	but it was working yesterday.
10:26	csharp_	@rss announce list
10:26	pinesol	csharp_: commits and qatests
10:26	csharp_	so @announce is an alias to @rss announce?
10:27	jeff	less of an alias, more of a "if nothing else claims it, there's no disambiguation required"
10:27	jeff	looks like the feed URL for commits is http://git.evergreen-ils.org/?p=Evergreen.git;a=atom
10:29	jeff	not sure if something changed between Sunday and now.
10:37	rfrasur	Hello. I come to you once again, asking for information. Where is the collection referral fee located? I've looked in library settings and action/triggers and have found nothing. Which means nothing.
10:38	jeff	rfrasur: it's passed by the entity making the call to place the user into collections.
10:41	rfrasur	the entity being the org unit? and where is it set/stored?
10:41	jeff	The open-ils.collections.put_into_collections method accepts arguments that include the user ID to be placed into collections, the library location where they are being placed into collections, and a fee amount and a fee note. If there's no fee_amount, no fee is added.
10:41	jeff	Not the org unit -- the collection agency making the API calls to place users into collections.
10:42	rfrasur	okay, that makes sense.
10:42	jeff	I wouldn't go that far, but... :-)
10:42	rfrasur	Well, it kind of makes some sense.
10:50	csharp_	rfrasur: I believe UMS adds that from their end
10:51	csharp_	they connect to Evergreen via an XML-RPC gateway, query the system for users who meet the criteria for putting in collections, and add them to collections
10:54	rfrasur	Right. I'm just wondering how then that fee gets passed back to Evergreen and is applied as a bill. More so how that patron gets charged. And I get that it's running through an API with mechanisms. But how is it, that when they charge $8.99 (arbitrary price) per referral fee, the patron gets billed $10. I'm asking because they're increasing their prices to $11ish, and that fee passed on to patrons needs to be $12.
10:55	rfrasur	(in EI's case)
11:13	csharp_	rfrasur: uhhh, I don't know - I would reach out to UMS - they are always responsive and helpful in our experience
11:14	jeff	Sorry, I thought that's what I was trying to say. I guess I'm unclear this morning. :-)
11:15	rfrasur	No worries. That's what you were saying. It was just very concise for my less than competent brain.
11:15	jeff	The company that you work with to place patrons into collections sends the fine amount to your Evergreen system. If you want to change the amount, you ask the company to change the amount.
11:15	rfrasur	csharp_++
11:15	rfrasur	jeff++
11:16	jeff	If the company mistakenly uses the wrong amount, in my past experience it's easiest/best to make corrections yourself.
11:16	csharp_	yeah, I've been through that
11:17	jeff	If you want to retroactively increase/decrease the amount billed to patrons that are already in collections, same: best in my experience to make those changes yourself. I wouldn't recommend increasing the fine retroactively, for purely non-technical reasons.
11:56	rfrasur	Okay, we don't want to do anything with any of it.
12:32		collum joined #evergreen
18:01	pinesol	News from qatests: Failed Installing Evergreen database pre-requisites <http://testing.evergreen-ils.org/~live//archive/2022-02/2022-02-21_16:00:02/test.39.html>
20:33		Weston joined #evergreen
20:34	Weston	Hello
21:03		Weston40 joined #evergreen
21:05		Weston12 joined #evergreen
21:21		Weston joined #evergreen