text:
Setup for building workers

This adds a task that transforms modules in the src/ol/worker directory into modules that export a create function that returns a new worker with the source of the original module.  When serving the examples, we configure a custom loader that transforms the worker modules (without minification).  Same goes for running the tests.  When the rendering tests depend on a worker, we can update the webpack config there to use the same loader.
I added an example worker that posts messages with the current version identifier.  This is not meant to stick around, but it demonstrates a worker with dependencies.  The example and test should also be deleted before a release, but they can serve as a starting point for developing more full featured workers.
With this setup, we can decide how many worker factories we want.  It may make sense to have only one initially, but eventually we may want separate workers so we don't pile all dependencies into one.
I anticipate that we'll also want to add in some utilities for message handling.  We can do this by adding utility modules that are dependencies of either the worker itself or the module that creates the worker.  I think we can do this without complicating the way workers are serialized.
Fixes #9547.

Hi,
I've tried adding a webgl worker based on this branch and it dit work really well! Setting up a new worker is straightforward, it just requires adding export default create; at the end and call that same create function when instantiating a worker. Very simple and elegant IMO.
Can't wait to dig more into optimization now!

authors: jahow tschaub


text:
creating a ci/cd pipeline for complete automation of deployment procedure

since the deployment part of the tool is still done by manually we really need a ci/cd pipeline to automate our deployment task further to production. we can add various types of practices while building our pipeline since our code is on github gitops can be beneficial for us, what do you think @pleia2 & @arshPratap ??

We have a basic implementation of this using GitHub Actions in this repository https://github.com/openmainframeproject/software-discovery-tool-deploy so that's where you'll want to start with enhancements to the process, there are a few open bugs about parts where it's a bit broken in production.

Thank you @pleia2 i'll take a look!

Closing in favor of specific issues in -deploy repository.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Update auto-generated documentation

Repository: openmicroscopy/ome-documentation
Already up-to-date.
Generated by build OMERO-5.1-latest-docs-autogen#822.

--no-rebase

Looks good just running merge built to confirm before merging

All good on staging, merging for release

source: gharchive/pull-request

authors: hflynn snoopycrimecop

repo: openmicroscopy/ome-documentation


text:
Questions regarding some specific parameters

Hello,
I have a couple of questions that I would love some answers.
First I would like to know if there is any information on precision of PM8, as it has been done to PM7 on the mopac website.
The second is that I am trying to run a polymer to calculate the vibration, but it says "Insufficient memory to run FORCE", I have 16 gb of Ram which is probably not much, and I am even using MOZYME recommended by the package. I guess there is nothing to be done correct? I even used FORCETS. It is very interesting that the energy minimization runs quite fine using PM7, RM1...
Lastly, I would like to know which kind of compounds THERMO should be used for, I tried to run some common drugs and none fits the criteria (paracetamol or caffeine). The system is only increasing as a straight line ? I don't know if it is my lack of background on physics but that doesn't fit the experimental data on Cp. No error is reported to the log file as well by mopac.
MOPAC executable

[X] Using pre-built executable
[ ] Compiled my own executable

Operating system

[ ] Linux
[ ] Mac
[X] Windows
[ ] Other (specify below)

Additional context
Add any other context about the problem here. (e.g. Linux distribution if that might be relevant)

I can answer these questions, and I've also made some changes to the development version of MOPAC in response to them (that will appear in the next MOPAC release).

There is no PM8 model yet, although it is in development (@Honza-R is leading the development as far as I understand). There is a placeholder PM8 model in MOPAC, but it is just a copy of PM6 at the moment. If the PM8 keyword is used, I've added a note to the output file that the model is still in development.

There is an artificial size limiter on FORCE and FORCETS calculations, which I've removed from the development version. You should be able to get around the size limiter in older versions of MOPAC with FORCETS if you freeze the positions of many atoms in the system, which should then not count against the limit of 9000 vibrational degrees of freedom.

Beyond the discussion in the manual, I don't have a lot of expert advice to offer at the moment, as I haven't used the THERMO feature personally beyond some basic testing. I can at least say that it is certainly only applicable to the gas-phase form of whatever molecule you input. What do you mean by "none fits the criteria"? The two examples you mentioned (caffeine and paracetamol) have methyl groups with low-frequency rotational modes that may limit the accuracy of THERMO, but I'm not clear on the practical significance of this problem.

Please keep the PM8 model in the code - I'm using it for my parametrization experiments and it will turn into a real PM8 in the future. Keeping it in the code would make it easier to sync my development branch with the main version.

@ggoetten > Lastly, I would like to know which kind of compounds THERMO should be used for
As @godotalgorithm has pointed out, the manual clearly states that there should be no internal rotors. This excludes many molecules of interest, such as those with methyl groups, alas.
For a nice handle on this problem in general, you should looks at Grimme's work with their mRRHO methods,
implemented in the CREST package.
With some (not-quite-trivial) tweaks it can be applied to the FORCE output from MOPAC. I've got some quick-and-dirty script for this, if you are interested.

The relevant reference for CREST's anharmonic corrections appears to be [https://doi.org/10.1039/D1SC00621E]. It uses a model that regularizes the free-energy divergences from low-frequency modes by approximating them as coming from rigid rotors, which is probably a good approximation for the rotations of small sp3-bonded side groups as in the original post.
A path to interfacing between MOPAC and CREST would certainly be welcome. I'm planning to add a directory in the MOPAC repo for pre/post-processing scripts, and I've received a few contributions this year over email. This script might fit in there.

@godotalgorithm > a good approximation for the rotations of small sp3-bonded side groups as in the original post.
In fact mRRHO seems to handle much more, e.g. non-covalently bound complexes, as well. Indeed Grimme has a lot of earlier published work on it. The nice thing about CREST is that its THERMO module can be used as stand-alone processor for externally provided vibrational frequencies (so one need not re-implement the algo in MOPAC, although that would be nice too).
Regarding the script directory, having a dedicated place for collecting them is an excellent idea. I am too lazy/busy to learn something modern like Python for this, alas ;-), so my code is quaint in awk.
But it works for me.

I do have an interface to MOPAC in my Cuby framework (
http://cuby4.molecular.cz/) where the rotor approximation can be applied
(using the keyword 'thermo_low_mode_fix'). At the moment, this may be the
most straightforward access to this combination of methods.
On Wed, Jul 12, 2023 at 9:25 PM Zoli Fekete @.***>
wrote:

@godotalgorithm https://github.com/godotalgorithm > a good
approximation for the rotations of small sp3-bonded side groups as in the
original post.
In fact mRRHO seems to handle much more, e.g. non-covalently bound
complexes, as well. Indeed Grimme has a lot of earlier published work on
it. The nice thing about CREST is that its THERMO module can be used as
stand-alone processor for externally provided vibrational frequencies (so
one need not re-implement the algo in MOPAC, although that would be nice
too).
Regarding the script directory, having a dedicated place for collecting
them is an excellent idea. I am too lazy/busy to learn something modern
like Python for this, alas ;-), so my code is quaint in awk.
But it works for me.
—
Reply to this email directly, view it on GitHub
https://github.com/openmopac/mopac/issues/97#issuecomment-1633089595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4DRVPAGKBHPIFQLAPAUQDXP324DANCNFSM536ZF2CA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Cool! I've been tempted to try Cuby for quite some time, maybe this will push me over the edge to actually do it ;-)...

