I am using VSCode to design DMN files. Sometimes when I try to read a file, it simply displays the message:
Editor content has not been set.
Something went wrong. An attempt has been made to view the editor before content is set.
Is there any way to find the error message that was actually produced when reading the file? Usually the exception that is thrown has a much better description about what is missing or wrong with the file. I have searched for log files produced by VSCode but I can't find any with this or any related error in it.
There are three possible reasons to explain the above error.
Your DMN file is invalid (eg. a XML tag is wrong or the schema hierarchy is broken)
Your DMN file version is not supported by the editor. Currently, the editor supports up to DMN version 1.3
An unexpected error occurred. In that case, the analysis of your file is the only way to determine the root cause.
The next version of the extension (0.27.0), will show an additional message reporting the root cause of the issue.
Related
Step 30: Debugging Tools of the UI5 documentation introduces the diagnostics, which can be accessed through the ctrl-alt-shift-S keycombo.
After deliberately inserting an error in a path, I've tried navigating to the binding info in the control tree as instructed:
I'm supposed to be able to see that the binding path of the number attribute is marked as invalid
It cannot possibly rely on me spotting the typo because that would imply already knowing what the error is in the first place.
Can anybody explain how exactly I should do that?
Additionally:
Chrome 84.0 or Firefox 79.0, same results.
tried the online version from the official demo kit as well as my own localhost copy
The fix is now in the master branch of UI5. If you run the downloaded sample with
https://openui5nightly.hana.ondemand.com/resources/sap-ui-core.js, we can see the invalid binding path indication:
ExTendedPrice (invalid)
I'm currently taking over someone's else project who was in a different country. He is using MumbleKit in his project, however when i try building the project, these errors occurred.
error: input is not a PCH file: '/Users/kai/Library/Developer/Xcode/DerivedData/TestBuild-bivflkvgwypsqidilllttbdfyjjq/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/70367429320928002/CELT-0.7.pch.gch'
fatal error: file '/Users/kai/Library/Developer/Xcode/DerivedData/TestBuild-bivflkvgwypsqidilllttbdfyjjq/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/70367429320928002/CELT-0.7.pch.gch' is not a valid precompiled PCH file
Now, i have tried fixing the header path file and cleaning the project and deleting derived folder's content, still this error occurred. I believe xcode is trying to find a pch file but this .gch is being created instead. How can i prevent this .gch from being created in the derived folder? Or how do i fix this in general since i don't really deal with 3rd party project dependency before.
EDIT : I believe this error is coming from the 3rd party Mumble kit, CELT-0.7 project
Okay, I've found the solution, Mumble kit's CELT project have a file : Base.xcconfig.
There is a variable, GCC_PRECOMPILE_PREFIX_HEADER, initially it was set to YES, after set it NO, that fixed it. Though it will be nice if someone would explain to me what it does exactly.
I am working on a VB6 application and I have requested to change the platinum gray style forms' to our new format.
In order to do that, I have first modified the Backcolorattribute as H8000000E (it was H8000000F previously) for labels, frames and forms.
Those forms were saved with .Dsr extension.
Each form is having three fils with .Dsr, .DCA and .dsx extensions.
After I modified the Backcolor, I compiled the code and it ran successfully. Then I close the project, reopen it and run again.
Then I got the Error in Loading DLL error.
We didn't commit the .DCA files to git. But once I committed one .DCA file and it caused a build failure. But this is occurring without even commit any changes.
I am still unable to find a reason why this occurred.
Could anybody please help me with this?
Thank you.
I removed the .DCA files set and it resolve the problem.
DCA is a temporary type information cache file created by Visual Basic. It is used by VB to speed up compilation.
I accidentally published Composite C1 from Visual Studio with "Precompile during publishing" when I first set it up and have now come to realize that several plugins do not work with precompile turned on. Unfortunately I have no idea how to reverse this. I've tried several things to no avail. I usually end up with a 500.0 error. If I go to the admin interface everything is working properly, and I can even preview the pages, but from the customer side all I get is a 500.0 error.
Of course I could republish from the Visual Studio project I have, but that project has the default template on it. I've tried copying what appears to be changed on the server to the original project but I end up with a 500 error. I've tried removing all the precompiled stuff on the server but I end up with a 500 error. I'm pretty lost.
At this point I'm willing to do anything. Is there a doc explaining how to copy the content to a newly downloaded copy, kind of like an upgrade doc but "side-grading"? I am using the most current version at the time of writing this 4.2 Update 1
Thank you
Solved use the PackageCreator suggested by wysocki's answer. It was not exactly straight forward to create the package. The errors can very cryptic at times. So here are some of the issues I encountered and how I got past them:
wysocki was correct to suggesting starting with a bare bones installation even though my original project was started with the Venus theme. I tried both ways.
I encountered issues with the MasterLayout and the Page Template Features which are currently not supported by the PackageCreator, although they may be supported in future versions. The solution was to add the missing elements to the fresh C1 project from the original C1 installation in the App_Data/PageTemplates and App_Data/PageTemplateFeatures folders.
A few times I ran into an issue where I added the same page or function twice to the PackageCreator. This was obviously my fault, but it should be mentioned that you can add the same site element twice which throws and error on import. Make sure you are careful to only getting one of each when creating the package to be exported.
If you are getting and error and it uses and Id like "4061397b-ee9e-4512-984d-f2b2d41eb654" I've found that it was very helpful to extract the zip file you are trying to import and then search the extracted folders for that Id. The lines with the Id usually have more information on them that will help you to identify exactly what content page or whatever the error is being generated from.
If you are using installed packages in your project like SimpleSearch for example, make sure you don't add it's functions to the PackageCreator. Install them separately.
I had an issue where I somehow had an element in the Data section that didn't have a "type". The error simply "The type cannot be empty". This was obviously tough to find so I suppose the lesson is, less is more. If you think your project might have a few elements that are unnecessary, don't add them at first and see if the project you import them into complains about missing them. It's much easier to troubleshoot missing elements than it is to figure out which element is causing the issue that you really didn't need.
Is there a doc explaining how to copy the content to a newly downloaded copy
You can try and export content / templates / anything else related to a "package" via Composite.Tools.PackageCreator.
Its latest version gives you quite a lot of flexibility in what you can export ("package") - please its user manual.
Once the package is made and downloaded, you can go on and install it on a new website. If you export / import a lot of content / templates etc, it makes sense to have a "Bare Bones" site as the new one.
All the starter sites like "Neptune", "Venus" are installed as a bunch of packages in specific order during Composite C1's initial setup.
I have an MVC2 application and use ReSharper 6.1 - I've heavily customised the Code Inspection Severity and edited what it decides to show as errors, warnings, suggestions and hints, but I cannot seem to stop it from telling me that a specific resource is missing when utilising a HTMLHelper.
So, for instance:
<img src="<%:Url.Content("~/Resources/Image12345.jpg")%>" />
I get an error on every line similar to the above telling me that the path above does not exist - which at design time it does not, but during the build process all of these views are XCOPY'd to a location which contains all of the resources, such as the images, so at the point of running the application all of this path resolution is correct. Because of working in a team of people, some of which are new to ReSharper, I wanted to exclude this error from appearing as it may cause colleagues of mine to start fiddling with something that isn't broken.
ReSharper obviously doesn't know that this isn't an issue and it has no way of knowing which is why I want to turn off this specific bit of analysis. I've found on the whole that ReSharper is massively customizable and in version 6.1 under Inspection Severity there are some new MVC options, which have proved useful - but I can see no way of turning off the inspection for this.
Anybody have any ideas?
There are few options, press ALT+ENTER.
Suppress inspection "Path Error" with comment. You can suppress whole block of code, not only each of tag.
Suppress inspection "Path Error" at all at whole project.
There is new feature of 6.1 - path mapping, but it seems broken in conjunction with MVC.
Set to ignore that specific error by:
Open Soultion Errors Window by ReSharper->Windows->Soultion Errors Window.
Right-click annoying error and select Ignore Error.
See answer for another error for more explanation.
Well - It seems that this particular type of inspection is not currently catered for. I'll see if I can request it with JetBrains and hopefully more granular MVC inspection will be included in the future.
Cheers guys