You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Apache SkyWalking Component
License Tools (apache/skywalking-eyes)
What happened
Once we updated apache/skywalking-eyes/header from v0.4.0 to v0.5.0
typescript and CSS files using a different comment kind than default are no longer detected as having the license and thus incorrectly get a second copy of license header applied.
+ /*+ * Copyright (c) Jupyter Development Team.+ * Distributed under the terms of the Modified BSD License.+ */#!/usr/bin/env node
/* -----------------------------------------------------------------------------
| Copyright (c) Jupyter Development Team.
| Distributed under the terms of the Modified BSD License.
|----------------------------------------------------------------------------*/
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Yes I am willing to submit a pull request on my own!
Hi @krassowski , thanks for reporting, this issue is brought by an enhancement in 0.5.0, apache/skywalking-eyes#142 , now it strictly checks the Copyright ... header, and in your case, in 0.4.0, the Copyright ... line is stripped so it only checks the line Distributed under the terms of the Modified BSD License and it passed, now that the Copyright ... line is also checked, the | between Copyright ... line and Distributed ... line prevents the tests to pass, so I added | as a comment indicator in apache/skywalking-eyes#168, hope it helps.
Search before asking
Apache SkyWalking Component
License Tools (apache/skywalking-eyes)
What happened
Once we updated
apache/skywalking-eyes/header
from v0.4.0 to v0.5.0typescript and CSS files using a different comment kind than default are no longer detected as having the license and thus incorrectly get a second copy of license header applied.
What you expected to happen
I would expect the existing headers to be detected. I am struggling to see whether this is intended change in the release because it was unpublished (see apache/skywalking-eyes#166 (comment)) and not published again (see https://github.com/apache/skywalking-eyes/releases - if there were release notes warning about breaking changes these are no longer visible)
How to reproduce
This can be seen on jupyterlab/jupyterlab#15068.
For example:
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: