Resolving NED Path issue Veins/Omnet++ - simulation

I am working with veins. I needed to change the default behavior of BaseWaveApplLayer. Rather doing in file changes, I created a second application file with the name MyApp. I added MyApp.cc, MyApp.h, MyApp.ned files. Then I duplicated TraCIDemoRSU11p, and added files for TraCIDemoRSU11pEnhanced. Now in .ini file when I changed *.rsu[*].applType to point to "TraCIDemoRSU11pEnhanced". It compiles fine, but when I try to run it, generates the following error:
Submodule appl: no module type named `TraCIDemo11pEnhanced' found that implements module interface org.car2x.veins.base.modules.IBaseApplLayer (not in the loaded NED files?).
In MyApp.ned file it is declared to be of type IBaseApplLayer. I tried setting ned-path parameter in ini file, didn't resolve the problem. In veins project properties, NED source folder is checked. Do I have to add the ned path for the newly created application file, somewhere?

Try using the cookiecutter package (https://veins.car2x.org/tutorial/#newprojects) to create new applications that use veins instead of copying and pasting files:
Use pip to install the package (https://github.com/cookiecutter/cookiecutter)
Then follow the steps in (https://github.com/veins/cookiecutter-veins-project/blob/master/README.md) to create the new project; following the prompts that appear.
This will create a new project that uses Veins and has the application layer-related files for you to update according to your application with no errors.

Related

Why does an attempted export of a plugin fragment "not find the exported unit"?

I am writing a plugin fragment named JunitGenerationFragment. I can test it using Launch an Eclipse application, and everything works fine.
I try to export using the 3 steps on the Exporting section of the manifest's Overview tab. When using the Export Wizard, I choose to install into a particular directory.
I get a Problems Occurred dialog that says "Could not find the exported unit with id..."
As far as I can tell, the directories have the appropriate content.
However, if I try to install from that site, "There are no items available".
How can I successfully make this plugin fragment available from the export repository?
Possibly there was some kind of file system problem? Additional attempts to export the repository to the C:\Tools\Eclipse\workspace2019-06\.metadata\.plugins\org.eclipse.pde.core\install directory failed. However, I could export to another directory.
Later, I renamed the original C:\Tools\Eclipse\workspace2019-06\.metadata\.plugins\org.eclipse.pde.core\install directory to something else and retried an export to C:\Tools\Eclipse\workspace2019-06\.metadata\.plugins\org.eclipse.pde.core\install. This time it succeeded, and I could load the plugin from that repository.
Update: The renaming "solution" does not seem to be repeatable. A repeat attempt to use the Export Wizard to exprort to C:\Tools\Eclipse\workspace2019-06\.metadata\.plugins\org.eclipse.pde.core\install fails, as in the original problem description. Renaming the directory again did not help.

Change .vscode folder location

I'm programming a client side applications using SharePoint Designer 2013.
I want to change to VSCODE since it supports a lot of extensions for some Javascript library like angular, jQuery. And because of the Chrome/Node.js debugger extension.
But when I try to start any Debugger, I got the error:
Unable to create 'launch.json' file inside the '.vscode' folder (Error: UNKNOWN: unknown error, mkdir '\\servername\DavWWWRoot\sitename\Style Library\.vscode').
I get this error because it's impossible to create a folder in SharePoint where the name starts with dot.
So there's a possibility to change the name of this folder or the file location to any directory in my local computer?
No, it's not possible to move/rename that folder. VS code is a tool that bases project management on folder content. So it is essential that the project settings reside in the folder being managed.
You can move the "extensions" folder, but unfortunately not the argv.json (so the ".vscode" will, at least be recreated on vscode launch)
https://github.com/microsoft/vscode/issues/17691#issuecomment-559234574
I hope that'll finally change sometime .
https://github.com/microsoft/vscode/issues/3884
https://github.com/OmniSharp/omnisharp-roslyn/issues/953

Aurelia exported bundle causes a 404 from SystemJS if a source module was in a subdirectory

I'm learning Aurelia via the TypeScript / ASP.NET Core skeleton navigation app. Everything runs fine in its default state. To test the exported production bundle, I run the Gulp Export task, then publish the app via Visual Studio project publish to a local folder, then replace the published wwwroot folder with the wwwroot folder from within the "export" folder, then use dotnet from the command line to run the app.
Things break if I have any source modules in a subdirectory. For example, I moved the welcome.ts/html component files into "/src/Pages" and adjusted its route moduleId in app.ts accordingly to "./pages/welcome". The unbundled app then still runs up fine, but when I try the exported version, I get a request being made by SystemJS to http://localhost:5000/dist/pages/welcome.js which 404s (as you'd expect).
I can see the contents of the welcome component in the app-build.js file, and the config.js file within the export folder contains the expected file paths, i.e. it has "Pages/welcome...".
I have read this seemingly similar issue:
https://github.com/aurelia/bundler/issues/131
But setting depCache to false made no difference in my case. Why is SystemJS trying to load this module separately from outside of the bundle?
I was able to reproduce this error locally.
Presuming that you have a Windows environment, it will be a case-sensitivity issue.
After renaming [P]ages folder to [p]ages, bundled version works as expected.
On the filesystem there is a [P]ages/welcome.js viewmodel, but [p]ages/welcome has been defined as moduleId.
Unbundled mode: Windows filesystem is case-insensitive, which behaviour can be misleading by loading [P]ages/welcome.js correctly.
Bundled mode:
Based on file path, bundling process embeds[P]ages/welcome.js as [P]ages/welcome module.
But, according to the route config, SystemJS will be looking for [p]ages/welcome module within app-build.js.
My recommendation would be to use lowercase folder/filenames whenever it's possible.

Unity3D 5 packages conflict

I have Unity 5.0.2f1. Firstly, I've successfully added GooglePlayGamesPlugin-0.9.20.unitypackage to my project. Then, I've tried to import GoogleMobileAds.unitypackage, but I got these errors:
Error importing folder (The pathName assets/plugins is already mapped to fce8a713f1e5a4cc4b9973d1ef630f31. But the meta data wants it to be mapped to cbde64d36fd994c458fffca9e931b232)
Error importing folder (The pathName assets/plugins/android is already mapped to b8f0d9a6a7f9240c981894807effddbc. But the meta data wants it to be mapped to 2f5d736f7c4cb4c1e80d0816d0e81625)
Error importing folder (The pathName assets/plugins/ios is already mapped to 6490bb8acab6f4f92b29615e7429b8df. But the meta data wants it to be mapped to da135550add3c4abca622bda5280d204)
How to resolve this?
First make a backup of your project and delete your metadata files in your asset project folder and childs.
Files with extension .meta
The easiest workaround I could come up with:
1. Within the Unity Editor, create a subfolder of the Assets folder, for instance called TEMP123.
2. Move the entire (other) content of the Assets folder to TEMP123.
3. Import your package.
4. Manually merge the content of TEMP123back to the Assets folder.
If you see these kinds of errors, reimport all the assets. This reprocesses the metadata and the error goes off.

Netbeans and PHPUnit Skeletion Generator: No such file or directory

I use netbeans 7.2.1 and newest phpunit. When I want to generate a unit test in netbeans by right-clicking on the php class then Tools-> Create phpUnit test the Skeleton generator throws an error: No such file or directory.
require_once(/sharedResources/connection.inc.php): failed to open stream: No such file or directory
The issue is that the path displayed in require_once is wrong. It is generatedliek this:
$sharedResources = getenv("DOCUMENT_ROOT") . "/sharedResources";
and should resolve to the absolute file path. This works fine when application is running in apache. However it seems that getenv("DOCUMENT_ROOT") is just wrong when running from netbeans. My question is how I can set it correctly? My application is under
getenv("DOCUMENT_ROOT") . "/MyApp";
and the file I'm creating a test for is in
"MyApp/services"
Under Project properties there is an option web root but it is greyed out and it is impossible to set it to a folder one level higher than your application.
How can I solve this?
EDIT:
Further clarification:
I initially had a relative filepath to sharedResources which did not work also. the I changed to this one and of coruse ti makes sense it is not working as DOCUMENT_ROOT is set by apache and hence not set when running in netbeans. So a temprary fix is to add
$docRoot = getenv("DOCUMENT_ROOT");
if(empty($docRoot)){
putenv("DOCUMENT_ROOT=C:/xampp/htdocs");
}
to the head of every class. of course that is not a very practical or good solution. I would need to tell netbeans to set this environment variable or to use correct relative path.
Well here is my solution. It's not ideal but simple and works. The issue is that DOCUMENT_ROOT is obviously empty when script is not called by Apache but by netbeans. Hence it must somehow be set. To do that I edited the php file phpunit-skelgen(it does not have a file ending but it's a php file).
Below the license text as first php line I added
putenv("DOCUMENT_ROOT=C:/xampp/htdocs");
That did the trick.