authors: Honza-R ggoetten godotalgorithm zfekete2

repo: openmopac/mopac


text:
Image not compliant with docker scan

Hello,
I was testing the base image openpim/production:1.5 for an application I was using. I ran a docker scan and it came back with a ton of vulnerabilities. I was wondering if we could get these critical and high security risks fixed. A big issue is node from the base image.
Summary of results:
Organization:      neilpasricha
Package manager:   deb
Project name:      docker-image|musing_sinoussi
Docker image:      musing_sinoussi
Platform:          linux/amd64
Base image:        node:16.9.1-buster
Licenses:          enabled

Tested 544 dependencies for known issues, found 569 issues.

Base Image          Vulnerabilities  Severity
node:16.9.1-buster  513              11 critical, 51 high, 51 medium, 400 low

Recommendations for base image upgrade:

Minor upgrades
Base Image         Vulnerabilities  Severity
node:16.13-buster  485              11 critical, 44 high, 31 medium, 399 low

Major upgrades
Base Image          Vulnerabilities  Severity
node:17.9.0-buster  438              3 critical, 27 high, 11 medium, 397 low

Alternative image types
Base Image               Vulnerabilities  Severity
node:18.1.0-buster-slim  70               0 critical, 1 high, 0 medium, 69 low
node:16.15.0-slim        70               0 critical, 1 high, 0 medium, 69 low
node:17-stretch-slim     87               0 critical, 2 high, 0 medium, 85 low
node:18.2-bullseye-slim  45               3 critical, 0 high, 0 medium, 42 low

A full detail of scan results are here:
High severity vulnerability found in tiff/libtiffxx5
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-TIFF-2420604
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > tiff/libtiff-dev@4.1.0+git191117-2~deb10u2 > tiff/libtiffxx5@4.1.0+git191117-2~deb10u2
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > tiff/libtiff-dev@4.1.0+git191117-2~deb10u2
  From: meta-common-packages@meta > tiff/libtiff5@4.1.0+git191117-2~deb10u2
  Fixed in: 4.1.0+git191117-2~deb10u4

✗ High severity vulnerability found in subversion/libsvn1
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-SUBVERSION-2635642
  Introduced through: subversion@1.10.4-1+deb10u2
  From: subversion@1.10.4-1+deb10u2 > subversion/libsvn1@1.10.4-1+deb10u2
  From: subversion@1.10.4-1+deb10u2
  Fixed in: 1.10.4-1+deb10u3

✗ High severity vulnerability found in postgresql-11/libpq5
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-POSTGRESQL11-1920111
  Introduced through: postgresql-11/libpq-dev@11.12-0+deb10u1
  From: postgresql-11/libpq-dev@11.12-0+deb10u1 > postgresql-11/libpq5@11.12-0+deb10u1
  From: postgresql-11/libpq-dev@11.12-0+deb10u1
  Fixed in: 11.14-0+deb10u1

✗ High severity vulnerability found in openssl
  Description: Loop with Unreachable Exit Condition ('Infinite Loop')
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-OPENSSL-2426310
  Introduced through: ca-certificates@20200601~deb10u2, meta-common-packages@meta, openssl/libssl-dev@1.1.1d-0+deb10u7
  From: ca-certificates@20200601~deb10u2 > openssl@1.1.1d-0+deb10u7
  From: meta-common-packages@meta > openssl/libssl1.1@1.1.1d-0+deb10u7
  From: openssl/libssl-dev@1.1.1d-0+deb10u7
  Fixed in: 1.1.1d-0+deb10u8

✗ High severity vulnerability found in openjdk-11/openjdk-11-jre-headless
  Description: CVE-2022-21476
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-OPENJDK11-2770093
  Introduced through: java-common/default-jre@2:1.11-71
  From: java-common/default-jre@2:1.11-71 > java-common/default-jre-headless@2:1.11-71 > openjdk-11/openjdk-11-jre-headless@11.0.12+7-2~deb10u1
  From: java-common/default-jre@2:1.11-71 > openjdk-11/openjdk-11-jre@11.0.12+7-2~deb10u1 > openjdk-11/openjdk-11-jre-headless@11.0.12+7-2~deb10u1
  From: java-common/default-jre@2:1.11-71 > openjdk-11/openjdk-11-jre@11.0.12+7-2~deb10u1
  Fixed in: 11.0.15+10-1~deb10u1

✗ High severity vulnerability found in openexr/libopenexr23
  Description: NULL Pointer Dereference
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-OPENEXR-1320028
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > openexr/libopenexr23@2.2.1-4.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > openexr/libopenexr-dev@2.2.1-4.1+deb10u1 > openexr/libopenexr23@2.2.1-4.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > openexr/libopenexr-dev@2.2.1-4.1+deb10u1

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2389282
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Heap-based Buffer Overflow
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2396505
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...
  Fixed in: 1:10.3.34-0+deb10u1

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use of Externally-Controlled Format String
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2396511
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...
  Fixed in: 1:10.3.34-0+deb10u1

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2396512
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...
  Fixed in: 1:10.3.34-0+deb10u1

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Stack-based Buffer Overflow
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2396513
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...
  Fixed in: 1:10.3.34-0+deb10u1

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27444
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766277
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27445
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766279
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27452
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766287
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27451
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766290
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27449
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766300
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Reachable Assertion
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766301
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: CVE-2022-27446
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766312
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766314
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766360
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766361
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Reachable Assertion
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766366
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766367
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766369
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766377
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766378
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766380
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766400
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766401
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766402
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766403
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766404
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766413
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766414
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in mariadb-10.3/mariadb-common
  Description: Buffer Overflow
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-MARIADB103-2766430
  Introduced through: mysql-defaults/default-libmysqlclient-dev@1.0.5
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1 > mariadb-10.3/mariadb-common@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb3@1:10.3.29-0+deb10u1
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1
  and 1 more...

✗ High severity vulnerability found in libxml2/libxml2-dev
  Description: Use After Free
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-LIBXML2-2413976
  Introduced through: libxml2/libxml2-dev@2.9.4+dfsg1-7+deb10u2, libxslt/libxslt1-dev@1.1.32-2.2~deb10u1, imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: libxml2/libxml2-dev@2.9.4+dfsg1-7+deb10u2
  From: libxslt/libxslt1-dev@1.1.32-2.2~deb10u1 > libxml2/libxml2-dev@2.9.4+dfsg1-7+deb10u2
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > libxml2/libxml2-dev@2.9.4+dfsg1-7+deb10u2
  and 1 more...
  Fixed in: 2.9.4+dfsg1-7+deb10u3

