Recherche avancée

Sur d’autres sites (13403)

• "File doesn't exist" - streamio FFMPEG on screenshot after create method

  3 mai 2013, par dodgerogers747

  I have videos being directly uploaded to S3 using Amazon's CORS configuration. Videos are uploaded via a dedicated S3 form, once they have been uploaded successfully the URL of the video is appended to the @video.file hidden_field via javascript and then the video saves.

  I can't get this after_save method to work which takes a screenshot of the video and saves it to S3 via carrierwave after the video has been saved as a rails object. ( It was previously working using a carrierwave video upload instance )

  It errors out withErrno::ENOENT - No such file or directory - the file 'http://bucket-name.s3.amazonaws.com/uploads/video/file/secure-random-hex/video_name.m4v' does not exist: I have tried running this method as a class method to call it from the console but it always comes back with the same error, even though the video exists.

  My bucket is set to public, read and write. How come it doesn't think the file exists ?

  If anyone needs more code just shout, thanks in advance.

  application trace

  Started POST "/videos" for 127.0.0.1 at 2013-05-03 10:48:07 -0700
  
  Processing by VideosController#create as JS
  
    Parameters: {"utf8"=>"✓", "authenticity_token"=>"MAHxrVcmPDtVIMfDWZBwL0YnzaAaAe1PTGip5M4OVoY=", "video"=>{"user_id"=>"5", "file"=>"http://bucket-name.s3.amazonaws.com/uploads/video/file/secure-random-hex/video.m4v"}}
  
    User Load (0.3ms)  SELECT `users`.* FROM `users` WHERE `users`.`id` = 5 LIMIT 1
  
     (0.1ms)  BEGIN
  
    SQL (20.5ms)  INSERT INTO `videos` (`created_at`, `file`, `question_id`, `screenshot`, `updated_at`, `user_id`) VALUES ('2013-05-03 17:48:07', 'http://teebox-network.s3.amazonaws.com/uploads/video/file/secure-random-hex/video.m4v', NULL, NULL, '2013-05-03 17:48:07', 5)
  
     (44.0ms)  ROLLBACK
  
  Completed 500 Internal Server Error in 71ms
  
  
  
  Errno::ENOENT - No such file or directory - the file 'http://teebox-network.s3.amazonaws.com/uploads/video/file/secure-random-hex/video.m4v' does not exist:
  
    (gem) streamio-ffmpeg-0.9.0/lib/ffmpeg/movie.rb:10:in `initialize'
  
    app/models/video.rb:25:in `new'
  
    app/models/video.rb:25:in `take_screenshot'

  video.rb

    attr_accessible :user_id, :question_id, :file, :screenshot
  
    belongs_to :question
  
    belongs_to :user
  
  
  
    default_scope order('created_at DESC')
  
  
  
    after_create :take_screenshot
  
  
  
    mount_uploader :screenshot, ImageUploader
  
  
  
    validates_presence_of :user_id, :file
  
  
  
    def take_screenshot
  
      FFMPEG.ffmpeg_binary = '/opt/local/bin/ffmpeg'
  
      movie = FFMPEG::Movie.new("#{self.file}")
  
      self.screenshot = movie.screenshot("#{Rails.root}/public/uploads/tmp/screenshots/#{File.basename(self.file)}.jpg", seek_time: 2 )
  
      self.save!
  
    end

  videos/_form.html.erb

  <form action="http://bucket-name.s3.amazonaws.com" data-remote="true" class="direct-upload" enctype="multipart/form-data" method="post">
  
    <input type="hidden" />
  
    <input type="hidden" value="ACCESS_KEY" />
  
    <input type="hidden" value="public-read" />
  
    <input type="hidden" />
  
    <input type="hidden" />
  
    <input type="hidden" value="201" />
  
    <input type="file" />
  
  </form>
  
  
  
  &lt;%= form_for @video, html: { multipart: true, id: "new_video" }, remote: true do |f| %>
  
          &lt;% if @video.errors.any? %>
  
      <div>
  
      <h2>&lt;%= pluralize(@video.errors.count, "error") %> prohibited this post from being saved:</h2>
  
  
  
    <ul>
  
      &lt;% @video.errors.full_messages.each do |msg| %>
  
          <li>&lt;%= msg %></li>
  
          &lt;% end %>
  
      </ul>
  
      </div>
  
  &lt;% end %>
  
  
  
      &lt;%= f.hidden_field :user_id, value: current_user.id %>
  
      &lt;%= f.hidden_field :file %><br />
  
  
  
      &lt;% end %>

  ImageUploader

  class ImageUploader < CarrierWave::Uploader::Base
  
  
  
    include CarrierWave::RMagick
  
  
  
     include Sprockets::Helpers::RailsHelper
  
     include Sprockets::Helpers::IsolatedHelper
  
  
  
    storage :fog
  
  
  
    before :store, :remember_cache_id
  
    after :store, :delete_tmp_dir
  
  
  
      def cache_dir
  
        Rails.root.join('public/uploads/tmp/') 
  
      end
  
  
  
      def remember_cache_id(new_file)
  
        @cache_id_was = cache_id
  
      end
  
  
  
      def delete_tmp_dir(new_file)
  
        if @cache_id_was.present? && @cache_id_was =~ /\A[\d]{8}\-[\d]{4}\-[\d]+\-[\d]{4}\z/
  
          FileUtils.rm_rf(File.join(root, cache_dir, @cache_id_was))
  
        end
  
      end
  
  
  
    process resize_and_pad: [306, 150, '#000']
  
  
  
    def store_dir
  
      "uploads/#{model.class.to_s.underscore}/#{mounted_as}/#{model.id}"
  
    end
  
  
  
    def extension_white_list
  
      %w(jpg)
  
      # %w(ogg ogv 3gp mp4 m4v webm mov)
  
    end

• Revision 6723e34224 : Merge "fix permissions on cpplint.py (0644->0755)" into experimental

  4 mai 2013, par James Zern

  Merge "fix permissions on cpplint.py (0644->0755)" into experimental

• Announcing Matomo 4 : More security, privacy and better performance

  17 novembre 2020, par Matomo Core Team — Community, Development, Privacy, Security
  The moment we’ve all been waiting for is here … Matomo Analytics 4 has launched !! We’re incredibly grateful for all community members and contributors who’ve helped with improvements, and our awesome team for all the fixes. 

  We can’t wait for you to gain greater security, privacy protection, and be able to boost your website performance. Now who’s ready ?

  Minimise your business’ web data security risk

  We’ve made Matomo even more secure to meet our users’ ever increasing security needs. Matomo 4 has certainly delivered on these expectations with a wide range of security enhancements and fixes across the platform :

  • Support for app specific API tokens. [#6559]
  • API tokens and session ids are now stored hashed in the database which means if someone can access your database they wouldn’t be able to get the actual token.
  • A more secure host validation. [#16169]
  • By default, you no longer can embed widgets through tokens with higher privileges. [#16264]
  • Plenty of other minor security fixes.

  More protection of your customer’s personal data

  Matomo 4 ensures you’re compliant with data privacy laws and provides you with more ways to keep your customer’s personal data private, such as :

  • The ability to automatically anonymise the referrer to avoid tracking personal data by accident. [#15426]
  • The option to enforce the disabling of cookies. [#16258]
  • Possibility in JavaScript tracker to turn cookies on and off at any time. [#13056]
  • The option to not store any IP address at all. [#16377]
  • Easily disable visits log and visitor profile feature if needed for privacy compliance [#16259]
  • New segment to separate visitors who gave consent vs visitors who didn’t give consent. [#16192]

  Matomo now offers PHP 8 support to users. Want to know more ? Get a detailed list of over 300 fixes and improvements in the Matomo 4 changelog.

  Increased conversion rates with a focus on page performance

  Our new Page Performance feature in Matomo 4 can help you increase conversion rates by showing you exactly how fast or slow your website is going, and WHY. An Akamai Online Retail Study in 2017 found that a 100-millisecond delay in website load time could underperform website conversion rates by up to 7%. 

  By using this new feature you can quickly identify slow pages and fix page speed issues as soon as they arise, meaning you never miss out on those valuable new sales opportunities.

  Improve your Google search rankings in 2021

  According to moz.com, Google’s bringing in a new ranking factor into their algorithm named Core Web Vitals, which will place greater emphasis on load speed (favouring websites that load faster). This means the slower your page loads, the worse it will rank in Google. With Matomo’s new feature, you’ll be able to optimise your pages to rank better according to the Core Web Vitals ranking factor. 

  Read more on how you can use this new feature : https://matomo.org/faq/how-to/how-do-i-see-page-performance-reports/

  Need help upgrading Matomo ?

  Read the Updating Matomo user guide or contact the Matomo experts. 

  Please note : It may take a while for you to receive a notice to update to Matomo 4.