Re: Violations Plugin and JSlint

[Michael Kusmiy]

Following custom build of Violations plugin (to fix similar issue with 
FxCop reports) resolved issue for me:
https://issues.jenkins-ci.org/browse/JENKINS-17548

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Violations Plugin and JSlint

[Ulli Hafner]

Ok, I see. 

Is it an option to switch to the checkstyle plug-in and see if it renders your 
results correctly?

Ulli
 
Am 17.01.2013 um 22:55 schrieb TeMc :

> I use:
> * jshint (not jslint)
> * the --checkstyle-reporter it features
> * written to an xml file
> * read by publisher "Violations" in the Jenkins job as type "checkstyle"
> 
> -- Tem
> 
> 
> On Jan 17, 2013, at 11:20 AM, Ulli Hafner  wrote:
> 
>> Just to make sure that we are talking about the same plug-ins:
>> Are you using the jslint and checkstyle plug-in? Or are you using the 
>> violations plug-in?
>> 
>> My comments make only sense if you use the jslint plugin and then the 
>> checkstyle plugin;-)
>> 
>> Ulli
>> 
>> Am 17.01.2013 um 02:49 schrieb TeMc :
>> 
>>> 
>>> On Jan 16, 2013, at 6:31 PM, Ulli Hafner  wrote:
>>> 
 
> Why does the Checkstyle page viewer need the full paths? All it needs to 
> do is output the given file name (regardless of whether it exists or not) 
> and the warnings/errors for those files.
> 
> If it wants to use the paths to display samples of the code, how does 
> that work for old builds? Files could have been moved by then, or Jenkins 
> might be installed in a different location etc. Unless it caches the 
> samples during the build this doesn't scale very well.
> 
 
 The checkstyle plug-in creates a copy for each file that contains a 
 warning. If the file does not exist, then you just can't navigate to the 
 source code - the rest of the plug-in should work without any problems…
 
 Ulli
>>> 
>>> I don't care much about navigating the source code.
>>> 
>>> All I want is to see the warnings that jshint outputted in the Checkstyle 
>>> XML file given to Jenkins via Violations.
>>> 
>>> Right now all I see isa number and a couple of files with broken links. I 
>>> can't read the actual warnings (which is the whole point, otherwise I can 
>>> just have the output go to the console output and read the xml directly, 
>>> I'm using this plugin to visualise the data).
>>> 
>>> I don't need it to do any fancy fetching of the files themselves, just read 
>>> the xml file and show each message for each file name.
>>> 
>>> It shouldn't fall flat on its face just because it doesn't know how to 
>>> resolve the file name. Checkstyle reports don't need to have absolute or 
>>> (currently) existing file paths. All the information is right there in the 
>>> xml file.
>>> 
>>> -- Tem
>>> 
>> 
> 

Re: Violations Plugin and JSlint

[TeMc]

I use:
* jshint (not jslint)
* the --checkstyle-reporter it features
* written to an xml file
* read by publisher "Violations" in the Jenkins job as type "checkstyle"

-- Tem


On Jan 17, 2013, at 11:20 AM, Ulli Hafner  wrote:

> Just to make sure that we are talking about the same plug-ins:
> Are you using the jslint and checkstyle plug-in? Or are you using the 
> violations plug-in?
> 
> My comments make only sense if you use the jslint plugin and then the 
> checkstyle plugin;-)
> 
> Ulli
> 
> Am 17.01.2013 um 02:49 schrieb TeMc :
> 
>> 
>> On Jan 16, 2013, at 6:31 PM, Ulli Hafner  wrote:
>> 
>>> 
 Why does the Checkstyle page viewer need the full paths? All it needs to 
 do is output the given file name (regardless of whether it exists or not) 
 and the warnings/errors for those files.
 
 If it wants to use the paths to display samples of the code, how does that 
 work for old builds? Files could have been moved by then, or Jenkins might 
 be installed in a different location etc. Unless it caches the samples 
 during the build this doesn't scale very well.
 
