tagged_logger 0.5.1 → 0.5.5

data/README.markdown

@@ -117,7 +117,7 @@ There is more general form for rules, it accepts block with three parameters:
 
 As previously explained the *tag* is a class name the *#logger* is being called from (except when you override Rails instrumentation, see below)
 
-## Integration with Rails (only Rails 3.0 supported at the moment, not completely tested)
+## Integration with Rails (only Rails 3.0 supported at the moment)
 
 ### Installation
 
@@ -127,8 +127,9 @@ In Rails.root/config/application.rb:
 
        TaggedLogger.config(:replace_existing_logger => true)
 
-Without that original methods *ActionController::Base#logger*, *ActiveRecord::Base#logger* and alike will remain untouched, and they have to be patched if we want
-redefine their behavior. 
+Without that original methods *ActionController::Base#logger*, *ActiveRecord::Base#logger* and alike will remain untouched, 
+and they have to be patched if we want to redefine their behavior. By default *TaggedLogger* is safe and it 
+does not patch existing *#logger()* method.
 
 ### Logging in Rails
 
@@ -151,12 +152,12 @@ The event *"sendfile.action_controller"* will be signaled after actual work on s
 ### Overriding Rails logging
 Logging inside Rails is done by log subscribers - their task to subscribe to instrumentation events, receive and log them.
 *TaggedLogger* allows you to override how these subscribers work, for example, 
