I wanted to patch a bug in sprockets-rails, but when I ran the test suite (using ruby-2.0.0-p0 as well as ruby-head), I got the following error:
/Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `block in _prepare_run': undefined method `size' for #<ParallelEach:0x007f823aa55e88> (NoMethodError)
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `each'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `inject'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:707:in `_prepare_run'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:648:in `_run_suites'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:861:in `_run_anything'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1068:in `run_tests'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1055:in `block in _run'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1054:in `each'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1054:in `_run'
from /Users/btaitelb/.rvm/gems/ruby-head#rails-dev/gems/minitest-4.7.1/lib/minitest/unit.rb:1042:in `run'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:21:in `run'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:774:in `run'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:834:in `run'
from /Users/btaitelb/.rvm/rubies/ruby-head/lib/ruby/2.1.0/test/unit.rb:838:in `run'
from /Users/btaitelb/.rvm/rubies/ruby-head/bin/testrb:7:in `<main>'
I'm not clear on the relationship between Test::Unit and MiniTest, especially since I see test/unit.rb referencing MiniTest::Unit
I can patch this issue in a couple ways, but I'm not sure which project is to blame (e.g. where I should submit the patch):
In test/unit.rb in ruby, I can replace the call to size with a call to count, but this only seems appropriate if Test::Unit expects a ParallelEach being part of the test suite
In minitest, I can alias count to size, which makes sense if minitest is responsible for sending ParallelEach objects to Test::Unit
Are either of these appropriate, or is there something else going on here (like a naming conflict)?
This turned out to be a bug in minitest, that has since been fixed: https://github.com/seattlerb/minitest/pull/275
Related
I have one of my application, that is created in Xcode 8. I have used CoreLocation and MapKit in that app.
I have update app with latest iOS till now. and it was working fine. Now I am updating application with iOS 1. So I hvae opened app with Xcode 11.0 and updated all the required code. Also updated setting that is suggested by Xcode "Perform Changes" and all that.
Now I run application, but I am getting error like :
Compiler error: Invalid library file.
I have searched lot, but can't find any solution. Is this a bug in new Xcode or new iOS ?
Is there anything I have to do extra changes or settings ? Please guide me.
Is this known bug by Apple ?
EDIT :
2019-10-18 10:34:39.899827+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.900098+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.915973+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.916228+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.920608+0530 MapLocation[1697:57778] Updated coordinate are : <+23.02055700,+72.50524900> +/- 5.00m (speed -1.00 mps / course -1.00) # 10/18/19, 10:34:39 AM India Standard Time
2019-10-18 10:34:39.920697+0530 MapLocation[1697:57778] Latitude:- 23.0206, Longitude:- 72.5052
2019-10-18 10:34:39.925441+0530 MapLocation[1697:57778] Entering in ----> (Latitude:- 23.0206, Longitude:- 72.5052), With Radius:- 300.00
2019-10-18 10:34:39.925546+0530 MapLocation[1697:57778] Stated in ----> (Latitude:- 23.0206, Longitude:- 72.5052), With Radius:- 300.00
2019-10-18 10:34:39.926582+0530 MapLocation[1697:57778] Exit from ----> (Latitude:- 23.0021, Longitude:- 72.4995), With Radius:- 300.00
2019-10-18 10:34:39.926683+0530 MapLocation[1697:57778] Stated in ----> (Latitude:- 23.0021, Longitude:- 72.4995), With Radius:- 300.00
2019-10-18 10:34:39.932080+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.932268+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.948942+0530 MapLocation[1697:57778] Compiler error: Invalid library file
2019-10-18 10:34:39.949220+0530 MapLocation[1697:57778] Compiler error: Invalid library file
I'm seeing this issue also. It only happens if you implement the renderFor overlay for MKMapView. And without this function, I can't display the polyline that I'm adding to the mapView. This was working fine in Xcode 10.
Hope this will be fixed in the next version of xcode. But this only happens on the simulator. Use your real device for testing for now..
For me what works is to disable OS Activity Logging.
Add the Environment Variable: OS_ACTIVITY_MODE with value: disable on Product > Scheme > Edit Scheme > Run > Arguments.
Warning
Folks have reported that other useful logs for them have also been silenced.
Taken from a similar answer I gave regarding WKWebView, but reposting here for visibility after finding the logging noise appears also with MKMapView.
I started running into this error recently and was able to get it to go away by clearing the Simulator from Hardware->Erase All Content and Settings... menu item.
I worked around this by using SwiftLog to log my messages, putting some unique string inside the tag of each logger (could just be com.yourcompany.yourapp to differentiate it), and then filtering to messages which contain that tag on the console.
A more general solution would be to have a negative filter inside the console view, which would obviate the need to use the logger in this way.
I've got the problem too, trying to update multiple polylines coordinates.
The problem was coming, in fact, from the way new coordinates were pushed into the array containing the polylines coordinates (which is a property of a model object in my case).
To get the problem, i was just pushing new coordinates into that array.
To solve the problem, I had to clone that array first in a new var, then add the new coordinate into the cloned array and update the model property.
Before, i was doing :
existingArray.push(object);
Now, I am doing :
var newArray = [...existingArray];
newArray.push(object);
existingArray = newArray;
Hope it can help !
For those of you experiencing this error with IOS 15, take a look at a helpful article on raywenderlich that says the error can be safely ignored:
Note: If you’re running on the Simulator, you’re likely to see a plethora of errors of the form Compiler error: Invalid library file in the Xcode console. This is a simulator bug and can safely be ignored. Unfortunately, it makes the console rather noisy, making it more difficult to see the results of your print statements.
You may want to do some more research to confirm this for yourself, but raywenderlich has never lead me astray.
For me, this only happens when I have Traffic turned on for the map.
I leave the feature on but turn it off in the simulator:
#IBOutlet
var mapView: MKMapView? {
didSet {
#if targetEnvironment(simulator)
mapView?.showsTraffic = false
#endif
}
}
I have a question regarding using the parameter_variation.py script provided on GitHub.
I'm using FMPy functions here (https://github.com/CATIA-Systems/FMPy) and have a specific error occurring only when I run a certain FMU, which is only slightly different from other FMU’s I’ve been using with a modified version of the parameter_variation.py example script provided.
Errors:
...
File "c:\parameter_variation.py", line 136, in simulate_fmu
fmu.terminate()
File "C:\AppData\Local\Continuum\anaconda3\lib\site-packages\fmpy\fmi2.py", line 231, in terminate
return self.fmi2Terminate(self.component)
File "C:\AppData\Local\Continuum\anaconda3\lib\site-packages\fmpy\fmi2.py", line 169, in w res = f(*args, **kwargs)
OSError: exception: access violation reading 0xFFFFFFFE1CD34660
End
I’m running 100 simulations for this FMU in 20 chunks, although the same FMU in the parameter_variation.py script appears to provide results if I run less than ~30 simulations in ~6 chunks.
Do you have any guesses why the access violation error may be occurring and how a solution can be forged? Let me know if this is enough information.
Thanks in advance.
In the title you mention multi-threading (multiple instances of the same FMU in the same process) which is not supported by many FMUs and can lead to unexpected side effects (e.g. through access to shared resources). If this is the case here you should be able to run your variation with a synchronized scheduler by setting the variable sync = True in parameter_variation.py (line 27).
I have these errors when I run my Unity project. They are related to a MCS character. These error cause other components to break. For example SALSA Lip-sync was not working correctly because this error was affecting the BlendShapes that are used by SALSA.
Error:
NullReferenceException: Object reference not set to an instance of an object
MORPH3D.COSTUMING.CostumeItem.setLODLevel (Single lodlevel, Boolean broadcast_change)
MORPH3D.COSTUMING.CIhair.setLODLevel (Single lodlevel, Boolean broadcast_change)
MORPH3D.SERVICES.CostumeModel.SetItemLODLevel (Single level)
MORPH3D.M3DCharacterManager.SyncCurrentLODLevel (Single level)
MORPH3D.M3DCharacterManager.initCharacterManager (Boolean refresh)
MORPH3D.M3DCharacterManager.Start ()
Warning:
Unable to find first CoreMesh/LOD in costume item: ShortPonytailHair, your asset will likely break and not work
UnityEngine.Debug:LogWarning(Object)
MORPH3D.COSTUMING.CostumeItem:DetectCoreMeshes()
MORPH3D.COSTUMING.CIhair:DetectCoreMeshes()
MORPH3D.M3DCharacterManager:DetectAttachedHair()
MORPH3D.M3DCharacterManager:initCharacterManager(Boolean)
MORPH3D.M3DCharacterManager:Start()
The problem turn up to be in one of the assets - the hair. The Mesh Type of the "C Ihair (script)" was incorrectly set to "body". It must be changed to "hair".
I am writting automatic test for GWT application. And I try to double click on table element. I am using this code fo click:
browser.element(:xpath, '/html/body/div[5]/div[2]/div/div/div/div[2]/div/div/div/div/div/div/div/div[2]/div/div[2]/div/div/table/tbody[2]/tr[1]/td[1]/div').double_click
When this command is executed I get error like:
test_search(TC_article_example):Selenium::WebDriver::Error::InvalidElementStateError: Cannot perform native interaction: Could not load native events component.
[remote server] file:///C:/Users/TOMASZ~1.RYB/AppData/Local/Temp/webdriver-profile20130403-4556-12yrrcd/extensions/fxdriver#googlecode.com/components/driver_component.js:8577:in `generateErrorForNativeEvents'
[remote server] file:///C:/Users/TOMASZ~1.RYB/AppData/Local/Temp/webdriver-profile20130403-4556-12yrrcd/extensions/fxdriver#googlecode.com/components/driver_component.js:8610:in `FirefoxDriver.prototype.mouseMove'
[remote server] file:///C:/Users/TOMASZ~1.RYB/AppData/Local/Temp/webdriver-profile20130403-4556-12yrrcd/extensions/fxdriver#googlecode.com/components/command_processor.js:10275:in `DelayedCommand.prototype.executeInternal_/h'
[remote server] file:///C:/Users/TOMASZ~1.RYB/AppData/Local/Temp/webdriver-profile20130403-4556-12yrrcd/extensions/fxdriver#googlecode.com/components/command_processor.js:10280:in `DelayedCommand.prototype.executeInternal_'
[remote server] file:///C:/Users/TOMASZ~1.RYB/AppData/Local/Temp/webdriver-profile20130403-4556-12yrrcd/extensions/fxdriver#googlecode.com/components/command_processor.js:10220:in `DelayedCommand.prototype.execute/<'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/response.rb:52:in `assert_ok'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/response.rb:15:in `initialize'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/http/common.rb:59:in `new'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/http/common.rb:59:in `create_response'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/http/default.rb:66:in `request'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/http/common.rb:40:in `call'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/bridge.rb:616:in `raw_execute'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/bridge.rb:594:in `execute'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/remote/bridge.rb:389:in `mouseMoveTo'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/common/mouse.rb:54:in `move_to'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/common/action_builder.rb:344:in `block in perform'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/common/action_builder.rb:343:in `each'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/selenium-webdriver-2.31.0/lib/selenium/webdriver/common/action_builder.rb:343:in `perform'
C:/Ruby193/lib/ruby/gems/1.9.1/gems/watir-webdriver-0.6.2/lib/watir-webdriver/elements/element.rb:181:in `hover'
C:/Watir/polisy.rb:27:in `test_search'
I have added this code to my script but this didn't help:
profile = Selenium::WebDriver::Firefox::Profile.new
profile.native_events = false
browser = Watir::Browser.new :firefox, :profile => profile
Please give me some tip. I use selenium 2.31, watir 4.0 and firefox 19.0.2.
PS: Sorry for my english.
The error sounds like it wants native events, and you are disallowing them. try changing the profile setting for native events to true
Also ditch the ugly, brittle, impossible to read xpath. Watir has far more readable, less brittle ways to identify the div you are trying to click.
Start a new question, include some of the HTML for the table where that div lives, the logic for how you are picking it (surely it relates to the content of the table? not just second cell of the second row of the third tablebody) and we can give you some advice on how to better select the element that will result in code that makes sense and is readable, won't break if the table contents change slightly, and won't break at the slightest re-design of the page.
I am trying to read a movie in avi format. But it's giving me the following error:
xyloObj = mmreader('1.avi',[1 5]);
??? Initialization failed. (No combination of intermediate filters could be found to make the connection.)
Error in ==>
mmreader.mmreader>mmreader.init at 423
obj.MMReaderImpl = audiovideo.mmreader(fullName);
Error in ==>
mmreader.mmreader>mmreader.mmreader at 133
obj.init(fileName);
Kindly help me
The likely source of the error is that you are missing the proper codec required to read the given AVI file. Apparently, this can often happen when using 64-bit versions of MATLAB on 64-bit Windows platforms. There are a number of solutions you can try given in this technical support documentation from the MathWorks.
First, can you play it with another application (such as VLC player, Windows Media Player, QuickTime, etc.) on your computer?
If yes, go to gnovice's link.
If no, go get the GSpot codec information tool which is very useful for determining which codec you need. Download the codec and make it work with a video player, then Matlab.
This pdf explains how to solve your problem. Or just use:
vid = aviread('Vid261.avi');
vi = frame2im(vid(1)) ;