I was gonna nudge you guys about #6175, before that, I was gonna download the patch and test it again. But... when I attempt to download it, track says it doesn''t exist. The previous patch file is mssing too. The others seem ok. What the two missing have in common is a "+" char in the name. Maybe that''s our culprit. Could someone check that, and try to rescue the patch from the dead? I don''t seem to have a local copy. Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
> Could someone check that, and try to rescue the patch from the dead? > I don''t seem to have a local copy.Seems trac 10.3 has a bug with cgi escaping, so don''t upload any files with spaces in them for the time being. I''ve de-ghosted that patch for you. give it a quick checkover and re-nudge us. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
(Sorry to have to ask this here, but dev.rubyonrails.org is 404 for me right now.) I understand the #7615 patch deals with the different order of reading files across different filesystems. I''m an Ubuntu Linux user brand new to the Edge and had "rake test" fails in actionpack related to this too. I''m sure that #7615 fixes the cached javascript/stylesheet problems I saw. I was wondering whether it also addressed another failure that stems from the same dir listing order issue:> test_should_cache_get_with_ok_status(PageCachingTest) > get with ok status should have been cached.The test passes when run on its own, but fails under "rake test" on my Ubuntu box since it does its initialization of ActionController::Base.perform_caching at the top of the file rather than using setup/teardown. The asset helper test plays with the same setting and I expect the caching test is passing for people on other platforms because of the order rake reads and runs the tests in. The fix is obvious: Index: actionpack/test/controller/caching_test.rb ==================================================================--- actionpack/test/controller/caching_test.rb (revision 6225) +++ actionpack/test/controller/caching_test.rb (working copy) @@ -4,7 +4,6 @@ CACHE_DIR = ''test_cache'' # Don''t change ''/../temp/'' cavalierly or you might hoze something you don''t want hozed FILE_STORE_PATH = File.join(File.dirname(__FILE__), ''/../temp/'', CACHE_DIR) -ActionController::Base.perform_caching = true ActionController::Base.page_cache_directory = FILE_STORE_PATH ActionController::Base.fragment_cache_store = :file_store, FILE_STORE_PATH @@ -30,6 +29,8 @@ class PageCachingTest < Test::Unit::TestCase def setup + ActionController::Base.perform_caching = true + ActionController::Routing::Routes.draw do |map| map.main '''', :controller => ''posts'' map.resources :posts @@ -51,6 +52,8 @@ def teardown FileUtils.rm_rf(File.dirname(FILE_STORE_PATH)) + + ActionController::Base.perform_caching = false end def test_page_caching_resources_saves_to_correct_path_with_extension_even_if_default_route I''ll happily submit this properly once Trac reappears for me, but wanted first to check whether Caio had already dealt with it in #7615. Thanks, --Anthony. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Anthony Bailey wrote:> [a query about patch #7615 and test_should_cache_get_with_ok_status(PageCachingTest)]OK, I can see Trac again now. To answer my own question: #7615 does not fix the issue in question. I''ll restate it. I''m new to Edge, running on Ubuntu Linux. The actionpack "rake test" failed for me in various places due to some platform-dependent nondeterministic orderings. Patches #7614 and #7615 address all but one:>> test_should_cache_get_with_ok_status(PageCachingTest)]>> get with ok status should have been cached. The test passes when run on its own, but fails under "rake test" on my Ubuntu box since it does its initialization of ActionController::Base.perform_caching at the top of the file rather than using setup/teardown. The asset helper test plays with the same setting, and I expect the caching test is passing for people on other platforms because of the order rake reads and runs the tests in. I''ve submitted a patch: http://dev.rubyonrails.org/ticket/7640 --Anthony. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 2007-02-24, at 22:35 , Michael Koziarski wrote:> >> Could someone check that, and try to rescue the patch from the dead? >> I don''t seem to have a local copy. > > Seems trac 10.3 has a bug with cgi escaping, so don''t upload any files > with spaces in them for the time being. > > I''ve de-ghosted that patch for you. give it a quick checkover and > re-nudge us.Thanks for that. Nudging you now: I''ve once reworked the patch as per marcel''s request and now I''ve done it again. All tests pass. Please review and apply it asap, I''d hate to see it go stale again. It''s a patch mostly about code removal, so a lot has to be verified to update it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
On 2007-02-24, at 22:35 , Michael Koziarski wrote:> > I''ve de-ghosted that patch for you. give it a quick checkover and > re-nudge us.Hi Koz, Did anyone from core get a chance to take a look at #6175 yet? Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---