YAML file IAM policies erroneously trigger "E2507 IAM Policy Documents needs to be JSON"

A resource like this:
Resources:
  MyUser:
    Type: AWS::IAM::User
    Properties:
      Policies:
        - PolicyName: !Sub ${AWS::StackName}-policy
          PolicyDocument:
            - Version: '2012-10-17'
              Statement:
                Action:
                  - s3:GetObject
                Effect: Allow
                Resource:
                  - arn:aws:s3:::*

Will be created just fine by the Amazon API, but cfn-lint reports:
E2507 IAM Policy Documents needs to be JSON
test.yaml:7:11

E3002 Property should be of type Json not List at Resources/MyUser/Properties/Policies/0/PolicyDocument
test.yaml:7:11

thanks @alexjurkiewicz I'll get on this one.

@alexjurkiewicz
CFNUser:
  Type: AWS::IAM::User
  Properties:
    Policies:
    - PolicyName: !Sub ${AWS::StackName}-policy
      PolicyDocument:
        - Version: '2012-10-17'
          Statement:
            Action:
              - s3:GetObject
            Effect: Allow
            Resource:
              - arn:aws:s3:::*

This gives me an error of Value of property PolicyDocument must be an object

Sorry ended that a little earlier.  I've been trying to replicate your success and I'm having troubles.
In fact cut and pasted your example and got the same error  Value of property PolicyDocument must be an object

@alexjurkiewicz so I can completely replicate what you are doing what region are deploying into?

Hi @alexjurkiewicz just checking in if you can provide details to help us replicate?  Is this still an issue?


Use sync mode when working with file API

When doing a hardware reset on a device immediately after the software update is finished it might happen that files are corrupted due to data not yet written to disk. The additional sync fixes this issue.

We could figure out a way to do a sync at the end of the update instead, but it is probably fine

Just FYI: performance penalty is not noticeable by me.


feat: add support for make it mine and deploy via cloudbuild trigger

Adding changes to enable make it mine via cloudshell as well as cloudbuild trigger.

/gcbrun

/gcbrun

/gcbrun


ts service 2.6 doesn't work for projects without configs

On open request:
ENOENT: no such file or directory, stat '/Users/anstarovoyt/WebstormProjects/untitled329/tsconfig.json'
Err 14    Exception on executing command
{"sessionId":1508169937196,"seq":0,"type":"request","command":"open","arguments":{"file":"/Users/anstarovoyt/WebstormProjects/untitled329/etsts.ts"}}:
Error: ENOENT: no such file or directory, stat '/Users/anstarovoyt/WebstormProjects/untitled329/tsconfig.json'
    at Object.fs.statSync (fs.js:968:11)
    at getModifiedTime (/Users/anstarovoyt/idea/IDEA/out/classes/production/JavaScriptLanguage/jsLanguageServicesImpl/typescript/ts-plugin.js:151:19)
    at Object.addFile (/Users/anstarovoyt/idea/IDEA/out/classes/production/JavaScriptLanguage/jsLanguageServicesImpl/typescript/ts-plugin.js:194:20)
    at Object.ts_impl.sys.watchFile (/Users/anstarovoyt/idea/IDEA/out/classes/production/JavaScriptLanguage/jsLanguageServicesImpl/typescript/ts-plugin.js:81:53)
    at addFileWatcher (evalmachine.<anonymous>:98584:21)
    at createWatcherWithLogging (evalmachine.<anonymous>:98614:23)
    at Object.addFileWatcherWithLogging (evalmachine.<anonymous>:98589:16)
    at ProjectService.watchFile (evalmachine.<anonymous>:100621:96)
    at ProjectService.createConfigFileWatcherOfConfigFileExistence (evalmachine.<anonymous>:101212:90)
    at evalmachine.<anonymous>:101280:31

please note that the problem is critical for JetBrains IDEs

ok, I see I can handle the problem on our side by processing non-existing files.


Feature: remove the panel prefix if only one panel is used in Filament

This PR provides the ability to allow for no panel prefix in the/api/ routes. Additionally this will only work if you have configured only one panel. Otherwise you'll still get the new InvalidTenancyConfiguration("Tenancy awareness is enabled!. Please set 'api-service.route.panel_prefix=true' and 'api-service.tenancy.enabled=true'"); message.


Deprecate any_slice

Description of changes:
See #2788 for details.
Resolved issues:
Resolves #2788
Resolves #2634
Related RFC:

Optional #ISSUE-NUMBER.
Call-outs:

Testing:

How is this change tested? Added one test

Is this a refactor change? No

Checklist

[X] Each commit message has a non-empty body, explaining why the change was made
[X] Methods or procedures are documented
[X] Regression or unit tests are included, or existing tests cover the modified code
[X] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

Please replace the usage of any_slice in our tests

Done.


Feature (Backend): Add uri licence for swagger config

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@f43ce3b). Click here to learn what that means.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #148   +/-   ##
=======================================
  Coverage        ?   75.69%
  Complexity      ?      128
=======================================
  Files           ?       41
  Lines           ?      358
  Branches        ?        7
=======================================
  Hits            ?      271
  Misses          ?       82
  Partials        ?        5

Impacted Files
Coverage Δ
Complexity Δ

...bo/swagger/configuration/SwaggerConfiguration.java
100.00% <100.00%> (ø)
7.00 <0.00> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f43ce3b...b72238c. Read the comment docs.


Fix FileSystem.listStatus javadoc

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
37
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1086
trunk passed

+1
compile
1041
trunk passed

+1
checkstyle
39
trunk passed

+1
mvnsite
71
trunk passed

+1
shadedclient
759
branch has no errors when building and testing our client artifacts.

+1
javadoc
58
trunk passed

0
spotbugs
120
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
118
trunk passed

_ Patch Compile Tests _

+1
mvninstall
48
the patch passed

+1
compile
996
the patch passed

+1
javac
996
the patch passed

+1
checkstyle
36
the patch passed

+1
mvnsite
75
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
645
patch has no errors when building and testing our client artifacts.

+1
javadoc
59
the patch passed

+1
findbugs
121
the patch passed

_ Other Tests _

+1
unit
526
hadoop-common in the patch passed.

+1
asflicense
43
The patch does not generate ASF License warnings.

5836

Subsystem
Report/Notes

Docker
Client=18.09.8 Server=18.09.8 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 5146ea88315b 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 7f1b76c

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/1/testReport/

Max. process+thread count
1361 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
63
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1138
trunk passed

+1
compile
1041
trunk passed

+1
checkstyle
38
trunk passed

+1
mvnsite
76
trunk passed

+1
shadedclient
749
branch has no errors when building and testing our client artifacts.

+1
javadoc
56
trunk passed

0
spotbugs
124
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
122
trunk passed

_ Patch Compile Tests _

+1
mvninstall
50
the patch passed

+1
compile
1001
the patch passed

+1
javac
1001
the patch passed

+1
checkstyle
35
the patch passed

+1
mvnsite
71
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
607
patch has no errors when building and testing our client artifacts.

+1
javadoc
57
the patch passed

+1
findbugs
123
the patch passed

_ Other Tests _

+1
unit
507
hadoop-common in the patch passed.

+1
asflicense
42
The patch does not generate ASF License warnings.

5826

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 0e3de8374a6f 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c01e137

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/2/testReport/

Max. process+thread count
1390 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
46
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1117
trunk passed

+1
compile
1090
trunk passed

+1
checkstyle
40
trunk passed

+1
mvnsite
75
trunk passed

+1
shadedclient
762
branch has no errors when building and testing our client artifacts.

+1
javadoc
60
trunk passed

0
spotbugs
127
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
124
trunk passed

_ Patch Compile Tests _

+1
mvninstall
54
the patch passed

+1
compile
1111
the patch passed

+1
javac
1111
the patch passed

+1
checkstyle
43
the patch passed

+1
mvnsite
78
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
653
patch has no errors when building and testing our client artifacts.

+1
javadoc
65
the patch passed

+1
findbugs
142
the patch passed

_ Other Tests _

-1
unit
566
hadoop-common in the patch failed.

+1
asflicense
39
The patch does not generate ASF License warnings.

6130

Reason
Tests

Failed junit tests
hadoop.ha.TestZKFailoverController

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux ce6eac378a31 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e872ceb

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/3/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/3/testReport/

Max. process+thread count
1461 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
34
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1198
trunk passed

+1
compile
1059
trunk passed

+1
checkstyle
46
trunk passed

+1
mvnsite
82
trunk passed

+1
shadedclient
868
branch has no errors when building and testing our client artifacts.

+1
javadoc
65
trunk passed

0
spotbugs
125
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
123
trunk passed

_ Patch Compile Tests _

+1
mvninstall
47
the patch passed

+1
compile
992
the patch passed

+1
javac
992
the patch passed

+1
checkstyle
45
the patch passed

+1
mvnsite
75
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
719
patch has no errors when building and testing our client artifacts.

+1
javadoc
61
the patch passed

+1
findbugs
133
the patch passed

_ Other Tests _

