小编eWi*_*dII的帖子

当我的重复警报广播器被调用时,我试图读取Android电池的状态我有以下设置:

public class RepeatingAlarm extends BroadcastReceiver {

    @Override       
    public void onReceive(Context context, Intent intent)
    {

            // Acquire the make of the device
            final String PhoneModel = android.os.Build.MODEL;
            final String AndroidVersion = android.os.Build.VERSION.RELEASE;

            // Grab the battery information
            int level = intent.getIntExtra(BatteryManager.EXTRA_LEVEL, -1);
            int scale = intent.getIntExtra(BatteryManager.EXTRA_SCALE, -1);
            final float batteryPct = level / (float)scale; 
    }

}

但我不明白它为什么要回归那个batteryPct = 1.这里有什么我想念的吗？我添加了基于Android Google页面的正确权限,但这似乎没有帮助.

在使用该subprocess.call方法的Python中是否有更高效或更快的效果？我注意到一年前有一个SO问题(Python子进程模块比命令(弃用)慢得多)除了由于Python删除了替代品而导致折旧,所以我想看看这是否是现在唯一的,因此最快意味着从Python中调用shell命令.具体来说,我正在运行以下命令:

subprocess.call( "foo" 的,壳=真)

或者我应该使用os？

谢谢.

我在这里关注指南:http://webtempest.com/how-to-allow-image-uploads-in-rails-on-heroku/我每次尝试运行rails服务器时都会收到错误 - 下面我已经添加了使用各自代码更改的文件.但我不明白错误来自哪里:

错误

sabiola@ubuntu:~/delta_bak$ rails server
=> Booting WEBrick
=> Rails 3.1.1 application starting in development on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/home/sabiola/delta_bak/app/models/user.rb:17: uninitialized constant User::RAILS_ROOT (NameError)
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/activesupport-3.1.1/lib/active_support/inflector/methods.rb:113:in `constantize'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/activesupport-3.1.1/lib/active_support/inflector/methods.rb:112:in `each'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/activesupport-3.1.1/lib/active_support/inflector/methods.rb:112:in `constantize'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise.rb:259:in `get'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/mapping.rb:103:in `to'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/mapping.rb:98:in `modules'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/mapping.rb:115:in `routes'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/mapping.rb:84:in `initialize'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise.rb:289:in `new'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise.rb:289:in `add_mapping'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/rails/routes.rb:190:in `devise_for'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/rails/routes.rb:189:in `each'
    from /home/sabiola/.rvm/gems/ruby-1.8.7-p352/gems/devise-1.4.9/lib/devise/rails/routes.rb:189:in `devise_for'
    from …

我的程序基本如下:

for l in range(0,100):  
 file = open("C:/Twitter/json/user_" + str(l) + ".json", "r")
 #do some stuff
 file.close()

我试图找出一种方法来处理如果丢失文件20将被抛出的异常,并告诉它continue.然而,我试图使用continuewith try语句,它一直在抱怨我没有把它正确放入循环中.任何意见,将不胜感激.

基本上我试过:

try:
 for:
except:
 continue

谢谢,

所以我已经阅读了如何解决这个问题:

使用AbstractController :: ActionNotFound,自定义设计会话控制器的RSpec测试失败

和

http://lostincode.net/blog/testing-devise-controllers

但是我在哪个文件下添加这些更改是我的问题:

在我的rspec文件夹下

registrations_controller

我试过这个

before :each do
  request.env['devise.mapping'] = Devise.mappings[:user]
end

require 'spec_helper'

describe RegistrationsController do

  describe "GET 'edit'" do
    it "should be successful" do
      get 'edit'
      response.should be_success
    end
  end

end

哪个不起作用,任何帮助改变特定文件使这项工作将不胜感激.

编辑

所以我也尝试过 -

https://github.com/plataformatec/devise/wiki/How-To:-Controllers-and-Views-tests-with-Rails-3-(and-rspec)

所以我创建了一个带有spec/support的文件夹,并创建了一个名为controllers_macros.rb的文件

module ControllerMacros
  def login_admin
    before(:each) do
      @request.env["devise.mapping"] = Devise.mappings[:admin]
      sign_in Factory.create(:admin) # Using factory girl as an example
    end
  end

  def login_user
    before(:each) do
      @request.env["devise.mapping"] = Devise.mappings[:user]
      user = Factory.create(:user)
      user.confirm! # or set …