Some of megasparkDiff libraries are not importing - apache-spark

I have cloned the MegaSparkDiff project from GitHub and just wanted to try it out. I use IntelliJ IDE, the project has sample examples and different libraries. Unfortunately, some libraries are not getting imported
I have tried to reload maven, deleted this project, and re-cloned again, but I am getting the same problem, which these libraries/classes are not getting imported :
import org.finra.msd.sparkcompare.SparkCompare;import org.finra.msd.sparkfactory.SparkFactory;
import org.finra.msd.containers.AppleTable;import org.finra.msd.containers.DiffResult;
so, how can I resolve this issue?

Related

Unresolved Reference to any class from kotlinx.coroutines. package

In an android Studio Project I received where kotlin coroutines library is added as dependency
implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.3.8",
implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.8",
Although everything builds and runs perfectly well, in Android Studio itself I see Unresolved Reference Errors on every import of a class from kotlinx.coroutines package.
And in my External Libs folder the jar file for corouties core seems not to have appropriate files: see screenshotsenter image description here
I searched the internet and tried various things that I could find but there is very few information on this topic and I nothing helped me
EDIT:
I seem to have found the culprit. It appears to be the kotlin.mpp.enableGranularSourceSetsMetadata=true in the gradle.properties file. When I commented it out the libraries imported properly and the classes work as expected.
I filed an issue on issuetracker.google.com:
END EDIT
I'm having the same issue using org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1-native-mt.
It's not clear where I would post a bug report...
Creating a new project and adding just adding coroutines has not reproduced the issue. So I have seen it work. My best guess at the moment is that it's some sort of conflicting dependency or dependency that causes a problem with AS pulling in the external library jar and sources.
Here is the project external libraries where it is not working. Image showing external klibs for commonMain, nativeMain:
And here is the one that works properly. Image showing coroutines-core with source and metadata:

KMM how to import the generated Greeting class in my current project?

I've added a KMM module in my Android Studio project.
My project builds successfully.
Now to test everything I'm trying to use the auto-created Greeting class in my main project, but autocompletion does not suggests the class.
Am I missing something? Do I need to add something to my gradle file?
Thanks!
If you have just created a new project with KMM Application Template then you might have already got the simple example where Greeting is already imported in the project.
Although if you are not able to import in any case then please check if you have added shared module in your dependencies of App level build.gradle.kts it looks like this :- implementation(project(":shared"))
and then you need to import is as
your shared package name.Greeting for example :- import com.example.kmmsample.shared.Greeting you can get your shared package name in manifest file for shared module it should be named as androidMain\AndroidManifest.xml
Now in iOS you can simply add it as import shared if you have already added it in your Framework.

Your application could not be compiled, because its dependencies could not be established

Your application could not be compiled, because its dependencies could not be established.
The following Dart file:
C:\flutter\packages\flutter\lib\foundation.dart
...refers, in an import, to the following library:
C:\flutter.pub-cache\hosted\pub.dartlang.org\meta-1.1.5\lib\meta.dart
Unfortunately, that library does not appear to exist on your file system.
it says that you are trying to import a library that does not exist.try to run
flutter packages get that will get the packages you need and this might solve your problem
Thanks... I solve by running the
flutter packages get
Although I tried this before as a i was connected to slow internet, but the moment i was on a faster internet it worked... thanks
Sorry for the bad formatting, i'm new here.

import an extension module in node

