search for: reviews

...(so I think)... but it doesn''t appear to be working correctly. Here is my setup: User (table Clients: basic user stuff belonging to a functional STI relationship) ========== def User < Client has_many :reviewings, :as => :reviewable, :dependent => true has_many :reviews, :through => :reviewings end ========== Review (table Reviews: id, rating, review) ========== def Review < AR:B has_many :reviewings end ========== Reviewing (table Reviewings: id, review_id, reviewable_id, reviewable_type) ========== def Reviewing < AR:B belongs_to :review...

Hi, At the last EuroLLVM, I gave a lightning talk about code review statistics on Phabricator reviews and what we could derive from that to try and reduce waiting-for-review bottlenecks. (see https://llvm.org/devmtg/2018-04/talks.html#Lightning_2). One of the items I pointed to is a script we've been using internally for a little while to try and match open Phabricator reviews to people who mi...

Hi, everyone, I've been fielding an increasing number of questions about how our code-review process in LLVM works from people who are new to our community, and it's been pointed out to me that our documentation on code reviews is both out of date and not as helpful as it could be to new developers.   http://llvm.org/docs/DeveloperPolicy.html#code-reviews I would like to compose a patch to update this, but before I do that, I want to highlight some of my thoughts to get feedback. My intent is to capture our communit...

...I need enlightenment. I have users who log in. For several views I want to let them add comments. Enter act_as_commentable which does just this -- it''s polymorphic, so you just tell your model to act_as_commentable and it obeys. However... Say I have a model, view and controller of my reviews of movies, which I''ll call Reviews. I write a reviews and I want to let my loyal users add comments. What does my view (rhtml) look like? The view shows my review, of course, and perhaps a list of other users'' comments on that review. But now, Joe wants to comment on my review...

...ve to say -- thanks, Kristof! Do you know if this is something that could be automated in Phabricator, instead of something that people run on their own? Or is the intent of this to be something that ran regularly (say, weekly or daily) that would email people (or the list) that could be doing the reviews for some of the open patches? On Sat, Apr 28, 2018 at 1:01 AM, Kristof Beyls via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, > > At the last EuroLLVM, I gave a lightning talk about code review > statistics on Phabricator reviews and what we could derive from that > to t...

...-dev wrote: > > Hi, everyone, > > > > I've been fielding an increasing number of questions about how our > > code-review process in LLVM works from people who are new to our > > community, and it's been pointed out to me that our documentation on > > code reviews is both out of date and not as helpful as it could be to > > new developers. > > > > http://llvm.org/docs/DeveloperPolicy.html#code-reviews > > > > I would like to compose a patch to update this, but before I do that, I > > want to highlight some of my thought...

...-dev wrote: > > Hi, everyone, > > > > I've been fielding an increasing number of questions about how our > > code-review process in LLVM works from people who are new to our > > community, and it's been pointed out to me that our documentation on > > code reviews is both out of date and not as helpful as it could be to > > new developers. > > > > http://llvm.org/docs/DeveloperPolicy.html#code-reviews > > > > I would like to compose a patch to update this, but before I do that, I > > want to highlight some of my thought...

...>> > >>> > I've been fielding an increasing number of questions about how our >>> > code-review process in LLVM works from people who are new to our >>> > community, and it's been pointed out to me that our documentation on >>> > code reviews is both out of date and not as helpful as it could be to >>> > new developers. >>> > >>> > http://llvm.org/docs/DeveloperPolicy.html#code-reviews >>> > >>> > I would like to compose a patch to update this, but before I do that, >>...

...> > 2. If someone feels motivated, and if it doesn't make the code obtuse, port > > scripts to work with either version -- and for such scripts, change the #! line > > to say "#!/usr/bin/env python". > > > I've started the work: > > https://reviews.llvm.org/D55121 > > More patch may come if there's an interest in that. Most if not all Python scripts in the clang/ repo have been ported and are waiting for reviews. I've split them in independant patches to ease the review works: https://reviews.llvm.org/D55259 https://reviews.l...

...; Hi, everyone, >> > >> > I've been fielding an increasing number of questions about how our >> > code-review process in LLVM works from people who are new to our >> > community, and it's been pointed out to me that our documentation on >> > code reviews is both out of date and not as helpful as it could be to >> > new developers. >> > >> > http://llvm.org/docs/DeveloperPolicy.html#code-reviews >> > >> > I would like to compose a patch to update this, but before I do that, I >> > want to high...

...ted by the fact that we keep working around not having these intrinsics, and that constantly leads us into having more workarounds, and causes infinite combine loops. Here's a (likely incomplete!) list of motivational bugs: infinite loops: https://bugs.llvm.org/show_bug.cgi?id=46271 / https://reviews.llvm.org/D81698 https://bugs.llvm.org/show_bug.cgi?id=45539 / https://reviews.llvm.org/rG01bcc3e93714 https://bugs.llvm.org/show_bug.cgi?id=44835 / https://reviews.llvm.org/D74278 https://reviews.llvm.org/D68408#1976760 https://reviews.llvm.org/D59378 https://bugs.llvm.org/show_bug.cgi?id=38915 / h...

...k welcome. https://docs.google.com/document/d/1oxmk0xUojybDaQDAuTEVpHVMi5xQX74cJPyMJbaSaRM The port is expected to work with modified versions of RTEMS and newlib. I have a git repo with changes to those projects, that I can make available if there is interest. Here is the patch series: https://reviews.llvm.org/D46451 [asan] Add instrumentation support for Myriad https://reviews.llvm.org/D46452 [sanitizer] Don't add --export-dynamic for Myriad https://reviews.llvm.org/D46453 [sanitizer] Add definitions for Myriad RTEMS platform https://reviews.llvm.org/D46454 [sanitizer] Trivial portion of th...

...p the broad message, but > make it more clear that it isn't a hard and fast rule? > My take on it is that even the broad message isn't how I think of LLVM code review practices - if the code owner/domain expert is at your company, so be it. If not, that's fine too - I see lots of reviews by people at the same company that generally look pretty good & I don't think their the exception. I'd personally leave this part out - maybe some caveat about not doing internal review & then summarily approving externally? But that I think is more the exception than the rule &...

def create # next statement is original and is removed # @review = Review.new(params[:review]) @school = School.find(params[:school_id]) # @review = @school.reviews.create!(params[:review]) @review = @school.reviews.build(params[:review]) respond_to do |format| if @review.save flash[:notice] = ''Review was successfully created.'' # format.html { redirect_to(@review) } format.html { redirect_to(@school) }...

Uh-oh: Failed to publish: GitHub error 404 on POST https://api.github.com/repos/llvm/mlir-npcomp/pulls/42/reviews: Not Found (The llvm organization may need to authorize Reviewable as an accepted third party application.) Can an admin take the suggested action on the mlir-npcomp project in the LLVM org? I've followed the instructions in this help doc <https://docs.github.com/en/github/setting-up-and-ma...

...hab's advanced > features and why. For example, what drives the need for patch series > and dependence relationships? Some walk-through examples would be very > helpful. Here's a somewhat more complex example of changes made by myself a year and a half ago, starting with https://reviews.llvm.org/D48013 It's a series of changes across TableGen and the AMDGPU backend to refactor how we represent a class of instructions. Some patterns that occur: - an NFC (no functional change) refactoring/rename change in an area that is then later touched by a functional change. - a change to...

I've read "LLVM Code-Review Policies and Practices," but I remain unsure of a couple of things. Do I always wait for an actual "LGTM", or can people approve the patch for submission in other ways? What happens when a patch is approved but then there are additional review comments? Should the patch be submitted as is, then a follow-up patch submitted, or should the

...t;> make it more clear that it isn't a hard and fast rule? >> > > My take on it is that even the broad message isn't how I think of LLVM > code review practices - if the code owner/domain expert is at your company, > so be it. If not, that's fine too - I see lots of reviews by people at the > same company that generally look pretty good & I don't think their the > exception. I'd personally leave this part out - maybe some caveat about not > doing internal review & then summarily approving externally? But that I > think is more the exception...

...try switching to reviewable.io, to evaluate whether that can more successfully replace phabricator than just GitHub PRs by themselves. On Mon, Sep 14, 2020 at 3:14 PM Nicolai Hähnle via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hi Stephen, > > Here's a real-life example of reviews that GitHub doesn't properly > support to my knowledge: https://reviews.llvm.org/D83088, look for > "Stack" under "Revision Contents". > > The key here is that there's a sequence of commits that's partially > dependent on each other, so that reviewing...

Hi all. I'm assuming most people reading this email are familiar with LLVM's code review process <http://llvm.org/docs/DeveloperPolicy.html#code-reviews> as well as LLVM Weekly, the development newsletter I've written and sent out every Monday since Jan 2014. Since that time, it's provided something of a "signal boost" for important mailing list discussions and commits. I feel it could play a similar role in helping patches tha...