[jira] [Closed] (FLAGON-331) Call and Configured UserAle.js via Webpack from src
[ https://issues.apache.org/jira/browse/FLAGON-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-331. --- Resolution: Duplicate > Call and Configured UserAle.js via Webpack from src > --- > > Key: FLAGON-331 > URL: https://issues.apache.org/jira/browse/FLAGON-331 > 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 use webpack to call and configure userale.js from src. > Merit's investigation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (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 closed FLAGON-343. --- Resolution: Fixed Fixed in 2.1.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 (v8.3.4#803005)
[jira] [Closed] (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 closed FLAGON-329. --- Resolution: Duplicate > 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 (v8.3.4#803005)
[jira] [Closed] (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 closed FLAGON-267. --- Resolution: Fixed > 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: UserALE.js 2.2.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Major > Fix For: UserALE.js 2.2.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 (v8.3.4#803005)
[jira] [Resolved] (FLAGON-487) test data-version in script and options params
[ https://issues.apache.org/jira/browse/FLAGON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-487. - Resolution: Fixed > test data-version in script and options params > -- > > Key: FLAGON-487 > URL: https://issues.apache.org/jira/browse/FLAGON-487 > Project: Flagon > Issue Type: Test > 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 > > > test to make sure that toolVersion populates using both script-tag HTML > params and options configs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-485) Add prototype .asf.yaml file
[ https://issues.apache.org/jira/browse/FLAGON-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-485. - Resolution: Fixed > Add prototype .asf.yaml file > > > Key: FLAGON-485 > URL: https://issues.apache.org/jira/browse/FLAGON-485 > Project: Flagon > Issue Type: Test > 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 > > > Add .asf.yaml to enable issues, projects and modify labels, description, etc. > Should add features for repo discovery. > prototype pending vote. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-487) test data-version in script and options params
Joshua Poore created FLAGON-487: --- Summary: test data-version in script and options params Key: FLAGON-487 URL: https://issues.apache.org/jira/browse/FLAGON-487 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 test to make sure that toolVersion populates using both script-tag HTML params and options configs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-486) toolName does not populate in logs
[ https://issues.apache.org/jira/browse/FLAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026431#comment-17026431 ] Joshua Poore commented on FLAGON-486: - was misreferenced in package logs as 'tool'. > toolName does not populate in logs > -- > > Key: FLAGON-486 > URL: https://issues.apache.org/jira/browse/FLAGON-486 > Project: Flagon > Issue Type: Bug > 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 > > > toolName does not populate in logs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-486) toolName does not populate in logs
Joshua Poore created FLAGON-486: --- Summary: toolName does not populate in logs Key: FLAGON-486 URL: https://issues.apache.org/jira/browse/FLAGON-486 Project: Flagon Issue Type: Bug Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 toolName does not populate in logs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-483) userale.log & userale.packageCustomLog logs are not being indexed by ES
[ https://issues.apache.org/jira/browse/FLAGON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026430#comment-17026430 ] Joshua Poore commented on FLAGON-483: - issue was that examples used non-objects for details field, just strings. Not a real issue with src. > userale.log & userale.packageCustomLog logs are not being indexed by ES > --- > > Key: FLAGON-483 > URL: https://issues.apache.org/jira/browse/FLAGON-483 > Project: Flagon > Issue Type: Bug > 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 > > > New examples for .log and .packageCustomLog are generating logs, but logs are > not being indexed by ES back end. > * Logs are being generated and show expected structure via example logging > server > * 'raw' logs generated from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-483) userale.log & userale.packageCustomLog logs are not being indexed by ES
[ https://issues.apache.org/jira/browse/FLAGON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-483. - Resolution: Fixed > userale.log & userale.packageCustomLog logs are not being indexed by ES > --- > > Key: FLAGON-483 > URL: https://issues.apache.org/jira/browse/FLAGON-483 > Project: Flagon > Issue Type: Bug > 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 > > > New examples for .log and .packageCustomLog are generating logs, but logs are > not being indexed by ES back end. > * Logs are being generated and show expected structure via example logging > server > * 'raw' logs generated from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-483) userale.log & userale.packageCustomLog logs are not being indexed by ES
[
https://issues.apache.org/jira/browse/FLAGON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026410#comment-17026410
]
Joshua Poore commented on FLAGON-483:
-
looks like a indexing issue. From LogStash:
[2020-01-30T02:58:53,581][WARN ][logstash.outputs.elasticsearch] Could not
index event to Elasticsearch. \{:status=>400, :action=>["index", {:_id=>nil,
:_index=>"userale", :_type=>"doc", :routing=>nil},
#], :response=>\{"index"=>{"_index"=>"userale",
"_type"=>"doc", "_id"=>"bHFj9G8BoZIUZ9d4Gw79", "status"=>400,
"error"=>{"type"=>"mapper_parsing_exception", "reason"=>"object mapping for
[details] tried to parse field [details] as object, but found a concrete
value"
> userale.log & userale.packageCustomLog logs are not being indexed by ES
> ---
>
> Key: FLAGON-483
> URL: https://issues.apache.org/jira/browse/FLAGON-483
> Project: Flagon
> Issue Type: Bug
> 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
>
>
> New examples for .log and .packageCustomLog are generating logs, but logs are
> not being indexed by ES back end.
> * Logs are being generated and show expected structure via example logging
> server
> * 'raw' logs generated from
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FLAGON-485) Add prototype .asf.yaml file
Joshua Poore created FLAGON-485: --- Summary: Add prototype .asf.yaml file Key: FLAGON-485 URL: https://issues.apache.org/jira/browse/FLAGON-485 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 Add .asf.yaml to enable issues, projects and modify labels, description, etc. Should add features for repo discovery. prototype pending vote. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-479) update readme for package manager/compiler deployment example
[ https://issues.apache.org/jira/browse/FLAGON-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-479. - Resolution: Fixed > update readme for package manager/compiler deployment example > - > > Key: FLAGON-479 > URL: https://issues.apache.org/jira/browse/FLAGON-479 > Project: Flagon > Issue Type: Improvement > 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 (v8.3.4#803005)
[jira] [Resolved] (FLAGON-484) confirm that 'require' method works as well as 'import' for webpack example
[ https://issues.apache.org/jira/browse/FLAGON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-484. - Resolution: Fixed > confirm that 'require' method works as well as 'import' for webpack example > --- > > Key: FLAGON-484 > URL: https://issues.apache.org/jira/browse/FLAGON-484 > Project: Flagon > Issue Type: Test > 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 > > > confirm that 'require' method works as well as 'import' for webpack example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-484) confirm that 'require' method works as well as 'import' for webpack example
Joshua Poore created FLAGON-484: --- Summary: confirm that 'require' method works as well as 'import' for webpack example Key: FLAGON-484 URL: https://issues.apache.org/jira/browse/FLAGON-484 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 confirm that 'require' method works as well as 'import' for webpack example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-484) confirm that 'require' method works as well as 'import' for webpack example
[ https://issues.apache.org/jira/browse/FLAGON-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17023709#comment-17023709 ] Joshua Poore commented on FLAGON-484: - confirmed > confirm that 'require' method works as well as 'import' for webpack example > --- > > Key: FLAGON-484 > URL: https://issues.apache.org/jira/browse/FLAGON-484 > Project: Flagon > Issue Type: Test > 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 > > > confirm that 'require' method works as well as 'import' for webpack example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-482) Log Call Back function from userale demo, might be interesting in mainline UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-482: Issue Type: Wish (was: Bug) > Log Call Back function from userale demo, might be interesting in mainline > UserALE.js > - > > Key: FLAGON-482 > URL: https://issues.apache.org/jira/browse/FLAGON-482 > Project: Flagon > Issue Type: Wish > Components: UserALE.js >Affects Versions: Website 0.1, UserALE.js 2.1.1 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, UserALE.js 2.1.1 > > > **Log Call Back function from userale demo, might be interesting in mainline > UserALE.js > > might want to do additional logging or client side work, leveraging callback > logs – last 5 logs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-483) userale.log & userale.packageCustomLog logs are not being indexed by ES
Joshua Poore created FLAGON-483: --- Summary: userale.log & userale.packageCustomLog logs are not being indexed by ES Key: FLAGON-483 URL: https://issues.apache.org/jira/browse/FLAGON-483 Project: Flagon Issue Type: Bug Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 New examples for .log and .packageCustomLog are generating logs, but logs are not being indexed by ES back end. * Logs are being generated and show expected structure via example logging server * 'raw' logs generated from -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-482) Log Call Back function from userale demo, might be interesting in mainline UserALE.js
Joshua Poore created FLAGON-482: --- Summary: Log Call Back function from userale demo, might be interesting in mainline UserALE.js Key: FLAGON-482 URL: https://issues.apache.org/jira/browse/FLAGON-482 Project: Flagon Issue Type: Bug Components: UserALE.js Affects Versions: Website 0.1, UserALE.js 2.1.1 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1, UserALE.js 2.1.1 **Log Call Back function from userale demo, might be interesting in mainline UserALE.js might want to do additional logging or client side work, leveraging callback logs – last 5 logs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-479) update readme for package manager/compiler deployment example
[ https://issues.apache.org/jira/browse/FLAGON-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-479: Summary: update readme for package manager/compiler deployment example (was: update readme for package manager/compiler deployment options and API usage) > update readme for package manager/compiler deployment example > - > > Key: FLAGON-479 > URL: https://issues.apache.org/jira/browse/FLAGON-479 > Project: Flagon > Issue Type: Improvement > 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 (v8.3.4#803005)
[jira] [Created] (FLAGON-481) update top level readme for new Package loader deployment instructions
Joshua Poore created FLAGON-481: --- Summary: update top level readme for new Package loader deployment instructions Key: FLAGON-481 URL: https://issues.apache.org/jira/browse/FLAGON-481 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 update top level readme for new Package loader deployment instructions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-436) Print Screen Resolution
[
https://issues.apache.org/jira/browse/FLAGON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013062#comment-17013062
]
Joshua Poore commented on FLAGON-436:
-
Looks like
scrnRes: \{ width: 1280, height: 689 },
Behaves as expected in plugin and scriptTag
> Print Screen Resolution
> ---
>
> Key: FLAGON-436
> URL: https://issues.apache.org/jira/browse/FLAGON-436
> Project: Flagon
> Issue Type: New Feature
> 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
>
>
> Most of these are gettable via standard, exposed document/window properties.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FLAGON-480) Test Browser Plugin Behavior with UMD userale format
Joshua Poore created FLAGON-480: --- Summary: Test Browser Plugin Behavior with UMD userale format Key: FLAGON-480 URL: https://issues.apache.org/jira/browse/FLAGON-480 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 ensure browser plugin works well now that UserALE.js is packaged into a UMD format, not iife. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-478) Update index.html to provide instructions for generating certain kinds of logs
[ https://issues.apache.org/jira/browse/FLAGON-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-478. --- Resolution: Fixed Updated with instructions on the Example page > Update index.html to provide instructions for generating certain kinds of logs > -- > > Key: FLAGON-478 > URL: https://issues.apache.org/jira/browse/FLAGON-478 > Project: Flagon > Issue Type: Improvement > 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 (v8.3.4#803005)
[jira] [Resolved] (FLAGON-480) Test Browser Plugin Behavior with UMD userale format
[ https://issues.apache.org/jira/browse/FLAGON-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-480. - Resolution: Fixed Tests as expected. > Test Browser Plugin Behavior with UMD userale format > > > Key: FLAGON-480 > URL: https://issues.apache.org/jira/browse/FLAGON-480 > Project: Flagon > Issue Type: Test > 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 > > > ensure browser plugin works well now that UserALE.js is packaged into a UMD > format, not iife. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-442) Update documentation for how to pass local storage, cookie data to sessionId
[ https://issues.apache.org/jira/browse/FLAGON-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-442. --- Resolution: Not A Problem Don't think we need this. Should be obvious. > Update documentation for how to pass local storage, cookie data to sessionId > > > Key: FLAGON-442 > URL: https://issues.apache.org/jira/browse/FLAGON-442 > Project: Flagon > Issue Type: Sub-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 > > > I don't think we want userale.js to mess around with passing session data > back and forth to local storage, as this global solution could open up > vulnerabilities and will be tricky to achieve desired behavior with (e.g., > all instances of the same app across tabs, have the same session_id, which is > refreshed when all instances are closed or browser is closed) as we only have > access to window properties with script tag deployment. > Better strategy is to update documentation so that users/developers can pass > their own local storage or cookie data to sessionid via the script-tag HTML > parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-479) update readme for package manager/compiler deployment options and API usage
Joshua Poore created FLAGON-479: --- Summary: update readme for package manager/compiler deployment options and API usage Key: FLAGON-479 URL: https://issues.apache.org/jira/browse/FLAGON-479 Project: Flagon Issue Type: Improvement 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 (v8.3.4#803005)
[jira] [Created] (FLAGON-478) Update index.html to provide instructions for generating certain kinds of logs
Joshua Poore created FLAGON-478: --- Summary: Update index.html to provide instructions for generating certain kinds of logs Key: FLAGON-478 URL: https://issues.apache.org/jira/browse/FLAGON-478 Project: Flagon Issue Type: Improvement 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 (v8.3.4#803005)
[jira] [Closed] (FLAGON-456) Develop npm example for including UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-456. --- > Develop npm example for including UserALE.js > > > Key: FLAGON-456 > URL: https://issues.apache.org/jira/browse/FLAGON-456 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Labels: Hacktoberfest > Fix For: UserALE.js 2.1.0 > > > OPEN TO HACKTOBER '19 PARTICIPANTS! > Currently documentation and examples only support exercising UserALE.js > directly through its API. Webpack users, however, find that userale.js code > blocks are stripped from their projects because their projects do not > directly reference exported userale functions. > Include examples and test apparatus to support using UserALE via npm/webpack. > DoD: examples for our .options, .filter, .map API functions are abstracted > for use via npm. These functions have already exposed via export, and should > be easy to abstract for npm. See: > [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] > for .options, .filter and .map API. > Ideally, for adding an npm implementation of our example test utility: > [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] > examples of npm use can also be embedded in our top-level readme as code > blocks: [https://github.com/apache/incubator-flagon-useralejs] > Thank You and find more HACKTOBER Tickets @ > https://issues.apache.org/jira/browse/FLAGON-456?jql=project%20%3D%20FLAGON%20AND%20labels%20%3D%20Hacktoberfest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-456) Develop npm example for including UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-456: Chose to make this a Webpack example to account for popularity > Develop npm example for including UserALE.js > > > Key: FLAGON-456 > URL: https://issues.apache.org/jira/browse/FLAGON-456 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Labels: Hacktoberfest > Fix For: UserALE.js 2.1.0 > > > OPEN TO HACKTOBER '19 PARTICIPANTS! > Currently documentation and examples only support exercising UserALE.js > directly through its API. Webpack users, however, find that userale.js code > blocks are stripped from their projects because their projects do not > directly reference exported userale functions. > Include examples and test apparatus to support using UserALE via npm/webpack. > DoD: examples for our .options, .filter, .map API functions are abstracted > for use via npm. These functions have already exposed via export, and should > be easy to abstract for npm. See: > [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] > for .options, .filter and .map API. > Ideally, for adding an npm implementation of our example test utility: > [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] > examples of npm use can also be embedded in our top-level readme as code > blocks: [https://github.com/apache/incubator-flagon-useralejs] > Thank You and find more HACKTOBER Tickets @ > https://issues.apache.org/jira/browse/FLAGON-456?jql=project%20%3D%20FLAGON%20AND%20labels%20%3D%20Hacktoberfest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-473) update packagefile for new version and engines
[ https://issues.apache.org/jira/browse/FLAGON-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-473. - Resolution: Fixed added 13.3 as engine > update packagefile for new version and engines > -- > > Key: FLAGON-473 > URL: https://issues.apache.org/jira/browse/FLAGON-473 > 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 (v8.3.4#803005)
[jira] [Closed] (FLAGON-475) Print Browser Types, Version
[ https://issues.apache.org/jira/browse/FLAGON-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-475. --- Resolution: Fixed > Print Browser Types, Version > > > Key: FLAGON-475 > URL: https://issues.apache.org/jira/browse/FLAGON-475 > 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 > > > Users would like to see browser and version in their logs. Good meta data and > is useful for tracing the root of user-facing issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-477) Print what tab# page is rendered in
Joshua Poore created FLAGON-477: --- Summary: Print what tab# page is rendered in Key: FLAGON-477 URL: https://issues.apache.org/jira/browse/FLAGON-477 Project: Flagon Issue Type: Wish Components: UserALE.js Affects Versions: UserALE.js 2.1.1 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.1 We get this via the browser plugin, however, that is a property of browser, which the page doesn't have access to. Will look into it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-436) Print Screen Resolution
[ https://issues.apache.org/jira/browse/FLAGON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-436: Description: Most of these are gettable via standard, exposed document/window properties. was: Most of these are gettable via standard, exposed document/window properties. Mobile device, touch screen operating system, what tabs are open. > Print Screen Resolution > --- > > Key: FLAGON-436 > URL: https://issues.apache.org/jira/browse/FLAGON-436 > Project: Flagon > Issue Type: New Feature > 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 > > > Most of these are gettable via standard, exposed document/window properties. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-475) Print Browser Types, Version
Joshua Poore created FLAGON-475: --- Summary: Print Browser Types, Version Key: FLAGON-475 URL: https://issues.apache.org/jira/browse/FLAGON-475 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 Users would like to see browser and version in their logs. Good meta data and is useful for tracing the root of user-facing issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-473) update packagefile for new version and engines
[ https://issues.apache.org/jira/browse/FLAGON-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-473: Summary: update packagefile for new version and engines (was: update packagefile for new version) > update packagefile for new version and engines > -- > > Key: FLAGON-473 > URL: https://issues.apache.org/jira/browse/FLAGON-473 > 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 (v8.3.4#803005)
[jira] [Created] (FLAGON-473) update packagefile for new version
Joshua Poore created FLAGON-473: --- Summary: update packagefile for new version Key: FLAGON-473 URL: https://issues.apache.org/jira/browse/FLAGON-473 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 (v8.3.4#803005)
[jira] [Commented] (FLAGON-472) test userale.js on node v > 13
[ https://issues.apache.org/jira/browse/FLAGON-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16996127#comment-16996127 ] Joshua Poore commented on FLAGON-472: - builds and unit tests pass w/o errors > test userale.js on node v > 13 > -- > > Key: FLAGON-472 > URL: https://issues.apache.org/jira/browse/FLAGON-472 > Project: Flagon > Issue Type: Test > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 > Environment: node.js >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > Currently testing on 12.2 and 12.7. Test on 13+ (13.3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-472) test userale.js on node v > 13
[ https://issues.apache.org/jira/browse/FLAGON-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-472. --- Resolution: Fixed builds, tests, and example server run on node 13.3 > test userale.js on node v > 13 > -- > > Key: FLAGON-472 > URL: https://issues.apache.org/jira/browse/FLAGON-472 > Project: Flagon > Issue Type: Test > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 > Environment: node.js >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > > Currently testing on 12.2 and 12.7. Test on 13+ (13.3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-472) test userale.js on node v > 13
Joshua Poore created FLAGON-472: --- Summary: test userale.js on node v > 13 Key: FLAGON-472 URL: https://issues.apache.org/jira/browse/FLAGON-472 Project: Flagon Issue Type: Test Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Environment: node.js Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 Currently testing on 12.2 and 12.7. Test on 13+ (13.3) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-468) expose PackageLog and supporting functions to aide in custom logging
[ https://issues.apache.org/jira/browse/FLAGON-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-468. --- Resolution: Fixed > expose PackageLog and supporting functions to aide in custom logging > > > Key: FLAGON-468 > URL: https://issues.apache.org/jira/browse/FLAGON-468 > 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 > > > users want to be able to pass custom logs through PackageLogs. PackageLog > will bundle HTML event logs into cannonical framework. Certain supporting > functions would be useful to expose as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-292) Browser Extension builds Intervals Differently was: Poorly Written Intervals logs
[ https://issues.apache.org/jira/browse/FLAGON-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-292: Affects Version/s: (was: UserALE.js 2.1.0) UserALE.js 2.1.1 > Browser Extension builds Intervals Differently was: Poorly Written Intervals > logs > - > > Key: FLAGON-292 > URL: https://issues.apache.org/jira/browse/FLAGON-292 > Project: Flagon > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 2.1.1 > Environment: javascript >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: UserALE.js 2.1.0 > > Original Estimate: 0.05h > Remaining Estimate: 0.05h > > We are seeing multiple interval logs written with same start, but different > end-times and counts. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-471) SetRequestHeader should include an Authorization option
[ https://issues.apache.org/jira/browse/FLAGON-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-471. - Resolution: Works for Me Could still use some additional testing with various OAUTH approaches. > SetRequestHeader should include an Authorization option > --- > > Key: FLAGON-471 > URL: https://issues.apache.org/jira/browse/FLAGON-471 > 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 > > > Coordinate with mods to config auth field -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-469) Need "meta" package function to add meta data to non HTML events
[ https://issues.apache.org/jira/browse/FLAGON-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-469. --- Resolution: Fixed tests well > Need "meta" package function to add meta data to non HTML events > > > Key: FLAGON-469 > URL: https://issues.apache.org/jira/browse/FLAGON-469 > 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 > > > For users that are custom logging non HTML events, should support with > options for adding meta data to those events in similar fashion to > PackageLogs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FLAGON-470) Expose event object in Package Log to allow users to add, extract properties to events
[ https://issues.apache.org/jira/browse/FLAGON-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-470. --- Resolution: Fixed tests well and example built > Expose event object in Package Log to allow users to add, extract properties > to events > -- > > Key: FLAGON-470 > URL: https://issues.apache.org/jira/browse/FLAGON-470 > 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 > > > Expose event object in PackageLog to allow users to add, extract properties > to events in exported PackageLog object. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-470) Expose event object in Package Log to allow users to add, extract properties to events
[ https://issues.apache.org/jira/browse/FLAGON-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976305#comment-16976305 ] Joshua Poore commented on FLAGON-470: - [~rf] Generally, you're right, Rob. Users have been asking for us to expose PackageLog as part of the larger API so that they can pass custom events through it and standardize their custom logs with raw logs. However, packageLog doesn't allow users to grab the event itself and pull attributes from it. For users that want to use packageLog along with the custom Log function, they want us to expose event so that they can extract its properties. Example: with event, they can grab e.target and other attributes like 'innerHTML'. Make sense? > Expose event object in Package Log to allow users to add, extract properties > to events > -- > > Key: FLAGON-470 > URL: https://issues.apache.org/jira/browse/FLAGON-470 > 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 > > > Expose event object in PackageLog to allow users to add, extract properties > to events in exported PackageLog object. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-470) Expose event object in Package Log to allow users to add, extract properties to events
[ https://issues.apache.org/jira/browse/FLAGON-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-470: Description: Expose event object in PackageLog to allow users to add, extract properties to events in exported PackageLog object. (was: Expose event object in Package Log to allow users to add, extract properties to events) > Expose event object in Package Log to allow users to add, extract properties > to events > -- > > Key: FLAGON-470 > URL: https://issues.apache.org/jira/browse/FLAGON-470 > 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 > > > Expose event object in PackageLog to allow users to add, extract properties > to events in exported PackageLog object. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-471) SetRequestHeader should include an Authorization option
Joshua Poore created FLAGON-471: --- Summary: SetRequestHeader should include an Authorization option Key: FLAGON-471 URL: https://issues.apache.org/jira/browse/FLAGON-471 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 Coordinate with mods to config auth field -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-470) Expose event object in Package Log to allow users to add, extract properties to events
Joshua Poore created FLAGON-470: --- Summary: Expose event object in Package Log to allow users to add, extract properties to events Key: FLAGON-470 URL: https://issues.apache.org/jira/browse/FLAGON-470 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 Expose event object in Package Log to allow users to add, extract properties to events -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-468) expose PackageLog and supporting functions to aide in custom logging
[ https://issues.apache.org/jira/browse/FLAGON-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965577#comment-16965577 ] Joshua Poore commented on FLAGON-468: - tested with updated version of example page. Still need to do more testing with "package logs + defineDetails" for customLog API usage. > expose PackageLog and supporting functions to aide in custom logging > > > Key: FLAGON-468 > URL: https://issues.apache.org/jira/browse/FLAGON-468 > 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 > > > users want to be able to pass custom logs through PackageLogs. PackageLog > will bundle HTML event logs into cannonical framework. Certain supporting > functions would be useful to expose as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-468) expose PackageLog and supporting functions to aide in custom logging
[ https://issues.apache.org/jira/browse/FLAGON-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965576#comment-16965576 ] Joshua Poore commented on FLAGON-468: - Complete list of exports are: exports.buildPath = buildPath; exports.details = defineDetails; exports.filter = setLogFilter; exports.getSelector = getSelector; exports.log = log; exports.map = setLogMapper; exports.options = options; exports.packageLog = packageLog; exports.start = start; exports.stop = stop; exports.version = version$1; > expose PackageLog and supporting functions to aide in custom logging > > > Key: FLAGON-468 > URL: https://issues.apache.org/jira/browse/FLAGON-468 > 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 > > > users want to be able to pass custom logs through PackageLogs. PackageLog > will bundle HTML event logs into cannonical framework. Certain supporting > functions would be useful to expose as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-469) Need "meta" package function to add meta data to non HTML events
Joshua Poore created FLAGON-469: --- Summary: Need "meta" package function to add meta data to non HTML events Key: FLAGON-469 URL: https://issues.apache.org/jira/browse/FLAGON-469 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 For users that are custom logging non HTML events, should support with options for adding meta data to those events in similar fashion to PackageLogs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-468) expose PackageLog and supporting functions to aide in custom logging
Joshua Poore created FLAGON-468: --- Summary: expose PackageLog and supporting functions to aide in custom logging Key: FLAGON-468 URL: https://issues.apache.org/jira/browse/FLAGON-468 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 users want to be able to pass custom logs through PackageLogs. PackageLog will bundle HTML event logs into cannonical framework. Certain supporting functions would be useful to expose as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-467) Add (custom) Log API examples
Joshua Poore created FLAGON-467: --- Summary: Add (custom) Log API examples Key: FLAGON-467 URL: https://issues.apache.org/jira/browse/FLAGON-467 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 Need examples for custom log API usage -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-457) Remove 'useraction' field from logstream
[ https://issues.apache.org/jira/browse/FLAGON-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-457. - Resolution: Not A Problem users have indicated that there are still uses for this field. > Remove 'useraction' field from logstream > > > Key: FLAGON-457 > URL: https://issues.apache.org/jira/browse/FLAGON-457 > 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 > > > Useless legacy field. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-466) Update ELK configs for v7.0+
Joshua Poore created FLAGON-466: --- Summary: Update ELK configs for v7.0+ Key: FLAGON-466 URL: https://issues.apache.org/jira/browse/FLAGON-466 Project: Flagon Issue Type: Task Components: stack Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 Configs are slightly outdated (but still support modern versions - 6.8.2). We should update these configs as we begin to support v7.0+ Good examples here: [https://github.com/deviantony/docker-elk] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-436) Print Screen Resolution, Browser Class
[ https://issues.apache.org/jira/browse/FLAGON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952256#comment-16952256 ] Joshua Poore commented on FLAGON-436: - probably want innerHeight innerWidth > Print Screen Resolution, Browser Class > -- > > Key: FLAGON-436 > URL: https://issues.apache.org/jira/browse/FLAGON-436 > Project: Flagon > Issue Type: New Feature > 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 > > > Most of these are gettable via standard, exposed document/window properties. > Mobile device, touch screen operating system, browser, what tabs are open. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FLAGON-436) Print Screen Resolution, Browser Class
[ https://issues.apache.org/jira/browse/FLAGON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952256#comment-16952256 ] Joshua Poore edited comment on FLAGON-436 at 10/15/19 8:08 PM: --- probably want innerHeight innerWidth [https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_win_innerheight] was (Author: poor...@me.com): probably want innerHeight innerWidth > Print Screen Resolution, Browser Class > -- > > Key: FLAGON-436 > URL: https://issues.apache.org/jira/browse/FLAGON-436 > Project: Flagon > Issue Type: New Feature > 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 > > > Most of these are gettable via standard, exposed document/window properties. > Mobile device, touch screen operating system, browser, what tabs are open. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLAGON-464) Figure out how to include PlotLy and Dash
Joshua Poore created FLAGON-464: --- Summary: Figure out how to include PlotLy and Dash Key: FLAGON-464 URL: https://issues.apache.org/jira/browse/FLAGON-464 Project: Flagon Issue Type: Task Components: Distill Affects Versions: Distill 0.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Distill 0.1.0 Does it get shipped through the PyPy libraries? Does it get shipped in its own module and gifted to plotly? How to abstract examples for testing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-456) Develop npm example for including UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-456: Description: OPEN TO HACKTOBER '19 PARTICIPANTS! Currently documentation and examples only support exercising UserALE.js directly through its API. Webpack users, however, find that userale.js code blocks are stripped from their projects because their projects do not directly reference exported userale functions. Include examples and test apparatus to support using UserALE via npm/webpack. DoD: examples for our .options, .filter, .map API functions are abstracted for use via npm. These functions have already exposed via export, and should be easy to abstract for npm. See: [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] for .options, .filter and .map API. Ideally, for adding an npm implementation of our example test utility: [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] examples of npm use can also be embedded in our top-level readme as code blocks: [https://github.com/apache/incubator-flagon-useralejs] Thank You and find more HACKTOBER Tickets @ https://issues.apache.org/jira/browse/FLAGON-456?jql=project%20%3D%20FLAGON%20AND%20labels%20%3D%20Hacktoberfest was: OPEN TO HACKTOBER '19 PARTICIPANTS! Currently documentation and examples only support exercising UserALE.js directly through its API. Webpack users, however, find that userale.js code blocks are stripped from their projects because their projects do not directly reference exported userale functions. Include examples and test apparatus to support using UserALE via npm/webpack. DoD: examples for our .options, .filter, .map API functions are abstracted for use via npm. These functions have already exposed via export, and should be easy to abstract for npm. See: [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] for .options, .filter and .map API. Ideally, for adding an npm implementation of our example test utility: [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] examples of npm use can also be embedded in our top-level readme as code blocks: [https://github.com/apache/incubator-flagon-useralejs] > Develop npm example for including UserALE.js > > > Key: FLAGON-456 > URL: https://issues.apache.org/jira/browse/FLAGON-456 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Labels: Hacktoberfest > Fix For: UserALE.js 2.1.0 > > > OPEN TO HACKTOBER '19 PARTICIPANTS! > Currently documentation and examples only support exercising UserALE.js > directly through its API. Webpack users, however, find that userale.js code > blocks are stripped from their projects because their projects do not > directly reference exported userale functions. > Include examples and test apparatus to support using UserALE via npm/webpack. > DoD: examples for our .options, .filter, .map API functions are abstracted > for use via npm. These functions have already exposed via export, and should > be easy to abstract for npm. See: > [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] > for .options, .filter and .map API. > Ideally, for adding an npm implementation of our example test utility: > [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] > examples of npm use can also be embedded in our top-level readme as code > blocks: [https://github.com/apache/incubator-flagon-useralejs] > Thank You and find more HACKTOBER Tickets @ > https://issues.apache.org/jira/browse/FLAGON-456?jql=project%20%3D%20FLAGON%20AND%20labels%20%3D%20Hacktoberfest -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLAGON-304) Update entire TAP Build
[
https://issues.apache.org/jira/browse/FLAGON-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16940616#comment-16940616
]
Joshua Poore commented on FLAGON-304:
-
Deferred until we DISCUSS and VOTE what to do with TAP given the maintainer is
unavailable.
> Update entire TAP Build
> ---
>
> Key: FLAGON-304
> URL: https://issues.apache.org/jira/browse/FLAGON-304
> Project: Flagon
> Issue Type: Improvement
> Components: TAP
>Affects Versions: Tap 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Arthi Vezhavendan
>Priority: Minor
> Fix For: Tap 0.2.0
>
>
> When one builds the Docker composition for TAP, there are several dire
> WARNINGS which we should definitely address
> {code}
> Step 8/19 : RUN npm install -g bower gulp
> ---> Running in 1c372060e1ec
> npm WARN deprecated bower@1.8.4: We don't recommend using Bower for new
> projects. Please consider Yarn and Webpack or Parcel. You can read how to
> migrate legacy project here:
> https://bower.io/blog/2017/how-to-migrate-away-from-bower/
> npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it,
> following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for
> compatibility with current and future versions of Node.js
> {code}
> Specifically migrating away from Bower.
> https://bower.io/blog/2017/how-to-migrate-away-from-bower/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLAGON-304) Update entire TAP Build
[
https://issues.apache.org/jira/browse/FLAGON-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated FLAGON-304:
Priority: Minor (was: Critical)
> Update entire TAP Build
> ---
>
> Key: FLAGON-304
> URL: https://issues.apache.org/jira/browse/FLAGON-304
> Project: Flagon
> Issue Type: Improvement
> Components: TAP
>Affects Versions: Tap 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Arthi Vezhavendan
>Priority: Minor
> Fix For: Tap 0.2.0
>
>
> When one builds the Docker composition for TAP, there are several dire
> WARNINGS which we should definitely address
> {code}
> Step 8/19 : RUN npm install -g bower gulp
> ---> Running in 1c372060e1ec
> npm WARN deprecated bower@1.8.4: We don't recommend using Bower for new
> projects. Please consider Yarn and Webpack or Parcel. You can read how to
> migrate legacy project here:
> https://bower.io/blog/2017/how-to-migrate-away-from-bower/
> npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it,
> following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
> npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for
> compatibility with current and future versions of Node.js
> npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or
> higher to avoid a RegExp DoS issue
> npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for
> compatibility with current and future versions of Node.js
> {code}
> Specifically migrating away from Bower.
> https://bower.io/blog/2017/how-to-migrate-away-from-bower/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLAGON-456) Develop npm example for including UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-456: Description: OPEN TO HACKTOBER '19 PARTICIPANTS! Currently documentation and examples only support exercising UserALE.js directly through its API. Webpack users, however, find that userale.js code blocks are stripped from their projects because their projects do not directly reference exported userale functions. Include examples and test apparatus to support using UserALE via npm/webpack. DoD: examples for our .options, .filter, .map API functions are abstracted for use via npm. These functions have already exposed via export, and should be easy to abstract for npm. See: [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] for .options, .filter and .map API. Ideally, for adding an npm implementation of our example test utility: [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] examples of npm use can also be embedded in our top-level readme as code blocks: [https://github.com/apache/incubator-flagon-useralejs] was: Currently documentation and examples only support exercising UserALE.js directly through its API. Webpack users, however, find that userale.js code blocks are stripped from their projects because their projects do not directly reference exported userale functions. Include examples and test apparatus to support using UserALE via npm/webpack. > Develop npm example for including UserALE.js > > > Key: FLAGON-456 > URL: https://issues.apache.org/jira/browse/FLAGON-456 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Labels: Hacktoberfest > Fix For: UserALE.js 2.1.0 > > > OPEN TO HACKTOBER '19 PARTICIPANTS! > Currently documentation and examples only support exercising UserALE.js > directly through its API. Webpack users, however, find that userale.js code > blocks are stripped from their projects because their projects do not > directly reference exported userale functions. > Include examples and test apparatus to support using UserALE via npm/webpack. > DoD: examples for our .options, .filter, .map API functions are abstracted > for use via npm. These functions have already exposed via export, and should > be easy to abstract for npm. See: > [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] > for .options, .filter and .map API. > Ideally, for adding an npm implementation of our example test utility: > [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] > examples of npm use can also be embedded in our top-level readme as code > blocks: [https://github.com/apache/incubator-flagon-useralejs] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLAGON-456) Develop npm example for including UserALE.js
[ https://issues.apache.org/jira/browse/FLAGON-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-456: Priority: Major (was: Critical) > Develop npm example for including UserALE.js > > > Key: FLAGON-456 > URL: https://issues.apache.org/jira/browse/FLAGON-456 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Labels: Hacktoberfest > Fix For: UserALE.js 2.1.0 > > > OPEN TO HACKTOBER '19 PARTICIPANTS! > Currently documentation and examples only support exercising UserALE.js > directly through its API. Webpack users, however, find that userale.js code > blocks are stripped from their projects because their projects do not > directly reference exported userale functions. > Include examples and test apparatus to support using UserALE via npm/webpack. > DoD: examples for our .options, .filter, .map API functions are abstracted > for use via npm. These functions have already exposed via export, and should > be easy to abstract for npm. See: > [https://github.com/apache/incubator-flagon-useralejs/blob/master/src/main.js] > for .options, .filter and .map API. > Ideally, for adding an npm implementation of our example test utility: > [https://github.com/apache/incubator-flagon-useralejs/tree/master/example] > examples of npm use can also be embedded in our top-level readme as code > blocks: [https://github.com/apache/incubator-flagon-useralejs] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-462) Port Over Disclaimer, Notice, and License Files to WIP PyPI project
[ https://issues.apache.org/jira/browse/FLAGON-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-462. - Resolution: Fixed > Port Over Disclaimer, Notice, and License Files to WIP PyPI project > --- > > Key: FLAGON-462 > URL: https://issues.apache.org/jira/browse/FLAGON-462 > Project: Flagon > Issue Type: Sub-task > Components: Distill >Affects Versions: Distill 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Blocker > Fix For: Distill 0.1.0 > > > Port Over Disclaimer, Notice, and License Files to WIP PyPI project -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-455) Integrate forms example into index.html
[ https://issues.apache.org/jira/browse/FLAGON-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-455. - Resolution: Fixed > Integrate forms example into index.html > --- > > Key: FLAGON-455 > URL: https://issues.apache.org/jira/browse/FLAGON-455 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 > Environment: html >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Minor > Fix For: UserALE.js 2.1.0 > > > Update index.html to include new form test features that exercise sessionId -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-434) capture what is submitted via forms
[ https://issues.apache.org/jira/browse/FLAGON-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-434. - Resolution: Fixed > capture what is submitted via forms > --- > > Key: FLAGON-434 > URL: https://issues.apache.org/jira/browse/FLAGON-434 > Project: Flagon > Issue Type: Improvement > 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 > > > We have a submit event handler, but we may not get what is submitted. > Get inner html on [https://www.w3schools.com/html/html_forms.asp] "text; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore resolved FLAGON-451.
-
Resolution: Fixed
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-task
> Components: UserALE.js
>Affects Versions: UserALE.js 2.1.0
>Reporter: Rob Foley
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 5) Userale API
> starts + stops:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Timeout._onTimeout (test/main_spec.js:75:24)
> at listOnTimeout (internal/timers.js:531:17)
> at processTimers (internal/timers.js:475:7)
> 6) Userale API
> sends custom logs:
> Uncaught TypeError: Cannot read property 'log' of undefined
> at Object.done (test/main_spec.js:93:22)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections
> (internal/process/task_queues.js:75:11){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939146#comment-16939146
]
Joshua Poore commented on FLAGON-451:
-
Rob fixed with commit 8e67a261f66a8dbaa17c1769dc4389e2a8f9
Thanks, Rob!
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-task
> Components: UserALE.js
>Affects Versions: UserALE.js 2.1.0
>Reporter: Rob Foley
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 5) Userale API
> starts + stops:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Timeout._onTimeout (test/main_spec.js:75:24)
> at listOnTimeout (internal/timers.js:531:17)
> at processTimers (internal/timers.js:475:7)
> 6) Userale API
> sends custom logs:
> Uncaught TypeError: Cannot read property 'log' of undefined
> at Object.done (test/main_spec.js:93:22)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections
> (internal/process/task_queues.js:75:11){code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (FLAGON-439) Disclaim TAP/DISTILL READMEs and WEB PAGES
[ https://issues.apache.org/jira/browse/FLAGON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-439. --- Resolution: Fixed > Disclaim TAP/DISTILL READMEs and WEB PAGES > -- > > Key: FLAGON-439 > URL: https://issues.apache.org/jira/browse/FLAGON-439 > Project: Flagon > Issue Type: Sub-task > Components: Distill, TAP >Affects Versions: Tap 0.1.0, Distill 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Tap 0.1.0, Distill 0.1.0 > > > These products are deprecated at the moment, that we should be clearer in > warning users from trying to use/download them, until we have a refactor plan. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (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 resolved FLAGON-341.
-
Resolution: Fixed
> 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.1.0
> Environment: Chrome 72
> Firefox 65
> javascript
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
> Attachments: Screen Shot 2019-07-23 at 11.26.58 PM.png,
> image-2019-07-24-20-59-18-395.png, image-2019-07-24-21-11-20-917.png
>
>
> 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
(v8.3.2#803003)
[jira] [Commented] (FLAGON-341) Web Extension Produces Duplicate Logs
[
https://issues.apache.org/jira/browse/FLAGON-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929665#comment-16929665
]
Joshua Poore commented on FLAGON-341:
-
After much experimentation, it looks like the cascade of events that results in
duplicate logs being passed to localhost:8000 is this code block in content.js
{code:java}
function injectScript(config) {
options(config);
// start(); not necessary given that autostart in place, and option is masked
from WebExt users
filter(function (log) {
queueLog(Object.assign({}, log, {
pageUrl: document.location.href,
}));
return false;
});
}{code}
> 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.1.0
> Environment: Chrome 72
> Firefox 65
> javascript
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
> Attachments: Screen Shot 2019-07-23 at 11.26.58 PM.png,
> image-2019-07-24-20-59-18-395.png, image-2019-07-24-21-11-20-917.png
>
>
> 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
(v8.3.2#803003)
[jira] [Closed] (FLAGON-454) Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0
[ https://issues.apache.org/jira/browse/FLAGON-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-454. --- Resolution: Fixed master now shows no vulnerabilities again > Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0 > > > Key: FLAGON-454 > URL: https://issues.apache.org/jira/browse/FLAGON-454 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: UserALE.js 2.1.0 > > > https://npmjs.com/advisories/1118 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (FLAGON-454) Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0
[ https://issues.apache.org/jira/browse/FLAGON-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929655#comment-16929655 ] Joshua Poore commented on FLAGON-454: - fixed via npm audit fix > Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0 > > > Key: FLAGON-454 > URL: https://issues.apache.org/jira/browse/FLAGON-454 > Project: Flagon > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: UserALE.js 2.1.0 > > > https://npmjs.com/advisories/1118 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-454) Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0
Joshua Poore created FLAGON-454: --- Summary: Update eslint-utils to remove critical vulnerability in gulp-eslint v5.0 Key: FLAGON-454 URL: https://issues.apache.org/jira/browse/FLAGON-454 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 https://npmjs.com/advisories/1118 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929013#comment-16929013
]
Joshua Poore commented on FLAGON-451:
-
Other observations:
# same error regardless if sessionStorage mock is added to 1 test or all 6
failing tests
# error message reads 'sessionStorage is undefined' if window. is stripped
from window.sessionStorage. This is likely because dom-storage isn't being
added to jsdom properly, but jsdom-global is mocking global objects like
'window' (doesn't mock session storage).
# have tried using dom-storage in both strict:true & false, to see if there is
a stringification issue in pulling key:values from storage. Doesn't seem to
affect anything (passing in strings anyway).
# have tried invoking dom-storage API to .setItem as a string integer, to rule
out possibility that time functions (to produce sessionIds) are breaking tests
in jsdom env.
Clearly, I'm just not passing the sessionStorage mock into the jsdom
environment correctly.
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 5) Userale API
> starts + stops:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Timeout._onTimeout (test/main_spec.js:75:24)
> at listOnTimeout (internal/timers.js:531:17)
> at processTimers (internal/timers.js:475:7)
> 6) Userale API
> sends custom logs:
> Uncaught TypeError: Cannot read property 'log' of undefined
> at Object.done (test/main_spec.js:93:22)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections
> (internal/process/task_queues.js:75:11){code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929009#comment-16929009
]
Joshua Poore edited comment on FLAGON-451 at 9/13/19 6:34 AM:
--
added dom-storage 2.0.2 (should be pre- jsdom 10) as dev-dependency to Mock
sessionStorage in unit tests. pushed to FLAGON-434 branch
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
added to getInitialSettings_spec.js @ 'fetches all settings from a script tag':
{code:java}
import 'jsdom-global/register'; #adds global objects like windows to jsdom
import { Storage } from 'dom-storage'; #storage mock
{code}
also added sessionStorage within test context
{code:java}
window.sessionStorage = new Storage(null, { strict: true });
{code}
was (Author: poor...@me.com):
added dom-storage 2.0.2 (should be pre- jsdom 10) as dev-dependency to Mock
sessionStorage in unit tests. pushed to FLAGON-434 branch
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
added to getInitialSettings_spec.js:
{code:java}
import 'jsdom-global/register'; #adds global objects like windows to jsdom
import { Storage } from 'dom-storage'; #storage mock
{code}
also added sessionStorage within test context
{code:java}
window.sessionStorage = new Storage(null, { strict: true });
{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 5) Userale API
> starts + stops:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Timeout._onTimeout (test/main_spec.js:75:24)
> at listOnTimeout (internal/timers.js:531:17)
> at processTimers (internal/timers.js:475:7)
> 6) Userale API
> sends custom logs:
> Uncaught TypeError: Cannot read property 'log' of undefined
> at Object.done (test/main_spec.js:93:22)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections
> (internal/process/task_queues.js:75:11){code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929011#comment-16929011
]
Joshua Poore commented on FLAGON-451:
-
Massaged how the 'getSessionId' function works, pulling it out of the
getInitialSettings context to allow for better testing.
However, still getting persistent failure on 'fetches all settings from a
script tag' test.
New error references 'getItem' of 'undefined'. Meaning, that
windows.sessionStorage still isn't working like it should.
{code:java}
TypeError: Cannot read property 'getItem' of undefined at getSessionId
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/src/getInitialSettings.js:58:40)
at Object.
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/src/getInitialSettings.js:18:17)
at Module._compile (internal/modules/cjs/loader.js:759:30) at loader
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/babel-register/lib/node.js:144:5)
at Object.require.extensions. [as .js]
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/babel-register/lib/node.js:154:7)
at Module.load (internal/modules/cjs/loader.js:628:32) at
Function.Module._load (internal/modules/cjs/loader.js:555:12) at
Module.require (internal/modules/cjs/loader.js:666:19) at require
(internal/modules/cjs/helpers.js:16:16) at Object.
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/test/getInitialSettings_spec.js:24:1)
at Module._compile (internal/modules/cjs/loader.js:759:30) at loader
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/babel-register/lib/node.js:144:5)
at Object.require.extensions. [as .js]
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/babel-register/lib/node.js:154:7)
at Module.load (internal/modules/cjs/loader.js:628:32) at
Function.Module._load (internal/modules/cjs/loader.js:555:12) at
Module.require (internal/modules/cjs/loader.js:666:19) at require
(internal/modules/cjs/helpers.js:16:16) at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/mocha/lib/mocha.js:250:27
at Array.forEach () at Mocha.loadFiles
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/mocha/lib/mocha.js:247:14)
at Mocha.run
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/mocha/lib/mocha.js:576:10)
at Object.
(/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/mocha/bin/_mocha:637:18)
at Module._compile (internal/modules/cjs/loader.js:759:30) at
Object.Module._extensions..js (internal/modules/cjs/loader.js:770:10) at
Module.load (internal/modules/cjs/loader.js:628:32) at
Function.Module._load (internal/modules/cjs/loader.js:555:12) at
Function.Module.runMain (internal/modules/cjs/loader.js:822:10) at
internal/main/run_main_module.js:17:11
{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929009#comment-16929009
]
Joshua Poore edited comment on FLAGON-451 at 9/13/19 6:23 AM:
--
added dom-storage 2.0.2 (should be pre- jsdom 10) as dev-dependency to Mock
sessionStorage in unit tests. pushed to FLAGON-434 branch
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
added to getInitialSettings_spec.js:
{code:java}
import 'jsdom-global/register'; #adds global objects like windows to jsdom
import { Storage } from 'dom-storage'; #storage mock
{code}
also added sessionStorage within test context
{code:java}
window.sessionStorage = new Storage(null, { strict: true });
{code}
was (Author: poor...@me.com):
added dom-storage 2.0.2 (should be pre- jsdom 10) as dev-dependency to Mock
sessionStorage in unit tests. pushed to FLAGON-434 branch
Again, added function to getInitialSettings ('getSessionId') works in testing
with example page, exactly as expected. But, unit tests fail
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
added to getInitialSettings_spec.js:
{code:java}
import 'jsdom-global/register'; #adds global objects like windows to jsdom
import { Storage } from 'dom-storage'; #storage mock
{code}
also added sessionStorage within test context
{code:java}
window.sessionStorage = new Storage(null, { strict: true });
{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 5) Userale API
> starts + stops:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Timeout._onTimeout (test/main_spec.js:75:24)
> at listOnTimeout (internal/timers.js:531:17)
> at processTimers (internal/timers.js:475:7)
> 6) Userale API
> sends custom logs:
> Uncaught TypeError: Cannot read property 'log' of undefined
> at Object.done (test/main_spec.js:93:22)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections
> (internal/process/task_queues.js:75:11){code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated FLAGON-451:
Description:
session storage needs to be a known object in unit tests.
exercising sessionStorage in getInitialSettings to preserve session Id at page
refresh (such as submit) performs expectedly in testing with the example page,
however breaks the following unit tests:
{code:java}
1) getInitialSettings
getInitialSettings
fetches all settings from a script tag:
Uncaught TypeError: Cannot read property 'options' of undefined
at Object.done (test/getInitialSettings_spec.js:76:39)
at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
at processTicksAndRejections (internal/process/task_queues.js:75:11)
2) getInitialSettings
getInitialSettings
grabs user id from params:
Uncaught TypeError: Cannot read property 'options' of undefined
at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
at processTicksAndRejections (internal/process/task_queues.js:75:11)
3) Userale API
provides configs:
Uncaught TypeError: Cannot read property 'options' of undefined
at Object.done (test/main_spec.js:33:37)
at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
at processTicksAndRejections (internal/process/task_queues.js:75:11)
4) Userale API
edits configs:
Uncaught TypeError: Cannot read property 'options' of undefined
at Object.done (test/main_spec.js:58:37)
at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
at processTicksAndRejections (internal/process/task_queues.js:75:11)
5) Userale API
starts + stops:
Uncaught TypeError: Cannot read property 'options' of undefined
at Timeout._onTimeout (test/main_spec.js:75:24)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)
6) Userale API
sends custom logs:
Uncaught TypeError: Cannot read property 'log' of undefined
at Object.done (test/main_spec.js:93:22)
at
/Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
at processTicksAndRejections (internal/process/task_queues.js:75:11){code}
was:session storage needs to be a known object in unit tests.
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
> exercising sessionStorage in getInitialSettings to preserve session Id at
> page refresh (such as submit) performs expectedly in testing with the example
> page, however breaks the following unit tests:
> {code:java}
> 1) getInitialSettings
> getInitialSettings
> fetches all settings from a script tag:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/getInitialSettings_spec.js:76:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 2) getInitialSettings
> getInitialSettings
> grabs user id from params:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.url [as done] (test/getInitialSettings_spec.js:95:39)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 3) Userale API
> provides configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:33:37)
> at
> /Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/node_modules/jsdom/lib/jsdom.js:325:18
> at processTicksAndRejections (internal/process/task_queues.js:75:11)
> 4) Userale API
> edits configs:
> Uncaught TypeError: Cannot read property 'options' of undefined
> at Object.done (test/main_spec.js:58:37)
> at
>
[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929009#comment-16929009
]
Joshua Poore commented on FLAGON-451:
-
added dom-storage 2.0.2 (should be pre- jsdom 10) as dev-dependency to Mock
sessionStorage in unit tests. pushed to FLAGON-434 branch
Again, added function to getInitialSettings ('getSessionId') works in testing
with example page, exactly as expected. But, unit tests fail
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
added to getInitialSettings_spec.js:
{code:java}
import 'jsdom-global/register'; #adds global objects like windows to jsdom
import { Storage } from 'dom-storage'; #storage mock
{code}
also added sessionStorage within test context
{code:java}
window.sessionStorage = new Storage(null, { strict: true });
{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Closed] (FLAGON-435) track usage across multi-tab applications via script tag was: TabID to attach handlers
[ https://issues.apache.org/jira/browse/FLAGON-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-435. --- Resolution: Duplicate sessionStorage + examples for how to pass local storage variables to sessionId resolves this issue. > track usage across multi-tab applications via script tag was: TabID to attach > handlers > -- > > Key: FLAGON-435 > URL: https://issues.apache.org/jira/browse/FLAGON-435 > Project: Flagon > Issue Type: New Feature > 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 > > > By design some apps want to spawn tabs for additional views. Using script > tags, this would create a new session id in each tab at page load. How to > preserve session attribution across multi-tab applications via script-tag > method of deployment? -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203
]
Joshua Poore edited comment on FLAGON-451 at 9/12/19 5:08 AM:
--
[~rf]
One likely cause for unit test failure owing to sessionStorage reference in
getInitialSettings is that jsdom v9 has no concept of sessionStorage.
v12 does; previous versions v10,11 have used mocks or 3rd party libraries.
[https://stackoverflow.com/questions/51569521/jsdom-11-12-0-how-to-mock-localstorage]
I have tried to use one option:
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
This seems simple and is well used, however, I haven't had success with it.
Given how we call jsdom.env via createEnv (testUtils), I just cant figure out
where to inject a mocked sessionStorage variable.
Another option is to update our unit tests for jsdom v12. This is sensible, as
we're now 3 major versions behind. However, this is also tricky given that
jsdom now uses a constructor and new resource loading options.
I have made an attempt, but am stuck on how to pull in our resource loader.
jsdom has a new customizable resource loader, but it doesnt seem to have the
options we need:
[https://github.com/jsdom/jsdom#loading-subresources]
Here is an example of some my experiments (not pushed):
Old createEnv:
{code:java}
export function createEnv(html, doneCallback, extraConfig) {
let extra = (typeof extraConfig === 'undefined') ? {} : extraConfig;
return jsdom.env(Object.assign({}, {
html : html,
url : 'http://localhost:8080',
features : {
FetchExternalResources : ['script'],
ProcessExternalResources : ['script']
},
resourceLoader,
done : doneCallback,
}, extraConfig));
}
{code}
w/ new jsdom constructor:
{code:java}
...
return JSDOM.fromFile(html, options)
.then(function (dom) {
let window = dom.window,
document = window.document,
sessionStorage = window.sessionStorage;
});
}
const jsdomOptions = {
url: "http://localhost:8080;,
runScripts: 'dangerously',
resources: "usable"
};{code}
was (Author: poor...@me.com):
[~rf]
One likely cause for unit test failure owing to sessionStorage reference in
getInitialSettings is that jsdom v9 has no concept of sessionStorage.
v12 does; previous versions v10,11 have used mocks or 3rd party libraries.
[https://stackoverflow.com/questions/51569521/jsdom-11-12-0-how-to-mock-localstorage]
I have tried to use one option:
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
This seems simple and is well used, however, I haven't had success with it.
Given how we call jsdom.env via createEnv (testUtils), I just cant figure out
where to inject a mocked sessionStorage variable.
Another option is to update our unit tests for jsdom v12. This is sensible, as
we're now 3 major versions behind. However, this is also tricky given that
jsdom now uses a constructor and new resource loading options.
I have made an attempt, but am stuck on how to pull in our resource loader.
jsdom has a new customizable resource loader, but it doesnt seem to have the
options we need:
[https://github.com/jsdom/jsdom#loading-subresources]
Here is an example of some my experiments (not pushed):
Old createEnv:
{code:java}
export function createEnv(html, doneCallback, extraConfig) {
let extra = (typeof extraConfig === 'undefined') ? {} : extraConfig;
return jsdom.env(Object.assign({}, {
html : html,
url : 'http://localhost:8080',
features : {
FetchExternalResources : ['script'],
ProcessExternalResources : ['script'] },
resourceLoader,
done : doneCallback, },
extraConfig));
{code}
w/ new jsdom constructor:
{code:java}
...
return JSDOM.fromFile(html, options)
.then(function (dom) {
let window = dom.window,
document = window.document,
sessionStorage = window.sessionStorage;
});
}
const jsdomOptions = {
url: "http://localhost:8080;,
runScripts: 'dangerously',
resources: "usable"
};{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Comment Edited] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203
]
Joshua Poore edited comment on FLAGON-451 at 9/12/19 5:07 AM:
--
[~rf]
One likely cause for unit test failure owing to sessionStorage reference in
getInitialSettings is that jsdom v9 has no concept of sessionStorage.
v12 does; previous versions v10,11 have used mocks or 3rd party libraries.
[https://stackoverflow.com/questions/51569521/jsdom-11-12-0-how-to-mock-localstorage]
I have tried to use one option:
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
This seems simple and is well used, however, I haven't had success with it.
Given how we call jsdom.env via createEnv (testUtils), I just cant figure out
where to inject a mocked sessionStorage variable.
Another option is to update our unit tests for jsdom v12. This is sensible, as
we're now 3 major versions behind. However, this is also tricky given that
jsdom now uses a constructor and new resource loading options.
I have made an attempt, but am stuck on how to pull in our resource loader.
jsdom has a new customizable resource loader, but it doesnt seem to have the
options we need:
[https://github.com/jsdom/jsdom#loading-subresources]
Here is an example of some my experiments (not pushed):
Old createEnv:
{code:java}
export function createEnv(html, doneCallback, extraConfig) {
let extra = (typeof extraConfig === 'undefined') ? {} : extraConfig;
return jsdom.env(Object.assign({}, {
html : html,
url : 'http://localhost:8080',
features : {
FetchExternalResources : ['script'],
ProcessExternalResources : ['script'] },
resourceLoader,
done : doneCallback, },
extraConfig));
{code}
w/ new jsdom constructor:
{code:java}
...
return JSDOM.fromFile(html, options)
.then(function (dom) {
let window = dom.window,
document = window.document,
sessionStorage = window.sessionStorage;
});
}
const jsdomOptions = {
url: "http://localhost:8080;,
runScripts: 'dangerously',
resources: "usable"
};{code}
was (Author: poor...@me.com):
One likely cause for unit test failure owing to sessionStorage reference in
getInitialSettings is that jsdom v9 has no concept of sessionStorage.
v12 does; previous versions v10,11 have used mocks or 3rd party libraries.
[https://stackoverflow.com/questions/51569521/jsdom-11-12-0-how-to-mock-localstorage]
I have tried to use one option:
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
This seems simple and is well used, however, I haven't had success with it.
Given how we call jsdom.env via createEnv (testUtils), I just cant figure out
where to inject a mocked sessionStorage variable.
Another option is to update our unit tests for jsdom v12. This is sensible, as
we're now 3 major versions behind. However, this is also tricky given that
jsdom now uses a constructor and new resource loading options.
I have made an attempt, but am stuck on how to pull in our resource loader.
jsdom has a new customizable resource loader, but it doesnt seem to have the
options we need:
[https://github.com/jsdom/jsdom#loading-subresources]
Here is an example of some my experiments (not pushed):
Old createEnv:
{code:java}
export function createEnv(html, doneCallback, extraConfig) {
let extra = (typeof extraConfig === 'undefined') ? {} : extraConfig;
return jsdom.env(Object.assign({}, {
html : html,
url : 'http://localhost:8080',
features : {
FetchExternalResources : ['script'],
ProcessExternalResources : ['script'] },
resourceLoader,
done : doneCallback, },
extraConfig));
{code}
w/ new jsdom constructor:
{code:java}
...
return JSDOM.fromFile(html, options)
.then(function (dom) {
let window = dom.window,
document = window.document,
sessionStorage = window.sessionStorage;
});
}
const jsdomOptions = {
url: "http://localhost:8080;,
runScripts: 'dangerously',
resources: "usable"
};{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (FLAGON-451) Update unit tests to accommodate session storage features
[
https://issues.apache.org/jira/browse/FLAGON-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928203#comment-16928203
]
Joshua Poore commented on FLAGON-451:
-
One likely cause for unit test failure owing to sessionStorage reference in
getInitialSettings is that jsdom v9 has no concept of sessionStorage.
v12 does; previous versions v10,11 have used mocks or 3rd party libraries.
[https://stackoverflow.com/questions/51569521/jsdom-11-12-0-how-to-mock-localstorage]
I have tried to use one option:
[https://www.npmjs.com/package/dom-storage/v/2.0.2]
This seems simple and is well used, however, I haven't had success with it.
Given how we call jsdom.env via createEnv (testUtils), I just cant figure out
where to inject a mocked sessionStorage variable.
Another option is to update our unit tests for jsdom v12. This is sensible, as
we're now 3 major versions behind. However, this is also tricky given that
jsdom now uses a constructor and new resource loading options.
I have made an attempt, but am stuck on how to pull in our resource loader.
jsdom has a new customizable resource loader, but it doesnt seem to have the
options we need:
[https://github.com/jsdom/jsdom#loading-subresources]
Here is an example of some my experiments (not pushed):
Old createEnv:
{code:java}
export function createEnv(html, doneCallback, extraConfig) {
let extra = (typeof extraConfig === 'undefined') ? {} : extraConfig;
return jsdom.env(Object.assign({}, {
html : html,
url : 'http://localhost:8080',
features : {
FetchExternalResources : ['script'],
ProcessExternalResources : ['script'] },
resourceLoader,
done : doneCallback, },
extraConfig));
{code}
w/ new jsdom constructor:
{code:java}
...
return JSDOM.fromFile(html, options)
.then(function (dom) {
let window = dom.window,
document = window.document,
sessionStorage = window.sessionStorage;
});
}
const jsdomOptions = {
url: "http://localhost:8080;,
runScripts: 'dangerously',
resources: "usable"
};{code}
> Update unit tests to accommodate session storage features
> -
>
> Key: FLAGON-451
> URL: https://issues.apache.org/jira/browse/FLAGON-451
> Project: Flagon
> Issue Type: Sub-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
>
>
> session storage needs to be a known object in unit tests.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (FLAGON-441) utilize sessionStorage for sessionId so that sessionId isn't cleared until the tab is closed.
[ https://issues.apache.org/jira/browse/FLAGON-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928196#comment-16928196 ] Joshua Poore commented on FLAGON-441: - moving conversation to https://issues.apache.org/jira/browse/FLAGON-451 > utilize sessionStorage for sessionId so that sessionId isn't cleared until > the tab is closed. > - > > Key: FLAGON-441 > URL: https://issues.apache.org/jira/browse/FLAGON-441 > Project: Flagon > Issue Type: Sub-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 > > > we can build sessionId the same way as we do, but it needs to be passed to, > checked for, and ingested from sessionId to keep sessionId from regenerating > on refresh (incl. submit). -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (FLAGON-436) Print Screen Resolution, Browser Class
[ https://issues.apache.org/jira/browse/FLAGON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated FLAGON-436: Description: Most of these are gettable via standard, exposed document/window properties. Mobile device, touch screen operating system, browser, what tabs are open. was:Most of these are gettable via standard, exposed document/window properties. > Print Screen Resolution, Browser Class > -- > > Key: FLAGON-436 > URL: https://issues.apache.org/jira/browse/FLAGON-436 > Project: Flagon > Issue Type: New Feature > 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 > > > Most of these are gettable via standard, exposed document/window properties. > Mobile device, touch screen operating system, browser, what tabs are open. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-451) Update unit tests to accommodate session storage features
Joshua Poore created FLAGON-451: --- Summary: Update unit tests to accommodate session storage features Key: FLAGON-451 URL: https://issues.apache.org/jira/browse/FLAGON-451 Project: Flagon Issue Type: Sub-task Components: UserALE.js Affects Versions: UserALE.js 2.1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: UserALE.js 2.1.0 session storage needs to be a known object in unit tests. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (FLAGON-444) Update UserALE.js API docs to include options example
[ https://issues.apache.org/jira/browse/FLAGON-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-444. - Resolution: Fixed > Update UserALE.js API docs to include options example > - > > Key: FLAGON-444 > URL: https://issues.apache.org/jira/browse/FLAGON-444 > Project: Flagon > Issue Type: Improvement > Components: website >Affects Versions: Website 0.1 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: Website 0.1 > > > Update UserALE.js API docs to include options example -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (FLAGON-443) Add Options API Example to UserALE.js Example
[ https://issues.apache.org/jira/browse/FLAGON-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore resolved FLAGON-443. - Resolution: Fixed > Add Options API Example to UserALE.js Example > - > > Key: FLAGON-443 > URL: https://issues.apache.org/jira/browse/FLAGON-443 > Project: Flagon > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 2.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Trivial > Fix For: UserALE.js 2.1.0 > > > Add Options API Example to UserALE.js Example -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-448) fix broken dev-subscribe links
Joshua Poore created FLAGON-448: --- Summary: fix broken dev-subscribe links Key: FLAGON-448 URL: https://issues.apache.org/jira/browse/FLAGON-448 Project: Flagon Issue Type: Task Components: website Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 fix broken dev-subscribe links -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-447) Add UserALE.js options API documentation
Joshua Poore created FLAGON-447: --- Summary: Add UserALE.js options API documentation Key: FLAGON-447 URL: https://issues.apache.org/jira/browse/FLAGON-447 Project: Flagon Issue Type: Task Components: website Affects Versions: Flagon 1.0 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 Add UserALE.js options API documentation -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-445) Update MakeReleaseArtifact Script to Include Disclaimer in .bin files
Joshua Poore created FLAGON-445: --- Summary: Update MakeReleaseArtifact Script to Include Disclaimer in .bin files Key: FLAGON-445 URL: https://issues.apache.org/jira/browse/FLAGON-445 Project: Flagon Issue Type: Task Components: release_scripts Affects Versions: Flagon 1.0 Environment: bash Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Flagon 1.0 Update MakeReleaseArtifact Script to Include Disclaimer in .bin files -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (FLAGON-421) Add Disclaimer to Flagon Repo
[ https://issues.apache.org/jira/browse/FLAGON-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-421. --- Resolution: Fixed > Add Disclaimer to Flagon Repo > - > > Key: FLAGON-421 > URL: https://issues.apache.org/jira/browse/FLAGON-421 > Project: Flagon > Issue Type: Task > Components: repository, website >Affects Versions: Website 0.1, Flagon 1.0, Tap 0.1.0, Distill 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Website 0.1, Flagon 1.0, Tap 0.1.0, Distill 0.1.0 > > > Disclaimer was missing. Add recently updated from UserALE.js -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Closed] (FLAGON-416) Update License file to correct issue with Appendix
[ https://issues.apache.org/jira/browse/FLAGON-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore closed FLAGON-416. --- Resolution: Fixed > Update License file to correct issue with Appendix > -- > > Key: FLAGON-416 > URL: https://issues.apache.org/jira/browse/FLAGON-416 > Project: Flagon > Issue Type: Task > Components: builds, Distill, STOUT, TAP, UserALE.js >Affects Versions: Flagon 1.0, Tap 0.1.0, Distill 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > Fix For: Flagon 1.0, Tap 0.1.0, Distill 0.1.0 > > > Update License file to correct issue with Appendix -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLAGON-444) Update UserALE.js API docs to include options example
Joshua Poore created FLAGON-444: --- Summary: Update UserALE.js API docs to include options example Key: FLAGON-444 URL: https://issues.apache.org/jira/browse/FLAGON-444 Project: Flagon Issue Type: Improvement Components: website Affects Versions: Website 0.1 Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Website 0.1 Update UserALE.js API docs to include options example -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (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 updated FLAGON-386: Fix Version/s: (was: UserALE.js 2.1.0) > 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 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (FLAGON-440) create sendOnRefresh function in sendlog
[
https://issues.apache.org/jira/browse/FLAGON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904125#comment-16904125
]
Joshua Poore commented on FLAGON-440:
-
Solution seems to test well:
Produced modified index.html (index_form.html) to test out behavior. (see in
/example)
we now capture all submit behavior:
{"target":"button","path":["{color:#FF}button","form#test_text_input","body","html","#document","Window"{color}],"pageUrl":"file:///Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/example/index_form.html?","pageTitle":"UserAleJS
- Example
Page","pageReferrer":"","clientTime":1565372541295,"microTime":0.02,"location":\{"x":0,"y":0},"type":"{color:#FF}click"{color},"logType":"raw","userAction":true,"details":\{"clicks":0,"ctrl":false,"alt":false,"shift":false,"meta":false},"userId":"example-user","toolVersion":"2.0.2","toolName":"Apache
UserALE.js
Example","useraleVersion":"2.0.2","sessionID":"session_1565372376875"},
{"target":"form#test_text_input","path":["{color:#FF}form#test_text_input"{color},"body","html","#document","Window"],"pageUrl":"file:///Users/jpoore/Documents/Apache_Flagon/test/incubator-flagon-useralejs/example/index_form.html?","pageTitle":"UserAleJS
- Example
Page","pageReferrer":"","clientTime":1565372541295,"microTime":0.59,"location":\{"x":null,"y":null},"type":"{color:#FF}submit"{color},"logType":"raw","userAction":true,"details":null,"userId":"example-user","toolVersion":"2.0.2","toolName":"Apache
UserALE.js
Example","useraleVersion":"2.0.2","sessionID":"session_1565372376875"},
> create sendOnRefresh function in sendlog
>
>
> Key: FLAGON-440
> URL: https://issues.apache.org/jira/browse/FLAGON-440
> Project: Flagon
> Issue Type: Sub-task
> Components: UserALE.js
>Affects Versions: UserALE.js 2.1.0
> Environment: java script
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
>
> In order to capture events that cascade and ultimately trigger page
> refreshes, we need a function to wrap up sendLogs.
> This function needs to be included in the listening function of the event
> handler for classes of events that initiate refreshes
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (FLAGON-440) create sendOnRefresh function in sendlog
[
https://issues.apache.org/jira/browse/FLAGON-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16904121#comment-16904121
]
Joshua Poore commented on FLAGON-440:
-
Broke out 'submit' events into its own category, similar to bufferedEvents, in
attachHandlers src:
bufferedEvents = {
'wheel' : function(e) \{ return { 'x' : e.deltaX, 'y' : e.deltaY, 'z' :
e.deltaZ }; },
'scroll' : function() \{ return { 'x' : window.scrollX, 'y' : window.scrollY
}; },
'resize' : function() \{ return { 'width' : window.outerWidth, 'height' :
window.outerHeight }; }
};
refreshEvents = {
'submit' : null
};
}
> create sendOnRefresh function in sendlog
>
>
> Key: FLAGON-440
> URL: https://issues.apache.org/jira/browse/FLAGON-440
> Project: Flagon
> Issue Type: Sub-task
> Components: UserALE.js
>Affects Versions: UserALE.js 2.1.0
> Environment: java script
>Reporter: Joshua Poore
>Assignee: Joshua Poore
>Priority: Major
> Fix For: UserALE.js 2.1.0
>
>
> In order to capture events that cascade and ultimately trigger page
> refreshes, we need a function to wrap up sendLogs.
> This function needs to be included in the listening function of the event
> handler for classes of events that initiate refreshes
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
