| Time |
Nick |
Message |
| 07:13 |
|
kworstell-isl joined #evergreen |
| 07:21 |
|
collum joined #evergreen |
| 07:32 |
* csharp_ |
does battle with Chinese bots |
| 07:33 |
csharp_ |
they finely dice IP subnets so blocking ranges is difficult and time consuming |
| 07:33 |
csharp_ |
(this morning's arena is the git server) |
| 08:12 |
|
BDorsey joined #evergreen |
| 08:45 |
|
mmorgan joined #evergreen |
| 09:11 |
|
dguarrac joined #evergreen |
| 10:27 |
berick |
may do a light weekened rust terminal UI project w/ https://ratatui.rs/ -- wonder if there any EG tasks that would be generally useful to perform via terminal ui |
| 10:49 |
|
Christineb joined #evergreen |
| 10:52 |
csharp_ |
berick: looking at SIP2Mediator finally - do you run that on dedicated SIP2 EG app servers or do you run that alongside your app bricks? |
| 10:53 |
csharp_ |
we typically don't have HTTP running on our sip servers, for context for my question |
| 10:56 |
|
sandbergja joined #evergreen |
| 10:56 |
berick |
csharp_: it's complicated... we're in the process of migrating to a Rust port of the mediator and sip service. the mediator and sip service run on dedicated SIP servers (for now, anyway). the sip service also runs on the main bricks since it's neeed for the admin UI. |
| 10:56 |
csharp_ |
got it |
| 10:57 |
berick |
i may eventually run the mediator on the main bricks so we don't need dedicated SIP servers. we'll see. |
| 10:57 |
csharp_ |
that's what I was pondering |
| 10:57 |
csharp_ |
I guess for now I'll just have apache running and just connect to the default localhost setup |
| 10:58 |
csharp_ |
so many new shiny things since 3.12! |
| 10:59 |
csharp_ |
redis and sip2-mediator and reports oh my! |
| 11:00 |
csharp_ |
"wellsir..." <slaps the roof of EG 3.12> "this Evergreen version has served us very well" |
| 11:01 |
berick |
and we (kcls) have moved on a bit from the stock EG mediator code, which would put you on the bleeding edge csharp_ fyi |
| 11:02 |
csharp_ |
I'll keep SIPServer around to crank up if needed |
| 11:03 |
csharp_ |
also, willing to test bleeding edge at this stage of our upgrade (targeted for mid February) |
| 11:07 |
berick |
in particular, the rust variant forgoes HTTP communication, a key facet of the original design, and ops for a more evergreen-centric opensrf client approach (i.e. direct redis communication). in the end, it's just more efficient and in some ways more practical. |
| 11:12 |
berick |
that is to say, though the http approach has its own benefits, there are no examples of it in use in the wild. |
| 11:12 |
berick |
that i'm aware of |
| 11:27 |
Bmagic |
csharp_: I feel your pain on the bot battle |
| 11:34 |
|
Dyrcona joined #evergreen |
| 11:37 |
mmorgan |
berick: jeff: Looking at bug 2076921. jeff's testing looks favorable, any reason not to roll it out? Our pc support tech is seeing changes being rolled out that disable the current extension. |
| 11:37 |
pinesol |
Launchpad bug 2076921 in Evergreen "Hatch: Chrome Extension Requires Redevelopment" [High,Confirmed] https://launchpad.net/bugs/2076921 - Assigned to Jeff Godin (jgodin) |
| 11:40 |
berick |
mmorgan: i see no reason to delay any longer |
| 11:41 |
|
sandbergja joined #evergreen |
| 11:41 |
berick |
in theory, it can be deployed to a percentage of the user base, but those knobs/buttons don't appear in the UI, at least not as documented. |
| 11:41 |
berick |
it's possible those options appear later in the deployement process or the docs i'm looking at are out of date |
| 11:41 |
berick |
either way, it may end up being deployed to everyone if those knobs aren't avaiable.. just fair warning |
| 11:42 |
berick |
we can revert it if necessary, though |
| 11:42 |
berick |
i would like to doublecheck that someone else can successfully login to the extension admin UI, though |
| 11:44 |
berick |
this probably warrants a message to the list... |
| 11:45 |
mmorgan |
berick++ |
| 11:56 |
|
sandbergja joined #evergreen |
| 12:00 |
|
jihpringle joined #evergreen |
| 13:01 |
sandbergja |
gmcharlt++ # thanks for taking a look at bug 2089795 and sharing the C knowledge! |
| 13:01 |
pinesol |
Launchpad bug 2089795 in Evergreen "Use after free in _oilsEventParseEvents" [Low,Confirmed] https://launchpad.net/bugs/2089795 |
| 13:02 |
|
mantis joined #evergreen |
| 13:34 |
|
kworstell_isl joined #evergreen |
| 13:58 |
|
sandbergja joined #evergreen |
| 13:59 |
Dyrcona |
Are we doing the collaborative code review today? |
| 13:59 |
Bmagic |
yep |
| 13:59 |
sandbergja |
Dyrcona: yup |
| 13:59 |
Dyrcona |
Be there in a moment. |
| 14:48 |
pinesol |
News from commits: LP#2089390: renormalize line endings per the new .gitattributes <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=eda808bfdf1ace6faf2fd74b588b0355a06a96e0> |
| 14:48 |
pinesol |
News from commits: LP#2089390: Add .gitattributes for consistent line endings <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=6a38e8e10661bfd10e94d6f44fc3303ead2c0ab9> |
| 16:48 |
pinesol |
News from commits: LP#2077443: Show template documenation in report list <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=63035ab5ee5a428198683cb316b229e3faab36bf> |
| 16:48 |
pinesol |
News from commits: LP2077443: Use Documentation URL When Schedulling Reports <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=67f97c08337b023c48dba26505f8a408363bc0b0> |
| 17:00 |
|
mmorgan left #evergreen |
| 17:41 |
|
jihpringle joined #evergreen |
| 18:21 |
|
jonadab joined #evergreen |