I have a Node.js Angular app which I am trying to import babylon.js into.
Current Setup
1) npm install --save babylonjs to get the npm repo installed in my project's node modules.
The following image depicts the folder structure of the npm repo.
2)In my angular component I import the BABYLON declaration from the babylon.module.d.ts and babylon.max.js files in the above picture like so.
import * as BABYLON from 'babylon.js'
Babylonjs now works great, has typings enabled and everything, so I
can use BABYLON as pictured below
Problem
None of the included extensions are hooked up. These extensions are located in the following folders
(Full folder structure is in the first image. I left the gui folder open since that is the specific extension I am >trying to activate at this time)
The main babylon.module.d.ts file defines BABYLON as follows:
declare module BABYLON { //class types are defined in here }
The gui extension (all others follow the same logic) declares itself as a part of BABYLON as follows:
declare module BABYLON.GUI { //extend classes & create new classes in here in here }
Attempted solutions
1) babylon.gui.d.ts declares BABYLON.GUI so I simply tried the following
import * as BABYLON from 'babylonjs';
import * as BABYLON.GUI from 'babylonjs/dist/preview release/gui/babylon.gui';
This generates the following Typescript error: Duplicate identifier 'BABYLON', which is not surprising, however, BABYLON.GUI is how thebabylon.gui.d.ts` file declares its parts.
2) Using the CDN in the index.html file. This works, however, types will not work. Even if I got typings to work,using the CDN is less performant. The resources will be loaded in the document <head> every page. with imports the resources will only be queried when the component is active.
3) Appending the babylon.gui.d.ts file to the babylon.module.d.ts file. BABYLON.GUI` is still undefined.
Modifications to the npm repo are undesireable anyways, since any npm updates, or installs will overwrite the changes.
4) I spoke with a BABYLON developer here, and we kind of hit a dead end.
Does anyone have any input on how to import this extension properly?
PS. once we get this answered I'm going to work with the dev to implement a seamless experience for all node users who wish to incorporate babylon.js into their projects!
I spoke with the lead developer deltakosh about this.
To clear a few things up:
This issue is not with npm
This issue is not with node
This issue is with how Babylon is structured
The developers are actively refactoring to support the import behavior desired in the above question.
If anyone is curious here is the link to the open issue on github pertaining to this question.
In the interim to use Babylon while import support for importing packages is being worked on I have done the following:
Use the CDN for all babylon libraries
To get rid of typescript compilation issues declare the following at the top of your .ts file declare let BABYLON: any; This will make babylon with packages useable, however, we will not have any typings benefits in the interim.
Feel free to chime in if you have found a more elegant interim solution!

I am having difficulty getting a new version of a 3rd party SDK to import into Android Studio

I am having difficulty getting a new version of a 3rd party SDK to import into Android Studio.
In the earlier version they released .jar and .so files which I copied into /lib and /jniLibs and then added the lib files into the Android Studio app and everything worked. The app ran, used the libraries and all was good in the world. Recently a new version of this SDK was released but in this new release they have resource files (but they are not compiled into the jar/so files; there is a $Rstring.class files that they say I should import. I've now spent days copying into various locations in the app project with no luck and the missing strings result in crashes when calling their SDK.
OK, I figure I'd try to import their SDK folder (which is how they document to do it if you are using Eclipse). Well, no matter what I've tried and after selecting the folder or SDK's project file I get a dialog asking for the Eclipse workspace and a list of what appears to be source file names. I can't get past this dialog because obviously I don't have their files.
Has anyone run into this and found a solution; perhaps I'm missing something in the process but after spending the better part of 3-4 days trying and searching and trying more things I'm hopeful for help from the community.
OK, I found the answer and it was a combination of issues in how this particular 3rd party distributed the SDK and not fully understanding the menu.
The 3rd party in question packaged the SDK with the output files of the build as well as files that needed to be imported making an import alone to not work.
Combine this with menu confusion: File->Import Module is NOT the same as New->Modules->Import Existing Project only added to the confusion.
The solution ended up being to use the File->Import Module which appears to be a very different operation and once done most of the issues where solved. It solved the main issues I asked above which was missing resourced.
Still missing was the library (.jar) files which had to me copied into the app's lib folder and "added as library" but the .SO files did not need to be copied and in fact doing that resulted in a duplicate files warning.
I'm not sure I can fully explain what happened but what I think happened is that the "module" was where the app read the .so and string resources from but was unable to load the .jar files because (I suspect) these files where not part of the module but rather where outputs of building the source and it was removing the source files which caused the inability of the new->Module->Import to fail.
Hopefully this makes sense or at least give someone an idea of what to look for when/if they run into a similar issue.

Resources