| 16:34 |
Bmagic |
terranm++ # hanging in there |
| 16:34 |
terranm |
Bmagic: was the auto-submitted line the problem, you think? Or was there something else? |
| 16:35 |
Bmagic |
not really sure - It's kind of assumed that libraries will customize the heck out of that and it won't look anything like the stock stub |
| 16:36 |
terranm |
Yeah, we've heavily customized all of ours. Hard to test when the stock doesn't work at all out of the box though. |
| 16:36 |
Bmagic |
looking to see what the differences are |
| 16:38 |
terranm |
I'm going to start plugging things back into the template |
| 16:38 |
Bmagic |
maybe something is required to appear in action_trigger.environment... this is mentioned target.0.home_ou.id which might throw a template error if the environment doesn't include home_ou |
| 17:07 |
terranm |
modifying the To to hardcode in my email |
| 17:07 |
Bmagic |
ok, now, I think we are good - the template is stock from patch |
| 17:08 |
Bmagic |
leave the template stock, and I've introduced a parameter recipient_email |
| 17:09 |
Bmagic |
that way we are testing the patch template exactly |
| 17:09 |
terranm |
k - testing now |
| 17:09 |
Bmagic |
(with the extra line return removed though) |
| 17:10 |
Bmagic |
also - no need to re-re-register new patrons - I'm resetting the AT's with each test, and it generates a new email from the old ones again |
| 17:10 |
terranm |
oh, ok |
| 17:11 |
|
mmorgan left #evergreen |
| 17:12 |
terranm |
Nothing coming through |
| 17:40 |
Bmagic |
alright - will probably do that tomorrow - I'll let you know when it's set |
| 17:40 |
terranm |
Thanks! Bmagic++ |
| 17:40 |
Bmagic |
terranm++ |
| 17:41 |
terranm |
There's only one other bite-sized patch on there that hasn't been tested yet - maybe I can get Elaine to test it tomorrow morning so you can start fresh with a new bite sized group too |
| 17:41 |
Bmagic |
ok, I'll hold off for your go-ahead then |
| 17:44 |
terranm |
Cool beans, have a good night! |
| 17:44 |
Bmagic |
you too :) |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:05 |
|
sandbergja joined #evergreen |
| 20:57 |
|
sandbergja joined #evergreen |
| 21:26 |
|
sandbergja joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:03 |
|
agoben joined #evergreen |
| 07:06 |
|
rjackson_isl joined #evergreen |
| 08:19 |
|
alynn26 joined #evergreen |
| 09:41 |
Bmagic |
in the face |
| 09:41 |
Bmagic |
Bugs are like monsters from The Mummy. They come out of the sand.... boxes |
| 09:42 |
terranm |
lol |
| 09:43 |
Bmagic |
If we could just get Brendan Fraser to test.... |
| 10:06 |
|
aabbee joined #evergreen |
| 10:07 |
rfrasur |
terranm++ |
| 11:11 |
|
sandbergja joined #evergreen |
| 12:35 |
terranm |
alynn26++ for already diving into pullrequest testing and signing off on four patches this morning! |
| 12:50 |
|
collum joined #evergreen |
| 13:03 |
|
dbwells_ joined #evergreen |
| 14:11 |
|
remingtron joined #evergreen |
| 14:12 |
bshum |
Well that's interesting... Chrome 80 doesn't let you bypass the self-signed certs anymore? :( |
| 14:15 |
bshum |
Oh, wait, I'm on v79. Let's update to 80 and see if it's better or worse... :D |
| 14:19 |
bshum |
Nope |
| 14:19 |
bshum |
Still doesn't work, blah |
| 14:27 |
bshum |
Well this'll be fun... |
| 14:30 |
bshum |
Bmagic: bugsquash.mobiusconsortium.org looks like the cert expired two days ago |
| 14:30 |
bshum |
But at least I can get past it since it used to be a legit cert and Google doesn't just completely kill the bypass options |
| 14:30 |
bshum |
But for self-signed on my own VMs locally with trying to get to it via IP, it bombs hard |
| 14:31 |
bshum |
Oh well, there's always Firefox, I guess? |
| 14:42 |
* bshum |
will need to ponder this and test some scenarios with the ssl cert generation and ansible installer |
| 14:55 |
jeff |
is there an issue documenting that change? |
| 14:56 |
jeff |
because i'm not able to reproduce based on your description. |
| 14:57 |
bshum |
Well I wonder if it's how ansible makes the cert during the installation |
| 14:58 |
bshum |
And Chrome is blocking it from getting further now |
| 14:58 |
bshum |
I tried changing the Chrome setting for chrome://flags/#allow-insecure-localhost |
| 14:58 |
bshum |
But that seems to have done nothing too |
| 14:58 |
jeff |
do you have an exposed instance with such a cert i can test? |
| 14:59 |
bshum |
Possibly because it's an IP address, not actually localhost |
| 14:59 |
bshum |
No, it's private networking within my Virtualbox |
| 14:59 |
jeff |
wait, did something generate a cert for an IP address? |
| 14:59 |
bshum |
I've got to expand my testing radius a bit, sorry jeff |
| 15:00 |
bshum |
jeff: No, the automatically generated cert doesn't include the IP address |
| 15:00 |
bshum |
Just a hostname of localhost and "XX" for most of the default values |
| 15:00 |
bshum |
https://github.com/berick/evergreen-ansible-installer/blob/ubuntu-18.04/evergreen/apache.yml#L37 |
| 15:01 |
bshum |
This is the part of berick's ansible script which generates the SSL cert |
| 15:01 |
bshum |
I'm tracking back from that to see what the generated SSL cert is |
| 15:01 |
bshum |
And how that's making everything unhappy |
| 15:02 |
bshum |
And yeah, web_domain is "localhost" in the variable settings |
| 15:03 |
bshum |
I was going to move that cert out of the way and then retry using a standard cert creation and maybe set a real hostname |
| 15:03 |
bshum |
That works within my private network |
| 15:03 |
bshum |
To see if it handles it differently |
| 15:03 |
bshum |
But of course, I also just blew away that VM, so I have to redo the whole install first |
| 15:08 |
bshum |
jeff: The most I can find is Google talking about trying to kill off mixed content stuff - https://security.googleblog.com/2019/10/no-more-mixed-messages-about-https_3.html |
| 15:08 |
bshum |
But nothing about self-signed certs specifically (yet) |
| 15:10 |
bshum |
Though some vendors noted issues with v79 and v80 for self-signed certs - https://support.google.com/chrome/thread/28404872?hl=en |
| 15:10 |
bshum |
So that's what got me thinking on the issue |
| 15:10 |
bshum |
But perhaps it is just the way the certs are done and there's still some lifelines to be grabbed |
| 15:12 |
jeff |
``As of 2/13/2020 Chrome has updated to version 80.0.3987.106 which no longer causes issues with firewall management.'' |
| 15:12 |
jeff |
from a sonicwall article linked from your URL above: https://www.sonicwall.com/support/product-notification/resolved-unable-to-access-firewall-management-using-chrome-v80/200211160032277/ |
| 15:12 |
jeff |
doesn't reference a chromium issue, though. |
| 16:42 |
bshum |
Besides getting a real SSL cert :D |
| 16:53 |
bshum |
jeff++ |
| 17:48 |
|
sandbergja joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 19:37 |
|
JBoyer joined #evergreen |
| 21:47 |
|
remingtron_ joined #evergreen |
| 22:16 |
|
sandbergja joined #evergreen |
| 02:45 |
|
cmalm joined #evergreen |
| 03:07 |
|
cmalm joined #evergreen |
| 04:40 |
|
StomproJ joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:57 |
|
rfrasur joined #evergreen |
| 06:59 |
|
collum joined #evergreen |
| 07:02 |
|
agoben joined #evergreen |
| 09:38 |
|
yboston joined #evergreen |
| 09:49 |
|
sandbergja joined #evergreen |
| 09:52 |
StomproJ |
I'm looking through the debian buster install makefile, to see what all needs to be changed to upgrade to PG 10... but it seems like the PG 9.6 client still gets installed. Is that an issue, to use an older client with a newer server? |
| 09:55 |
csharp |
StomproJ: PINES just upgraded to 9.6 after unwittingly going to 10 without the backported fixes on 3.2 - been running 3.4 on 10 on a test server problem-free for months |
| 09:55 |
csharp |
StomproJ: not a problem in most cases to have a client/server version mismatch |
| 09:55 |
|
cmalm joined #evergreen |
| 09:56 |
phasefx |
are we talking the psql client? I think, at worse, stuff like tab completion might not work |
| 09:56 |
csharp |
yeah |
| 16:14 |
jeff |
And yes, I think we have at least one class of item where it should always come "home" for inspection before going elsewhere to fill a hold. |
| 16:49 |
|
jvwoolf left #evergreen |
| 16:53 |
|
khuckins_ joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 20:01 |
|
sandbergja joined #evergreen |
| 20:16 |
|
sandbergja joined #evergreen |
| 23:11 |
|
serflog joined #evergreen |
| 15:19 |
csharp |
ok cool |
| 15:20 |
terranm |
What Bill said |
| 15:20 |
* berick |
notes 2/17 may be a holiday for some |
| 15:20 |
terranm |
If we can get a bunch of those pullrequests on some sandboxes, the New Developers Group should be able to test a good chunk of them |
| 15:20 |
csharp |
# feedback fest scheduled for the week of 2/17 - 2/22 - code reviewers and committers are expected to participate |
| 15:20 |
csharp |
#info feedback fest scheduled for the week of 2/17 - 2/22 - code reviewers and committers are expected to participate |
| 15:20 |
* csharp |
will get the hang of it |
| 15:32 |
pinesol |
sandbergja: [evergreen|Galen Charlton] LP#1855931: (follow-up) make grid filter control cells wrap as well - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9077cbc> |
| 15:32 |
jeffdavis |
berick: yes, I think so |
| 15:32 |
jeffdavis |
ah, I was trying to find that follow-up bug |
| 15:32 |
sandbergja |
(just musing, I have not tested a rebased version of gmcharlt's branch for 1846042) |
| 15:33 |
terranm |
PINES has this one in production and it seems to be working well: https://bugs.launchpad.net/evergreen/+bug/1570072 - I'm not sure if anyone else from ECDI has seen any issues with testing |
| 15:33 |
pinesol |
Launchpad bug 1570072 in Evergreen "Hold request update notification preferences on change" [Wishlist,Confirmed] |
| 15:34 |
jeffdavis |
terranm: do you want that targeted for 3.5? Currently it's 3.next |
| 15:34 |
csharp |
ECDI = Evergreen Community Development Initiative for those who don't know |
| 15:49 |
sandbergja |
So we don't totally slow down everything for the user with sequential requests |
| 15:49 |
sandbergja |
But don't clobber the server with simultaneous requests |
| 15:49 |
sandbergja |
jeffdavis mentioned that this should be an approach that we take not just in Item Status, but throughout the Web client |
| 15:50 |
berick |
sandbergja: your promise batching code looks sane. i have not kept up with the bug... does that solve the issue in your tests? |
| 15:50 |
sandbergja |
It does |
| 15:50 |
sandbergja |
But all my tests have been on a little VM on my laptop |
| 15:51 |
sandbergja |
So I'd really appreciate more help testing the specific case in bug 1821094 |
| 15:51 |
pinesol |
Launchpad bug 1821094 in Evergreen 3.3 "Item status refresh after editing can get confusingly slow" [Medium,Confirmed] https://launchpad.net/bugs/1821094 |
| 15:51 |
sandbergja |
And also some discussion about whether we want to batch the promise resolving in other places in the AngularJS client |
| 15:51 |
sandbergja |
Here's the specific commit: https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=75176bca0ce8051a6dd4ba56f5613bce75901f09 |
| 15:52 |
csharp |
sandbergja: we can test it on a PINES server with realistic data/specs |
| 15:52 |
sandbergja |
charp++ |
| 15:52 |
sandbergja |
That would be really helpful! |
| 15:52 |
csharp |
#action csharp will arrange testing for sandbergja's fix to https://launchpad.net/bugs/1821094 on a realistic test server |
| 15:52 |
pinesol |
Launchpad bug 1821094 in Evergreen 3.3 "Item status refresh after editing can get confusingly slow" [Medium,Confirmed] |
| 15:53 |
berick |
i think that's a good tool to have in our toolbox. I also think devs should consider the option of creating UI specific APIs for new interfaces. |
| 15:53 |
berick |
batching some of the exising angjs stuff seems like it would be helpful |
| 16:05 |
sandbergja |
My vague sense is that it's not quite ready to be the default catalog, but definitely ready to be less hidden... |
| 16:06 |
berick |
re: what patrons see, there is a tab in the detail page that shows the patron view. you can also open a new tab to the tpac. i'm confused what the issue is on that. |
| 16:07 |
|
mmorgan joined #evergreen |
| 16:07 |
terranm |
I honestly haven't looked at it since Bill did a demo for the catalogers group a few months ago, but Chris enabled it on one of our test servers so I'll make a point to look further with real data |
| 16:07 |
jeffdavis |
We haven't enabled the Angular catalogue in production here, but I've proposed making it visible. We're seeing a lot of slowness in the staff catalogue and I wonder if the Angular version would be an improvement. |
| 16:07 |
berick |
sandbergja: same. until it gets more use in the wild, making it the default is a hard sell. |
| 16:08 |
berick |
and by the same token, if no staff know it exists, no one will use it |
| 16:11 |
terranm |
+1 to the patron view tab |
| 16:11 |
jeffdavis |
sandbergja: that's a surprising number of reference copies of that particular title |
| 16:11 |
berick |
jeff: maybe. but it gets complicated with routerLink's, target=_self, etc. depending on the context |
| 16:14 |
jeffdavis |
berick: sounds like more testing is wanted before we make it the default, but maybe we can at least make it more visible (or not call it "Experimental" anymore or whatever) in 3.5? |
| 16:14 |
terranm |
+1 |
| 16:14 |
remingtron |
berick: maybe during feedback fest we could invite EG users to test the staff catalog and give feedback |
| 16:14 |
remingtron |
(and/or during a bug squashing week) |
| 16:14 |
terranm |
+1 |
| 16:15 |
berick |
remingtron: on that note, I'll be posting all of the pending staff catalog pullreqs to a demo server for fests and squashes |
| 16:15 |
remingtron |
cool |
| 16:22 |
sandbergja |
csharp++ |
| 16:27 |
|
tlittle joined #evergreen |
| 16:31 |
dbwells |
csharp++ berick++ ui_specific_apis++ |
| 16:34 |
mdriscoll |
What is the recommended version of Postgres for 3.4 and beyond? The install instructions say that 9.6 is the minimum. I'm running 9.4 on production and test servers. Should I plan on 9.6 or jump to 10, 11? |
| 16:40 |
bshum |
Stick with 9.6 |
| 16:40 |
bshum |
10 was wonky for some people, I remember csharp having issues after their upgrade? |
| 16:41 |
bshum |
So we're still needing some DB refinements I think for some database function changes |
| 16:42 |
Dyrcona |
I did a grep through the code and didn't see any. |
| 16:42 |
bshum |
And we'll tackle 10/11/12 next time |
| 16:43 |
bshum |
Yeah I wondered if maybe he just had some custom function |
| 16:43 |
* Dyrcona |
has 9.6 through 12 installed on a test server. |
| 16:43 |
bshum |
Or it's some reporter one |
| 16:43 |
bshum |
That would generally also be custom to PINES |
| 16:43 |
bshum |
I thought we nailed down all the ones from concerto clean master for PG 10 |
| 16:44 |
Dyrcona |
mdriscoll: We upgraded to 9.6 in January from 9.5, if that's any help. |
| 16:44 |
bshum |
But then again, we also didn't yet write pgtap tests for every core function |
| 16:44 |
bshum |
Just to be safe |
| 16:44 |
* bshum |
adds to his Hackfest ideas list |
| 16:44 |
Dyrcona |
Yeah, we need more pgtap tests. |
| 16:45 |
Dyrcona |
Not sure that we can really test all of the functions since they rely so heavily on side effects. |
| 16:45 |
bshum |
Right |
| 16:45 |
bshum |
But at least we can put some input and see what expected output ought to be |
| 16:46 |
Dyrcona |
I *think* we can do multistep tests, i.e. run the function and check table values after. |
| 16:46 |
bshum |
Right |
| 16:46 |
bshum |
I'm pretty sure we can |
| 16:47 |
mdriscoll |
bshum++ |
| 17:16 |
csharp |
berick++ # finishing the meeting |
| 17:16 |
csharp |
@band add Tab Crash |
| 17:16 |
pinesol |
csharp: Band 'Tab Crash' added to list |
| 17:17 |
Dyrcona |
Also for the logs, you can backport the Pg 10 fixes to earlier versions and things are OK. I've tested them on both 9.5 and 9.6. |
| 18:03 |
|
sandbergja_ joined #evergreen |
| 20:16 |
|
sandbergja joined #evergreen |
| 20:57 |
|
JBoyer joined #evergreen |
| 00:49 |
|
cmalm_ joined #evergreen |
| 00:51 |
|
sandbergja joined #evergreen |
| 02:30 |
|
sandbergja joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:58 |
|
rfrasur joined #evergreen |
| 07:06 |
|
agoben joined #evergreen |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 09:51 |
Dyrcona |
Some vendors are still stuck in the '90s where PINs were used instead of passwords. |
| 09:52 |
rfrasur |
lol, yes, some of them are. Bless them. |
| 09:52 |
Dyrcona |
I do the opposite of bless them. :) |
| 09:53 |
Dyrcona |
But, anyway.... I guess it is still worth looking into the bugs with passwords, even if I can't use my account to test it. |
| 09:55 |
Dyrcona |
Really, I think it would be better if we had an OAuth provider and vendors connected to that to authorize our patrons. Looks like OverDrive's authentication is a form of OAuth provider. |
| 09:56 |
rfrasur |
(blessing and cursing can often bear striking similarities) |
| 09:57 |
Dyrcona |
:) |
| 17:06 |
|
mmorgan left #evergreen |
| 17:21 |
|
jihpringle joined #evergreen |
| 17:21 |
jeff |
is there anything attendees need to do to prevent our information from being shared with sched? |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 20:01 |
|
sandbergja joined #evergreen |
| 21:13 |
|
jvwoolf joined #evergreen |
| 21:42 |
|
yboston joined #evergreen |
| 11:34 |
Dyrcona |
If you just install the plain old pgtap package on Ubuntu 16, it also tries to install Pg 9.6 if Pg 10 is already installed. |
| 11:48 |
Dyrcona |
And, then, you're back on a variation of the way you thought that things wouldn't work. |
| 11:49 |
|
jihpringle joined #evergreen |
| 11:50 |
Dyrcona |
Here's a question: Do we want translators to have to install the browsers for testing? I don't think so, but... |
| 11:51 |
Dyrcona |
Packagers, definitely. |
| 12:11 |
|
rjackson_isl_ joined #evergreen |
| 12:21 |
|
sandbergja joined #evergreen |
| 17:52 |
csharp |
ok, I just fixed the GPLS email lists issue (open-ils-general, -dev, -documentation, commits, etc.) - I deactivated some lists recently and removed a required configuration piece without noticing |
| 17:52 |
csharp |
systemd-- # for not telling me what's going on |
| 17:52 |
csharp |
so you may see an influx of messages |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:05 |
Bmagic |
csharp++ |
| 18:26 |
|
jihpringle joined #evergreen |
| 18:28 |
jihpringle |
Bmagic: re: your acq questions when I've seen it it's because the activation timed out partway through (activating again usually fixes it) or it's run into an item it doesn't like, such as one attached to a deleted record |
| 02:29 |
|
cmalm joined #evergreen |
| 03:09 |
|
kip joined #evergreen |
| 05:54 |
|
dbwells_ joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:54 |
|
rfrasur joined #evergreen |
| 07:02 |
|
agoben joined #evergreen |
| 07:15 |
|
rjackson_isl joined #evergreen |
| 10:37 |
|
sandbergja__ joined #evergreen |
| 10:57 |
gmcharlt |
csharp: I've updated 1811710 |
| 11:04 |
csharp |
gmcharlt: responded |
| 11:05 |
gmcharlt |
csharp: thanks |
| 11:05 |
gmcharlt |
two more questions |
| 11:06 |
gmcharlt |
1. is the test DB in question still around? if so, I'd like to see the result of select * from pg_attribute where attname = 'hopeless_date'; |
| 11:06 |
gmcharlt |
2. is it possible that the test DB would have originated from a database that was created back in the pre-Pg-8.3 days? |
| 11:07 |
gmcharlt |
in particular, of a lineage that would have be upgraded via pg_upgrade, not pg_dump & restore? |
| 11:07 |
csharp |
1. the DB is around, but I dropped the hopeless columns to fully roll back the changes |
| 11:08 |
csharp |
2. I've used pg_upgrade to go from 9.3 -> 9.5, then 9.5 -> 9.6, but it was all pg_dump/pg_restore before that |
| 11:09 |
gmcharlt |
ok, in that DB, what attypid values do you get from select * from pg_attribute where attname = 'request_time';? |
| 15:54 |
Dyrcona |
And, with that, I'm signing out for the day. |
| 16:00 |
jeffdavis |
the fix for bug 1848550 will mitigate open-ils.actor drone exhaustion |
| 16:00 |
pinesol |
Launchpad bug 1848550 in Evergreen "Cache settings more aggressively in web client" [Undecided,Confirmed] https://launchpad.net/bugs/1848550 |
| 16:01 |
jeffdavis |
I still need to test the Angular parts on that one |
| 16:05 |
|
rfrasur joined #evergreen |
| 16:18 |
|
mmorgan joined #evergreen |
| 16:23 |
dbs |
jeffdavis++ |
| 17:03 |
|
mmorgan left #evergreen |
| 17:34 |
|
jihpringle joined #evergreen |
| 17:35 |
|
rfrasur joined #evergreen |
| 18:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:20 |
|
sandbergja_ joined #evergreen |
| 19:26 |
|
sandbergja_ joined #evergreen |
| 02:18 |
|
cmalm joined #evergreen |
| 02:29 |
|
cmalm_ joined #evergreen |
| 02:43 |
|
cmalm joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:43 |
|
_bott_ joined #evergreen |
| 06:57 |
|
agoben joined #evergreen |
| 07:13 |
|
rjackson_isl joined #evergreen |
| 11:02 |
dbs |
We had two separate instances of clark-kent.pl running, each with --concurrency 2 |
| 11:30 |
|
sandbergja joined #evergreen |
| 11:49 |
|
_bott_ joined #evergreen |
| 11:59 |
gmcharlt |
csharp: re 1811710, do you happen to still have final fm_IDL.xml as installed on your test system? |
| 12:02 |
|
jihpringle joined #evergreen |
| 12:05 |
jeff |
Thinking about the physical logistics of distributing a large number of new patron cards (>5000): has anyone here ordered cards from somewhere where they're pre-stuck to a card / mailer, or something creative like that? |
| 12:05 |
jeff |
or used a removable sticker on the card? |
| 14:00 |
csharp |
gmcharlt: https://pastebin.com/a263dZ74 |
| 14:12 |
jeffdavis |
autogen? |
| 14:13 |
|
Christineb joined #evergreen |
| 14:14 |
csharp |
jeffdavis: I ran autogen - no dice |
| 14:15 |
csharp |
after we upgrade this weekend, we'll put it back on our test server so we can suss it out non-forensically |
| 14:48 |
|
_bott_1 joined #evergreen |
| 15:04 |
jihpringle |
sandbergja: is LP 1852782 the best bug to add the screenshot to? |
| 15:04 |
pinesol |
Launchpad bug 1852782 in Evergreen "Angular MARC Editor Part 2 -- Enriched Editor" [Wishlist,New] https://launchpad.net/bugs/1852782 |
| 16:28 |
|
sandbergja_ joined #evergreen |
| 17:12 |
|
mmorgan left #evergreen |
| 17:32 |
|
stephengwills left #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 20:47 |
|
stephengwills joined #evergreen |
| 20:48 |
|
stephengwills left #evergreen |
| 20:54 |
|
sandbergja joined #evergreen |
| 01:23 |
|
cmalm joined #evergreen |
| 01:53 |
|
sandbergja joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Failed Create Evergreen Database <http://testing.evergreen-ils.org/~live//archive/2020-01/2020-01-10_04:00:02/test.41.html> |
| 06:57 |
|
rfrasur joined #evergreen |
| 07:26 |
|
rjackson_isl joined #evergreen |
| 08:28 |
pastebot |
"phasefx" at 168.25.130.30 pasted "re: pgtap failure" (34 lines) at http://paste.evergreen-ils.org/10119 |
| 08:31 |
csharp |
investigating an issue where bib TCNs are getting changed to the record ID upon saving - I've ruled out BibCommon.pm as a possible cause - now looking at marcedit.js |
| 08:32 |
csharp |
apparently only happening when editing an existing record - imports from z39.50 are not affected as far as I understand |
| 08:32 |
csharp |
confirmed - only already existing records |
| 08:32 |
|
Dyrcona joined #evergreen |
| 08:33 |
csharp |
(on 3.4 testing server, btw) |
| 08:35 |
|
sandbergja joined #evergreen |
| 08:40 |
|
mantis1 joined #evergreen |
| 08:44 |
|
_bott_ left #evergreen |
| 10:54 |
gmcharlt |
upshot: open-ils.cat.biblio.record.xml.update appears to be what's needed |
| 10:55 |
gmcharlt |
also, this affects both the AngularJS and Angular sides |
| 10:57 |
* berick |
follows conversation |
| 10:58 |
csharp |
gmcharlt++ |
| 11:04 |
csharp |
gmcharlt: I can confirm that changing that call to xml.update works |
| 11:53 |
|
mmorgan joined #evergreen |
| 11:57 |
|
jihpringle joined #evergreen |
| 11:57 |
csharp |
gmcharlt: I added a branch to bug 1859191 for review - not sure about how to test Angular cataloging |
| 11:57 |
pinesol |
Launchpad bug 1859191 in Evergreen "Editing and saving MARC record changes the TCN value" [High,Confirmed] https://launchpad.net/bugs/1859191 |
| 12:10 |
|
rfrasur joined #evergreen |
| 12:12 |
|
yboston joined #evergreen |
| 12:19 |
|
aabbee left #evergreen |
| 16:34 |
|
dbwells joined #evergreen |
| 16:46 |
|
jvwoolf left #evergreen |
| 17:04 |
|
mmorgan left #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:14 |
|
dbwells_ joined #evergreen |
| 18:37 |
|
_bott_ joined #evergreen |
| 21:18 |
|
sandbergja joined #evergreen |
| 02:26 |
|
cmalm joined #evergreen |
| 02:50 |
|
cmalm joined #evergreen |
| 03:11 |
|
cmalm joined #evergreen |
| 06:00 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:06 |
|
agoben joined #evergreen |
| 07:15 |
|
rjackson_isl joined #evergreen |
| 08:16 |
|
alynn26 joined #evergreen |
| 14:09 |
abneiman |
probably so. +1 to collab alynn26 |
| 14:10 |
dluch |
That would be great. And maybe we could do some version as an online thing for folks who can't be at conference |
| 14:10 |
abneiman |
dluch: that's a good idea |
| 14:10 |
dluch |
abneiman++ alynn26++ |
| 14:11 |
dluch |
#3, abneiman: I know you have prodded gmcharlt about the test server. More on that shortly, unless you want to say anything now? |
| 14:11 |
abneiman |
nope nothing from me |
| 14:11 |
dluch |
abneiman++ |
| 14:11 |
dluch |
#4, sandbergja, gmcharlt, and/or Dyrcona: how's work on setting up a git repo for ui (and maybe layouts) coming? |
| 14:15 |
Bmagic |
tkatie217: Thank you :) |
| 14:15 |
dluch |
remingtron++ |
| 14:15 |
Bmagic |
remingtron++ |
| 14:16 |
dluch |
#6, Everyone will test the new Antora server and email the DIG list (or IRC) with problems (or suggestions). I don't think I've seen many (any?) emails with problems or suggestions. How is testing going? (Also, more on Antora shortly.) |
| 14:17 |
dluch |
crickets... |
| 14:17 |
alynn26 |
It looks great. |
| 14:17 |
Bmagic |
:) |
| 14:17 |
dluch |
I agree, it does look great |
| 14:17 |
remingtron |
there are still little bugs hiding everywhere, so please test! |
| 14:18 |
dluch |
I'll keep that on as an action item, then. :-) |
| 14:18 |
Bmagic |
yep - lots of hidden "gems" in there |
| 14:18 |
dluch |
#action Everyone will test the Antora server and email the DIG list (or IRC) with problems (or suggestions). |
| 14:18 |
alynn26 |
Home icon needs updating. If you click on it it goes to the "it's powered by Antora". |
| 14:19 |
remingtron |
alynn26++ #testing! |
| 14:19 |
Bmagic |
lol |
| 14:19 |
Bmagic |
I threw that page on there in the very very beginning |
| 14:19 |
dluch |
Good find, lol |
| 14:22 |
tkatie217 |
+remingtron that would make sense :) |
| 14:22 |
alynn26 |
I think it does, if you check out the Glossary it says Glossary. |
| 14:23 |
sandbergja |
alynn26: I think the glossary looks so cool in antora. :-) |
| 14:23 |
dluch |
navlabels++ :-D |
| 14:23 |
dluch |
Okay, everyone keep up the good testing! Let's move on |
| 14:23 |
tkatie217 |
+1 to glossary! gorgeous! |
| 14:24 |
dluch |
+1 The glossary really is awesome |
| 14:24 |
dluch |
#info Update on Documentation server move |
| 17:07 |
|
mmorgan joined #evergreen |
| 17:09 |
|
jihpringle joined #evergreen |
| 17:12 |
|
mmorgan left #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:13 |
|
stephengwills left #evergreen |
| 18:24 |
|
khuckins joined #evergreen |
| 20:18 |
|
sandbergja joined #evergreen |
