| Time |
Nick |
Message |
| 07:07 |
|
collum joined #evergreen |
| 07:20 |
|
Dyrcona joined #evergreen |
| 07:23 |
|
rjackson_isl_hom joined #evergreen |
| 08:08 |
|
BDorsey joined #evergreen |
| 08:33 |
|
mmorgan joined #evergreen |
| 08:40 |
|
jvwoolf joined #evergreen |
| 08:43 |
|
rfrasur joined #evergreen |
| 09:02 |
|
mantis1 joined #evergreen |
| 10:19 |
* mmorgan |
has a potential dev meeting topic, unless it can be answered here |
| 10:19 |
mmorgan |
Thoughts on backporting bug 1771636? |
| 10:19 |
berick |
@eightball here or there |
| 10:19 |
pinesol |
Launchpad bug 1771636 in Evergreen "Optionally use full library name in org unit selector" [Wishlist,Fix committed] https://launchpad.net/bugs/1771636 |
| 10:19 |
pinesol |
berick: No chance. |
| 10:19 |
berick |
@decide here or there |
| 10:19 |
pinesol |
berick: go with here |
| 10:19 |
mmorgan |
:) |
| 10:20 |
berick |
+1 to backporting |
| 10:20 |
berick |
we're using it here on 3.6 |
| 10:23 |
mmorgan |
berick: Thanks for the feedback! |
| 10:27 |
Dyrcona |
I'm opposed to backporting it on the grounds that it is a new feature, i.e. a deliberate change in behavior that wasn't actually a bug. |
| 10:28 |
Dyrcona |
But, don't let my opposition stop you. :) |
| 10:28 |
berick |
Dyrcona: you're not wrong |
| 10:28 |
mmorgan |
:) |
| 10:28 |
* mmorgan |
is in favor since it resolves a staffcatalogblocker bug. |
| 10:30 |
Dyrcona |
Hmm. It is rectifying a change in the Angular Staff Catalog versus TPAC or BooPAC? If that's the case, I could consider it a bug. |
| 10:30 |
* mmorgan |
*could* argue against it being a new feature since the old staff catalog did show full library name... |
| 11:04 |
Dyrcona |
Anyway, I guess I'm not really opposed to backporting the full library name in org unit selector patches. |
| 11:05 |
Dyrcona |
Also, following up my monologues about encoding. I totally missed that there is an Encoding::Guess module. I may have to play with that to see if it would be useful. |
| 11:18 |
|
jihpringle joined #evergreen |
| 11:44 |
|
mantis1 joined #evergreen |
| 12:30 |
mantis1 |
Can anyone recommend a kiosk add on for Firefox? This would be for an opac station |
| 12:34 |
|
collum joined #evergreen |
| 12:34 |
bshum |
You didn't like the built in kiosk mode? -- https://support.mozilla.org/en-US/kb/firefox-enterprise-kiosk-mode |
| 12:35 |
bshum |
Or want more options |
| 12:36 |
bshum |
Oh, or you mean you want to also lock down the OS side |
| 12:37 |
mantis1 |
bshum: yeah and we're also running the OPACs on Mint |
| 12:37 |
mantis1 |
Can you do the same run commands with that OS? |
| 12:38 |
mantis1 |
I only found Windows examples when looking around |
| 12:40 |
bshum |
Yeah it should be possible to pass that same --kiosk to firefox when executing it in Linux |
| 12:41 |
bshum |
Locking down the OS probably takes more tweaks though |
| 12:53 |
mantis1 |
bshum++ |
| 12:53 |
mantis1 |
thank yuo! |
| 13:16 |
Dyrcona |
gmcharlt: I saw a message about needing to run git prune on the working repository when pushing to it just now. |
| 13:18 |
* csharp_ |
cool-guy-nods at bshum |
| 13:20 |
Dyrcona |
I've also seen something similar on my gitlab instance and haven't figured out how to resolve that, yet. |
| 13:36 |
* bshum |
waves at csharp_ |
| 13:50 |
JBoyer |
Dyrcona, I think that git prune has to be run on the actual repo on the gitlab server (either by the git user or whatever system account gitlab is using) |
| 13:50 |
JBoyer |
bshum++ |
| 14:03 |
Dyrcona |
JBoyer: Yes, but I haven't figure out how. There's some documentation that says it is run after X number of commits with a setting to control that, so I lowered the setting, but I still get a weekly email that one of my repos has failed its check. |
| 14:07 |
JBoyer |
Ah, sorry, didn't follow that part. |
| 14:10 |
Dyrcona |
It's no biggie. I was just throwing it out there as an aside. |
| 14:10 |
Dyrcona |
I'm not sure which account to login as on the community git server to run git prune on the working repo.... I suppose myself, if I have an account, and it's allowed to sudo as the git user? |
| 14:13 |
JBoyer |
Dyrcona, I would expect so, I wouldn't expect the git user to be allowed to login directly |
| 14:19 |
berick |
anyone else see intermittent cpu spikes in Chrome that last several minutes? chrome task manager shows "browser" as the culprit, not a specific tab. |
| 14:19 |
berick |
suppose it could be an extension |
| 14:23 |
Dyrcona |
berick: Not seeing anything unusual with Chrome today. |
| 14:24 |
berick |
this has been weeks :\ |
| 14:24 |
Dyrcona |
Chrome and Firefox both sometimes goes nuts. It's usually JavaScript on a page for me. |
| 14:34 |
JBoyer |
Dev meeting is in 30 minutes and we have essentially no topics. (mmorgan asked her question earlier and it sounds like the consensus was to do it.) |
| 14:34 |
JBoyer |
Thoughts on punting until September? |
| 14:35 |
mmorgan |
+1 from me (since my question was answered) :) |
| 14:36 |
* mmorgan |
may get pulled away anyway |
| 14:40 |
Dyrcona |
+1 to punting until September. I may actually get to look at test setup by the next meeting. |
| 14:41 |
|
jihpringle joined #evergreen |
| 14:51 |
|
tlittle joined #evergreen |
| 14:55 |
|
terranm joined #evergreen |
| 14:56 |
JBoyer |
Ok, with still no topics and no opposition I'm returning the next hour to everyone. Enjoy! |
| 14:57 |
terranm |
Hi - bye! |
| 14:58 |
mmorgan |
JBoyer++ |
| 15:02 |
gmcharlt |
Dyrcona: I'll take a look |
| 15:03 |
jvwoolf |
Anybody out there every had a problem with EBSCO suddenly spamming your servers? |
| 15:03 |
jvwoolf |
ever* |
| 15:06 |
|
jeff joined #evergreen |
| 15:08 |
jeffdavis |
jvwoolf: yep that's a common problem. We've never been heavily hit but I know others have blocked Ebsco IPs because of it. |
| 15:10 |
jeffdavis |
some past discussion here for example: http://irc.evergreen-ils.org/evergreen/2021-01-07#i_470409 |
| 15:15 |
jvwoolf |
jeffdavis++ |
| 15:24 |
gmcharlt |
Dyrcona: cleanup of working/Evergreen complete |
| 15:25 |
Dyrcona |
gmcharlt++ |
| 15:25 |
* Dyrcona |
has to figure out how to do that for gitlab. |
| 15:26 |
gmcharlt |
does gitlab (self-hsoted?) give you access to the underlying repo? |
| 15:26 |
gmcharlt |
if so, this is what I did for git.evergreen-ils.org: https://www.lynnbright.com/git-there-are-too-many-unreachable-loose-objects/ |
| 15:27 |
Dyrcona |
I tried finding the repos briefly, but honestly didn't look very hard. I'm sure that they are there somewhere. |
| 15:31 |
Dyrcona |
So, the repositories are managed by gitaly. Not sure if I should mess with them directly or not. |
| 15:34 |
jeffdavis |
Hmm, "too many unreachable loose objects"? I wonder if those git commands would work on my closet. |
| 15:36 |
berick |
or my brain |
| 15:38 |
Dyrcona |
Heh. |
| 15:39 |
Dyrcona |
Too many force pushes. I believe that's the main culprit, and I do quite a few of those. |
| 15:39 |
* Dyrcona |
also hasn't figured out where gitaly keeps the repos, but I also got distracted.... Squirrel! |
| 15:42 |
Dyrcona |
Ok. I have to use praefect...yadda, yadda. All so it's easy to cluster storage over multiple servers. A case of the default being overkill for a single, simple installation. :) |
| 15:43 |
Dyrcona |
I think I'll leave it up to the server setting of 100 commits or whatever I changed it to. |
| 16:02 |
|
jihpringle joined #evergreen |
| 16:24 |
jeff |
berick++ "or my brain" |
| 16:25 |
|
jvwoolf left #evergreen |
| 16:28 |
jeff |
I felt that this afternoon, drafting notes on a process several days after the fact, and a roller coaster "oh no, I did that all wrong! oh, wait. no, I didn't. I did it this other way after all, and it wasn't all wrong." |
| 16:42 |
Dyrcona |
jeff++ |
| 16:49 |
* Dyrcona |
calls it a day. |
| 17:16 |
|
mmorgan left #evergreen |
| 19:37 |
|
JBoyer_ joined #evergreen |
| 20:25 |
|
JBoyer_ joined #evergreen |
