Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 05 19:15

    shadaj on master

    Also update Sonatype plugin ver… (compare)

  • Jan 05 19:03

    shadaj on master

    Also update Sonatype plugin ver… (compare)

  • Jan 05 18:46

    shadaj on master

    Also update Sonatype plugin ver… (compare)

  • Jan 05 18:36

    shadaj on master

    Don't use + in publish.sh since… (compare)

  • Dec 23 2019 01:45

    shadaj on master

    Add Travis CI caching (#47) Se… (compare)

  • Dec 23 2019 01:45
    shadaj closed #47
  • Dec 23 2019 01:44

    shadaj on master

    Add cross-building to Scala 2.1… (compare)

  • Dec 23 2019 01:44
    shadaj closed #46
  • Dec 15 2019 16:41
    MaximeKjaer synchronize #46
  • Dec 15 2019 16:25
    MaximeKjaer opened #47
  • Dec 15 2019 16:14
    MaximeKjaer opened #46
  • Nov 19 2019 00:04
    bfdes commented #37
  • Nov 18 2019 23:33
    shadaj commented #37
  • Nov 17 2019 20:26

    shadaj on new-vs-borrowed-ref

    (compare)

  • Nov 17 2019 20:26

    shadaj on master

    Cleanup CPythonInterpreter to c… (compare)

  • Nov 17 2019 20:26
    shadaj closed #45
  • Nov 17 2019 19:56
    shadaj labeled #45
  • Nov 17 2019 19:56
    shadaj opened #45
  • Nov 17 2019 19:56
    shadaj milestoned #45
  • Nov 17 2019 19:55

    shadaj on new-vs-borrowed-ref

    Cleanup CPythonInterpreter to c… (compare)

any idea how can I fix this ?
Jozsefs-MacBook-Pro:scalapytest joco$ sbt
[info] Loading global plugins from /Users/joco/.sbt/1.0/plugins
[info] Loading project definition from /Users/joco/dev/ml/scalapy/test01/github/scalapytest/project
[info] Loading settings for project root from build.sbt ...
[info] Set current project to ScalaPyTest (in build file:/Users/joco/dev/ml/scalapy/test01/github/scalapytest/)
[info] sbt server started at local:///Users/joco/.sbt/1.0/server/3f6c4d00bf97ae0f90ba/sock
sbt:ScalaPyTest> run
[info] running (fork) example.Hello
[info] code runs
[error] Exception in thread "main" java.lang.Error: java.lang.UnsatisfiedLinkError: jep.MainInterpreter.initializePython([Ljava/lang/String;)V
[error]     at jep.MainInterpreter.initialize(MainInterpreter.java:183)
[error]     at jep.MainInterpreter.getMainInterpreter(MainInterpreter.java:97)
[error]     at jep.Jep.<init>(Jep.java:232)
[error]     at jep.Jep.<init>(Jep.java:228)
[error]     at me.shadaj.scalapy.py.JepInterpreter.<init>(JepInterpreter.scala:9)
[error]     at me.shadaj.scalapy.py.Platform$.newInterpreter(Platform.scala:5)
[error]     at me.shadaj.scalapy.py.package$.interpreter(package.scala:11)
[error]     at me.shadaj.scalapy.py.Writer$$anon$11.write(Writer.scala:75)
[error]     at me.shadaj.scalapy.py.Any$.from(Any.scala:28)
[error]     at example.Hello$.delayedEndpoint$example$Hello$1(Hello.scala:6)
[error]     at example.Hello$delayedInit$body.apply(Hello.scala:3)
[error]     at scala.Function0.apply$mcV$sp(Function0.scala:39)
[error]     at scala.Function0.apply$mcV$sp$(Function0.scala:39)
[error]     at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
[error]     at scala.App.$anonfun$main$1$adapted(App.scala:80)
[error]     at scala.collection.immutable.List.foreach(List.scala:392)
[error]     at scala.App.main(App.scala:80)
[error]     at scala.App.main$(App.scala:78)
[error]     at example.Hello$.main(Hello.scala:3)
[error]     at example.Hello.main(Hello.scala)
[error] Caused by: java.lang.UnsatisfiedLinkError: jep.MainInterpreter.initializePython([Ljava/lang/String;)V
[error]     at jep.MainInterpreter.initializePython(Native Method)
[error]     at jep.MainInterpreter.access$100(MainInterpreter.java:64)
[error]     at jep.MainInterpreter$1.run(MainInterpreter.java:140)
[error] Nonzero exit code returned from runner: 1
[error] (Compile / run) Nonzero exit code returned from runner: 1
[error] Total time: 1 s, completed Dec 24, 2019 11:51:02 PM
sbt:ScalaPyTest>
Eric K Richardson
@ekrich
Seems like something is wrong with the python install or something.
Maxime Kjaer
@MaximeKjaer
@jhegedus42 what version of Jep have you installed? You can try again with pip install jep==3.8.2
Eric K Richardson
@ekrich
I haven't tried honestly, but there is some discussion above that could help.
Shadaj Laddad
@shadaj
looks like a version mismatch as @MaximeKjaer noted, since some shared library is being loaded but there's a JNI definition that's missing
jhegedus42
@jhegedus42
thanks !
nice
this works
with 3.8.2 jep
thanks
image.png
how about jupyter ?
image.png
Maxime Kjaer
@MaximeKjaer
@jhegedus42 This looks like Ammonite doesn't fetch from the right resolver? I can't see anything else than 0.2.0 on Maven https://search.maven.org/artifact/me.shadaj/scalapy_2.12.
Ah, it could just be that you should be loading scalapy-core:0.3.0, which is on Maven https://search.maven.org/artifact/me.shadaj/scalapy-core_2.12
Btw, @shadaj, I think deployments have been broken since this build https://travis-ci.com/shadaj/scalapy/builds/142068062. It complains about:
[error] Multiple repositories are found:
[error] [meshadaj-1361] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1362] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1363] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1364] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1365] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1366] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1367] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1368] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1369] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1370] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1371] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1372] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] [meshadaj-1373] status:open, profile:me.shadaj(efba3c89dc27) description: Implicitly created (auto staging).
[error] Specify one of the repository ids in the command line
[error] java.lang.IllegalStateException: Found multiple staging repositories
[error] Use 'last' for the full log.
Maxime Kjaer
@MaximeKjaer
This means that nothing has been published since 0.3.0+2. I'd like to submit a PR adding cross-building to Scala 2.13 to scalapy-numpy, but this is a blocker for that.
Maxime Kjaer
@MaximeKjaer
I have very little experience or knowledge of how publishing Scala projects works, but from what I can gather it seems (from this issue xerial/sbt-sonatype#78) that updating sbt-sonatype could help
jhegedus42
@jhegedus42
@MaximeKjaer hmmm, thanks, i guess for the time being I will be just playing around in colab... google, that is pretty neat ... and easy ...
Shadaj Laddad
@shadaj
oh thanks @MaximeKjaer for catching that, I'll clear out the Sonatype staging and re-publish for now
Maxime Kjaer
@MaximeKjaer
@shadaj Could you perhaps publish ScalaPy manually for now? I have scalapy-numpy cross building to 2.13 in this commit MaximeKjaer/scalapy-numpy@d8805dc but would need version 0.3.0+13-0c255e53 of ScalaPy on Maven in order to make builds reproducible
Shadaj Laddad
@shadaj
@MaximeKjaer cleared out staging repositories and restarted the build, it should be out soon!
Shadaj Laddad
@shadaj
I think I identified the source of the publish failures, just added a new commit that's publishing now
Shadaj Laddad
@shadaj
0.3.0+15-598682f0 has been released!
Maxime Kjaer
@MaximeKjaer
That's fantastic, thank you so much! I'm submitting a PR to scalapy-numpy now :)
nova
@nova999
Hi, does scalapy work with anaconda environments?
Shadaj Laddad
@shadaj
@nova999 yep, Anaconda correctly overrides the python3-config utility so as long as you use the javaOptions += s"-Djna.library.path=${"python3-config --prefix".!!.trim}/lib" config it should pick up the current environment's Python
nova
@nova999
Thank you :)
nova
@nova999
So I got a simple pyopencl program working in scalapy. With typings it could be a good alternative to the seemingly abandoned ScalaCL.
Jorge
@jvican
nice! consider working on those typings then, i'm sure they'd be well received ;)
nova
@nova999
I did intend to. I was studying the numpy facade. Some things are still not quite clear to me. But I suppose I could lay a groundwork to begin with.
Maxime Kjaer
@MaximeKjaer
Based on previous discussion in this channel, I said I'd ping both @shadaj and @ekrich once I open sourced the shape-safe TensorFlow library for Dotty. So with a little bit of a delay, here's a link! https://github.com/MaximeKjaer/tf-dotty
Maxime Kjaer
@MaximeKjaer
@shadaj I copied the code of scalapy-tensorflow into a scalapy-tensorflow module. This is just the easiest way that I found to augment the existing typings while working on tf-dotty. I would be happy to contribute them back to the main scalapy-tensorflow project, once I've typed a full TF module
Shadaj Laddad
@shadaj
@MaximeKjaer this is very exciting! Took a quick glance over the website just now, looks very nice! Also was cool to see the thought process that went into the implementation