| Time |
Nick |
Message |
| 04:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:37 |
|
rlefaive joined #evergreen |
| 05:46 |
|
rlefaive joined #evergreen |
| 06:52 |
|
rlefaive joined #evergreen |
| 07:09 |
|
rjackson_isl joined #evergreen |
| 07:32 |
|
agoben joined #evergreen |
| 08:39 |
|
sard_ joined #evergreen |
| 08:39 |
|
kipd_ joined #evergreen |
| 08:39 |
|
gsams joined #evergreen |
| 08:40 |
|
abneiman_ joined #evergreen |
| 08:42 |
|
gmcharlt joined #evergreen |
| 08:42 |
|
dbs joined #evergreen |
| 08:44 |
|
mmorgan joined #evergreen |
| 08:45 |
|
pastebot joined #evergreen |
| 08:46 |
|
Dyrcona joined #evergreen |
| 08:50 |
|
bos20k joined #evergreen |
| 08:53 |
|
kmlussier joined #evergreen |
| 08:53 |
|
_adb joined #evergreen |
| 08:58 |
|
dbwells joined #evergreen |
| 08:59 |
|
yboston joined #evergreen |
| 09:26 |
Dyrcona |
heh. I keep typing 0ff instead of off... |
| 09:26 |
* Dyrcona |
is working on a postgresql config for optimized restore speed. |
| 10:02 |
|
mmorgan1 joined #evergreen |
| 10:21 |
csharp |
@band add Autovacuum 0ff |
| 10:21 |
pinesol_green |
csharp: Band 'Autovacuum 0ff' added to list |
| 10:52 |
Dyrcona |
heh |
| 10:52 |
Dyrcona |
I think i got that one right. |
| 10:59 |
csharp |
if you're seeing net weirdness this morning - this is probably the cause: https://www.reddit.com/r/sysadmin/comments/6mtxpd/56_marietta_in_atlanta_ga_is_having_major_power/ |
| 11:02 |
|
ningalls_ left #evergreen |
| 11:03 |
dbs |
csharp++ # that explains my nick's disappearance for a bit: https://status.linode.com/ |
| 11:04 |
Dyrcona |
The Android app, Hemlock, has a self check feature, doesn't it? |
| 11:07 |
kmlussier |
Dyrcona: That doesn't sound familiar to me. |
| 11:08 |
Dyrcona |
kmlussier: Right. Doesn't look like it does. |
| 11:09 |
JBoyer |
I've brought up that potential feature before, but I don't know of any apps that offer it. |
| 11:09 |
Dyrcona |
JBoyer: Boopsie can do it if the library enables the option. |
| 11:10 |
Dyrcona |
Boopsie is commercial, of course. |
| 11:10 |
kmlussier |
How well does Evergreen's native self check work in a browser on a mobile device? |
| 11:10 |
JBoyer |
I forgot about Boopsie. Not sure any of our libraries using them turn that on. |
| 11:10 |
Dyrcona |
I have never tried the native self check on my phone. |
| 11:11 |
Dyrcona |
It requires a staff login, so probably not very well. :) |
| 11:11 |
kmlussier |
Oh, of course. :) |
| 11:11 |
Dyrcona |
At least, not for patrons. |
| 11:12 |
Dyrcona |
OK. I'm going to start a restore on my new server with optimized settings. |
| 11:12 |
kmlussier |
But, if it does display well on a screen, it probably could be a small enhancement to have a version that allows patrons to use it on their phones. |
| 11:14 |
Dyrcona |
Hmm... Not sure it would be so small, and it would pose a bigger security risk. |
| 11:14 |
Dyrcona |
Like basically having a publicly accessible staff client that is auto-logged in. |
| 11:16 |
Dyrcona |
Though, it could be a matter of modifying it not to require a staff login and to allow patrons with the proper permissions to do self checks. |
| 11:17 |
JBoyer |
And getting rid of dojo because trying to login to it currently is miserable. |
| 11:17 |
JBoyer |
And adding all of the html5 autocorrect/autocomplete/autocapitalizing options to the text boxes. ;) |
| 11:17 |
Dyrcona |
And, making it a progressive web app. :) |
| 11:17 |
kmlussier |
OK, never mind. :) |
| 11:17 |
Dyrcona |
So, a whole new thing. |
| 11:19 |
kmlussier |
As far as the security risk, it seems like that would be a risk putting it in a patron-centered app too. |
| 11:20 |
Dyrcona |
Less so, if it based on the patron having a self-check permission. |
| 11:20 |
Dyrcona |
That would require some backend work. |
| 11:25 |
|
rlefaive joined #evergreen |
| 11:35 |
dbs |
this room has been talking my language for the past 20 minutes! |
| 11:35 |
dbs |
en-CA-PWA |
| 11:35 |
Dyrcona |
ha! |
| 11:46 |
dbs |
I feel like I targeted one too many releases in bug 1703678 |
| 11:46 |
pinesol_green |
Launchpad bug 1703678 in Evergreen 3.0 "Conjoined items do not display without an extra copy attached to the record" [Undecided,New] https://launchpad.net/bugs/1703678 |
| 11:50 |
JBoyer |
Speaking of targeting, I'm still choosing the 3.0 beta milestone for bugs, should that just be regular 3.0 now? |
| 11:50 |
|
mmorgan joined #evergreen |
| 11:50 |
Dyrcona |
I don't think 3.0 beta has been released, yet. |
| 11:51 |
Dyrcona |
I guess it depends on if you think you can make the beta deadline? |
| 11:51 |
Dyrcona |
But, gmcharlt should have the final say on that, I think. :) |
| 11:52 |
JBoyer |
Oh, right. The question was "3.0 Alpha or 3.0" There's no beta milestone but there are still alpha and uh, undecorated. |
| 11:52 |
gmcharlt |
stick with 3.0-alpha |
| 11:52 |
JBoyer |
gmcharlt++ |
| 11:52 |
JBoyer |
One less thing to add to the pile of things to do, heh. |
| 11:54 |
gmcharlt |
now, in the case of bugs that are in backbranches where there's a reasonable expectation that it will make it into 2.11/12.x prior to 3.0-alpha, I typically do not personally target the current master milestone |
| 11:55 |
gmcharlt |
reasoning is that (a) patch gets rolled into master, of course and more to the point |
| 11:56 |
gmcharlt |
(b) it makes for less noise in major version release notes for bugfixes made to the previous maintenance release stream to be, in effect, incoporated by reference |
| 11:57 |
gmcharlt |
however, I'm surfacing this practice because, well, it's entirely possible I'm being idiosyncratic and off-base here |
| 11:59 |
|
sandbergja joined #evergreen |
| 12:01 |
JBoyer |
Makes sense to me. I think most of what I've targeted have been web client bugs and I don't have a good grasp of the backporting plans there. |
| 12:01 |
kmlussier |
gmcharlt: I've usually targeted the upcoming release for bug fixes, mainly because that's how I've seen others do it. |
| 12:02 |
kmlussier |
JBoyer: Bug fixes can be backported to 2.12 |
| 12:03 |
kmlussier |
JBoyer: And I'm very liberal in my definition of 'bug fix.' |
| 12:03 |
JBoyer |
So I maybe should nudge a few milestones. I'll try to look over what I've got open at the moment. |
| 12:27 |
JBoyer |
Pfft. 2 bugs, 50/50. |
| 12:36 |
|
jihpringle joined #evergreen |
| 13:09 |
dbs |
gmcharlt: so should it be "Affects: Evergreen / Milestone: 3.0-alpha" or "Affects: 3.0 / Milestone: 3.0-alpha"? |
| 13:11 |
gmcharlt |
dbs: 3.0 series, 3.0-alpha for something that's reasonably expected to have a PR by the 3.0-alpha cutoff |
| 13:12 |
gmcharlt |
master series / 3.next for a wishlist or new feature that is not expected to make the cutoff |
| 13:13 |
Dyrcona |
hmm. I recall seeing/running a query to list all database indexes and their types, but can't seem to find such a thing today. |
| 13:16 |
Dyrcona |
Ah, wait. Google is apparently my friend, again. :) |
| 13:17 |
dbs |
"You are about to mark bug "Conjoined items do not display without an extra copy attached to the record" |
| 13:17 |
dbs |
as no longer affecting Evergreen." seems like a weird thing to say "okay" to but okay :) |
| 13:18 |
|
rlefaive joined #evergreen |
| 13:18 |
Dyrcona |
Yeah, that's a weird message but that happens if you change the series on the default target. |
| 13:18 |
Dyrcona |
And the Google results are not so friendly.... |
| 13:19 |
Dyrcona |
First query doesn't work on my database. |
| 13:20 |
dbs |
"\di *.*" for a non-query |
| 13:20 |
dbs |
psql++ |
| 13:21 |
gmcharlt |
dbs: :( I fear I led you down the garden path; doing it that way looks like it makes it impossible to search for the bug directly from https://bugs.launchpad.net/evergreen |
| 13:21 |
dbs |
haha |
| 13:21 |
Dyrcona |
It does? I didn't think it did that. |
| 13:21 |
Dyrcona |
re: what gmcharlt said. |
| 13:22 |
dbs |
Okay, added "Affects: Evergreen / Milestone: 3.0-alpha" back |
| 13:22 |
Dyrcona |
dbs: Thanks I was looking for a select statement, but \di might be what I need. |
| 13:22 |
gmcharlt |
Dyrcona: sadly yes |
| 13:22 |
dbs |
Should I delete "Affects: 3.0 / Milestone: 3.0-alpha"? |
| 13:22 |
gmcharlt |
dbs: yeah |
| 13:22 |
dbs |
okay |
| 13:22 |
gmcharlt |
also... |
| 13:22 |
dbs |
gmcharlt++ |
| 13:23 |
* gmcharlt |
*shakes fist at LP* |
| 13:23 |
* dbs |
*shakes fist at meetings* |
| 13:24 |
Dyrcona |
I think selecting from pg_indexes is more what I want. I want to be able to tell if I have "duplicate" indexes and if they are GIN or GIST. |
| 13:26 |
* Dyrcona |
*shakes fist* |
| 14:03 |
|
rlefaive joined #evergreen |
| 14:50 |
* dbs |
comes back from a meeting about shaking fists |
| 14:51 |
kmlussier |
Sounds like my kind of meeting |
| 14:54 |
|
collum joined #evergreen |
| 14:55 |
JBoyer |
"I'll get you yet, Batman!" "HAHAHAHAHAhaha! Good meeting boys, now get out there and do what you do, Hehehe!" |
| 15:01 |
* kmlussier |
chuckles |
| 15:04 |
Dyrcona |
:) |
| 15:12 |
Dyrcona |
There's a small issue with the websockets instructions for Debian Jessie. |
| 15:12 |
Dyrcona |
If you follow the README literally, you'll install the wrong Apache configuration file. |
| 15:19 |
|
jvwoolf joined #evergreen |
| 15:59 |
dbs |
Dyrcona: "SELECT * FROM pg_catalog.pg_indexes WHERE indexdef ~* 'GIST';" for a rough first draft? |
| 16:00 |
Dyrcona |
dbs: Something like that. |
| 16:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:04 |
|
Jillianne joined #evergreen |
| 17:08 |
|
mmorgan left #evergreen |
| 17:19 |
|
jvwoolf left #evergreen |
| 17:45 |
pinesol_green |
[evergreen|Angela Kilsdonk] Docs: Email Checkout Receipts (web client) - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=688df85> |
| 18:35 |
|
dbs joined #evergreen |
| 19:37 |
|
StomproJ joined #evergreen |
| 22:07 |
|
rlefaive joined #evergreen |