>>> 
>>> The checkstyle plug-in creates a copy for each file that contains a 
>>> warning. If the file does not exist, then you just can't navigate to the 
>>> source code - the rest of the plug-in should work without any problems…
>>> 
>>> Ulli
>> 
>> I don't care much about navigating the source code.
>> 
>> All I want is to see the warnings that jshint outputted in the Checkstyle 
>> XML file given to Jenkins via Violations.
>> 
>> Right now all I see isa number and a couple of files with broken links. I 
>> can't read the actual warnings (which is the whole point, otherwise I can 
>> just have the output go to the console output and read the xml directly, I'm 
>> using this plugin to visualise the data).
>> 
>> I don't need it to do any fancy fetching of the files themselves, just read 
>> the xml file and show each message for each file name.
>> 
>> It shouldn't fall flat on its face just because it doesn't know how to 
>> resolve the file name. Checkstyle reports don't need to have absolute or 
>> (currently) existing file paths. All the information is right there in the 
>> xml file.
>> 
>> -- Tem
>> 
> 

Re: Violations Plugin and JSlint

[Ulli Hafner]

Just to make sure that we are talking about the same plug-ins:
Are you using the jslint and checkstyle plug-in? Or are you using the 
violations plug-in?

My comments make only sense if you use the jslint plugin and then the 
checkstyle plugin;-)

Ulli

Am 17.01.2013 um 02:49 schrieb TeMc :

> 
> On Jan 16, 2013, at 6:31 PM, Ulli Hafner  wrote:
> 
>> 
>>> Why does the Checkstyle page viewer need the full paths? All it needs to do 
>>> is output the given file name (regardless of whether it exists or not) and 
>>> the warnings/errors for those files.
>>> 
>>> If it wants to use the paths to display samples of the code, how does that 
>>> work for old builds? Files could have been moved by then, or Jenkins might 
>>> be installed in a different location etc. Unless it caches the samples 
>>> during the build this doesn't scale very well.
>>> 
>> 
>> The checkstyle plug-in creates a copy for each file that contains a warning. 
>> If the file does not exist, then you just can't navigate to the source code 
>> - the rest of the plug-in should work without any problems…
>> 
>> Ulli
> 
> I don't care much about navigating the source code.
> 
> All I want is to see the warnings that jshint outputted in the Checkstyle XML 
> file given to Jenkins via Violations.
> 
> Right now all I see isa number and a couple of files with broken links. I 
> can't read the actual warnings (which is the whole point, otherwise I can 
> just have the output go to the console output and read the xml directly, I'm 
> using this plugin to visualise the data).
> 
> I don't need it to do any fancy fetching of the files themselves, just read 
> the xml file and show each message for each file name.
> 
> It shouldn't fall flat on its face just because it doesn't know how to 
> resolve the file name. Checkstyle reports don't need to have absolute or 
> (currently) existing file paths. All the information is right there in the 
> xml file.
> 
> -- Tem
> 

Re: Violations Plugin and JSlint

[TeMc]

On Jan 16, 2013, at 6:31 PM, Ulli Hafner  wrote:

> 
>> Why does the Checkstyle page viewer need the full paths? All it needs to do 
>> is output the given file name (regardless of whether it exists or not) and 
>> the warnings/errors for those files.
>> 
>> If it wants to use the paths to display samples of the code, how does that 
>> work for old builds? Files could have been moved by then, or Jenkins might 
>> be installed in a different location etc. Unless it caches the samples 
>> during the build this doesn't scale very well.
>> 
> 
> The checkstyle plug-in creates a copy for each file that contains a warning. 
> If the file does not exist, then you just can't navigate to the source code - 
> the rest of the plug-in should work without any problems…
> 
> Ulli

I don't care much about navigating the source code.

All I want is to see the warnings that jshint outputted in the Checkstyle XML 
file given to Jenkins via Violations.

Right now all I see isa number and a couple of files with broken links. I can't 
read the actual warnings (which is the whole point, otherwise I can just have 
the output go to the console output and read the xml directly, I'm using this 
plugin to visualise the data).

I don't need it to do any fancy fetching of the files themselves, just read the 
xml file and show each message for each file name.

It shouldn't fall flat on its face just because it doesn't know how to resolve 
the file name. Checkstyle reports don't need to have absolute or (currently) 
existing file paths. All the information is right there in the xml file.

-- Tem

