| Time |
Nick |
Message |
| 00:51 |
|
jonadab joined #evergreen |
| 04:13 |
|
gmcharlt joined #evergreen |
| 07:43 |
|
collum joined #evergreen |
| 08:36 |
|
Dyrcona joined #evergreen |
| 08:38 |
|
mmorgan joined #evergreen |
| 09:17 |
|
smayo joined #evergreen |
| 09:24 |
Dyrcona |
Anubis strikes again..... |
| 09:25 |
Dyrcona |
@blame Bots |
| 09:25 |
pinesol |
Dyrcona: but I never knew until this day that it was Bots all along |
| 09:25 |
Dyrcona |
pinesol: It's bots all the way down. |
| 09:25 |
pinesol |
Dyrcona: git diff origin/hamster |
| 09:25 |
Dyrcona |
Hamster dance! |
| 09:27 |
|
smayo joined #evergreen |
| 09:29 |
Dyrcona |
TIL: It's actually "Hampster Dance." The word was deliberately misspelled. |
| 09:29 |
* Dyrcona |
ponders putting his own website back up somewheres... |
| 09:30 |
|
smayo joined #evergreen |
| 09:30 |
Dyrcona |
"I was there 3,000 years ago...." |
| 09:31 |
Dyrcona |
@who misses GeoCities |
| 09:31 |
pinesol |
eby misses GeoCities. |
| 09:33 |
smayo |
hampter |
| 09:33 |
Dyrcona |
hamper dance? .... um, no. |
| 09:34 |
* Dyrcona |
considers using an actual certificate with PostgreSQL because of rust and TLS. |
| 09:36 |
* Dyrcona |
gives it a try with snakeoil.pem. |
| 10:30 |
pinesol |
News from commits: LP#2096672: Simple Reports template folder <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f8113a263db93843466d06e27c1b920d08817f30> |
| 11:01 |
|
sandbergja joined #evergreen |
| 11:05 |
Dyrcona |
Whee! Got postgres_openssl to work with rust at least for my test database. |
| 11:17 |
Dyrcona |
TLS doesn't work with ssh tunnels. I get a hostname mismatch with the certificate. That's good to know, but TLS should also not be needed with a ssh tunnel. :) |
| 11:23 |
Dyrcona |
Added an option to set sslmode and I can connect over a ssh tunnel by setting it to "disable." :) |
| 11:26 |
Dyrcona |
Rust is OK as far as languages go. :) |
| 11:28 |
Dyrcona |
Think I'll reimplement one of my recent Perl utilities in Rust for a comparison. |
| 11:52 |
|
jihpringle joined #evergreen |
| 12:33 |
|
jihpringle joined #evergreen |
| 13:11 |
Bmagic |
Dyrcona++ |
| 13:18 |
* Dyrcona |
should probably refactor some of this into functions, but maybe later. :) |
| 13:24 |
Bmagic |
functions++ |
| 13:36 |
|
csharp_ joined #evergreen |
| 13:42 |
|
mantis1 joined #evergreen |
| 13:43 |
mantis1 |
I merged a doc branch but was getting TLS certificate warnings during pushes. What's the best way for me to check to see if the branches went through? |
| 13:50 |
eeevil |
FTR (but, especially probably for berick), I've been unexpectedly unavailable for ... well ... like, half of the summer. but I did finally get my "old man shakes fist at Redis clouds" branch up back in mid-July. I did LP it on the OpenSRF project, but figured I'd link it here to advertise, as well: https://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/miker/lp-2116980-redis-STREAMs-HA-LB-ACLs and https://bugs.launchpad. |
| 13:50 |
eeevil |
net/opensrf/+bug/2116980 |
| 13:54 |
eeevil |
I've been using it on my jankiest dev VM since then, and it seems to work. I want to try it with valkey, but packages aren't readily available for debian yet, AFAICT |
| 14:02 |
Dyrcona |
mantis1: TLS certificate warnings during pushes? Was that on Github? |
| 14:03 |
mantis1 |
yeah I realized that I didn't have my authenicator set up, but I think I was able to push something through at least on main - I see some evidence of it on GitHub |
| 14:03 |
mantis1 |
I did try to backport it to rel_3_15_4 and that's where I'm uncertain if that went through |
| 14:07 |
Dyrcona |
In your own repo on github? |
| 14:09 |
mantis1 |
I don't think so I pushed it to the github-evergreen repo |
| 14:09 |
mantis1 |
at least I hope it's the origin and not a local copy of it |
| 14:12 |
Dyrcona |
mantis1: I don't that repo accepts pushes. It doesn't show any commits since f8113a263db93843466d06e27c1b920d08817f30. |
| 14:13 |
Dyrcona |
Unrelated: writing postgres result to csv in rust is harder than it should be. |
| 14:13 |
mantis1 |
here's the set of instructions I used: https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:github-workflow |
| 14:16 |
Dyrcona |
mantis1; your origin is supposed to set to git git.evergreen-ils.org:Evergreen.git and not github. github-evergreen is the suggested local name to use for the github repo. Those instructions are meant for pulling pull requests from github into evergreen proper. |
| 14:19 |
mantis1 |
I guess I'm just surprised because I was able to use this set of instructions and it worked before |
| 14:21 |
Dyrcona |
Your origin was set properly then, and it is probably not set properly now. |
| 14:21 |
Dyrcona |
What's the output of `git remote -v` ? |
| 14:21 |
mantis1 |
shows the github.com address under github-evergreen and origin |
| 14:21 |
mantis1 |
upstream is the same |
| 14:22 |
* Dyrcona |
gives up on this rust utility. coercing the pg output into something that I can just dump into csv::Writer is more work than I want to go through for something that already works elsewhere. |
| 14:23 |
Dyrcona |
I'd like to see the output of the command. Otherwise, I can't really help you. |
| 14:23 |
Dyrcona |
The Evergreen repo on github doesn't accept pushes. It is updated when git.evergreen-ils.org is updated. |
| 14:29 |
Dyrcona |
mantis1: Maybe I don't understand what part of the process is breaking for you. |
| 14:33 |
mantis1 |
I think I can start with the fetch: git fetch github-evergreen pull/[PULL_REQ_NUMBER]/head:[BRANCHNAME] |
| 14:33 |
mantis1 |
I can successfully do it with a repo that's based off of the github repo but not from the repo hosted on gitolite |
| 14:33 |
Dyrcona |
did you add github-evergreen in the latter repo? |
| 14:34 |
Dyrcona |
git remote add github-evergreen https://github.com/evergreen-library-system/Evergreen.git |
| 14:36 |
mantis1 |
yeah that's been added |
| 14:36 |
mantis1 |
I can fetch and push |
| 14:36 |
mantis1 |
looking at this again, it did push but only to my local cloned repo on GitHub |
| 14:37 |
|
redavis joined #evergreen |
| 14:41 |
Dyrcona |
I got back to ask for the output of `git remote -v` If you're following the steps literally then, origin is probably your github repo. |
| 14:41 |
Dyrcona |
ugh... typos.. |
| 14:42 |
mantis1 |
github-evergreen https://github.com/evergreen-library-system/Evergreen.git (fetch) |
| 14:42 |
mantis1 |
github-evergreen https://github.com/evergreen-library-system/Evergreen.git (push) |
| 14:42 |
mantis1 |
gitolite gitgit.evergreen-ils.org:Evergreen.git (fetch) |
| 14:42 |
mantis1 |
gitolite gitgit.evergreen-ils.org:Evergreen.git (push) |
| 14:42 |
mantis1 |
origin https://github.com/gmontimantis/Evergreen.git (fetch) |
| 14:42 |
mantis1 |
origin https://github.com/gmontimantis/Evergreen.git (push) |
| 14:42 |
mantis1 |
upstream gitgithub.com:evergreen-library-system/Evergreen.git (fetch) |
| 14:42 |
mantis1 |
upstream gitgithub.com:evergreen-library-system/Evergreen.git (push) |
| 14:42 |
mantis1 |
ah I see now |
| 14:43 |
mantis1 |
so I'll need to amend the origin repo |
| 14:43 |
Dyrcona |
You can push to gitolite instead of origin and it should work. IIRC, you're a "docwriter." |
| 14:43 |
mantis1 |
ok but I'll need to fetch from github-evergreen? |
| 14:44 |
Dyrcona |
Well, I'd fetch from gitolite to make sure your copy is up to date. Otherwise, your push will be rejected. |
| 14:45 |
Dyrcona |
Might be better to swap gitolite and origin. |
| 14:45 |
Dyrcona |
Well, maybe rename origin and rename gitolite to origin. |
| 14:45 |
mantis1 |
ok thank you |
| 14:45 |
Dyrcona |
FWIW, I usually `git fetch --all` before doing any work. |
| 14:45 |
mantis1 |
Dyrcona++ |
| 14:54 |
mantis1 |
looks like I can't fetch that pullrequest from my new repo |
| 14:54 |
mantis1 |
I don't know if it's because of the merge I did on my local repo |
| 14:54 |
Dyrcona |
Probably. What's the message? |
| 14:55 |
mantis1 |
fatal: couldn't find remote ref pull/369/head |
| 14:55 |
mantis1 |
command: git fetch working pull/369/head:sip-docs-update |
| 14:55 |
mantis1 |
the working repo is off of the gitgit.evergreen-ils.org repo |
| 14:55 |
Dyrcona |
is working pointing to github or elsewhere? |
| 14:56 |
Dyrcona |
My working is gitgit.evergreen-ils.org:working/Evergreen.git, and that will not have the pull requests. They're only on github. |
| 14:59 |
mantis1 |
ok I added origin off of gitgit.evergreen-ils.org/Evergreen.git |
| 14:59 |
mantis1 |
still same error |
| 14:59 |
Dyrcona |
I think you want to fetch the pullrequest from github-evergreen not working. |
| 15:00 |
|
jihpringle43 joined #evergreen |
| 15:01 |
mantis1 |
when I do that, it returns and I'm still on main branch |
| 15:02 |
Dyrcona |
Right, fetch just updates your local metadata. I think you want to git pull to actually get the changes or something like that. |
| 15:02 |
Dyrcona |
Oh. The instructions say to cherry-pick.. Look at step 5. |
| 15:04 |
jeffdavis |
Heh, I actually manage to make it to a Rust WG meeting and it's cancelled. Oh well, next time! |
| 15:06 |
* Dyrcona |
is starting over on the Rust utility from scratch. I think I have a way around my issue of writing rows to a csv. It won't be fast, but it should work if I use format! and a Vec<String>. |
| 15:06 |
mantis1 |
woo success |
| 15:06 |
mantis1 |
Dyrcona++ |
| 15:07 |
Dyrcona |
mantis1++ |
| 15:09 |
* Dyrcona |
needs to learn more about the #[derive..] macro. |
| 15:23 |
Dyrcona |
ok, gonna be more "rustic" this time around. less perly. |
| 15:29 |
|
mantis1 left #evergreen |
| 15:31 |
pinesol |
News from commits: Docs: Resolves LP#2121614 <http://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=4d508431a6b10c00c007af3ef09c3c6d45c9328e> |
| 16:11 |
Bmagic |
eeevil++ # I'll give that branch some testing |
| 16:16 |
eeevil |
Bmagic: cool, thanks. note: the way the message bus is set up has changed significantly. please take a look at the new stuff in osrf_control, and note too the new way that the redis default user password is set up in /etc/redis/redis.conf via the "requirepass" setting (see: `osrf_control --help|less` for info, along with the commit message and docs changes) |
| 16:45 |
Bmagic |
eeevil: thanks for pointing that out, will do! |
| 17:00 |
|
mmorgan left #evergreen |
| 19:03 |
|
jihpringle joined #evergreen |
| 23:54 |
|
smayo joined #evergreen |
