Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2015-03-25

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

All times shown according to UTC.

Time Nick Message
01:05 bala joined #gluster-dev
01:14 suliba joined #gluster-dev
02:14 ira joined #gluster-dev
02:25 ira joined #gluster-dev
02:55 ppai joined #gluster-dev
03:29 bala joined #gluster-dev
03:38 hchiramm__ joined #gluster-dev
03:39 rafi joined #gluster-dev
03:42 shubhendu joined #gluster-dev
03:52 ilbot3 joined #gluster-dev
03:52 Topic for #gluster-dev is now Gluster Development Channel - http://gluster.org | For general chat go to #gluster | Patches - http://review.gluster.org/ | Channel Logs - https://botbot.me/freenode/gluster-dev/ & http://irclog.perlgeek.de/gluster-dev/
03:52 lalatenduM joined #gluster-dev
03:56 atinmu joined #gluster-dev
04:08 kdhananjay joined #gluster-dev
04:11 kanagaraj joined #gluster-dev
04:24 spandit joined #gluster-dev
04:29 anoopcs joined #gluster-dev
04:29 jiffin joined #gluster-dev
04:41 ppai joined #gluster-dev
04:45 anoopcs joined #gluster-dev
04:51 bala joined #gluster-dev
04:54 soumya joined #gluster-dev
05:00 aravindavk joined #gluster-dev
05:18 vimal joined #gluster-dev
05:20 nishanth joined #gluster-dev
05:20 ndarshan joined #gluster-dev
05:25 deepakcs joined #gluster-dev
05:26 hgowtham joined #gluster-dev
05:28 aravindavk joined #gluster-dev
05:29 rjoseph joined #gluster-dev
05:31 anoopcs joined #gluster-dev
05:32 kshlm joined #gluster-dev
05:38 suliba joined #gluster-dev
05:39 aravindavk joined #gluster-dev
05:39 gem joined #gluster-dev
05:41 aravindavk joined #gluster-dev
05:47 ashiq joined #gluster-dev
05:48 hgowtham joined #gluster-dev
05:48 92AAAWFTA joined #gluster-dev
05:50 hagarth joined #gluster-dev
06:11 hgowtham joined #gluster-dev
06:15 overclk joined #gluster-dev
06:25 soumya joined #gluster-dev
06:26 soumya joined #gluster-dev
06:56 bala joined #gluster-dev
07:11 raghu joined #gluster-dev
07:15 anrao joined #gluster-dev
07:30 badone joined #gluster-dev
07:49 bala joined #gluster-dev
07:49 ppai joined #gluster-dev
07:50 anrao joined #gluster-dev
08:01 hgowtham_ joined #gluster-dev
08:07 ndevos JustinClift: client-side bugzilla package? I guess that is the 'bugzilla' command from python-bugzilla
08:15 hagarth ndevos: IIRC, a response for any fop from the server resets the ping timer
08:16 ndevos hagarth: yes, shyam pointed me to it. its more like, it is not counted as a timeout by the ping-timer if there were recent packets sent/received
08:17 hagarth ndevos: right
08:17 ndevos the ping-timer timout function would get execute, but it has those additional checks
08:17 ndevos executeD
08:17 hagarth ndevos: correct, that is the behavior.
08:24 hagarth atinmu: looking into http://review.gluster.org/#/c/9862/3, is glusterd getting re-configured for every volume set CLI?
09:01 atinmu hagarth, in CLI volume set all the daemons are reconfigure (for eg : refer validate_shdopts)
09:02 atinmu hagarth, there it uses local volgen_graph_t but it never frees up its mem_rec which causes the memory leak
09:03 atinmu hagarth, I believe the changes are not going to solve memory leak for volume set CLI only as its in a generic path
09:26 pranithk joined #gluster-dev
09:26 hagarth atinmu: yeah, that was my thinking too about memory leaks in volume set CLI not getting addressed with this patch. any chances of running glusterd with valgrind and volume set CLI in a loop?
09:26 hagarth atinmu: I will merge this patch nevertheless
09:28 atinmu hagarth, correction, my last statement was incorrect
09:28 hagarth kshlm: can you please merge http://review.gluster.org/9985 if there are no problems?
09:28 atinmu hagarth, I meant it will solve other memory leak issues along with volume set CLI
09:29 atinmu I did run volume set in loop before and after applying the patch and could see the difference
09:29 hagarth atinmu: let me check validate_shdopts, has been a while since I visited that part :)
09:29 atinmu hagarth, sure
09:30 hgowtham_ joined #gluster-dev
09:30 hagarth atinmu: OK, did that and understand the patch better now. will merge it shortly.
09:31 atinmu hagarth, thanks
09:31 atinmu hagarth++
09:31 glusterbot atinmu: hagarth's karma is now 45
09:34 ira joined #gluster-dev
09:34 anrao joined #gluster-dev
09:34 ppai joined #gluster-dev
09:35 kaushal_ joined #gluster-dev
09:37 ira joined #gluster-dev
09:38 u-ha joined #gluster-dev
09:38 ira joined #gluster-dev
09:46 kanagaraj joined #gluster-dev
09:50 atinmu joined #gluster-dev
09:51 rjoseph joined #gluster-dev
09:55 hgowtham joined #gluster-dev
10:03 ndevos spandit: Makefile.am review again? http://review.gluster.org/9973
10:03 spandit ndevos, Sure
10:04 ndevos spandit++ thanks!
10:04 glusterbot ndevos: spandit's karma is now 2
10:09 kdhananjay joined #gluster-dev
10:09 anoopcs joined #gluster-dev
10:12 anrao joined #gluster-dev
10:12 badone joined #gluster-dev
10:55 ppai joined #gluster-dev
10:56 bala joined #gluster-dev
10:58 kaushal_ joined #gluster-dev
10:58 hgowtham joined #gluster-dev
11:03 anrao joined #gluster-dev
11:07 kanagaraj joined #gluster-dev
11:09 atinmu joined #gluster-dev
11:19 nishanth joined #gluster-dev
11:22 rjoseph joined #gluster-dev
11:30 kdhananjay joined #gluster-dev
11:34 soumya_ joined #gluster-dev
11:35 raghu can someone please review the patch http://review.gluster.org/#/c/8351/???. It has passed regression runs, but has been around there since sometime
11:35 lalatenduM joined #gluster-dev
11:40 hagarth joined #gluster-dev
11:45 ppai joined #gluster-dev
11:59 Debloper joined #gluster-dev
12:01 ndevos REMINDER: Gluster Community meeting starts now in #gluster-meeting
12:05 jdarcy joined #gluster-dev
12:06 shaunm joined #gluster-dev
12:09 gem joined #gluster-dev
12:14 itisravi joined #gluster-dev
12:18 rjoseph joined #gluster-dev
12:27 lalatenduM joined #gluster-dev
12:42 hchiramm gem++
12:42 glusterbot hchiramm: gem's karma is now 8
12:55 rafi joined #gluster-dev
13:12 ndevos a must read for all developers/maintainers: http://thread.gmane.org/gmane.com​p.file-systems.gluster.devel/9971
13:12 rjoseph joined #gluster-dev
13:22 kkeithley anyone have the DHT log flooding BZ at hand?
13:28 lalatenduM kkeithley, ndevos hchiramm check http://paste.fedoraproject.org/202665/27290073/
13:28 lalatenduM do you want to add anything to it?
13:29 hchiramm lalatenduM,  http://www.gluster.org/community/d​ocumentation/index.php/Planning37
13:29 hchiramm mahy be u can add the reference for the new  features
13:29 lalatenduM hchiramm, yup thanks
13:30 kkeithley Personally I'd drop the "gentle" from "gentle reminder"
13:30 kkeithley It's a pretty gentle reminder as it is.
13:31 hchiramm LGTM
13:32 ndevos anoopcs++
13:32 glusterbot ndevos: anoopcs's karma is now 2
13:32 lalatenduM kkeithley, :)
13:32 lalatenduM hchiramm, I am putting your name with me , partner in crime :)
13:33 lalatenduM in the mail
13:33 hchiramm hahahaha :)
13:33 ndevos lalatenduM: make sure to add the feature owners on CC ;-)
13:34 lalatenduM ndevos, looks like the next mail with bug numbers in it :)
13:34 ndevos lalatenduM: the email or http://www.gluster.org/community/documentatio​n/index.php/Submitting_Documentation_Patches does not point directly to the docs/features/ directory in the sources for examples?
13:36 lalatenduM ndevos, nope. do we need examples?
13:36 ndevos lalatenduM: filing bugs for it could wait a little? it would be best if the feature documentation is filed against the same bug as the rest of the patches for the feature
13:37 ndevos lalatenduM: I think examples always help while encouraging how to do things
13:37 lalatenduM ndevos, you mean while sending the doc patches we should use the same bug number as feature?
13:38 lalatenduM right
13:39 lalatenduM ndevos, do u have an example which I can share
13:39 lalatenduM ?
13:40 ndevos lalatenduM: any from https://github.com/gluster/glus​terfs/tree/master/doc/features >
13:40 ndevos ?
13:40 kkeithley nobody knows the dht log flooding BZ?  My bugzilla search fu is failing. Also my email search fu
13:40 dlambrig_ joined #gluster-dev
13:41 ndevos lalatenduM: and yes, the best practise would be to have all patches for a feature attached to one bug, that makes it easier to find the whole series
13:41 kkeithley let's see what I can find in the git log....
13:41 ndevos kkeithley: wasnt that an email on gluster-users?
13:42 kkeithley I thought hagarth mentioned back porting. Maybe I just imagined that
13:43 kkeithley nope, he didn't
13:43 lalatenduM ndevos, agree about the bz number to use
13:43 dlambrig_ left #gluster-dev
13:43 lalatenduM ndevos, regarding the feature dir, there might be situation where we need to modify the admin guide pages
13:44 ndevos lalatenduM: when you file a bug specially for the documentation, you can have it block the bug that was used for the feature too, as an alternative path
13:44 lalatenduM ndevos, yeah
13:44 ndevos lalatenduM: oh, yes, the admin guide as well, you should point to both pieces of documentation in your email :)
13:45 ndevos otherwise people will only do one...
13:45 lalatenduM ndevos, spoon feeding ?;)
13:46 ndevos lalatenduM: yes, do not assume developers can think :P
13:49 ndevos kkeithley: you wanted to send a one-liner for review?
13:50 kkeithley today's one-liner? ;-)
13:50 ndevos one line, every day!
13:51 lalatenduM ndevos, have sent the mail :)
13:51 kkeithley The only gluster-users mail about log flooding I find is  http://www.gluster.org/pipermail/glu​ster-users/2014-November/019374.html, and hagarth's patch http://review.gluster.org/#/c/8781/ , BZ 1144527
13:52 kkeithley Is that the right one?
13:52 ndevos lalatenduM++ thanks
13:52 glusterbot ndevos: lalatenduM's karma is now 75
13:52 kkeithley hagarth: ^^^
13:52 ndevos kkeithley: yes, I think thats the one
13:54 kkeithley If a back port to 3.4 is needed, I think we ought to do 3.5 and 3.6 as well.
13:56 kkeithley ah, it's already been backported to 3.5 and 3.6 and merged.
13:57 kkeithley 3.6 BZ 1188064 is still only in POST even though the change has been merged.
13:57 * kkeithley fixes that
14:02 atinmu joined #gluster-dev
14:03 kkeithley hang on, I'll have a more-than-one-liner for you to review shortly
14:09 hchiramm lalatenduM++ thanks for the mail
14:09 glusterbot hchiramm: lalatenduM's karma is now 76
14:10 lpabon joined #gluster-dev
14:10 ndevos kkeithley: not sure I'm in the mood for 1+ liners
14:10 ndevos kkeithley: oh, when I review your libntirpc package, will you review my richacl one?
14:11 kkeithley most definitely
14:15 wushudoin joined #gluster-dev
14:29 dlambrig1 joined #gluster-dev
14:29 kkeithley http://review.gluster.org/9996
14:29 hchiramm ndevos++
14:29 glusterbot hchiramm: ndevos's karma is now 98
14:30 kshlm joined #gluster-dev
14:31 kkeithley ndevos, hagarth: http://review.gluster.org/9996
14:37 atinmu joined #gluster-dev
14:52 firemanxbr_ joined #gluster-dev
14:56 atinmu joined #gluster-dev
14:56 shubhendu joined #gluster-dev
15:30 Debloper joined #gluster-dev
15:50 firemanxbr joined #gluster-dev
15:51 ndevos my Gerrit karma must have gone down today, I gave a lot of -1 review comments :-/
15:52 ndevos and kkeithley should be lucky with this +1 and a small remark
15:52 ndevos s/this/his/
15:54 bala joined #gluster-dev
15:57 ndevos joined #gluster-dev
15:57 ndevos joined #gluster-dev
16:16 ndevos kkeithley: I'm stepping out now, did not yet manage to review libntirpc, maybe I'll get that done tonight
16:17 soumya_ joined #gluster-dev
16:32 vimal joined #gluster-dev
17:10 anoopcs joined #gluster-dev
17:11 kkeithley @later tell ndevos I'm not sure luck had anything to do with it, but I'll take the +1 anyway.
17:11 glusterbot kkeithley: The operation succeeded.
17:14 jiffin joined #gluster-dev
17:47 kkeithley (07:35:11 AM) raghu: can someone please review the patch http://review.gluster.org/#/c/8351/  ???. It has passed regression runs, but has been around there since sometime
17:47 kkeithley someone help raghu out please!!!
17:53 kkeithley this is the Ubuntu code audit cleanup so that 3.6.x can go into Ubuntu eventually!
17:54 kkeithley Although at this point maybe 3.7 has a better chance of making into an Ubuntu release
17:55 rafi joined #gluster-dev
18:05 dlambrig1 if I write a fix for a coverity bug, how can I test to see if the problem has gone away? Do we have coverity loaded on any of the slave machines?
18:17 shyam joined #gluster-dev
18:19 anrao joined #gluster-dev
18:32 jobewan joined #gluster-dev
18:35 dlambrig1 left #gluster-dev
18:39 lalatenduM joined #gluster-dev
18:45 deZillium joined #gluster-dev
19:09 kkeithley dlambrig1: no, covscan isn't installed on any slave, we don't have a license
19:09 kkeithley we = community gluster
19:14 lalatenduM dlambrig, we do weekly runs, you can get to know then
19:15 dlambrig lalatenduM: thanks
19:15 lalatenduM dlambrig, also we dont mind Coverity complaining if developers has gone through CIDs and have addressed that
19:25 ndevos dlambrig: yeah, we're happy to review and merge patches that should address coverity issues, just mention the CID in the commit message when posting
19:27 dlambrig ndovos: its fix 10000 (we hit a magic number!)
19:42 kkeithley ndevos: what do you think about those BZs? Are they must-fix for 3.7/3.1?
19:56 vipulnayyar joined #gluster-dev
20:03 ndevos kkeithley: just responded to your email, I'll be sweating if I need to fix all of those!
20:04 ndevos dlambrig: oh, I was hoping I could post a patch with that number tomorrow :-/
20:10 lpabon joined #gluster-dev
20:10 shaunm joined #gluster-dev
20:12 aravindavk joined #gluster-dev
20:13 kkeithley dlambrig1: I have covscan installed on an internal machine. pm me tomorrow for info
20:14 kkeithley lalatenduM: ^^^
20:14 kkeithley dlambrig: ^^^
20:20 dlambrig kkeithley: ok, thanks
20:38 shyam joined #gluster-dev
20:42 anrao joined #gluster-dev
21:20 badone joined #gluster-dev
21:24 misc JustinClift: got the server with a internet access. I am installing the webserver with centos 7, will look at the jenkins one after ?
21:25 misc any preference between hardware riad or software one ?
21:49 dlambrig left #gluster-dev
22:29 _Bryan_ joined #gluster-dev
23:48 JustinClift misc: No real preference
23:54 misc JustinClift: ok, well, I am gonna install tomorow, because uploading the centos 7 netinstall on my adsl line is slow
23:54 misc and I am out of mana to cast enough curses on the developper of the java applet and their whole familly up to 7th generation
23:55 misc ( the applet who is unable to read a file, but do not give any feedback at all )

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