Re: Violations Plugin and JSlint

[Ulli Hafner]

> Why does the Checkstyle page viewer need the full paths? All it needs to do 
> is output the given file name (regardless of whether it exists or not) and 
> the warnings/errors for those files.
> 
> If it wants to use the paths to display samples of the code, how does that 
> work for old builds? Files could have been moved by then, or Jenkins might be 
> installed in a different location etc. Unless it caches the samples during 
> the build this doesn't scale very well.
> 

The checkstyle plug-in creates a copy for each file that contains a warning. If 
the file does not exist, then you just can't navigate to the source code - the 
rest of the plug-in should work without any problems…

Ulli

> And besides, when looking at the build page in Jenkins I don't want to see 
> "/var/lib/jenkins/jobs/Job-Name/workspace" in front of it, just the relevant 
> path names for the project.
> 
> -- Tem Corner
> 
> On Monday, November 5, 2012 4:50:27 PM UTC+1, Bertrand Tornil wrote:
> Hi
> 
> I have something working, here :
> 
> In the generated jshint.xml file, the full path is missing into the "name" 
> attribute of each tag  .
> 
> For instance : 
> 
> 
> 
>   
>   
> ...
> 
> You need to add the full path : in my case something like
> 
> 
> 
>   
>   
> 
> 
> I was able to fix it with a sed oneliner :
> 
> sed -E 's???' jshint.xml > 
> jshint-proper.xml
> 
> 
> Then adapt your job configuration to use the jshint-proper file instead of 
> the jshint.xml
> 
> 
> Hope it will help, 
> 
> B.
> 
> 
> 
> Le vendredi 3 février 2012 18:33:58 UTC+1, Bob Koertge a écrit :
> I cannot seem to get detailed infomration on my errors with JSLint and 
> violations.  Here is some screenshots 
> http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but clicking 
> any of the .js file links leads to a blank page! 
> http://screencast.com/t/LHM09UYw9ruf
> 
> Anyone have any ideas?

Re: Violations Plugin and JSlint

[TeMc]

Why does the Checkstyle page viewer need the full paths? All it needs to do 
is output the given file name (regardless of whether it exists or not) and 
the warnings/errors for those files.

If it wants to use the paths to display samples of the code, how does that 
work for old builds? Files could have been moved by then, or Jenkins might 
be installed in a different location etc. Unless it caches the samples 
during the build this doesn't scale very well.

And besides, when looking at the build page in Jenkins I don't want to see 
"/var/lib/jenkins/jobs/Job-Name/workspace" in front of it, just the 
relevant path names for the project.

-- Tem Corner

On Monday, November 5, 2012 4:50:27 PM UTC+1, Bertrand Tornil wrote:
>
> Hi
>
> I have something working, here :
>
> In the generated jshint.xml file, the full path is missing into the "name" 
> attribute of each tag  .
>
> For instance : 
>
> 
> 
> 
> 
> ...
>
> You need to add the full path : in my case something like
>
> 
> 
> 
> 
>
>
> I was able to fix it with a sed oneliner :
>
> sed -E 's???' jshint.xml > 
> jshint-proper.xml
>
>
> Then adapt your job configuration to use the jshint-proper file instead of 
> the jshint.xml
>
>
> Hope it will help, 
>
> B.
>
>
>
> Le vendredi 3 février 2012 18:33:58 UTC+1, Bob Koertge a écrit :
>>
>> I cannot seem to get detailed infomration on my errors with JSLint and 
>> violations.  Here is some screenshots 
>> http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but 
>> clicking any of the .js file links leads to a blank page! 
>> http://screencast.com/t/LHM09UYw9ruf
>>
>> Anyone have any ideas?
>>
>

Re: Violations Plugin and JSlint

[Bertrand Tornil]

Hi

I have something working, here :

In the generated jshint.xml file, the full path is missing into the "name" 
attribute of each tag  .

For instance : 





...

You need to add the full path : in my case something like







I was able to fix it with a sed oneliner :

sed -E 's???' jshint.xml > 
jshint-proper.xml


Then adapt your job configuration to use the jshint-proper file instead of 
the jshint.xml


Hope it will help, 

B.



