| Time |
Nick |
Message |
| 00:11 |
abneiman |
release notes here (in main, not backported): https://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=713820677305189a00151229f424841e01c81dea |
| 00:37 |
pinesol |
News from commits: Docs: Release notes for 3.11.5 and 3.12.3 <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=713820677305189a00151229f424841e01c81dea> |
| 07:18 |
|
kworstell-isl joined #evergreen |
| 07:39 |
|
collum joined #evergreen |
| 07:48 |
|
redavis joined #evergreen |
| 08:00 |
csharp__ |
@eightball is LP down? |
| 08:00 |
pinesol |
csharp__: Maybe... |
| 08:14 |
|
kworstell_isl joined #evergreen |
| 08:39 |
Rogan |
loading for me right now but no idea about earlier |
| 08:47 |
|
mmorgan joined #evergreen |
| 09:01 |
|
mmorgan1 joined #evergreen |
| 09:06 |
|
Dyrcona joined #evergreen |
| 09:25 |
csharp__ |
redis-- |
| 09:25 |
csharp__ |
huh - why do I have an extra tail? |
| 09:27 |
|
csharp_ joined #evergreen |
| 09:47 |
|
dguarrac joined #evergreen |
| 10:04 |
Rogan |
there's an evolution joke to make there but my pollen filled head can't think of it |
| 10:25 |
Dyrcona |
I'm getting the "something went wrong" page from Launchpad today. They must not have patched xz-utils.... :) |
| 10:26 |
csharp_ |
Rogan: prehensile something something |
| 10:26 |
* Dyrcona |
was gonna make a crack like "Appendix to the appendix" |
| 10:27 |
Dyrcona |
"Technically, this is a 503 error and has been caused by our database having temporary operational issues." |
| 10:27 |
csharp_ |
the xz thing feels like an espionage op |
| 10:28 |
Dyrcona |
I'm sure it was have you read this: https://boehs.org/node/everything-i-know-about-the-xz-backdoor |
| 10:28 |
csharp_ |
per https://ubuntu.social/@launchpadstatus, LP was having hardware trouble last week or so |
| 10:28 |
Dyrcona |
csharp_++ |
| 10:28 |
Dyrcona |
I was kidding about the xz-utils. Ubuntu wasn't affected. |
| 10:29 |
csharp_ |
right |
| 10:30 |
csharp_ |
I did happen to upgrade to Fedora 40 over the weekend :-) |
| 10:30 |
csharp_ |
(on my personal machine) |
| 10:31 |
Dyrcona |
I apparently had the bad code on my personal laptop for a couple of days before Arch patched it. |
| 10:31 |
Bmagic |
Fedora 40! Did it ship with Plasma 6? |
| 10:32 |
csharp_ |
Bmagic: I use GNOME, so I don't know |
| 10:32 |
Bmagic |
:) gotcha |
| 10:32 |
Dyrcona |
Thom Holwerda's editorial is also worth reading for people who don't maintain OSS code: https://www.osnews.com/story/139070/open-source-is-about-more-than-just-code/ |
| 10:32 |
csharp_ |
I keep meaning to try and use KDE again, but I'm old and feeble now and don't like change |
| 10:32 |
* csharp_ |
shakes cane |
| 10:32 |
Bmagic |
reminds me of this https://www.youtube.com/watch?v=YVI6SCtVu4c&t=398s |
| 10:33 |
|
sandbergja joined #evergreen |
| 10:33 |
Bmagic |
I like how she pronounces gnome: guh-nome |
| 10:33 |
Dyrcona |
csharp_++ I keep KDE on one laptop that I pull it out and use for a few hours every few weeks, just to run updates. I keep it around as a spare mostly. |
| 10:35 |
Dyrcona |
Bmagic: I think that's how it is supposed be pronounced: guh-nome.... like guh-nu.... |
| 10:36 |
* berick |
was about to say |
| 10:36 |
Bmagic |
even better |
| 10:36 |
csharp_ |
in practice I usually say "nome" because I don't want to have to explain all the things when talking to people unfamiliar with the history (sorry, rms) |
| 10:37 |
csharp_ |
"ACK-tually, it's GNU/Linux because Linux is just the kernel..." - I know, I know |
| 10:37 |
Dyrcona |
Yeah, what csharp_ just said, same gnu, I usually say 'nu.' I also don't usually say "'nu/linux" either. |
| 10:37 |
Dyrcona |
Ha! |
| 10:38 |
csharp_ |
great minds |
| 10:54 |
|
kworstell-isl joined #evergreen |
| 12:49 |
|
adam_reid joined #evergreen |
| 12:53 |
adam_reid |
hey all! if I make a bulk change to asset.copy status value in the database of evergreen are there any scripts I should run to update the search in the OPAC, or will build in triggers take care of any necessary updates? |
| 13:05 |
Dyrcona |
adam_reid: Triggers should take care of everything if all you do is update the copy.status. |
| 13:05 |
adam_reid |
yep, that was the only column, thanks as always Dyrcona! |
| 13:20 |
|
adam_reid joined #evergreen |
| 14:07 |
|
kworstell_isl joined #evergreen |
| 15:00 |
csharp_ |
Bmagic: not a browser, but you might want to check out https://github.com/Swordfish90/cool-retro-term on your Fedora box |
| 15:09 |
pinesol |
News from commits: LP1086550 Not clear to patron how to deselect a facet <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=ae4ac1d2fc10a1cbfdd4a3453731ac11d4dc451f> |
| 15:23 |
Bmagic |
csharp_++ # I've not installed that on my terminal, but I'm aware of it! It's soooo friggin cool |
| 15:39 |
pinesol |
News from commits: LP1821094: Add an AngularJS module that runs promises in batches <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=b4c8c29a24556d81dade49d797cfb2bbdbb1db90> |
| 15:39 |
pinesol |
News from commits: LP1821094: Improve item status reload performance <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=c1ea5dcb50ce27070958962822f8df3e5adc5c9f> |
| 16:03 |
|
csharp_ joined #evergreen |
| 16:06 |
jmurray-isl |
Anyone know of something beyond max_stanza_size that would cause ejabberd to drop its connection? Despite having a max_stanza_size of 20000000 on our utility server, we had an issue today where a message of 12500000 continually broke ejabberd. |
| 16:08 |
csharp_ |
jmurray-isl: we're struggling with the same problem |
| 16:10 |
csharp_ |
jmurray-isl: if you limit max_stanza_size to something reasonable, it will kill that drone - I've found that too-high (or no) max_stanza_size kills the router completely |
| 16:10 |
jmurray-isl |
Good to know |
| 16:10 |
csharp_ |
OpenSRF knows it's coming too - the WARN logs will say something like "large message" (the threshold for which is set in opensrf.xml, I think) |
| 16:11 |
jmurray-isl |
Yep. That's how I confirmed the issue. |
| 16:11 |
csharp_ |
I would love if OpenSRF would just, you know, not just commit suicide and use the large message detection to not try and deliver it |
| 16:12 |
csharp_ |
jmurray-isl: the other thing I'm planning to look at this week is trying to prevent A/T from creating the massive messages in the first place |
| 16:12 |
jmurray-isl |
That would be nice... |
| 16:13 |
csharp_ |
I assume it's pulling fully-fleshed circ and bib data and trying to gulp it all down at once |
| 16:14 |
jmurray-isl |
We build XML templates that can be pretty large for Print Templates (which is what this was), so we might need the option to send large messages. |
| 16:14 |
csharp_ |
ah |
| 16:14 |
jmurray-isl |
We generate daily PDFs using fop from the XML templates. |
| 16:15 |
csharp_ |
in our case it's 3-day reminder notices - we have a 50-item circ limit so gathering all those circs is probably what's killing us |
| 16:15 |
csharp_ |
(even though the template for reminders only displays the first 10 or so) |
| 16:24 |
Bmagic |
abneiman: we good for building? |
| 16:28 |
abneiman |
Bmagic: AFAIK, yes; though anything merged after last night will need an amended release note |
| 16:28 |
Bmagic |
oh right, we just merged three things onto main |
| 16:28 |
abneiman |
I'm not available this afternoon unfortunately though I can still do LP updates & announcements tomorrow or Weds |
| 16:29 |
abneiman |
I'll be on the road though so IRC will be hit or miss, if you really need to get my attention email is best |
| 16:30 |
Bmagic |
git log |
| 16:30 |
Bmagic |
wrong window :) |
| 16:45 |
sandbergja |
Bmagic: if you want, I can backport the release notes and add entries for the newly committed bits |
| 16:45 |
Bmagic |
sandbergja++ # yes please |
| 16:45 |
Bmagic |
I was just scratching my head over that |
| 16:53 |
sandbergja |
Bmagic: pushed |
| 16:54 |
Bmagic |
ok then! I'll build 3.11.5 |
| 16:54 |
sandbergja |
woohoo! |
| 16:54 |
sandbergja |
And I will start building 3.12.3 in a bit |
| 17:04 |
|
mmorgan1 left #evergreen |
| 17:09 |
pinesol |
News from commits: Additional entry for release notes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=8989919f9821826870d11c7c1835b7fbb2c7fd96> |
| 17:20 |
sandbergja |
I upgraded to podman 5, and that apparently deleted the vm that all the podman containers run on. So, rebuilding my container image. To be continued... |
| 17:46 |
sandbergja |
Bmagic++ # the README on https://github.com/mcoia/eg-docker has the answers for everything |
| 17:52 |
Bmagic |
sandbergja++ |
| 19:42 |
sandbergja |
Tarball and other build artifacts for 3.12.3 at https://drive.google.com/drive/folders/1eQA1eY9HJCXt_0GLARR6Anx5qlcMaSFD?usp=sharing |
| 19:43 |
sandbergja |
I'm running the tests now, pgtap looks happy! |
| 19:49 |
sandbergja |
so do c tests, perl live, perl unit, angularjs unit, angular unit, and opac tests |
| 19:49 |
sandbergja |
So, I think 3.12.3 is built and tested |
| 20:10 |
pinesol |
News from commits: Forward-port 3.12.2-3.12.3 upgrade script <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=a67de67b5d5981e74d076dd8f5e1987f39c1079f> |
| 20:36 |
|
Guest20 joined #evergreen |
| 21:05 |
Bmagic |
sandbergja++ # I downloaded your tarball and accomanied files and posted them onto the webserver's hard drive. Though, not linked onto the downloads page. abneiman was signed up to do that portion |
| 21:15 |
Bmagic |
Mine are there too: in other words, 3.11.5 and 3.12.3 are done and staged onto the web server |
| 21:24 |
Bmagic |
I think I will need a hand pushing to the non-working Evergreen repo. I attempted to push a new tags branch but w as met with some erro messages. I updated my push remote url but still didn't overcome. So, I've pushed my tags branch to the working repo: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/blake/tags/rel_3_11_5 |
