similar to: Trac Triage - Time to fix them

Evening, Alright folks, as Jeremy Kemper mentioned I''m working on a set of "triage" scripts for the Rails trac using RFuzz to go through all the tickets and clean them out. I''ve talked this over with the core guys, and they''re behind it. I''m calling this set of scripts "THE MAGGOT" thanks to hasmanyjosh. Basically THE MAGGOT (all caps)

Evening, Alright folks, as Jeremy Kemper mentioned I''m working on a set of "triage" scripts for the Rails trac using RFuzz to go through all the tickets and clean them out. I''ve talked this over with the core guys, and they''re behind it. I''m calling this set of scripts "THE MAGGOT" thanks to hasmanyjosh. Basically THE MAGGOT (all caps)

When I try to submit a ticket using http://dev.rubyonrails.org/newticket, I get the following: Oops... *Trac detected an internal error:* If you think this really should work and you can reproduce it. Then you should consider to report this problem to the Trac team. Go to http://trac.edgewall.com/ and create a new ticket where you describe the problem, how to reproduce it. Don''t forget

Trying to create a user account on dev.rubyonrails.org Error: [Errno 28] No space left on device Traceback (most recent call last): File "/opt/csw/lib/python2.3/site-packages/trac/web/main.py", line 335, in dispatch_request dispatcher.dispatch(req) File "/opt/csw/lib/python2.3/site-packages/trac/web/main.py", line 220, in dispatch resp =

Hey guys, I''ve been trying out ferret 0.9.3 on my powerbook this weekend and I''ve been triggering ''bus errors'' when using the Query API. If I programmatically build up strings, it works just fine. There''s some more information available in the trac ticket http://ferret.davebalmain.com/trac/ticket/62 Is anyone successfully using the Query API on

Hello guys, I went into milestones page (https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones) and found out that Rails 2.3.6 was due Jan 15, 2010. Does it mean all tickets in that milestone should be cleared first? If so, then I would pay attention to clear tickets in that bucket first. Thank you, Prem Sichanugrist (sikachu) -- You received this message because you are

Its awesome to see so much progress on this! A very minor question - why is it called M680x0 and not M68K given that's what the target arch/triple is and how its usually referred to? Sorry for the bikeshedding.... Simon. On 30/09/2020 21:14, Min-Yih Hsu via llvm-dev wrote: > Hi All, > > I've composed a draft roadmap for this new target. I've decided to try >

http://dev.rubyonrails.org/ticket/1117 I''ve attached a patch to ticket 1117 which fixes it so that booleans are escaped as booleans, not integers. Specifically, this situation will now work find_all(["send_date=? and sent=?", Date.today, false]) Which matches peoples expectations, but it causes some problems with the postgresql unit tests. Specifically, the use of

Hi James, > On Nov 18, 2015, at 11:53 AM, James Molloy <james at jamesmolloy.co.uk> wrote: > > Hi Quentin, > > I'm really excited to see this happening! > > My major question is over the testing story for this. How are we going to write unit tests for GIR? Thanks for bringing that up! That is a very good question and also one that will require a lot of work to

I just noticed I frequently encounter patches that need to be updated because of applied changes. Maybe this can be automated? Not automating the "updating of the patch" part, but the part where a comment is posted to the ticket so the submitter is informed. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

All, I''ve run into a few cases recently where I have environments that are nearly (or totally) identical, except for the database. For example, I have a "live" environment locally where I pull production data for load testing or triage, and I generally want it to behave like "development". Similar situations occur for continuous-integration or staging boxen that

Hey guys, With the addition of has_many :through, a number of people will probably want to add primary keys to their current ''rich association'' tables. Currently we don''t have an add_primary_key. We have a ticket for it[1], and I''ve attached a simple patch[2]. It works fine for mysql and postgres (8) and Rick is looking at sqlite. Could those of you who use

On Wed, Aug 15, 2007 at 05:29:03AM -0000, puppet wrote: > #761: mount tries to mount an already mounted FS > -----------------------------+---------------------------------------------- > Reporter: porridge | Owner: luke > Type: defect | Status: new > Priority: normal | Milestone: misspiggy >

I just found this ticket because I noticed the same issue. http://dev.rubyonrails.org/ticket/6251 The official response was that it''s not a bug because when you use :joins you are "riding close to the metal". But I''m at a loss as to figure out why this behavior even needs to exist. Every table (except HABTM links) in a typical Rails app is going to have an id

Hello I was wondering if someone could put together a bug triage guide and put it on the wiki. I was looking for something to do tonight and z00dax said go hunt some bugs. So I went first to the wiki to look for a guide for a proper procedure on how the team would like bug triaging handled but didn't find one. I have triaged before but i know every place is different. So some guidelines

As everyone probably realizes, I''m getting swamped with incoming problems and tickets and I still need help triaging the tickets. James Turnbull has volunteered to help some, but I think we need more than one person. We''ve had a few people step in once or twice, but I''d like to be able to depend on Unreviewed tickets getting handled by someone else, rather

hello theora lovers! I opened few weeks ago this issue on Xiph tracker and I understand that there are higher priority issues to dela with before creating an installer. However, it could be a Blocker for my theora HTML5 video deployement on some websites, I explain : With the new beta State of Chrome frame for IE, IE is no more a problem (at least if you have admin rights) , So the 40% IE

Hi, Attached are links to two patches I submitted via the RoR Trac system a week or so ago: http://dev.rubyonrails.org/ticket/8305 http://dev.rubyonrails.org/ticket/8308 I refrained from creating a new Trac ticket for ARes, which will be affected if both of these patches are accepted by Core. There are a couple of workarounds for this issue, but it would be nice for AR, AS and ARes to output

Hey guys, Take a look at http://dev.rubyonrails.org/ticket/732. The essential ''problem'' is that Rails doesn''t support a module and a class both named Customer. (::Customer, not in modules themselves) Is this something that''s even possible with ruby? it looks like it should be marked as wontfix? But as I''m a little new to ruby, I figured

Wine is approaching the 0.9 release, and it's time to start fixing all the lingering bug reports in Wine's bug database. You can help the Wine developers do this even if you're not a developer yourself! All you have to do is spend an hour trying to reproduce a bug that somebody else filed. If you're interested, please go to http://kegel.com/wine/qa for step-by-step instructions.