Add ability to combine under-sampled bins for reliability calibration

Interacts with #1314 and #1315 . Created as draft PR until #1314 and #1315 are merged.
Description
Adds a method to combine under-sampled bins, so that any information from the under-sampled bins is still retained in the calibration. Note the _sum_pairs method has also been added in #1314. The version of _sum_pairs in this PR contains a minor difference, which should be used in preference to the version in #1314. At least one unit test will require updating following merging #1315, so that the Test__calculate_reliability_probabilities::test_combine_undersampled_bins unit test can test the combination of the under-sampled bins.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  24
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  24
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  29
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  1

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  29
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  1

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  29
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  1

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  29
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  3

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  1

Clones added
============
- improver_tests/calibration/reliability_calibration/test_ManipulateReliabilityTable.py  28
- improver_tests/calibration/reliability_calibration/test_ApplyReliabilityCalibration.py  3

See the complete overview on Codacy


Create README.md

Added instructions on how to integrate CR into shopify store

Also, this should probably be in some folder like integrations/shopify.


[big num] allow markdown in subheader field

allow markdown in subheader field
wrap long lines

at the moment it's svg but I think it's possible to embed html in svg somehow, or layer it on top

Notice: this issue has been closed because it has been inactive for 423 days. Feel free to comment and request for this issue to be reopened.


Add upload document area

Add upload document area
Screenshots will be added when the page design is complete.

Duplicate of #149


Can't edit property

Can't edit component property.
Steps to reproduce:

ng new myapp
cd myapp
ng serve
Open Chrome developer tools and go to the Augury tab. In the component tree, click the AppComponent.
In the properties on the right, notice the "title" property with the "app works!" value
Click either on the property name ("title") or it's value, and the field becomes editable (thus suggesting it is editable).
Change it to anything and press enter. Notice it reverts to the initial value once you press enter.

I've also set up a local server and build the app with "ng build" and served my app through apache, instead of ng serve, but it makes no difference.
Augury: 1.1.3
angular-cli: tried with 1.0.0-beta.11-webpack.8 or 1.0.0-beta.11-webpack.9-4
Angular: either 2.0.0-rc.6 or rc.7 (haven't tested on rc.5 or lower)
Google Chrome: 53.0.2785.113 m (64-bit)
OS: Windows 10 Pro

Thanks for the report, currently we have an issue with editing state in OnPush components. Check where it says "Change Detection: " in the info panel right below your component name, if that says "OnPush" then this is a known issue. If it says "Default" then it seems we might have a new one.

@xorgy
Unfortunately, it is "Default".

I don't see this issue on some test applications but I'll take a look at what you suggest.
Thanks.

@MrCroft So I am indeed seeing an issue. It's not that you can't edit the property, but it seems that it only succeeds about half the time. I'm going to update the title of this issue to match that. This is going to be fun to debug.

As a nuance, it only seems to fail when the value you enter is the same as the original value, I think I know why this would manifest.
https://drive.google.com/a/rangle.io/file/d/0BwfHP4-tCgx-azMxZGRlNXB4dG8/view

Weird thing: If I set ChangeDetectionStrategy to be OnPush, Augury still says "Default" (but this is ONLY happening with rc.7 - so I don't think it's relevant here. It does say "OnPush" if I use rc.6).
Further more, back to the "Default" change detection strategy, if I change the "title" property in a later event/method, it surely gets updated in the view, but it doesn't get updated in Augury:
export class AppComponent {
    title = 'app works!';

    // Placed a button in my template
    // <button (click)="changeTitle()">CHANGE TITLE</button>
    changeTitle() {
        this.title = "does not get updated in Augury"; // < the value of the title property doesn't get updated in Augury
    }
}

I've just tried the above code while simply "ng serve" with latest angular-cli (1.0.0-beta.11-webpack.9-4) and latest 2 versions of Angular 2 (rc.6 and rc.7). It behaves the same with both rc.6 and rc.7 (removed node_modules folder and ran npm cache clean between changing versions, so I would be sure).
Hope this helps, I can't think of anything else that might actually help you to narrow it down.
Just an Angular 2 newb here :) learning

That seems like a separate issue, it's possible that they've changed the reflect metadata between rc.6 and rc.7. 😞

This is a build of the extension from the state of our development branch.
https://1253-41743300-gh.circle-artifacts.com/0//tmp/circle-artifacts.o49SEp7/augury-1253.crx
If you remove Augury, download this file, then drag the file directly into a window at chrome://extensions then try the issue again, we will be on the same page. We should do a release today if the issue is partially resolved.

Sorry for the delay, I was having trouble installing the build you gave me. Chrome issues.
So... with the above build (and the "Default" change detection strategy) for both rc.6 and rc.7:
- changing property value in Augury works and value instantly gets updated in the view (which this issue was about)
- changing the property value in my changeTitle() method, doesn't update the value in Augury while having the Developer Tools open. If I close it and open it again, then I see the new title. But this would be another issue I think.

@MrCroft RE-PS: Basically it doesn't update the application when you enter the original value of the field after editing it. So for example if it started with 'app works!' and you changed it to 'app works!!', then tried to change it back to 'app works!' it would still show 'app works!!' after you submit.
Anyway, this seems like a separate issue. And no, this release will sadly not address the inability to edit OnPush components. There is a separate issue logged for that.
Anyway, I'm going to consider this closed, since your original bug no longer seems to appear. I'll see if we can push out a proper release in the mean time to address this.

I tell too long stories :)
Definitely, the bug I've actually opened this issue for is fixed by that build.
Thank you!

Sorry to come back on this, I should have been more careful the first time.
At that moment I was only careful enough to check what I initially observed: that the value didn't get updated in the component, once I changed it in Augury.
And then said it's all good, without also checking what @xorgy noticed: that it doesn't get updated when you change the value back to what it was initially.
It seems that's still happening (Default change detection strategy).
Unless this is already mentioned again in some other open issue, would you reopen this or should I open a new issue?
You can notice this in the same repo I gave as an example for another issue I've just opened: https://github.com/MrCroft/lazy (see HomeComponent)
Augury: 1.2.1
Angular: 2.0.1
os: win32 x64
Google Chrome: 53.0.2785.116 m (64-bit)

And I feel the need to add: Thank you for Augury! 😃


add docs for AWS CodeArtifact

Summary
This adds explicit information about using uv with AWS CodeArtifact (both as an extra index to fetch private packages and also to publish packages using twine).
Test Plan
I'm currently using this setup with several private projects that use CodeArtifact.

Thank you for contributing! I touched this up for consistency with our other documentation and tried to make it a bit easier to read. Want to let me know if I made any mistakes?

Thank you for contributing! I touched this up for consistency with our other documentation and tried to make it a bit easier to read. Want to let me know if I made any mistakes?

I just tested your changes and they worked great. Thanks!


[SPARK-7289] handle project -> limit -> sort efficiently

make the TakeOrdered strategy and operator more general, such that it can optionally handle a projection when necessary

Merged build triggered.

Merged build started.

Test build #34755 has started for   PR 6780 at commit d74c960.

Test build #34755 has finished for   PR 6780 at commit d74c960.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34759 has started for   PR 6780 at commit be08a91.

Test build #34759 has finished for   PR 6780 at commit be08a91.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

What's the relationship between this PR and SPARK-7289?

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34890 has started for   PR 6780 at commit 3c7dab0.

Test build #34890 has finished for   PR 6780 at commit 3c7dab0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class JoinedRow extends InternalRow
class JoinedRow2 extends InternalRow
class JoinedRow3 extends InternalRow
class JoinedRow4 extends InternalRow
class JoinedRow5 extends InternalRow
class JoinedRow6 extends InternalRow
class BaseOrdering extends Ordering[InternalRow]
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34892 has started for   PR 6780 at commit 91d798d.

Test build #34892 has finished for   PR 6780 at commit 91d798d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class JoinedRow extends InternalRow
class JoinedRow2 extends InternalRow
class JoinedRow3 extends InternalRow
class JoinedRow4 extends InternalRow
class JoinedRow5 extends InternalRow
class JoinedRow6 extends InternalRow
class BaseOrdering extends Ordering[InternalRow]
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34901 has started for   PR 6780 at commit edfdc6f.

Test build #34901 has finished for   PR 6780 at commit edfdc6f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #34904 has started for   PR 6780 at commit 0d53727.

Test build #34904 has finished for   PR 6780 at commit 0d53727.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test PASSed.

How about the Limit(Sort(Aggregate)), will that be a bug? Sorry, I didn't test it, can you confirm that? Probably it's not a good idea to put 3 functionalities into a single physical operator.

Hmm...this PR doesn't change the handling of Limit(Sort(Aggregate)), it just swap Limit and Project(and combine them) for case Project(Limit(Sort(...))), is it safe to do so?

Merged build triggered.

Merged build started.

Test build #35230 has started for   PR 6780 at commit d11fa9e.

Test build #35230 has finished for   PR 6780 at commit d11fa9e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SerializableConfiguration(@transient var value: Configuration) extends Serializable
class SerializableJobConf(@transient var value: JobConf) extends Serializable
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

cc @marmbrus , NotSerializableException error will exist at HiveCompatibilitySuite when insert into hive table.

Merged build triggered.

Merged build started.

Test build #35395 has started for   PR 6780 at commit ec57bad.

Test build #35395 has finished for   PR 6780 at commit ec57bad.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35400 has started for   PR 6780 at commit 9420510.

Test build #35400 has finished for   PR 6780 at commit 9420510.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #35406 has started for   PR 6780 at commit 9420510.

Merged build triggered.

Merged build started.

Test build #35408 has started for   PR 6780 at commit e5c19c8.

Test build #35406 has finished for   PR 6780 at commit 9420510.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Test build #35408 has finished for   PR 6780 at commit e5c19c8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35410 has started for   PR 6780 at commit b65dd6b.

Test build #35410 has finished for   PR 6780 at commit b65dd6b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35558 has started for   PR 6780 at commit 72c3f69.

Test build #35558 has finished for   PR 6780 at commit 72c3f69.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35634 has started for   PR 6780 at commit 34aa07b.

Test build #35634 has finished for   PR 6780 at commit 34aa07b.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test FAILed.

retest this please.

Merged build triggered.

Merged build started.

