| Time |
Nick |
Message |
| 00:30 |
|
Keith_isl joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:09 |
JBoyer |
I guess that's finally the end of #evergreen on Freenode. As of ~ 1am it now requires TLS and SASL (good) with their relatively new nickserv database (bad). |
| 07:09 |
JBoyer |
csharp_++ # less + v is a good tip! |
| 07:12 |
|
rjackson_isl_hom joined #evergreen |
| 08:31 |
|
rfrasur joined #evergreen |
| 08:31 |
|
Dyrcona joined #evergreen |
| 08:32 |
|
mmorgan joined #evergreen |
| 08:34 |
|
mantis joined #evergreen |
| 09:10 |
|
jvwoolf joined #evergreen |
| 11:06 |
|
mmorgan1 joined #evergreen |
| 11:10 |
Bmagic |
Dyrcona (or anyone) - what's a "better" max_stanza_size for bug 1858471 ? |
| 11:10 |
pinesol |
Launchpad bug 1858471 in Evergreen "Events with large amount of data can crash action_trigger_runner.pl" [Undecided,New] https://launchpad.net/bugs/1858471 |
| 11:16 |
Dyrcona |
Bmagic: I'm using 10MB on my utility server that runs action triggers, 10485760. |
| 11:16 |
Dyrcona |
I use 2MB everywhere else. |
| 11:17 |
Bmagic |
I've got: 2000000 |
| 11:17 |
Bmagic |
but I like yours better :) |
| 11:17 |
Dyrcona |
:) |
| 11:17 |
Bmagic |
why not set it like that for all app servers? |
| 11:17 |
Dyrcona |
I found some email notices with lots of copies/titles would fail, so I bumped it to 10 million. |
| 11:18 |
Dyrcona |
They didn't seem to need it. |
| 11:18 |
Bmagic |
right, but could it hurt? |
| 11:18 |
Bmagic |
just curious |
| 11:19 |
Dyrcona |
It could make some things slower if you do exceed the 2 million limit, but those would have failed, so..... |
| 11:19 |
Dyrcona |
It probably wouldn't hurt, but I didn't change it everywhere because it didn't seem to be necessary. |
| 11:19 |
berick |
2MB everywhere here |
| 11:20 |
Dyrcona |
I *think* I went to 4MB on the utility server, first, and still had this one user whose auto-renewal notice blew up, so then I went to 10MB. |
| 11:21 |
Dyrcona |
There should be some chatter in IRC logs from January of 2019 or 2020 about it. |
| 11:21 |
Bmagic |
right, that's what led me to the bug |
| 11:22 |
Bmagic |
Perhaps our official install procedure should recommend this setting for ejabberd? |
| 11:22 |
Bmagic |
grepping IRC to find that our documentation is lacking.... |
| 11:23 |
Dyrcona |
It used to recommend setting it to 2 million, then chunking and bundling was added and the instruction was removed. (TBH, I think I had something to do with that whether I did it or just signed off.) |
| 11:24 |
Dyrcona |
The trouble with max stanza size is the necessary value can vary by circumstances, so some places might get by with a lower setting. |
| 11:25 |
Dyrcona |
And, we might be fine with a certain value, except that one "lost" card or whatever with 1,000 items checked out to it. |
| 11:42 |
|
jihpringle joined #evergreen |
| 12:02 |
|
Christineb joined #evergreen |
| 12:32 |
|
rjackson_isl_hom joined #evergreen |
| 14:13 |
|
rlefaive joined #evergreen |
| 14:17 |
rlefaive |
Hello! Does anyone know how to safely kill a Vandelay session? I got ambitious, and started an ingest using marc_stream_importer.pl. But it didn’t complete (maybe because I didn’t use screen?) and a session in vandelay.session_tracker is still open with no progress, after a few days. The queue is acting frozen.Any help is appreciated! |
| 14:26 |
|
jvwoolf joined #evergreen |
| 14:28 |
mmorgan1 |
rlefaive: The session tracker is a database table, vandelay.session_tracker, that gets updated as the session progresses. We've had situations where something bad happened to the vandelay process and we've had to manually update a session to remove it from the display. |
| 14:51 |
rlefaive |
thanks mmorgan! |
| 14:54 |
|
mantis1 joined #evergreen |
| 15:23 |
miker |
Dyrcona/Bmagic: re stanza size and chunking, the modern problem is method param size. I have a WIP for perl and c that should chunk params they /send/ when too big, and Perl def knows how to receive chunked params, but I got badly stuck with teaching js to send chunked params... that's still an issue because of copy and print templates, iirc, but a/t should theoretically be happy with that branch |
| 15:24 |
miker |
the js is just abstracted in a very different way from the perl, and I couldn't see how to do it in the existing code |
| 15:25 |
Dyrcona |
miker++ |
| 15:25 |
miker |
without it becoming a sign ball of spaghetti |
| 15:25 |
Dyrcona |
Lasagna, but all we have is spaghetti.... |
| 15:27 |
miker |
if anyone's interested in picking it up to coauthor, I'm happy to push it out for more brains to attack |
| 15:27 |
miker |
I don't have tuits for it ATM, but really want it to happen |
| 15:28 |
Dyrcona |
Yeah. There has been a long term shortage of tuits. |
| 15:30 |
Dyrcona |
I'll take a look at the rebased branch next week. I can't promise that I can do anything with the JavaScript. I'm going to be busy testing Quipu integration. |
| 15:48 |
|
miker joined #evergreen |
| 16:06 |
|
nfBurton joined #evergreen |
| 16:26 |
|
mmorgan1 joined #evergreen |
| 16:35 |
|
jvwoolf left #evergreen |
| 16:44 |
|
brettgilio left #evergreen |
| 17:08 |
|
mmorgan left #evergreen |
| 17:26 |
|
rlefaive joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 20:45 |
|
rlefaive joined #evergreen |
