Version: 3.8.2.RELEASE
Build Id: 201610040743
Platform: Eclipse Neon.1 (4.6.1)
This is my version
Plug-in org.springsource.ide.eclipse.commons.gettingstarted was unable to load class org.springsource.ide.eclipse.commons.gettingstarted.dashboard.WelcomeDashboard
It can depends on your OS, as seen here
The 'WelcomeDashboard' uses JavaFX which requires Java 1.8 and GTK2 on unix systems. Eclipse 4.4 runs with GTK3 by default.
As mentioned in issue 252,
The error log probably contains more detailed information and/or other errors that might help determine why this class could not be loaded. You can use menu "Window >> Show View >> Other >> Error Log" to show the error log.
Maybe something indicative of problems activating bundles. The reason the class can't be found is probably because some bundle requirement aren't satisfied on startup.
you could also try to open a console view, switch to the Host OSGI Console, and try a > diag org.springsource.ide.eclipse.commons.gettingstarted to see if there is a problem with that bundle (not resolved for any reason, for example).
As in:
You would see typically:
The same issue adds:
You can use the 'Old Dashboard' as a workaround. It offers the same functionality as the one that for still unknown reason isn't work for you. To switch to the old dashboard do as follows:
Go to Menu "Window >> Preferences".
Search for 'dashboard'. Then select 'Use Old Dashboard' as in the screenshot below.
Then click the 'Apply and Close' button to save the changed setting.
Then close the 'new dashboard' (that is the view in your screenshot that has the error in it).
Now you can reopen the dashboard by clicking on the Dashboard icon in the toolbar. I.e. this one:
Related
I have written an Espresso test that fails (matching view not found).
Example:
onView((allOf(withText("OK"), hasSibling(withText("Text"))))).perform(click());
The error I get is:
androidx.test.espresso.NoMatchingViewException: No views in hierarchy found
matching: (with text: is "OK" and has sibling: with text: is "Text")
If the target view is not part of the view hierarchy, you may need to use
Espresso.onData to load it from one of the following
AdapterViews:androidx.appcompat.widget.AppCompatSpinner{da0caf9 VFED..CL.
........ 273,0-505,48 #7f0901c1 app:id/structure_formation_spinner}
View Hierarchy:
....
Then the view hierarchy is displayed. The problem is that in Android Studio, the hierarchy is truncated to 32K characters.
I know how to fix the returned error, this is not my problem.
My question is: How can I see the full view hierarchy ?
Is it possible in Android Studio?
If not, is it possible from the command line?
Since the test is executed on the Device/Emulator, exception with the full message (view hierarchy is just a message, attached to NoMatchingViewException) can be obtained from Logcat (i.e. Logcat window in the Android Studio). Filter E/TestRunner simplifies the search.
Logcat itself is not unlimited though. Default size is 1024KB. It can be changed via Settings | Editor | General | Console
TL;DR;
Android Studio and Android Device/Emulator communicate via protobuf messages. Data from the device arrives to com.android.ddmlib.testrunner.InstrumentationProtoResultParser#updateState in the form of key-value map (collection of InstrumentationData.ResultsBundleEntry).
Instrumented Test Results view in Android Studio only displays stackTrace. You can convince yourself by adding println("hello") anywhere in the instrumented test. The line will only appear in the Logcat, and not in the Test Result view.
stackTrace is obtained from the map by key StatusKeys.STACK (see ln 239). Unfortunately, data already arrives truncated at this point. There is STREAM key which contains the full text, but it is not used. So the problem is on device side which failed to send complete stacktrace, IMO.
Other runners (e.g., gradle, when running from console) may use different values from that map. This explains why you see full message when running from console.
The only way I have found is to launch the test in a "terminal" window.
Then the full hierarchy is displayed (around 300K chars in my case)
You can also checkout Radiography by Square. It will help you to print the view hierachy in the logs.
After publishing the application I get the error:
"InvalidOperationException: The layout view '_Layout' could not be located. The following locations were searched:
/Views/Home/_Layout.cshtml
/Views/Shared/_Layout.cshtml
Microsoft.AspNetCore.Mvc.Razor.RazorView.GetLayoutPage(ViewContext context, string executingFilePath, string layoutPath)"
The Layout is there in the Views/Shared folder and the application works with it locally, so this must be something wrong with the publishing.
Unfortunately in the published app the views appear all contained into a single dll file and I cannot do anything to solve the problem.
Could be anything in my code that makes the publisher to forget to add the _Layout.cshtml view?
I have a reference to the layout in my _ViewStart.cshtml
That should be for all pages. Without Layout my app is doomed and I do not know what to do.
Ok After many tries I found the cause of why the publishing did not include my layout page! It was so tricky that I am amazed. I hope this helps other people!
When you right-click on the layout file (or on any other file) you have the menu with the option properties. I opened the properties of the layout file and I noticed that there you have an "advanced" option: "Compilation Action". My option was set to "none" that means the file was not compiled and therefore not included in the publishing. I put it on "Content" and tried the publishing again and all went well, this time the layout file was compiled and included in the publishing.
In my case the "Copy to output directory" was set to "Do Not Copy", I changed it "Copy if newer" and then it work.
I recently upgraded to RedHawk V2.1.0, which has fixed several of the issues I had with previous versions, but one feature that I used seems to now not work. I have rebuilt and installed working components and waveforms. One of the components has a unsigned short property that is configured as readwrite and has an external id in the waveform. With v 2.0.1 I could launch and start the waveform and then view the properties in the properties tab at the bottom of the IDE window for the waveform or any component I clicked on and I could change a value in that window while the component was running or stop the component change it and restart. With version 2.1.0 I can still override the value when launching the waveform, but after launch the properties tab at the bottom displays the original default value (not the overridden value from launch) and it is not editable when the component is started or stopped. Was this changed intentionally or is this a bug? It seems to be true of all properties my components have. I have checked that these are still listed as readwrite in the prf file.
Or is there now a different way to change property values on the fly?
I should add that I am running in a domain, NOT the sandbox.
I think that I noticed this in the 2.0.5 IDE as well. For the time being, try just removing the "external" attribute from the PRF for that property and see what you get. I anticipate that this will be fixed in the next release of the 2.0.x and 2.1.x series.
Action type="external" in PRF or declaring in externalproperties in SAD does NOT affect ability to edit in the Properties panel, but I found that the checkbox for "Pass on command line" DID affect this. I am fairly certain that with v2.0.1 I was able to check pass on command line and still edit the value in the panel. With 2.1.0 checking it makes it NOT editable but without it checked I CAN edit. I am not sure if this change was intentional or not but at least I know how to work around it.
Opening a VB6 Project, I get errors like:
Errors during load. Refer to xyz.LOG
I open the log file and see these errors:
Line 42: Class Threed.SSPanel of control XYZ was not a loaded control
class.
In this case I can see the problem is due to the Sheridan 3D Controls: C:\WINDOWS\system32\THREED32.OCX
I thought the project was missing a component so, VB6 > Project > Components > tick the Sheridan 3D Controls and got this error:
---------------------- Microsoft Visual Basic ---------------------------
Name conflicts with existing module, project, or object library
--------------------------- OK Help ---------------------------
I will give you the best way to get rid of this problem. I came across many ways, but this is the most best way to deal with..
Close the project. Right click on the vb project and open with notepad (not with vb). This Project file will only consist of all the references, libraries and information about forms and modules used in the project.
Now just remove the conflicting module or component file, you have problem, by just deleting the entire line.. Save and close it
and now open the project and add component. I swear you wont get that error.
Thank you. Enjoy
The way to troubleshoot this problem is to start a new VB6 project > Project Menu Components > tick the Components that are selected in the affected project until you get the error.
---------------------- Microsoft Visual Basic ---------------------------
Name conflicts with existing module, project, or object library
--------------------------- OK Help ---------------------------
You need to narrow it down to the two OCX's that are conflicting.
In my case I narrowed it down to Sheridan 3D Controls / THREED32.OCX and Outrider Spin Control / SPIN32.ocx
To fix the problem I used RegSvr32 to unregister the OCXs - make sure you UNregister with the /u flag.
REGSVR32 "C:\WINDOWS\system32\THREED32.OCX" /u
I then copied the OCX's to the project folder and registered them again using:
REGSVR32 "C:\Dev\Project\THREED32.OCX"
Then in the project with the problem > Project Menu Components > select the item in the listbox Sheridan 3D controls / THREED32.ocx (you cant tick without getting the error or untick the conflicting one that is selected as its in use) > click Browse and reference it from the project folder rather than C:\WINDOWS\system32\
Another trick is close the project and unregister the affected ocx - make sure you UNregister it with the /u flag, eg
RegSvr32 "c:\Windows\system32\mscomctl.ocx" /u
Then open the project > Components > and you should see the "Microsoft Windows Common Controls 6.0 (SP6)" is using a OCX file in C:...\Microsoft Vi..\VB98\mscomctl.ocx" rather than c:\Windows\system32\mscomctl.ocx.
The project should then load without these errors:
Errors during load. Refer to xyz.LOG
Try unchecking the latest object library / reference from the references and check it again and then go for your desired reference (vb6 has few bugs which can be countered by a reverse process). I solved the error mentioned using this process.
Just getting started with xamarin studio and iOS development... I'm trying to set up my development projects. When setting all this up, I had initially created a project called 'MyProject.iOS'. I later decided that I didn't want the 'p' in MyProject to be capitalized. I deleted the existing project (using finder), removed it from my existing solution, and created a new one named 'Myproject.iOS'.
Now, when I try to open the Myproject_iOSViewController.xib file to edit in xCode, I get the following error:
Error updating Objective-C type information. Multiple types (MyProject.iOS.AppDelegate and Myproject.iOS.AppDelegate) registered with the same Objective-C name: AppDelegate
Seems like something is stuck in xCode from my original project that had the same name w/ different casing. I looked in Finder and confirmed that all the old files are gone.
I believe I am experiencing the same issue that was reported here (not sure why this issue is marked as resolved): https://bugzilla.xamarin.com/show_bug.cgi?id=7550
The last commenter has a great repo and reports this solution that worked for him:
1. Close XS
2. Delete ~/Library/Caches/XamarinStudio-4.0 folder
3. Open XS : voilà everything works again now !
My issue at this point is that I cannot find the ~/Library/Caches/XamarinStudio-4.0 to delete. I found a ~Library/Caches/ folder but it did not have a XamarinStudio-4.0 sub-folder in there. How can I resolve this?
I am using 4.0.9 (Build 12) of Xamarin studio.
Here is the full stack trace from the error message box that shows up when I double click the xib file:
System.ArgumentException: Multiple types (MyProject.iOS.AppDelegate and Myproject.iOS.AppDelegate) registered with the same Objective-C name: AppDelegate
at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update () [0x00118] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.0.9-branch/f9c5c24e/source/md-addins/MonoDevelop.MacDev/MonoDevelop.MacDev/ObjCIntegration/NSObjectProjectInfo.cs:98
at MonoDevelop.MacDev.ObjCIntegration.NSObjectProjectInfo.Update (Boolean force) [0x0000c] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.0.9-branch/f9c5c24e/source/md-addins/MonoDevelop.MacDev/MonoDevelop.MacDev/ObjCIntegration/NSObjectProjectInfo.cs:72
at MonoDevelop.MacDev.XcodeSyncing.XcodeProjectTracker.UpdateTypes (IProgressMonitor monitor) [0x0003c] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-4.0.9-branch/f9c5c24e/source/md-addins/MonoDevelop.MacDev/MonoDevelop.MacDev/XcodeSyncing/XcodeProjectTracker.cs:476
I just had this problem. I used that post to solve it. At first I could not find the folder that is referenced. This is how I found it.
Go into finder on the Mac.
Under Favorites on the left of the screen, select the primary volume. For me that was labeled Macintosh HD.
Select Go/Go to Folder from the toolbar.
In the Go to the Folder screen that pops up type in ~/Library.
From there you can navigate to the proper directory and delete it.
Hope that helps. Best of luck.