Test build #35652 has started for   PR 6780 at commit 34aa07b.

Test build #35652 has finished for   PR 6780 at commit 34aa07b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class TakeOrderedAndProject(

Merged build finished. Test PASSed.

Thanks!  Merged to master.


FreeBSD: Linker errors on cexpl, clogl, and cpowl

Trying to compile an older project with the latest version of Ctypes and getting the following.
.opam/4.03.0+flambda/lib/ctypes/libctypes_stubs.a(ldouble_stubs.o): In function `ctypes_ldouble_powl':
.opam/4.03.0+flambda/build/ctypes.0.11.2/src/ctypes/ldouble_stubs.c:253: warning: powl has lower than advertised precision
.opam/4.03.0+flambda/lib/ctypes/libctypes_stubs.a(ldouble_stubs.o): In function `ctypes_ldouble_complex_cexpl':
.opam/4.03.0+flambda/build/ctypes.0.11.2/src/ctypes/ldouble_stubs.c:(.text+0x1eb3): undefined reference to `cexpl'
.opam/4.03.0+flambda/lib/ctypes/libctypes_stubs.a(ldouble_stubs.o): In function `ctypes_ldouble_complex_clogl':
.opam/4.03.0+flambda/build/ctypes.0.11.2/src/ctypes/ldouble_stubs.c:(.text+0x1f53): undefined reference to `clogl'
.opam/4.03.0+flambda/lib/ctypes/libctypes_stubs.a(ldouble_stubs.o): In function `ctypes_ldouble_complex_cpowl':
.opam/4.03.0+flambda/build/ctypes.0.11.2/src/ctypes/ldouble_stubs.c:(.text+0x2025): undefined reference to `cpowl'

Thanks for the report.  This looks similar to #486 (see the diff).


Suggestion: Sort on Family name or Type in stead of Description

First of all, I'm really pleased with the development of this plugin, it has great potential!
When using/testing it, I have the following small suggestion: Elements are now listed by their Description, which not always makes sense as sometimes the description isn't right, or is the same as other elements. My suggestion therefore is to list by Family and/or Type name which is much better recognizable.
Regards,
René

Hello @ReneSondermijer ,
In the recent update v1.6.0 we added a few more options:

Will this do the trick for you or would you like more options?

Hi @Rien777,
Yes, this having these different options makes searching elements much easier. Adding the Assembly Code to this list would also be really helplful.
Regards,
René


Add ability to customize TabBar

From what I can tell it doesn't seem it's possible to replace the TabBar similar to NavBar.
I get that I can change the icon but I'd like to change the press feedback away from TouchableOpacity.
At the point is my only choice to connect redux and fire actions? Where do I put the TabBar component to allow for hiding in the event I'm showin a modal?

In the scene where you set tabs={true} you can set the component like component={MyTabBar}. I suggest you copy src/TabBar.js as a starting point.

@cridenour thanks so much this works awesome!


bug on the Safari and Chrome on iOS 13.2.2 devices with seekTo on YouTube player

The essence of the bug.
An incorrect value comes to a callback function onProgress once after calling the "seekTo" function.
Example:
onProgress gets the values {playedSeconds}  (values for example):
1.01 initial
2.02 higher
3.03 higher
4.04 higher
5.05 higher
... and so on
Then on the timestamp "5.05" we call "seekTo" to the label "2.00".
After that the function onProgress will receive the following values:
5.06 <- apparently the last challenge of progress
2.00 <- correct
1.98 <- LESS - INCORRECT VALUE (this is bug)
2.01 <- higher
2.02 <- higher
...then everything is right
On version iOS 12.4 there is no bug. Also it is not on Android devices and desktop browsers, including desktop Safari on macOS.

I think this is just an unfortunate nuance in the way that Youtube seeking and getCurrentTime works, together with the fact that onProgress is called every second, but not exactly every second (because of drift) and not exactly in time with any calls to seekTo or  getCurrentTime.
My guess is that after calling seekTo on these certain browsers, Youtube will sort of snap the seeking position to the nearest keyframe or certain point. In your case, this happens to be 1.98 seconds. I'm not sure what this library can do about this.


Looking for maintainers

Hi all,
I'm no longer working in the industry, and probably will not have time to maintain this gem anymore... anyone interested in taking over?

I could be interested, let's talk about it

I'm the maintainer now


Tracing for 2-level launches

My code is using a 2-level launch. The first level tasks are declared as inner and I am creating instances at the first level (ie I don't use virtual mappings). Currently, in debug mode, -dm:memoize throws the following error
solver: /home/bandokihiro/Sources/legion/runtime/legion/legion_tasks.cc:6906: virtual void Legion::Internal::PointTask::complete_replay(Legion::Internal::ApEvent): Assertion `is_leaf()' failed.

@magnatelee


A lot of CSS duplication

Using Jeet to generate grid/column classes generates a lot of code duplication. For example:
*zoom: 1;
float: left;
clear: none;
text-align: inherit;

These style attributes are put on every single element that has a col(x/x) on it. So the following stylus code generates over 1500 lines of CSS code:
.row
  cf()

  .cols
    for c, i in 1..$grid-columns
      &.sm-{c}
        col(c/$grid-columns)

      +above('s')
        &.md-{c}
          col(c/$grid-columns)

      +above('m')
        &.lg-{c}
          col(c/$grid-columns)

  &.collapse
    .cols
      for c, i in 1..$grid-columns
        &.sm-{c}
          span(c/$grid-columns)

        +above('s')
          &.md-{c}
            span(c/$grid-columns)

        +above('m')
          &.lg-{c}
            span(c/$grid-columns)

I am trying to create classnames to create a grid system similar to the one found in Foundation. Is this something that is possible/recommended or is this grid system not meant to be used this way?

See this issue.

As @microcipcip said, that issue should answer your questions.


Provide a way to compile less or sass application

Hello,
Perhaps I have miss something in the documention, but since component style are kinda hard to override from external , it would be great if you can by default process less and sass application.
Exemple to process  less application in  "src/less/**" : gulpfile.js
var p = require('gulp-load-plugins')();
var less = require('gulp-less');
var cleanCSS = require('clean-css');

/**
 * Process less application
 */
gulp.task('process-css', function () {
  var src = ['src/less/**/*.less'];

  return gulp.src(src)
    .pipe(less({}))
    .pipe(p.concat('styles.css'))
    .pipe(p.sizereport({
      gzip: true,
      total: false,
      minifier: function (contents, filepath) {
        return new cleanCSS().minify(contents).styles;
      }
    }))
    .pipe(p.cleanCss())
    .pipe(gulp.dest('dist/styles'));
});

package.json file :
    "gulp-less": "3.1.0",
    "gulp-clean-css": "^2.0.6",
    "gulp-load-plugins": "^0.10.0",
    "gulp-sizereport": "^1.1.3",
    "gulp-concat": "^2.5.2"

Thanks

I guess I have a similar issue. I have a component library (working) but I also have a couple of styles (scss) with variables (like $buttonColor). Before using this generator I simply used a symlink to consume the library in my app. This allowed me to overwrite the variables in my app. How can I achieve this with the generator?
Currently, I added a styles folder in the src folder but this won't work because it is not copied to the dist folder.

Hey,
I also use my library in symlink and non symlink, I dont understand what's the problem  if your scss application is already copied in the dist folder. When you will  consume your application you simply need to  create a scss application in your new angular project and to import your library scss application.
1 : Create a scss file
2. Add this file in the  angular-cli.json
3. Import your library scss application (who will be in node_modules) in your scss file
4. You can now override variable

@Ixoh — Would you be able to document your setup in a guide? Then we could add it to the WIKI page to help others if they have a similar need. Thanks in advance!

