You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flagon.apache.org by Joshua Poore <po...@apache.org> on 2019/08/02 01:08:31 UTC

Potential Issue with UserALE.js example server

Hi Furkan,

Let’s walk through this and see if there’s a problem that we need a ticket for.


> On the other hand, I've tried to run example but could not see the event
> logs at terminal. Accessing to a file is blocked by browsers and could not
> load userale js.

I’m running current versions of Chrome and Firefox. Just tested logging with useralejs-2.0.1.min.js in our example page with our example server, and things worked just fine on my end. Generally, script-tags are widely used and not blocked. In fact, Mozilla offers quite a lot of support, including documentation on nonces and hashing to make using script tags safer and more adoptable. But, if its not working in your environment, then walking through this with you will be extremely helpful for finding a remedy!

Can you tell me a bit about your environment?

1. Browser & version
2. any privacy/security settings you have active in your browser
3. nodejs version (note that I did find a few minor issues with the example server on node 12.7.0/which is why I walked back our package file to cover 12.2.0. I found some nasty ELIFECYCLE (version) errors with npm RE nodemon when I killed the server) https://issues.apache.org/jira/browse/FLAGON-431 <https://issues.apache.org/jira/browse/FLAGON-431>


> This issue maybe related with this (
> https://issues.apache.org/jira/browse/FLAGON-169)

This was a mixed-media issue related to our browser plugin (WebExtension), not the script tag. 

Can you walk me through the steps you used to deploy?

1. Did you modify example/index.html to reflect your path to useralejs-2.0.1.min.js or did you build your own script tag in your own website? If the latter, which settings did you use in your HTML5 params
2. Did you try reloading you page when you didn’t receive any logs?
3. Did you see any browser console messages that indicated a POST error or anything else?
4. Did you have any other applications utilizing port:8000?

> but I couldn't find any
> information at here (
> https://github.com/apache/incubator-flagon-useralejs/tree/2.0.1-RC1-07_30_2019/example)
> It can be included both how to fetch userale js from local file and serve
> it via nodejs server to access it.

I can work on documentation to better flesh out the step by step instructions. Hearing the steps you went through will help me figure out the best way to improve documentation.

> 
> Kind Regards,
> Furkan KAMACI

thanks, Furkan, for diving into things. I look forward to working with you on Flagon! 

> 
> On Thu, Aug 1, 2019 at 11:01 PM Dave Meikle <dm...@apache.org> wrote:
> 
>> Hello,
>> 
>> On Wed, 31 Jul 2019 at 03:46, Joshua Poore <po...@apache.org> wrote:
>> 
>>> Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate #
>> 1.
>>> 
>>> Vote will be open for 72 hours. Please VOTE as follows:
>>> 
>>> [ ] +1, let's get it released!!!
>>> [ ] +/-0, fine, but consider to fix few issues before...
>>> [ ] -1, nope, because... (and please explain why)
>>> 
>> 
>> +1 - signatures, hashes, NOTICE and LICENSE, incubating in name, builds on
>> Ubuntu 19.04 with Node 12.7.0
>> 
>> Cheers,
>> Dave
>>