+1
unit
554
hadoop-common in the patch passed.

+1
asflicense
44
The patch does not generate ASF License warnings.

6199

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 81b565a45137 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 00b5a27

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/4/testReport/

Max. process+thread count
1369 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
39
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1074
trunk passed

+1
compile
1139
trunk passed

+1
checkstyle
39
trunk passed

+1
mvnsite
78
trunk passed

+1
shadedclient
800
branch has no errors when building and testing our client artifacts.

+1
javadoc
61
trunk passed

0
spotbugs
120
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
118
trunk passed

_ Patch Compile Tests _

+1
mvninstall
51
the patch passed

+1
compile
1116
the patch passed

+1
javac
1116
the patch passed

+1
checkstyle
42
the patch passed

+1
mvnsite
71
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
677
patch has no errors when building and testing our client artifacts.

+1
javadoc
62
the patch passed

+1
findbugs
135
the patch passed

_ Other Tests _

-1
unit
560
hadoop-common in the patch failed.

+1
asflicense
44
The patch does not generate ASF License warnings.

6165

Reason
Tests

Failed junit tests
hadoop.util.TestDiskCheckerWithDiskIo

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux d249303bf832 4.4.0-157-generic #185-Ubuntu SMP Tue Jul 23 09:17:01 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e356e4f

Default Java
1.8.0_212

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/5/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/5/testReport/

Max. process+thread count
1429 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
69
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1231
trunk passed

+1
compile
1436
trunk passed

+1
checkstyle
46
trunk passed

+1
mvnsite
90
trunk passed

+1
shadedclient
810
branch has no errors when building and testing our client artifacts.

+1
javadoc
64
trunk passed

0
spotbugs
131
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
129
trunk passed

_ Patch Compile Tests _

+1
mvninstall
51
the patch passed

+1
compile
1283
the patch passed

+1
javac
1283
the patch passed

+1
checkstyle
50
the patch passed

+1
mvnsite
81
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
789
patch has no errors when building and testing our client artifacts.

+1
javadoc
69
the patch passed

+1
findbugs
155
the patch passed

_ Other Tests _

-1
unit
622
hadoop-common in the patch failed.

+1
asflicense
45
The patch does not generate ASF License warnings.

7069

Reason
Tests

Failed junit tests
hadoop.ha.TestZKFailoverController

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 428b277f812a 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 094d736

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/6/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/6/testReport/

Max. process+thread count
1374 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1060
trunk passed

+1
compile
1125
trunk passed

+1
checkstyle
36
trunk passed

+1
mvnsite
67
trunk passed

+1
shadedclient
770
branch has no errors when building and testing our client artifacts.

+1
javadoc
53
trunk passed

0
spotbugs
110
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
107
trunk passed

_ Patch Compile Tests _

+1
mvninstall
44
the patch passed

+1
compile
1031
the patch passed

+1
javac
1031
the patch passed

+1
checkstyle
39
the patch passed

+1
mvnsite
72
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
661
patch has no errors when building and testing our client artifacts.

+1
javadoc
56
the patch passed

+1
findbugs
121
the patch passed

_ Other Tests _

+1
unit
541
hadoop-common in the patch passed.

+1
asflicense
38
The patch does not generate ASF License warnings.

5932

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 5deb9f9a49f5 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 61b2df2

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/7/testReport/

Max. process+thread count
1361 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
80
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1253
trunk passed

+1
compile
1101
trunk passed

+1
checkstyle
48
trunk passed

+1
mvnsite
83
trunk passed

+1
shadedclient
880
branch has no errors when building and testing our client artifacts.

+1
javadoc
72
trunk passed

0
spotbugs
152
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
149
trunk passed

_ Patch Compile Tests _

+1
mvninstall
52
the patch passed

+1
compile
1072
the patch passed

+1
javac
1072
the patch passed

+1
checkstyle
44
the patch passed

+1
mvnsite
80
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
791
patch has no errors when building and testing our client artifacts.

+1
javadoc
82
the patch passed

+1
findbugs
171
the patch passed

_ Other Tests _

-1
unit
596
hadoop-common in the patch failed.

+1
asflicense
62
The patch does not generate ASF License warnings.

6697

Reason
Tests

Failed junit tests
hadoop.security.TestRaceWhenRelogin

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux a1993e5134ee 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3329257

Default Java
1.8.0_222

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/8/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/8/testReport/

Max. process+thread count
1342 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
42
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
1094
trunk passed

+1
compile
1024
trunk passed

+1
checkstyle
48
trunk passed

+1
mvnsite
84
trunk passed

+1
shadedclient
837
branch has no errors when building and testing our client artifacts.

+1
javadoc
67
trunk passed

0
spotbugs
124
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
122
trunk passed

_ Patch Compile Tests _

+1
mvninstall
48
the patch passed

+1
compile
962
the patch passed

+1
javac
962
the patch passed

+1
checkstyle
48
the patch passed

+1
mvnsite
81
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
657
patch has no errors when building and testing our client artifacts.

+1
javadoc
68
the patch passed

+1
findbugs
128
the patch passed

_ Other Tests _

+1
unit
560
hadoop-common in the patch passed.

+1
asflicense
53
The patch does not generate ASF License warnings.

5996

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-350/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/350

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 6893ea287441 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 915cbc9

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/9/testReport/

Max. process+thread count
1508 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common U: hadoop-common-project/hadoop-common

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-350/9/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


Add get apps command

Towards giantswarm/giantswarm#16978
This adds the get apps command.
$ kubectl gs get apps -h

Display one or many apps

Output columns:

- NAME: Name of the app.
- VERSION: Version of the app.
- LAST DEPLOYED: When the app was last deployed.
- STATUS: Status of the app.

Usage:
  kubectl gs get apps <app-name> [flags]

Aliases:
  apps, app

Examples:
  # List all apps for the current namespace
  kubectl gs get apps

  # Get one app by its name
  kubectl gs get app coredns
...

$ kubectl gs get apps -n dmie3

NAME                 VERSION   LAST DEPLOYED   STATUS
cert-exporter        1.2.3     10d             deployed
cert-manager         2.3.2     10d             deployed
chart-operator       2.5.1     10d             deployed
cluster-autoscaler   1.17.3    10d             deployed
coredns              1.2.0     10d             deployed
external-dns         1.5.0     10d             deployed
kiam                 1.5.0     10d             deployed
kube-state-metrics   1.1.1     10d             deployed
metrics-server       1.1.1     10d             deployed
net-exporter         1.9.0     10d             deployed
node-exporter        1.3.0     10d             deployed

Tested on gauss.

What happens if this command is executed with a WC kubeconfig? It just fails or is there a notice printed, that this probably does not work on a WC?

What happens if this command is executed with a WC kubeconfig? It just fails or is there a notice printed, that this probably does not work on a WC?

@ubergesundheit Currently just the CRD missing error is printed. Not sure why there is the throttling message from my test cluster.
Good idea to show a custom message. I'll get that done.
go run main.go get apps -n giantswarm
I0504 11:56:34.906668   94876 request.go:621] Throttling request took 1.056960859s, request: GET:https://api.ni0t5.k8s.gauss.eu-west-1.aws.gigantic.io/apis/coordination.k8s.io/v1?timeout=32s
Error: No matches for kind "App" in version "application.giantswarm.io/v1alpha1"
exit status 1

go run main.go get apps -n giantswarm
I0504 14:13:14.348650   98718 request.go:621] Throttling request took 1.078231816s, request: GET:https://api.ni0t5.k8s.gauss.eu-west-1.aws.gigantic.io/apis/coordination.k8s.io/v1?timeout=32s
No App CRD found.
Please check you are accessing a management cluster

@ubergesundheit I added this message.
The rate limiter error is still there but it includes the API server URL which is kind of useful. So I think we can live with it. WDYT?

The rate limiter error is still there but it includes the API server URL which is kind of useful. So I think we can live with it. WDYT?

Fine with me :)


gadgets/snapshot_socket: provide human representation of state

The snapshot socket should provide a human readable representation of the socket state.
https://github.com/inspektor-gadget/inspektor-gadget/blob/13b255708ad3ced3a12cbe01d46d3c7c55636758/gadgets/snapshot_socket/program.bpf.c#L53
It can probably be done by defining (or reusing) an enumeration from the kernel.

Hi @mauriciovasquezbernal can you elaborate more about this issue? currently this is what i see running this gadget

@mani1911 sorry for the big delay, I thought I replied to your question.

Here state 10 corresponds to TCP_LISTEN ?

You're right.
It was handled in the built-in gadget by using this
https://github.com/inspektor-gadget/inspektor-gadget/blob/4daf81ad7cbbad820112de7a66010897cd34dadb/pkg/gadgets/snapshot/socket/tracer/tracer.go#L49-L76
I think the right solution will be to define a enum with different states as defined in https://github.com/inspektor-gadget/inspektor-gadget/blob/4daf81ad7cbbad820112de7a66010897cd34dadb/pkg/gadgets/snapshot/socket/tracer/tracer.go#L51-L55
and implement the udp specific logic directly in ebpf
https://github.com/inspektor-gadget/inspektor-gadget/blob/4daf81ad7cbbad820112de7a66010897cd34dadb/pkg/gadgets/snapshot/socket/tracer/tracer.go#L63-L73
Pinging @blanquicet as he implemented that initially.

