Time |
Nick |
Message |
01:22 |
|
beanjammin joined #evergreen |
06:30 |
pinesol_green |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
08:06 |
|
Dyrcona joined #evergreen |
08:40 |
|
idjit joined #evergreen |
08:46 |
Dyrcona |
Interesting change in Firefox... |
08:47 |
Dyrcona |
I visited the web staff client on a local test vm after rebuilding it and using a new, self-signed certificate. |
08:48 |
Dyrcona |
Firefox went to offline mode until I clicked on the info button in the location bar, cleared the old security exception, and added an exception for the new certificate. |
08:48 |
Dyrcona |
I think it used to go straight to "your connection is insecure" when the cert. changed. |
08:49 |
Dyrcona |
This is Firefox 60.0.2 on Ubuntu 18.04. |
08:50 |
Dyrcona |
And, yeah, I remembered to do the exception for port 7682, and that seemed to work like it used to. |
10:45 |
|
beanjammin joined #evergreen |
13:19 |
|
jlamos joined #evergreen |
13:22 |
idjit |
happy caturday, #evergreen https://i.imgur.com/CZJSOWm.gifv |
13:38 |
Dyrcona |
Hmm... Edit items seems to be broken, at least in Firefox. |
13:38 |
Dyrcona |
Well, getting there from Item Status. |
13:38 |
Dyrcona |
I was able to successfully edit an item from Item Status once, after that, every try bring up an empty screen. |
13:39 |
Dyrcona |
Maybe this warrants a bug? |
13:40 |
Dyrcona |
Same thing happens in Chromium. |
13:40 |
Dyrcona |
My first try brought up an empty edit screen. |
13:41 |
Dyrcona |
This is stock master. Guess I'll open a bug. |
13:45 |
idjit |
how'd you open the "edit" option? was it in a new tab or same tab? |
13:48 |
idjit |
is bug 1761276 related? |
13:48 |
pinesol_green |
Launchpad bug 1761276 in Evergreen "Odd behaviour when clicking on title hyperlink " [High,Confirmed] https://launchpad.net/bugs/1761276 |
13:54 |
idjit |
and are you trying to edit multiple items at the same time? it works for me (on master, concerto data)... |
13:54 |
idjit |
(chrome) |
15:09 |
|
rlefaive joined #evergreen |
15:13 |
|
rlefaive left #evergreen |
15:19 |
|
rlefaive joined #evergreen |
15:22 |
|
rlefaive joined #evergreen |
15:49 |
Dyrcona |
idjit: Sorry I missed you earlier, I went for a walk. |
15:49 |
Dyrcona |
I describe how I opened it in bug 1777267. |
15:49 |
pinesol_green |
Launchpad bug 1777267 in Evergreen "Web Client: Edit Items from Item Status comes up empty" [Undecided,New] https://launchpad.net/bugs/1777267 |
15:50 |
idjit |
'sall good. i saw the bug, but didn't read carefully enough to know if my replication efforts were sufficient |
15:50 |
Dyrcona |
I would not be surprised if no one else can replicate it, though I don't think there's anything particularly special about my setup. |
15:51 |
idjit |
the only oddity i observed was when opening the editor for two copies, it opened two tabs. one of the tabs listed both copies, with several fields empty (i guess because they weren't the same), and the other tab with just one of the copies. |
15:51 |
Dyrcona |
I pulled master Evergreen this morning, did the npm update, npm run build, make, make install dance. |
15:51 |
|
rlefaive joined #evergreen |
15:51 |
idjit |
oh, i skipped the npm stuff. i'll give that a shot. |
15:51 |
Dyrcona |
I only opened 1 at a time and it pretty much always came up empty. |
15:52 |
* Dyrcona |
wonders if build-prod would make a difference. |
15:53 |
* Dyrcona |
is working on a quote for something where editing copies is related, but not the main thing, so I wanted to check the behavior of changing to and from a certain status. |
15:53 |
Dyrcona |
It worked, once I got the item data to load. :) |
15:54 |
idjit |
did you notice any javascript errors on browser console? |
15:54 |
Dyrcona |
Nope. |
15:55 |
Dyrcona |
Chromium had some SSL errors that it throws up on every screen, and something about a 404 for a minimized css file that also comes up everywhere. |
15:55 |
Dyrcona |
Firefox had no errors at all. |
15:56 |
Dyrcona |
Just a warning for https://xenial.sigio.com/js/ui/default/staff/build/css/bootstrap.min.css, which only shows up on certain screens and not on the Vol/Copy Editor. |
15:56 |
Dyrcona |
That's the same css file that Chromium complains about. |
16:00 |
Dyrcona |
I'm trying again with npm run build-prod to see if that makes a difference. One hopes it shouldn't. |
16:01 |
Dyrcona |
I expected the source map error for bootstrap.min.css to go away, but it didn't. |
16:02 |
Dyrcona |
OK. This time it loaded on the first shot with 1 copy in Firefox, but that happened last time, too. |
16:02 |
Dyrcona |
It was when I tried to open one after closing the tab that it started happening, IIRC. |
16:02 |
idjit |
it still works for me after the npm update/npm run build. chrome 65.0 |
16:02 |
idjit |
but i'm logged in as admin. what's the pass for this user you mention? |
16:03 |
Dyrcona |
br1bbrown / beverlyb1234 |
16:03 |
Dyrcona |
You know about the list of concerto users? |
16:04 |
Dyrcona |
It seems to be working for me after doing npm run build-prod. |
16:04 |
Dyrcona |
I wonder if I just got a bad build somehow, even though it said everything was OK and npm run test passed? |
16:05 |
idjit |
yeah, this user still works for me. |
16:05 |
* Dyrcona |
tries with Chromium, again. |
16:05 |
* idjit |
tries with firefox |
16:05 |
Dyrcona |
OK. Second time I edit the same copy from Item Status fails. |
16:06 |
Dyrcona |
And, third time works. Seems inconsistent. |
16:09 |
idjit |
firefox worked for me. |
16:09 |
Dyrcona |
It seems to be working in Chromium for me, but I should add another copy and edit that, then go back and edit the first one again. That seemed to trigger it last time on Firefox. |
16:10 |
idjit |
i haven't been saving edits. just opening and closing the window. |
16:10 |
Dyrcona |
I've been saving. |
16:10 |
Dyrcona |
Just opening the other copy gives me a blank Vol/Copy Edit tab. |
16:11 |
Dyrcona |
I mean the fields are there but empty/default values. |
16:11 |
Dyrcona |
Then, if I hit reload, it shows the copy values. |
16:12 |
Dyrcona |
That behavior is consistent with CONC4000038 in Chromium for me right now. |
16:12 |
Dyrcona |
And reload doesn't always work. |
16:13 |
idjit |
erm.. where's reload? |
16:14 |
idjit |
if there's a button, like refresh on the patron editor, i'm not seeing it. or are you refreshing the browser window? |
16:16 |
Dyrcona |
Refreshing the browser window. |
16:16 |
idjit |
ah, ok |
16:16 |
idjit |
i was thinking of the "reload" button in the xul client. |
16:16 |
idjit |
which.. does not exist here. |
16:17 |
Dyrcona |
Right, using the browser's control. |
16:17 |
Dyrcona |
I have to step away for a bit. |
16:19 |
idjit |
ok. i haven't managed to replicate it yet |
16:26 |
idjit |
worked for me on mlnc4.noblenet.org, too in chrome. ff, however, complains about the certificate and refuses to establish a websocket connection, so i can't log in. O_o |
16:27 |
|
jlamos joined #evergreen |
16:27 |
idjit |
"Could not verify this certificate because the issuer is unknown." |
17:32 |
|
rlefaive joined #evergreen |
17:41 |
Dyrcona |
idjit: You have to accept the certificate twice if no proxy is in place with Firefox. |
17:41 |
Dyrcona |
Once as normal, and also for https://host.domain.tld:7682/ |
17:42 |
idjit |
ah, ok. i'll see about testing that out more on monday, then. |
17:42 |
Dyrcona |
I was seeing it more in Chromium than in Firefox just before I had to leave last time. |
17:43 |
idjit |
well hopefully someone can replicate it. i couldn't. gotta run though, good luck! |
17:44 |
Dyrcona |
I get these in Chromium, but I think they can be ignored: |
17:44 |
Dyrcona |
An SSL certificate error occurred when fetching the script. |
17:44 |
Dyrcona |
Failed to load resource: net::ERR_CERT_AUTHORITY_INVALID |
17:44 |
Dyrcona |
That's after accepting the cert, too. |
17:45 |
* Dyrcona |
avoids getting started on certificates and authorities, etc. :) |
17:45 |
idjit |
i don't get any ssl errors on my test instance. |
17:47 |
Dyrcona |
Well, I do in Chromium 66 but not Firefox 60. Everything seems to work, mostly. |
17:48 |
Dyrcona |
Anyway, I'm moving on to something completely different, i.e. not Evergreen. I filed a bug and I still see the behavior more or less as described. |
17:49 |
|
beanjammin joined #evergreen |
18:32 |
pinesol_green |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
19:03 |
|
beanjammin joined #evergreen |
19:14 |
Dyrcona |
Don't you hate it when you swear you had a file with certain information in it, but now you can find no trace of it? |
19:18 |
Dyrcona |
I'm also guessing that if I deleted it, my oldest backup is likely too recent to have it. |
19:57 |
|
rlefaive joined #evergreen |