✗ High severity vulnerability found in gmp/libgmp-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-GMP-1920939
  Introduced through: gmp/libgmp-dev@2:6.1.2+dfsg-4, mysql-defaults/default-libmysqlclient-dev@1.0.5, meta-common-packages@meta
  From: gmp/libgmp-dev@2:6.1.2+dfsg-4
  From: mysql-defaults/default-libmysqlclient-dev@1.0.5 > mariadb-10.3/libmariadb-dev-compat@1:10.3.29-0+deb10u1 > mariadb-10.3/libmariadb-dev@1:10.3.29-0+deb10u1 > gnutls28/libgnutls28-dev@3.6.7-4+deb10u7 > nettle/nettle-dev@3.4.1-1+deb10u1 > gmp/libgmp-dev@2:6.1.2+dfsg-4
  From: meta-common-packages@meta > gmp/libgmp10@2:6.1.2+dfsg-4
  and 1 more...
  Fixed in: 2:6.1.2+dfsg-4+deb10u1

✗ High severity vulnerability found in gcc-8
  Description: Information Exposure
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-GCC8-347558
  Introduced through: gcc-defaults/g++@4:8.3.0-1, libtool@2.4.6-9, imagemagick@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: gcc-defaults/g++@4:8.3.0-1 > gcc-8@8.3.0-6
  From: libtool@2.4.6-9 > gcc-8@8.3.0-6
  From: gcc-defaults/g++@4:8.3.0-1 > gcc-8/g++-8@8.3.0-6 > gcc-8@8.3.0-6
  and 23 more...

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Resource Exhaustion
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2329087
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2330888
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331795
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331796
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331820
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ High severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2406126
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u3

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-1278421
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-1290628
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-1290629
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-1290633
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-1290638
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in djvulibre/libdjvulibre21
  Description: NULL Pointer Dereference
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-DJVULIBRE-481572
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6-extra@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre21@3.5.27.1-10
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > djvulibre/libdjvulibre-dev@3.5.27.1-10
  and 1 more...
  Fixed in: 3.5.27.1-10+deb10u1

✗ High severity vulnerability found in cyrus-sasl2/libsasl2-modules-db
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-CYRUSSASL2-2412041
  Introduced through: curl@7.64.0-4+deb10u2, subversion@1.10.4-1+deb10u2
  From: curl@7.64.0-4+deb10u2 > curl/libcurl4@7.64.0-4+deb10u2 > openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 > cyrus-sasl2/libsasl2-2@2.1.27+dfsg-1+deb10u1 > cyrus-sasl2/libsasl2-modules-db@2.1.27+dfsg-1+deb10u1
  From: subversion@1.10.4-1+deb10u2 > cyrus-sasl2/libsasl2-2@2.1.27+dfsg-1+deb10u1
  From: subversion@1.10.4-1+deb10u2 > subversion/libsvn1@1.10.4-1+deb10u2 > cyrus-sasl2/libsasl2-2@2.1.27+dfsg-1+deb10u1
  and 1 more...
  Fixed in: 2.1.27+dfsg-1+deb10u2

✗ Critical severity vulnerability found in pcre2/libpcre2-8-0
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-PCRE2-2808696
  Introduced through: git@1:2.20.1-2+deb10u3, wget@1.20.1-1.1
  From: git@1:2.20.1-2+deb10u3 > pcre2/libpcre2-8-0@10.32-5
  From: wget@1.20.1-1.1 > pcre2/libpcre2-8-0@10.32-5

✗ Critical severity vulnerability found in pcre2/libpcre2-8-0
  Description: Out-of-bounds Read
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-PCRE2-2808698
  Introduced through: git@1:2.20.1-2+deb10u3, wget@1.20.1-1.1
  From: git@1:2.20.1-2+deb10u3 > pcre2/libpcre2-8-0@10.32-5
  From: wget@1.20.1-1.1 > pcre2/libpcre2-8-0@10.32-5

✗ Critical severity vulnerability found in openssl
  Description: OS Command Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-OPENSSL-2807585
  Introduced through: ca-certificates@20200601~deb10u2, meta-common-packages@meta, openssl/libssl-dev@1.1.1d-0+deb10u7
  From: ca-certificates@20200601~deb10u2 > openssl@1.1.1d-0+deb10u7
  From: meta-common-packages@meta > openssl/libssl1.1@1.1.1d-0+deb10u7
  From: openssl/libssl-dev@1.1.1d-0+deb10u7
  Fixed in: 1.1.1n-0+deb10u2

✗ Critical severity vulnerability found in openldap/libldap-common
  Description: SQL Injection
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-OPENLDAP-2808412
  Introduced through: curl@7.64.0-4+deb10u2, gnupg2/dirmngr@2.2.12-1+deb10u1, git@1:2.20.1-2+deb10u3, postgresql-11/libpq-dev@11.12-0+deb10u1
  From: curl@7.64.0-4+deb10u2 > curl/libcurl4@7.64.0-4+deb10u2 > openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6 > openldap/libldap-common@2.4.47+dfsg-3+deb10u6
  From: gnupg2/dirmngr@2.2.12-1+deb10u1 > openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  From: curl@7.64.0-4+deb10u2 > curl/libcurl4@7.64.0-4+deb10u2 > openldap/libldap-2.4-2@2.4.47+dfsg-3+deb10u6
  and 2 more...
  Fixed in: 2.4.47+dfsg-3+deb10u7

✗ Critical severity vulnerability found in nss/libnss3
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-NSS-2306555
  Introduced through: java-common/default-jre@2:1.11-71
  From: java-common/default-jre@2:1.11-71 > java-common/default-jre-headless@2:1.11-71 > openjdk-11/openjdk-11-jre-headless@11.0.12+7-2~deb10u1 > nss/libnss3@2:3.42.1-1+deb10u3
  From: java-common/default-jre@2:1.11-71 > java-common/default-jre-headless@2:1.11-71 > openjdk-11/openjdk-11-jre-headless@11.0.12+7-2~deb10u1 > ca-certificates-java@20190405 > nss/libnss3@2:3.42.1-1+deb10u3
  Fixed in: 2:3.42.1-1+deb10u4

✗ Critical severity vulnerability found in libde265/libde265-0
  Description: Out-of-bounds Write
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-LIBDE265-2445048
  Introduced through: imagemagick@8:6.9.10.23+dfsg-2.1+deb10u1
  From: imagemagick@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/imagemagick-6.q16@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-6@8:6.9.10.23+dfsg-2.1+deb10u1 > libheif/libheif1@1.3.2-2~deb10u1 > libde265/libde265-0@1.0.3-1+b1

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331803
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331813
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2331818
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2359258
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2384929
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u2

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Improper Encoding or Escaping of Output
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2403513
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u3

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Exposure of Resource to Wrong Sphere
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2403518
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u3

