| Time |
Nick |
Message |
| 03:07 |
|
Jillianne2 joined #evergreen |
| 06:30 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 07:43 |
|
rlefaive joined #evergreen |
| 07:57 |
|
dwgreen joined #evergreen |
| 08:32 |
|
_adb joined #evergreen |
| 09:02 |
|
Dyrcona joined #evergreen |
| 09:40 |
|
jvwoolf joined #evergreen |
| 10:48 |
dbwells |
Intel hardware bug news popping up all over, looks pretty bad right now. 7-23% Postgresql performance regression in preliminary testing: https://www.postgresql.org/message-id/20180102222354.qikjmf7dvnjgbkxe@alap3.anarazel.de (will affect other services as well, but PG is certainly big for our community) :( |
| 10:48 |
csharp |
yep |
| 10:48 |
csharp |
been watching that closely |
| 10:49 |
csharp |
fortunately our DBs are running on AMD processors, but last time we ordered from Dell it was Intel-only and we're looking to replace them within the next year or so |
| 10:50 |
csharp |
all of our app servers (VM hosts) are Intel, though |
| 10:51 |
|
Christineb joined #evergreen |
| 10:53 |
dbwells |
csharp: I am curious, what AMD generation are you running? I didn't think AMD had anything competitive for anything other than special cases for the last 5 years or more (excluding the very recent EPYC stuff). |
| 10:54 |
csharp |
dbwells: AMD Opteron(tm) Processor 6380 |
| 10:57 |
csharp |
we did see that Dell is adding EPYC processors to the PowerEdge line: https://blog.dellemc.com/en-us/poweredge-servers-amd-epyc-processors/ |
| 10:57 |
csharp |
but that might not be immediately |
| 11:01 |
dbwells |
csharp: Thanks. Looks like the 6380 was release Nov. 2012, so that's less surprising, then. It's us with newer toys who will feel the burn. Guess you should be in a good position to upgrade right over this problem :) |
| 11:03 |
dbwells |
In the end, I am guessing it boils down to a 5-10% performance hit is real world typical usage, and we all just grumble and live with it. |
| 11:05 |
csharp |
yeah |
| 11:17 |
|
kmlussier joined #evergreen |
| 11:21 |
|
mmorgan joined #evergreen |
| 11:26 |
|
ejk joined #evergreen |
| 11:52 |
Bmagic |
I am troubleshooting an issue with both staff clients where checking in an item for transit doesn't prompt for a printed transit slip. The end of log is circulator: bailing out with events: ROUTE_ITEM |
| 11:57 |
phasefx |
Bmagic: migrated data or native transit? |
| 11:57 |
Bmagic |
native |
| 11:57 |
Bmagic |
the item was already in transit |
| 11:57 |
phasefx |
haven't seen that before |
| 11:57 |
Bmagic |
and presumably it prompted for the print the first time |
| 11:58 |
Bmagic |
this is new to us as well |
| 11:58 |
Bmagic |
version 3.0.2 |
| 12:17 |
|
khuckins joined #evergreen |
| 12:25 |
mmorgan |
Bmagic: Is this a single item or happening for all items already in transit? |
| 12:25 |
|
jihpringle joined #evergreen |
| 12:26 |
Bmagic |
mmorgan: multiple items but I am not sure it's "all" |
| 12:26 |
Bmagic |
good point though. I will try some at random |
| 12:27 |
* mmorgan |
tried checking in an already in transit item in 3.0.2 xul client, and got the pop-up and option to print |
| 12:29 |
Bmagic |
mmorgan: ok, just tried a different one and it prompted! Let me try one that has the same copy_status (8) |
| 12:49 |
Bmagic |
mmorgan: I wonder if it has to do with patrons perferring to have emailed receipts |
| 12:50 |
Bmagic |
I see some business related to that in the logs during checkin |
| 12:51 |
rjackson_isl |
before adding to the pile... anyone know if there is an existing ticket about column picker in copy buckets? It seems several columns not available. Also, the title is in lower case and has leading spaces? |
| 12:53 |
rjackson_isl |
I did searches for column picker and copy bucket but nothing looked like a match |
| 13:03 |
kmlussier |
rjackson_isl: I don't know off the top of my head, I've been adding a webstaffcolumns tag to LP bugs related to web client column pickers. It might be another way to search before filing a new one. |
| 13:03 |
rjackson_isl |
kmlussier++ I will give that a whirl |
| 14:08 |
csharp |
berick: (haven't seen you yet, so don't know if you're around, but) do you have plans to upload Hatch 0.1.3 to the chrome webstore? |
| 14:09 |
csharp |
we're working up installation instructions for our MLK weekend upgrade and wanted to be able to specify ;-) |
| 14:09 |
berick |
lemme check something.. |
| 14:11 |
berick |
csharp: there were no changes to the extension between 0.1.2 and 0.1.3. i was not planning to update it. |
| 14:11 |
berick |
i can though |
| 14:11 |
berick |
to avoid confusion |
| 14:13 |
csharp |
oh - okay |
| 14:13 |
csharp |
yeah, I think that would be a good idea |
| 14:13 |
berick |
k, no prob, i'll do it now. will take a few minutes to propagate |
| 14:14 |
csharp |
I was able to run 0.1.2 with the changes from the chromestore/nsis combined branch |
| 14:14 |
csharp |
berick++ # thanks! |
| 14:14 |
|
slink joined #evergreen |
| 14:16 |
berick |
csharp: done |
| 14:16 |
csharp |
berick: awesome - thank you! |
| 14:16 |
berick |
"Your item is in the process of being published and may take up to 60 minutes to appear in the Chrome Web Store. " |
| 14:35 |
|
slink-lib joined #evergreen |
| 14:39 |
slink-lib |
I'm having some Hatch issues - it works fine when installed under a local admin account, but not when on a domain admin account. When installed under local admin, domain accounts give a "native messenging host not found" error on the background page for the extension. |
| 14:41 |
slink-lib |
But if it's installed under a domain admin account, the user accounts get a "native messaging host disconnected" error. |
| 14:45 |
berick |
slink-lib: hm, windows is a bit of a mystery to me, but i might start running 'hatch.bat test' from the command prompt |
| 14:45 |
berick |
as the user that's having problems |
| 14:46 |
berick |
should be in Program Files (x32)/Hatch or similar |
| 14:46 |
berick |
it creates a log file too |
| 14:47 |
csharp |
slink-lib: FYI, we're updating our install notes for hatch as I type - should be up later today or tomorrow ;-) |
| 14:47 |
csharp |
but sounds like your problem is (probably) not related to the way it was installed |
| 14:47 |
slink-lib |
charp: Thanks! Maybe that'll help ;) |
| 14:48 |
berick |
may be possible there are permission issues with writing the log file too |
| 14:48 |
slink-lib |
berick: I've done that, and I'm not seeing an error in the log. |
| 14:48 |
berick |
slink-lib: and it prints a bunch of logs to the console? |
| 14:48 |
berick |
when you run the test |
| 14:48 |
slink-lib |
berick: Yes. Even gives a readout of all the printers in the logs. |
| 14:48 |
berick |
ok |
| 14:49 |
csharp |
oh - cool - the webstore version is now 0.1.3 |
| 14:49 |
|
rlefaive joined #evergreen |
| 15:17 |
kmlussier |
berick: I'll update the downloads page. |
| 15:18 |
berick |
kmlussier++ |
| 15:18 |
berick |
thanks |
| 15:18 |
berick |
wasn't sure if anyone would see that buried in the thread ;) |
| 15:30 |
|
khuckins joined #evergreen |
| 15:57 |
Dyrcona |
jboyer++ # Because Lp isn't IRC. :) |
| 16:04 |
|
rlefaive joined #evergreen |
| 16:12 |
kmlussier |
Dyrcona++ |
| 16:14 |
Dyrcona |
So, now firm dates have been provided for Evergreen 3.1 release cycle, or I'm looking in the wrong places? |
| 16:14 |
Dyrcona |
s/now/no/ |
| 16:14 |
|
sandbergja joined #evergreen |
| 16:14 |
Dyrcona |
Ah, never mind. Found dbwells' email to the general lit. |
| 16:15 |
Dyrcona |
s/lit/list/ |
| 16:15 |
* Dyrcona |
should do a more thorough search before asking things. :) |
| 16:17 |
Dyrcona |
dbwells++ |
| 16:25 |
jeff |
Dyrcona: if you hadn't asked, you probably wouldn't have found it. |
| 16:25 |
Dyrcona |
heh. |
| 16:48 |
|
khuckins_ joined #evergreen |
| 16:52 |
|
khuckins__ joined #evergreen |
| 17:00 |
|
mmorgan left #evergreen |
| 17:34 |
|
jvwoolf left #evergreen |
| 18:32 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 18:38 |
csharp |
so current Hatch lore is to only use for printing? or should we also be able to use the storage and offline settings? |
| 20:14 |
|
jeffdavis joined #evergreen |
| 20:30 |
|
eby joined #evergreen |
| 20:31 |
|
eby joined #evergreen |
| 23:47 |
|
Jillianne joined #evergreen |
