| Time |
Nick |
Message |
| 02:14 |
|
eady joined #evergreen |
| 06:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:51 |
|
rlefaive joined #evergreen |
| 08:16 |
|
Dyrcona joined #evergreen |
| 08:18 |
|
kmlussier joined #evergreen |
| 08:31 |
|
rlefaive_ joined #evergreen |
| 08:36 |
|
rjackson_isl joined #evergreen |
| 08:42 |
|
_adb joined #evergreen |
| 08:58 |
|
rlefaive joined #evergreen |
| 09:04 |
Dyrcona |
Anyone have any idea why simple2zoom would refuse connections after an update? I did not change the configuration and it was working last night before installing updates and upgrading to 2.12.8. |
| 09:10 |
Dyrcona |
Ah ha! We're using the standard port (210) and I forgot to start it with sudo. |
| 09:10 |
csharp |
rubber_ducking++ |
| 09:11 |
Dyrcona |
Well, that's the trouble with thing that "just work" and you don't have to restart them but every few months. |
| 09:11 |
Dyrcona |
You forget a few details sometimes. |
| 09:11 |
csharp |
ugh - upgraded the DB servers to 16.04 (already had been running 9.5 from pg apt repos on 14.04) and bug 1714026 reappeared |
| 09:11 |
pinesol_green |
Launchpad bug 1714026 in Evergreen "Maintain Control Numbers function should be schema-qualified" [High,Fix released] https://launchpad.net/bugs/1714026 |
| 09:12 |
csharp |
finally applied the change to our live server so everything is now schema-qualified :-/ |
| 09:12 |
csharp |
working again, but needed to vent |
| 09:12 |
csharp |
I guess the path for the PG user got re-set with the upgrade |
| 09:14 |
Dyrcona |
csharp: I'm going to run the 2.12.7 to 2.12.8 db upgrade script tonight since it failed last night. |
| 09:14 |
Dyrcona |
I've added "concurrently" to the drop and create index commands. |
| 09:15 |
Dyrcona |
Dunno if my laptop was working when I mentioned that last night...... |
| 09:15 |
Dyrcona |
Always fun to lose your Internet connection in the middle of doing an upgrade. |
| 09:16 |
Dyrcona |
I don't know what the problem was, really. |
| 09:16 |
Dyrcona |
At the point of renewing a dhcp lease, systemd-resolved decided that it didn't like my ISP's DNS servers. |
| 09:18 |
Dyrcona |
My wifi was flooded with packets, and syslog had all kinds of messages "using degraded feature set for DNS server." |
| 09:18 |
Dyrcona |
Google wasn't much help. |
| 09:19 |
Dyrcona |
Reboot didn't help, so I tethered vis USB to my cell phone. That worked. |
| 09:20 |
Dyrcona |
After I finished the upgrade, I switched back to wifi and it was working again. |
| 09:21 |
Dyrcona |
The closest thing that I could find was systemd-resolved sometimes gets confused with dnsmasq running, but the messages in that case mention 12.0.0.1 or 127.0.0.5 as the DNS server, not the remote IP. |
| 09:22 |
csharp |
Dyrcona: yowza |
| 09:22 |
Dyrcona |
127.0.0.1, of course. not 12.0.0.1 |
| 09:22 |
Dyrcona |
typos-- |
| 09:22 |
csharp |
glad my suggestion is helpful ;-) |
| 09:22 |
Dyrcona |
yes, thank you. |
| 09:23 |
Dyrcona |
csharp++ |
| 09:32 |
|
rlefaive joined #evergreen |
| 09:34 |
|
yboston joined #evergreen |
| 09:35 |
|
jvwoolf joined #evergreen |
| 09:36 |
|
rlefaive joined #evergreen |
| 09:52 |
|
_adb joined #evergreen |
| 09:52 |
|
jonadab joined #evergreen |
| 09:54 |
|
troy__ joined #evergreen |
| 09:54 |
|
ejk joined #evergreen |
| 09:54 |
|
eby joined #evergreen |
| 09:54 |
|
sard joined #evergreen |
| 09:54 |
|
bshum joined #evergreen |
| 09:54 |
|
book` joined #evergreen |
| 09:54 |
|
rlefaive joined #evergreen |
| 09:54 |
|
jvwoolf joined #evergreen |
| 09:54 |
|
yboston joined #evergreen |
| 09:54 |
|
rjackson_isl joined #evergreen |
| 09:54 |
|
Dyrcona joined #evergreen |
| 09:54 |
|
genpaku joined #evergreen |
| 09:54 |
|
dbwells joined #evergreen |
| 09:54 |
|
yar joined #evergreen |
| 09:54 |
|
abneiman joined #evergreen |
| 09:54 |
|
pinesol_green joined #evergreen |
| 09:54 |
|
JBoyer joined #evergreen |
| 09:54 |
|
RBecker joined #evergreen |
| 09:54 |
|
Bmagic joined #evergreen |
| 09:54 |
|
ericar joined #evergreen |
| 09:54 |
|
miker joined #evergreen |
| 09:54 |
|
rhamby joined #evergreen |
| 09:54 |
|
berick joined #evergreen |
| 09:54 |
|
bwicksall joined #evergreen |
| 09:54 |
|
kipd joined #evergreen |
| 09:54 |
|
jeffdavis joined #evergreen |
| 09:54 |
|
dbs joined #evergreen |
| 09:54 |
|
gmcharlt joined #evergreen |
| 09:55 |
|
rlefaive_ joined #evergreen |
| 10:08 |
|
rlefaive joined #evergreen |
| 10:12 |
|
montgoc1 joined #evergreen |
| 10:46 |
|
Christineb joined #evergreen |
| 11:00 |
pinesol_green |
[evergreen|Remington Steed] Docs: Use new images for in-house use - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9a7e27b> |
| 11:10 |
Dyrcona |
So, bugs that affect only the XUL staff client and not the web staff client, are they worth filing at this point? |
| 11:12 |
rhamby |
Dyrcona: in my opionion they are as dead to me as some very dead person |
| 11:12 |
rhamby |
s/opionion/opinion |
| 11:13 |
* Dyrcona |
thought you'd crossed poppies with onions for a second. :) |
| 11:15 |
* csharp |
idly wonders if we could leverage hatch to make EG selfcheck connect to demagnitizing device |
| 11:15 |
kmlussier |
Dyrcona: Is it a new bug? Something that wasn't there before? |
| 11:15 |
csharp |
*devices |
| 11:15 |
csharp |
@decide opionion or opinion |
| 11:15 |
pinesol_green |
csharp: go with opinion |
| 11:16 |
Dyrcona |
kmlussier: Yes and no. |
| 11:18 |
Dyrcona |
I believe it is Lp 1235458 |
| 11:18 |
pinesol_green |
Launchpad bug 1235458 in Evergreen "Holdings maintenance screen gets hung up" [Undecided,Confirmed] https://launchpad.net/bugs/1235458 |
| 11:19 |
Dyrcona |
Doesn't happen in the web staff client, though. |
| 11:19 |
kmlussier |
Yeah, I would say that one should be set to Won't Fix if it's not happening in the web client. |
| 11:20 |
kmlussier |
It doesn't meet one of the 3 criteria identified here - http://libmail.georgialibraries.org/pipermail/open-ils-dev/2017-August/010400.html |
| 11:21 |
Dyrcona |
kmlussier: I'll quote on that. :) |
| 11:24 |
berick |
csharp: certainly possible |
| 11:27 |
csharp |
berick: good to know |
| 11:27 |
csharp |
when I'm out from under next month's upgrade and the following month's migration, I'd be interested in looking into that |
| 11:30 |
jeff |
Dyrcona: i see value in reporting them for a time, even if you then set them wontfix. |
| 11:31 |
Dyrcona |
Does won't fix show up in simple search? |
| 11:32 |
bshum |
I think "won't fix" is usually hidden by default from the searches, but of course we'll all get emailed about it (those who subscribe) |
| 11:33 |
berick |
hm, limit-to-avail in staff client throwing PG error. |
| 11:33 |
* berick |
looks for LP entry |
| 11:37 |
bshum |
Personally I don't see a point in opening bugs that will get marked won't fix and end up mostly hidden anyways. |
| 11:37 |
bshum |
But it's out there for anybody to use the way they like :) |
| 11:40 |
kmlussier |
berick: I haven't seen a bug report on that. |
| 11:41 |
berick |
kmlussier: you will now :) |
| 11:41 |
berick |
arg! |
| 11:41 |
berick |
followed directly by LP timeout error |
| 11:41 |
berick |
sheesh |
| 11:41 |
* berick |
takes deep breath, starts over typing |
| 11:41 |
csharp |
@blame it on the rain |
| 11:41 |
pinesol_green |
csharp: it on the rain 's bugfix broke csharp's feature! |
| 11:52 |
|
montgoc1 joined #evergreen |
| 11:55 |
|
rlefaive joined #evergreen |
| 12:01 |
|
khuckins joined #evergreen |
| 12:09 |
|
beanjammin joined #evergreen |
| 12:39 |
|
jihpringle joined #evergreen |
| 12:52 |
|
bwicksall joined #evergreen |
| 13:07 |
|
sandbergja joined #evergreen |
| 13:16 |
* Dyrcona |
wishes he had a simple way to test action_trigger template changes without having to rig up a lot of Perl code with data (real or bogus). |
| 13:18 |
Dyrcona |
I could try it on a test server, but my data is too far out of date and a reload would take a day with copying the 40GB dump and waiting on a pg_restore. |
| 13:21 |
Dyrcona |
And, then, others don't realize that template changes are really programming, when you have to add IF blocks on some fairly complex logic. |
| 13:22 |
csharp |
Dyrcona: we have the same problem |
| 13:22 |
csharp |
we just do the refresh when we need it :-/ |
| 13:23 |
Dyrcona |
One library wants a notice about their holiday hours on the hold is ready notification. |
| 13:23 |
Dyrcona |
To start and end between certain dates. |
| 13:24 |
Dyrcona |
I was thinking of checking for one of the 3 org unit ids and the date being in the range, since the db update that would remove the text is outside the date range. |
| 13:25 |
Dyrcona |
Now, I think I'll just check the org unit ids and that's it. |
| 13:25 |
Dyrcona |
If the text is included 1 extra day, it's no big deal, right? :) |
| 13:25 |
Dyrcona |
But, I see that I can make a small improvement to the template to make this easier now and in the future. |
| 13:33 |
Dyrcona |
$$++ |
| 13:34 |
Dyrcona |
$$ quotes, that is. |
| 13:34 |
|
ohiojoe joined #evergreen |
| 13:44 |
ohiojoe |
just an FYI, DIG meeting in about 15 minutes |
| 13:49 |
sandbergja |
ohiojoe: so excited for DIG meeting! |
| 13:50 |
ohiojoe |
:-) |
| 13:53 |
|
dwgreen joined #evergreen |
| 13:53 |
remingtron |
Equinox folks, I'm getting JS errors in the Action Triggers UI, both web and XUL client |
| 13:53 |
remingtron |
any reason that would be local to you, or should I file a 3.0 bug? |
| 13:54 |
remingtron |
gmcharlt: phasefx: --^ (not sure who to ask) |
| 13:55 |
gmcharlt |
remingtron: in webby.evergreencatalog.com/ |
| 13:55 |
gmcharlt |
? |
| 13:55 |
kmlussier |
ohiojoe: I'm going only going to be able to stick around for the first 30 minutes. I have another meeting to run to. |
| 13:57 |
ohiojoe |
sounds like a plan.. I'll keep that in mind |
| 13:57 |
ohiojoe |
or try at any rate |
| 13:58 |
remingtron |
gmcharlt: sorry, on demo |
| 13:58 |
gmcharlt |
remingtron: OK, we'll take a look |
| 14:00 |
ohiojoe |
#startmeeting 2017-12-07 - Documentation Interest Group Meeting |
| 14:00 |
pinesol_green |
Meeting started Thu Dec 7 14:00:29 2017 US/Eastern. The chair is ohiojoe. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 14:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 14:00 |
pinesol_green |
The meeting name has been set to '2017_12_07___documentation_interest_group_meeting' |
| 14:00 |
ohiojoe |
agenda can be found online at: |
| 14:00 |
ohiojoe |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:dig_meeting_20171207-agenda |
| 14:00 |
ohiojoe |
#topic Introductions: please paste "#info <username> is <name> <affiliation>" to identify who you are and what organization, if any, you represent |
| 14:01 |
sandbergja |
#info sandbergja is Jane Sandberg, Linn-Benton Community College |
| 14:01 |
ohiojoe |
#info ohiojoe is Joe Knueven, Germantown Public Library, Consortium of Ohio Libraries |
| 14:01 |
jihpringle |
#info jihpringle is Jennifer Pringle, BC Libraries Cooperative (Sitka) |
| 14:01 |
kmlussier |
#info kmlussier is Kathy Lussier, MassLNC |
| 14:03 |
ohiojoe |
#topic Old Business |
| 14:03 |
abneiman |
#info abneiman is Andrea Neiman, EOLI |
| 14:03 |
ohiojoe |
#topic Progress on Web Client docs |
| 14:06 |
ohiojoe |
any thoughts on this? it reminds me that I had a few action items on my to-do list from last month that I didn't get done yet |
| 14:08 |
sandbergja |
I don't know -- do we need a new approach, or to bring new volunteers in? |
| 14:08 |
sandbergja |
I don't know how much action there has been on the Web Client docs recently |
| 14:08 |
kmlussier |
I haven't found that the web client doc days have been very effective. |
| 14:09 |
sandbergja |
do we have a sense for how much XUL-specific stuff remains in the documentation? |
| 14:09 |
sandbergja |
and how much confusion the XUL-specific stuff is causing? |
| 14:09 |
sandbergja |
#link https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:webclient |
| 14:11 |
jihpringle |
do we maybe need to update that page to reflect the re-org? |
| 14:11 |
sandbergja |
jihpringle: perhaps |
| 14:12 |
sandbergja |
it feels like we have a lot of docs revision/cleanup projects going right now, and maybe we could combine them somehow? |
| 14:12 |
jihpringle |
what if we had one wiki page per manual that listed chapters/sections that needed review as well as a list of topics that needed to be added? |
| 14:13 |
jihpringle |
combining review and missing docs into one page |
| 14:13 |
sandbergja |
I like that idea! |
| 14:14 |
jihpringle |
list of topics needing documentation could include new web client features and old ported from xul features |
| 14:15 |
ohiojoe |
That sounds like it'd help focus what resources we have on the places where we'll do the most good |
| 14:15 |
jihpringle |
I'd be happy to set up wiki pages to match our list of EG 3.0 manuals if we want to go forward with this |
| 14:16 |
|
rlefaive joined #evergreen |
| 14:16 |
ohiojoe |
that sounds like a good plan to me.. |
| 14:17 |
sandbergja |
jihpringle++ |
| 14:17 |
ohiojoe |
#action jihpringle will set up wiki pages to match the list of EG 3.0 manuals |
| 14:18 |
|
jlundgren_ joined #evergreen |
| 14:18 |
jihpringle |
if everyone agress, I'm going to use the 3.0 page as the starting point and divide up the info on that page into the specific manuals - https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:3.0_needs |
| 14:18 |
jihpringle |
agress = agrees |
| 14:19 |
jihpringle |
any objections? |
| 14:19 |
ohiojoe |
jihpringle++ |
| 14:20 |
ohiojoe |
perhaps in the same vein I could collapse that old business item into the ongoing item on documenting the EG 3.0 new features? |
| 14:20 |
sandbergja |
no objections |
| 14:20 |
jihpringle |
that makes sense to me |
| 14:21 |
kmlussier |
+1 |
| 14:22 |
ohiojoe |
well, with what sounds like a solid plan for that, let's move along.. |
| 14:22 |
|
jlundgren joined #evergreen |
| 14:22 |
ohiojoe |
#topic Previous action items |
| 14:23 |
ohiojoe |
kmlussier: do you have any update on item #3, identifying unclaimed bite sized tasks for new DIG participants, since I know you need to leave shortly.. |
| 14:24 |
kmlussier |
Sorry, no, that one slipped my mind. Could you add another action item for me on that one? |
| 14:25 |
ohiojoe |
no worries, I can leave that in there |
| 14:26 |
ohiojoe |
which is as good a time as any for me to say that I have work to do on #4, 8 & 11 that thanks to local circumstances did not occur this past month |
| 14:27 |
ohiojoe |
My intention is to push out the info I meant to share in November on #11 there by the end of the week and email out to the general EG list for volunteers today or tomorrow as well.. |
| 14:28 |
|
khuckins_ joined #evergreen |
| 14:28 |
jihpringle |
I'll follow up on #1 and #2 with Christineb (she had training this morning so sends her regrets for missing the meeting) |
| 14:29 |
jihpringle |
#6 is done and being used - https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:reorg:clean_up |
| 14:29 |
jihpringle |
but I think maybe needs to be included in the new wiki pages for the 3.0 manuals as well |
| 14:30 |
sandbergja |
Could you add another action item for #10 for me, please? |
| 14:30 |
|
rlefaive joined #evergreen |
| 14:30 |
ohiojoe |
when I read #6 I was thinking that it did sound like it tied into what we just decided a minute ago.. |
| 14:31 |
ohiojoe |
#action kmlussier will identify unclaimed bite sized tasks for new DIG participants |
| 14:31 |
ohiojoe |
#action sandbergja will share asciidoc level knowledge of how to work with the new manuals |
| 14:32 |
ohiojoe |
wow, it looks like that only leaves the "everyone" action items that we haven't mentioned or otherwise given an update on.. |
| 14:34 |
ohiojoe |
and from my reading, it looks like those three (#5, 7 & 9) are still relevant, so I'm thinking we should keep them on the agenda for now.. |
| 14:34 |
jihpringle |
agreed, I think those ones will be ongoing for a while |
| 14:36 |
ohiojoe |
well, with that said, is there any additional to report or discuss in the area of previous action items? |
| 14:40 |
ohiojoe |
#topic Ongoing business |
| 14:40 |
ohiojoe |
#topic Progress on documenting new features in Evergreen 3.0 (and previous) |
| 14:41 |
ohiojoe |
does anyone have anything to share/discuss here? We kind of talked about it a earlier... |
| 14:42 |
jihpringle |
we're still in the early stages but we're going to be redoing all of our Sitka specific documentation before our next upgrade in May (either to 3.0 or 3.1) and we're moving to asciidoc with our repos in github |
| 14:43 |
jihpringle |
so once we get going it should be much easier for us to share our docs back to the community docs and for others to copy and paste from our repos |
| 14:44 |
ohiojoe |
that's great news! |
| 14:44 |
ohiojoe |
jihpringle++ |
| 14:45 |
jihpringle |
big thanks to everyone who answered our questions about how the community docs are set up |
| 14:46 |
jihpringle |
once we start documentating new features I'll try and make sure we push back any that aren't already documented |
| 14:48 |
sandbergja |
Sitka is so cool! Thanks to jihpringle and all of your colleagues! |
| 14:49 |
jihpringle |
sandbergja: thanks for the help getting us going :) |
| 14:52 |
ohiojoe |
with that said.. that leaves only one item from the agenda... |
| 14:52 |
ohiojoe |
#topic Progress on documentation launchpad bugs |
| 14:52 |
ohiojoe |
does anyone have any thoughts here before we wrap up for today (it feels so odd to actually get through the whole agenda.. ) |
| 14:53 |
sandbergja |
I think I'm good |
| 14:54 |
jihpringle |
would it be helpful to reference the bugs on the wiki page for the applicable manual? |
| 14:54 |
jihpringle |
looks like some of the bugs are about sections that are out of date or missing |
| 14:56 |
sandbergja |
that sounds helpful! Having a one-stop shop for documentation work on a particular manual seems really useful. |
| 14:56 |
jihpringle |
k, I'll combine everything :) |
| 14:57 |
sandbergja |
Thanks! |
| 14:57 |
ohiojoe |
that sounds helpful to me too.. should also help in terms of communicating back to those who are looking for those docs that they've been created or updated.. |
| 14:58 |
ohiojoe |
well, if there's nothing else.. |
| 14:58 |
ohiojoe |
thank you everyone |
| 14:58 |
ohiojoe |
#endmeeting |
| 14:58 |
pinesol_green |
Meeting ended Thu Dec 7 14:58:27 2017 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 14:58 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-12-07-14.00.html |
| 14:58 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-12-07-14.00.txt |
| 14:58 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-12-07-14.00.log.html |
| 14:58 |
jihpringle |
ohiojoe++ |
| 14:58 |
ohiojoe |
that few seconds of delay made me nervous that I'd misspelled the command or the like.. lol |
| 14:59 |
sandbergja |
haha |
| 14:59 |
sandbergja |
Thanks for facilitating, ohiojoe! |
| 14:59 |
sandbergja |
ohiojoe++ |
| 15:00 |
ohiojoe |
Thank you. Also, thank you for the work you all have put in on the docs.. I know there's a lot we're working to do now, but it's impressive to see how much gets accomplished for the community by relatively few hands.. thank you |
| 15:03 |
|
khuckins__ joined #evergreen |
| 15:52 |
jeffdavis |
JBoyer: for bug 1737016, your schema update adds a NOT NULL to acq.funding_source.code but the upgrade script doesn't make the same change, I wonder if it should |
| 15:52 |
pinesol_green |
Launchpad bug 1737016 in Evergreen "Acq: Funding Source codes should be unique to owners, not the entire system" [Undecided,Confirmed] https://launchpad.net/bugs/1737016 |
| 15:55 |
|
jlundgren left #evergreen |
| 16:00 |
|
JBoyer_ joined #evergreen |
| 16:16 |
JBoyer_ |
berick++ # I found the staff available error recently and haven't had time to bug it. :( |
| 16:19 |
JBoyer_ |
jeffdavis, re: your comment about bug 1737016 - yes, it should. Thanks for catching that. |
| 16:19 |
pinesol_green |
Launchpad bug 1737016 in Evergreen "Acq: Funding Source codes should be unique to owners, not the entire system" [Undecided,Confirmed] https://launchpad.net/bugs/1737016 |
| 16:26 |
|
khuckins_ joined #evergreen |
| 16:28 |
JBoyer_ |
And fixed. |
| 16:48 |
|
Christineb joined #evergreen |
| 16:48 |
|
troy__ joined #evergreen |
| 17:11 |
|
khuckins__ joined #evergreen |
| 17:26 |
|
jvwoolf left #evergreen |
| 17:42 |
|
Christineb joined #evergreen |
| 17:42 |
|
troy__ joined #evergreen |
| 18:31 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 19:01 |
|
JBoyer joined #evergreen |
| 19:02 |
|
Bmagic joined #evergreen |