btw, it's already being done in #3314.


Two saliency maps missing on DUT-OMRON dataset

There are two saliency maps missing on DUT-OMRON: sun_akxddynsopjifavt.png and sun_barwtmnxkuxyttlj.png.

好像得翻墙，能否百度云盘

resnet-50 based model dont have the pre-computed map??


READ-FAILED operation?

Hi,
I'm receiving such entries in YCSB log:
2016-03-02 14:58:23:453 100 sec: 97621 operations; 912.3 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10945.5] [UPDATE AverageLatency(us)=3496.61] [READ-FAILED AverageLatency(us)=4593.01]
2016-03-02 14:58:23:453 100 sec: 97621 operations; 912.3 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10945.5] [UPDATE AverageLatency(us)=3496.61] [READ-FAILED AverageLatency(us)=4593.01]
2016-03-02 14:58:33:453 110 sec: 107778 operations; 1015.7 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=9686.13] [UPDATE AverageLatency(us)=3453.05] [READ-FAILED AverageLatency(us)=4478.34]
2016-03-02 14:58:33:453 110 sec: 107778 operations; 1015.7 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=9686.13] [UPDATE AverageLatency(us)=3453.05] [READ-FAILED AverageLatency(us)=4478.34]
2016-03-02 14:58:43:453 120 sec: 117358 operations; 958 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10317.59] [UPDATE AverageLatency(us)=3562.18] [READ-FAILED AverageLatency(us)=4896.01]
2016-03-02 14:58:43:453 120 sec: 117358 operations; 958 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10317.59] [UPDATE AverageLatency(us)=3562.18] [READ-FAILED AverageLatency(us)=4896.01]
2016-03-02 14:58:53:453 130 sec: 126732 operations; 937.4 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10497.2] [UPDATE AverageLatency(us)=3673.27] [READ-FAILED AverageLatency(us)=4770.35]
2016-03-02 14:58:53:453 130 sec: 126732 operations; 937.4 current ops/sec; est completion in 1 minutes [READ AverageLatency(us)=10497.2] [UPDATE AverageLatency(us)=3673.27] [READ-FAILED AverageLatency(us)=4770.35]

What does READ-FAILED mean? Is this bad? If so, how can I fix that?

Yes, in general READ_FAILED is bad. It means for what ever reason YCSB was not able to perform a read operation it attempted. Can you please post the command you ran, all of the output (if it is not too long), and any workload files you are using if you have modified them?

 The exception you posted says 2 responses were required but only 1 replica responded. This is causing the reads to fail since not all the replicas are responding.

@risdenk I went with default Cassandra configuration (3 node and 5 node setups). Nothing interesting in logs except
│DEBUG [SharedPool-Worker-12] 2016-03-03 18:07:50,161 StorageProxy.java:1462 - Read timeout; received 1 of 2 responses

@kamsz - so, it looks like some of the read operations are succeeding, since you have READ latency numbers. Can you confirm that by posting the final printout after the entire benchmark has finished? There should be some final output.
If some reads succeed and some don't then you might be exceeding a comfortable load level of your Cassandra cluster.
Checkout the Read Consistency table here: http://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_config_consistency_c.html
The QUORUM level reads:

Ensures strong consistency if you can tolerate some level of failure.

So, you have high consistency, but potentially with some expected failure since Cassandra must meet a Quorum before returning you an answer, or just not returning you an answer which seems like is happening here. You might try fiddling with -p cassandra.readtimeoutmillis, making this longer may give Cassandra more opportunity to return a quorum on reads.
You might also be able confirm that you have passed the comfortable load threshold if by running smaller workloads (less operations + less threads) runs successfully with no issues.

Forgot to add, I'm running 1:1 YCSB/Cassandra ratio. Perhaps that's the issue?
Edit: Tried wih 1:2 YCSB/Cassandra ratio, same result.

Can you explain what you mean by this? do you have multiple instances of YCSB running? 1 instance of YCSB for each node of Cassandra?

@kruthar Yes, I've several YCSB instances that are stressing Cassandra cluster. From the summary log for  I'm getting:

211438 READ-FAILED operations,
275771 UPDATE operations,
612790 READ operations.
864 operations/second

I've lowered operation count, but I'm still getting READ-FAILED operations...

Are you all the YCSB instances at the same time? with the same command I presume?
By how much did you lower the operation count?

@kruthar Yup, same command, but I split insertstart based on YCSB instances. I've lowered operation count to 1100000.

So, 1100000 operations, 8 threads, 3 instances of YCSB is still a very large test. If you run a test that is maybe just one instance of YCSB running on one thread, do you have the same issues.
Did you try cassandra.readtimeoutmillis?
What I'm trying to get at here is that what it looks like is that there is actually no problem happening, that you have simply surpassed your Cassandra cluster's capability. Keep trying to lower your benchmarks and see at what point you don't have any issues anymore.

@kruthar the results are the same However, I've noticed that the number of the READ-FAILED operations is equal to actual successful reads, but with NOT_FOUND response. Is there any way to diagnose why there's NOT_FOUND status in these reads?

@kamsz - Which version of YCSB are you using? Is the load phase working correctly?

@kamsz - can you try with an easier read consistency? say cassandra.readconsistencylevel=ONE, which is the default. If you don't see issues with ONE as the consistency level then that would seem to tell me that your Cassandra cluster cannot keep up with the load because it is having to wait to long on each read request.
And just to be clear, you said that the results were the same when you tried to increase cassandra.readtimeoutmillis? What did you try to increase it to?

@kruthar @risdenk I've resolved the issue... the problem was field_length in workload file - apparently it doesn't like 255 value. When I lowered that to 250, everything started to work.


idea-ultimate: libasyncProfiler.so cannot find libstdc++.so.6

Describe the bug
When trying to profile a Java program in Intellij IDEA Ultimate, the execution stop with
Error occurred during initialization of VM
Could not find agent library /tmp/libasyncProfiler.so in absolute path, with error: libstdc++.so.6: cannot open shared object file: No such file or directory

To Reproduce
Steps to reproduce the behavior:

Open/Create a Java project with an executable class in IntelliJ IDEA Ultimate
In 2019.1: Enable experimental profiler support as described here
In 2019.2: Profiler support should already be available
Run the project with profiling.

Expected behavior
The program executes an the profiler view is available.
Additional context
It seems that IDEA is copying the libasyncProfiler.so from somewhere to /tmp/ which may make it difficult to patch. You can work around the error by setting LD_LIBRARY_PATH to /nix/store/95i38z61425xrci8h178blwff88p0a4h-gcc-7.3.0-lib/lib/ in the environment variables of the profiled "Run/Debug Configuration". Starting idea-ultimate with LD_LIBRARY_PATH set does not help
Metadata
Please run nix run nixpkgs.nix-info -c nix-info -m and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 4.19.40, NixOS, 19.03.172500.aade6ded796 (Koi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - channels(root): `"nixos-19.03.172500.aade6ded796"`
 - channels(markus): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: idea-ultimate
# a list of nixos modules affected by the problem
module:

Is it still relevant?

I just tried and it still reproduces with 2019.3, the workaround with modifying LD_LIBRARY_PATH in the run configurations also still works.


Sidekiq: capture sidekiq context as extra info

The Sidekiq context contains some very useful things for debugging purposes, for instance:

ID of the failed job
arguments for the job
name of the worker class

Side note: should support for Sidekiq v2 be dropped? Version 4 was just released, and the latest version 2 release is over a year old already.

:+1:

This could definitely use a matching spec. Could you add one? Thanks! 👏🏼


make Editor lightning quick

Naive use of ceylon.ast.core::Editor is too slow to be used in a compiler. So I'd like to explore ideas to make it fast.

Change default implementations of leaf nodes to return that
Add a method default Boolean editNode(Node node) => true; called by default implementations of all non-leaf nodes; return that if false.
Other?

Here's a somewhat optimized Editor that can help serve as an example. This one runs in a little under twice the time of a simple count-nodes visitor on the SDK. A non-optimized Editor takes about 3 or 4 times as long to run.
The big downside to this approach is that editNode() can be complex and serves no purpose other than optimization.

First bullet done. Perhaps we could do the second one in a subclass of Editor?

Is there an advantage to having a subclass that outweighs the maintenance overhead?
I'd hazard to guess that a when using the default editNode() => true, the overhead of the check would not be measurable.

The big downside to this approach is that editNode() can be complex

True, but it can also be simple. I would think that often, a simple => is X; or => is X|Y|Z; would be enough. For known X, Y, Z, this would compile down to an instanceof test (or instanceof || instanceof || …), and I think I recall reading that HotSpot can often optimize instanceof down to a single instruction.

The advantage would be to keep Editor a bit simpler, but I guess that’s a pretty small advantage

True, but it can also be simple

Agreed. And, editNode() impls can error on the side of returning true, to reduce complexity.

Right. So let’s add this…

Second bullet also done. Should I leave this issue open for more suggestions, or close it, and you’ll open new issues for new suggestions?

Great, thanks @lucaswerkmeister!
I'm still interested in any ideas/techniques anyone might have for writing fast Editors, but I'm out of improvement ideas for now, so I'll go ahead and close the issue.


change to minzip version bundle and add fela core package to main readme

Like the title said, i changed to minzip instead of min and added core package bundle size to main readme.
related to #619

awesome!


In case of HTTPS tunnel filtering event does not contain whitelisted request status

If I disable HTTPS filtering for Firefox (or it is disabled for some other app), filtering events in filtering log are as HTTPS tunnel. This is right.
But if I add some whitelist rule to user filter like @@||example.org$app=org.mozilla.firefox, the event's request status should become Whitelisted, not just Processed.

The RequestProcessedEvent object has relevant applied rules and type is BASIC_EXCEPTIONS, we need just to add request status WHITELISTED for such events.

core/pull-requests/1024


Plans to support preprocessor tokens

Thank you for this project, it has been help me for developing a new processor in IntelliJ IDEA.
I noticed that the preprocessor tokens are not supported and I get error like: <spec element> expected, got '@if or <statement> or SleighTokenType.} expected, got '@if'
Are there any plans to support preprocessor tokens?

Hi there!  I guess I forgot to add @if support to the missing features list.
At the moment the plugin supports more or less all I've ever needed so I didn't really prioritise other features.  Right now I haven't worked with Ghidra for a while so I may pick this up again if I get back to it.  I also kept things on hold waiting to see if Ghidra would move to a Treesitter grammar but I think the development team decided not to.
However, if you want to give a try at adding that feature yourself, you're more than welcome to!  I'd definitely merge such a PR if that would show up :)


