[jira] [Reopened] (FLAGON-322) minimatch deprecation: ReDOS vulnerability
[ https://issues.apache.org/jira/browse/FLAGON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-322: - > minimatch deprecation: ReDOS vulnerability > -- > > Key: FLAGON-322 > URL: https://issues.apache.org/jira/browse/FLAGON-322 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0, UserALE.js 1.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 1.0.0, UserALE.js 1.1.0 > > Attachments: minimatch 2.0.7 vulnerability > > > minimatch 2.0.7 has a ReDOS vulnerability. minimatch must be upgraded to > ^3.0.2 to remove vulnerability. However, minimatch 2.0.7 is a dependency of > vinyl-fs, which is a dependency of gulp 3.9.1. Two potential options: > # The right way: update to gulp 4.0.0, which has breaking changes. > # The wonky way: coerce global environment to use minimatch 3.0.2 using "npm > install -g minimatch@3.0.2". gulp 3.9.1 will still force installation of > vinyl-fs, which will force installation of minimatch 2.0.7. However, coercing > npm to install 3.0.2 should remove vulnerability. This solution is purely a > downstream hack. see this thread: > [https://stackoverflow.com/questions/38046392/npm-warn-deprecated-minimatch2-0-10-please-update-to-minimatch-3-0-2-or-higher/38077214] > Will test #2 as an intermediate solution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FLAGON-271) Investigate workflow for adding Chrome plugin to Chrome Store
[ https://issues.apache.org/jira/browse/FLAGON-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-271: - > Investigate workflow for adding Chrome plugin to Chrome Store > - > > Key: FLAGON-271 > URL: https://issues.apache.org/jira/browse/FLAGON-271 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 1.1.0 > > > Chrome has changed the way it allows temp plugins to work. As a result ours > is no longer persistent. May need to go through chrome store. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FLAGON-221) Elasticsearch 5.x does not support microsecond precision
[ https://issues.apache.org/jira/browse/FLAGON-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-221: - > Elasticsearch 5.x does not support microsecond precision > > > Key: FLAGON-221 > URL: https://issues.apache.org/jira/browse/FLAGON-221 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0 >Reporter: Michelle Beard >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > In order to do accurate sequence analysis, it is imperative that the > clientTime generated by userALE is set to microseconds. Unfortunately, > Elasticsearch only supports up to milliseconds. This impacts how sorting is > done at the clientTime level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FLAGON-192) Record Interval Events
[ https://issues.apache.org/jira/browse/FLAGON-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-192: - > Record Interval Events > -- > > Key: FLAGON-192 > URL: https://issues.apache.org/jira/browse/FLAGON-192 > Project: Flagon > Issue Type: New Feature > Components: UserALE.js >Reporter: Michelle Beard >Assignee: Michelle Beard >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 4h > Remaining Estimate: 4h > > Detect repeated userale events by keeping track of an interval: > An interval event describes a sequence of identical userale events > (mouseovers, drags, etc). It must record the start of the event and the end > of the event. In the case that a userale event does not update/timeouts, the > interval is closed by the library and emitted to the logging server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FLAGON-99) Add custom log API method
[ https://issues.apache.org/jira/browse/FLAGON-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-99: > Add custom log API method > - > > Key: FLAGON-99 > URL: https://issues.apache.org/jira/browse/FLAGON-99 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Reporter: Rob Foley >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > Expose a method on the API to allow users to add custom logs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (FLAGON-239) Submit Firefox Extension to Firefox Verification
[ https://issues.apache.org/jira/browse/FLAGON-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reopened FLAGON-239: - > Submit Firefox Extension to Firefox Verification > > > Key: FLAGON-239 > URL: https://issues.apache.org/jira/browse/FLAGON-239 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 1.1.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 1.1.0 > > Time Spent: 3h > Remaining Estimate: 0h > > Submit to firefox > Definition of Done = Receipt of Submission -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-284) "userid" field seems to impact ability to correctly map 'details' field for tab meta data.
[ https://issues.apache.org/jira/browse/FLAGON-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-284: Affects Version/s: (was: UserALE.js 1.0.0) > "userid" field seems to impact ability to correctly map 'details' field for > tab meta data. > -- > > Key: FLAGON-284 > URL: https://issues.apache.org/jira/browse/FLAGON-284 > Project: Flagon > Issue Type: Sub-task > Components: UserALE.js > Environment: CentOS, JavaScript, Logstash, Elastic >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Minor > Fix For: UserALE.js 1.1.0 > > Original Estimate: 2h > Remaining Estimate: 2h > > The problem is: the ‘details’ field in tab transitions doesn’t map uniformly > when different userids are passed to the logs via the plugin interface > (firefox). Specifically, details appears as a searchable field with no meta > data, where we would expect the various subtitles to map as details.[]. > It affects very simple visualizations in Kibana for tracking page visits > (details.title.keyword) by userid. pageUrl does map (though this is not part > of 'details'). details.title however is more pragmatic for tabulating visits > to domains without munging through pageUrls. > Here are the details: > 1. When userid is left at default (‘nobody’), details.title.keyword maps > correctly. details.title appears as a searchable field and > details.title.keyword aggregates correctly in visualizations in kibana. > 2. When userid is changed to any other strings, ‘details’ appears in logs as > an empty field with a warning “(paraphrase) data is available for search but > will not populate, consider refreshing Index mappings” in kibana’s discover > tab. > 3. If userid is changed back to "nobody" from some other value, 'details' > appears to map along its subfields correctly (esp details.title) > Testing details: > # Tested on 3 different clients: > ## Confirmed that when userid was set to nobody, logs from each different > client (hostname) correctly mapped details.title. > ## Confirmed that when userid was set to another value, logs with > userid==[string] did not have valid data that could be read in "explore" tab > of kibana, and did not aggregate through table visualization. > NOTE: Untested in script tag method -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-225) UserALE not stringifying javascript objects correctly
[
https://issues.apache.org/jira/browse/FLAGON-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated FLAGON-225:
Component/s: (was: UserALE.js)
> UserALE not stringifying javascript objects correctly
> -
>
> Key: FLAGON-225
> URL: https://issues.apache.org/jira/browse/FLAGON-225
> Project: Flagon
> Issue Type: Bug
>Reporter: Michelle Beard
>Assignee: Rob Foley
>Priority: Major
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> While analyzing some logs stored in Elasticsearch, I noticed some of the
> element targets are not being probably stringified in UserALE. Worth
> investigating.
> {code:javascript}
> {
> "pathLength": 18,
> "sequenceID": "rect.[object SVGAnimatedString]->Window",
> "source": 2,
> "sourceName": "rect.[object SVGAnimatedString]",
> "target": 0,
> "targetChange": 1,
> "targetName": "Window",
> "type": "mouseover",
> "typeChange": 1,
> "value": 1
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (FLAGON-294) Branch Management
[ https://issues.apache.org/jira/browse/FLAGON-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-294. --- > Branch Management > - > > Key: FLAGON-294 > URL: https://issues.apache.org/jira/browse/FLAGON-294 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 1.1.0 > Environment: GH >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 1m > Remaining Estimate: 1m > > Branches are a mess. [~rf] and [~poor...@me.com] discussed this issue today. > Please ask [~mbeard] for consensus before we delete. Comparing branches, the > following can be deleted: > 214 (redundant with 192) > 175 (redundant with 192) > v0.2 (redundant and behind MASTER) > gh-pages (frmr defunct website, replaced by Apache.org site.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-284) "userid" field seems to impact ability to correctly map 'details' field for tab meta data.
[ https://issues.apache.org/jira/browse/FLAGON-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-284: Fix Version/s: (was: UserALE.js 1.1.0) > "userid" field seems to impact ability to correctly map 'details' field for > tab meta data. > -- > > Key: FLAGON-284 > URL: https://issues.apache.org/jira/browse/FLAGON-284 > Project: Flagon > Issue Type: Sub-task > Components: UserALE.js > Environment: CentOS, JavaScript, Logstash, Elastic >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > The problem is: the ‘details’ field in tab transitions doesn’t map uniformly > when different userids are passed to the logs via the plugin interface > (firefox). Specifically, details appears as a searchable field with no meta > data, where we would expect the various subtitles to map as details.[]. > It affects very simple visualizations in Kibana for tracking page visits > (details.title.keyword) by userid. pageUrl does map (though this is not part > of 'details'). details.title however is more pragmatic for tabulating visits > to domains without munging through pageUrls. > Here are the details: > 1. When userid is left at default (‘nobody’), details.title.keyword maps > correctly. details.title appears as a searchable field and > details.title.keyword aggregates correctly in visualizations in kibana. > 2. When userid is changed to any other strings, ‘details’ appears in logs as > an empty field with a warning “(paraphrase) data is available for search but > will not populate, consider refreshing Index mappings” in kibana’s discover > tab. > 3. If userid is changed back to "nobody" from some other value, 'details' > appears to map along its subfields correctly (esp details.title) > Testing details: > # Tested on 3 different clients: > ## Confirmed that when userid was set to nobody, logs from each different > client (hostname) correctly mapped details.title. > ## Confirmed that when userid was set to another value, logs with > userid==[string] did not have valid data that could be read in "explore" tab > of kibana, and did not aggregate through table visualization. > NOTE: Untested in script tag method -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-311) [POST RENAME] Remove SensSoft References from JIRA INFRA
[ https://issues.apache.org/jira/browse/FLAGON-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-311. --- Resolution: Done Assignee: Joshua Poore > [POST RENAME] Remove SensSoft References from JIRA INFRA > > > Key: FLAGON-311 > URL: https://issues.apache.org/jira/browse/FLAGON-311 > Project: Flagon > Issue Type: Task >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-386) Update Readmes to include methods for including useralejs in project as NPM package
Joshua Poore created FLAGON-386: --- Summary: Update Readmes to include methods for including useralejs in project as NPM package Key: FLAGON-386 URL: https://issues.apache.org/jira/browse/FLAGON-386 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-392) Clean up for Merge with master
[ https://issues.apache.org/jira/browse/FLAGON-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-392. - Resolution: Fixed > Clean up for Merge with master > -- > > Key: FLAGON-392 > URL: https://issues.apache.org/jira/browse/FLAGON-392 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Fix the following content conflicts prior to 2.0.0 release: > > You have unmerged paths. > (fix conflicts and run "git commit") > (use "git merge --abort" to abort the merge) > > Changes to be committed: > > modified: .babelrc > modified: DISCLAIMER > modified: NOTICE > new file: build/UserAleWebExtension/background.js > new file: build/UserAleWebExtension/content.js > new file: build/UserAleWebExtension/icons/border-48.png > new file: build/UserAleWebExtension/manifest.json > new file: build/UserAleWebExtension/options.js > new file: build/UserAleWebExtension/optionsPage.html > deleted: build/userale-1.0.0.min.js > renamed: build/userale-1.0.0.js -> build/userale-2.0.0.js > new file: build/userale-2.0.0.min.js > modified: example/README.md > new file: src/UserALEWebExtension/README.md > new file: src/UserALEWebExtension/background.js > new file: src/UserALEWebExtension/content.js > new file: src/UserALEWebExtension/globals.js > new file: src/UserALEWebExtension/icons/border-48.png > new file: src/UserALEWebExtension/manifest.json > new file: src/UserALEWebExtension/messageTypes.js > new file: src/UserALEWebExtension/options.js > new file: src/UserALEWebExtension/optionsPage.html > new file: src/UserALEWebExtension/public/index.html > modified: src/attachHandlers.js > modified: src/getInitialSettings.js > modified: src/main.js > modified: src/packageLogs.js > modified: src/sendLogs.js > modified: test/attachHandlers_spec.js > modified: test/packageLogs_spec.js > modified: test/sendLogs_spec.js > > Unmerged paths: > (use "git add ..." to mark resolution) > > both modified: LICENSE > both modified: README.md > both modified: doap-userale.js.rdf > both modified: example/index.html > both modified: gulpfile.js > both added: package-lock.json > both modified: package.json > both modified: test/main_spec.js > > MacBook-Pro:incubator-flagon-useralejs jpoore$ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-407) Jenkins Builds Failing
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-407: Description: Local builds, unit tests, and functional tests check out. I've tested locally on node 11.10.0 and 12.2.0. Jenkins tests are failing on both following inclusion of rollup operations in Gulp pipeline for WebExtension. Here is current: * *Tests:* npm * *Node:*node-v12.2.0-linux-x64 relevant? [https://github.com/tj/n/issues/565] Error: [19:00:37] Starting 'test'... [19:00:37] Starting 'build'... [19:00:37] Starting 'rollup'... [19:00:38] Finished 'rollup' after 493 ms [19:00:38] Starting 'build-web-ext'... [19:00:38] Starting 'rollup-web-ext-content'... [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms [19:00:38] Error: Could not resolve entry module (src/UserAleWebExtension/content.js). at error (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) at pluginDriver.hookFirst.then.resolveIdResult (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) at process._tickDomainCallback (internal/process/next_tick.js:135:7) [19:00:38] 'build-web-ext' errored after 18 ms [19:00:38] 'build' errored after 513 ms [19:00:38] 'test' errored after 516 ms npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! useralejs@2.0.0 test: `gulp test` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the useralejs@2.0.0 test script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log was: Local builds, unit tests, and functional tests check out. I've tested locally on node 11.10.0 and 12.2.0. Jenkins tests are failing on both as well. Here is current: * *Tests:* npm * *Node:*node-v12.2.0-linux-x64 relevant? [https://github.com/tj/n/issues/565] > Jenkins Builds Failing > -- > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-394) Latency Between Funnel Elements (Kibana)
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864398#comment-16864398 ] Joshua Poore commented on FLAGON-394: - Not at all. Completely different class of analytics: [https://chartio.com/learn/product-analytics/what-is-a-funnel-analysis/]. Way simple, which is why I was able to show one off in Kibana that does the most basic aggregation and math. > Latency Between Funnel Elements (Kibana) > > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-378) Create Modifying UserALE.js src docs for site
[ https://issues.apache.org/jira/browse/FLAGON-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-378. - Resolution: Fixed > Create Modifying UserALE.js src docs for site > - > > Key: FLAGON-378 > URL: https://issues.apache.org/jira/browse/FLAGON-378 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Users should have some guidance for how to modify userale.js at source prior > to builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-407) Jenkins Builds Failing
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864389#comment-16864389 ] Joshua Poore commented on FLAGON-407: - Any one have bandwidth to test master on an Ubuntu box? Would be helpful if we could replicate. Any other idea welcome. > Jenkins Builds Failing > -- > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-407) Jenkins Builds Failing
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864387#comment-16864387 ] Joshua Poore commented on FLAGON-407: - Often refers to version issue: code ELIFECYCLE npm ERR! errno 1 Also fsevents didn't load: but fsevents aides in helping on Darwin. > Jenkins Builds Failing > -- > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-408) Update webextension files for Userale version number
[ https://issues.apache.org/jira/browse/FLAGON-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-408. - Resolution: Fixed > Update webextension files for Userale version number > > > Key: FLAGON-408 > URL: https://issues.apache.org/jira/browse/FLAGON-408 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update webextension files for Userale version number -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-347) Update Docker Build for Flagon Tags
[ https://issues.apache.org/jira/browse/FLAGON-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-347: Priority: Critical (was: Blocker) > Update Docker Build for Flagon Tags > --- > > Key: FLAGON-347 > URL: https://issues.apache.org/jira/browse/FLAGON-347 > Project: Flagon > Issue Type: Task > Components: builds >Affects Versions: Flagon 1.0 > Environment: Docker >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: Flagon 1.0 > > > All our various containers are cross-referenced with the SensSoft namesake. > Replace with "Flagon". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-408) Update webextension files for Userale version number
Joshua Poore created FLAGON-408: --- Summary: Update webextension files for Userale version number Key: FLAGON-408 URL: https://issues.apache.org/jira/browse/FLAGON-408 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update webextension files for Userale version number -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-407) Jenkins Builds Failing
Joshua Poore created FLAGON-407: --- Summary: Jenkins Builds Failing Key: FLAGON-407 URL: https://issues.apache.org/jira/browse/FLAGON-407 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Local builds, unit tests, and functional tests check out. I've tested locally on node 11.10.0 and 12.2.0. Jenkins tests are failing on both as well. Here is current: * *Tests:* npm * *Node:*node-v12.2.0-linux-x64 relevant? [https://github.com/tj/n/issues/565] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-404) Update Readme.md to reflect version 2.0.0
[ https://issues.apache.org/jira/browse/FLAGON-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-404. - Resolution: Fixed > Update Readme.md to reflect version 2.0.0 > - > > Key: FLAGON-404 > URL: https://issues.apache.org/jira/browse/FLAGON-404 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update Readme.md to reflect version 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-405) Add new filter examples to Readme.md
[ https://issues.apache.org/jira/browse/FLAGON-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-405. - Resolution: Fixed > Add new filter examples to Readme.md > > > Key: FLAGON-405 > URL: https://issues.apache.org/jira/browse/FLAGON-405 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Add new filter examples to Readme.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-407) Jenkins Builds Failing
[
https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864385#comment-16864385
]
Joshua Poore commented on FLAGON-407:
-
have udpated rollup and plugins and have made relevant updates to syntax in
gulp. Same effect. Local testing works, but builds/tests fail on Jenkins ubuntu.
This is operation things are barfing on:
// Build the module with Rollup
gulp.task('rollup-web-ext-content', function() {
return rollup({
input : 'src/' + userAleWebExtDirName + '/content.js',
plugins : [
json()
]
})
.then(function(bundle) {
return bundle.write({ #is output missing here?)
file : 'build/' + userAleWebExtDirName + '/content.js',
name : 'user-ale-ext-content',
format : 'esm'
});
});
});
> Jenkins Builds Failing
> --
>
> Key: FLAGON-407
> URL: https://issues.apache.org/jira/browse/FLAGON-407
> Project: Flagon
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 2.0.0
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Blocker
> Fix For: UserALE.js 2.0.0
>
>
> Local builds, unit tests, and functional tests check out. I've tested locally
> on node 11.10.0 and 12.2.0.
> Jenkins tests are failing on both following inclusion of rollup operations in
> Gulp pipeline for WebExtension. Here is current:
> * *Tests:* npm
> * *Node:*node-v12.2.0-linux-x64
> relevant?
> [https://github.com/tj/n/issues/565]
>
> Error:
>
> [19:00:37] Starting 'test'...
> [19:00:37] Starting 'build'...
> [19:00:37] Starting 'rollup'...
> [19:00:38] Finished 'rollup' after 493 ms
> [19:00:38] Starting 'build-web-ext'...
> [19:00:38] Starting 'rollup-web-ext-content'...
> [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms
> [19:00:38] Error: Could not resolve entry module
> (src/UserAleWebExtension/content.js).
> at error
> (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30)
> at pluginDriver.hookFirst.then.resolveIdResult
> (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20)
> at process._tickDomainCallback (internal/process/next_tick.js:135:7)
> [19:00:38] 'build-web-ext' errored after 18 ms
> [19:00:38] 'build' errored after 513 ms
> [19:00:38] 'test' errored after 516 ms
> npm ERR! code ELIFECYCLE
> npm ERR! errno 1
> npm ERR! useralejs@2.0.0 test: `gulp test`
> npm ERR! Exit status 1
> npm ERR!
> npm ERR! Failed at the useralejs@2.0.0 test script.
> npm ERR! This is probably not a problem with npm. There is likely additional
> logging output above.
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FLAGON-407) Jenkins Builds Failing at Master
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864586#comment-16864586 ] Joshua Poore commented on FLAGON-407: - Lots of folks have this issue. To resolve this I have tried adding: # rollup-plugin-node-resolve # rollup-plugin-commonjs # updating rollup and rollup-plugin-js, including updating syntax for rollup ^1.0.0 I'm neither able to fix the build on Jenkins with these actions, nor am I able to replicate the error on my Mac. I've tested on node v 10, 11, 12, clearing package-lock, builds, node_modules, and clearing npm cache. Also, running nvm as a node manager, so pretty sure I don't have globals that are overridding behavior of locals. I've tried running 10, 11, 12 on Jenkins and no luck on the build. The only difference I can think of is that I'm not running Ubuntu. I'll try testing down to version 8 on Jenkins, but I'm thrashing at this point. Any ideas are welcome. > Jenkins Builds Failing at Master > > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-407) Jenkins Builds Failing at Master
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-407: Summary: Jenkins Builds Failing at Master (was: Jenkins Builds Failing) > Jenkins Builds Failing at Master > > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (FLAGON-407) Jenkins Builds Failing at Master
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-407: Comment: was deleted (was: Often refers to version issue: code ELIFECYCLE npm ERR! errno 1 Also fsevents didn't load: but fsevents aides in helping on Darwin.) > Jenkins Builds Failing at Master > > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FLAGON-407) Jenkins Builds Failing at Master
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864586#comment-16864586 ] Joshua Poore edited comment on FLAGON-407 at 6/15/19 3:27 AM: -- Lots of folks have this issue. To resolve this I have tried adding: # rollup-plugin-node-resolve [https://www.npmjs.com/package/rollup-plugin-node-resolve] # rollup-plugin-commonjs [https://www.npmjs.com/package/rollup-plugin-commonjs] # updating rollup and rollup-plugin-json, including updating syntax for rollup ^1.0.0 [https://devhints.io/rollup] I'm neither able to fix the build on Jenkins with these actions, nor am I able to replicate the error on my Mac. I've tested on node v 10, 11, 12, clearing package-lock, builds, node_modules, and clearing npm cache. Also, running nvm as a node manager, so pretty sure I don't have globals that are overridding behavior of locals. I've tried running 10, 11, 12 on Jenkins and no luck on the build. The only difference I can think of is that I'm not running Ubuntu. I'll try testing down to version 8 on Jenkins, but I'm thrashing at this point. Any ideas are welcome. was (Author: poor...@me.com): Lots of folks have this issue. To resolve this I have tried adding: # rollup-plugin-node-resolve # rollup-plugin-commonjs # updating rollup and rollup-plugin-js, including updating syntax for rollup ^1.0.0 I'm neither able to fix the build on Jenkins with these actions, nor am I able to replicate the error on my Mac. I've tested on node v 10, 11, 12, clearing package-lock, builds, node_modules, and clearing npm cache. Also, running nvm as a node manager, so pretty sure I don't have globals that are overridding behavior of locals. I've tried running 10, 11, 12 on Jenkins and no luck on the build. The only difference I can think of is that I'm not running Ubuntu. I'll try testing down to version 8 on Jenkins, but I'm thrashing at this point. Any ideas are welcome. > Jenkins Builds Failing at Master > > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-296) UserALE should be able to detect if there is Restricted Content
[ https://issues.apache.org/jira/browse/FLAGON-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860496#comment-16860496 ] Joshua Poore commented on FLAGON-296: - I'm not 100% sure about this one either... note that this is an old ticket. The reason why it appeared as new is that I moved it back to a future release. > UserALE should be able to detect if there is Restricted Content > --- > > Key: FLAGON-296 > URL: https://issues.apache.org/jira/browse/FLAGON-296 > Project: Flagon > Issue Type: New Feature > Components: UserALE.js >Reporter: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.4.0 > > > For both security purposes and forensic purposes it would be useful to note > if there is restricted content on the page. > > Restricted Content = Anything behind a password > > Helps with filtering, prevention of content extraction, and logging -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency Between Funnel Elements (Kibana)
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Summary: Latency Between Funnel Elements (Kibana) (was: Latency Between Funnel Elements () > Latency Between Funnel Elements (Kibana) > > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-394) Latency
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860498#comment-16860498 ] Joshua Poore commented on FLAGON-394: - I put together a rudimentary user funnel viz in kibana. It's basically shows the proportion of users that land on certain pages/elements of a page, indicating that they're moving through content in a desired/efficient way. You can find in the Bus. Analytics dashboard in incubator-flagon/docker/kibana/saved objects > Latency > > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > visualize time or latency between funnel elements. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Description: visualize time or latency between moving through funnel elements. Experiment with Timelion. (was: visualize time or latency between funnel elements.) > Latency > > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency Between Funnel Elements (
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Affects Version/s: (was: UserALE.js 2.1.0) Flagon 1.0 > Latency Between Funnel Elements ( > - > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency Between Funnel Elements (
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Fix Version/s: (was: UserALE.js 2.1.0) Flagon 1.0 > Latency Between Funnel Elements ( > - > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency Between Funnel Elements (
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Summary: Latency Between Funnel Elements ( (was: Latency) > Latency Between Funnel Elements ( > - > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-394) Latency
[ https://issues.apache.org/jira/browse/FLAGON-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-394: Summary: Latency (was: Latency ) > Latency > --- > > Key: FLAGON-394 > URL: https://issues.apache.org/jira/browse/FLAGON-394 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > visualize time or latency between moving through funnel elements. Experiment > with Timelion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-387) [reReleaseProc] generate rc candidates in staging environment for review
[ https://issues.apache.org/jira/browse/FLAGON-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-387. - Resolution: Fixed > [reReleaseProc] generate rc candidates in staging environment for review > > > Key: FLAGON-387 > URL: https://issues.apache.org/jira/browse/FLAGON-387 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 1.0.0 > > > Update Keys and post to master -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-393) Update Kibana Saved Objects to Flagon name
Joshua Poore created FLAGON-393: --- Summary: Update Kibana Saved Objects to Flagon name Key: FLAGON-393 URL: https://issues.apache.org/jira/browse/FLAGON-393 Project: Flagon Issue Type: Sub-task Components: builds Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 Saved objects still show Apache SensSoft. Change to Apache Flagon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-393) Update Kibana Saved Objects to Flagon name
[ https://issues.apache.org/jira/browse/FLAGON-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-393. - Resolution: Fixed Pushed to FLAGON-344 > Update Kibana Saved Objects to Flagon name > -- > > Key: FLAGON-393 > URL: https://issues.apache.org/jira/browse/FLAGON-393 > Project: Flagon > Issue Type: Sub-task > Components: builds >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0 > > > Saved objects still show Apache SensSoft. Change to Apache Flagon. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-375) Update _site to reflect Flagon name change
[ https://issues.apache.org/jira/browse/FLAGON-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-375: Issue Type: Sub-task (was: Task) Parent: FLAGON-351 > Update _site to reflect Flagon name change > -- > > Key: FLAGON-375 > URL: https://issues.apache.org/jira/browse/FLAGON-375 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Update _site to reflect Flagon name change -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FLAGON-398) Update NPM release via registry
[ https://issues.apache.org/jira/browse/FLAGON-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reassigned FLAGON-398: --- Assignee: (was: Rob Foley) > Update NPM release via registry > --- > > Key: FLAGON-398 > URL: https://issues.apache.org/jira/browse/FLAGON-398 > Project: Flagon > Issue Type: Task > Components: release_scripts, UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Priority: Blocker > Fix For: Flagon 1.0 > > > NOTE: belongs in > [https://github.com/apache/incubator-flagon/tree/FLAGON-344/release] > Our NPM distro on registry is poor: > # distribution doesn't contain pre-build userale scripts (+min) in /build > dir or as 'files': [https://docs.npmjs.com/files/package.json] > # > [https://github.com/apache/incubator-flagon-useralejs/blob/master/build/userale-1.0.0.js] > (not-minified script) has a function (exports) flag, however, unclear if > this exposes functions in prebuilt useralejs script via npm. Would be > convenient if we could package this file, so that npm users could invoke > functions from a single 'require' call, rather than having to require > different src files to find the functions they want exposed. See > [https://docs.npmjs.com/files/package.json] for examples of different include > strategies for npm modules including single vs. multiple src files. > # We have no examples for usage. Generally, our API is great and users of > npm distro don't need to invoke important functions via npm (e.g., .filter, > .map, attachHandler). Even so, it would be good to have at least an > attachHandler example for userale usage via npm. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-398) Update NPM release via registry
Joshua Poore created FLAGON-398: --- Summary: Update NPM release via registry Key: FLAGON-398 URL: https://issues.apache.org/jira/browse/FLAGON-398 Project: Flagon Issue Type: Task Components: release_scripts, UserALE.js Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Rob Foley Fix For: Flagon 1.0 NOTE: belongs in [https://github.com/apache/incubator-flagon/tree/FLAGON-344/release] Our NPM distro on registry is poor: # distribution doesn't contain pre-build userale scripts (+min) in /build dir or as 'files': [https://docs.npmjs.com/files/package.json] # [https://github.com/apache/incubator-flagon-useralejs/blob/master/build/userale-1.0.0.js] (not-minified script) has a function (exports) flag, however, unclear if this exposes functions in prebuilt useralejs script via npm. Would be convenient if we could package this file, so that npm users could invoke functions from a single 'require' call, rather than having to require different src files to find the functions they want exposed. See [https://docs.npmjs.com/files/package.json] for examples of different include strategies for npm modules including single vs. multiple src files. # We have no examples for usage. Generally, our API is great and users of npm distro don't need to invoke important functions via npm (e.g., .filter, .map, attachHandler). Even so, it would be good to have at least an attachHandler example for userale usage via npm. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-401) Add License to WebExtension Files
Joshua Poore created FLAGON-401: --- Summary: Add License to WebExtension Files Key: FLAGON-401 URL: https://issues.apache.org/jira/browse/FLAGON-401 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Add headers to WebExtension src. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-402) Update index.html version number
Joshua Poore created FLAGON-402: --- Summary: Update index.html version number Key: FLAGON-402 URL: https://issues.apache.org/jira/browse/FLAGON-402 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update index.html version number -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-404) Update Readme.md to reflect version 2.0.0
Joshua Poore created FLAGON-404: --- Summary: Update Readme.md to reflect version 2.0.0 Key: FLAGON-404 URL: https://issues.apache.org/jira/browse/FLAGON-404 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update Readme.md to reflect version 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-405) Add new filter examples to Readme.md
Joshua Poore created FLAGON-405: --- Summary: Add new filter examples to Readme.md Key: FLAGON-405 URL: https://issues.apache.org/jira/browse/FLAGON-405 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Add new filter examples to Readme.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-406) interval log start/end times converted to decimals not time/date formate
Joshua Poore created FLAGON-406: --- Summary: interval log start/end times converted to decimals not time/date formate Key: FLAGON-406 URL: https://issues.apache.org/jira/browse/FLAGON-406 Project: Flagon Issue Type: Task Components: builds Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 Enforce strict mapping in userale.json index -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-394) Latency
Joshua Poore created FLAGON-394: --- Summary: Latency Key: FLAGON-394 URL: https://issues.apache.org/jira/browse/FLAGON-394 Project: Flagon Issue Type: Wish Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 visualize time or latency between funnel elements. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-410) Add setLogMapper API examples to README.md and Website
Joshua Poore created FLAGON-410: --- Summary: Add setLogMapper API examples to README.md and Website Key: FLAGON-410 URL: https://issues.apache.org/jira/browse/FLAGON-410 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: Flagon 1.0, UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0, UserALE.js 2.0.0 Add setLogMapper API examples to README.md and Website -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-413) Update Changelog for Release Candidate
Joshua Poore created FLAGON-413: --- Summary: Update Changelog for Release Candidate Key: FLAGON-413 URL: https://issues.apache.org/jira/browse/FLAGON-413 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update Changelog for Release Candidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-411) Update Release Scripts to Package WebExtension
Joshua Poore created FLAGON-411: --- Summary: Update Release Scripts to Package WebExtension Key: FLAGON-411 URL: https://issues.apache.org/jira/browse/FLAGON-411 Project: Flagon Issue Type: Task Components: release_scripts, UserALE.js Affects Versions: Flagon 1.0, UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0, UserALE.js 2.0.0 Update Release Scripts to Package WebExtension -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-412) Update Example page to include mapping and filtering examples
[ https://issues.apache.org/jira/browse/FLAGON-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-412. - Resolution: Fixed > Update Example page to include mapping and filtering examples > - > > Key: FLAGON-412 > URL: https://issues.apache.org/jira/browse/FLAGON-412 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update Example page to include mapping and filtering examples -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-414) Update release scripts to remove md5 sigs
[ https://issues.apache.org/jira/browse/FLAGON-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-414. --- Resolution: Fixed > Update release scripts to remove md5 sigs > - > > Key: FLAGON-414 > URL: https://issues.apache.org/jira/browse/FLAGON-414 > Project: Flagon > Issue Type: Task > Components: release_scripts >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0 > > > violates Apache policy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-339) Update to JSDOM for Unit Testing
[ https://issues.apache.org/jira/browse/FLAGON-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869153#comment-16869153 ] Joshua Poore commented on FLAGON-339: - [https://www.npmjs.com/package/jsdom-global/v/2.0.0] > Update to JSDOM for Unit Testing > > > Key: FLAGON-339 > URL: https://issues.apache.org/jira/browse/FLAGON-339 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.1.0 > > > Something like 22 of 45 unit tests use JSDOM as a prod environment emulator > (webpage). We currently use v8, which is outdated. New version (13.1.0) > introduces breaking changes (as of v10). Namely there are > scripting/syntactical differences in how environments are configured and > called. > Update to current version 13.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-339) Update to JSDOM for Unit Testing
[ https://issues.apache.org/jira/browse/FLAGON-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869140#comment-16869140 ] Joshua Poore commented on FLAGON-339: - [https://github.com/jsdom/jsdom/issues/1815] > Update to JSDOM for Unit Testing > > > Key: FLAGON-339 > URL: https://issues.apache.org/jira/browse/FLAGON-339 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.1.0 > > > Something like 22 of 45 unit tests use JSDOM as a prod environment emulator > (webpage). We currently use v8, which is outdated. New version (13.1.0) > introduces breaking changes (as of v10). Namely there are > scripting/syntactical differences in how environments are configured and > called. > Update to current version 13.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-398) Update NPM release via registry
[ https://issues.apache.org/jira/browse/FLAGON-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-398. - Resolution: Not A Problem Reviewed more documentation. Updated package.json file in useralejs v1r+ should produce usable NPM module > Update NPM release via registry > --- > > Key: FLAGON-398 > URL: https://issues.apache.org/jira/browse/FLAGON-398 > Project: Flagon > Issue Type: Task > Components: release_scripts, UserALE.js >Affects Versions: Flagon 1.0 >Reporter: Joshua Poore >Priority: Blocker > Fix For: Flagon 1.0 > > > NOTE: belongs in > [https://github.com/apache/incubator-flagon/tree/FLAGON-344/release] > Our NPM distro on registry is poor: > # should update package.json and distro for npm module (for release on npm > registry), include at minimum $bash code snippets on release process page on > wiki. Should also include sample package.json for npm module in /release > # distribution doesn't contain pre-build userale scripts (+min) in /build > dir or as 'files': [https://docs.npmjs.com/files/package.json] > # > [https://github.com/apache/incubator-flagon-useralejs/blob/master/build/userale-1.0.0.js] > (not-minified script) has a function (exports) flag, however, unclear if > this exposes functions in prebuilt useralejs script via npm. Would be > convenient if we could package this file, so that npm users could invoke > functions from a single 'require' call, rather than having to require > different src files to find the functions they want exposed. See > [https://docs.npmjs.com/files/package.json] for examples of different include > strategies for npm modules including single vs. multiple src files. > # We have no examples for usage. Generally, our API is great and users of > npm distro don't need to invoke important functions via npm (e.g., .filter, > .map, attachHandler). Even so, it would be good to have at least an > attachHandler example for userale usage via npm. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-414) Update release scripts to remove md5 sigs
Joshua Poore created FLAGON-414: --- Summary: Update release scripts to remove md5 sigs Key: FLAGON-414 URL: https://issues.apache.org/jira/browse/FLAGON-414 Project: Flagon Issue Type: Task Components: release_scripts Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 violates Apache policy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-411) Update Release Scripts to Package WebExtension
[ https://issues.apache.org/jira/browse/FLAGON-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-411. --- Resolution: Fixed > Update Release Scripts to Package WebExtension > -- > > Key: FLAGON-411 > URL: https://issues.apache.org/jira/browse/FLAGON-411 > Project: Flagon > Issue Type: Task > Components: release_scripts, UserALE.js >Affects Versions: Flagon 1.0, UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0, UserALE.js 2.0.0 > > > Update Release Scripts to Package WebExtension -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-413) Update Changelog for Release Candidate
[ https://issues.apache.org/jira/browse/FLAGON-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-413. --- Resolution: Fixed > Update Changelog for Release Candidate > -- > > Key: FLAGON-413 > URL: https://issues.apache.org/jira/browse/FLAGON-413 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update Changelog for Release Candidate -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-329) Browser Fingerprints in UseALE.js
[ https://issues.apache.org/jira/browse/FLAGON-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-329: Fix Version/s: (was: UserALE.js 2.1.0) UserALE.js 2.2.0 > Browser Fingerprints in UseALE.js > - > > Key: FLAGON-329 > URL: https://issues.apache.org/jira/browse/FLAGON-329 > Project: Flagon > Issue Type: New Feature > Components: UserALE.js >Affects Versions: UserALE.js 2.2.0 >Reporter: Joshua Poore >Priority: Minor > Fix For: UserALE.js 2.2.0 > > > End Users want to get details about a browser. They want this available in > the script tag deployment scheme. > It should be trivial to get through navigator.appVersion property, and add > some logic to parse the broswer and version to make them searchable in one or > more fields. > This should be on every document, so this is a mod to packageLogs UserALE.js > src -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-329) Browser Fingerprints in UseALE.js
[ https://issues.apache.org/jira/browse/FLAGON-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-329: Affects Version/s: (was: UserALE.js 2.1.0) UserALE.js 2.2.0 > Browser Fingerprints in UseALE.js > - > > Key: FLAGON-329 > URL: https://issues.apache.org/jira/browse/FLAGON-329 > Project: Flagon > Issue Type: New Feature > Components: UserALE.js >Affects Versions: UserALE.js 2.2.0 >Reporter: Joshua Poore >Priority: Minor > Fix For: UserALE.js 2.1.0 > > > End Users want to get details about a browser. They want this available in > the script tag deployment scheme. > It should be trivial to get through navigator.appVersion property, and add > some logic to parse the broswer and version to make them searchable in one or > more fields. > This should be on every document, so this is a mod to packageLogs UserALE.js > src -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-386) Update Readmes to include methods for including useralejs in project as NPM package
[ https://issues.apache.org/jira/browse/FLAGON-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-386. - Resolution: Fixed not an issue–>can use API and standard methods (better). NPM is mostly a CD tool. > Update Readmes to include methods for including useralejs in project as NPM > package > --- > > Key: FLAGON-386 > URL: https://issues.apache.org/jira/browse/FLAGON-386 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-397) Add method for including Apache License headers to Build Artifacts
Joshua Poore created FLAGON-397: --- Summary: Add method for including Apache License headers to Build Artifacts Key: FLAGON-397 URL: https://issues.apache.org/jira/browse/FLAGON-397 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 build pipeline needs to produce artifacts with /*commented*/ apache licenses. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-396) Add License to testUtils
[ https://issues.apache.org/jira/browse/FLAGON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-396: Reporter: Dave Meikle (was: Joshua Poore) > Add License to testUtils > > > Key: FLAGON-396 > URL: https://issues.apache.org/jira/browse/FLAGON-396 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Dave Meikle >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > Need to add license to testUtils prior to release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-396) Add License to testUtils
[ https://issues.apache.org/jira/browse/FLAGON-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-396. --- Resolution: Fixed Pushed. > Add License to testUtils > > > Key: FLAGON-396 > URL: https://issues.apache.org/jira/browse/FLAGON-396 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Dave Meikle >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > Need to add license to testUtils prior to release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-397) Add Apache License headers to pre-built Artifacts
[ https://issues.apache.org/jira/browse/FLAGON-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-397: Description: add apache licenses to build artifacts (was: build pipeline needs to produce artifacts with /*commented*/ apache licenses.) > Add Apache License headers to pre-built Artifacts > - > > Key: FLAGON-397 > URL: https://issues.apache.org/jira/browse/FLAGON-397 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > add apache licenses to build artifacts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-397) Add Apache License headers to pre-built Artifacts
[ https://issues.apache.org/jira/browse/FLAGON-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-397: Summary: Add Apache License headers to pre-built Artifacts (was: Add method for including Apache License headers to Build Artifacts) > Add Apache License headers to pre-built Artifacts > - > > Key: FLAGON-397 > URL: https://issues.apache.org/jira/browse/FLAGON-397 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > build pipeline needs to produce artifacts with /*commented*/ apache licenses. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-397) Add Apache License headers to pre-built Artifacts
[ https://issues.apache.org/jira/browse/FLAGON-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-397. - Resolution: Fixed pulled, merged with master > Add Apache License headers to pre-built Artifacts > - > > Key: FLAGON-397 > URL: https://issues.apache.org/jira/browse/FLAGON-397 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Dave Meikle >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > add apache licenses to build artifacts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-397) Add Apache License headers to pre-built Artifacts
[ https://issues.apache.org/jira/browse/FLAGON-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-397: Reporter: Dave Meikle (was: Joshua Poore) > Add Apache License headers to pre-built Artifacts > - > > Key: FLAGON-397 > URL: https://issues.apache.org/jira/browse/FLAGON-397 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 >Reporter: Dave Meikle >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 > > > add apache licenses to build artifacts -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-396) Add License to testUtils
Joshua Poore created FLAGON-396: --- Summary: Add License to testUtils Key: FLAGON-396 URL: https://issues.apache.org/jira/browse/FLAGON-396 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0, UserALE.js 1.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0, UserALE.js 1.0.0 Need to add license to testUtils prior to release -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FLAGON-395) Add ability to send data via Sockets (as opposed to POST)
[ https://issues.apache.org/jira/browse/FLAGON-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862608#comment-16862608 ] Joshua Poore edited comment on FLAGON-395 at 6/13/19 1:01 AM: -- Welcome [~maschreib28]. This is an interesting feature. I like the idea of reducing comms burden on a network, and sockets would help handle heavy traffic, which UserALE.js can create. I'll check out your project. Currently swamped in releases and branch clean-up. Note that our newest features are on branches 192 and 336. I expect to merge ++192 with Master this week. I'll take a look at your fork soon. Glad to have you! Don't forget to join our list: [dev-subscr...@flagon.incubator.org|mailto:dev-subscr...@flagon.incubator.org] so that you can participate in VOTEs and chat with the community. was (Author: poor...@me.com): Welcome [~maschreib28]. This is an interesting feature. I like the idea of reducing comms burden on a network, and sockets would help handle heavy traffic, which UserALE.js can create. I'll check out your project. Currently swamped in releases and branch clean-up. Note that our newest features are on branches FLAGON-192 and FLAGON-336. I expect to merge FLAGON-192 with Master this week. I'll take a look at your fork soon. Glad to have you! Don't forget to join our list: [dev-subscr...@flagon.incubator.org|mailto:dev-subscr...@flagon.incubator.org] so that you can participate in VOTEs and chat with the community. > Add ability to send data via Sockets (as opposed to POST) > - > > Key: FLAGON-395 > URL: https://issues.apache.org/jira/browse/FLAGON-395 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Reporter: Michael Schreiber >Assignee: Rob Foley >Priority: Minor > Labels: features > > It would be nice to add the capability to send via sockets, as opposed to > POST requests, however, this adds some additional complication with how to > reference the app. > I have some work in progress > ([https://github.com/mschreib28/UserALE-sockets]). But anyone is welcome to > work on this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FLAGON-395) Add ability to send data via Sockets (as opposed to POST)
[ https://issues.apache.org/jira/browse/FLAGON-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16862608#comment-16862608 ] Joshua Poore commented on FLAGON-395: - Welcome [~maschreib28]. This is an interesting feature. I like the idea of reducing comms burden on a network, and sockets would help handle heavy traffic, which UserALE.js can create. I'll check out your project. Currently swamped in releases and branch clean-up. Note that our newest features are on branches FLAGON-192 and FLAGON-336. I expect to merge FLAGON-192 with Master this week. I'll take a look at your fork soon. Glad to have you! Don't forget to join our list: [dev-subscr...@flagon.incubator.org|mailto:dev-subscr...@flagon.incubator.org] so that you can participate in VOTEs and chat with the community. > Add ability to send data via Sockets (as opposed to POST) > - > > Key: FLAGON-395 > URL: https://issues.apache.org/jira/browse/FLAGON-395 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Reporter: Michael Schreiber >Assignee: Rob Foley >Priority: Minor > Labels: features > > It would be nice to add the capability to send via sockets, as opposed to > POST requests, however, this adds some additional complication with how to > reference the app. > I have some work in progress > ([https://github.com/mschreib28/UserALE-sockets]). But anyone is welcome to > work on this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-407) Jenkins Builds Failing at Master
[ https://issues.apache.org/jira/browse/FLAGON-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-407. - Resolution: Fixed The issue was that gulp var for UserAleWebExtension dir name did not match actual src file. *headslap*. I guess ubuntu is less flexible in resolving paths than my Mac... Anyway, builds are back to normal and have rolled back changes in new packages 'Rollup-Plugin-CommonJS', 'Rollup-Plugin-Node-Resolve' to avoid bloat. Kept version updates to existing rollup packages. > Jenkins Builds Failing at Master > > > Key: FLAGON-407 > URL: https://issues.apache.org/jira/browse/FLAGON-407 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.0.0 > > > Local builds, unit tests, and functional tests check out. I've tested locally > on node 11.10.0 and 12.2.0. > Jenkins tests are failing on both following inclusion of rollup operations in > Gulp pipeline for WebExtension. Here is current: > * *Tests:* npm > * *Node:*node-v12.2.0-linux-x64 > relevant? > [https://github.com/tj/n/issues/565] > > Error: > > [19:00:37] Starting 'test'... > [19:00:37] Starting 'build'... > [19:00:37] Starting 'rollup'... > [19:00:38] Finished 'rollup' after 493 ms > [19:00:38] Starting 'build-web-ext'... > [19:00:38] Starting 'rollup-web-ext-content'... > [19:00:38] 'rollup-web-ext-content' errored after 3.63 ms > [19:00:38] Error: Could not resolve entry module > (src/UserAleWebExtension/content.js). > at error > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:9365:30) > at pluginDriver.hookFirst.then.resolveIdResult > (<[https://builds.apache.org/job/useralejs-ci/ws/node_modules/rollup/dist/rollup.js]>:16097:20) > at process._tickDomainCallback (internal/process/next_tick.js:135:7) > [19:00:38] 'build-web-ext' errored after 18 ms > [19:00:38] 'build' errored after 513 ms > [19:00:38] 'test' errored after 516 ms > npm ERR! code ELIFECYCLE > npm ERR! errno 1 > npm ERR! useralejs@2.0.0 test: `gulp test` > npm ERR! Exit status 1 > npm ERR! > npm ERR! Failed at the useralejs@2.0.0 test script. > npm ERR! This is probably not a problem with npm. There is likely additional > logging output above. > npm ERR! A complete log of this run can be found in: > npm ERR! /home/jenkins/.npm/_logs/2019-06-14T19_00_38_238Z-debug.log > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-409) Update package.json file to indicate that we can now support Node 12.2.0 (engines)
[ https://issues.apache.org/jira/browse/FLAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-409. - Resolution: Done > Update package.json file to indicate that we can now support Node 12.2.0 > (engines) > -- > > Key: FLAGON-409 > URL: https://issues.apache.org/jira/browse/FLAGON-409 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update package.json file to indicate that we can now support Node 12.2.0 > (engines) > Successful testing on Node 12.2.0! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-409) Update package.json file to indicate that we can now support Node 12.2.0 (engines)
[ https://issues.apache.org/jira/browse/FLAGON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-409. --- > Update package.json file to indicate that we can now support Node 12.2.0 > (engines) > -- > > Key: FLAGON-409 > URL: https://issues.apache.org/jira/browse/FLAGON-409 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update package.json file to indicate that we can now support Node 12.2.0 > (engines) > Successful testing on Node 12.2.0! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-409) Update package.json file to indicate that we can now support Node 12.2.0 (engines)
Joshua Poore created FLAGON-409: --- Summary: Update package.json file to indicate that we can now support Node 12.2.0 (engines) Key: FLAGON-409 URL: https://issues.apache.org/jira/browse/FLAGON-409 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update package.json file to indicate that we can now support Node 12.2.0 (engines) Successful testing on Node 12.2.0! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-383) Update README.md and Notices to Reflect Flagon namechange
[ https://issues.apache.org/jira/browse/FLAGON-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-383: Affects Version/s: UserALE.js 2.1.0 UserALE.js 1.0.0 > Update README.md and Notices to Reflect Flagon namechange > - > > Key: FLAGON-383 > URL: https://issues.apache.org/jira/browse/FLAGON-383 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0, UserALE.js 2.0.0, UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > Update README.md and Notices to Reflect Flagon namechange > Also modifying copyright to correct appropriate copyright attribution to > Apache Software Foundation (double checked software grant on file and > [https://www.apache.org/legal/src-headers.html#header-existingcopyright]. The > Apache SensSoft/Flagon Copyright does not fall under the category of a > 'Third-Party Work'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-384) useralejs Jenkins build is failing (#32-33)
[ https://issues.apache.org/jira/browse/FLAGON-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-384. - Resolution: Not A Problem action is to update configs or raise issue with builds. > useralejs Jenkins build is failing (#32-33) > --- > > Key: FLAGON-384 > URL: https://issues.apache.org/jira/browse/FLAGON-384 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Trivial > Fix For: UserALE.js 1.0.0 > > Attachments: CIFail32useralejs, useralejsNODE4_6_0_replication.rtf > > > [https://builds.apache.org/job/useralejs-ci/32/] [^CIFail32useralejs] > Jenkins build failed after recent > [commit|[https://github.com/apache/incubator-flagon-useralejs/commit/4bb5ebe8be228242861556c31ac6f4b78b929177]]. > This is weird because the commit exclusively incorporated changes to text > referencing SensSoft, and links (Flagon–>SensSoft). This triggered a build > test on Jenkins, which failed (see attachment). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-384) useralejs Jenkins build is failing (#32-33)
Joshua Poore created FLAGON-384: --- Summary: useralejs Jenkins build is failing (#32-33) Key: FLAGON-384 URL: https://issues.apache.org/jira/browse/FLAGON-384 Project: Flagon Issue Type: Bug Components: UserALE.js Affects Versions: UserALE.js 1.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 1.0.0 Attachments: CIFail32useralejs [https://builds.apache.org/job/useralejs-ci/32/] [^CIFail32useralejs] Jenkins build failed after recent [commit|[https://github.com/apache/incubator-flagon-useralejs/commit/4bb5ebe8be228242861556c31ac6f4b78b929177]]. This is weird because the commit exclusively incorporated changes to text referencing SensSoft, and links (Flagon–>SensSoft). This triggered a build test on Jenkins, which failed (see attachment). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-376) Add pre-build UserALE.js in src
Joshua Poore created FLAGON-376: --- Summary: Add pre-build UserALE.js in src Key: FLAGON-376 URL: https://issues.apache.org/jira/browse/FLAGON-376 Project: Flagon Issue Type: Improvement Components: documentation, UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 To make new adopters' lives easier, include a pre-build version of userale.js in src. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-376) Add pre-build UserALE.js in src
[ https://issues.apache.org/jira/browse/FLAGON-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-376. --- Resolution: Fixed pushed to FLAGON-192, FLAGON-336 > Add pre-build UserALE.js in src > --- > > Key: FLAGON-376 > URL: https://issues.apache.org/jira/browse/FLAGON-376 > Project: Flagon > Issue Type: Improvement > Components: documentation, UserALE.js >Affects Versions: UserALE.js 2.0.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.0.0 > > > To make new adopters' lives easier, include a pre-build version of userale.js > in src. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-378) Create Modifying UserALE.js src docs for site
Joshua Poore created FLAGON-378: --- Summary: Create Modifying UserALE.js src docs for site Key: FLAGON-378 URL: https://issues.apache.org/jira/browse/FLAGON-378 Project: Flagon Issue Type: Improvement Components: website Affects Versions: Website 0.1, Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, Flagon 1.0 Users should have some guidance for how to modify userale.js at source prior to builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-379) Create stack scaling docs page
Joshua Poore created FLAGON-379: --- Summary: Create stack scaling docs page Key: FLAGON-379 URL: https://issues.apache.org/jira/browse/FLAGON-379 Project: Flagon Issue Type: Improvement Components: website Affects Versions: Website 0.1, Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, Flagon 1.0 Should provide users with some benchmarks and scaling guidance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-361) Update UserALEjs Getting Started instructions in docs
[ https://issues.apache.org/jira/browse/FLAGON-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-361. - Resolution: Fixed Updated. Pushed to branch FLAGON-344 > Update UserALEjs Getting Started instructions in docs > - > > Key: FLAGON-361 > URL: https://issues.apache.org/jira/browse/FLAGON-361 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Update UserALE.js docs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-378) Create Modifying UserALE.js src docs for site
[ https://issues.apache.org/jira/browse/FLAGON-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-378: Issue Type: Sub-task (was: Improvement) Parent: FLAGON-351 > Create Modifying UserALE.js src docs for site > - > > Key: FLAGON-378 > URL: https://issues.apache.org/jira/browse/FLAGON-378 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Users should have some guidance for how to modify userale.js at source prior > to builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-377) Create UserALE.js API docs page
[ https://issues.apache.org/jira/browse/FLAGON-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-377: Issue Type: Sub-task (was: Improvement) Parent: FLAGON-351 > Create UserALE.js API docs page > --- > > Key: FLAGON-377 > URL: https://issues.apache.org/jira/browse/FLAGON-377 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Users should know how to use our API. Also, we need a place to collect > additional examples. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-377) Create UserALE.js API docs page
[ https://issues.apache.org/jira/browse/FLAGON-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-377. - Resolution: Fixed > Create UserALE.js API docs page > --- > > Key: FLAGON-377 > URL: https://issues.apache.org/jira/browse/FLAGON-377 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Users should know how to use our API. Also, we need a place to collect > additional examples. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FLAGON-380) Update UserALE.js build & test page
[ https://issues.apache.org/jira/browse/FLAGON-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-380. --- Updated pushed to branch FLAGON-344 > Update UserALE.js build & test page > --- > > Key: FLAGON-380 > URL: https://issues.apache.org/jira/browse/FLAGON-380 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Need to update UserALE.js docs pages to reflect modern build/test docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-377) Create UserALE.js API docs page
Joshua Poore created FLAGON-377: --- Summary: Create UserALE.js API docs page Key: FLAGON-377 URL: https://issues.apache.org/jira/browse/FLAGON-377 Project: Flagon Issue Type: Improvement Components: website Affects Versions: Website 0.1, Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, Flagon 1.0 Users should know how to use our API. Also, we need a place to collect additional examples. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-379) Create stack scaling docs page
[ https://issues.apache.org/jira/browse/FLAGON-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-379: Issue Type: Sub-task (was: Improvement) Parent: FLAGON-351 > Create stack scaling docs page > -- > > Key: FLAGON-379 > URL: https://issues.apache.org/jira/browse/FLAGON-379 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Should provide users with some benchmarks and scaling guidance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-380) Update UserALE.js build & test page
Joshua Poore created FLAGON-380: --- Summary: Update UserALE.js build & test page Key: FLAGON-380 URL: https://issues.apache.org/jira/browse/FLAGON-380 Project: Flagon Issue Type: Sub-task Components: website Affects Versions: Website 0.1, Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, Flagon 1.0 Need to update UserALE.js docs pages to reflect modern build/test docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-381) Create dataschema docs page for UserALE.js
Joshua Poore created FLAGON-381: --- Summary: Create dataschema docs page for UserALE.js Key: FLAGON-381 URL: https://issues.apache.org/jira/browse/FLAGON-381 Project: Flagon Issue Type: Sub-task Components: website Affects Versions: Website 0.1, Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, Flagon 1.0 Create dataschema docs page for UserALE.js. Should detail UserALE.js data model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-289) Remove Logstash Dependency for Header Requests
[ https://issues.apache.org/jira/browse/FLAGON-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-289. - Resolution: Not A Problem Not really a problem > Remove Logstash Dependency for Header Requests > -- > > Key: FLAGON-289 > URL: https://issues.apache.org/jira/browse/FLAGON-289 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 1.0.0 > Environment: JavaScript >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 1.1.0 > > Original Estimate: 2m > Remaining Estimate: 2m > > We have previously relied on Logstash to handle requests from the page for > data from headers. This is a vulnerability for two reasons: it makes certain > information passed to UserALE.js via our API unobtainable and it places a > strong dependency on Elastic assets and specific system configurations to get > basic data. > Definition of Done: Header Requests are Made By UserALE.js not LogStash. > Remove configs from existing logstash-config. Confirm that when logging, > UserALE.js logs from browser tabs are correctly providing data pushed through > UserALE.js API (useraleVersion, toolName, toolVersion, userId. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-267) Update ElasticSearch Templates to Properly Index new UserALE.js WebEXT Fields
[ https://issues.apache.org/jira/browse/FLAGON-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-267: Fix Version/s: (was: UserALE.js 1.1.0) UserALE.js 2.1.0 > Update ElasticSearch Templates to Properly Index new UserALE.js WebEXT Fields > - > > Key: FLAGON-267 > URL: https://issues.apache.org/jira/browse/FLAGON-267 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Affects Versions: Flagon 1.0, UserALE.js 1.0.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 2.1.0 > > > Some new fields generated through the webextension are being indexed as > string, but should be integers or others. Configs and mapping need be updated. > in userale forwarder, not in 'es' container > Definition of Done = updating userale-conf -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-341) Web Extension Produces Duplicate Logs
[
https://issues.apache.org/jira/browse/FLAGON-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated FLAGON-341:
Affects Version/s: (was: UserALE.js 2.0.0)
(was: UserALE.js 1.1.0)
UserALE.js 2.2.0
> Web Extension Produces Duplicate Logs
> -
>
> Key: FLAGON-341
> URL: https://issues.apache.org/jira/browse/FLAGON-341
> Project: Flagon
> Issue Type: Bug
> Components: UserALE.js
>Affects Versions: UserALE.js 2.2.0
> Environment: Chrome 72
> Firefox 65
> javascript
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.2.0
>
>
> The Web Extension produces duplicate logs w/ identical class structure and
> time stamps (incl. microtime).
> Affects 'SENSSOFT-336', '-SENSSOFT-192'- branches, and pre-Gulp 4.0.0
> '-SENSSOFT-192'- builds.
> Affects logs originating from both Firefox and Chrome
> Confirmed that this isn't an indexing problem with Elastic–duplicate logs
> appear in local file using our example server test utility.
> Confirmed using both temporary 'unpacked' extensions built from source, and
> pre-build extension on chrome store.
> Behavior noted following upgrade to recent versions of Chrome/Firefox (72/65)
> Confirmed that this behavior DOES NOT affect UserALE.js script tag
> deployments.
> Confirmed that this behavior originates from browser using java "example" log
> server (see below).
> {code:java}
> {"target":"div#main-masthead.ui masthead padded center aligned inverted
> vertical segment","path":["div#main-masthead.ui masthead padded center
> aligned inverted vertical
> segment","div.main-wrapper","body","html","#document","Window"],"pageUrl":"http://senssoft.incubator.apache.org/","pageTitle":"Apache
>
> SensSoft","pageReferrer":"","clientTime":1553281575226,"microTime":0.73,"location":{"x":288,"y":70},"type":"click","logType":"raw","userAction":true,"details":{"clicks":1,"ctrl":false,"alt":false,"shift":false,"meta":false},"userId":"nobody","toolVersion":null,"toolName":"test_app","useraleVersion":"1.1.0","sessionID":"session_1553280781567"},
> {"target":"div#main-masthead.ui masthead padded center aligned inverted
> vertical segment","path":["div#main-masthead.ui masthead padded center
> aligned inverted vertical
> segment","div.main-wrapper","body","html","#document","Window"],"pageUrl":"http://senssoft.incubator.apache.org/","pageTitle":"Apache
>
> SensSoft","pageReferrer":"","clientTime":1553281575226,"microTime":0.73,"location":{"x":288,"y":70},"type":"click","logType":"raw","userAction":true,"details":{"clicks":1,"ctrl":false,"alt":false,"shift":false,"meta":false},"userId":"nobody","toolVersion":null,"toolName":"test_app","useraleVersion":"1.1.0","sessionID":"session_1553280781567"},
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLAGON-339) Update to JSDOM for Unit Testing
[ https://issues.apache.org/jira/browse/FLAGON-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-339: Affects Version/s: (was: UserALE.js 2.0.0) UserALE.js 2.1.0 > Update to JSDOM for Unit Testing > > > Key: FLAGON-339 > URL: https://issues.apache.org/jira/browse/FLAGON-339 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: UserALE.js 2.1.0 > > > Something like 22 of 45 unit tests use JSDOM as a prod environment emulator > (webpage). We currently use v8, which is outdated. New version (13.1.0) > introduces breaking changes (as of v10). Namely there are > scripting/syntactical differences in how environments are configured and > called. > Update to current version 13.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLAGON-343) Browser "Options" 'Tool Version" field doesn't appear to write to tool_version (or tool major, minor, patch) version
[ https://issues.apache.org/jira/browse/FLAGON-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-343: Affects Version/s: (was: UserALE.js 2.0.0) UserALE.js 2.2.0 > Browser "Options" 'Tool Version" field doesn't appear to write to > tool_version (or tool major, minor, patch) version > > > Key: FLAGON-343 > URL: https://issues.apache.org/jira/browse/FLAGON-343 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 2.2.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Minor > Fix For: UserALE.js 2.2.0 > > > major_version, minor_version, patch_version successfully parse > userAleVersion, but ToolVersion is not similarly parsed and viewable in > kibana. Could be an indexing issue. If so, will move ticket to SensSoft v 1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FLAGON-379) Create stack scaling docs page
[ https://issues.apache.org/jira/browse/FLAGON-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-379. - Resolution: Done Done. Pushed to branch FLAGON-344 > Create stack scaling docs page > -- > > Key: FLAGON-379 > URL: https://issues.apache.org/jira/browse/FLAGON-379 > Project: Flagon > Issue Type: Sub-task > Components: website >Affects Versions: Website 0.1, Flagon 1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0 > > > Should provide users with some benchmarks and scaling guidance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FLAGON-383) Update README.md and Notices to Reflect Flagon namechange
Joshua Poore created FLAGON-383: --- Summary: Update README.md and Notices to Reflect Flagon namechange Key: FLAGON-383 URL: https://issues.apache.org/jira/browse/FLAGON-383 Project: Flagon Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 2.0.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.0.0 Update README.md and Notices to Reflect Flagon namechange Also modifying copyright to correct appropriate copyright attribution to Apache Software Foundation (double checked software grant on file and [https://www.apache.org/legal/src-headers.html#header-existingcopyright]. The Apache SensSoft/Flagon Copyright does not fall under the category of a 'Third-Party Work'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