Hum yes I can manage to right a little documention.
About @jhuenges  probleme, sorry I miss readed the last part of your comment : About the fact your style folder not being copied in the dist folder you can  modify the  gulpfile.js by adding :
//This task is used to copy everything from  'src/styles' into the dist folder
gulp.task("copy-css", function () {
var src = ['src/styles/**/*'];
return gulp.src(src).pipe(gulp.dest('dist/styles'));
});
and add it at the end of the compile task  runSequence( .... , 'copy-css' , function (err).....
By doing this your styles folder will be copied automatically in the dist folder at the end of the compilation.

I'm not working with scss application so I write this for "less" application,  but normally it should work for both
Add and consume your library's less application

Create a "styles" folder in your application "src" folder
Create your main less file (we will name it  my_library.less  for exemple)
Currently the generator will not copy our new "styles" folder into the dist which will be a problem for us.  To achieve this we can modifiy the gulpfile.js and add a task to copy this folder.

//This task is used to copy everything from 'src/styles' into the dist/styles folder
gulp.task("copy-css", function () {
var src = ['src/styles/**/*'];
return gulp.src(src).pipe(gulp.dest('dist/styles'));
});

and add it at the end of the 'compile' task runSequence( .... , 'copy-css' , function (err).....

Deploy your library

Update your consumer application : you will now see the "styles" your node_modules application package.

Import "/node_modules/mylibraryr/styles/my_library.less" in your consumer less application to be able to override your styles.

Enjoy

Perhaps we can modifiy the point 3 to make a generic folder who will see is content automatically copied in the dist folder

@Ixoh yes, I wrote the gulp task a couple of minutes after I posted this question. But thanks anyways!


pass correct parameter to Invoke-DQVTesting in CICD pipeline

Pass correct parameter to Invoke-DQVTesting so only the changed and refreshed semantic models are tested.

deleted branch by accident


When there is an operandrequest in the updating status, it will take a long time to uninstall other requests.

/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

solved by #407


Add Interstitial for find course

Added an Interstitial Screen before proceeding with course discovery in browser.

Looks good. Just a few minor things to clean up.

I have integrated the interstitial screen with the code along with Enrolments under a different PR (#38). I did this because there the mechanism was slightly different than this PR.


jsconfig default settings for module type is inconsistent

No jsconfig.json in the workspace
Then the module type defaults to none
jsconfig.json exists but no module property defined
Then the module type defaults to commonjs
Suggest that the module type default is always the same independent of whether there is a jsconfig.json.
If the module property is commonjs by default then I suggest that there is also a default for exclude containing the node_modules folder.

the problem here was you will get an error:

error TS1148: Cannot compile modules unless the '--module' flag is provided. Consider setting the 'module' compiler option in a 'tsconfig.json' file.

which most ppl have found annoying int he past. given that JS users would probably have a transpiler already, do we want to show them that error?

@mhegazy  Does't the default module option also impact how we resolve modules for js files? Even without the error message

@mhegazy the error message is unpleasant since I don't think of code generation when I use JS only. However, given your argument, shouldn't then the default also be commonjs when there is no jsconfig.json?

that is correct, but for that we could set the "moduleResolution" flag, but the error still stays.

shouldn't then the default also be commonjs when there is no jsconfig.json?

in retrospect, yes :) but this would be a big breaking change.

I sent an email on this couple mins ago... repeating below
We chose the current behavior as without a ‘module’ setting the TypeScript engine gives you errors on import/export statements that no module type is defined. With an ES3/ES5 emit target (the default and most common settings), we need to know how to treat these (e.g. as CommonJS, AMD, or System modules). With JavaScript also (optionally) being transpiled now, the same problem exists.
We initially did have a default other than ‘none’, but found too many users were trying to use modules without understand them and the need for a runtime that supported them, so we wanted to add a little impedance to make them stop and think “what module type are trying to use”, and maybe look at some docs if not sure.
Some of the user confusion was caused by TypeScript overloading the “module” keyword for both internal & external modules. Now we’ve moved to “namespace” for internal modules, this should be lessened. Also, Node development being more prevelant, and with CommonJS also being commonly the format of choice in the browser (via browserify, WebPack, etc.), perhaps we could consider defaulting to CommonJS again. Thus ES6 import/export syntax just works, and would emit CommonJS by default, if there is no “module” setting provided.

in retrospect, yes :) but this would be a big breaking change.

correction for my original statement, that would not be a breaking change, existing projects should not be affected. it would be a surprising change though to existing users of TS.
We should consider this for the design meeting tomorrow.

Conclusion is to move to CommonJs as the default module kind

a good outcome, thanks.
Should this also be assigned to the Salsa 0.9 milestone?

closing in favor of https://github.com/Microsoft/TypeScript/issues/6807


feature: storage adapter for images and themes

refs #2852
Right now it was only possible to configure the storage configuration like:
storage: {
  active: 's3'
  s3: {...options..}
}

The whole storage implementation/configuration was strongly designed for images only.
With theme uploads (see #7209), we upload themes to Ghost.
Some custom adapters only offer the ability to store images, that's why we need a way to configure a separate theme adapter or take the default.
When you have this configured for storage:
storage: {
  active: 's3',
  s3: {}
}

It will still work with the only difference that we will define that the default theme storage is the default storage (local file storage).
You can change this behaviour:
storage: {
  active: { images: 's3', themes: 's3' }
  s3: {}
}

I have tested this code with https://github.com/spanishdict/ghost-s3-compat, worked

ready to review 🎉


use mongoengine

principal is very good.
i do`t know how to use principal use mongodb.
can you update you doc,give a demo about mongoengine and principal?
thk.

Hi :wave: Thanks for your concern. If you need help using Mongodb and Flask-principal, please consider asking for help on the Pallets Discord. Thanks.


Objectron broken w/ new blueprint model

Easy repro by just running objectron.
Appears related to the rendering of the world/camera entity as disabling it makes the behavior go away.
It seems like we might be toggling between treating the scene as a 2d vs a 3d view.
The space-view flickers between two states:

It looks like EditableAutoValue is the cause of the instability here.


Html formatter doesn't work together with whitespace

(Original issue 1136 created by gena2x on 2015-08-06T16:38:08.217253+00:00)
This doesn't work:
$ pygmentize -F whitespace:tabs=true,spaces=true -f html -l c test.cc
*** Error while highlighting:
TypeError: expected a character buffer object
(file "/usr/lib/python2.7/dist-packages/pygments/formatters/html.py", line 709, in _format_lines)
This works:
$ pygmentize -F whitespace:tabs=true,spaces=true -l c test.cc
This works too:
pygmentize -F whitespace:tabs=true,spaces=true,newlines=True -f html -l c test.cc
test.cc contains anything which include at least two lines and one line with spaces

(Original issue 1136 last updated on 2015-11-01T00:22:34.710604+00:00)
(Issue automaticaly closed due to status in Bitbucket: duplicate)

(Original comment by tshatch on 2015-11-01T00:22:20.459446+00:00)
Duplicate of #1028.

(Original comment by tshatch on 2015-11-01T00:22:34.707143+00:00)
Please upgraded past 1.6


Add an example for cast balance --erc20

No description provided.

Hey, I want to contribute to this!


Refactor ICFolderDialog build toolchain

This fixes #131.

Pull Request Test Coverage Report for Build 743

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 74.667%

Totals

Change from base Build 735:
0.0%

Covered Lines:
1232

Relevant Lines:
1650

💛  - Coveralls


Add proxy setting for pip fix

This changes are needed for pip install not to fail in our CI.
We make sure pip uses the proxy passed.

@battlemidget these are the changes for the latest and 1.12 tracks. Need to do the same for 1.11 and 1.10.


puppet: Add a label to teleport applications, to allow RBAC.

Roles can only grant or deny access based on labels; set one based on
the application name.
Testing plan: Test-applied.

Merged, thanks @alexmv!


Link to http://europeana.eu/schemas/ is broken

the URL http://europeana.eu/schemas/ returns a forbidden error. It needs to work as it is referenced in the DEA:

Metadata Specifications: The most recent version of the Metadata specifications published by Europeana and available at http://europeana.eu/schemas/ on the Effective Date

this URL needs to point (or forward) to the most recent version of the EDM metadata specification

@juliafallon this is still broken. can you assign this to someone on the technical team to fix this link. as pointed out in the comments this should be directed to https://pro.europeana.eu/resources/standardization-tools/edm-documentation

I've requested this - will update when I have confirmation this has been applied.

Done.


fix: open uri in new tab

If user doesn't have desktop wallet installed, and clicks "Pay Now". The browser tries to open the uri in the same tab. This shows user a message that firefox(browser) cannot open this link.
If user now presses back, everything is gone, data will change.
This PR solves this problem.

If there is no app to handle the link then nothing will happen.

@faustbrian then Firefox tries to open link itself


Fixed #217 - guidance on running cookbooks

@clyne I would suggest leaving it in there - there may be cookbook-specific instructions, and it simplifies pointing someone directly to a cookbook with the overview and installation instructions in one spot

That is the easy thing to do :-). Works for me.

Fixed #17 (not 217)


Podspec / Release out of date

Hi there. Love this project and the quality of the code! Can you do us a favor and release a new version with the latest changes? The current podspec and release tags cause an older version of the code to be installed (pre Swift 3) Thanks!

Bumping this request. I can make the new podspec if you'd like @klaaspieter?

#33 should do it. I'll push it when I get pod trunk access.


Feature: add support for WMS tile layers.

As discussed in #7 , this PR should add support to create tile layers using L.tileLayer.WMS(). The function signature of this constructor is identical to L.tileLayer() so I have simply added an additional optional argument called wms, which when true causes the component to use the alternative constructor. As far as I can tell there are no other constructors which could require such support.
I have also updated the docs. I haven't bumped the version, and would appreciate feedback/support on testing prior to merge.

Thanks for the contribution! Some minor issues, which I can easily fix. 'Testing' is primarily done via providing examples/documentation in svelte-docs.

For your reference:

ccc0741055f6c1e577b81ae40a8210cdbef1443d
4d03648c440f442ef4904ed2003d9a64a79b77e2

To test:

npm run dev
Go to http://localhost:5000


The default behaviour when using eloquent relations is it will inherit comment blocks from Laravel trait HasRelations,
However, when using this package traits those comments are overridden by methods implemented in the package.

Good addition, thanks @tumainimosha!


Create error enums in zebra-consensus.

Is your feature request related to a problem? Please describe.
zebra-consensus handles verification of blocks and transactions.  This means that it needs to report errors on verification failures.
Describe the solution you'd like
Rather than building ad-hoc errors with string descriptions, zebra-consensus could have BlockError and TransactionError enums, whose variants exhaustively enumerate all possible verification failures.  This would be useful because each error variant corresponds to a consensus rule, so enumerating all possible verification failures enumerates the consensus rules we implement, and ensures that we don't reject blocks or transactions for any non-enumerated reason.
use thiserror::Error;

#[derive(Error, Debug)]
pub enum TransactionError {
    // ... transaction errors ...
}

#[derive(Error, Debug)]
pub enum BlockError {
    /// The block contained an invalid transaction.
    #[error("invalid transaction")]
   Transaction(#[from] TransactionError),
    // ... other block errors ...
}

Zcashd also enumerates verification failures, so we can crossreference the enum variants with the Zcashd verification failure modes.
Describe alternatives you've considered
Currently, the consensus checks generate ad-hoc errors with string formatting.  This makes it hard to see what all the potential verification failures are.  In addition, the more consensus checks we implement, the more work it will be to enumerate errors.

Will try to make some progress on this one in the next day(s).


Introduce Provisoned and Scheduled condition.

Summary:
We would like to create instances in a scheduled state before they are
launched. That is why we introduce a Scheduled and Provisioned
condition.
So far instances require agent info. However, when an instance is just
scheduled there is no meanningful agent info. So it has to be optional.
All requests that require this info filter out instances that have no
info. This way we stay backwards compatible since there are no instance
in scheduled condition currently it is safe to ignore them.
JIRA issues: MARATHON-8168

I will follow up with a second pull requests that surfaces the value of these changes.


Cannot build for iOS

Using:
Haxe 3.3.0
Lime 2.9.1
OpenFL 3.6.1 (next)
Looks like the library is not working for non-legacy iOS projects.  Thanks!

Looks like this is only a matter of substituting flash.Lib for lime.system.CFFI.
I'm gonna test it here and make the PR if it works correctly.


Fix authentication middleware

i just ran into the same issue, maybe this solution is more elegant :)

Substantially more elegant haha.  It had been a long day what can I say :sleeping: many thanks.


Better Keyboard A11y + Navigation

Keyboard accessibility is super important, and not just for the visually impaired. It's common practice to TAB through a website when your mouse is faulty and/or you can't be bothered to reach for it. The options components  aren't very keyboard-accessible; this PR aims to change that.
Changes include:

Making all input types react to keyboard focus
Minor design improvements in this scope

Visual Comparison
In both before and after I TAB to the Advanced Settings expander, and then TAB to the end. If it feels like I'm not doing anything in the before changes video... well, that's the issue. I also try to make the checkboxes feel like Material UI, but I can only get so far without a complete overhaul.
Before changes - Little to no focus effects
After changes - 100% support for keyboard navigation

Hi @argyleink, do the changes look good to you? Before/After comparisons are in the description, and I've made the branch up-to-date with dev :)

@argyleink Ahh no worries at all, hope you're feeling better now 😄

@argyleink I added some new changes, would love to hear your thoughts :)

I added the focus outline to the save/import buttons, and made them conditionally disabled (instead of just reducing the opacity)
The back button now has a simple blue pulse outline animation on focus. Nothing too fancy, just something to make it stand out against the light/dark backgrounds (image below)


Version 102 never finishes loading

Describe the bug
Figma Tokens never finishes loading. Tried closing and reopening the plug-in and quitting and restarting Figma. Still won't finish loading.
To Reproduce
Steps to reproduce the behavior:

Open Figma Tokens

Expected behavior
Figma Tokens loads
Screenshots or Screencasts
If applicable, add screenshots to help explain your problem.

Opens fine in a blank file. The issue happens in an existing file with tokens.

Fixed in 103, thank you for the details ❤

I'm still having this issue when I open a file with tokens synced with Github on a new computer (version 104). Would you want me to open a new issue?

I'm still having this issue when I open a file with tokens synced with Github on a new computer (version 104). Would you want me to open a new issue?

Yes please 👍 if possible provide as many details as you can, also inviting me to your figma file / the repo (or a clone of it) would help immensely 🙏

At least one of our team members is still experiencing this in the same file that I sent. Granted, I did setup ADO support on my end.

At least one of our team members is still experiencing this in the same file that I sent. Granted, I did setup ADO support on my end.

We identified an issue and published a fix several hours ago. Please let me know if the issue still occurs 🙏

Seems fixed here! Thank you!


Please invite me to the GitHub Community Organization

Name
Daivid Morgan
Discord Username (if applicable)
No response
Additional Context
Please invite me to your github group.
Here is Daivid Morgan from Macedonia.
I love teamwork and I really wanna be one of your teammates.
Thanks. Daivid

Thanks for your help.


Can't make it work with a specific site

I am trying to access a page on the easyJet website via a node.js server. The page normally produces a json object with a set of flight schedules. If I test this page on a regular browser it works. Similarly, it works if I access it with a js script of mine, but only if I run it via a browser with CORS disabled.
Now I'm trying to access it via a node server using CORS-anywhere. If I do so, I receive a different HTML page saying that I "don't have permission to access ... on this server"
These are the relevant portions of the code:
var host = process.env.HOST || 'localhost';
var port = process.env.PORT || 8080;
cors_proxy.createServer({
    originWhitelist: [], // Allow all origins
    requireHeader: ['origin', 'x-requested-with'],
    removeHeaders: ['cookie', 'cookie2']
}).listen(port, host, function() {
    console.log('Running CORS Anywhere on ' + host + ':' + port);
});

var cors_api_url = 'http://localhost:8080/';
url = 'https://www.easyjet.com/ejavailability/api/v381/availability/query?AdditionalSeats=0&AdultSeats=1&ArrivalIata=MXP&ChildSeats=0&DepartureIata=LGW&IncludeAdminFees=true&IncludeFlexiFares=false&IncludeLowestFareSeats=true&IncludePrices=true&Infants=0&IsTransfer=false&LanguageCode=EN&MaxDepartureDate=2020-09-02&MinDepartureDate=2020-09-02'

fetch(cors_api_url + url, {
	headers: {
		'Method': 'GET',
		'Origin': '',
		'Content-Type': 'application/json'
}})

I have tried to have the server and the client in two different computers on the same network (i.e, using the specific IP address for the server such as <IP_ADDRESS>, and accessing it from another device), and I also tried using a completely different WAN IP address, so to exclude the possibility of my IP being blacklisted.
I also have no luck if I try to use the server on https://cors-anywhere.herokuapp.com/ instead of my own, so I guess that easyJet is, in one way or another, successfully blocking every effort to bypass the CORS policy.
Just to be clear, I am no expert at all, so I might have seriously misunderstood some of the functions/purposes of the tool. What options do I have? Is there anything that I didn't do correctly? Is your app supposed to work with any web server (apart from blacklisting), or are there some site where it doesn't work?
Many thanks for any help
Bob

This is not an issue with CORS. If I use curl to send a request, then I get the same response.
Odds are that the API endpoint relies on cookies or some other way to identify the client before accepting requests. Use the browser's developer tools to inspect the network traffic and find what you need.

Thanks Rob!


Ember upgrades + Engine wrapping of ahoy

TODO

[ ] Ensure there is a human readable title
The titles will be what shows up in the automated changelog for the rest of the company to see.

[ ] Ensure there is a description of the work that helps reviewers understand the context.

[ ] Tag the PR appropriately
In particular, tag with 'bug' if it's a bug fix, 'enhancement' for any other customer facing code, or 'skip changelog' if it's something that only matters to the tech team (i.e. weekly-release branch PRs should always be tagged 'skip changelog').
Tag with "Needs Code Review" when it is ready for code review, and "Needs AC Review" if it is a Sprint item.

[ ] Complete any applicable sections below

Related repo links, such as Rails, Ember, addons or gems (if applicable)
Podio link (if applicable)
PRE DEPLOY TASKS

[ ]

POST DEPLOY TASKS

[ ]

I believe that is from the default blueprint.
(Though admittedly that is a bit out of date)


fix: test python3.11

Description
Test Python3.11.0

Related resources

#...
#...

Checklist

[ ] I have opened this pull request against develop
[ ] I have added or modified the tests when changing logic
[ ] I have followed the conventional commits guidelines to add meaningful information into the changelog
[ ] I have read the contribution guidelines  and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

@vinitkumar @fsbraun with tests passing, should this include 3.11 in the setup classifiers and official support in the changelog?

Yes, I believe it should!

@marksweb @fsbraun Update trove classifiers and updated the changelog. Let me know if anything else needs to be done here.


ENH: stats.xp_var: array-API compatible variance with scipy.stats interface

Reference issue
Toward gh-20544
What does this implement/fix?
This creates an array-API compatible var with features we need in other functions (e.g. nan_policy='omit'). The approach is to use _xp_mean to compute the second central moment, then correction is applied if need be.
This will be used by tvar, tstd, and the zscore functions.

Failures are all JAX due to not supporting item assignment. I'll just skip JAX while https://github.com/scipy/scipy/pull/20085#issuecomment-2119307509 is still unresolved and _lazywhere doesn't work with JAX.

thanks Matt!


fix: fix caption button fluent theme and default theme.

What does the pull request do?

Fix CaptionButtons fluent/simple theme.
What is the current behavior?

Type and name in selector cannot match any elements.
What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

Hm, this must have been broken a while. I dont think it's my fault and never even updated this control's template. Anyway, thanks for finding this one too!

Yea, I checked history. It's been broken a while. The template parts look correct now and match with code-behind:
https://github.com/AvaloniaUI/Avalonia/blob/4f6ef463693033cdeea206a4235a5cc847fb45e3/src/Avalonia.Controls/Chrome/CaptionButtons.cs#L11-L14
and
https://github.com/AvaloniaUI/Avalonia/blob/4f6ef463693033cdeea206a4235a5cc847fb45e3/src/Avalonia.Controls/Chrome/CaptionButtons.cs#L91-L94

You can test this PR using the following package version. 11.0.999-cibuild0024882-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

It seems to be broken in this PR, so it is isolated with 11.0
https://github.com/AvaloniaUI/Avalonia/commit/23a6517a6b064cecda957be0eeb768074bf76823


Formatting update

Removed a line break to maintain great formatting techniques.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congrats @alz-sinton on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Error 500 on import of wpscan results v2 API

Bug description
Error 500 upon import of a WPscan result via V2 API
[18/Jan/2022 19:32:52] ERROR [dojo.api_v2.exception_handler:32] can only concatenate str (not "NoneType") to str
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/rest_framework/mixins.py", line 19, in create
    self.perform_create(serializer)
  File "/app/./dojo/api_v2/views.py", line 1935, in perform_create
    serializer.save(push_to_jira=push_to_jira)
  File "/app/./dojo/api_v2/serializers.py", line 1324, in save
    test, finding_count, closed_finding_count = importer.import_scan(scan, scan_type, engagement, lead, environment,
  File "/app/./dojo/importers/importer/importer.py", line 298, in import_scan
    parsed_findings = parser.get_findings(scan, test)
  File "/app/./dojo/tools/wpscan/parser.py", line 59, in get_findings
    finding.mitigation = 'fixed in : ' + vul['fixed_in']
TypeError: can only concatenate str (not "NoneType") to str
[18/Jan/2022 19:32:52] ERROR [django.request:224] Internal Server Error: /api/v2/import-scan/
ERROR:django.request:Internal Server Error: /api/v2/import-scan/

Steps to reproduce
Steps to reproduce the behavior:

Import wpscans recursively from several host over API
Sometimes API import says error 500
See error

Expected behavior
Upload and parse wpscan report
Deployment method (select with an X)

[X] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: Ubuntu
DefectDojo version: 2.6.2

Logs
[18/Jan/2022 19:32:52] ERROR [dojo.api_v2.exception_handler:32] can only concatenate str (not "NoneType") to str
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/rest_framework/mixins.py", line 19, in create
    self.perform_create(serializer)
  File "/app/./dojo/api_v2/views.py", line 1935, in perform_create
    serializer.save(push_to_jira=push_to_jira)
  File "/app/./dojo/api_v2/serializers.py", line 1324, in save
    test, finding_count, closed_finding_count = importer.import_scan(scan, scan_type, engagement, lead, environment,
  File "/app/./dojo/importers/importer/importer.py", line 298, in import_scan
    parsed_findings = parser.get_findings(scan, test)
  File "/app/./dojo/tools/wpscan/parser.py", line 59, in get_findings
    finding.mitigation = 'fixed in : ' + vul['fixed_in']
TypeError: can only concatenate str (not "NoneType") to str
[18/Jan/2022 19:32:52] ERROR [django.request:224] Internal Server Error: /api/v2/import-scan/
ERROR:django.request:Internal Server Error: /api/v2/import-scan/

Sample scan files
Have not been able to reproduce to a specific wpscan.json file
Additional context
Not happening everytime.

Version: 2.6.2
I also noticed that the error 500 is giving to delete products and when importing reports only the first vulnerability is registered.

Please upload a sample report once you see the issue again, probably the fixed_in field is not always present.
For any other problems, please create separate issues.

I can take care of this one. But I agree with @valentijnscholten . if you can provide a report (even obfuscated) it make things easier for us to fix.

{
  "banner": {
    "description": "WordPress Security Scanner by the WPScan Team",
    "version": "3.8.20",
    "authors": [
      "@_WPScan_",
      "@ethicalhack3r",
      "@erwan_lr",
      "@firefart"
    ],
    "sponsor": "Sponsored by Automattic - https://automattic.com/"
  },
  "start_time":<PHONE_NUMBER>,
  "start_memory": 46145536,
  "target_url": "REDACTEDURL",
  "target_ip": "REDACTEDIP",
  "effective_url": "REDACTEDURL",
  "interesting_findings": [
    {
      "url": "REDACTEDURL",
      "to_s": "Headers",
      "type": "headers",
      "found_by": "Headers (Passive Detection)",
      "confidence": 100,
      "confirmed_by": {

      },
      "references": {

      },
      "interesting_entries": [
        "x-cdn-diag: jfk4-2051-2-9270-r-0-0-304-0.068--;2051-14-9468----0-0-72"
      ]
    },
    {
      "url": "REDACTEDURLxmlrpc.php",
      "to_s": "XML-RPC seems to be enabled: REDACTEDURLxmlrpc.php",
      "type": "xmlrpc",
      "found_by": "Link Tag (Passive Detection)",
      "confidence": 30,
      "confirmed_by": {

      },
      "references": {
        "url": [
          "http://codex.wordpress.org/XML-RPC_Pingback_API"
        ],
        "metasploit": [
          "auxiliary/scanner/http/wordpress_ghost_scanner",
          "auxiliary/dos/http/wordpress_xmlrpc_dos",
          "auxiliary/scanner/http/wordpress_xmlrpc_login",
          "auxiliary/scanner/http/wordpress_pingback_access"
        ]
      },
      "interesting_entries": [

      ]
    }
  ],
  "version": {
    "number": "4.7.6",
    "release_date": "2017-09-19",
    "status": "insecure",
    "found_by": "Emoji Settings (Passive Detection)",
    "confidence": 100,
    "interesting_entries": [
      "REDACTEDURL, Match: 'wp-includes\\/js\\/wp-emoji-release.min.js?ver=4.7.6'"
    ],
    "confirmed_by": {
      "Meta Generator (Passive Detection)": {
        "confidence": 60,
        "interesting_entries": [
          "REDACTEDURL, Match: 'WordPress 4.7.6'"
        ]
      }
    },
    "vulnerabilities": [
      {
        "title": "WordPress 2.3-4.8.3 - Host Header Injection in Password Reset",
        "fixed_in": null,
        "references": {
          "cve": [
            "2017-8295"
          ],
          "url": [
            "https://exploitbox.io/vuln/WordPress-Exploit-4-7-Unauth-Password-Reset-0day-CVE-2017-8295.html",
            "https://blog.dewhurstsecurity.com/2017/05/04/exploitbox-wordpress-security-advisories.html",
            "https://core.trac.wordpress.org/ticket/25239"
          ],
          "wpvulndb": [
            "b3f2f3db-75e4-4d48-ae5e-d4ff172bc093"
          ]
        }
      },
      {
        "title": "WordPress <= 4.8.2 - $wpdb->prepare() Weakness",
        "fixed_in": "4.7.7",
        "references": {
          "cve": [
            "2017-16510"
          ],
          "url": [
            "https://wordpress.org/news/2017/10/wordpress-4-8-3-security-release/",
            "https://github.com/WordPress/WordPress/commit/a2693fd8602e3263b5925b9d799ddd577202167d",
            "https://twitter.com/ircmaxell/status/923662170092638208",
            "https://blog.ircmaxell.com/2017/10/disclosure-wordpress-wpdb-sql-injection-technical.html"
          ],
          "wpvulndb": [
            "c161f0f0-6527-4ba4-a43d-36c644e250fc"
          ]
        }
      },
      {
        "title": "WordPress 2.8.6-4.9 - Authenticated JavaScript File Upload",
        "fixed_in": "4.7.8",
        "references": {
          "cve": [
            "2017-17092"
          ],
          "url": [
            "https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/67d03a98c2cae5f41843c897f206adde299b0509"
          ],
          "wpvulndb": [
            "0d2323bd-aecd-4d58-ba4b-597a43034f57"
          ]
        }
      },
      {
        "title": "WordPress 1.5.0-4.9 - RSS and Atom Feed Escaping",
        "fixed_in": "4.7.8",
        "references": {
          "cve": [
            "2017-17094"
          ],
          "url": [
            "https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/f1de7e42df29395c3314bf85bff3d1f4f90541de"
          ],
          "wpvulndb": [
            "1f71a775-e87e-47e9-9642-bf4bce99c332"
          ]
        }
      },
      {
        "title": "WordPress 4.3.0-4.9 - HTML Language Attribute Escaping",
        "fixed_in": "4.7.8",
        "references": {
          "cve": [
            "2017-17093"
          ],
          "url": [
            "https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/3713ac5ebc90fb2011e98dfd691420f43da6c09a"
          ],
          "wpvulndb": [
            "a6281b30-c272-4d44-9420-2ebd3c8ff7da"
          ]
        }
      },
      {
        "title": "WordPress 3.7-4.9 - 'newbloguser' Key Weak Hashing",
        "fixed_in": "4.7.8",
        "references": {
          "cve": [
            "2017-17091"
          ],
          "url": [
            "https://wordpress.org/news/2017/11/wordpress-4-9-1-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/eaf1cfdc1fe0bdffabd8d879c591b864d833326c"
          ],
          "wpvulndb": [
            "809f68d5-97aa-44e5-b181-cc7bdf5685c5"
          ]
        }
      },
      {
        "title": "WordPress 3.7-4.9.1 - MediaElement Cross-Site Scripting (XSS)",
        "fixed_in": "4.7.9",
        "references": {
          "cve": [
            "2018-5776",
            "2016-9263"
          ],
          "url": [
            "https://github.com/WordPress/WordPress/commit/3fe9cb61ee71fcfadb5e002399296fcc1198d850",
            "https://wordpress.org/news/2018/01/wordpress-4-9-2-security-and-maintenance-release/",
            "https://core.trac.wordpress.org/ticket/42720"
          ],
          "wpvulndb": [
            "6ac45244-9f09-4e9c-92f3-f339d450fe72"
          ]
        }
      },
      {
        "title": "WordPress <= 4.9.4 - Application Denial of Service (DoS) (unpatched)",
        "fixed_in": null,
        "references": {
          "cve": [
            "2018-6389"
          ],
          "url": [
            "https://baraktawily.blogspot.fr/2018/02/how-to-dos-29-of-world-wide-websites.html",
            "https://github.com/quitten/doser.py",
            "https://thehackernews.com/2018/02/wordpress-dos-exploit.html"
          ],
          "wpvulndb": [
            "5e0c1ddd-fdd0-421b-bdbe-3eee6b75c919"
          ]
        }
      },
      {
        "title": "WordPress 3.7-4.9.4 - Remove localhost Default",
        "fixed_in": "4.7.10",
        "references": {
          "cve": [
            "2018-10101"
          ],
          "url": [
            "https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/804363859602d4050d9a38a21f5a65d9aec18216"
          ],
          "wpvulndb": [
            "835614a2-ad92-4027-b485-24b39038171d"
          ]
        }
      },
      {
        "title": "WordPress 3.7-4.9.4 - Use Safe Redirect for Login",
        "fixed_in": "4.7.10",
        "references": {
          "cve": [
            "2018-10100"
          ],
          "url": [
            "https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/14bc2c0a6fde0da04b47130707e01df850eedc7e"
          ],
          "wpvulndb": [
            "01b587e0-0a86-47af-a088-6e5e350e8247"
          ]
        }
      },
      {
        "title": "WordPress 3.7-4.9.4 - Escape Version in Generator Tag",
        "fixed_in": "4.7.10",
        "references": {
          "cve": [
            "2018-10102"
          ],
          "url": [
            "https://wordpress.org/news/2018/04/wordpress-4-9-5-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/31a4369366d6b8ce30045d4c838de2412c77850d"
          ],
          "wpvulndb": [
            "2b7c77c3-8dbc-4a2a-9ea3-9929c3373557"
          ]
        }
      },
      {
        "title": "WordPress <= 4.9.6 - Authenticated Arbitrary File Deletion",
        "fixed_in": "4.7.11",
        "references": {
          "cve": [
            "2018-12895"
          ],
          "url": [
            "https://blog.ripstech.com/2018/wordpress-file-delete-to-code-execution/",
            "http://blog.vulnspy.com/2018/06/27/Wordpress-4-9-6-Arbitrary-File-Delection-Vulnerbility-Exploit/",
            "https://github.com/WordPress/WordPress/commit/c9dce0606b0d7e6f494d4abe7b193ac046a322cd",
            "https://wordpress.org/news/2018/07/wordpress-4-9-7-security-and-maintenance-release/",
            "https://www.wordfence.com/blog/2018/07/details-of-an-additional-file-deletion-vulnerability-patched-in-wordpress-4-9-7/"
          ],
          "wpvulndb": [
            "42ab2bd9-bbb1-4f25-a632-1811c5130bb4"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - Authenticated File Delete",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20147"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/"
          ],
          "wpvulndb": [
            "e3ef8976-11cb-4854-837f-786f43cbdf44"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - Authenticated Post Type Bypass",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20152"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/",
            "https://blog.ripstech.com/2018/wordpress-post-type-privilege-escalation/"
          ],
          "wpvulndb": [
            "999dba5a-82fb-4717-89c3-6ed723cc7e45"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - PHP Object Injection via Meta Data",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20148"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/"
          ],
          "wpvulndb": [
            "046ff6a0-90b2-4251-98fc-b7fba93f8334"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - Authenticated Cross-Site Scripting (XSS)",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20153"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/"
          ],
          "wpvulndb": [
            "3182002e-d831-4412-a27d-a5e39bb44314"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - Cross-Site Scripting (XSS) that could affect plugins",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20150"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/",
            "https://github.com/WordPress/WordPress/commit/fb3c6ea0618fcb9a51d4f2c1940e9efcd4a2d460"
          ],
          "wpvulndb": [
            "7f7a0795-4dd7-417d-804e-54f12595d1e4"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - User Activation Screen Search Engine Indexing",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20151"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/"
          ],
          "wpvulndb": [
            "65f1aec4-6d28-4396-88d7-66702b21c7a2"
          ]
        }
      },
      {
        "title": "WordPress <= 5.0 - File Upload to XSS on Apache Web Servers",
        "fixed_in": "4.7.12",
        "references": {
          "cve": [
            "2018-20149"
          ],
          "url": [
            "https://wordpress.org/news/2018/12/wordpress-5-0-1-security-release/",
            "https://github.com/WordPress/WordPress/commit/246a70bdbfac3bd45ff71c7941deef1bb206b19a"
          ],
          "wpvulndb": [
            "d741f5ae-52ca-417d-a2ca-acdfb7ca5808"
          ]
        }
      },
      {
        "title": "WordPress 3.7-5.0 (except 4.9.9) - Authenticated Code Execution",
        "fixed_in": "5.0.1",
        "references": {
          "cve": [
            "2019-8942",
            "2019-8943"
          ],
          "url": [
            "https://blog.ripstech.com/2019/wordpress-image-remote-code-execution/",
            "https://www.rapid7.com/db/modules/exploit/multi/http/wp_crop_rce"
          ],
          "wpvulndb": [
            "1a693e57-f99c-4df6-93dd-0cdc92fd0526"
          ]
        }
      },
      {
        "title": "WordPress 3.9-5.1 - Comment Cross-Site Scripting (XSS)",
        "fixed_in": "4.7.13",
        "references": {
          "cve": [
            "2019-9787"
          ],
          "url": [
            "https://github.com/WordPress/WordPress/commit/0292de60ec78c5a44956765189403654fe4d080b",
            "https://wordpress.org/news/2019/03/wordpress-5-1-1-security-and-maintenance-release/",
            "https://blog.ripstech.com/2019/wordpress-csrf-to-rce/"
          ],
          "wpvulndb": [
            "d150f43f-6030-4191-98b8-20ae05585936"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.2 - Cross-Site Scripting (XSS) in URL Sanitisation",
        "fixed_in": "4.7.14",
        "references": {
          "cve": [
            "2019-16222"
          ],
          "url": [
            "https://wordpress.org/news/2019/09/wordpress-5-2-3-security-and-maintenance-release/",
            "https://github.com/WordPress/WordPress/commit/30ac67579559fe42251b5a9f887211bf61a8ed68",
            "https://hackerone.com/reports/339483"
          ],
          "wpvulndb": [
            "4494a903-5a73-4cad-8c14-1e7b4da2be61"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - Stored XSS in Customizer",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17674"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
          ],
          "wpvulndb": [
            "d39a7b84-28b9-4916-a2fc-6192ceb6fa56"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - Unauthenticated View Private/Draft Posts",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17671"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html",
            "https://github.com/WordPress/WordPress/commit/f82ed753cf00329a5e41f2cb6dc521085136f308",
            "https://0day.work/proof-of-concept-for-wordpress-5-2-3-viewing-unauthenticated-posts/"
          ],
          "wpvulndb": [
            "3413b879-785f-4c9f-aa8a-5a4a1d5e0ba2"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - Stored XSS in Style Tags",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17672"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
          ],
          "wpvulndb": [
            "d005b1f8-749d-438a-8818-21fba45c6465"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - JSON Request Cache Poisoning",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17673"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://github.com/WordPress/WordPress/commit/b224c251adfa16a5f84074a3c0886270c9df38de",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
          ],
          "wpvulndb": [
            "7804d8ed-457a-407e-83a7-345d3bbe07b2"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - Server-Side Request Forgery (SSRF) in URL Validation ",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17669",
            "2019-17670"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://github.com/WordPress/WordPress/commit/9db44754b9e4044690a6c32fd74b9d5fe26b07b2",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
          ],
          "wpvulndb": [
            "26a26de2-d598-405d-b00c-61f71cfacff6"
          ]
        }
      },
      {
        "title": "WordPress <= 5.2.3 - Admin Referrer Validation",
        "fixed_in": "4.7.15",
        "references": {
          "cve": [
            "2019-17675"
          ],
          "url": [
            "https://wordpress.org/news/2019/10/wordpress-5-2-4-security-release/",
            "https://github.com/WordPress/WordPress/commit/b183fd1cca0b44a92f0264823dd9f22d2fd8b8d0",
            "https://blog.wpscan.com/wordpress/security/release/2019/10/15/wordpress-524-security-release-breakdown.html"
          ],
          "wpvulndb": [
            "715c00e3-5302-44ad-b914-131c162c3f71"
          ]
        }
      },
      {
        "title": "WordPress <= 5.3 - Authenticated Improper Access Controls in REST API",
        "fixed_in": "4.7.16",
        "references": {
          "cve": [
            "2019-20043",
            "2019-16788"
          ],
          "url": [
            "https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-g7rg-hchx-c2gw"
          ],
          "wpvulndb": [
            "4a6de154-5fbd-4c80-acd3-8902ee431bd8"
          ]
        }
      },
      {
        "title": "WordPress <= 5.3 - Authenticated Stored XSS via Crafted Links",
        "fixed_in": "4.7.16",
        "references": {
          "cve": [
            "2019-20042"
          ],
          "url": [
            "https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/",
            "https://hackerone.com/reports/509930",
            "https://github.com/WordPress/wordpress-develop/commit/1f7f3f1f59567e2504f0fbebd51ccf004b3ccb1d",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-xvg2-m2f4-83m7"
          ],
          "wpvulndb": [
            "23553517-34e3-40a9-a406-f3ffbe9dd265"
          ]
        }
      },
      {
        "title": "WordPress <= 5.3 - Authenticated Stored XSS via Block Editor Content",
        "fixed_in": "4.7.16",
        "references": {
          "cve": [
            "2019-16781",
            "2019-16780"
          ],
          "url": [
            "https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-pg4x-64rh-3c9v"
          ],
          "wpvulndb": [
            "be794159-4486-4ae1-a5cc-5c190e5ddf5f"
          ]
        }
      },
      {
        "title": "WordPress <= 5.3 - wp_kses_bad_protocol() Colon Bypass",
        "fixed_in": "4.7.16",
        "references": {
          "cve": [
            "2019-20041"
          ],
          "url": [
            "https://wordpress.org/news/2019/12/wordpress-5-3-1-security-and-maintenance-release/",
            "https://github.com/WordPress/wordpress-develop/commit/b1975463dd995da19bb40d3fa0786498717e3c53"
          ],
          "wpvulndb": [
            "8fac612b-95d2-477a-a7d6-e5ec0bb9ca52"
          ]
        }
      },
      {
        "title": "WordPress < 5.4.1 - Password Reset Tokens Failed to Be Properly Invalidated",
        "fixed_in": "4.7.17",
        "references": {
          "cve": [
            "2020-11027"
          ],
          "url": [
            "https://wordpress.org/news/2020/04/wordpress-5-4-1/",
            "https://core.trac.wordpress.org/changeset/47634/",
            "https://www.wordfence.com/blog/2020/04/unpacking-the-7-vulnerabilities-fixed-in-todays-wordpress-5-4-1-security-update/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-ww7v-jg8c-q6jw"
          ],
          "wpvulndb": [
            "7db191c0-d112-4f08-a419-a1cd81928c4e"
          ]
        }
      },
      {
        "title": "WordPress < 5.4.1 - Unauthenticated Users View Private Posts",
        "fixed_in": "4.7.17",
        "references": {
          "cve": [
            "2020-11028"
          ],
          "url": [
            "https://wordpress.org/news/2020/04/wordpress-5-4-1/",
            "https://core.trac.wordpress.org/changeset/47635/",
            "https://www.wordfence.com/blog/2020/04/unpacking-the-7-vulnerabilities-fixed-in-todays-wordpress-5-4-1-security-update/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-xhx9-759f-6p2w"
          ],
          "wpvulndb": [
            "d1e1ba25-98c9-4ae7-8027-9632fb825a56"
          ]
        }
      },
      {
        "title": "WordPress < 5.4.1 - Authenticated Cross-Site Scripting (XSS) in Customizer",
        "fixed_in": "4.7.17",
        "references": {
          "cve": [
            "2020-11025"
          ],
          "url": [
            "https://wordpress.org/news/2020/04/wordpress-5-4-1/",
            "https://core.trac.wordpress.org/changeset/47633/",
            "https://www.wordfence.com/blog/2020/04/unpacking-the-7-vulnerabilities-fixed-in-todays-wordpress-5-4-1-security-update/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-4mhg-j6fx-5g3c"
          ],
          "wpvulndb": [
            "4eee26bd-a27e-4509-a3a5-8019dd48e429"
          ]
        }
      },
      {
        "title": "WordPress < 5.4.1 - Cross-Site Scripting (XSS) in wp-object-cache",
        "fixed_in": "4.7.17",
        "references": {
          "cve": [
            "2020-11029"
          ],
          "url": [
            "https://wordpress.org/news/2020/04/wordpress-5-4-1/",
            "https://core.trac.wordpress.org/changeset/47637/",
            "https://www.wordfence.com/blog/2020/04/unpacking-the-7-vulnerabilities-fixed-in-todays-wordpress-5-4-1-security-update/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-568w-8m88-8g2c"
          ],
          "wpvulndb": [
            "e721d8b9-a38f-44ac-8520-b4a9ed6a5157"
          ]
        }
      },
      {
        "title": "WordPress < 5.4.1 - Authenticated Cross-Site Scripting (XSS) in File Uploads",
        "fixed_in": "4.7.17",
        "references": {
          "cve": [
            "2020-11026"
          ],
          "url": [
            "https://wordpress.org/news/2020/04/wordpress-5-4-1/",
            "https://core.trac.wordpress.org/changeset/47638/",
            "https://www.wordfence.com/blog/2020/04/unpacking-the-7-vulnerabilities-fixed-in-todays-wordpress-5-4-1-security-update/",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-3gw2-4656-pfr2",
            "https://hackerone.com/reports/179695"
          ],
          "wpvulndb": [
            "55438b63-5fc9-4812-afc4-2f1eff800d5f"
          ]
        }
      },
      {
        "title": "WordPress 4.7-5.7 - Authenticated Password Protected Pages Exposure",
        "fixed_in": "4.7.20",
        "references": {
          "cve": [
            "2021-29450"
          ],
          "url": [
            "https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/",
            "https://blog.wpscan.com/2021/04/15/wordpress-571-security-vulnerability-release.html",
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-pmmh-2f36-wvhq",
            "https://core.trac.wordpress.org/changeset/50717/"
          ],
          "youtube": [
            "https://www.youtube.com/watch?v=J2GXmxAdNWs"
          ],
          "wpvulndb": [
            "6a3ec618-c79e-4b9c-9020-86b157458ac5"
          ]
        }
      },
      {
        "title": "WordPress 3.7 to 5.7.1 - Object Injection in PHPMailer",
        "fixed_in": "4.7.21",
        "references": {
          "cve": [
            "2020-36326",
            "2018-19296"
          ],
          "url": [
            "https://github.com/WordPress/WordPress/commit/267061c9595fedd321582d14c21ec9e7da2dcf62",
            "https://wordpress.org/news/2021/05/wordpress-5-7-2-security-release/",
            "https://github.com/PHPMailer/PHPMailer/commit/e2e07a355ee8ff36aba21d0242c5950c56e4c6f9",
            "https://www.wordfence.com/blog/2021/05/wordpress-5-7-2-security-release-what-you-need-to-know/"
          ],
          "youtube": [
            "https://www.youtube.com/watch?v=HaW15aMzBUM"
          ],
          "wpvulndb": [
            "4cd46653-4470-40ff-8aac-318bee2f998d"
          ]
        }
      },
      {
        "title": "WordPress < 5.8 - Plugin Confusion",
        "fixed_in": "5.8",
        "references": {
          "cve": [
            "2021-44223"
          ],
          "url": [
            "https://vavkamil.cz/2021/11/25/wordpress-plugin-confusion-update-can-get-you-pwned/"
          ],
          "wpvulndb": [
            "95e01006-84e4-4e95-b5d7-68ea7b5aa1a8"
          ]
        }
      },
      {
        "title": "WordPress < 5.8.3 - SQL Injection via WP_Query",
        "fixed_in": "4.7.22",
        "references": {
          "cve": [
            "2022-21661"
          ],
          "url": [
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-6676-cqfm-gw84",
            "https://hackerone.com/reports/1378209"
          ],
          "wpvulndb": [
            "7f768bcf-ed33-4b22-b432-d1e7f95c1317"
          ]
        }
      },
      {
        "title": "WordPress < 5.8.3 - Author+ Stored XSS via Post Slugs",
        "fixed_in": "4.7.22",
        "references": {
          "cve": [
            "2022-21662"
          ],
          "url": [
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-699q-3hj9-889w",
            "https://hackerone.com/reports/425342",
            "https://blog.sonarsource.com/wordpress-stored-xss-vulnerability"
          ],
          "wpvulndb": [
            "dc6f04c2-7bf2-4a07-92b5-dd197e4d94c8"
          ]
        }
      },
      {
        "title": "WordPress 4.1-5.8.2 - SQL Injection via WP_Meta_Query",
        "fixed_in": "4.7.22",
        "references": {
          "cve": [
            "2022-21664"
          ],
          "url": [
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jp3p-gw8h-6x86"
          ],
          "wpvulndb": [
            "24462ac4-7959-4575-97aa-a6dcceeae722"
          ]
        }
      },
      {
        "title": "WordPress < 5.8.3 - Super Admin Object Injection in Multisites",
        "fixed_in": "4.7.22",
        "references": {
          "cve": [
            "2022-21663"
          ],
          "url": [
            "https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jmmq-m8p8-332h",
            "https://hackerone.com/reports/541469"
          ],
          "wpvulndb": [
            "008c21ab-3d7e-4d97-b6c3-db9d83f390a7"
          ]
        }
      }
    ]
  },
  "main_theme": {
    "slug": "twentyfourteen",
    "location": "REDACTEDURLwp-content/themes/twentyfourteen/",
    "latest_version": "3.2",
    "last_updated": "2021-07-22T00:00:00.000Z",
    "outdated": true,
    "readme_url": false,
    "directory_listing": false,
    "error_log_url": null,
    "style_url": "REDACTEDURLwp-content/themes/twentyfourteen/style.css?ver=4.7.6",
    "style_name": "Twenty Fourteen",
    "style_uri": "https://wordpress.org/themes/twentyfourteen/",
    "description": "In 2014, our default theme lets you create a responsive magazine website with a sleek, modern design. Feature your favorite homepage content in either a grid or a slider. Use the three widget areas to customize your website, and change your content's layout with a full-width page template and a contributor page to show off your authors. Creating a magazine website with WordPress has never been easier.",
    "author": "the WordPress team",
    "author_uri": "https://wordpress.org/",
    "template": null,
    "license": "GNU General Public License v2 or later",
    "license_uri": "http://www.gnu.org/licenses/gpl-2.0.html",
    "tags": "blog, news, two-columns, three-columns, left-sidebar, right-sidebar, custom-background, custom-header, custom-menu, editor-style, featured-images, flexible-header, footer-widgets, full-width-template, microformats, post-formats, rtl-language-support, sticky-post, theme-options, translation-ready, accessibility-ready",
    "text_domain": "twentyfourteen",
    "found_by": "Css Style In Homepage (Passive Detection)",
    "confidence": 70,
    "interesting_entries": [

    ],
    "confirmed_by": {

    },
    "vulnerabilities": [

    ],
    "version": {
      "number": "1.9",
      "confidence": 80,
      "found_by": "Style (Passive Detection)",
      "interesting_entries": [
        "REDACTEDURLwp-content/themes/twentyfourteen/style.css?ver=4.7.6, Match: 'Version: 1.9'"
      ],
      "confirmed_by": {

      }
    },
    "parents": [

    ]
  },
  "plugins": {
    "all-in-one-seo-pack": {
      "slug": "all-in-one-seo-pack",
      "location": "REDACTEDURLwp-content/plugins/all-in-one-seo-pack/",
      "latest_version": "<IP_ADDRESS>",
      "last_updated": "2022-01-11T16:02:00.000Z",
      "outdated": true,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Comment (Passive Detection)",
      "confidence": 30,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [
        {
          "title": "All in One SEO Pack <= <IP_ADDRESS> - Authenticated Stored Cross-Site Scripting (XSS)",
          "fixed_in": "2.10",
          "references": {
            "url": [
              "https://www.ripstech.com/php-security-calendar-2018/#day-4",
              "https://wordpress.org/support/topic/a-critical-vulnerability-has-been-detected-in-this-plugin/",
              "https://semperfiwebdesign.com/all-in-one-seo-pack-release-history/"
            ],
            "wpvulndb": [
              "16353d45-75d1-4820-b93f-daad90c322a8"
            ]
          }
        },
        {
          "title": "All In One SEO Pack < 3.2.7 - Stored Cross-Site Scripting (XSS)",
          "fixed_in": "3.2.7",
          "references": {
            "cve": [
              "2019-16520"
            ],
            "url": [
              "https://github.com/sbaresearch/advisories/tree/public/2019/SBA-ADV-20190913-04_WordPress_Plugin_All_in_One_SEO_Pack"
            ],
            "wpvulndb": [
              "868dccee-089b-43d2-a80a-6cadba91f770"
            ]
          }
        },
        {
          "title": "All in One SEO Pack < 3.6.2 - Authenticated Stored Cross-Site Scripting",
          "fixed_in": "3.6.2",
          "references": {
            "cve": [
              "2020-35946"
            ],
            "url": [
              "https://www.wordfence.com/blog/2020/07/2-million-users-affected-by-vulnerability-in-all-in-one-seo-pack/"
            ],
            "youtube": [
              "https://www.youtube.com/watch?v=2fqMM6HRV5s"
            ],
            "wpvulndb": [
              "528fff6c-54fe-4812-9b08-8c4e47350c83"
            ]
          }
        },
        {
          "title": "All in One SEO Pack <  <IP_ADDRESS> - Admin RCE via unserialize",
          "fixed_in": "<IP_ADDRESS>",
          "references": {
            "cve": [
              "2021-24307"
            ],
            "url": [
              "https://aioseo.com/changelog/"
            ],
            "wpvulndb": [
              "ab2c94d2-f6c4-418b-bd14-711ed164bcf1"
            ]
          }
        }
      ],
      "version": {
        "number": "<IP_ADDRESS>.1",
        "confidence": 60,
        "found_by": "Comment (Passive Detection)",
        "interesting_entries": [
          "REDACTEDURL, Match: 'All in One SEO Pack <IP_ADDRESS>.1 by'"
        ],
        "confirmed_by": {

        }
      }
    },
    "cleaner-gallery": {
      "slug": "cleaner-gallery",
      "location": "REDACTEDURLwp-content/plugins/cleaner-gallery/",
      "latest_version": "1.1.0",
      "last_updated": "2014-07-11T15:17:00.000Z",
      "outdated": false,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Urls In Homepage (Passive Detection)",
      "confidence": 80,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [

      ],
      "version": null
    },
    "nextcellent-gallery-nextgen-legacy": {
      "slug": "nextcellent-gallery-nextgen-legacy",
      "location": "REDACTEDURLwp-content/plugins/nextcellent-gallery-nextgen-legacy/",
      "latest_version": "1.9.35",
      "last_updated": "2017-10-16T09:19:00.000Z",
      "outdated": false,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Comment (Passive Detection)",
      "confidence": 30,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [

      ],
      "version": {
        "number": "2.2.3",
        "confidence": 60,
        "found_by": "Comment (Passive Detection)",
        "interesting_entries": [
          "REDACTEDURL, Match: '<meta name=\"NextGEN\" version=\"2.2.3\"'"
        ],
        "confirmed_by": {

        }
      }
    },
    "nextgen-gallery": {
      "slug": "nextgen-gallery",
      "location": "REDACTEDURLwp-content/plugins/nextgen-gallery/",
      "latest_version": "3.22",
      "last_updated": "2022-01-20T21:04:00.000Z",
      "outdated": true,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Comment (Passive Detection)",
      "confidence": 30,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [
        {
          "title": "NextGEN Gallery <= 2.2.46 - Galley Paths Not Secured",
          "fixed_in": "2.2.50",
          "references": {
            "cve": [
              "2018-7586"
            ],
            "wpvulndb": [
              "1097f6e4-1473-4969-8f27-a71945b7c09b"
            ]
          }
        },
        {
          "title": "NextGEN Gallery <= 2.2.44 - Cross-Site Scripting (XSS)",
          "fixed_in": "2.2.45",
          "references": {
            "cve": [
              "2018-1000172"
            ],
            "url": [
              "https://fortiguard.com/zeroday/FG-VD-17-215",
              "https://plugins.trac.wordpress.org/changeset/1822089/nextgen-gallery"
            ],
            "wpvulndb": [
              "0f58c270-9e41-4785-bd25-687b924b6867"
            ]
          }
        },
        {
          "title": "NextGen Gallery <= 3.1.5 - Authenticated PHP Object Injection",
          "fixed_in": "3.1.6",
          "references": {
            "url": [
              "https://medium.com/websec/wordpress-nextgen-gallery-3-1-5-rce-via-low-priviledged-users-85a37ff87423",
              "https://plugins.trac.wordpress.org/changeset/2013508/nextgen-gallery",
              "https://plugins.trac.wordpress.org/changeset/2008464/nextgen-gallery"
            ],
            "wpvulndb": [
              "e17ed5ce-6bb5-4f0e-b6b4-bd5648a1e5b6"
            ]
          }
        },
        {
          "title": "Freemius Library < 2.2.4 - Subscriber+ Arbitrary Option Update ",
          "fixed_in": "3.1.7",
          "references": {
            "url": [
              "https://wptavern.com/freemius-patches-severe-vulnerability-in-library-used-by-popular-wordpress-plugins",
              "https://freemius.com/blog/sdk-security-vulnerability/",
              "https://github.com/Freemius/wordpress-sdk/commit/50a7ca3d921d59e1d2b39bb6ab3c6c7efde494b8",
              "https://plugins.trac.wordpress.org/changeset/2039381/"
            ],
            "wpvulndb": [
              "6ff37c2e-e21d-4abc-bafe-8ca6a2c1ed76"
            ]
          }
        },
        {
          "title": "Nextgen Gallery < 3.2.11 - SQL Injection",
          "fixed_in": "3.2.11",
          "references": {
            "cve": [
              "2019-14314"
            ],
            "url": [
              "https://fortiguard.com/zeroday/FG-VD-19-099",
              "https://www.fortinet.com/blog/threat-research/wordpress-plugin-sql-injection-vulnerability.html"
            ],
            "wpvulndb": [
              "01732835-90f6-48f2-8f51-a8a09c97b076"
            ]
          }
        },
        {
          "title": "NextGen Gallery < 3.5.0 - CSRF allows File Upload, Stored XSS, and RCE",
          "fixed_in": "3.5.0",
          "references": {
            "cve": [
              "2020-35942"
            ],
            "url": [
              "https://www.wordfence.com/blog/2021/02/severe-vulnerabilities-patched-in-nextgen-gallery-affect-over-800000-wordpress-sites/"
            ],
            "wpvulndb": [
              "811beb4d-89b7-42bd-b387-ec588d318ef8"
            ]
          }
        },
        {
          "title": "NextGen Gallery < 3.5.0 - CSRF allows File Upload",
          "fixed_in": "3.5.0",
          "references": {
            "cve": [
              "2020-35943"
            ],
            "url": [
              "https://www.wordfence.com/blog/2021/02/severe-vulnerabilities-patched-in-nextgen-gallery-affect-over-800000-wordpress-sites/"
            ],
            "wpvulndb": [
              "7e1f1083-4c41-41c8-bbf0-640484384196"
            ]
          }
        }
      ],
      "version": {
        "number": "2.2.3",
        "confidence": 60,
        "found_by": "Comment (Passive Detection)",
        "interesting_entries": [
          "REDACTEDURL, Match: '<meta name=\"NextGEN\" version=\"2.2.3\"'"
        ],
        "confirmed_by": {

        }
      }
    },
    "shadowbox-js": {
      "slug": "shadowbox-js",
      "location": "REDACTEDURLwp-content/plugins/shadowbox-js/",
      "latest_version": "<IP_ADDRESS>.2",
      "last_updated": "2012-04-20T15:32:00.000Z",
      "outdated": false,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Urls In Homepage (Passive Detection)",
      "confidence": 80,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [

      ],
      "version": null
    },
    "simply-poll": {
      "slug": "simply-poll",
      "location": "REDACTEDURLwp-content/plugins/simply-poll/",
      "latest_version": "1.4.1",
      "last_updated": "2012-01-05T16:11:00.000Z",
      "outdated": false,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Urls In Homepage (Passive Detection)",
      "confidence": 80,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [
        {
          "title": "Simply Poll 1.4.1 - wp-admin/admin.php question Parameter XSS",
          "fixed_in": null,
          "references": {
            "exploitdb": [
              "24850"
            ],
            "url": [
              "https://packetstormsecurity.com/files/120833/"
            ],
            "wpvulndb": [
              "29ef1824-cdbc-4135-9798-12b00f06efd8"
            ]
          }
        },
        {
          "title": "Simply Poll 1.4.1 - wp-admin/admin.php Poll Manipulation CSRF",
          "fixed_in": null,
          "references": {
            "exploitdb": [
              "24850"
            ],
            "url": [
              "https://packetstormsecurity.com/files/120833/"
            ],
            "wpvulndb": [
              "3be72fb8-d5c3-4158-8e2e-7db7b1b173b5"
            ]
          }
        }
      ],
      "version": null
    },
    "wp-pagenavi": {
      "slug": "wp-pagenavi",
      "location": "REDACTEDURLwp-content/plugins/wp-pagenavi/",
      "latest_version": "2.94.0",
      "last_updated": "2021-05-25T02:33:00.000Z",
      "outdated": false,
      "readme_url": null,
      "directory_listing": null,
      "error_log_url": null,
      "found_by": "Urls In Homepage (Passive Detection)",
      "confidence": 80,
      "interesting_entries": [

      ],
      "confirmed_by": {

      },
      "vulnerabilities": [

      ],
      "version": null
    }
  },
  "config_backups": {

  },
  "vuln_api": {
    "plan": "professional_yearly",
    "requests_done_during_scan": 9,
    "requests_remaining": 216
  },
  "stop_time":<PHONE_NUMBER>,
  "elapsed": 15,
  "requests_done": 205,
  "cached_requests": 5,
  "data_sent": 46395,
  "data_sent_humanised": "45.308 KB",
  "data_received": 320640,
  "data_received_humanised": "313.125 KB",
  "used_memory": 308379648,
  "used_memory_humanised": "294.094 MB"
}

@BoBeR182 thanks, will work on it.

I'm able to reproduce it on master and 2.6.2
I'm not able to reproduce the error and the report load well with dev
So I confirm that there is a bug with previous versions.

It seems that one maintenance PR added a check to fix this bug : https://github.com/DefectDojo/django-DefectDojo/pull/5562
If you take a look at the code of the commit, the parser check if the data exists:

I'm afraid you will be forced to upgrade to 2.7.0 to have this fix ready.

@BoBeR182 it should be ok for 2.7.0


Switch off of pkgdown for website

Right now the web-presence for the ui editor is done with a pkgdown site. This is inherently tied to the R package and also is a bit of a mismatch for the scope of the project. The website should be decoupled from the R package so it can treat Python as a first-class citizen and also have a more flexible setup.
One thing to keep in mind is we probably want to use a toolset/chain that the userbase is familiar with so it's not impossible for users to contribute things like articles or typo fixes etc. This means probably not making it something like a full next.js app and instead using Quarto most likely.

Done in #201


Allow List: Using "Stable" still allows pre-release versions

Testing #234993
I am using the pre-release version of github copilot chat and setting:
"extensions.allowed": { "github": "stable" }
Does not disable the chat extension or causes any change to it.

Good catch!


[Tech]: Add KYC documents link ahead of application

Problem statement
Users experienced unclear rejection because their proof of address were not accepted by our partner.
Sumsub is currently rejecting neobank bank statements: Revolut, N26, ...
It should work if you apply with a regular commercial bank statement. We want to make sure the user is aware before starting the application process and KYC.
Description
No response
Definition of Done
Add the following disclaimer on the "Get SORA Card" page:
"You will need to provide the following documents in order to successfully pass the KYC."
"the following documents" leads to a page with
Identification:
National ID card
Passport
Proof of Address:

Bank statement (NOT from a neobank like Revolut or N26)
Utility bill for gas, electricity, water, etc. linked to the property.
Letters from a recognized public authority or public servant/any government-issued correspondence.
Current lease agreement with signatures of the landlord and the tenant.
Credit card statement.
Employer’s certificate for proof of residence.
House purchase deed.
*For 1) and 2), it’s common practice to reject proof of address documents older than 3 months.

Requirements
No response

Duplicates #94


Support local project dependencies

grease(project(":other-project")) doesn't work: https://github.com/deepmedia/Grease/blob/v0.3.0/tests/sample-library/build.gradle.kts#L71-L73

It looks strange because main purpose of agp 8 support was  to fix local projects merging :) I have tested it now and it works for me...

It failed for me today on that line, using cd tests && ../gradlew sample-library:assembleDebug. Something like that.
I guess AGP properly configures api and implementation configurations to fallback on release buildType, but we may have to do the same on grease configurations.


review trigger matching

Should include new triggers (EG, MuonEG, Diphoton Double Tau and Tau)

done