Example use with Gin Framework

Your's such great & useful software

Gin framework seems interesting, I'm going to add it to the list of possible modules and middlewares
Thank you!

I might create a working plugin in the future but this will work for phases 1, 2 and 5. Phases 3 and 4 requires a responseWriter overwrite.
func Coraza() gin.HandlerFunc {
        waf := engine.NewWaf()
        parser := seclang.NewParser(waf)
        parser.FromString(`secrule.....`)
	return func(c *gin.Context) {
		tx := waf.NewTransaction()
                 tx.ProcessRequest(c.Request)
                 if tx.Interruption != nil {...}
		c.Next()
		// in order to parse the response, you must overwrite the ResponseWriter https://github.com/gin-gonic/gin/blob/caf2802593277033683c4e8cb5f22c81cc35eae8/response_writer.go#L20
	}
}

func main() {
	r := gin.New()
	r.Use(Coraza())

	r.GET("/test", func(c *gin.Context) {
// your code
	})

	// Listen and serve on <IP_ADDRESS>:8080
	r.Run(":8080")
}

Now there is a gin implementation: https://github.com/jptosso/coraza-gin

Now there is a gin implementation: https://github.com/jptosso/coraza-gin

I hope this message finds you well. I am reaching out to kindly request support for Coraza version 3 compatibility in the coraza-gin middleware library.
I've noticed that the current version of coraza-gin supports Coraza version 2, but as Coraza version 3 has been released with notable enhancements, I believe that updating the middleware to support Coraza v3 would greatly benefit the community.
Coraza version 3 introduces significant changes, I understand that this might require adjustments in the middleware's codebase. Is there a roadmap or plan in place to bring coraza-gin up to date with Coraza version 3?


what would it take to update to Node 6?

If I were to attempt to update this project to a more recent version of node what issues could I expect to run into? I guess my question really boils down to is whether this is even worth considering

It's mostly around express, and old incompatible code.
On Mon, 15 Aug 2016, 17:03 Miguel Clement<EMAIL_ADDRESS>wrote:

If I were to attempt to update this project to a more recent version of
node what issues could I expect to run into? I guess my question really
boils down to is whether this is even worth considering
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jsbin/jsbin/issues/2848, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAA1hCVWi0OILzv1H3m3jBRgfT3pk5VNks5qgI26gaJpZM4Jkg2i
.


Uncaught Error: Attempted to resolve swiper, which was expected to be a component, but nothing was found.

index.hbs
<Swiper as |swiper|>
  <swiper.slide>
    // or not contextual Swiper::Slide Slide 1
  </swiper.slide>
  <swiper.slide>
    Slide 2
  </swiper.slide>
  <swiper.slide>
    Slide 3
  </swiper.slide>
</Swiper>

index.js
import Component from '@glimmer/component';

export default class RoomsSliderComponent extends Component {}

package.json
  "devDependencies": {
    "@ember/optional-features": "^2.0.0",
    "@ember/render-modifiers": "^2.0.4",
    "@ember/test-helpers": "^2.8.1",
    "@glimmer/component": "^1.1.2",
    "@glimmer/tracking": "^1.1.2",
    "autoprefixer": "^10.4.13",
    "babel-eslint": "^10.1.0",
    "broccoli-asset-rev": "^3.0.0",
    "ember-auto-import": "^2.4.3",
    "ember-browserify": "^1.2.2",
    "ember-cli": "~4.8.0",
    "ember-cli-app-version": "^5.0.0",
    "ember-cli-babel": "^7.26.11",
    "ember-cli-dependency-checker": "^3.3.1",
    "ember-cli-htmlbars": "^6.1.1",
    "ember-cli-inject-live-reload": "^2.1.0",
    "ember-cli-postcss": "^8.2.0",
    "ember-cli-sri": "^2.1.1",
    "ember-cli-swiper": "^1.0.6",
    "ember-cli-terser": "^4.0.2",
    "ember-data": "~4.7.3",
    "ember-fetch": "^8.1.2",
    "ember-load-initializers": "^2.1.2",
    "ember-page-title": "^7.0.0",
    "ember-qunit": "^6.0.0",
    "ember-resolver": "^8.0.3",
    "ember-source": "~4.8.0",
    "ember-swiper7": "^1.3.0",
    "ember-template-lint": "^4.16.1",
    "ember-welcome-page": "^6.2.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-ember": "^11.1.0",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-prettier": "^4.2.1",
    "eslint-plugin-qunit": "^7.3.1",
    "loader.js": "^4.7.0",
    "npm-run-all": "^4.1.5",
    "prettier": "^2.7.1",
    "qunit": "^2.19.2",
    "qunit-dom": "^2.0.0",
    "tailwindcss": "^3.2.4",
    "webpack": "^5.74.0"
  }

Any reason why'd not work ?

To be safe, it's a good idea to restart the local server after installing new dependencies, and especially before trying to debug an addon that isn't working.
Sorry , lol.


Path for plugins to upgrade to OpenSearch, support backwards compatibility

We need to have a design to upgrade plugins while supporting backward compatibility.
This issue will cover all the pieces which should be upgraded.

[ ]  Renaming Rest APIs
[ ] Renaming Indexes
[ ] Renaming Settings
[ ] Renaming Namespaces (E.g. com.amazon.opendistroforelasticsearch to org.opensearch)
[ ] Renaming all remaining identifiers (E.g Opendistro to OpenSearch).
[ ] 100% Backward compatibility with ES v.?
[ ] Drop in replacement for Opendistro plugins with OpenSearch plugins

Settings renaming support in progress in https://github.com/opensearch-project/OpenSearch/pull/643.

@dblock @saratvemulapalli
I see that Renaming Namespaces has been checked. Have we already had a decision/POC for it?
How does renaming all class names and namespaces support backward compatibility, e.g Java serialization, Transport Actions? Especially during B/G deployment on the managed service where nodes are upgraded/migrated from opendistro cluster to opensearch cluster, how would opensearch cluster recognize the transport requests that have opendistro namespaces and classes serialized in the header and know how to deserialize them?

Renaming was focused on just the naming part. For the items you describe we already have some bugs open like https://github.com/opensearch-project/OpenSearch/issues/669 that @shwetathareja is looking into. If there's a scenario that you know of that is not covered, let's at least open an issue in OpenSearch?

@dblock @saratvemulapalli
I see that Renaming Namespaces has been checked. Have we already had a decision/POC for it?
How does renaming all class names and namespaces support backward compatibility, e.g Java serialization, Transport Actions? Especially during B/G deployment on the managed service where nodes are upgraded/migrated from opendistro cluster to opensearch cluster, how would opensearch cluster recognize the transport requests that have opendistro namespaces and classes serialized in the header and know how to deserialize them?

In general the Java Serialization and Transport action shouldn't fail during upgrade from Elasticsearch to OpenSearch as actual serialization and actions are not dependent on the class/ package names. As long the class attributes data types and their ordering in not changing while reading and write to stream, It should work as is. And as @dblock mentioned the version compatibility logic is already taken as part of https://github.com/opensearch-project/OpenSearch/pull/775

Are we ready to close this issue? What remains?

Are we ready to close this issue? What remains?

