| Time |
Nick |
Message |
| 07:50 |
|
BDorsey joined #evergreen |
| 07:55 |
|
kworstell-isl joined #evergreen |
| 08:01 |
|
rfrasur joined #evergreen |
| 08:10 |
|
collum joined #evergreen |
| 08:26 |
|
mantis1 joined #evergreen |
| 08:35 |
|
mmorgan joined #evergreen |
| 08:52 |
|
dguarrac joined #evergreen |
| 09:01 |
|
jvwoolf joined #evergreen |
| 09:28 |
JBoyer |
So, anyone else having trouble building Evergreen because the socks-proxy-agent module is blowing up npm? (Asking in case it's just something I've busted on my end) |
| 09:35 |
* miker |
whispers "elll paaaadddddd" from the darkness |
| 09:44 |
|
rfrasur joined #evergreen |
| 10:00 |
|
sleary joined #evergreen |
| 10:23 |
JBoyer |
Well, this is starting to look more like some garbage from switching back and forth between node versions (install master here, rel_3_7 there, bounce around for fun, etc.) |
| 10:28 |
csharp_ |
npm-- |
| 11:35 |
|
mantis1 joined #evergreen |
| 12:11 |
|
jihpringle joined #evergreen |
| 12:30 |
JBoyer |
followup: looks like it was the version swapping thing. |
| 13:27 |
jvwoolf |
If doing a browse only reingest, do I just use the options --skip-search --skip-facets --skip-display? |
| 13:28 |
jvwoolf |
batch-size does nothing because it doesn't parallelize, right? What about --max-child? |
| 13:41 |
|
jihpringle joined #evergreen |
| 13:45 |
|
mantis1 joined #evergreen |
| 13:58 |
JBoyer |
jvwoolf, I think max-child is how parallel it can be, so you can ignore it if doing browse only |
| 13:59 |
JBoyer |
Each child will do batch-size number of records before it's replaced with a new child process |
| 14:08 |
jvwoolf |
JBoyer++ |
| 14:41 |
pinesol |
News from commits: LP1422927 Opac hold history pagination <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=c70bde9b34bf0f844c6fa6c8d0d5878dfcd43baf> |
| 15:25 |
|
Dyrcona joined #evergreen |
| 15:42 |
|
jvwoolf left #evergreen |
| 15:44 |
* Dyrcona |
isn't here. |
| 16:04 |
|
sleary joined #evergreen |
| 17:03 |
|
mmorgan left #evergreen |
