[00:10:30] *** Joins: tomzawadzki (~tzawadzk@192.55.54.44) [01:00:39] *** Quits: ziyeyang_ (~ziyeyang@134.134.139.83) (Quit: Leaving) [07:55:06] *** Quits: johnmeneghini (~johnmeneg@pool-96-252-112-122.bstnma.fios.verizon.net) (Quit: Leaving.) [08:00:26] *** Quits: tomzawadzki (~tzawadzk@192.55.54.44) (Ping timeout: 245 seconds) [09:26:08] dverkamp: can you take a look at ziyeyang's async patches? [09:28:38] yes [09:31:09] the first one looks OK, but the second one adds a comment in the wrong spot [09:44:47] jimharris: I'm in the lab now [11:45:50] *** Joins: johnmeneghini (~johnmeneg@216.240.19.91) [11:52:01] *** Quits: johnmeneghini (~johnmeneg@216.240.19.91) (Quit: Leaving.) [12:14:46] *** Joins: johnmeneghini (~johnmeneg@216.240.19.91) [12:59:12] jimharris: is wkb-fedora-04 running that specific kernel version because of the RocksDB issues with newer kernels? [13:00:00] hmmm - that's possible - we have a fix we can put in our rev of rocksdb to work around it [13:02:09] I'm not sure how it is set up, but it doesn't seem to get upgraded by a normal dnf upgrade at least, so I assume someone explicitly pinned it to that version [13:02:23] just curious mostly, don't want to break it by accident if we upgrade stuff [13:31:34] *** Quits: johnmeneghini (~johnmeneg@216.240.19.91) (Quit: Leaving.) [14:40:41] *** Joins: johnmeneghini (~johnmeneg@pool-96-252-112-122.bstnma.fios.verizon.net) [16:34:02] *** Quits: whitepa (~whitepa@2601:601:1200:f23b:28cf:18e0:5a0b:6d6f) (Ping timeout: 255 seconds) [18:33:42] *** Joins: ziyeyang_ (~ziyeyang@192.55.55.41) [18:34:15] *** Parts: ziyeyang_ (~ziyeyang@192.55.55.41) () [19:54:10] *** Quits: johnmeneghini (~johnmeneg@pool-96-252-112-122.bstnma.fios.verizon.net) (Quit: Leaving.)