We should be able to close this as the follow up is: https://github.com/opensearch-project/opensearch-plugins/issues/39


cargo machete: leptos_macro - Removed unused crates.

"Say hello, wave goodbye" to leptos_server.

Cheers! I wonder if we can set up some checks for this during the CI so you don't have to keep cleaning up after us all the time 😄


Include version number in extracted path

Fixes #26

Friendly ping.
This PR would help to make sure you are always using the version you think you are using.

@Ardesco I think this is worth adding.

Alright. I don't see why it is a problem though that old versions would be kept around unless you go and delete them manually. My ~/.m2 folder is full of old versions of libs I do not actively use. If it becomes a problem, I go and delete them and they are redownloaded if still needed by some build. Maybe I am using the plugin in a different way than you but I don't see why it should even try to remove old versions.

Assuming we don't care about cleanup you still have the rest of the problems noted above.  Remember there is no guarantee that the version number used actually relates to the version of the binary you are downloading.
We could save the binaries to a folder that matches the hash of the file, that would guarantee that the binary in the folder is the expected one, but a file hash isn't very meaningful.
I find that giving people wrong information is worse than not providing information at all, this PR will provide people with information that can quite easily be wrong.
You will know what version of a driver binary is used when you run your tests anyway, thanks to output like this:
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.lazerycode.selenium.tests.GoogleExampleIT

Local Operating System: MAC OS X
Local Architecture: x86_64
Selected Browser: firefox
Connecting to Selenium Grid: false

1523714359544	geckodriver	INFO	geckodriver 0.20.0
1523714359550	geckodriver	INFO	Listening on <IP_ADDRESS>:34501