-you could redirect what is being logged in *ActionController* to some external logging service, like [Logworm](http://www.logworm.com/):
+you could redirect what is being logged in *ActionController* to some external hosted log service, like [Logbook.me](http://logbook.me/):
 
     # In Rails.root/config/initializers/tagged_logger.rb:
     TaggedLogger.rules do
       debug "action_controller.logsubscriber" do |level, tag, msg|
-        Logworm::Logger.log(:controllers, :level => level.to_s, :tag => tag.to_s, :message => msg.to_s )
+          Logbook.send(level, tag.to_s, :msg => msg.to_s )
       end
     end
 
@@ -168,8 +169,9 @@ rule with regular expression:
       #your special logging
     end
 
-
-You also could use *#logger* in your classes inherited from Rails bases and define your own logging rules, for example:
+Rails classes having method *#logger()* are patched by *tagged_logger* (only if it is configured 
+with option :replace_existing_logger => true, of cause), so you may define rules for your controllers and models, 
+for example:
 
     class ApplicationController < ActionController::Base
       def welcome

data/lib/tagged_logger/railtie.rb

@@ -2,27 +2,37 @@ if defined?(Rails::Railtie)
   module TaggedLogger
     class Railtie < Rails::Railtie
       ActiveSupport.on_load(:action_controller) do
-        TaggedLogger.patch_logger(ActionController::Base, TaggedLogger.options[:replace_existing_logger]).
-          patch_logger(ActionController::LogSubscriber, TaggedLogger.options[:replace_existing_logger]).
-          rename [ActionController::LogSubscriber] => "action_controller.logsubscriber"
+        if TaggedLogger.options[:replace_existing_logger]
+          TaggedLogger.patch_logger(ActionController::Base, true).
+            patch_logger(ActionController::LogSubscriber, true).
+            rename [ActionController::LogSubscriber] => "action_controller.logsubscriber"
+        end
       end
       ActiveSupport.on_load(:active_record) do
-        TaggedLogger.patch_logger(ActiveRecord::Base, TaggedLogger.options[:replace_existing_logger]).
-          patch_logger(ActiveRecord::LogSubscriber, TaggedLogger.options[:replace_existing_logger]).
-          rename [ActiveRecord::LogSubscriber] => "active_record.logsubscriber"
+        if TaggedLogger.options[:replace_existing_logger]
+          TaggedLogger.patch_logger(ActiveRecord::Base, true).
+            patch_logger(ActiveRecord::LogSubscriber, true).
+            rename [ActiveRecord::LogSubscriber] => "active_record.logsubscriber"
+        end
       end
       ActiveSupport.on_load(:action_mailer) do
-        TaggedLogger.patch_logger(ActionMailer::Base, TaggedLogger.options[:replace_existing_logger]).
-          patch_logger(ActionMailer::LogSubscriber, TaggedLogger.options[:replace_existing_logger]).
-          rename [ActionMailer::LogSubscriber] => "action_mailer.logsubscriber"
+        if TaggedLogger.options[:replace_existing_logger]
+          TaggedLogger.patch_logger(ActionMailer::Base, true).
+            patch_logger(ActionMailer::LogSubscriber, true).
+            rename [ActionMailer::LogSubscriber] => "action_mailer.logsubscriber"
+        end
       end
       ActiveSupport.on_load(:action_view) do
-        TaggedLogger.patch_logger(ActionView::LogSubscriber, TaggedLogger.options[:replace_existing_logger]).
-          rename [ActionView::LogSubscriber] => "action_view.logsubscriber"
+        if TaggedLogger.options[:replace_existing_logger]
+          TaggedLogger.patch_logger(ActionView::LogSubscriber, true).
+            rename [ActionView::LogSubscriber] => "action_view.logsubscriber"
+        end
       end
       ActiveSupport.on_load(:after_initialize) do
-        TaggedLogger.patch_logger(Rails::Rack::Logger, TaggedLogger.options[:replace_existing_logger]).
-          rename [Rails::Rack::Logger] => "rack.logsubscriber"
+        if TaggedLogger.options[:replace_existing_logger]
+          TaggedLogger.patch_logger(Rails::Rack::Logger, true).
+            rename [Rails::Rack::Logger] => "rack.logsubscriber"
+        end
       end
       
     end

data/lib/tagged_logger/tagged_logger.rb

@@ -108,11 +108,6 @@ module TaggedLogger
     def warn(what, where = {}, &block) output(:warn, what, where, &block) end
     def error(what, where = {}, &block) output(:error, what, where, &block) end
     def fatal(what, where = {}, &block) output(:fatal, what, where, &block) end
-    def any_level(what, where = {}, &block)
-      [:debug, :info, :warn, :error, :fatal].each do |level|
-        output(level, what, where, &block)
-        end
-    end
 
     def formatter
       @formatter = lambda { |level, tag, message| "#{message}\n"} unless @formatter
@@ -200,6 +195,9 @@ module TaggedLogger
         eigenclass.send(:define_method, level) do |msg|
           blocks.each { |(tag_alias, block)| block.call(level, tag_alias, msg) }
         end
+        eigenclass.send(:define_method, "#{level}?".to_sym) do
+          !blocks.empty?
+        end
       end    
     end
     

data/test/test_rails.rb

@@ -24,6 +24,7 @@ class TaggedLoggerRailsTest < Test::Unit::TestCase
 
   context "stub output device @@stub_out;" do
     setup do
+      TaggedLogger.config(:replace_existing_logger => true)
       @@stub_out = TestLogDevice.new
     end
     
@@ -33,7 +34,6 @@ class TaggedLoggerRailsTest < Test::Unit::TestCase
 
     should "be able possible to initialize in the way to override Rails existing logger" do
       assert TestController.new.respond_to? :logger
-      TaggedLogger.config(:replace_existing_logger => true)
       TaggedLogger.rules do 
         info /.*/ do |level, tag, message|
           @@stub_out.write(tag.to_s)
@@ -44,7 +44,6 @@ class TaggedLoggerRailsTest < Test::Unit::TestCase
     end
     
     should "be possible to restore old logger methods" do
-      TaggedLogger.config(:replace_existing_logger => true)
       TaggedLogger.rules do 
         info(/.*/) {|level, tag, message|}
       end

data/test/test_rails_app/Gemfile

@@ -0,0 +1,12 @@
+source 'http://rubygems.org'
+
+gem 'rails', '3.0.1'
+gem 'sqlite3-ruby', :require => 'sqlite3'
+
+group :test do
+  gem 'tagged_logger', :path => '../..'
+  gem 'capybara'
+  gem 'launchy'
+  gem 'rr'
+end
+

data/test/test_rails_app/Gemfile.lock

@@ -0,0 +1,115 @@
+PATH
+  remote: ../..
+  specs:
+    tagged_logger (0.5.1)
+      hashery
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    abstract (1.0.0)
+    actionmailer (3.0.1)
+      actionpack (= 3.0.1)
+      mail (~> 2.2.5)
+    actionpack (3.0.1)
+      activemodel (= 3.0.1)
+      activesupport (= 3.0.1)
+      builder (~> 2.1.2)
+      erubis (~> 2.6.6)
+      i18n (~> 0.4.1)
+      rack (~> 1.2.1)
+      rack-mount (~> 0.6.12)
+      rack-test (~> 0.5.4)
+      tzinfo (~> 0.3.23)
+    activemodel (3.0.1)
+      activesupport (= 3.0.1)
+      builder (~> 2.1.2)
+      i18n (~> 0.4.1)
+    activerecord (3.0.1)
+      activemodel (= 3.0.1)
+      activesupport (= 3.0.1)
+      arel (~> 1.0.0)
+      tzinfo (~> 0.3.23)
+    activeresource (3.0.1)
+      activemodel (= 3.0.1)
+      activesupport (= 3.0.1)
+    activesupport (3.0.1)
+    arel (1.0.1)
+      activesupport (~> 3.0.0)
+    builder (2.1.2)
+    capybara (0.4.0)
+      celerity (>= 0.7.9)
+      culerity (>= 0.2.4)
+      mime-types (>= 1.16)
+      nokogiri (>= 1.3.3)
+      rack (>= 1.0.0)
+      rack-test (>= 0.5.4)
+      selenium-webdriver (>= 0.0.27)
+      xpath (~> 0.1.2)
+    celerity (0.8.2)
+    childprocess (0.1.3)
+      ffi (~> 0.6.3)
+    configuration (1.1.0)
+    culerity (0.2.12)
+    erubis (2.6.6)
+      abstract (>= 1.0.0)
+    ffi (0.6.3)
+      rake (>= 0.8.7)
+    hashery (1.3.0)
+    i18n (0.4.2)
+    json_pure (1.4.6)
+    launchy (0.3.7)
+      configuration (>= 0.0.5)
+      rake (>= 0.8.1)
+    mail (2.2.9)
+      activesupport (>= 2.3.6)
+      i18n (~> 0.4.1)
+      mime-types (~> 1.16)
+      treetop (~> 1.4.8)
+    mime-types (1.16)
+    nokogiri (1.4.3.1)
+    polyglot (0.3.1)
+    rack (1.2.1)
+    rack-mount (0.6.13)
+      rack (>= 1.0.0)
+    rack-test (0.5.6)
+      rack (>= 1.0)
+    rails (3.0.1)
+      actionmailer (= 3.0.1)
+      actionpack (= 3.0.1)
+      activerecord (= 3.0.1)
+      activeresource (= 3.0.1)
+      activesupport (= 3.0.1)
+      bundler (~> 1.0.0)
+      railties (= 3.0.1)
+    railties (3.0.1)
+      actionpack (= 3.0.1)
+      activesupport (= 3.0.1)
+      rake (>= 0.8.4)
+      thor (~> 0.14.0)
+    rake (0.8.7)
+    rr (1.0.1)
+    rubyzip (0.9.4)
+    selenium-webdriver (0.0.29)
+      childprocess (>= 0.0.7)
+      ffi (~> 0.6.3)
+      json_pure
+      rubyzip
+    sqlite3-ruby (1.3.2)
+    thor (0.14.3)
+    treetop (1.4.8)
+      polyglot (>= 0.3.1)
+    tzinfo (0.3.23)
+    xpath (0.1.2)
+      nokogiri (~> 1.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  capybara
+  launchy
+  rails (= 3.0.1)
+  rr
+  sqlite3-ruby
+  tagged_logger!

data/test/test_rails_app/README

@@ -0,0 +1,256 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.com/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |   |-- images
+  |   |-- javascripts
+  |   `-- stylesheets
+  |-- script
+  |   `-- performance
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for
+  images, stylesheets, and javascripts. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.

data/test/test_rails_app/Rakefile

@@ -0,0 +1,7 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+require 'rake'
+
+TestRailsApp::Application.load_tasks

data/test/test_rails_app/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/test/test_rails_app/app/controllers/users_controller.rb

@@ -0,0 +1,8 @@
+class UsersController < ApplicationController
+  def index
+    logger.debug "listing users..."
+    @users = User.everyone
+    UserMailer.index_email.deliver
+    render
+  end
+end

data/test/test_rails_app/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/test/test_rails_app/app/helpers/users_helper.rb

@@ -0,0 +1,2 @@
+module UsersHelper
+end

data/test/test_rails_app/app/mailers/user_mailer.rb

@@ -0,0 +1,6 @@
+class UserMailer < ActionMailer::Base
+  default :from => "from@example.com"
+  def index_email
+    mail(:to => "to@example.com",  :subject => "list of users has been requested")
+  end
+end

data/test/test_rails_app/app/models/user.rb

@@ -0,0 +1,6 @@
+class User < ActiveRecord::Base
+  def self.everyone
+    logger.debug "everyone..."
+    all
+  end
+end

data/test/test_rails_app/app/views/layouts/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>TestRailsApp</title>
+  <%= stylesheet_link_tag :all %>
+  <%= javascript_include_tag :defaults %>
+  <%= csrf_meta_tag %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>

data/test/test_rails_app/app/views/user_mailer/index_email.html.erb

@@ -0,0 +1,2 @@
+<!DOCTYPE html>
+<html></html>

data/test/test_rails_app/app/views/users/index.html.erb

@@ -0,0 +1 @@
+<h1>Listing users</h1>

data/test/test_rails_app/config/application.rb

@@ -0,0 +1,42 @@
+require File.expand_path('../boot', __FILE__)
+
+require 'rails/all'
+
+# If you have a Gemfile, require the gems listed there, including any gems
+# you've limited to :test, :development, or :production.
+Bundler.require(:default, Rails.env) if defined?(Bundler)
+
+module TestRailsApp
+  class Application < Rails::Application
+    # Settings in config/environments/* take precedence over those specified here.
+    # Application configuration should go into files in config/initializers
+    # -- all .rb files in that directory are automatically loaded.
+
+    # Custom directories with classes and modules you want to be autoloadable.
+    # config.autoload_paths += %W(#{config.root}/extras)
+
+    # Only load the plugins named here, in the order given (default is alphabetical).
+    # :all can be used as a placeholder for all plugins not explicitly named.
+    # config.plugins = [ :exception_notification, :ssl_requirement, :all ]
+
+    # Activate observers that should always be running.
+    # config.active_record.observers = :cacher, :garbage_collector, :forum_observer
+
+    # Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
+    # Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
+    # config.time_zone = 'Central Time (US & Canada)'
+
+    # The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
+    # config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
+    # config.i18n.default_locale = :de
+
+    # JavaScript files you want as :defaults (application.js is always included).
+    # config.action_view.javascript_expansions[:defaults] = %w(jquery rails)
+
+    # Configure the default encoding used in templates for Ruby 1.9.
+    config.encoding = "utf-8"
+
+    # Configure sensitive parameters which will be filtered from the log file.
+    config.filter_parameters += [:password]
+  end
+end

data/test/test_rails_app/config/boot.rb

@@ -0,0 +1,13 @@
+require 'rubygems'
+
+# Set up gems listed in the Gemfile.
+gemfile = File.expand_path('../../Gemfile', __FILE__)
+begin
+  ENV['BUNDLE_GEMFILE'] = gemfile
+  require 'bundler'
+  Bundler.setup
+rescue Bundler::GemNotFound => e
+  STDERR.puts e.message
+  STDERR.puts "Try running `bundle install`."
+  exit!
+end if File.exist?(gemfile)