On May 5, 2015, at 8:10 PM, Allen Wittenauer wrote:
> * We’ll be closing registrations to the Bug Bash on May 6th at
> 3PM Pacific time. So make sure you do it son:
> https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-16507188445
That should be
Hey gang!
A couple of things in regards to the Bug Bash on Friday:
* We’ll be closing registrations to the Bug Bash on May 6th at
3PM Pacific time. So make sure you do it son:
https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-165071884
Thanks, Allen. This has long been a thorn in our side, and it's
really good to see someone work on it.
cheers,
Colin
On Tue, May 5, 2015 at 2:59 PM, Allen Wittenauer wrote:
> TL;DR:
>
> Heads up: I’m going to hack on these scripts to fix the race
> conditions.
>
>
>
> Pre
HDFS, MAPREDUCE, and YARN have been migrated.
Let me know of any issues and I’ll try to get to them as I can. This should be
the end of the Jenkins race conditions for our pre commits! *crosses fingers*
I typically split my IDE into two side-by-side panes, the 80 char limit
works pretty well once you factor in the side panes too. I've worked on a
project with a 100 char limit, and that's about the point where even my 30"
monitor needs side scrolling.
I think Colin pretty much nailed it with his r
Jay,
Does bigtop use a line length limit at all? I was mostly hoping that we could
update to using a limit that was more appropriate (IMO) to modern IDEs, like
100-120 chars perhaps?
On May 5, 2015, at 4:38 PM, jay vyas
mailto:jayunit100.apa...@gmail.com>> wrote:
im glad you've started thi
Allen Wittenauer created HADOOP-11926:
-
Summary: test-patch.sh mv does wrong math
Key: HADOOP-11926
URL: https://issues.apache.org/jira/browse/HADOOP-11926
Project: Hadoop Common
Issue Ty
im glad you've started this thread.
1) i like the idea of dropping the 80 char limit !
2) and indeed, we've now adopted it in ASF BigTop, where we try to take
queues from hadoop when possible.
On Tue, May 5, 2015 at 3:53 PM, Rich Haase wrote:
> Arun,
>
> I use my IDE split vertically all the t
TL;DR:
Heads up: I’m going to hack on these scripts to fix the race
conditions.
Presently, we have a pretty wicked race condition in the precommit
scripts, namely writing to a directory that is outside of Jenkins' workspace
directory. I’ve committed changes this morning
Historical issues aside, the reasons are:
* When doing vertical, side-by-side diffs, you need some reasonable
length length standard or else it Just Doesn't Work. And vertical,
side-by-side diffs are how most people prefer to do code reviews.
* Really long lines are visually difficult to follow.
[
https://issues.apache.org/jira/browse/HADOOP-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11925.
---
Resolution: Fixed
Fix Version/s: 2.8.0
Thanks for the quick turn around. comm
Quoting Niels Basjes (2015-05-05 11:29:03)
> So the 80 chars thing was at best reconsidered 16 years ago.
>
> Things have changed ...
Limiting text to a particular width isn't just a byzantine coding convention.
It arose in programming from much older practices, and it has persisted through
the ye
Allen Wittenauer created HADOOP-11925:
-
Summary: branch-2's smart-apply-patch.sh needs to be updated
Key: HADOOP-11925
URL: https://issues.apache.org/jira/browse/HADOOP-11925
Project: Hadoop Common
Arun,
I use my IDE split vertically all the time on projects without strict line
limits and I have never had a problem seeing the code from multiple classes in
such a setup.
I can certainly setup my IDE to only do 80 characters a line, although I think
it hurts readability in many cases where
My 2 cents :
I actually like the lower char limit. Since most of the time, I end up
having to switch between classes, I end up splitting my screen vertically
and having multiple files open. for some reason, I find splitting
vertically is better for readability than horizontally.
In anycase, my IDE
> I respect immensely the contributions Doug has made to many Apache
projects,
Hear hear! I fully agree with that one.
On Tue, May 5, 2015 at 8:30 PM, Rich Haase wrote:
> I respect immensely the contributions Doug has made to many Apache
> projects, but I don’t think that should be a reason to
I respect immensely the contributions Doug has made to many Apache projects,
but I don’t think that should be a reason to force everyone to write code as if
our screen sizes can’t support more than 80 characters.
On May 5, 2015, at 12:21 PM, Niels Basjes
mailto:ni...@basjes.nl>> wrote:
Perhaps
Quote from that page (i.e. the big block in RED at the top):
The information on this page is for Archive Purposes Only
This page is not being actively maintained.
Links within the documentation may not work and the information itself may
no longer be valid.
The last revision to this document was m
Perhaps we should tell him these screens can also be turned landscape ? ;)
But seriously:
1) Does Doug still actively work on code? From my perspective; Only very
infrequently.
2) In the 200+ people IT department where I work I know only 1 colleague
who uses his screen in portrait mode and he does
More formally, we follow the sun java coding standards which follow
the 80 character limit. There is recent discussion over this, so it is
a very relevant comment.
http://wiki.apache.org/hadoop/HowToContribute
http://www.oracle.com/technetwork/java/javase/documentation/codeconventions-136091.html#
On May 5, 2015, at 11:05 AM, Rich Haase wrote:
> Can someone explain to me why on earth we care about limiting line length to
> 80 characters? Are there hadoop developers out there working from teletype
> terminals? Can we perhaps update this limit to something sane, like 120
> chars?
>
Gera Shegalov created HADOOP-11924:
--
Summary: Tolerate JDK-8047340-related exceptions in
Shell#isSetSidAvailable preventing class init
Key: HADOOP-11924
URL: https://issues.apache.org/jira/browse/HADOOP-11924
Can someone explain to me why on earth we care about limiting line length to 80
characters? Are there hadoop developers out there working from teletype
terminals? Can we perhaps update this limit to something sane, like 120 chars?
Rich Haase| Sr. Software Engineer | Pandora
m (303) 887-1146
Sean Busbey created HADOOP-11923:
Summary: test-patch whitespace checker doesn't flag new files
Key: HADOOP-11923
URL: https://issues.apache.org/jira/browse/HADOOP-11923
Project: Hadoop Common
Brahma Reddy Battula created HADOOP-11922:
-
Summary: Misspelling of threshold in log4j.properties for tests in
hadoop-nfs
Key: HADOOP-11922
URL: https://issues.apache.org/jira/browse/HADOOP-11922
Kai Zheng created HADOOP-11921:
--
Summary: Enhance tests for erasure coders
Key: HADOOP-11921
URL: https://issues.apache.org/jira/browse/HADOOP-11921
Project: Hadoop Common
Issue Type: Sub-task
Kai Zheng created HADOOP-11920:
--
Summary: Refactor erasure coders and enhance the tests
Key: HADOOP-11920
URL: https://issues.apache.org/jira/browse/HADOOP-11920
Project: Hadoop Common
Issue Typ
27 matches
Mail list logo
