[
https://issues.apache.org/jira/browse/SENSSOFT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741683#comment-16741683
]
Joshua Poore commented on SENSSOFT-322:
---
Solution #2 is a terrible idea. While it's possible to
[
https://issues.apache.org/jira/browse/SENSSOFT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore resolved SENSSOFT-324.
---
Resolution: Pending Closed
see comments
> Example Page Does Not Generate Logs
>
[
https://issues.apache.org/jira/browse/SENSSOFT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741710#comment-16741710
]
Joshua Poore commented on SENSSOFT-324:
---
Resolution:
[1] In master, previous commit changed
Joshua Poore created SENSSOFT-324:
-
Summary: Example Page Does Not Generate Logs
Key: SENSSOFT-324
URL: https://issues.apache.org/jira/browse/SENSSOFT-324
Project: SensSoft
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SENSSOFT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741746#comment-16741746
]
Joshua Poore commented on SENSSOFT-324:
---
Pushed patch to MASTER and SENSSOFT-192
> Example
[
https://issues.apache.org/jira/browse/SENSSOFT-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore closed SENSSOFT-321.
-
> Gulp Mocha Dependency Deprecation: Critical Command Injection Vulnerability
>
[
https://issues.apache.org/jira/browse/SENSSOFT-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore closed SENSSOFT-324.
-
> Example Page Does Not Generate Logs
> ---
>
>
[
https://issues.apache.org/jira/browse/SENSSOFT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741747#comment-16741747
]
Joshua Poore commented on SENSSOFT-322:
---
In order to appropriately update minimatch in sub-,
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741753#comment-16741753
]
Joshua Poore edited comment on SENSSOFT-323 at 1/14/19 4:17 AM:
Added
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741753#comment-16741753
]
Joshua Poore commented on SENSSOFT-323:
---
Added SENSSOFT-323 branch (off SENSSOFT-192) for Gulp
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741753#comment-16741753
]
Joshua Poore edited comment on SENSSOFT-323 at 1/14/19 4:17 AM:
Added
Hi Folks,
Started pruning branches that were many commits behind master (SENSSOFT-214,
v0.2)
website-demo and SENSSOFT-175 are also antiquated, but I want to double/double
check they don’t have anything we should keep. Both are just 1-2 ahead of
master, and likely dupe commits.
For the time
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741758#comment-16741758
]
Joshua Poore commented on SENSSOFT-323:
---
Next, started updating gulpfile.js with new syntax.
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741755#comment-16741755
]
Joshua Poore commented on SENSSOFT-323:
---
First thing I tried was just updating package.json to
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741760#comment-16741760
]
Joshua Poore commented on SENSSOFT-323:
---
Reading a little more–it looks like gulp-utilities is
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741758#comment-16741758
]
Joshua Poore edited comment on SENSSOFT-323 at 1/14/19 4:42 AM:
Next,
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741760#comment-16741760
]
Joshua Poore edited comment on SENSSOFT-323 at 1/14/19 4:45 AM:
I
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741762#comment-16741762
]
Joshua Poore commented on SENSSOFT-323:
---
Another thing that could have broken in the gulpfile is
Hi Folks,
If you’ve been following JIRA, you’ll note that in doing some testing in
UserALE.js, I’ve found that we have a number of critical vulnerabilities in our
UserALE.js build pipeline. This affects 1.0.0 and (forthcoming) 1.1.0. In
summary, Gulp 3.9.1 has some sub, sub dependencies that
[
https://issues.apache.org/jira/browse/SENSSOFT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-322:
--
Attachment: minimatch 2.0.7 vulnerability
> minimatch deprecation: ReDOS vulnerability
>
[
https://issues.apache.org/jira/browse/SENSSOFT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-323:
--
Sprint: Sprint 17
> Update to Gulp 4.0.0
>
>
> Key:
[
https://issues.apache.org/jira/browse/SENSSOFT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-322:
--
Sprint: Sprint 17
> minimatch deprecation: ReDOS vulnerability
>
Joshua Poore created SENSSOFT-323:
-
Summary: Update to Gulp 4.0.0
Key: SENSSOFT-323
URL: https://issues.apache.org/jira/browse/SENSSOFT-323
Project: SensSoft
Issue Type: Task
Joshua Poore created SENSSOFT-322:
-
Summary: minimatch deprecation: ReDOS vulnerability
Key: SENSSOFT-322
URL: https://issues.apache.org/jira/browse/SENSSOFT-322
Project: SensSoft
Issue
[
https://issues.apache.org/jira/browse/SENSSOFT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-322:
--
Description:
minimatch 2.0.7 has a ReDOS vulnerability. minimatch must be upgraded to ^3.0.2
25 matches
Mail list logo