Le vendredi 3 février 2012 18:33:58 UTC+1, Bob Koertge a écrit :
>
> I cannot seem to get detailed infomration on my errors with JSLint and 
> violations.  Here is some screenshots 
> http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but 
> clicking any of the .js file links leads to a blank page! 
> http://screencast.com/t/LHM09UYw9ruf
>
> Anyone have any ideas?
>

Re: Violations Plugin and JSlint

[Jonathan Hartley]

On Tuesday, May 1, 2012 4:04:25 AM UTC+1, djcbecroft wrote:
>
> On Tue, May 1, 2012 at 12:17 PM, Daniel Becroft wrote:
>
>> On Mon, Apr 30, 2012 at 5:28 PM, Ullrich Hafner > > wrote:
>>
>>>  On 04/29/2012 10:46 PM, Daniel Becroft wrote: 
>>>
>>> On Wed, Mar 21, 2012 at 6:34 PM, timos wrote:
>>>
 The same problem here. At file system level I can see a generated
 jshint.xml file containing the JSLint errors, a violations/
 violations.xml file and violations/file/.xml
 files but still each file specific link leads to a blank page.

 Any updates on this? Was anyone able to resolve the problem?

>>>  
>>> I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, 
>>> but I still have the issue.
>>>
>>> A few things to note:
>>> 1) The build is performance on a slave node (not the master)
>>> 2) For FxCop, where the link is to a .cs file, I get the code snippets 
>>> highlighted with the errors, but I don't get anything about the error text 
>>> listed above. But if the link is to a class, I get a blank page (with just 
>>> the violations icon).
>>>
>>> It's really getting annoying. Is there anywhere else we should be 
>>> raising this? 
>>>
>>>
>>> During the integration of the violations parsers (JSLint, FXCop, etc.) 
>>> into the warnings plug-in I noticed that the parsers are not serializable. 
>>> Maybe this is the reason for the behavior. Does the plug-in work on the 
>>> master? In order to have a working JSLint parser on a slave (for my 
>>> warnings plug-in) the parsers should be made serializable... 
>>>
>>
>> I've just setup a sandpit with a fresh Jenkins installation, and built 
>> the same job on the MASTER node. Same issue.
>>
>
> I've managed to get some more information (thankfully found some spare 
> tuits).
>
> Using PROCMON.exe (from sysinternals), I can see the following:
>
> 1) Clicking on a *.cs link in the Violations screen gives the following 
> PATH accesses (all with PATH NOT FOUND):
>
> %JENKINS_HOME%\war\job\JOB_NAME\violations\file\RELATIVE_PATH_TO_FILENAME
>
> This path obviously does not exist - why would there be a JOB_NAME folder 
> under the 'war' directory? The file that it is trying to access appears to 
> be:
>
>
> %JENKINS_HOME%\jobs\%JOB_NAME%\builds\%BUILD_NAME%\violations\file\%RELATIVE_PATH_TO_FILENAME%.xml
>
> 2) Clicking on an object name (ie Namespace.ClassName), gives alot of 
> pathname accesses, trying to locate Namespace.ClassName with .groovy, 
> .default.groovy and .jelly. 
>
> Hopefully this helps track down the issue.
>
> Cheers,
> Daniel B.
>


I'm using Python/Pylint, and also see a blank page when I look at the 
errors for a particular file.

The page contains normal header, footer and sidebar, and displays the 
violations 'exclamation mark roadsign' icon on the top left, but is 
otherwise blank

It used to work on this same jenkins installation and project, but I'm 
afraid I'm not sure when or why it stopped working. Possibly a jenkins or 
violations update, or possibly of course I changed/broke the config 
somewhere.

Any other info is very welcome.

  Jonathan Hartley

Re: Violations Plugin and JSlint

[Daniel Becroft]

On Tue, May 1, 2012 at 12:17 PM, Daniel Becroft wrote:

