Evergreen ILS Website

IRC log for #evergreen, 2022-12-29

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
08:32 BDorsey joined #evergreen
08:42 kworstell-isl joined #evergreen
08:45 Dyrcona joined #evergreen
08:48 tsadok joined #evergreen
10:26 Dyrcona miker: ping
11:29 kworstell-isl joined #evergreen
12:31 BDorsey joined #evergreen
12:41 Dyrcona gmcharlt: ping
13:00 Dyrcona If anyone sees a message from the working repository about "too many unreachable loose objects" and needing to remove gc.log, I did a remote prune, but I can't get in to remove gc.log, so I think the issue is resolved, but the log is hanging around.
13:14 berick thanks Dyrcona
13:45 pinesol News from commits: LP#1908455 - Prevent multiple server processes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=f9d445​a511b59cbae88bd9a28dd253cd68e49840>
14:09 JBoyer I suspect we should also remove some of the more ancient working branches. They're not necessarily large individually, but they do add up.
14:11 Dyrcona Yeahp. For those who don't know, you can delete your own branches by pushing an empty branch git push working :user/yourname/remotebranchname. Where user could also be "collab."
14:19 BDorsey_ joined #evergreen
14:19 BDorsey_ joined #evergreen
14:24 berick or create a new working-v2 repo and keep the old one, maybe read-only
14:24 Dyrcona And move to Github or GitLab at the same time?
14:32 Dyrcona If we move to Github or to GitLab, we wouldn't need the working repo.
14:35 Dyrcona We could eventually replace Lp bugs with issues and pull requests.
14:44 JBoyer True. I think there's enough support (or rather, not enough resistance) to make that move.
14:44 JBoyer It needs a champion though, someone who can put a schedule together, execute it - including the cat-herding of the rest of us that would be required - and I don't know who has that time.
14:45 Dyrcona Maybe in a few months....
14:45 Dyrcona I'm leaning towards Github.
14:45 JBoyer Same.
14:49 Dyrcona We've only been talking about it for 6 or 7 years.... :)
14:50 JBoyer Yup. Because of the above. :-/
14:51 JBoyer And I'm noticing that my bouncer doesn't correctly keep my messages, so this is quite an interesting monologue on my other devices.
14:51 Dyrcona Heh.
14:52 Dyrcona One of the big sticking points is moving away from Lp and all of the bugs with references to the working repo, but I think we can work something out.
14:52 Dyrcona #action Dyrcona to work out a migration plan to move to Github.
14:52 Dyrcona :)
14:53 JBoyer Even just forcing the working repos to RO and pushing new things to GH would work, (might make some collab/ stuff annoying I suppose, but that doesn't seem very common)
14:54 Dyrcona Yeah, very few collab branches are actually collab. It's possible to share repos/branches with others on Github, too.
14:59 jeff github parsing imported issues for username mentions and not having a way to specify issue numbers for imported issues are both annoying quirks/limitations.
14:59 jeff (not saying that either is insurmountable)
15:00 jeff re-evaluating how we merge/cherry-pick things would be good also.
15:01 Dyrcona jeff: Are you suggesting that we switch to merge? I'm not against it, just curious if that's what you mean.
15:01 * jeff prepares to place his tuit order
15:01 JBoyer GH seems to very strongly lean that way. (At least that seems to be all the various buttons want to do)
15:01 kworstell_isl joined #evergreen
15:02 JBoyer "Update this branch?" Sure, it could stand a rebase "Ok! Merged with upstream!" :-(
15:02 Dyrcona TBH I don't use the GUI much. I mostly do stuff locally and push.
15:03 JBoyer Unless we forbid use of the UI it's going to happen, so we may as well be amenable to the results.
15:03 JBoyer (whatever those may be)
15:03 Dyrcona I'm cool with merges. I use them on one of my local and some other projects that I dabble on.
15:06 * Dyrcona makes note: Add bit about working with merge commits to git presentation.
15:09 jeff Dyrcona: I'm not suggesting anything yet, other than noting that GitHub has opinions (and options for us to choose as default) and if the way we're doing things right now clashes somewhat, we might consider the options and reach some concensus/etc.
15:10 jeff i.e., do we want to use GitHub's idea of pull requests, do we want to default to merge/squash/rebase for those pull requests, do we want to discourage the use of the UI for marging/accepting said pull requests because of the side effects, etc.
15:11 Dyrcona Yeah. Wonder if we should start that conversation on the list and then have a vote on moving to Github during the conference?
15:25 JBoyer +1 to list leading into in-person.
15:28 Dyrcona I'll see if I can get the conversation started next week.
15:29 JBoyer Dyrcona++
15:35 kworstell-isl joined #evergreen
16:04 JBoyer joined #evergreen
16:05 JBoyer testing
16:05 berick ack: testing
16:05 JBoyer But not from my bouncer. :(
16:06 JBoyer A mystery for another year I suppose
16:10 JBoyer Speaking of, whoever is around today (Dycona++, berick++, jeff++) have a happy new year.
16:10 JBoyer Alas, typos. Dyrcona++
16:10 Dyrcona Happy New Year to you also, JBoyer++
16:11 Dyrcona berick++ jeff++
16:11 Dyrcona I'll be here tomorrow, too.
16:38 * Dyrcona starts winding down the day.
16:38 Dyrcona If I don't "see" you tomorrow, have a Happy New Year!
16:45 pinesol News from commits: LP1999954 Modal header color contrast fixes <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=e91f28​37865f1f22363c49acb40f241b2d589ed0>
17:15 pinesol News from commits: LP1995418 Shelving location selector won't dropdown <https://git.evergreen-ils.org/?p=E​vergreen.git;a=commitdiff;h=142a51​bb71a8ff922943be79fae3cc57ebe9d1ad>

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat