Podling Report Reminder - February 2018
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 February 2018, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, February 07). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://wiki.apache.org/incubator/February2018 Note: This is manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] [Commented] (TOREE-463) Startup performance: initialize ScalaInterpreter earlier and in its own thread
[ https://issues.apache.org/jira/browse/TOREE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16356156#comment-16356156 ] ASF GitHub Bot commented on TOREE-463: -- Github user sanjay-saxena commented on a diff in the pull request: https://github.com/apache/incubator-toree/pull/151#discussion_r166772771 --- Diff: kernel/src/main/scala/org/apache/toree/boot/layer/ComponentInitialization.scala --- @@ -28,6 +28,7 @@ import org.apache.toree.comm.{CommManager, CommRegistrar, CommStorage, KernelCom import org.apache.toree.dependencies.{CoursierDependencyDownloader, Credentials, DependencyDownloader} import org.apache.toree.interpreter._ import org.apache.toree.kernel.api.Kernel +import org.apache.toree.kernel.interpreter.scala.ScalaInterpreter --- End diff -- Based on my limited understanding of the code, picking up a dependency on an implementation such as `ScalaInterpreter` from `scala-interpreter` project in the generic `kernel` project maybe an abstraction violation. It may also lead to circular dependencies. Maybe, you should look at either reusing the existing APIs on the generic trait `Interpreter`. And, if the existing APIs are not sufficient, then maybe add new APIs to the generic trait `Interpreter`. > Startup performance: initialize ScalaInterpreter earlier and in its own thread > -- > > Key: TOREE-463 > URL: https://issues.apache.org/jira/browse/TOREE-463 > Project: TOREE > Issue Type: Bug >Reporter: Brad >Priority: Major > > The Scala Interpreter is the slowest thing to start up, have it start earlier > and run concurrently with the rest of Toree -- This message was sent by Atlassian JIRA (v7.6.3#76005)