> On Mon, Apr 30, 2012 at 5:28 PM, Ullrich Hafner 
> wrote:
>
>>  On 04/29/2012 10:46 PM, Daniel Becroft wrote:
>>
>> On Wed, Mar 21, 2012 at 6:34 PM, timos wrote:
>>
>>> The same problem here. At file system level I can see a generated
>>> jshint.xml file containing the JSLint errors, a violations/
>>> violations.xml file and violations/file/.xml
>>> files but still each file specific link leads to a blank page.
>>>
>>> Any updates on this? Was anyone able to resolve the problem?
>>>
>>
>> I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, but
>> I still have the issue.
>>
>> A few things to note:
>> 1) The build is performance on a slave node (not the master)
>> 2) For FxCop, where the link is to a .cs file, I get the code snippets
>> highlighted with the errors, but I don't get anything about the error text
>> listed above. But if the link is to a class, I get a blank page (with just
>> the violations icon).
>>
>> It's really getting annoying. Is there anywhere else we should be raising
>> this?
>>
>>
>> During the integration of the violations parsers (JSLint, FXCop, etc.)
>> into the warnings plug-in I noticed that the parsers are not serializable.
>> Maybe this is the reason for the behavior. Does the plug-in work on the
>> master? In order to have a working JSLint parser on a slave (for my
>> warnings plug-in) the parsers should be made serializable...
>>
>
> I've just setup a sandpit with a fresh Jenkins installation, and built the
> same job on the MASTER node. Same issue.
>

I've managed to get some more information (thankfully found some spare
tuits).

Using PROCMON.exe (from sysinternals), I can see the following:

1) Clicking on a *.cs link in the Violations screen gives the following
PATH accesses (all with PATH NOT FOUND):

%JENKINS_HOME%\war\job\JOB_NAME\violations\file\RELATIVE_PATH_TO_FILENAME

This path obviously does not exist - why would there be a JOB_NAME folder
under the 'war' directory? The file that it is trying to access appears to
be:

%JENKINS_HOME%\jobs\%JOB_NAME%\builds\%BUILD_NAME%\violations\file\%RELATIVE_PATH_TO_FILENAME%.xml

2) Clicking on an object name (ie Namespace.ClassName), gives alot of
pathname accesses, trying to locate Namespace.ClassName with .groovy,
.default.groovy and .jelly.

Hopefully this helps track down the issue.

Cheers,
Daniel B.

Re: Violations Plugin and JSlint

[Daniel Becroft]

On Mon, Apr 30, 2012 at 5:28 PM, Ullrich Hafner wrote:

>  On 04/29/2012 10:46 PM, Daniel Becroft wrote:
>
> On Wed, Mar 21, 2012 at 6:34 PM, timos  wrote:
>
>> The same problem here. At file system level I can see a generated
>> jshint.xml file containing the JSLint errors, a violations/
>> violations.xml file and violations/file/.xml
>> files but still each file specific link leads to a blank page.
>>
>> Any updates on this? Was anyone able to resolve the problem?
>>
>
> I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, but
> I still have the issue.
>
> A few things to note:
> 1) The build is performance on a slave node (not the master)
> 2) For FxCop, where the link is to a .cs file, I get the code snippets
> highlighted with the errors, but I don't get anything about the error text
> listed above. But if the link is to a class, I get a blank page (with just
> the violations icon).
>
> It's really getting annoying. Is there anywhere else we should be raising
> this?
>
>
> During the integration of the violations parsers (JSLint, FXCop, etc.)
> into the warnings plug-in I noticed that the parsers are not serializable.
> Maybe this is the reason for the behavior. Does the plug-in work on the
> master? In order to have a working JSLint parser on a slave (for my
> warnings plug-in) the parsers should be made serializable...
>

I've just setup a sandpit with a fresh Jenkins installation, and built the
same job on the MASTER node. Same issue.

Cheers,
Daniel B.

Re: Violations Plugin and JSlint

[Ullrich Hafner]

On 04/29/2012 10:46 PM, Daniel Becroft wrote:
> On Wed, Mar 21, 2012 at 6:34 PM, timos  > wrote:
>
> The same problem here. At file system level I can see a generated
> jshint.xml file containing the JSLint errors, a violations/
> violations.xml file and violations/file/.xml
> files but still each file specific link leads to a blank page.
>
> Any updates on this? Was anyone able to resolve the problem?
>
>
> I'm still having no luck. I'm using stylecop/fxcop instead of JSLint,
> but I still have the issue.
>
> A few things to note:
> 1) The build is performance on a slave node (not the master)
> 2) For FxCop, where the link is to a .cs file, I get the code snippets
> highlighted with the errors, but I don't get anything about the error
> text listed above. But if the link is to a class, I get a blank page
> (with just the violations icon).
>
> It's really getting annoying. Is there anywhere else we should be
> raising this?