[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.lazerycode.selenium.tests.GoogleExampleIT

Local Operating System: MAC OS X
Local Architecture: x86_64
Selected Browser: chrome
Connecting to Selenium Grid: false

Starting ChromeDriver 2.37.544337 (8c0344a12e552148c185f7d5117db1f28d6c9e85) on port 1136
Only local connections are allowed.
Apr 14, 2018 3:00:16 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS

I agree that your solution would work in a happy path scenario.  However I think it would cause more confusion in the long run and I would expect to see bugs raised along the lines of:

Chromedriver version 2.35 was downloaded but it's using Chromedriver version 2.42 in my tests!!!

If you can convince me otherwise and provide code to mitigate the listed problems I'll happily look at it again, we are in danger of adding complex code into the codebase that provides very little utility though.

Whatever goes in the extracted path, I would like to be able to propagate this to Java/Selenium when it is executing. Currently I am setting
<webdriver.chrome.driver>/path/to/binary</webdriver.chrome.driver> manually in  in the failsafe-plugin configuration.
And already this is hard to make OS independent, as the Java code needs to know about the path choices of this plugin here. Better to propagate it somehow, e.g. use
${os.name} and such properties instead of "linux" / "osx" .

Discussion for the extracted path is in comments for #89


Model cannot be automatically unloading

What is the issue?
I ran the following model, but keep_alive is at the default value. I haven't requested the above model for more than 10 hours, why is the following model not automatically uninstalled? Why does the UNTIL column of ollama ps change to the model's start time (how long ago was the model started)? How can I manually uninstall the above model?
NAME                                    ID              SIZE    PROCESSOR       UNTIL
LongWriter-llama3.1-8b-quantized:latest 1f0dfed4427c    6.7 GB  100% GPU        4 minutes from now
LongWriter-glm4-9b-quantized:latest     e37d70795165    29 GB   100% GPU        19 hours ago
qwen2-tools:7b                          474fd321869c    5.7 GB  100% GPU        19 hours ago
llama3.1:latest                         91ab477bec9d    6.7 GB  100% GPU        19 hours ago
LongWriter-glm4-9b:latest               1d3f6bf6ada8    6.6 GB  100% GPU        19 hours ago

OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.10

https://github.com/ollama/ollama/blob/main/docs/faq.md#how-do-i-keep-a-model-loaded-in-memory-or-make-it-unload-immediately

Version 0.1.10 is pretty old, and we've fixed a lot of bugs since then.  Please upgrade to the latest version and let us know if you're still having troubles with unload timeouts not being respected.


zarr v3

this library supports zarr v2 right now. it should support zarr v3.

initial support for zarrv3 data structures added in #17


parallelization for unit tests

Signed-off-by: Sally MacFarlane<EMAIL_ADDRESS>

PR description
Fixed Issue(s)

Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[ ] I thought about the changelog and included a changelog update if required.

4826 tests in 4 minutes. https://app.circleci.com/pipelines/github/hyperledger/besu/20033/workflows/98bad614-d7cb-4190-9726-db18ad19f94c/jobs/122598


ActiveDirectoryDsc: Fix comment based help

Pull Request (PR) description

Changes to ADGroup

Added comment-based help (issue #338).
Update the documentation with the correct default value for the parameter
GroupScope.

Changes to ADDomainDefaultPasswordPolicy

Added comment-based help (issue #336).

This Pull Request (PR) fixes the following issues

Fixes #338
Fixes #336

Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in resource directory README.md.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #464 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #464   +/-   ##
===================================
  Coverage    98%    98%
===================================
  Files        20     20
  Lines      2815   2815
  Branches     10     10
===================================
  Hits       2767   2767
  Misses       38     38
  Partials     10     10


npm run server breaking in macOS Sequoia

The docker image is failing to be created in macOS Sequoia.
Steps to reproduce:
npm run sever
Observed output:
=> ERROR [grafana 3/8] RUN if [ "false" = "true" ]; then     if grep -i -q alpine /etc/issue; then     apk add supervisor inotify-tools git;    0.1s
------
 > [grafana 3/8] RUN if [ "false" = "true" ]; then     if grep -i -q alpine /etc/issue; then     apk add supervisor inotify-tools git;     elif grep -i -q ubuntu /etc/issue; then     DEBIAN_FRONTEND=noninteractive &&     apt-get update &&     apt-get install -y supervisor inotify-tools git &&     rm -rf /var/lib/apt/lists/*;     else     echo 'ERROR: Unsupported base image' && /bin/false;     fi     fi:
------
failed to solve: process "/bin/sh -c if [ \"${development}\" = \"true\" ]; then     if grep -i -q alpine /etc/issue; then     apk add supervisor inotify-tools git;     elif grep -i -q ubuntu /etc/issue; then     DEBIAN_FRONTEND=noninteractive &&     apt-get update &&     apt-get install -y supervisor inotify-tools git &&     rm -rf /var/lib/apt/lists/*;     else     echo 'ERROR: Unsupported base image' && /bin/false;     fi     fi" did not complete successfully: unable to find user root: no matching entries in passwd file

@oshirohugo Is it on the latest create-plugin scaffold? Do you have commands to reproduce?
I am on Sequoia 15.0.1, just tried out latest scaffolding for a datasource and it works as before.

Looks like it might be setup specific and not related to plugin-tools. reopen otherwise


List all checks done by  this scanner

Is your feature request related to a problem? Please describe.
Want to get a list of all checks along with description.
Describe the solution you'd like
List of checks that will list:
test_id
test_name
issue_text
issue_severity
Describe alternatives you've considered
Trying to get it, but didn't succeeded.
Additional context
Add any other context or screenshots about the feature request here.

I managed to get list like this, but maybe there is a better way to accomplish it. I run bandit on examples to get this.
{
  "B101": {
    "severity": "LOW",
    "description": "Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.",
    "categories": [],
    "title": "assert_used"
  },
  "B104": {
    "severity": "MEDIUM",
    "description": "Possible binding to all interfaces.",
    "categories": [],
    "title": "hardcoded_bind_all_interfaces"
  },
  "B305": {
    "severity": "MEDIUM",
    "description": "Use of insecure cipher mode cryptography.hazmat.primitives.ciphers.modes.ECB.",
    "categories": [],
    "title": "blacklist"
  },
  "B413": {
    "severity": "HIGH",
    "description": "The pyCrypto library and its module RSA are no longer actively maintained and have been deprecated. Consider using pyca/cryptography library.",
    "categories": [],
    "title": "blacklist"
  },
  "B414": {
    "severity": "HIGH",
    "description": "The pycryptodome library is not considered a secure alternative to pycrypto.Consider using pyca/cryptography library.",
    "categories": [],
    "title": "blacklist"
  },
  "B304": {
    "severity": "HIGH",
    "description": "Use of insecure cipher cryptography.hazmat.primitives.ciphers.algorithms.IDEA. Replace with a known secure cipher such as AES.",
    "categories": [],
    "title": "blacklist"
  },
  "B303": {
    "severity": "MEDIUM",
    "description": "Use of insecure MD2, MD4, MD5, or SHA1 hash function.",
    "categories": [],
    "title": "blacklist"
  },
  "B610": {
    "severity": "MEDIUM",
    "description": "Use of extra potential SQL attack vector.",
    "categories": [],
    "title": "django_extra_used"
  },
  "B611": {
    "severity": "MEDIUM",
    "description": "Use of RawSQL potential SQL attack vector.",
    "categories": [],
    "title": "django_rawsql_used"
  },
  "B307": {
    "severity": "MEDIUM",
    "description": "Use of possibly insecure function - consider using safer ast.literal_eval.",
    "categories": [],
    "title": "blacklist"
  },
  "B102": {
    "severity": "MEDIUM",
    "description": "Use of exec detected.",
    "categories": [],
    "title": "exec_used"
  },
  "B201": {
    "severity": "HIGH",
    "description": "A Flask app appears to be run with debug=True, which exposes the Werkzeug debugger and allows the execution of arbitrary code.",
    "categories": [],
    "title": "flask_debug_true"
  },
  "B402": {
    "severity": "HIGH",
    "description": "A FTP-related module is being imported.  FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B321": {
    "severity": "HIGH",
    "description": "FTP-related functions are being called. FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B107": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_default"
  },
  "B105": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_string"
  },
  "B106": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_funcarg"
  },
  "B108": {
    "severity": "MEDIUM",
    "description": "Probable insecure usage of temp file/directory.",
    "categories": [],
    "title": "hardcoded_tmp_directory"
  },
  "B324": {
    "severity": "MEDIUM",
    "description": "Use of insecure MD4 or MD5 hash function.",
    "categories": [],
    "title": "hashlib_new"
  },
  "B309": {
    "severity": "MEDIUM",
    "description": "Use of HTTPSConnection on older versions of Python prior to 2.7.9 and 3.4.3 do not provide security, see https://wiki.openstack.org/wiki/OSSN/OSSN-0033",
    "categories": [],
    "title": "blacklist"
  },
  "B412": {
    "severity": "HIGH",
    "description": "Consider possible security implications associated with twisted.web.twcgi.CGIScript module.",
    "categories": [],
    "title": "blacklist"
  },
  "B404": {
    "severity": "LOW",
    "description": "Consider possible security implications associated with subprocess module.",
    "categories": [],
    "title": "blacklist"
  },
  "B403": {
    "severity": "LOW",
    "description": "Consider possible security implications associated with pickle module.",
    "categories": [],
    "title": "blacklist"
  },
  "B602": {
    "severity": "LOW",
    "description": "subprocess call with shell=True seems safe, but may be changed in the future, consider rewriting without shell",
    "categories": [],
    "title": "subprocess_popen_with_shell_equals_true"
  },
  "B301": {
    "severity": "MEDIUM",
    "description": "Pickle library appears to be in use, possible security issue.",
    "categories": [],
    "title": "blacklist"
  },
  "B322": {
    "severity": "HIGH",
    "description": "The input method in Python 2 will read from standard input, evaluate and run the resulting string as python source code. This is similar, though in many ways worse, then using eval. On Python 2, use raw_input instead, input is safe in Python 3.",
    "categories": [],
    "title": "blacklist"
  },
  "B701": {
    "severity": "HIGH",
    "description": "Using jinja2 templates with autoescape=False is dangerous and can lead to XSS. Ensure autoescape=True or use the select_autoescape function to mitigate XSS vulnerabilities.",
    "categories": [],
    "title": "jinja2_autoescape_false"
  },
  "B702": {
    "severity": "MEDIUM",
    "description": "Mako templates allow HTML/JS rendering by default and are inherently open to XSS attacks. Ensure variables in all templates are properly sanitized via the 'n', 'h' or 'x' flags (depending on context). For example, to HTML escape the variable 'data' do ${ data |h }.",
    "categories": [],
    "title": "use_of_mako_templates"
  },
  "B308": {
    "severity": "MEDIUM",
    "description": "Use of mark_safe() may expose cross-site scripting vulnerabilities and should be reviewed.",
    "categories": [],
    "title": "blacklist"
  },
  "B703": {
    "severity": "MEDIUM",
    "description": "Potential XSS on mark_safe function.",
    "categories": [],
    "title": "django_mark_safe"
  },
  "B302": {
    "severity": "MEDIUM",
    "description": "Deserialization with the marshal module is possibly dangerous.",
    "categories": [],
    "title": "blacklist"
  },
  "B306": {
    "severity": "MEDIUM",
    "description": "Use of insecure and deprecated function (mktemp).",
    "categories": [],
    "title": "blacklist"
  },
  "B506": {
    "severity": "MEDIUM",
    "description": "Use of unsafe yaml load. Allows instantiation of arbitrary objects. Consider yaml.safe_load().",
    "categories": [],
    "title": "yaml_load"
  },
  "B317": {
    "severity": "MEDIUM",
    "description": "Using xml.sax.make_parser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.sax.make_parser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B103": {
    "severity": "HIGH",
    "description": "Chmod setting a permissive mask 0777 on file (key_file).",
    "categories": [],
    "title": "set_bad_file_permissions"
  },
  "B606": {
    "severity": "LOW",
    "description": "Starting a process without a shell.",
    "categories": [],
    "title": "start_process_with_no_shell"
  },
  "B605": {
    "severity": "LOW",
    "description": "Starting a process with a shell: Seems safe, but may be changed in the future, consider rewriting without shell",
    "categories": [],
    "title": "start_process_with_a_shell"
  },
  "B601": {
    "severity": "MEDIUM",
    "description": "Possible shell injection via Paramiko call, check inputs are properly sanitized.",
    "categories": [],
    "title": "paramiko_calls"
  },
  "B603": {
    "severity": "LOW",
    "description": "subprocess call - check for execution of untrusted input.",
    "categories": [],
    "title": "subprocess_without_shell_equals_true"
  },
  "B607": {
    "severity": "LOW",
    "description": "Starting a process with a partial executable path",
    "categories": [],
    "title": "start_process_with_partial_path"
  },
  "B311": {
    "severity": "LOW",
    "description": "Standard pseudo-random generators are not suitable for security/cryptographic purposes.",
    "categories": [],
    "title": "blacklist"
  },
  "B501": {
    "severity": "HIGH",
    "description": "Requests call with verify=False disabling SSL certificate checks, security issue.",
    "categories": [],
    "title": "request_with_no_cert_validation"
  },
  "B608": {
    "severity": "MEDIUM",
    "description": "Possible SQL injection vector through string-based query construction.",
    "categories": [],
    "title": "hardcoded_sql_expressions"
  },
  "B502": {
    "severity": "MEDIUM",
    "description": "Function call with insecure SSL/TLS protocol identified, possible security issue.",
    "categories": [],
    "title": "ssl_with_bad_version"
  },
  "B504": {
    "severity": "LOW",
    "description": "ssl.wrap_socket call with no SSL/TLS protocol version specified, the default SSLv23 could be insecure, possible security issue.",
    "categories": [],
    "title": "ssl_with_no_version"
  },
  "B503": {
    "severity": "MEDIUM",
    "description": "Function definition identified with insecure SSL/TLS protocol version by default, possible security issue.",
    "categories": [],
    "title": "ssl_with_bad_defaults"
  },
  "B604": {
    "severity": "MEDIUM",
    "description": "Function call with shell=True parameter identified, possible security issue.",
    "categories": [],
    "title": "any_other_function_with_shell_equals_true"
  },
  "B401": {
    "severity": "HIGH",
    "description": "A telnet-related module is being imported.  Telnet is considered insecure. Use SSH or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B312": {
    "severity": "HIGH",
    "description": "Telnet-related functions are being called. Telnet is considered insecure. Use SSH or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B325": {
    "severity": "MEDIUM",
    "description": "Use of os.tempnam() and os.tmpnam() is vulnerable to symlink attacks. Consider using tmpfile() instead.",
    "categories": [],
    "title": "blacklist"
  },
  "B112": {
    "severity": "LOW",
    "description": "Try, Except, Continue detected.",
    "categories": [],
    "title": "try_except_continue"
  },
  "B110": {
    "severity": "LOW",
    "description": "Try, Except, Pass detected.",
    "categories": [],
    "title": "try_except_pass"
  },
  "B323": {
    "severity": "MEDIUM",
    "description": "By default, Python will create a secure, verified ssl context for use in such classes as HTTPSConnection. However, it still allows using an insecure context via the _create_unverified_context that reverts to the previous behavior that does not validate certificates or perform hostname checks.",
    "categories": [],
    "title": "blacklist"
  },
  "B310": {
    "severity": "MEDIUM",
    "description": "Audit url open for permitted schemes. Allowing use of file:/ or custom schemes is often unexpected.",
    "categories": [],
    "title": "blacklist"
  },
  "B505": {
    "severity": "HIGH",
    "description": "RSA key sizes below 1024 bits are considered breakable. ",
    "categories": [],
    "title": "weak_cryptographic_key"
  },
  "B609": {
    "severity": "HIGH",
    "description": "Possible wildcard injection in call: subprocess.Popen",
    "categories": [],
    "title": "linux_commands_wildcard_injection"
  },
  "B405": {
    "severity": "LOW",
    "description": "Using xml.etree.ElementTree to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.ElementTree with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B313": {
    "severity": "MEDIUM",
    "description": "Using xml.etree.cElementTree.XMLParser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.cElementTree.XMLParser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B314": {
    "severity": "MEDIUM",
    "description": "Using xml.etree.ElementTree.XMLParser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.ElementTree.XMLParser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B407": {
    "severity": "LOW",
    "description": "Using xml.dom.expatbuilder to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.expatbuilder with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B316": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.expatbuilder.parseString to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.expatbuilder.parseString with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B406": {
    "severity": "LOW",
    "description": "Using sax to parse untrusted XML data is known to be vulnerable to XML attacks. Replace sax with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B315": {
    "severity": "MEDIUM",
    "description": "Using xml.sax.expatreader.create_parser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.sax.expatreader.create_parser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B410": {
    "severity": "LOW",
    "description": "Using etree to parse untrusted XML data is known to be vulnerable to XML attacks. Replace etree with the equivalent defusedxml package.",
    "categories": [],
    "title": "blacklist"
  },
  "B320": {
    "severity": "MEDIUM",
    "description": "Using lxml.etree.fromstring to parse untrusted XML data is known to be vulnerable to XML attacks. Replace lxml.etree.fromstring with its defusedxml equivalent function.",
    "categories": [],
    "title": "blacklist"
  },
  "B408": {
    "severity": "LOW",
    "description": "Using parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace parse with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B318": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.minidom.parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.minidom.parse with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B409": {
    "severity": "LOW",
    "description": "Using parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace parse with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B319": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.pulldom.parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.pulldom.parse with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B411": {
    "severity": "HIGH",
    "description": "Using xmlrpclib to parse untrusted XML data is known to be vulnerable to XML attacks. Use defused.xmlrpc.monkey_patch() function to monkey-patch xmlrpclib and mitigate XML vulnerabilities.",
    "categories": [],
    "title": "blacklist"
  }
}

Are you looking for a CLI command to list all of the test plugins?  If you run bandit -h it will list the plugin names, but maybe not to the detail you're looking for.  We also document each check here:
https://bandit.readthedocs.io/en/latest/plugins/index.html#complete-test-plugin-listing
https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html
https://bandit.readthedocs.io/en/latest/blacklists/blacklist_imports.html

I managed to get list like this, but maybe there is a better way to accomplish it. I run bandit on examples to get this.
{
  "B101": {
    "severity": "LOW",
    "description": "Use of assert detected. The enclosed code will be removed when compiling to optimised byte code.",
    "categories": [],
    "title": "assert_used"
  },
  "B104": {
    "severity": "MEDIUM",
    "description": "Possible binding to all interfaces.",
    "categories": [],
    "title": "hardcoded_bind_all_interfaces"
  },
  "B305": {
    "severity": "MEDIUM",
    "description": "Use of insecure cipher mode cryptography.hazmat.primitives.ciphers.modes.ECB.",
    "categories": [],
    "title": "blacklist"
  },
  "B413": {
    "severity": "HIGH",
    "description": "The pyCrypto library and its module RSA are no longer actively maintained and have been deprecated. Consider using pyca/cryptography library.",
    "categories": [],
    "title": "blacklist"
  },
  "B414": {
    "severity": "HIGH",
    "description": "The pycryptodome library is not considered a secure alternative to pycrypto.Consider using pyca/cryptography library.",
    "categories": [],
    "title": "blacklist"
  },
  "B304": {
    "severity": "HIGH",
    "description": "Use of insecure cipher cryptography.hazmat.primitives.ciphers.algorithms.IDEA. Replace with a known secure cipher such as AES.",
    "categories": [],
    "title": "blacklist"
  },
  "B303": {
    "severity": "MEDIUM",
    "description": "Use of insecure MD2, MD4, MD5, or SHA1 hash function.",
    "categories": [],
    "title": "blacklist"
  },
  "B610": {
    "severity": "MEDIUM",
    "description": "Use of extra potential SQL attack vector.",
    "categories": [],
    "title": "django_extra_used"
  },
  "B611": {
    "severity": "MEDIUM",
    "description": "Use of RawSQL potential SQL attack vector.",
    "categories": [],
    "title": "django_rawsql_used"
  },
  "B307": {
    "severity": "MEDIUM",
    "description": "Use of possibly insecure function - consider using safer ast.literal_eval.",
    "categories": [],
    "title": "blacklist"
  },
  "B102": {
    "severity": "MEDIUM",
    "description": "Use of exec detected.",
    "categories": [],
    "title": "exec_used"
  },
  "B201": {
    "severity": "HIGH",
    "description": "A Flask app appears to be run with debug=True, which exposes the Werkzeug debugger and allows the execution of arbitrary code.",
    "categories": [],
    "title": "flask_debug_true"
  },
  "B402": {
    "severity": "HIGH",
    "description": "A FTP-related module is being imported.  FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B321": {
    "severity": "HIGH",
    "description": "FTP-related functions are being called. FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B107": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_default"
  },
  "B105": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_string"
  },
  "B106": {
    "severity": "LOW",
    "description": "Possible hardcoded password: 'blerg'",
    "categories": [],
    "title": "hardcoded_password_funcarg"
  },
  "B108": {
    "severity": "MEDIUM",
    "description": "Probable insecure usage of temp file/directory.",
    "categories": [],
    "title": "hardcoded_tmp_directory"
  },
  "B324": {
    "severity": "MEDIUM",
    "description": "Use of insecure MD4 or MD5 hash function.",
    "categories": [],
    "title": "hashlib_new"
  },
  "B309": {
    "severity": "MEDIUM",
    "description": "Use of HTTPSConnection on older versions of Python prior to 2.7.9 and 3.4.3 do not provide security, see https://wiki.openstack.org/wiki/OSSN/OSSN-0033",
    "categories": [],
    "title": "blacklist"
  },
  "B412": {
    "severity": "HIGH",
    "description": "Consider possible security implications associated with twisted.web.twcgi.CGIScript module.",
    "categories": [],
    "title": "blacklist"
  },
  "B404": {
    "severity": "LOW",
    "description": "Consider possible security implications associated with subprocess module.",
    "categories": [],
    "title": "blacklist"
  },
  "B403": {
    "severity": "LOW",
    "description": "Consider possible security implications associated with pickle module.",
    "categories": [],
    "title": "blacklist"
  },
  "B602": {
    "severity": "LOW",
    "description": "subprocess call with shell=True seems safe, but may be changed in the future, consider rewriting without shell",
    "categories": [],
    "title": "subprocess_popen_with_shell_equals_true"
  },
  "B301": {
    "severity": "MEDIUM",
    "description": "Pickle library appears to be in use, possible security issue.",
    "categories": [],
    "title": "blacklist"
  },
  "B322": {
    "severity": "HIGH",
    "description": "The input method in Python 2 will read from standard input, evaluate and run the resulting string as python source code. This is similar, though in many ways worse, then using eval. On Python 2, use raw_input instead, input is safe in Python 3.",
    "categories": [],
    "title": "blacklist"
  },
  "B701": {
    "severity": "HIGH",
    "description": "Using jinja2 templates with autoescape=False is dangerous and can lead to XSS. Ensure autoescape=True or use the select_autoescape function to mitigate XSS vulnerabilities.",
    "categories": [],
    "title": "jinja2_autoescape_false"
  },
  "B702": {
    "severity": "MEDIUM",
    "description": "Mako templates allow HTML/JS rendering by default and are inherently open to XSS attacks. Ensure variables in all templates are properly sanitized via the 'n', 'h' or 'x' flags (depending on context). For example, to HTML escape the variable 'data' do ${ data |h }.",
    "categories": [],
    "title": "use_of_mako_templates"
  },
  "B308": {
    "severity": "MEDIUM",
    "description": "Use of mark_safe() may expose cross-site scripting vulnerabilities and should be reviewed.",
    "categories": [],
    "title": "blacklist"
  },
  "B703": {
    "severity": "MEDIUM",
    "description": "Potential XSS on mark_safe function.",
    "categories": [],
    "title": "django_mark_safe"
  },
  "B302": {
    "severity": "MEDIUM",
    "description": "Deserialization with the marshal module is possibly dangerous.",
    "categories": [],
    "title": "blacklist"
  },
  "B306": {
    "severity": "MEDIUM",
    "description": "Use of insecure and deprecated function (mktemp).",
    "categories": [],
    "title": "blacklist"
  },
  "B506": {
    "severity": "MEDIUM",
    "description": "Use of unsafe yaml load. Allows instantiation of arbitrary objects. Consider yaml.safe_load().",
    "categories": [],
    "title": "yaml_load"
  },
  "B317": {
    "severity": "MEDIUM",
    "description": "Using xml.sax.make_parser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.sax.make_parser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B103": {
    "severity": "HIGH",
    "description": "Chmod setting a permissive mask 0777 on file (key_file).",
    "categories": [],
    "title": "set_bad_file_permissions"
  },
  "B606": {
    "severity": "LOW",
    "description": "Starting a process without a shell.",
    "categories": [],
    "title": "start_process_with_no_shell"
  },
  "B605": {
    "severity": "LOW",
    "description": "Starting a process with a shell: Seems safe, but may be changed in the future, consider rewriting without shell",
    "categories": [],
    "title": "start_process_with_a_shell"
  },
  "B601": {
    "severity": "MEDIUM",
    "description": "Possible shell injection via Paramiko call, check inputs are properly sanitized.",
    "categories": [],
    "title": "paramiko_calls"
  },
  "B603": {
    "severity": "LOW",
    "description": "subprocess call - check for execution of untrusted input.",
    "categories": [],
    "title": "subprocess_without_shell_equals_true"
  },
  "B607": {
    "severity": "LOW",
    "description": "Starting a process with a partial executable path",
    "categories": [],
    "title": "start_process_with_partial_path"
  },
  "B311": {
    "severity": "LOW",
    "description": "Standard pseudo-random generators are not suitable for security/cryptographic purposes.",
    "categories": [],
    "title": "blacklist"
  },
  "B501": {
    "severity": "HIGH",
    "description": "Requests call with verify=False disabling SSL certificate checks, security issue.",
    "categories": [],
    "title": "request_with_no_cert_validation"
  },
  "B608": {
    "severity": "MEDIUM",
    "description": "Possible SQL injection vector through string-based query construction.",
    "categories": [],
    "title": "hardcoded_sql_expressions"
  },
  "B502": {
    "severity": "MEDIUM",
    "description": "Function call with insecure SSL/TLS protocol identified, possible security issue.",
    "categories": [],
    "title": "ssl_with_bad_version"
  },
  "B504": {
    "severity": "LOW",
    "description": "ssl.wrap_socket call with no SSL/TLS protocol version specified, the default SSLv23 could be insecure, possible security issue.",
    "categories": [],
    "title": "ssl_with_no_version"
  },
  "B503": {
    "severity": "MEDIUM",
    "description": "Function definition identified with insecure SSL/TLS protocol version by default, possible security issue.",
    "categories": [],
    "title": "ssl_with_bad_defaults"
  },
  "B604": {
    "severity": "MEDIUM",
    "description": "Function call with shell=True parameter identified, possible security issue.",
    "categories": [],
    "title": "any_other_function_with_shell_equals_true"
  },
  "B401": {
    "severity": "HIGH",
    "description": "A telnet-related module is being imported.  Telnet is considered insecure. Use SSH or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B312": {
    "severity": "HIGH",
    "description": "Telnet-related functions are being called. Telnet is considered insecure. Use SSH or some other encrypted protocol.",
    "categories": [],
    "title": "blacklist"
  },
  "B325": {
    "severity": "MEDIUM",
    "description": "Use of os.tempnam() and os.tmpnam() is vulnerable to symlink attacks. Consider using tmpfile() instead.",
    "categories": [],
    "title": "blacklist"
  },
  "B112": {
    "severity": "LOW",
    "description": "Try, Except, Continue detected.",
    "categories": [],
    "title": "try_except_continue"
  },
  "B110": {
    "severity": "LOW",
    "description": "Try, Except, Pass detected.",
    "categories": [],
    "title": "try_except_pass"
  },
  "B323": {
    "severity": "MEDIUM",
    "description": "By default, Python will create a secure, verified ssl context for use in such classes as HTTPSConnection. However, it still allows using an insecure context via the _create_unverified_context that reverts to the previous behavior that does not validate certificates or perform hostname checks.",
    "categories": [],
    "title": "blacklist"
  },
  "B310": {
    "severity": "MEDIUM",
    "description": "Audit url open for permitted schemes. Allowing use of file:/ or custom schemes is often unexpected.",
    "categories": [],
    "title": "blacklist"
  },
  "B505": {
    "severity": "HIGH",
    "description": "RSA key sizes below 1024 bits are considered breakable. ",
    "categories": [],
    "title": "weak_cryptographic_key"
  },
  "B609": {
    "severity": "HIGH",
    "description": "Possible wildcard injection in call: subprocess.Popen",
    "categories": [],
    "title": "linux_commands_wildcard_injection"
  },
  "B405": {
    "severity": "LOW",
    "description": "Using xml.etree.ElementTree to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.ElementTree with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B313": {
    "severity": "MEDIUM",
    "description": "Using xml.etree.cElementTree.XMLParser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.cElementTree.XMLParser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B314": {
    "severity": "MEDIUM",
    "description": "Using xml.etree.ElementTree.XMLParser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.etree.ElementTree.XMLParser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B407": {
    "severity": "LOW",
    "description": "Using xml.dom.expatbuilder to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.expatbuilder with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B316": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.expatbuilder.parseString to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.expatbuilder.parseString with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B406": {
    "severity": "LOW",
    "description": "Using sax to parse untrusted XML data is known to be vulnerable to XML attacks. Replace sax with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B315": {
    "severity": "MEDIUM",
    "description": "Using xml.sax.expatreader.create_parser to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.sax.expatreader.create_parser with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B410": {
    "severity": "LOW",
    "description": "Using etree to parse untrusted XML data is known to be vulnerable to XML attacks. Replace etree with the equivalent defusedxml package.",
    "categories": [],
    "title": "blacklist"
  },
  "B320": {
    "severity": "MEDIUM",
    "description": "Using lxml.etree.fromstring to parse untrusted XML data is known to be vulnerable to XML attacks. Replace lxml.etree.fromstring with its defusedxml equivalent function.",
    "categories": [],
    "title": "blacklist"
  },
  "B408": {
    "severity": "LOW",
    "description": "Using parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace parse with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B318": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.minidom.parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.minidom.parse with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B409": {
    "severity": "LOW",
    "description": "Using parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace parse with the equivalent defusedxml package, or make sure defusedxml.defuse_stdlib() is called.",
    "categories": [],
    "title": "blacklist"
  },
  "B319": {
    "severity": "MEDIUM",
    "description": "Using xml.dom.pulldom.parse to parse untrusted XML data is known to be vulnerable to XML attacks. Replace xml.dom.pulldom.parse with its defusedxml equivalent function or make sure defusedxml.defuse_stdlib() is called",
    "categories": [],
    "title": "blacklist"
  },
  "B411": {
    "severity": "HIGH",
    "description": "Using xmlrpclib to parse untrusted XML data is known to be vulnerable to XML attacks. Use defused.xmlrpc.monkey_patch() function to monkey-patch xmlrpclib and mitigate XML vulnerabilities.",
    "categories": [],
    "title": "blacklist"
  }
}

How can i get updated list for this one?


Update .gitlab-ci.yml

Status
Ready/In Progress/In Hold (Reason for hold)
Related Content Pull Request
Related PR: link to the PR at demisto/content
Related Issues
Related: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.

@michal-dagan to test properly you also need to make a change to a docker image


42: Resolve "bonds are added sporadically without a reason" - [merged]

In GitLab by @Asacolips on Mar 1, 2021, 08:59
Merges 42-fix-bonds -> master
Closes #42

In GitLab by @Asacolips on Mar 1, 2021, 09:00
mentioned in commit a1653f8400aa5ae1732d3726c51dce9a3778644a


wandb: Network error (ConnectTimeout), entering retry loop.

The error caused by wandb sync run-**** when i login to the self-hosting server.
wandb: Network error (ConnectTimeout), entering retry loop.
wandb: Network error (ReadTimeout), entering retry loop.
...
I can sync this run to https://api.wandb.ai，but i cant sync to self-hosting server
The detailed error like the below images:

Hey @JieGenius this is due to a firewall or networking configuration issue on your end.  Can you try running:
curl -v http://<IP_ADDRESS>:9998/healthz

And paste the input.  You may need to open the firewall or otherwise configure your network to allow connections from other machines.


Optimistic updates / Refetching queries after mutations

Thanks for the amazing work so far!
I am using antd Form element, which takes props, then keeps an internal form state. When my form is ready, i submit a mutation. The problem is, this triggers a new render with the initital props, causing the fields to flicker back to the original values until the mutation is complete (http request)
This all makes sense. I guess i need to overwrite the local state immediately?

The default cache is document based so it doesn't support optimistic updates as we only know about very specific query and variables combinations.
So from our perspective it makes more Re sense to add this functionality to a normalised cache, like the one that Apollo has.
I'm currently working on a normalised cache for urql and it's not quite ready yet, but you can track it's progress here: https://github.com/kitten/urql-exchange-graphcache

That sounds great.
I was thinking that there might be a way to override the cache even on the document however - a another argument to the mutation? Im sure you know the limitations however

@tonypee So basically, you're looking for a cacheExchange that maps mutations to queries that should be refetched?
I think that should be a possible option that can be implemented outside of the exchange infrastructure. It could be built into useMutation / <Mutation> but essentially you can trigger executeQuery after a mutation with the publish operator (which subscribes without issuing any callbacks / events) which would then update that query across components.

@kitten I see the normalized cache is out now so can we do Optimistic updates now?

@deadcoder0904 Hiya 👋 Yes, @urql/exchange-graphcache supports everything that you might expect from a normalised cache including optimistic updates https://github.com/FormidableLabs/urql-exchange-graphcache#usage

Thanks, Phil for your work on this. I really love the name "Wonka" for some reason 😂