| Time |
Nick |
Message |
| 00:03 |
|
sandbergja joined #evergreen |
| 00:22 |
|
eady joined #evergreen |
| 00:27 |
|
eady joined #evergreen |
| 00:29 |
|
sandbergja joined #evergreen |
| 01:54 |
|
Lenin joined #evergreen |
| 07:15 |
|
rjackson_isl joined #evergreen |
| 07:49 |
|
sandbergja joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 08:58 |
mmorgan |
@coffee [someone] |
| 08:58 |
* pinesol |
brews and pours a cup of Ibonia Kenya Peaberry, and sends it sliding down the bar to gsams_ |
| 08:58 |
mmorgan |
@tea [someone] |
| 08:58 |
* pinesol |
brews and pours a pot of Holy Basil Purple Leaf, and sends it sliding down the bar to jonadab (http://ratetea.com/tea/upton/holy-basil-purple-leaf-organic/1937/) |
| 08:58 |
mmorgan |
@dessert [someone] |
| 08:58 |
* pinesol |
grabs some Carrot Cake for troy__ |
| 09:00 |
mmorgan |
Lazy troubleshooting question - is there anywhere in the web client that reveals the id of the registered workstation that is currently in use? |
| 09:12 |
|
yboston joined #evergreen |
| 09:32 |
|
jvwoolf joined #evergreen |
| 09:36 |
|
tlittle joined #evergreen |
| 09:48 |
alynn26 |
mmorgan: not that I am aware of. |
| 09:50 |
|
Dyrcona joined #evergreen |
| 09:50 |
mmorgan |
Ok, thanks for confirming. |
| 09:50 |
alynn26 |
I do have a report that gives me that information. |
| 09:54 |
* mmorgan |
can get it from the database, but it would be handy to see it somewhere in the client, like the patron id that pops up when you hover over the name. When you hover over the workstation name, the authkey pops up. |
| 10:03 |
|
Christineb joined #evergreen |
| 10:37 |
|
sandbergja joined #evergreen |
| 10:52 |
csharp |
TFW when 'git rebase -i' has conflicts on 8 of the first 9 commits with 80 to go |
| 10:53 |
berick |
@coffee csharp |
| 10:53 |
* pinesol |
brews and pours a cup of Guatemala El Diamante, and sends it sliding down the bar to csharp |
| 10:58 |
csharp |
berick++ |
| 10:59 |
csharp |
fortunately, just after complaining about that, the rebase chewed through the last 75 or so with no issues |
| 10:59 |
csharp |
so next time, I'll just kvetch here first and save two hours |
| 10:59 |
berick |
heh |
| 11:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 11:03 |
phasefx |
berick: when you have a moment, I want to pick your brain on certain action dialogs for the eg2 holds grid. For example, retarget-dialog.component.html, where it says {{numSucceeded}} Hold(s) Successfully Retargeted. Is that meant to summarize the results of previous invocations of the action? |
| 11:11 |
berick |
phasefx: looking... |
| 11:11 |
phasefx |
berick++ |
| 11:14 |
berick |
phasefx: i think the idea there was to provide feedback to the user in the case of large batches of retargets. numSucceeded would increase with each hold retargeted. |
| 11:14 |
berick |
in practice, though, with small batches, you never see that message |
| 11:14 |
berick |
cuz the dialog almost immediately closes |
| 11:16 |
phasefx |
berick: ah, so for a large batch, the dialog is supposed to stay open and that would get updated continously before the dialog closed itself? What I'm seeing with small batches is that the previous outcome gets shown immediately |
| 11:16 |
phasefx |
previous outcome from previous invocation of the action |
| 11:16 |
berick |
phasefx: exactly. |
| 11:16 |
berick |
phasefx: oooh.. |
| 11:17 |
berick |
ok, that needs a fix. this.numSucceeded should be reset in the open() function as well |
| 11:17 |
berick |
an oversight |
| 11:17 |
phasefx |
berick++ I'll bundle it with what I'm doing |
| 11:17 |
berick |
phasefx++ |
| 11:17 |
phasefx |
thanks man |
| 12:06 |
|
jihpringle joined #evergreen |
| 12:08 |
dbs |
In today's random performance test, how long does it take to navigate to page 7000 of a results list? Answer: gateway timeout :) |
| 12:11 |
|
sandbergja joined #evergreen |
| 12:15 |
dbs |
Looks like I can page forward about 250 pages w/10 results per page at a time. If I try to skip forward 500 pages, I get a timeout. Interesting |
| 13:22 |
|
sandbergja joined #evergreen |
| 13:31 |
|
sandbergja joined #evergreen |
| 13:43 |
|
Ryan_McG joined #evergreen |
| 13:43 |
Ryan_McG |
Anyone monitoring currently? |
| 13:43 |
Ryan_McG |
I have a question! |
| 13:50 |
dbs |
@later tell RyanMcG you can always ask a question and watch the IRC logs to see if anyone answers it over the course of the day |
| 13:50 |
pinesol |
dbs: The operation succeeded. |
| 15:26 |
|
sandbergja joined #evergreen |
| 15:49 |
Bmagic |
I suppose some IRC channels are a bit more responsive (less than three minutes which is all he gave it) |
| 16:16 |
|
jvwoolf left #evergreen |
| 16:24 |
|
yboston joined #evergreen |
| 16:28 |
|
sandbergja joined #evergreen |
| 17:04 |
|
sandbergja joined #evergreen |
| 17:08 |
|
mmorgan left #evergreen |
| 18:36 |
|
sandbergja joined #evergreen |
| 18:46 |
|
sandbergja joined #evergreen |
| 20:24 |
|
sandbergja joined #evergreen |
| 20:37 |
|
sandbergja joined #evergreen |
| 21:01 |
|
sandbergja joined #evergreen |
| 23:02 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 23:36 |
|
sandbergja joined #evergreen |