During the integration of the violations parsers (JSLint, FXCop, etc.)
into the warnings plug-in I noticed that the parsers are not
serializable. Maybe this is the reason for the behavior. Does the
plug-in work on the master? In order to have a working JSLint parser on
a slave (for my warnings plug-in) the parsers should be made
serializable...

Ulli

Re: Violations Plugin and JSlint

[Daniel Becroft]

On Wed, Mar 21, 2012 at 6:34 PM, timos  wrote:

> The same problem here. At file system level I can see a generated
> jshint.xml file containing the JSLint errors, a violations/
> violations.xml file and violations/file/.xml
> files but still each file specific link leads to a blank page.
>
> Any updates on this? Was anyone able to resolve the problem?
>

I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, but I
still have the issue.

A few things to note:
1) The build is performance on a slave node (not the master)
2) For FxCop, where the link is to a .cs file, I get the code snippets
highlighted with the errors, but I don't get anything about the error text
listed above. But if the link is to a class, I get a blank page (with just
the violations icon).

It's really getting annoying. Is there anywhere else we should be raising
this?

Re: Violations Plugin and JSlint

[timos]

The same problem here. At file system level I can see a generated
jshint.xml file containing the JSLint errors, a violations/
violations.xml file and violations/file/.xml
files but still each file specific link leads to a blank page.

Any updates on this? Was anyone able to resolve the problem?

Re: Violations Plugin and JSlint

[Daniel Becroft]

2012/2/13 Grzegorz Ślusarek 

> Bob Koertge  gmail.com> writes:
>
> >
> > I cannot seem to get detailed infomration on my errors with JSLint and
> violations.  Here is some screenshots http://screencast.com/t/Vu6vo2y9 ->
> I get
> the overall results, but clicking any of the .js file links leads to a
> blank
> page! http://screencast.com/t/LHM09UYw9rufAnyone have any ideas?
>
>
> I have the same issue, see the jslint violation chart, but when I clik in
> any of
> *.js files, I get empty page.
> This happen on Jenkins 1.450 with Jenkins Violations plugin 0.7.10.
> Any tip to solve this issue will be appreciated.
>

Has anyone had any luck with this problem?

Re: Violations Plugin and JSlint

[Grzegorz Ślusarek]

Bob Koertge  gmail.com> writes:

> 
> I cannot seem to get detailed infomration on my errors with JSLint and 
violations.  Here is some screenshots http://screencast.com/t/Vu6vo2y9 -> I get 
the overall results, but clicking any of the .js file links leads to a blank 
page! http://screencast.com/t/LHM09UYw9rufAnyone have any ideas?


I have the same issue, see the jslint violation chart, but when I clik in any 
of 
*.js files, I get empty page. 
This happen on Jenkins 1.450 with Jenkins Violations plugin 0.7.10.
Any tip to solve this issue will be appreciated.

Grzegorz Ślusarek 

Re: Violations Plugin and JSlint

[Daniel Becroft]

I've had the same issues with the violations plugin and style cop/fxcop. Not 
sure why.

Sent from my phone - any correct spelling is accidental.

On 04/02/2012, at 3:33 AM, Bob Koertge  wrote:

> I cannot seem to get detailed infomration on my errors with JSLint and 
> violations.  Here is some screenshots 
> http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but clicking 
> any of the .js file links leads to a blank page! 
> http://screencast.com/t/LHM09UYw9ruf
> 
> Anyone have any ideas?

Violations Plugin and JSlint

[Bob Koertge]

I cannot seem to get detailed infomration on my errors with JSLint and 
violations.  Here is some screenshots 
http://screencast.com/t/Vu6vo2y9 -> I get the overall results, but clicking 
any of the .js file links leads to a blank page! 
http://screencast.com/t/LHM09UYw9ruf

Anyone have any ideas?