✗ Critical severity vulnerability found in expat/libexpat1-dev
  Description: Integer Overflow or Wraparound
  Info: https://snyk.io/vuln/SNYK-DEBIAN10-EXPAT-2406128
  Introduced through: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1, meta-common-packages@meta
  From: imagemagick/libmagickcore-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > imagemagick/libmagickcore-6.q16-dev@8:6.9.10.23+dfsg-2.1+deb10u1 > librsvg/librsvg2-dev@2.44.10-2.1 > cairo/libcairo2-dev@1.16.0-4+deb10u1 > fontconfig/libfontconfig1-dev@2.13.1-2 > expat/libexpat1-dev@2.2.6-2+deb10u1
  From: meta-common-packages@meta > expat/libexpat1@2.2.6-2+deb10u1
  Fixed in: 2.2.6-2+deb10u3

Organization:      neilpasricha
Package manager:   deb
Project name:      docker-image|musing_sinoussi
Docker image:      musing_sinoussi
Platform:          linux/amd64
Base image:        node:16.9.1-buster
Licenses:          enabled

Tested 544 dependencies for known issues, found 569 issues.

Base Image          Vulnerabilities  Severity
node:16.9.1-buster  513              11 critical, 51 high, 51 medium, 400 low

Recommendations for base image upgrade:

Minor upgrades
Base Image         Vulnerabilities  Severity
node:16.13-buster  485              11 critical, 44 high, 31 medium, 399 low

Major upgrades
Base Image          Vulnerabilities  Severity
node:17.9.0-buster  438              3 critical, 27 high, 11 medium, 397 low

Alternative image types
Base Image               Vulnerabilities  Severity
node:18.1.0-buster-slim  70               0 critical, 1 high, 0 medium, 69 low
node:16.15.0-slim        70               0 critical, 1 high, 0 medium, 69 low
node:17-stretch-slim     87               0 critical, 2 high, 0 medium, 85 low
node:18.2-bullseye-slim  45               3 critical, 0 high, 0 medium, 42 low

-------------------------------------------------------

Testing musing_sinoussi...

Tested 384 dependencies for known issues, found 7 issues.

