[jira] [Created] (EDGENT-315) The d3 images on the streaming-concepts.html page are not appearing
Susan L. Cline created EDGENT-315: - Summary: The d3 images on the streaming-concepts.html page are not appearing Key: EDGENT-315 URL: https://issues.apache.org/jira/browse/EDGENT-315 Project: Edgent Issue Type: Bug Components: Web Site Reporter: Susan L. Cline Priority: Minor When I was reading this page it was referring to colors and streams and I could not see any images. It turns out that this error is being thrown when browsing to the page and looking at a javascript console: Mixed Content: The page at 'https://edgent.apache.org/docs/streaming-concepts.html' was loaded over HTTPS, but requested an insecure script 'http://d3js.org/d3.v3.min.js'. This request has been blocked; the content must be served over HTTPS. This seems to be due to attempting to fetch the d3 library at a non-https url. There is this post about this: https://github.com/jsbin/jsbin/issues/2549 Also, I tried changing the url from 'http://d3js.org/d3.v3.min.js' in my local incubator-edgent-website 'streaming-concepts.html' to 'https://d3js.org/d3.v3.min.js' and it seems to work fine. I.e, the images appear. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-305) Test the Edgent Console
[ https://issues.apache.org/jira/browse/EDGENT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15677876#comment-15677876 ] Susan L. Cline commented on EDGENT-305: --- I added this page to the wiki, under a new 'Testing Components for a Release' section: https://cwiki.apache.org/confluence/display/EDGENT/Testing+the+Console and I logged the JIRA issue EDGENT-314 for the minor issue I found with the view all properties table. https://issues.apache.org/jira/browse/EDGENT-314 > Test the Edgent Console > --- > > Key: EDGENT-305 > URL: https://issues.apache.org/jira/browse/EDGENT-305 > Project: Edgent > Issue Type: Sub-task >Reporter: Dale LaBossiere >Assignee: Susan L. Cline > Fix For: 0.4.0 > > > (manual) Testing of the console seems to warrant a separate item. > Please update the RM Guide with info for what should be tested, on what > platforms, etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EDGENT-314) Table opened by View all oplet properties link in Console does not refresh
Susan L. Cline created EDGENT-314: - Summary: Table opened by View all oplet properties link in Console does not refresh Key: EDGENT-314 URL: https://issues.apache.org/jira/browse/EDGENT-314 Project: Edgent Issue Type: Bug Components: Console Reporter: Susan L. Cline Priority: Minor When testing the console for the 1.0.0 release, I noticed that the table that is opened when the 'View all oplet properties' is clicked does not refresh. That is, even if the 'View by' drop down is set to Tuple count, the tuple count values in the table are not refreshing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-305) Test the Edgent Console
[ https://issues.apache.org/jira/browse/EDGENT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15675211#comment-15675211 ] Susan L. Cline commented on EDGENT-305: --- Okay, should I just outline what I tested here or do you want me to edit the release manager's guide page? If so, put it under 'Testing the Release' - Testing Application Console? Thanks, Susan > Test the Edgent Console > --- > > Key: EDGENT-305 > URL: https://issues.apache.org/jira/browse/EDGENT-305 > Project: Edgent > Issue Type: Sub-task >Reporter: Dale LaBossiere >Assignee: Susan L. Cline > > (manual) Testing of the console seems to warrant a separate item. > Please update the RM Guide with info for what should be tested, on what > platforms, etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (EDGENT-313) Documentation: Application Console page has errors
Susan L. Cline created EDGENT-313: - Summary: Documentation: Application Console page has errors Key: EDGENT-313 URL: https://issues.apache.org/jira/browse/EDGENT-313 Project: Edgent Issue Type: Bug Components: Web Site Affects Versions: 0.4.0 Reporter: Susan L. Cline Assignee: Susan L. Cline Priority: Minor Fix For: 0.4.0 In testing the console to get ready for the 1.0.0 release I'm looking at this page: https://edgent.apache.org/docs/console.html and noticing that there are many references to 'ant'. I'll update the page to use gradle instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-305) Test the Edgent Console
[ https://issues.apache.org/jira/browse/EDGENT-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15675053#comment-15675053 ] Susan L. Cline commented on EDGENT-305: --- To test the console first I will go through the instructions on our web site: https://edgent.apache.org/docs/console.html If documentation issues are found, I will open pull requests for these. I already see that the instructions outline 'ant'. Additionally I will outline what I tested in the release manager's guide here: https://cwiki.apache.org/confluence/display/EDGENT/Release+Manager's+Guide > Test the Edgent Console > --- > > Key: EDGENT-305 > URL: https://issues.apache.org/jira/browse/EDGENT-305 > Project: Edgent > Issue Type: Sub-task >Reporter: Dale LaBossiere >Assignee: Susan L. Cline > > (manual) Testing of the console seems to warrant a separate item. > Please update the RM Guide with info for what should be tested, on what > platforms, etc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-210) Submit an app, closing an app and then attempting to resubmit an app "kills" the parent app
[ https://issues.apache.org/jira/browse/EDGENT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566184#comment-15566184 ] Susan L. Cline commented on EDGENT-210: --- This is fixed. I verified it today. > Submit an app, closing an app and then attempting to resubmit an app "kills" > the parent app > --- > > Key: EDGENT-210 > URL: https://issues.apache.org/jira/browse/EDGENT-210 > Project: Edgent > Issue Type: Bug > Components: Runtime >Reporter: Susan L. Cline >Assignee: Daniel John Debrunner >Priority: Critical > > I have a quarks application that creates an IotProvider and registers two > applications. One is called piCpuSensor. > Once the main program (the one with IotProvider) is started and registers the > two applications I send a device command to the piCpuSensor. > At that point the piCpuSensor starts spitting out temperature readings every > second. > Now I send a "CLOSE" command to piCpuSensor. At this point the temperature > readings stop. > Now, I want to restart my piCpuSensor application. I send a submit command > again. At that point an error is thrown and my main program is no longer > functional. (i.e ,it can not receive or send any info) > Here is the stack trace: > Jun 22, 2016 1:12:17 PM quarks.runtime.etiao.ThreadFactoryTracker > trackedThreadUncaughtException > SEVERE: Uncaught exception in thread > pool-2-thread-4-quarksIotCommandsToControl > java.lang.RuntimeException: java.lang.reflect.InvocationTargetException > at > quarks.providers.iot.IotProvider.lambda$null$6cfee445$1(IotProvider.java:239) > at quarks.providers.iot.IotProvider$$Lambda$27/12209492.accept(Unknown > Source) > at > quarks.function.Functions$ThreadSafeConsumer.accept(Functions.java:204) > at > quarks.runtime.etiao.SettableForwarder.accept(SettableForwarder.java:54) > at quarks.oplet.core.Pipe.submit(Pipe.java:65) > at quarks.oplet.functional.Filter.accept(Filter.java:37) > at > quarks.runtime.etiao.SettableForwarder.accept(SettableForwarder.java:54) > at quarks.oplet.core.Pipe.submit(Pipe.java:65) > at quarks.oplet.plumbing.Isolate.run(Isolate.java:86) > at quarks.oplet.plumbing.Isolate.lambda$initialize$3(Isolate.java:64) > at quarks.oplet.plumbing.Isolate$$Lambda$20/10725227.run(Unknown Source) > at > quarks.runtime.etiao.ThreadFactoryTracker$2.run(ThreadFactoryTracker.java:88) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at > quarks.runtime.jsoncontrol.JsonControlService.executeMethod(JsonControlService.java:241) > at > quarks.runtime.jsoncontrol.JsonControlService.controlOperation(JsonControlService.java:180) > at > quarks.runtime.jsoncontrol.JsonControlService.controlRequest(JsonControlService.java:101) > at > quarks.providers.iot.IotProvider.lambda$null$6cfee445$1(IotProvider.java:237) > ... 12 more > Caused by: java.lang.IllegalStateException > at > quarks.runtime.jsoncontrol.JsonControlService.registerControl(JsonControlService.java:123) > at quarks.runtime.etiao.EtiaoJob.(EtiaoJob.java:71) > at quarks.runtime.etiao.Executable.createJob(Executable.java:271) > at > quarks.providers.direct.DirectTopology.executeCallable(DirectTopology.java:104) > at quarks.providers.direct.DirectProvider.submit(DirectProvider.java:87) > at quarks.providers.direct.DirectProvider.submit(DirectProvider.java:52) > at quarks.providers.iot.IotProvider.submit(IotProvider.java:188) > at quarks.providers.iot.IotProvider.submit(IotProvider.java:81) > at > quarks.runtime.appservice.AppServiceControl.submit(AppServiceControl.java:66) > ... 20 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15563543#comment-15563543
]
Susan L. Cline commented on EDGENT-262:
---
[~dlaboss] - can we mark this resolved?
Thanks,
Susan
> origin and disposition of console/servlets/webapp_content/js/ext
>
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
> Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository
> (EDGENT-261, EDGENT-139) I encountered
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as
> org.webjars:jquery-ui:1.11.4 (@
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such
> luck.
> Ultimately, will we be able to remove those files from the repository and
> download them from a maven repository to build Edgent and include in a
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553635#comment-15553635
]
Susan L. Cline commented on EDGENT-262:
---
I looked around a bit more about that jar being pointed to in a script and
talked to a colleague at work and I don't think it is doable.
For where I got d3.min.js, it is available here now, but it no longer seems to
have a BSD license.
https://github.com/d3/d3/releases/tag/v3.5.9
When I downloaded it previously they were BSD licenses.
See this thread:
https://groups.google.com/forum/#!topic/d3-js/MVZ3ft0UvSs
Here is the sankey license, which also was changed:
https://github.com/d3/d3-sankey/blob/master/LICENSE
With regard to d3.legend.js, I got it from here:
https://github.com/jieter/d3-legend/blob/master/d3.legend.js
and inside d3.legend.js is this text:
// d3.legend.js
// (C) 2012 ziggy.jonsson@gmail.com
// MIT licence
wrt stuff I have changed, yes, it kind of seems like we are stuck in that
regard. Sorry if this complicates things.
> origin and disposition of console/servlets/webapp_content/js/ext
>
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
> Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository
> (EDGENT-261, EDGENT-139) I encountered
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as
> org.webjars:jquery-ui:1.11.4 (@
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such
> luck.
> Ultimately, will we be able to remove those files from the repository and
> download them from a maven repository to build Edgent and include in a
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15553063#comment-15553063
]
Susan L. Cline commented on EDGENT-262:
---
I have never tried that - referencing js files that are contained in a jar
file. I got one hit on it here:
http://stackoverflow.com/questions/38153716/can-we-refer-to-a-javascript-inside-the-jar-file-of-a-maven-dependency
but it sounds like you need to use maven? I'm not sure.
WRT the other js files here is where they came :
https://github.com/mbostock/d3 - d3.min.js
The d3.BSD.LICENSE is in ext.
https://github.com/d3/d3-plugins/tree/master/sankey - I modified sankey.ds and
renamed it sankey_edgent.js the license file is in that ext directory.
https://github.com/jieter/d3-legend (Inside the d3.legend.js file is this note:
// d3.legend.js
// (C) 2012 ziggy.jonsson@gmail.com
// MIT licence
License: ps://github.com/mbostock/d3/blob/master/LICENSE)
I also slightly modified d3.legend.js to fit our needs.
> origin and disposition of console/servlets/webapp_content/js/ext
>
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
> Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository
> (EDGENT-261, EDGENT-139) I encountered
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as
> org.webjars:jquery-ui:1.11.4 (@
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such
> luck.
> Ultimately, will we be able to remove those files from the repository and
> download them from a maven repository to build Edgent and include in a
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552629#comment-15552629
]
Susan L. Cline commented on EDGENT-262:
---
Here are the files I need/took from the jquery-ui.jar file:
LICENSE.txt jquery-ui.structure.min.css
ui-icons_44_256x240.png ui-icons_cc_256x240.png
jquery-ui.jsjquery-ui.theme.min.css
ui-icons_55_256x240.png ui-icons_ff_256x240.png
jquery-ui.min.css
ui-icons_777620_256x240.png
jquery-ui.min.js
ui-icons_77_256x240.png
Here are the two files i got from the jquery.jar file:
jquery.js
jquery.min.js
I only modified one file actually, to
console/servlets/webapp_content/html/index.html.
Note that I created a new directory structure and shoved jquery.js under
jquery-ui-1.12.1 .. It does not matter to me if you prefer to have a separate
jquery directory from the jquery-ui-1.12.1:
incubator-edgent/console/servlets/webapp_content/js/ext/jquery-ui-1.12.1
Susans-MBP-795:html susancline$ git diff index.html
diff --git a/console/servlets/webapp_content/html/index.html
b/console/servlets/webapp_content/html/index.html
index f310059..774e0be 100644
--- a/console/servlets/webapp_content/html/index.html
+++ b/console/servlets/webapp_content/html/index.html
@@ -4,9 +4,9 @@
Apache Edgent Console
-
-
-
+
+
+
@@ -98,8 +98,8 @@
-
-
+
+
Another thing to note is that included in the jquery-ui.jar file is a
LICENSE.txt, in the jquery.jar file there is no LICENSE. Also, the link here
to the license is broken:
https://mvnrepository.com/artifact/org.webjars/jquery/3.1.1
license url: https://github.com/jquery/jquery/blob/master/MIT-LICENSE.txt
Thanks,
Susan
> origin and disposition of console/servlets/webapp_content/js/ext
>
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
> Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository
> (EDGENT-261, EDGENT-139) I encountered
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as
> org.webjars:jquery-ui:1.11.4 (@
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such
> luck.
> Ultimately, will we be able to remove those files from the repository and
> download them from a maven repository to build Edgent and include in a
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (EDGENT-262) origin and disposition of console/servlets/webapp_content/js/ext
[
https://issues.apache.org/jira/browse/EDGENT-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15552421#comment-15552421
]
Susan L. Cline commented on EDGENT-262:
---
[~dlaboss] - I downloaded the content of two jar files at the URL you
suggested: https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4 for
the jquery-ui requirements, and then I went here:
https://mvnrepository.com/artifact/org.webjars/jquery/3.1.1 for the main
jquery.js file.
I put them under
ncubator-edgent/console/servlets/webapp_content/js/ext/jquery-ui-1.12.1 and
built using gradle, then modified a couple of files under the console directory
to point to the new files and everything worked fine.
Please let me know how to proceed to replace this stuff. Or if you need
additional info! Thanks
> origin and disposition of console/servlets/webapp_content/js/ext
>
>
> Key: EDGENT-262
> URL: https://issues.apache.org/jira/browse/EDGENT-262
> Project: Edgent
> Issue Type: Task
>Reporter: Dale LaBossiere
>
> Working towards removal of external dependencies from the Edgent repository
> (EDGENT-261, EDGENT-139) I encountered
> console/servlets/webapp_content/js/ext/jquery-ui-1.11.4.custom.
> [~slc] what's the origin of these files?
> Looking at the name I had hoped it was the same as
> org.webjars:jquery-ui:1.11.4 (@
> https://mvnrepository.com/artifact/org.webjars/jquery-ui/1.11.4) but no such
> luck.
> Ultimately, will we be able to remove those files from the repository and
> download them from a maven repository to build Edgent and include in a
> generated console.war and binary release?
> If not, that seems to imply needing to augment various files to capture the
> included content's license/notice info:
>console.war/{LICENSE,NOTICE}
>edgent-repository/LICENSE,NOTICE
>binary-release-{license,notice}
> looking for some guidance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (EDGENT-194) Console: the "no metric" stream width scaling needs tweaking
[ https://issues.apache.org/jira/browse/EDGENT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan L. Cline updated EDGENT-194: -- Component/s: Console > Console: the "no metric" stream width scaling needs tweaking > > > Key: EDGENT-194 > URL: https://issues.apache.org/jira/browse/EDGENT-194 > Project: Edgent > Issue Type: Bug > Components: Console >Reporter: Dale LaBossiere >Priority: Minor > Labels: newbie > > The scaling for a stream lacking metrics needs tweaking (e.g., the stream > between the filter and peek: `... -> filter -> peek` ; no sink). > The width of such a stream can end up being much larger than streams that > have a larger actual flow. A good heuristic for this case is: #output > tuples == #input tuples. > This can easily be demonstrated by the SensorAnalyticsApplication sample, > where there are widely disparate tuple flow rates -- e.g., 1k/sec and 1/sec. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (EDGENT-196) Console: FanOut is scaled too large
[ https://issues.apache.org/jira/browse/EDGENT-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan L. Cline updated EDGENT-196: -- Component/s: Console > Console: FanOut is scaled too large > --- > > Key: EDGENT-196 > URL: https://issues.apache.org/jira/browse/EDGENT-196 > Project: Edgent > Issue Type: Improvement > Components: Console >Reporter: Dale LaBossiere > > The size scaling for a FanOut oplet seems too large relative to its > significance. That can be distracting and misleading relative to the rest of > the oplets in the graph. Note, a Splitter handing the same number of input > tuples is scaled smaller than a FanOut. Any oplet feeding a FanOut will be > scaled smaller than the FanOut. > I think it also makes sense to present FanOut, an implementation injected > "plumbing" oplet, differently than an application's "functional" oplets. > Maybe FanOut should always be colored light grey for starters? Maybe > hexagonal, or rectangular like instrumentation injected oplets, instead of a > circle? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
