similar to: Any plans to fix Ticket #6951

Displaying 20 results from an estimated 50000 matches similar to: "Any plans to fix Ticket #6951"

2006 Jul 24
1
Can''t create new ticket on Trac
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
2008 Feb 29
0
Ticket 6000 (was: a year of rails magic)
On 16/02/2008, Michael Koziarski <michael@koziarski.com> wrote: > > I wonder if I could suggest considering it when you look at ticket > 6000. While this patch no longer applies cleanly, if you took the > time to rebase it against trunk and resubmit it, I''m sure we''d be > happy to apply it. Don''t assume we''re actively disregarding patches
2007 Mar 20
1
Ticket 6953: Support Method Not Allowed Responses
Hi, I was wondering if someone wouldn''t mind looking at ticket 6953 and committing it if everything looks ok: http://dev.rubyonrails.org/ticket/6953 This patch properly handles setting the Allow header and the proper status code when an HTTP method is used that a resource doesn''t support or understand. -- Thanks, Dan
2001 Mar 01
2
timeline for R-1.2.x where x>1?
> Date: Thu, 1 Mar 2001 08:52:09 -0500 (EST) > From: Walter Tautz <wtautz@math.uwaterloo.ca> Re: [Rd] timeline for R-1.2.x where x>1? Just curious as I am looking to update our installation. You can always find the current plans on developer.r-project.org. That says The latest release of R was 1.2.2 on February 26th, 2001. We might have a 1.2.3 release mainly with fixes
2007 Mar 27
1
Ticket #7124
http://dev.rubyonrails.org/ticket/7124 I just attached a patch against 1.2 that cleanly applies to trunk too. This allows functional and integration tests to have the same interface to the xhr/xml_http_request method. The patch also includes a deprecation workaround when called without the appropriate parameters. If the patch could also be applied to the 1.2 branch, I would appreciate. The
2008 Mar 17
0
Patch to provide has_one :through functionality (ticket 4756) - eyeballs required
I''ve been working on a patch for has_one :through associations and now it needs some verification love. http://dev.rubyonrails.org/ticket/4756 Please have a look and see if it fits the bill. Constructive criticism welcome! Thanks, Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails:
2008 Jan 19
0
http://dev.rubyonrails.org/ticket/10350
Would someone mind taking a look at this verified ticket and give feedback/apply it? Thanks, -- Mark Van Holstyn, Partner / Software Developer mvanholstyn@mutuallyhuman.com, (616) 706-6842 Mutually Human Software, http://mutuallyhuman.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails:
2007 Jun 12
0
Ticket #8614: Correct default page cache url
> Currently if you use page cache, Rails will take the default route for > controller the controller to construct the path. > > If you wanted to cache the root url (see example below), Rails will create > the cache at /welcome/index.html. Not really what we want. > > map.root :controller => "welcome" # Page cache defaults to >
2010 Jul 07
1
Ticket 5063: Typo in named_scope in activerecord tests category.rb
Hey all, Does someone want to look over a super-trivial patch I just submitted? It''s just correcting a typo; someone accidentally spelled "group_by_title" as "gruop_by_title" in the category.rb model in the activerecord tests. I just fixed it in the model, and in the two places it''s referenced in the habtm test. Thanks, Ben -- You received this message
2010 Jul 02
3
Ticket #5038 ActiveResource not handling updates correctly
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5038-activeresource-not-handling-updates-correctly I just added this ticket. I''m writing a Sinatra API to be consumed by Rails and I''ve run into an issue where the ActiveResource documentation specifies that on update you should return an HTTP 204 status with no body. The problem is that Rack doesn''t
2011 Apr 22
0
Re: [Puppet-dev] Re: Distributed Puppet Architecture and Management
So, we have plans to be smarter about cross-machine dependencies, and about managing the network rather than just the nodes. Part of that comes from the MCollective system, which is all over "network". What I don''t have is a timeline for you: today we don''t have that around, other than the MCollective puppet agent, and we don''t have a concrete plan (that I am
2009 Oct 20
4
any plans to support pkgutil?
Seems that blastwave is all about pkgutil now. Are there any plans to support this? Best, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to
2010 Jul 31
0
Redmine Ticket Creation and Updates via email - an update
Hi all We''ve just finished enabling ticket creation and updates via email. You can now send an email to tickets@puppetlabs.com to create a ticket. You must have a Redmine account to do this and your From address must match the address on your Redmine account. Any attachments added to the email will be applied to the ticket. By default, issues are added to the Puppet project but you
2004 Mar 25
2
Any plans to fix Bug 1139 in 3.0.3?
I was wondering if anyone knows if there are any plans to fix Bug #1139 (reproduced below) in version 3.0.3. I haven't tried 3.0.3pre1 yet, but from what I read of the changes it doesn't look like this bug has been addressed. Is there some other work around? This bug is quite annoying as some of our users/administrators would like to use Windows to modify ACLs and we recently
2007 May 17
4
Namespaced model valid #to_xml support in ActiveRecord, ActiveSupport and ActiveResource
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
2008 Oct 14
1
Any Plans on Tag support in Cucumber
Hi, ThoughtWorks just released the auto test toolset Twist, the "tagging" feature seems pretty useful, http://studios.thoughtworks.com/twist-agile-test-automation/twist-features-and-benefits "Tags allow you to organize test suites in multiple dimensions. With tags, you can include a test in a smoke test suite by just tagging it smoke, or exclude unfinished tests from running by
2013 Oct 18
1
'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca
Hi, ppl I dont know what to do. I configure a new client do sync with my server. the server accept de client_cert without errors and then when i run the "puppet agent -t" agaion i got this error output info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using ''eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server
2018 Apr 26
0
samba4 ticket server cifs/ not found in keytab
Hai, >From your smb. > realm = AD.INTERNALTWO.COM > netbios name = nas1dev-rhel7 > server string = nas1dev-rhel7 Is i expect cifs/nas1dev-rhel7.ad.yourPrimaryDomain.tld at AD.INTERNALTWO.COM Check you hosts file and resolve.conf Like in what is the output of : hostname -I and hostname -A For cifs kerberos tickets, add in krb5.conf the following
2024 Jan 11
0
Announce: timeline to remove DSA support in OpenSSH
Hi, OpenSSH plans to remove support for DSA keys in the near future. This message describes our rationale, process and proposed timeline. Rationale --------- DSA, as specified in the SSHv2 protocol, is inherently weak - being limited to a 160 bit private key and use of the SHA1 digest. Its estimated security level is <=80 bits symmetric equivalent[1][2]. OpenSSH has disabled DSA keys by
2024 Jan 11
0
Announce: timeline to remove DSA support in OpenSSH
Hi, OpenSSH plans to remove support for DSA keys in the near future. This message describes our rationale, process and proposed timeline. Rationale --------- DSA, as specified in the SSHv2 protocol, is inherently weak - being limited to a 160 bit private key and use of the SHA1 digest. Its estimated security level is <=80 bits symmetric equivalent[1][2]. OpenSSH has disabled DSA keys by