Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2017-01-20

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:17 ashiq joined #gluster-dev
01:31 nbalacha joined #gluster-dev
02:00 ashiq joined #gluster-dev
02:32 gyadav joined #gluster-dev
03:21 sanoj joined #gluster-dev
03:34 nbalacha joined #gluster-dev
03:41 sanoj joined #gluster-dev
03:44 magrawal joined #gluster-dev
03:44 kdhananjay joined #gluster-dev
03:46 karthik_us joined #gluster-dev
03:52 mchangir joined #gluster-dev
03:55 atinm_ joined #gluster-dev
03:57 gyadav joined #gluster-dev
03:58 atinm joined #gluster-dev
04:03 Shu6h3ndu joined #gluster-dev
04:04 nishanth joined #gluster-dev
04:13 gyadav_ joined #gluster-dev
04:42 t1m1 joined #gluster-dev
04:42 skumar joined #gluster-dev
04:43 apandey joined #gluster-dev
04:46 ppai joined #gluster-dev
05:02 rjoseph joined #gluster-dev
05:05 itisravi joined #gluster-dev
05:08 rafi joined #gluster-dev
05:21 msvbhat joined #gluster-dev
05:23 prasanth joined #gluster-dev
05:25 sanoj joined #gluster-dev
05:26 skoduri joined #gluster-dev
05:37 kshlm Is it just me, or is gerrit slow today?
05:41 riyas joined #gluster-dev
05:42 anoopcs kshlm, http://lists.gluster.org/pipermail/gl​uster-infra/2017-January/003115.html
05:43 kshlm anoopcs, Thanks! I was going through my mail and hadn't reached this yet.
05:43 sanoj joined #gluster-dev
05:43 anoopcs kshlm, np. :-)
05:51 ndarshan joined #gluster-dev
05:52 vimal joined #gluster-dev
05:53 mchangir joined #gluster-dev
05:57 msvbhat joined #gluster-dev
05:58 ashiq joined #gluster-dev
06:09 susant joined #gluster-dev
06:17 ppai joined #gluster-dev
06:21 t1m1 joined #gluster-dev
06:23 jiffin joined #gluster-dev
06:48 ankit_ joined #gluster-dev
06:49 k4n0 joined #gluster-dev
07:04 aravindavk joined #gluster-dev
07:37 ashiq joined #gluster-dev
07:37 msvbhat joined #gluster-dev
07:42 ankit__ joined #gluster-dev
07:45 k4n0 joined #gluster-dev
07:46 rastar joined #gluster-dev
07:51 tdasilva joined #gluster-dev
08:30 lpabon joined #gluster-dev
08:37 ashiq joined #gluster-dev
08:51 skumar joined #gluster-dev
08:57 Humble joined #gluster-dev
09:05 Shu6h3ndu joined #gluster-dev
09:05 nishanth joined #gluster-dev
09:11 Saravanakmr joined #gluster-dev
09:20 apandey joined #gluster-dev
09:25 apandey joined #gluster-dev
09:32 percevalbot joined #gluster-dev
09:32 pranithk1 joined #gluster-dev
09:34 nigelb I've had to quickly restart gerrit.
09:34 nigelb If you see an outage now, we should be back in less than a minute
09:35 mchangir okay
09:35 nigelb (I think we're already back)
09:44 kotreshhr joined #gluster-dev
09:46 kdhananjay joined #gluster-dev
10:15 misc so network team have found that the issue is likely coming from another tenant
10:15 misc (in the cage)
10:18 anoopcs And the situation has become worse as in it takes more longer to load r.g.o
10:18 misc yeah, NOC is on it
10:18 anoopcs Ok.
10:36 gem joined #gluster-dev
10:39 bfoster joined #gluster-dev
10:39 riyas_ joined #gluster-dev
10:40 t1m1 joined #gluster-dev
10:42 misc network is back
10:50 rraja joined #gluster-dev
10:53 ashiq joined #gluster-dev
11:21 rastar joined #gluster-dev
11:24 nishanth joined #gluster-dev
11:27 hgowtham joined #gluster-dev
11:40 percevalbot joined #gluster-dev
11:44 kotreshhr left #gluster-dev
11:45 ndevos anoopcs: on the RDMA email, it seems that gluster tries to use the wrong device, there seem to be two of them in this users' system - but I dont know anything about RDMA....
11:53 ankit_ joined #gluster-dev
11:57 percevalbot joined #gluster-dev
11:59 nishanth joined #gluster-dev
12:02 ppai kshlm, PR 226 needs some attention, CI builds might fail otherwise.
12:03 apandey joined #gluster-dev
12:04 percevalbot joined #gluster-dev
12:08 rjoseph joined #gluster-dev
12:10 nishanth joined #gluster-dev
12:14 ppai kshlm++
12:15 glusterbot ppai: kshlm's karma is now 134
12:25 Shu6h3ndu joined #gluster-dev
12:33 xavih joined #gluster-dev
12:40 pranithk1 xavih: hey!
12:41 pranithk1 xavih: just got cthon lock tests to be working on ec volumes. But I am not happy with the code changes. I think we need some extra things.
12:41 ppai kshlm: you can merge #223 now if you'd like
12:52 xavih pranithk1: sorry, I'm a bit busy right now...
12:53 xavih pranithk1: have you posted it for review ? I can look at it later...
12:54 pranithk1 xavih: I will do that. You comment and we will take it from there. The thing is it already passes the cthon tests but I know it is not the solution we thought of...
12:55 pranithk1 xavih: I haven't tested it thoroughly putting it in gdb
12:55 pranithk1 xavih: I will send it for review though...
12:57 ankit_ joined #gluster-dev
13:00 ira joined #gluster-dev
13:11 ankit_ joined #gluster-dev
13:17 mchangir joined #gluster-dev
13:23 pranithk1 joined #gluster-dev
13:31 kkeithley ndevos: did you see my question about glfs_ipc in 3.10?
13:45 shyam joined #gluster-dev
13:46 ndevos kkeithley: I do not think any application can use glfs_ipc() because it uses dict_t and that is not exposed in libgfapi, so it can be PRIVATE_... only
13:46 ndevos kkeithley: iirc there was a previous version of the glfs_ipc() function, not sure how that was exported
13:48 ndevos right, that was glfs_ipc (struct glfs *fs, int opcode)
13:49 ndevos and it is marked as a public function, so no, I do not think we can have the glfs_ipc 4.0 version in gfapi
13:58 ndevos kkeithley: does that answer your question?
14:13 rastar joined #gluster-dev
14:13 vbellur joined #gluster-dev
14:22 kkeithley ndevos: not really. The types were changed to void** so as to not expose libgluster types in gfapi.
14:23 kkeithley s/not really/no, doesn't really answer my question/
14:24 kkeithley so, with void** params, are you okay with pulling it into 3.10?
14:24 kkeithley although point may be moot as shyam is now saying let's leave it out until 4.0.
14:38 kotreshhr joined #gluster-dev
14:40 k4n0 joined #gluster-dev
14:40 rastar joined #gluster-dev
14:56 kotreshhr left #gluster-dev
15:09 nishanth joined #gluster-dev
15:12 ppai joined #gluster-dev
15:28 pranithk1 joined #gluster-dev
15:45 skoduri joined #gluster-dev
16:02 ndevos kkeithley: void* should not be in a public API if those can never be used, it should be a private function instead
16:02 ira joined #gluster-dev
16:03 vbellur joined #gluster-dev
16:03 kkeithley ?  They can be used. You just need to know how to use them.  But I like the idea of having it be a PRIVATE function instead
16:07 wushudoin joined #gluster-dev
16:07 kkeithley Whcih still begs the question: leave it for 4.0?  (i.e. take it out of 3.10?
16:07 kkeithley which
16:08 wushudoin joined #gluster-dev
16:18 ndevos they can not reasonably be used by applications, hence it should not be a public function in gfapi
16:18 ndevos because glfs_ipc is already a public function, we can not have a new glfs_ipc private function with the same name
16:19 kkeithley indeed. Although with symbol versioning and PUBLIC/PRIVATE they might be able to have the same name.
16:19 ndevos so if glfs_ipc/v4.0 is useful for internal usage, if can be added as a private function, with a different name so that any users of glfs_ipc do not break
16:20 kkeithley well, without getting hung up on the name (a different name is obviously called for), the question is: take it out? Or keep it?
16:21 ndevos I dont think we need it in 3.10, jbr will not be in 3.10, so why would we include a function that is only used by that?
16:21 shyam joined #gluster-dev
16:22 kkeithley so take it out is your answer.  Sounds good. Out it comes
16:22 ndevos yes, I dont see a usecase for it in 3.10
16:23 ndevos better out than in
16:25 ndevos great NLM segfault is fixed, but now it ends in an endless loop trying to RPC_TRANSPORT_DISCONNECT the whole time...
16:25 * ndevos frowns
16:27 * kkeithley wonders why atinm's comment for http://review.gluster.org/#/c/16447/ wasn't also the case for  http://review.gluster.org/16283
16:30 ndevos kkeithley: the 3.10 version only modifies one file? if it is a backport, it should state why it is different from the original/master patch, right?
16:44 susant joined #gluster-dev
16:49 shyam joined #gluster-dev
16:49 nishanth joined #gluster-dev
16:58 vbellur joined #gluster-dev
17:37 rastar joined #gluster-dev
17:49 vbellur joined #gluster-dev
17:50 shyam joined #gluster-dev
17:58 ndevos no centos-release-gluster39 package on http://mirror.centos.org/cent​os/7/extras/x86_64/Packages/ yet, I guess I'll announce the release next week then
18:16 ashiq joined #gluster-dev
18:17 kkeithley :-/
18:31 vbellur joined #gluster-dev
18:31 shyam joined #gluster-dev
18:32 gnulnx joined #gluster-dev
18:47 esmiurium joined #gluster-dev
19:07 k4n0 joined #gluster-dev
19:10 Acinonyx joined #gluster-dev
19:11 menaka joined #gluster-dev
19:36 menaka help register
20:09 menaka Please ignore the last message. That was by mistake.
20:09 menaka left #gluster-dev
20:11 menaka joined #gluster-dev
20:31 esmiurium joined #gluster-dev
21:15 ashiq joined #gluster-dev
23:41 wushudoin joined #gluster-dev
23:43 wushudoin joined #gluster-dev
23:51 vbellur joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary