| Time |
Nick |
Message |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 07:21 |
|
rjackson_isl_hom joined #evergreen |
| 08:30 |
|
Dyrcona joined #evergreen |
| 08:46 |
|
collum joined #evergreen |
| 08:48 |
JBoyer |
Looks like the 3.6.2-3.6.3 version upgrade script only exists in the 3.6.3 tarball (if you upgrade by just running all of the individual scripts you're fine). I'll be pushing that to all of the necessary branches here in a minute. |
| 08:54 |
|
mmorgan joined #evergreen |
| 08:55 |
|
rfrasur joined #evergreen |
| 09:04 |
pinesol |
[evergreen|gmontimantis] docs: updating batch_importing_MARC.adoc - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=0cb6086> |
| 09:11 |
|
mantis joined #evergreen |
| 09:17 |
mmorgan |
Is anyone aware of new white screen issues? We're getting multiple reports. Login, only the top menu bar shows. Clear cache, or possibly just refresh and the screen loads. Similar blank screens navigating around the client, a clear cache or refresh loads the screen. |
| 09:17 |
mmorgan |
This is happening on some, not all, computers. |
| 09:20 |
JBoyer |
mmorgan, I've seen that after not logging into a site for a long time, likely post updates. Since I've not seen it beyond that initial load I assume in my case at least it's cache related. |
| 09:23 |
Dyrcona |
mmorgan: Yes, that sounds like typical post-upgrade type of thing. Our default cache settings are way too aggressive. |
| 09:27 |
mmorgan |
Our last upgrade was Oct. 4, and we didn't start getting these reports until November, so I don't think it's upgrade related. This is happening on mostly new computers. |
| 09:28 |
JBoyer |
nothing useful in the console? (Or not happening to someone who thinks to check that before reloading?) |
| 09:28 |
pinesol |
[evergreen|Jason Boyer] Forward Port 3.6.3 Upgrade Script - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=f7026b9> |
| 09:28 |
JBoyer |
"in a minute" the comedy is effortless. |
| 09:29 |
mmorgan |
:) |
| 09:29 |
alynn26_away |
We dp see it here, usually we trace it to HATCH having issues with a Chrome update. We have them uninstall Hatch and reinstall hatch and that works for a time. |
| 09:29 |
JBoyer |
git fa |
| 09:29 |
JBoyer |
opos |
| 09:29 |
alynn26_away |
dp/do |
| 09:29 |
Bmagic |
mmorgan: a browser "hard refresh" (CTRL+SHIFT+R) does the trick 99% of the time. Mind you, it needs to be done on several pages throughout the staff client as you encounter strange page loads/dropdowns missing items/etc |
| 09:30 |
JBoyer |
Bmagic, I think the concern is "why" not how, especially with no recent changes. |
| 09:30 |
mmorgan |
JBoyer: Haven't been able to get info from the console yet. |
| 09:30 |
mmorgan |
We've had folks reinstall hatch, but it hasn't helped. |
| 09:31 |
Dyrcona |
mmorgan: I think JBoyer meant the JavaScript console in the browser's dev tools. |
| 09:31 |
mmorgan |
Dyrcona: Right. Staff at our libraries generally don't go there :) |
| 09:31 |
Dyrcona |
Chrome 96 threw up a bunch of "new" errors when I was looking at something yesterday. |
| 09:32 |
Bmagic |
I've not come up with a good "why" other than "it does that sometimes" - it's definitely local browser cache related. Stale local Javascript code, etc. |
| 09:32 |
mmorgan |
Going to ask our pc support folks to check the JavaScript console. |
| 09:33 |
Dyrcona |
Bmagic: See what i said about out cache settings earlier, plus the web just sucks. |
| 09:33 |
Dyrcona |
s/out/our/ |
| 09:34 |
Bmagic |
right, I was going to reference your words but didn't |
| 09:35 |
Dyrcona |
Ha! |
| 09:36 |
Dyrcona |
It's always convenient to blame browser updates, and they do very often cause this. |
| 09:36 |
mmorgan |
Wish I could reproduce it on my workstation. I have the same version of Chrome, and hatch, and can't make it happen. It's happening consistently on these workstations. They're needing to refresh/clear cache constantly to get the screen back. |
| 09:36 |
Dyrcona |
mmorgan: They will probably have to open the dev tools, go to storage, and nuke all of the cache and settings for Evergreen. |
| 09:36 |
mmorgan |
Dyrcona: Yes, have seen browser updated cause similar issues, but this doesn't seem to be update related. |
| 09:37 |
Dyrcona |
Well, Chrome 96 just came out recently and reportedly has a lot of problems with various sites. |
| 09:37 |
Bmagic |
One way to simulate it, is to setup an Evergreen server on a previous version of Evergreen. Like several versions old. Update your hosts file to point your domain name to this test server. Hard refresh the login page, login, hard refresh a few pages. This gets the old JS code into your browser |
| 09:37 |
Bmagic |
then, change your hosts file back so that it points to production, and try to login |
| 09:39 |
mmorgan |
Bmagic: I don't feel like this is upgrade related, reports started a month after our last upgrade. |
| 09:41 |
JBoyer |
I usually suspect things like chrome addons, some of them get pretty wild. (And they sync if you login to the browser, so even if a machine is fairly new that could still happen.) |
| 09:41 |
collum |
We had it happen on two machines a couple of weeks ago, and again this week on the same two machines. We can't figure out what is different with these two machines. |
| 09:42 |
collum |
JBoyer++ add ons might be a possibility |
| 09:42 |
Dyrcona |
We get reports of it sometimes in between upgrades, too. I chalk it up to bugs. |
| 09:43 |
mmorgan |
collum: That sounds like our experience. It's a chronic problem on selected machines. |
| 09:43 |
Bmagic |
Same here, we see white screen/browser issues throughout the year. I figured it was "normal" and cured with browser fiddling |
| 09:44 |
Dyrcona |
Well, yeah, I meant browser or O/S bugs, not necessarily Evergreen bugs, but I wouldn't rule those out, either. |
| 09:45 |
Dyrcona |
When you get beneath the surface, this stuff is incredibly complicated. |
| 09:45 |
mmorgan |
We also see white screen issues not infrequently. Staff at our libraries are very familiar with clearing cache :) |
| 09:47 |
mmorgan |
But this behavior is different in that they need to clear cache (or refresh) consistently while using evergreen to get the screens to load. |
| 09:48 |
Bmagic |
mmorgan: the same page needs hard refreshed every* time to load it? That would be new to me |
| 09:48 |
mmorgan |
We've checked add ons. I'm going to ask a few to try incognito mode. |
| 09:48 |
Dyrcona |
@blame Chrome |
| 09:48 |
pinesol |
Dyrcona: Chrome tests their code on the LIVE SERVERS, then blames the user. SAD! |
| 09:49 |
JBoyer |
That is significantly more annoying. If Hatch is installed have they verified that it's the same version as is currently available to download today? It should either be the newest available or not installed. (turning it off isn't enough anymore) |
| 09:49 |
mmorgan |
Bmagic: Yes, not sure if it's *every* time, but frequently while using evergreen. And I am not sure from reports whether a hard refresh or just a refresh is necessary. But some sort of refresh is. |
| 09:50 |
Bmagic |
I wonder if it's packet loss |
| 09:51 |
Bmagic |
If the library has an inconsistent connection to the Evergreen server, page loads may not deliver 100% of the JS code required, and a refresh (enough times) gets the code delivered |
| 09:51 |
Dyrcona |
Could be anything...Phase of the moon and its gravitational pull disturbing the electrons. |
| 09:52 |
alynn26 |
I thought packet loss, Always blamed Chrome, or chrome extension, I did get that here on my computer the other day, and after I turned off all of my extensions, And everythng worked after that. But I had been on several different versions of Evergreen that day between upgrading different servers and testing |
| 09:52 |
mmorgan |
Bmagic: Doesn't happen on all computers. Happens consistently on "Circ Desk 1" but "Circ Desk 2" is fine. |
| 09:53 |
Bmagic |
It still could be packet loss for that one machine. Faulty cable/wifi adapter,etc |
| 09:54 |
Dyrcona |
Faulty transistor, blown capacitor, bad solder.... You name it. |
| 09:55 |
mmorgan |
If it was just one or two computers at one library, could be, but we're getting increasing independent reports from different libraries. |
| 09:56 |
* mmorgan |
needs to run to a meeting. We'll have our pc support techs do some more troubleshooting. |
| 09:57 |
Dyrcona |
Chrome 96 |
| 11:02 |
JBoyer |
I mean, http is TCP so it's not like there are packets not getting there, they may just be delayed / re-sent. |
| 11:29 |
|
mantis1 joined #evergreen |
| 11:30 |
Dyrcona |
So the 0824.item_import_defaults.pg fails on Pg 11+, but based on what I'm seeing on Pg 11, it should also fail on Pg 10, since I'm getting an invalid circ_modifier error and no circ modifiers seem to exist in a stock database. |
| 11:34 |
|
mantis joined #evergreen |
| 11:36 |
Dyrcona |
OIC. I misunerstood what the test is doing. It's actually looking at the failure message. |
| 11:36 |
Dyrcona |
So, it doesn't really test if items were created or not. |
| 11:37 |
|
eady joined #evergreen |
| 11:42 |
|
troy joined #evergreen |
| 11:42 |
|
jeffdavis joined #evergreen |
| 11:44 |
|
ejk joined #evergreen |
| 11:51 |
|
Christineb joined #evergreen |
| 11:57 |
|
jihpringle joined #evergreen |
| 12:14 |
* Dyrcona |
goes to comment on a bug. Reads through the comments and sees that he already commented some months ago. |
| 12:36 |
jeff |
:-) |
| 13:20 |
|
jihpringle joined #evergreen |
| 13:55 |
Dyrcona |
I'm going to say it again, because it can't be said often enough: We're doing it wrong. |
| 13:58 |
Dyrcona |
Maybe I should just close the bug with "Won't Fix" and a comment: We're like, doomed. |
| 13:58 |
Dyrcona |
Ha! Wrong tab.... but whatever. |
| 14:00 |
Dyrcona |
Anyway, long story short, our XPATH is totally hosed because PostgreSQL fixed their implementation, so most of our XPATH expressions need to be totally revamped. I got some working, but others have just made it worse. |
| 14:01 |
Dyrcona |
I suspect that we're going to have to figure out how to use namespaces properly. |
| 14:02 |
Dyrcona |
So, I'm scrapping my branch and starting over. Nothing like wasting a week, but at least I know what doesn't work. |
| 14:03 |
jeffdavis |
Doesn't sound like wasted time to me, just irritatingly slow. |
| 14:03 |
jeffdavis |
I'm really glad you're looking at that stuff. |
| 14:54 |
Bmagic |
Dyrcona++ # yes, I second that! You're doing awesome work! |
| 14:54 |
Bmagic |
Dyrcona++ # and again for good measure |
| 15:35 |
csharp_ |
Dyrcona++ |
| 15:41 |
Dyrcona |
Well, authority.generate_overlay_template is fixed. |
| 15:56 |
Dyrcona |
So, I think we need to rethink our "'working' code wins" mantra, 'cause what used to work doesn't work any more. |
| 16:32 |
|
jihpringle joined #evergreen |
| 17:08 |
|
mmorgan left #evergreen |
| 17:31 |
|
jihpringle joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 18:08 |
|
jihpringle joined #evergreen |