Issues to fix by upgrading:

  Upgrade formidable@2.0.1 to formidable@3.2.4 to fix
  ✗ Arbitrary File Upload (new) [Critical Severity][https://snyk.io/vuln/SNYK-JS-FORMIDABLE-2838956] in formidable@2.0.1
    introduced by formidable@2.0.1

Patchable issues:

  Patch available for lodash@4.17.15
  ✗ Prototype Pollution [High Severity][https://snyk.io/vuln/SNYK-JS-LODASH-567746] in lodash@4.17.15
    introduced by graphql-import@1.0.2 > @graphql-toolkit/core@0.10.3 > lodash@4.17.15 and 11 other path(s)

Issues with no direct upgrade or patch:
  ✗ Regular Expression Denial of Service (ReDoS) [Medium Severity][https://snyk.io/vuln/SNYK-JS-LODASH-1018905] in lodash@4.17.15
    introduced by graphql-import@1.0.2 > @graphql-toolkit/core@0.10.3 > lodash@4.17.15 and 11 other path(s)
  This issue was fixed in versions: 4.17.21
  ✗ Command Injection [High Severity][https://snyk.io/vuln/SNYK-JS-LODASH-1040724] in lodash@4.17.15
    introduced by graphql-import@1.0.2 > @graphql-toolkit/core@0.10.3 > lodash@4.17.15 and 11 other path(s)
  This issue was fixed in versions: 4.17.21
  ✗ Prototype Pollution [High Severity][https://snyk.io/vuln/SNYK-JS-LODASH-608086] in lodash@4.17.15
    introduced by graphql-import@1.0.2 > @graphql-toolkit/core@0.10.3 > lodash@4.17.15 and 11 other path(s)
  This issue was fixed in versions: 4.17.17
  ✗ Information Exposure [Medium Severity][https://snyk.io/vuln/SNYK-JS-NODEFETCH-2342118] in node-fetch@2.6.0
    introduced by graphql-import@1.0.2 > @graphql-toolkit/url-loader@0.10.3 > cross-fetch@3.0.4 > node-fetch@2.6.0
  This issue was fixed in versions: 2.6.7, 3.1.1
  ✗ Denial of Service [Medium Severity][https://snyk.io/vuln/SNYK-JS-NODEFETCH-674311] in node-fetch@2.6.0
    introduced by graphql-import@1.0.2 > @graphql-toolkit/url-loader@0.10.3 > cross-fetch@3.0.4 > node-fetch@2.6.0
  This issue was fixed in versions: 2.6.1, 3.0.0-beta.9

Organization:      neilpasricha
Package manager:   npm
Target file:       /server/package.json
Project name:      server
Docker image:      musing_sinoussi
Licenses:          enabled

-------------------------------------------------------

Testing musing_sinoussi...

Organization:      neilpasricha
Package manager:   maven
Target file:       /usr/share/ca-certificates-java
Project name:      musing_sinoussi:latest:/usr/share/ca-certificates-java
Docker image:      musing_sinoussi

Licenses:          enabled

✔ Tested musing_sinoussi for known issues, no vulnerable paths found.

-------------------------------------------------------

Testing musing_sinoussi...

Organization:      neilpasricha
Package manager:   maven
Target file:       /usr/share/java
Project name:      musing_sinoussi:latest:/usr/share/java
Docker image:      musing_sinoussi
Licenses:          enabled

✔ Tested musing_sinoussi for known issues, no vulnerable paths found.

Tested 4 projects, 2 contained vulnerable paths.

Hello,
If wee wanted to use the openpim service modified to pass our vulnerability checks, how do we do that? I have copied the repo into my own and modified what I needed for security, but it seems now that the service is copying external files itself too. Is it possible to get access to those files in order to use this in our repo? Currently when running the image nothing happens (with just the files existing in the repo). Thank you!

Hi @neil-pasricha,
What about to have a call and discuss this together? Please write me an email at vpedak@openpim.org and we will arrange a call. Hope we will be able to resolve this issue.
Thanks,
Slava Pedak

Hello, I sent an email yesterday to reach out. We have the web and the server communicating, but when we try to login as admin we end up with this screen which will not let us select values or move past:

Any help with this?

Hi @neil-pasricha,
I already answered your email, did you receive response?
Regarding this issue with login, this is special was to login when user if a super user (if you creates such one). Usually you should not have such login. Can you please take a look what data you have in users database table for this user?
What tenantId is has?
Thanks,
Slava Pedak

authors: neil-pasricha openpim

repo: openpim/server


text:
Added API Console

This adds an API Console to NadeoServices, available when developer mode is enabled.

We'll probably want to populate ApiConsoleRoutes*.json files a bit more before merging.

This is turning out to be a larger amount of code than I thought, so I might branch it off into a new plugin for the website instead. For now, it will remain to live in the branch, but I will move it soon.

This has now moved to its own repository: https://github.com/codecat/tm-api-console

repo: openplanet-nl/nadeoservices

license: MIT


text:
Automatic filename problem

Perhaps it's only searching within the same journal or something. There's a conflict, but the lettering is working somewhat.

So to clarify. custom_filename() renames uploaded PDF files so they follow the pattern [first author's last name]_[year][letter].pdf. This is so that all the filenames have a consistent format, which is nice for people downloading pubs. The letter part of the name is based on the number of previous pubs published by that first author that year. The first pub get's a, the second, b, and so on.
Above we can see that this pattern is generally, but not entirely followed. Why? It's not because of an error in the code, per se, it's because the publications were added in the wrong order. To keep names consistent, they must be added in chronological order -- oldest first. If one does not do this, the following will happen:

Pub from 2016 August by author X is uploaded. The function checks how many previous pubs by this author that year and finds 0. The pub gets the name X_2016a.pdf.
Pub from 2016 April by author X is uploaded. The function checks how many previous pubs by this author that year and finds 0. The pub gets the name X_2016a.pdf.
Conflict. Both pubs would be named X_2016a.pdf. To avoid conflict, Django renames the second one by adding some filler characters at the end, as can be seen in the code above.

Solutions:

A: Add pubs in chronological order: oldest first. This problem never happens.
B: Make a fancy function that checks all files and renames them.

In general, once we get the database full of old content, this problem will never again arise as pubs are always added in chronological order, i.e. in the order they get published.
I will go with solution (A) above. The current naming problems can be helped simply by reuploading the papers in the right order.

repo: openpsych/django

license: mit

license_source: bigquery


text:
EIC console - add reviewer rating

add reviewer rating in review progress column under reviewer status tab
add a rating column under reviewer status tab

Is there a way to show the counters in the same line always?

Is there a way to show the counters in the same line always?

please try 0b80483

average rating is added in 8e6eeb8
it assumes that the rating text used in reviewer rating invitations (and thus in the dropdown in note editor) are all the same and is the same as in the map defined in EIC webfield

authors: melisabok xkopenreview

repo: openreview/openreview-py


text:
Feature/optimize consoles

Some optimizations for the author, reviewer, area chair and program chair consoles
EDIT: This PR will fail until this PR is merged

I tested with a few existing large venues and got some very impressive results! I tested each with a clean cache and a hard refresh (in parens) and with a primed cache and a normal refresh. Also I logged in as a PC for each group to try to make the test as realistic as possible. I didn't test the 10k submission test venue, but I'd be interested to see the results for that as well.

Venue
URL
Loading Time (old)
Loading Time (new)

ECCV 2020
PC Console
19.9s (20.5s)
5.8s (15s)

ICLR 2021
PC Console
10.1s (27.3s)
3.5s (8.2s)

ICLR 2020
PC Console
3.7s (16.4s)
2.8s (6.2s)

Wow! Thanks for making such thorough testing @zbialecki! I really hope this reduces the stress in Mongo as well.

authors: carlosmondra zbialecki


text:
[openrr-gui] Add text input to set duration and improve error handling about text input

cc https://github.com/openrr/openrr/issues/101

https://user-images.githubusercontent.com/43724913/109290713-505c6b80-786b-11eb-8df4-57798da0b059.mov

repo: openrr/openrr


text:
LE changed the certbot interface for requesting staging certs

--dry-run now doesn't write any certs to disk

https://github.com/slateci/container-osg-hostedce/issues/4


text:
Improved best first level calculation

Fixes #1197
The issue hinges around the levelVisibility calculation that's based in part on TileSource.getClosestLevel. With 254px tiles, the response from getClosestLevel is reasonable, but with 500px tiles it just returns 0.
I'm not actually sure why getClosestLevel compares against the container size. It seems to me the best thing to do is just find the highest level where the entire image can fit on a single tile, so I changed it to do that, and in my testing the results are good: regardless of the tile size or the viewer size, the first tile that's loaded is the largest single-tile level, and then higher level tiles are loaded to fill in the remainder.
If you force the defaultZoomLevel to be something small, it will start with a lower level, since it doesn't need a tile as large as the largest single-tile level. If you force defaultZoomLevel to something big, it still starts with the largest single-tile level (unless you have immediateRender on), since we don't want to risk having holes. All seems good to me.
Even though getClosestLevel is technically a documented function, I'm not terribly concerned about changing it like this; it's not really a function people would use, and it still produces the same kind of value (even if the logic is different now), and ignoring the old argument isn't really a breaking change. Also note that this function is currently called in only one place. I suppose I could at least improve its documentation.
That said, I'd love a second opinion... @avandecreme, what do you think?
@rmcloughlin, can you verify that this fixes the issue you found?

When I apply this change to the test page I made in https://github.com/rmcloughlin/osd-tile-loading, this PR fixes the problem perfectly; no low layer images are fetched at all.
However in my actual application things still act a bit strange.  My image is about 60,000 (w) by 40,000 (h) with tile size 1024 and overlap 1.  Before the fix is applied (using OSD 2.2.1). The tiles are loaded in this order:
0/0_0.jpeg
1/0_0.jpeg
8/0_0.jpeg
2/0_0.jpeg
7/0_0.jpeg
3/0_0.jpeg
6/0_0.jpeg
4/0_0.jpeg
5/0_0.jpeg
9/0_0.jpeg
10/0_0.jpeg
11/0_0.jpeg
11/1_0.jpeg
11/0_1.jpeg
11/1_1.jpeg

When I use OSD that was built from this PR, the tiles are loaded in the following order:
10/0_0.jpeg
11/0_0.jpeg
8/0_0.jpeg
11/1_0.jpeg
7/0_0.jpeg
11/0_1.jpeg
6/0_0.jpeg
11/1_1.jpeg
5/0_0.jpeg
9/0_0.jpeg
4/0_0.jpeg
3/0_0.jpeg
2/0_0.jpeg
1/0_0.jpeg
0/0_0.jpeg

So in this case it's still loading the low-layer tiles but it's getting them after loading the more appropriate tiles.

@rmcloughlin That second issue you're seeing is the one fixed by #1193. To see both this patch and the other patch together you can use this combined branch:
https://github.com/openseadragon/openseadragon/tree/ig-both
Could you try that one and verify that it does the right thing?

Yes that one (ig-both) works better.  It makes fewer requests and doesn't request all the low layer images (like 0/0_0.jpeg, 1/0_0.jpeg).

@rmcloughlin Awesome, thank you for testing it!
I'll leave this open for a few more days to see if @avandecreme (or anyone else) has anything to add.

authors: iangilman rmcloughlin

repo: openseadragon/openseadragon


text:
Some dependency updates

Signed-off-by: Andriy Redko andriy.redko@aiven.io
Description
Routine dependency updates
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Why isn't dependabot doing @reta's work?

Always forgetting about proper labels, thanks a lot @saratvemulapalli !

Why isn't dependabot doing @reta's work?

Cuz it inspect build.gradle but we have not found the way yet to tell depandabot to look into version.properties, we track it under https://github.com/opensearch-project/OpenSearch/issues/3782

@dblock do you see risks backporting to 2.x?

@reta unless it breaks things in 2.x, from the look it seems fine.

authors: dblock reta saratvemulapalli

repo: opensearch-project/OpenSearch


text:
Update several dependencies

Signed-off-by: Tyler Ohlsen ohltyler@amazon.com
Description
Updates several dependencies to resolve CVEs

ansi-regex
glob-parent
loader-utils

Note that these all come from upstream core Dashboards. They have been patched by adding them in a resolutions field in package.json, which forces dependencies of all versions to resolve to a version that is patched. I've copied the versions directly from core Dashboards' package.json for version parity and to guarantee we have patched the CVEs for these. After updating package.json, I ran yarn osd bootstrap to update the lockfile.
We only need to backport to 2.x such that the next releases will have these patches.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Cypress tests failed, I'm unsure why JS 3.0 is now unavailable as the previous merged PR worked just fine:
Could not determine the dependencies of task ':run'.
> Can't get https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/3.0.0/latest/linux/x64/tar/builds/opensearch/plugins/opensearch-job-scheduler-3.0.0.0.zip

Codecov Report

Merging #339 (25148f8) into main (d8af147) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #339   +/-   ##
=======================================
  Coverage   52.04%   52.04%
=======================================
  Files         147      147
  Lines        5015     5015
  Branches      965      965
=======================================
  Hits         2610     2610
  Misses       2148     2148
  Partials      257      257

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Cypress tests failed, I'm unsure why JS 3.0 is now unavailable as the previous merged PR worked just fine:
Could not determine the dependencies of task ':run'.
> Can't get https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/3.0.0/latest/linux/x64/tar/builds/opensearch/plugins/opensearch-job-scheduler-3.0.0.0.zip

This is due to the latest build not including JS because of some broken builds caused by https://github.com/opensearch-project/anomaly-detection/issues/713.
That issue needs to be addressed, and then later builds may include all plugins, including JS

are we trying to include this in 2.4? or is it okay to wait for AD fix so CI passes here?

are we trying to include this in 2.4? or is it okay to wait for AD fix so CI passes here?

We can wait for the AD fix. Not needed in 2.4.

It will be fixed in https://github.com/opensearch-project/anomaly-detection/pull/714, and then after some time once the infra builds have AD and JS we can re-run CI here.

https://github.com/opensearch-project/sql/issues/1065 is still blocking a 3.0 build

3.0 is consistently failing still - will go ahead and merge and re-run CI once there is an available build.

authors: amitgalitz codecov-commenter ohltyler


text:
[BUG] Event Explorer Home breadcrumb doesn't seem to do anything - should it be removed?

What is the bug?
A clear and concise description of the bug.

How can one reproduce the bug?
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?

OS: [e.g. iOS]
Version [e.g. 22]
Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

Outdated


text:
[RFC] Data Prepper Expression Syntax

Is your feature request related to a problem? Please describe.
As part of a larger feature (#522) to support complex condition statements in data prepper there is a need to define a syntax for conditional statements. A conditional statement is a String that is evaluated at runtime and may reference fields within a record.
Describe the solution you'd like
Terms used throught this document are defined in the Definitions section
Supported Operators in order of evaluation priority

List Initialiser []
Priority Expression ()
List Operators in, not in
Relational Operators <, <=, >, >=
Regex Equality Operators =~, !~
Equality Operators ==, !=
Conditional Expression and, or, not

List Initialiser
Defines a list or term and/or expressions.
Examples
[1, 2, 3]
["a", "b", "c"]
[/people/0/name, /status==500]

Priority Expression
Identifies an expression that will be evaluated at the highest priority level
Examples
/is_cool == (true or false)

List Operators
Tests if a value is in/not in a list. Note, the right hand side operand must be a list.
Syntax
<Expression> in <List>
<Expression> not in <List>

Examples
/status_code in [200, 202]

Relational Operators
Tests the relationship of two numeric values. Note, the operands must be a number or Json Pointer that will resolve to a number.
Syntax
<Number | Json Pointer> < <Number | Json Pointer>
<Number | Json Pointer> <= <Number | Json Pointer>
<Number | Json Pointer> > <Number | Json Pointer>
<Number | Json Pointer> >= <Number | Json Pointer>

Examples
3 < 4

Regex Equality Operators
Used to test if a String value matches/does not match a Regular Expression. Note, the left hand side operand must be a string or Json Pointer that resolves to a String. The right hand side operand must be a String that contains a regular expression or a Json Pointer that resolves to a String that contains a regular expression.
Syntax
<String | Json Pointer> =~ <Regex String | Json Pointer>
<String | Json Pointer> !~ <Regex String | Json Pointer>

Examples
"Hello World" =~ "^[A-Za-z\s]*$"
"Hello!" !~ "\s"

Equality Operators
Used to test if two value are/are not equivalent.
Syntax
<Any> == <Any>
<Any> != <Any>

Examples
true == true
3.14 != /status_code
[1, 2] == /some/collection

Conditional Expression
Used to chain together multiple expressions and/or values.
Syntax
<Any> and <Any>
<Any> or <Any>
not <Any>

Examples
/status_code == 200 and /message == "Hello world"
/status_code == 200 or /status_code == 202
not /status_code in [200, 202]

Describe alternatives you've considered (Optional)
n/a
Additional context
Definitions
Literal A fundamental value that has no children.

Float
Integer
Boolean
Json Pointer
String

Expression String
The String that will be parsed for evaluation. Note, an Expression String is not the same as an Expression
Statement
The highest level component of the Expression String.
Expression
A generic component that contains a Primary or an Operator. Expressions may contain expressions. An expressions imminent children can contains 0-1 Operators.
Primary
A List, Priority Expression, or Literal.
Operator
Hard coded token that identifies the operation use in an Expression.
Json Pointer
A Literal used to reference a value within the Event provided as context for the Expression String. Json Pointers are identified by a leading / containing alpha numeric character or underscores, delimited by /. Json Pointers can use an extended character set if wrapped in double quotes (") using the escape character \. Note, Json Pointer require ~ and / that should be used as part of the path and not a delimiter to be escaped.

~0 representing ~
~1 representing /

White Space
White space is insignificant and will be removed at the start of parsing unless the whitespace is part of a Literal surrounded by double quotes (").

Thanks for putting this together! It looks great.
One change I'd like to make is to use the term "set" instead of "list." For example, the section "List Operators" should be "Set Operators." I think that we are viewing them as sets, so it would be better to be explicit in that.
Along those lines, I also wonder if it would make sense to change the syntax for set initialization. Perhaps a set could be initialized with curly braces like {"a", "b", "c"}. This is a more common convention for sets whereas brackets are lists.
I'm not sure if Data Prepper will ever need to evaluate against true lists or not. Perhaps /myList == ["a", "b"] will matter to somebody. Using curly braces will help keep these concepts distinct.
There may be some value in supporting variables in the future too. I'd probably say Data Prepper would use the standard ${} syntax. I don't think this would be a problem with {} sets, but do want to point it out.

Great feedback!
I'd like to add that variable names should be supported within string "Hello ${name}". To support embedded variables $ will need to be escaped within Strings.

5 + 5
true == true
How would customer use these examples?

Do we need assignment operators? How will they be used?

Do we need Increment (++) and Decrement Arithmetic Operators?
What are min and max values for Integer literal ?
Do we set set concatenation ?

Thanks @sbayer55 ,
You added set initializer to 1.3.0, but set operations to 1.4.0. Is there value in having the initializers without the operations? If not, I'd say we add set initialization in 1.4.0 as well.
Also, Data Prepper may want to support a limited set of functions in the future. For example length(/list). I'm not sure that is what we'd do or not. But, it may be valuable to disallow whitespace before parenthesis. So /a and(/b or /c) could be confused with a function. Should Data Prepper tighten restrictions regarding whitespace?

Issues regarding white space and potential future function support raised.

Perhaps it is too late to comment on this RFC, but I would like a little clarity on expressions for matching against string values with . characters (as this seems to be quite common for OTEL data). In the JSON Pointer definition it says

Json Pointers can use an extended character set if wrapped in double quotes (") using the escape character \. Note, Json Pointer require ~ and / that should be used as part of the path and not a delimiter to be escaped.

And I also see the "Escaped Example" above; however, when trying to write my own expression I am not able to get it to work for conditional routing with something like this (trying to escape my . characters):
  route:
    - super-tenant: '/"span\.attributes\.tenant" == "super"'
    - other-tenant: '/"span\.attributes\.tenant" != "super"'

Do you have any recommendations for this scenario? Thanks!
I also commented on https://github.com/opensearch-project/data-prepper/issues/2259

repo: opensearch-project/data-prepper


text:
[DOC]Create documentation for _mget API

What do you want to do?

[ ] Request a change to existing documentation
[x ] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

 GET /_mget
POST /_mget
GET /<index>/_mget
POST /<index>/_mget

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

We have documentation for mget here: https://opensearch.org/docs/latest/api-reference/document-apis/multi-get/. @kolchfa-aws , does this suffice, or is something missing? Thanks.

POST is missing

As shown in the following screenshot, POST mget does exist in the current API reference.

authors: Naarcha-AWS hdhalter kolchfa-aws


text:
Revert "Add documentation for security config upgrade feature (#6634)"

Description
This reverts commit 6f862fa69d674c86a1c19f0e8262da987d8bf2cd.  The feature was missed in the 2.13 release and will be included in 2.14
Issues Resolved

Related https://github.com/opensearch-project/documentation-website/pull/6955

Checklist

[ ] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

the backport to 2.13 failed

This change targeted the 2.13 branch, so no backport is needed since this will be out in the next release.

the backport to 2.13 failed

This change targeted the 2.13 branch, so no backport is needed since this will be out in the next release.

Did we not previously merge it into 2.13?

the backport to 2.13 failed

This change targeted the 2.13 branch, so no backport is needed since this will be out in the next release.

Did we not previously merge it into 2.13?

I see, you reverted the original PR. No need to backport. :)

authors: hdhalter peternied


text:
Add support for codeowners to repo

Signed-off-by: Ryan Bogan rbogan@amazon.com
Description
Add support for codeowners to repo
Issues Resolved
Progress on:
Meta issue
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ryanbogan Amy updates on this? Looks like it is lying stale since a long time here.

I used the same formatting for every repo and did not encounter any problems so I do not believe that the spacing matters.

@bbarani please approve.
Thanks.

authors: TheAlgo peterzhuamazon ryanbogan

repo: opensearch-project/helm-charts


text:
[BUG] Incomplete search results against rollup index composed of data from multiple rollup jobs

Describe the bug
Incomplete results when querying rollup index with date histogram.
To Reproduce
Enter the following into the dev console and execute each query in sequence (waiting for completion of rollup jobs at that step)
# Insert some test data

POST sharej-data-2023-07-25/_doc
{
  "timestamp": "2023-07-25T14:10:43.1",
  "numberOfCalls": 1
}

POST sharej-data-2023-07-25/_doc
{
  "timestamp": "2023-07-25T14:12:43.1",
  "numberOfCalls": 1
}

POST sharej-data-2023-07-24/_doc
{
  "timestamp": "2023-07-24T13:14:43.1",
  "numberOfCalls": 4
}

POST sharej-data-2023-07-23/_doc
{
  "timestamp": "2023-07-23T15:11:43.1",
  "numberOfCalls": 2
}

POST sharej-data-2023-07-23/_doc
{
  "timestamp": "2023-07-23T17:18:43.1",
  "numberOfCalls": 4
}

# Create rollup job for above indexes, emulating what happens when you have an ISM policy applying the rollup to each index after X days
PUT _plugins/_rollup/jobs/sharej-rollup-2023-07-23
{
  "rollup": {
    "enabled": true,
    "source_index": "sharej-data-2023-07-23",
    "target_index": "rollup-sharej-data-2023",
    "schedule": {
      "interval": {
        "start_time": 1,
        "period": "1",
        "unit": "Minutes"
      }
    },
    "description": "Test rollup",
    "page_size": 1000,
    "delay": 0,
    "continuous": false,
    "dimensions": [
      {
        "date_histogram": {
          "source_field": "timestamp",
          "fixed_interval": "1h",
          "timezone": "UTC"
        }
      }
    ],
    "metrics": [
      {
        "source_field": "numberOfCalls",
        "metrics": [
          {
            "avg": {}
          },
          {
            "sum": {}
          },
          {
            "max": {}
          },
          {
            "min": {}
          },
          {
            "value_count": {}
          }
        ]
      }
    ]
  }
}

PUT _plugins/_rollup/jobs/sharej-rollup-2023-07-24
{
  "rollup": {
    "enabled": true,
    "source_index": "sharej-data-2023-07-24",
    "target_index": "rollup-sharej-data-2023",
    "schedule": {
      "interval": {
        "start_time": 1,
        "period": "1",
        "unit": "Minutes"
      }
    },
    "description": "Test rollup",
    "page_size": 1000,
    "delay": 0,
    "continuous": false,
    "dimensions": [
      {
        "date_histogram": {
          "source_field": "timestamp",
          "fixed_interval": "1h",
          "timezone": "UTC"
        }
      }
    ],
    "metrics": [
      {
        "source_field": "numberOfCalls",
        "metrics": [
          {
            "avg": {}
          },
          {
            "sum": {}
          },
          {
            "max": {}
          },
          {
            "min": {}
          },
          {
            "value_count": {}
          }
        ]
      }
    ]
  }
}

PUT _plugins/_rollup/jobs/sharej-rollup-2023-07-25
{
  "rollup": {
    "enabled": true,
    "source_index": "sharej-data-2023-07-25",
    "target_index": "rollup-sharej-data-2023",
    "schedule": {
      "interval": {
        "start_time": 1,
        "period": "1",
        "unit": "Minutes"
      }
    },
    "description": "Test rollup",
    "page_size": 1000,
    "delay": 0,
    "continuous": false,
    "dimensions": [
      {
        "date_histogram": {
          "source_field": "timestamp",
          "fixed_interval": "1h",
          "timezone": "UTC"
        }
      }
    ],
    "metrics": [
      {
        "source_field": "numberOfCalls",
        "metrics": [
          {
            "avg": {}
          },
          {
            "sum": {}
          },
          {
            "max": {}
          },
          {
            "min": {}
          },
          {
            "value_count": {}
          }
        ]
      }
    ]
  }
}

# Watch status of rollup jobs until complete

GET _plugins/_rollup/jobs/sharej-rollup-2023-07-23/_explain

GET _plugins/_rollup/jobs/sharej-rollup-2023-07-24/_explain

GET _plugins/_rollup/jobs/sharej-rollup-2023-07-25/_explain

# Execute query against source data. Three buckets returned
GET sharej-data-2023-*/_search
{
  "size": 0,
  "query": {
    "match_all": {}
  },
  "aggregations": {
    "by_day": {
      "date_histogram": {
        "field": "timestamp",
        "fixed_interval": "1d"
      },
      "aggregations": {
        "totalCalls": {
          "sum": {
            "field": "numberOfCalls"
          }
        }
      }
    }
  }
}

# Execute query against rollup data. Only 1 bucket returned!?!?!? Where's the rest of the data?
GET rollup-sharej-data-2023/_search
{
  "size": 0,
  "query": {
    "match_all": {}
  },
  "aggregations": {
    "by_day": {
      "date_histogram": {
        "field": "timestamp",
        "fixed_interval": "1d"
      },
      "aggregations": {
        "totalCalls": {
          "sum": {
            "field": "numberOfCalls"
          }
        }
      }
    }
  }
}

# Execute against rollup data without query. Expected result again (but this isn't the query we get when adding a visualisation)
GET rollup-sharej-data-2023/_search
{
  "size": 0,
  "aggregations": {
    "by_day": {
      "date_histogram": {
        "field": "timestamp",
        "fixed_interval": "1d"
      },
      "aggregations": {
        "totalCalls": {
          "sum": {
            "field": "numberOfCalls"
          }
        }
      }
    }
  }
}

Expected behavior
All three queries at the end should return the same results. What appears to be happening is that the results from only one of the rollup jobs are returned when the query parameter is provided to the search against the rollup index.
Host/Environment (please complete the following information):

OS: Linux (discovered in Aiven hosted version but behaviour reproduced locally with docker image)
Version 2.8.0

Additional context
We've got some metrics that we have posted to daily indexes. We have an ISM policy applied to the daily index pattern that after three days, performs a rollup to an annual index and deletes the source index. When trying to create visualisations based upon the rollup index we're getting strange results. When hand crafting a search against the rollup index I'm able to see that all the expected data is there, but when placing the equivalent query via a visualisation on a dashboard we're missing data. The difference between my hand-crafted search and the search from the dashboard is the presence of the query field that narrows down the time-frame and optionally drills down on other facets (not included in code example above). How do we get our visualisations to show all the data, or have I stubled upon a genuine bug here?

I ran into the same problem. It looks like it only returns the result from the last rollup index (Not just date_histogram but others as well)
Same as when I create a visualization, data only show for the last rollup index.

Is there any update on this? I'm having the same problem!

Hi @sharebear and @msfroh,
I've identified the cause of the reported behavior and believe this issue can now be closed.
The behavior is related to the code snippet found here:
https://github.com/opensearch-project/index-management/blob/d4ee795e22f4490b78662f171f62d566a81c1abc/src/main/kotlin/org/opensearch/indexmanagement/rollup/interceptor/RollupInterceptor.kt#L347
This code references the setting "plugins.rollup.search.search_all_jobs", documented here:
https://opensearch.org/docs/2.4/im-plugin/index-rollups/settings/
To modify the current behavior, you can update your cluster configuration using the following API call:
PUT https://localhost:9200/_cluster/settings
Content-Type: application/json

{
  "persistent": {
    "plugins.rollup.search.search_all_jobs": true
  },
  "transient": {
    "plugins.rollup.search.search_all_jobs": true
  }
}

This update will enable searching across all rollup jobs, both persistently and transiently.
Please don't hesitate to let me know if you have any questions or need any more help.

Thanks, I've confirmed that the setting does seem to resolve my issue in local testing, just need to work out how to get that set in my Aiven hosted instance (not your problem)

authors: DucQuach KagariSan sharebear

repo: opensearch-project/index-management


text:
Use published daily snapshot dependencies

Signed-off-by: Vijayan Balasubramanian balasvij@amazon.com
Description
Fetch dependencies from published locations in the following order
maven local, aws sonatype, central.
Issues Resolved
#106
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #119 (f2899b9) into main (21af40c) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #119      +/-   ##
============================================
- Coverage     83.14%   83.08%   -0.06%
+ Complexity      480      479       -1
============================================
  Files            69       69
  Lines          1821     1821
  Branches        178      178
============================================
- Hits           1514     1513       -1
- Misses          247      248       +1
  Partials         60       60

Impacted Files
Coverage Δ

.../java/org/opensearch/knn/index/util/KNNEngine.java
89.47% <0.00%> (-5.27%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: VijayanB codecov-commenter

repo: opensearch-project/k-NN


text:
[BUG] Cypress test cleanup deleting same config multiple times

What is the bug?
The Cypress tests were refactored in https://github.com/opensearch-project/notifications/pull/442 and the tests were updated to clear existing configs in the before() hook. For some reason, the cleanup being done in "Test channel details" is fairly consistently trying to delete the same config multiple times causing 404s.
This could be some strange behavior from the last test in the spec file since the other tests don't have this problem. The before() hook for the problematic tests has been commented out for the time being while the root cause is found and can be added back in at that time.
A few things that were observed:

Tested adding a baseUrl since this Cypress issue mentioned that cy.visit() could cause the before() hook to be invoked twice, this didn't make a difference so is likely unrelated here
Tried to log within the deleteAllConfigs command and sometimes the same config is logged twice implying it's executing a single loop twice, however, sometimes the log only appears once but the request is made twice

@amsiglan @sbcd90 could you transfer this issue to https://github.com/opensearch-project/dashboards-notifications/issues
Will need to investigate whether this is still an issue.

authors: AWSHurneyt qreshi

repo: opensearch-project/notifications