Vulnerability roundup 111: mysql-8.0.26: 72 advisories [7.1]

search, files

[ ] CVE-2022-21278 CVSSv3=7.1 (nixos-21.11)
[ ] CVE-2022-21351 CVSSv3=7.1 (nixos-21.11)
[ ] CVE-2022-21363 CVSSv3=6.6 (nixos-21.11)
[ ] CVE-2022-21358 CVSSv3=6.5 (nixos-21.11)
[ ] CVE-2022-21279 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21280 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21284 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21285 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21286 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21287 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21288 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21289 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21290 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21307 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21308 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21309 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21310 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21314 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21315 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21316 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21318 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21320 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21322 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21326 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21327 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21328 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21329 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21330 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21332 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21334 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21335 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21336 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21337 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21356 CVSSv3=6.3 (nixos-21.11)
[ ] CVE-2022-21352 CVSSv3=5.9 (nixos-21.11)
[ ] CVE-2022-21301 CVSSv3=5.5 (nixos-21.11)
[ ] CVE-2022-21367 CVSSv3=5.5 (nixos-21.11)
[ ] CVE-2022-21378 CVSSv3=5.5 (nixos-21.11)
[ ] CVE-2022-21254 CVSSv3=5.3 (nixos-21.11)
[ ] CVE-2022-21302 CVSSv3=5.3 (nixos-21.11)
[ ] CVE-2022-21253 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21256 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21264 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21270 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21297 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21303 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21304 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21339 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21342 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21344 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21348 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21362 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21370 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21374 CVSSv3=4.9 (nixos-21.11)
[ ] CVE-2022-21368 CVSSv3=4.7 (nixos-21.11)
[ ] CVE-2022-21245 CVSSv3=4.3 (nixos-21.11)
[ ] CVE-2022-21265 CVSSv3=3.8 (nixos-21.11)
[ ] CVE-2022-21311 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21312 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21313 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21317 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21319 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21321 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21323 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21324 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21325 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21331 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21333 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21355 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21357 CVSSv3=2.9 (nixos-21.11)
[ ] CVE-2022-21249 CVSSv3=2.7 (nixos-21.11)
[ ] CVE-2022-21372 CVSSv3=2.7 (nixos-21.11)

CVE details
CVE-2022-21278
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).
CVE-2022-21351
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).
CVE-2022-21363
Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H).
CVE-2022-21358
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Encryption). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21279
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21280
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21284
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21285
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21286
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21287
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21288
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21289
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21290
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21307
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21308
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21309
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21310
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21314
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21315
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21316
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21318
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21320
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21322
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21326
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21327
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21328
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21329
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21330
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21332
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21334
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21335
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21336
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21337
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21356
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).
CVE-2022-21352
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.26 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.9 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H).
CVE-2022-21301
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
CVE-2022-21367
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Compiling). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
CVE-2022-21378
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
CVE-2022-21254
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21302
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21253
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21256
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Group Replication Plugin). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21264
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21270
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Federated). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21297
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21303
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Stored Procedure). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21304
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Parser). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21339
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21342
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21344
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21348
Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21362
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Information Schema). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21370
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21374
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Information Schema). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2022-21368
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Components Services). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data as well as unauthorized read access to a subset of MySQL Server accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 4.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L).
CVE-2022-21245
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 4.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).
CVE-2022-21265
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 3.8 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L).
CVE-2022-21311
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21312
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21313
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21317
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21319
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21321
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21323
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21324
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21325
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21331
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21333
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21355
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21357
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Cluster accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Cluster. CVSS 3.1 Base Score 2.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:L).
CVE-2022-21249
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 2.7 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L).
CVE-2022-21372
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Encryption). Supported versions that are affected are 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 2.7 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L).

Scanned versions: nixos-21.11: 2128d0aa28e.
Cc @orivej

See also: #147892

Fixed:

nixos-21.11: mysql-5.7.37, mysql-8.0.28


[Question]: How to insert data into specific database for Milvus?

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I use llamaindex to connect the Milvus, and I specify the Milvus db-name as "New_DBName". But when insert data, I found all the data is inserted into 'default' database. Following is my connect code:
vector_store = MilvusVectorStore(dim=384, db_name="New_DBName", overwrite=True)
Env:
python 3.9
llamaindex 0.9.48

It appears there's a mix-up with the parameter used to specify the database or collection name in your code. In the version of LlamaIndex you're using, the MilvusVectorStore class expects a collection_name parameter for defining where the data should be stored, not db_name. Here's how you can adjust your code to ensure data is inserted into the correct collection:
from llama_index.legacy.vector_stores.milvus import MilvusVectorStore

vector_store = MilvusVectorStore(
    dim=384,
    collection_name="New_DBName",  # Use collection_name instead of db_name
    overwrite=True
    # Include other necessary parameters like URI and token if needed
)

By specifying collection_name="New_DBName", your data will be inserted into the "New_DBName" collection. Ensure that any other required parameters, such as the Milvus instance URI and token (if using RBAC), are also correctly set in your MilvusVectorStore initialization.
This adjustment should direct your insert operations to the intended collection. If you encounter further issues or have additional questions, feel free to ask.
Sources

llama-index-legacy/llama_index/legacy/vector_stores/milvus.py

About Dosu

not solve my problem.
Milvus support user to manage different database (note: not the collection),  you can pass in the db_name to connect different database using pymilvus. So I want to know, how can I access different database using llamaindex, so that I can insert different data into different database.

@momocat-aric db_name is not a valid kwarg to milvus vector store. It seems like it might get passed in as part of kwargs, but I wouldn't be surprised if this wasn't supported properly
Feel free to checkout the source code
https://github.com/run-llama/llama_index/blob/ce5963486d8b99fa045659dbdb7bd1398d6b7da5/llama-index-integrations/vector_stores/llama-index-vector-stores-milvus/llama_index/vector_stores/milvus/base.py#L173

@momocat-aric db_name is not a valid kwarg to milvus vector store. It seems like it might get passed in as part of kwargs, but I wouldn't be surprised if this wasn't supported properly
Feel free to checkout the source code
https://github.com/run-llama/llama_index/blob/ce5963486d8b99fa045659dbdb7bd1398d6b7da5/llama-index-integrations/vector_stores/llama-index-vector-stores-milvus/llama_index/vector_stores/milvus/base.py#L173

Thanks for your reply.
Yes, I debugged the code and found the db_name actually can be passed into MilvusClient class. But it still not work, that is weird.
And I tried another way:  use "/" to concat the URI and db_name,  it works, like:
URI = "<URI>/<DB_NAME>"
vector_store = MilvusVectorStore(dim=N, uri=URI, overwrite=True)


react. Allow any property on HTMLAttributes.

This is necessary for data-attributes  (e.g data-*) support with Typescirpt >= 1.6.0

umm...
@pspeter3 @vsiao @jbrantly could you review this PR?

The problem with this is that you then lose any typing for actual HTML attributes (like if you make a typo). I think if you need to support custom data-* attributes you should just extend the interface in your own custom definition file.

To clarify: I mean use module & interface merging. We do this today at AssureSign. We have a definition file called react-custom.d.ts which (currently) looks like:
declare namespace __React {
    interface HTMLAttributes {
        class?: string;
    }

    interface CSSProperties {
        margin?: string | number;
        maxWidth?: string;
    }
}

You can use this method to easily either fix issues until the repo is updated or add custom stuff like your own data attributes. In our case we've added a class attribute since we use a class => className preprocessor.

I agree with @jbrantly

@jbrantly ok, sounds reasonable


Do not set db if no client.

Already found a bug. Because we are using callbacks if the connect fails then client is undefined. If client is undefined then client.db is also undefined. This results in getting an object undefined error instead of the connection error you would expect. So we check if client exists before calling on client.db then if there is no client we pass the connection error to the callback.

Codecov Report

Merging #41 into master will increase coverage by 0.24%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
+ Coverage   52.20%   52.45%   +0.24%
==========================================
  Files           4        4
  Lines         385      387       +2
==========================================
+ Hits          201      203       +2
  Misses        184      184

Impacted Files
Coverage Δ

lib/index.js
47.57% <100.00%> (+0.30%)
:arrow_up:

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 211284e...1a135a4. Read the comment docs.

Is that useNewUrlParser change just a patch change too?  Does it need a changelog entry?


Design issue

Design in disturbed slightly due to base.css in admin folder. But I am not able to find that location

Django has it's own base.css, locate at: https://github.com/django/django/tree/master/django/contrib/admin/static/admin/css
I'm overriding the Django Admin's base.css, so we have one at:
https://github.com/django-admin-bootstrap/django-admin-bootstrap/blob/master/bootstrap_admin/static/admin/css/base.css
You will find both of them in your virtualenv folder, if you are using virtualenv.
If your problem it's with overriding templates / static files of existing packages, you may find useful:
https://docs.djangoproject.com/en/1.10/ref/contrib/admin/#admin-overriding-templates
Don't know if I did answer your question, so let me know. =]

Closing for now, reopen if this persists.


Relative paths in remote datapackages don't work

Overview
const Datapackage = require('datapackage-test').Datapackage
const descriptor = 'https://raw.githubusercontent.com/frictionlessdata/datapackage-js/master/data/dp1/datapackage.json'

new Datapackage(descriptor).then(dp => {
    dp.resources[0].table.then(table => console.log(table.read()))
})

Error: ENOENT: no such file or directory, open 'data.csv'

Tasks

[ ] fix broken behavior
[ ] add tests

@roll any update on a fix here (or confirmation this is a bug)? I'd like to use this feature in DPR if we can ...

@rufuspollock
It's confirmed - we're starting to work on it.

@roll
this should be fixed in jsontableschema-js, because we're just wrapping the Table class here. Basically when doing table.read() you are using only jsontableschema-js code.
Therefore, the estimate is for jsontableschema-js.

I suppose error could be in code where we pass path to jsontableschema.Table


Hello! Could you please provide the revised paper code?

Hello! Could you please provide the revised paper code?

Hi, just wondering what do you mean by "revised paper code"? The current GitHub code is already the latest version. Thanks.

Hello dear author! The Salience Augmented Memory Completion for Continuous Learning article method dataset you previously published only provides CIFAR-100. You mentioned in REDED that other datasets will be published later. Can you provide me with data from other datasets in the article so that I can replicate the experiment. Thank you!


Convert effects/dust to typescript

I'm struggling with the type for the wheels. I know CannonApi is not right for them, but I don't know what it's supposed to be.

You can use extends mesh to also get the mesh properties as that's after all a mesh. https://github.com/pmndrs/racing-game/pull/130/files#diff-2717c7fb31c2070dd96f07394997809bc9be7f3fff03ab638db696cc480f39b6R80


exoscale: bump version to 0.11

we fixed one or two things in the dns section.

Oh, sorry I could have performed a rebase.

Thanks for your PR! 👍


Add Mormon Pioneer and Pony Express National Historic Trail Auto Tour Route shields

These are just plain shield since we don't have permission to use NHT shields yet, but the routes are mapped.
Re: #1101

A note of caution, some of these NHT are collinear with long stretches of interstates and US routes, so the shields may show up at relatively low zooms. This is z6 in Utah with this PR. The orange blob looks kind of weird considering there is no graphic.


Video/Audio is not available

Hi,
I am using rtsp player for including rtsp streams in html5 video tag. The stream plays well in VLC but in the rtsp player, I am able to listen to only audio and the video is not being rendered. I get the below statement in the console.
"no video for this : video track is not attached cause there is no remuxer for MP4V-ES"
RTSP URL:
rtsp://mm2.pcslab.com/mm/7m800.mp4
Also, there seems to be some problem when rendering audio in this rtsp stream.
rtsp://freja.hiof.no:1935/rtplive/definst/hessdalen03.stream -
audio track is not attached cause there is no remuxer for mpeg4-generic

It seems the support for some formats is currently unavailable. Please correct me if I am wrong.
If the problem is supporting the formats, any rough timeline of when the support for these formats would be available?
Also, the server doesn't get installed in Ubuntu14.04. Can you suggest any workaround for this without having to upgrade the OS to 16.04?

Many Thanks,
Praneeth

This player can only handle 'H264' for video and MP4A-LATM for audio, as you can find in remuxer.js

Can you help me to convert audio file into file mp4a-latm format in rtp? thank you very much.

I would say have a look at ffmpeg. It has all the tools necessary to make
a compatible stream.
ᐧ
On Sat, Dec 17, 2016 at 11:41 AM, tungct1201<EMAIL_ADDRESS>wrote:

Can you help me to convert audio file into file mp4a-latm format in rtp?
thank you very much.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SpecForge/html5_rtsp_player/issues/25#issuecomment-267740575,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8UwDfg4RbddNT4kn1nijUZ0Joik8GLks5rI1nZgaJpZM4LKWUN
.

--
Find my profile on LinkedIn:
http://uk.linkedin.com/in/victordmdb

I tried to rebuild the player to run a standard audio mpeg4-generic and video h264 as the following demo
http://specforge.com/html5playerstream/index.html.
Data payload was successful with mpeg4-generic but there was no sound. Can you help me to solve this problem?
Thank you very much!

The demo you're pointing to is still using an MP4A-LATM audio stream. How
did you "rebuild the player to run a standard audio mpeg4-generic"? You
would need to write a javascript parser for the mpeg4-generic stream.
Have a look at
https://github.com/SpecForge/html5_rtsp_player/blob/master/src/remuxer/aac.js
and modify this to read the stream.
ᐧ
On Wed, Dec 21, 2016 at 12:56 AM, tungct1201<EMAIL_ADDRESS>wrote:

I tried to rebuild the player to run a standard audio mpeg4-generic and
video h264 as the following demo
http://specforge.com/html5playerstream/index.html.
Data payload was successful with mpeg4-generic but there was no sound. Can
you help me to solve this problem?
Thank you very much!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/SpecForge/html5_rtsp_player/issues/25#issuecomment-268296514,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA8UwEjHmvJamej7BpmLn7oEfmYKdXMGks5rKAjTgaJpZM4LKWUN
.

--
Find my profile on LinkedIn:
http://uk.linkedin.com/in/victordmdb

Thank you so much for your help. I fixed and it works perfectly. I have another question that needs your help. I want to install a public proxy running on my server on port 80 as the following demo http://specforge.com/html5playerstream/index.html which uses wss://specforge.com/ws. Is it possible if I use ws-rtsp-repo_1.3_all.deb? Look forward to your reply. Thanks in advance!

Could you please explain to me how to install a public proxy? thank you very much

you can download package from http://streamedian.com/
Deb/RPM repositories are temporary disabled


spin component modules out into separate repos?

Pull the following out into separate GitHub repos?

resolvers (or maybe just Webpack resolver)
utils folder (eslint-module-utils)

pros:

separate Travis builds, coveralls coverage, etc.
separate issue tracking for each
more consistent with community resolvers
changelog can actually show commit diff for just a resolver
decoupling resolver versions from core plugin

cons:

separate repos (commit history no longer related)
confusion about where issues should be reported

@jfmengels, curious what you think of this. Current setup (one repo, many npm packages) was inspired by Babel, but it feels like more work than it's worth for ~4 packages that ideally should be somewhat loosely-coupled. I think in Babel's case, it's more warranted.

@jfmengels: bump. 😄
I'm thinking this is a bad idea, but I'm still curious what your perspective is.

Totally missed this issue.
I think it's better to have it all here, except if it's a lot of trouble to manage for you.
Btw, "separate issue tracking for each" is not right IMO, as people will pretty much always file issues/complain here anyway. The "confusion about where issues should be reported" will probably be much bigger than you think. It's probably more accurate to think that people will simply put it in the wrong repo than for them to be confused.

Yeah, makes sense, thanks for the feedback.


proxy_url available for relabelling

What did you do?
Try to use relabelling to populate the target parameter "proxy_url"
But it cant be done, you cant override it via relabelling, there is no possibility to do so.
Can you make it append ?
What did you expect to see?
The "proxy_url" populate from value from consul tag "proxy"
What did you see instead? Under which circumstances?
nothing
Environment

System information:

Linux 3.10.0-693.11.1.el7.x86_64 x86_64

Prometheus version:
2.1.0

Prometheus configuration file:

relabel_configs:
  - source_labels: ['__meta_consul_tags']
      regex: '.*;proxy=([^;]*).*'
      target_label: '__proxy_url'

Logs:

nothing

This is not possible, you should have at most one proxy that you are using. If you need this you will need to get your configuration management's templating functionality to generate the config file.


Meld GTK icons missing

Describe the bug
Meld can't find any GTK icons, and doesn't render text.
To Reproduce
Install meld under 20.09. Open two directories under meld (i.e. meld dir1/ dir2/)
Expected behavior
Useful directory diffs etc.
Screenshots

Additional context
This is installed from most recent 20.09, via home-manager.
The console meld was run from produces error logs like:
Traceback (most recent call last):
  File "/nix/store/q1fgpmgk5yvqzyl0llfxk8qc3qrgdb8p-meld-3.21.0/lib/python3.8/site-packages/meld/ui/emblemcellrenderer.py", line 76, in do_render
    pixbuf = self._get_pixbuf(self.icon_name, self._icon_size)
  File "/nix/store/q1fgpmgk5yvqzyl0llfxk8qc3qrgdb8p-meld-3.21.0/lib/python3.8/site-packages/meld/ui/emblemcellrenderer.py", line 64, in _get_pixbuf
    pixbuf = icon_theme.load_icon(name, size, 0).copy()
gi.repository.GLib.Error: gtk-icon-theme-error-quark: Icon 'folder' not present in theme hicolor (0)
cairo.Error: Context.restore() without matching Context.save()
cairo.Error: Context.restore() without matching Context.save()
cairo.Error: Context.restore() without matching Context.save()
cairo.Error: Context.restore() without matching Context.save()

entries are triggered as the mouse moves over the meld window
Notify maintainers
@jtojnar @mimame
Metadata

system: "x86_64-linux"
host os: Linux 5.4.97, NixOS, 20.09.3124.2118cf551b9 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(root): "home-manager-20.09, nixos-20.09.3732.91b77fe6942, nixpkgs-20.09.3732.91b77fe6942"
channels(judson): "home-manager-20.09, nixpkgs-20.09.3732.91b77fe6942"
nixpkgs: /home/judson/.nix-defexpr/channels/nixpkgs

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

This should be fixed by https://github.com/NixOS/nixpkgs/commit/f02fc10d0dd79559de62e265da091d58f251a030, if someone wants it in 20.09, they will need to backport it.

I thought this had been pulled into unstable, but https://github.com/nixos/nixpkgs-channels/archive/4762fba469e2baa82f983b262e2c06ac2fdaae67.tar.gz doesn't appear to have it (unstable as of 3/3/21)
If I need to bring it in by copying, that's fine. A backport seems warranted, since it's effectively broken there.


Add normalization post augmentation

As the title says :-)

One initial comment: I think the norm op should maybe be before the copy_image_to_seg call


tests: Add InvalidBarriers layer validation test

Add a test checking for 8 ways to get INVALID_BARRIER.  Tested on 16.04 Mesa and Win 7 Nvidia

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

LGTM :+1:
There were two subcases within the test that weren't commented so would be nice to see comments for those cases as well.

Added comments and pushed to master


[Fix] Package schema and request errors

Description
[Depends on PR #602 #654 #656]
This PR has been extracted from #628  (a lot of the relevant discussion still lives there)
Package version schema and request errors
Breakdown

fix schema issue with packages including dashes for example importlib_metadata->=0.5

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Test Configuration:

Python version: 2.7.15, 2.7.16
OS: Linux, Windows 10
Toolchain: rez 2.33, pip 18.1, 19.1.1, distlib 0.2.9.post0

Todos

[ ] Tests

I'm a little lost on this one - I've gone over the conversation history on https://github.com/nerdvegas/rez/pull/628 but I can't see how these changes relate.
Also might be good to re-merge with master now that #602 is merged, there are loads of diffs here that no longer apply and it's quite difficult to see which changes are specific to this PR.
Thx!
A

Re-merged as required!

Worth looking into I think.
Related to this - if we are to obey pip package requirements to the letter,
that means taking markers into account (such as in this example). However,
that also implies that the rez package must require/be varianted on at
least major.minor of the python version. It's possible to have a
requirement like "configparser>=3.5; python_version < '3'" in pip, because
the current python version is known ahead of time. Such requirement logic
isn't possible in rez however, because python is just another package. So
if a package has markers, the only way to satisfy the related requirements
is to have those requirements specified alongside the python version range
that requires them.
Here's where it gets tricky: what if you had a marker like so:
pathlib2; python_version=='3.4.1'

Now we're in trouble. The only way to express this requirement in rez would
be to have a variant on python-3.4.1, and that's getting a bit odd.
Furthermore, you might also have several markers, whose overlapped python
version requirements would cause even stranger varianting on python.
I'm not sure what the best solution is. It seems to me atm that the
considerable extra complexity needed to exactly define markered
requirements (ie, varianting the package on python in such a way that the
requirements are correct, but python version is never overspecified) is
more trouble than it's worth. If we just varianted on python-major.minor,
yes that would be overly specific for many cases, but it would also avoid
this problem.
On Thu, Jul 11, 2019 at 1:20 PM Ira<EMAIL_ADDRESS>wrote:

@lambdaclan commented on this pull request.
In src/rez/package_maker__.py
https://github.com/nerdvegas/rez/pull/658#discussion_r302349814:

@@ -128,6 +128,10 @@ def get_package(self):
def _get_data(self):
data = self._data.copy()

   if "requires" in data:

Looking at the importlib-metadata setup.cfg
https://gitlab.com/python-devs/importlib_metadata/blob/master/setup.cfg
file I can see the install requires being as follows:
install_requires =
zipp>=0.5
pathlib2; python_version=='3.4.*' or python_version < '3'
contextlib2; python_version < '3'
configparser>=3.5; python_version < '3'
Now looking at the requires above:
'requires': [u'zipp->=0.5', None, u'configparser->=3.5', None]
It seems to be missing two of its dependencies? pathlib2 and contextlib2
should have been included.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/pull/658?email_source=notifications&email_token=AAMOUSVGPDJR32R4YZEDK63P62RIFA5CNFSM4H6XI7SKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB6DC3XI#discussion_r302349814,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMOUSTVKGYFAE2CA47VZB3P62RIFANCNFSM4H6XI7SA
.

I'm pretty confident that #667 addresses this, so will close this PR when that is merged.

Closing now, I'm certain that #667 fixes the issue, cheers


Strange behaviour when dettaching children element

How to reproduce: drop an element, then drop another element as a child, then a third one as child of the second one, now we hace three connected elements.
Now dettach the second element from the first one by moving it away from the parent. The 2nd and 3rd elements disappear when you release the mouse button. This seemed a bit strange to me, I was expecting those two elements to remain connected and on screen, just independent from the first element.
But the real problem is that form this point on you can't drop another element. You can drag it to the canvas, but upon releasing the mouse button the element stays "glued" to the cursor.
Here's a video of this behaviour

Just fixed it - was a small issue with the blue indicator block getting accidentally deleted and thus triggering a javascript error.
As per the blocks getting removed, I've currently kept it that way for simplicity, with only one tree, although if there's a lot of interest I could allow for multiple trees. Shouldn't be hard to implement, but it would lead to having blocks that overlap, making it harder to snap new blocks or to rearrange them.

Thanks a lot for the quick fix!

As per the blocks getting removed, I've currently kept it that way for simplicity

When a block is detached from all blocks, is it possible to snap it back to the previous parent instead of removing it ?
Because when I click on the header (or on the 3 dots in the block header), my mouse often move just a little bit, and the block is suddenly removed.
Or maybe add a threshold distance value above which the block is removed ?


School aliases in extract

I have had a go but still failing so need another try tomorrow! Is this kinda on the right track?
I am not 100% sure how to set the self._school_alias 🤔

@stefpiatek thanks for the help - sorry final re-review! all checks have passed yay! i just changed one of the tests test_read_redcap_extract_rows_and_cols


Meaning of variables

Hey, thanks for this lib. I want to understand a little bit how it works, but the calculus that you do is not clear.
Can you provide a little clarification on the meaning of that part of the code? For example on the creation of this variables
    private int p = 14;
    private int s = 2;
    private int pm = 10;
    private int sm = 2;

Also can you extend on the why of the calculus for the width?
Thanks in advance.

Hey mate.
So p is basically the padding around the text (top, bottom, left and right).
s is the side space of the text. So it just adds to the padding p in same scale but only on the sides (left and right).
pm, sm are the same but for the meta texts.
About the width calculations. I assume you mean this line.
int w = textW + p * 2 + s * 2;
int h = textH + p * 2;

So we want to know the width of the rectangle we want to draw later. Thus we take the width of the text and add the padding times two (for left and right). Also we add the sidespace variable times two since this is an addition to the padding (only left and right).
For the height we do the same with the height of the text and this time only the padding since we don't want additional space on the top or the bottom.
Hope that answers your questions otherwise just ask again.

Hey,
Thanks for the clarification was really helpful.


Add a Gitter chat badge to README.md

geopython/pywps now has a Chat Room on Gitter
@jorgejesus has just created a chat room. You can visit it here: https://gitter.im/geopython/pywps.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Coverage remained the same at 75.818% when pulling f2585ad8f75bf58a379b7c3e2a7df5fa3eb9335e on gitter-badger:gitter-badge into e7fc27fbf01b7fbd6cfb1f05c3b1e8d043cd939e on geopython:master.

Coverage remained the same at 75.818% when pulling f2585ad8f75bf58a379b7c3e2a7df5fa3eb9335e on gitter-badger:gitter-badge into e7fc27fbf01b7fbd6cfb1f05c3b1e8d043cd939e on geopython:master.


Dying makes u get an error and screen goes brrrrrrrrrrrrrrrrr

Describe your bug here.
Basically when i pressed "R", the game instead of showing the deathscreen, it show this error:

I tried by missing the notes but, the error appeared again.
After u get the error, the game crashes, even the error appears in the non-builded psych engine.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
I left it how it was (it means no)

Happens when your death screen character is missing animations

i got all of them, the three of them

what's the character, if it's bf his death animations are stored separately

no it was by the caps, am so dumb

this can be closed then?

this can be closed then?

This is a rare phenomenon where they're so excited to go get they're thing to work that they forget to close the thing...

@WilliamGaming12 close this.


Yarja Laravel-DataTables with Acacha Adminlte-laravel

Basically, how do we make yajra/laravel-datatables work with acacha/adminlte-laravel?
where do I place the  and {!! $dataTable->scripts() !!}.
When I place these scripts in resources/views/vendor/adminlte/layouts/partials/scripts.blade.php I get following error
users:389 Uncaught TypeError: $(...).DataTable is not a function
I need to place these scripts after adminlte loads datatables plugin.
Any help appreciated.
I am using Laravel 5.5

Hey,
I'm not an expert in adminlte template and I don't know anything about Yarja so maybe it's better you use adminlte forums of github or stackoverflow to ask questions:
https://stackoverflow.com/questions/tagged/adminlte


Change default value of pinot.set.instance.id.to.hostname to true.

By default, the instance names chosen is the IP address of the node (host + port). However, with cloud deployments becoming more mainstream using hostname is more desirable. This PR changes the default behavior to use hostname instead of IP address.
Although, most deployments should not be impacted by this change, still marking this as backward incompatible to err on the side of being cautious.
Release Notes
The default behavior of pinot.set.instance.id.to.hostname is being changed from false to true. With this change, the hostname would be used for pinot component instance names as opposed to the host IP address by default. The behavior can be reverted by setting this config to false.

Codecov Report
Attention: Patch coverage is 12.50000% with 7 lines in your changes missing coverage. Please review.

Project coverage is 61.98%. Comparing base (59551e4) to head (aaf9aab).
Report is 715 commits behind head on master.

Files
Patch %
Lines

.../main/java/org/apache/pinot/minion/MinionConf.java
0.00%
3 Missing :warning:

.../pinot/server/starter/helix/BaseServerStarter.java
0.00%
2 Missing :warning:

...e/pinot/broker/broker/helix/BaseBrokerStarter.java
50.00%
0 Missing and 1 partial :warning:

...apache/pinot/controller/BaseControllerStarter.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #13536      +/-   ##
============================================
+ Coverage     61.75%   61.98%   +0.23%
+ Complexity      207      198       -9
============================================
  Files          2436     2557     +121
  Lines        133233   140888    +7655
  Branches      20636    21855    +1219
============================================
+ Hits          82274    87336    +5062
- Misses        44911    46924    +2013
- Partials       6048     6628     +580

Flag
Coverage Δ

custom-integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration1
<0.01% <0.00%> (-0.01%)
:arrow_down:

integration2
?

java-11
<0.01% <0.00%> (-61.71%)
:arrow_down:

java-21
61.99% <12.50%> (+0.36%)
:arrow_up:

skip-bytebuffers-false
35.23% <0.00%> (-26.52%)
:arrow_down:

skip-bytebuffers-true
61.96% <12.50%> (+34.24%)
:arrow_up:

temurin
61.98% <12.50%> (+0.23%)
:arrow_up:

unittests
61.98% <12.50%> (+0.23%)
:arrow_up:

unittests1
46.52% <ø> (-0.37%)
:arrow_down:

unittests2
27.66% <12.50%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Seems like the backward incompatibility test won't pass with this change. Closing the PR for now.


Pypsa importer for scenario objects

Purpose
This PR builds on top of of PR #600. It is still in draft mode following the idea to allow "early" feedback on the overall design.
What the code is doing
The code changes allow to create a Scenario object from arbitrary PyPSA networks.
The conversion is starting from the set_grid function of the Scenario class. This function was extended by supporting a pypsa Network as grid_model argument.
For the conversion, a _PypsaBuilder, mimicking the behavior of the powersimdata.scenario.create._Builder was created. It can be found in the import_data.py.
One major difficulty is given by the functionality of get_bus_demand. Since PyPSA defines demand time series per bus (not per zone), the distribution of the demand time series to buses after the import is ambiguous. At the moment, the get_demand function of a Scenario built from PyPSA, already returns demand time series per bus. The get_demand_per_bus raises an errors due to the unsuccessful distribution to buses.
Testing
from powersimdata import Scenario
from powersimdata.input.export_data import export_to_pypsa
from pandas.testing import assert_frame_equal

ref = Scenario()
ref.set_grid(grid_model="usa_tamu", interconnect='Texas')
ref.set_name("test", "dummy")
ref.set_time("2016-08-01 00:00:00", "2016-08-31 23:00:00", "24H")
ref.set_base_profile("demand", "vJan2021")
ref.set_base_profile("hydro", "vJan2021")
ref.set_base_profile("solar", "vJan2021")
ref.set_base_profile("wind", "vJan2021")

kwargs = dict(add_substations=True, add_load_shedding=False, add_all_columns=True)
n = export_to_pypsa(ref, **kwargs)

test = Scenario()
test.set_grid(grid_model=n)

assert_frame_equal(test.get_hydro(), ref.get_hydro())
assert_frame_equal(test.get_solar(), ref.get_solar())
assert_frame_equal(test.get_wind(), ref.get_wind())
assert_frame_equal(test.get_demand(), ref.get_bus_demand())

This code should work without assertion errors.

What files are most important?
import_data.py
create.py

Time estimate
~20 min

@BainanXia if already tested, now, the test script should also run.

The get_demand_per_bus raises an errors due to the unsuccessful distribution to buses.

I'm a little confused here. If from PyPSA we have a demand profile for each bus, then when we convert to a Scenario, can we just create a zone for every bus, which contains only that bus? Then calling Scenario.get_demand() should return the zone demand, and calling Scenario.get_bus_demand should return the bus demand, which should be identical because we translate one to one from zones to buses.

I'm seeing some interesting behavior when taking a Scenario that's already been run (i.e. it's in Analyze state), converting it to a Network, and then converting it back to a Scenario. First of all, calling Scenario(network) prints a whole lot of information that seems to relate to building a connection to Azure.  Thanks.

Thanks @danielolsen for the comments, I addressed them and resolved the comments, please reopen if you still think there is something missing.

One way we could keep imports at the top level is moving the AnalyzePypsa class to the powersimdata.scenario subpackage. That's also where the Analyze class is, but I think it also avoids any dependency on that package from within powersimdata.input. Since we have a bunch of imports in the other direction, that should prevent circular imports.
I tested that out in this commit.

@jon-hagg thanks for looking at it. You are right about considering the module hierarchy. The benefit of the current implementation is that all code, that is related to other packages, is in the import_data.py and there is the structure to include other imports as well (thinking about the switch wrapper and possible others). But from a hierarchical point of view, your change makes more sense. Should we pull it in this PR, so I can test every thing again?


Don't hard-code -Werror.

Not sure if I am missing something here but use of -Werror is hard-coded into the Makefile.am as well as being an opt-in configure-switch, is that deliberate?

I agree with you. This should not be in there.


Missing Sigmoid when calculating BCE loss / Activation function during inference

Hi JongWook,
Thank you for your implementation.
I have 2 questions regarding your implementation.

Based on the documentation, a sigmoid activation function needs to be applied to the logits before calculating the BCE loss. However, in transcriber.py, a sigmoid activation is not applied before activation. May I know whether this is an error?

During inference in evaluate.py, I noticed that a relu activation is applied in the function evaluate(). Instead of relu, shouldn't sigmoid be used here?

Best,
Nicolas

Finished my investigation: 1. The Sigmoid activation is embedded within the conv stacks. It's correct to use BCE loss. 2. The Relu activation in evaluate() would not make a difference since value.squeeze_(0).relu_() would not change the pred[key] in the dictionary anyway. Although it's a bit confusing..


Alternative to countTrailingZeros for bitmap iteration

unionArrayBy and intersectionArrayBy currently use countTrailingZeros to detect set bits in bitmaps.
Alternatively, lowest set bits can be isolated like this:
isolateLowestSetBit :: Word -> Word
isolateLowestSetBit x = x .&. negate x

(Explanation in https://stackoverflow.com/a/12250963/1013393)
The latter technique is already being used in submapBitmapIndexed to create the initial bit mask.
It would be good to consistently use only one technique, ideally by refactoring this pattern into a proper function like isolateLowestSetBit.

clearLowestSetBit x = x .&. (x - 1) might be useful to simplify clearing the lowest set bit for the next iteration.


cfstore flash-journal integration with config_system

Changes so the flash mode can be selected with config system property.

Why do you remove "LOWPOWERTIMER" in several targets?

@ohagendorf which targets?
I'll rebase again to see if this changes.

Just have a look here under "Files changed": several Nucleo targets.

rebase done

Rebase changes to fork didn't automatically update this PR, so closing this PR and will resubmit.


CLI: Add the union-default-graph option to make SPARQL queries use the union of all graphs as the default graph

Issue #973

Wonderful. How is the CLI configured then? An environment variable?
Sorry for the basic question.

Just set the --union-default-graph option when starting Oxigraph server

Is this intended?
2024-08-26 00:21:15 error: unrecognized subcommand 'serve-secondary'
2024-08-26 00:21:15
2024-08-26 00:21:15   tip: some similar subcommands exist: 'serve', 'serve-read-only'
2024-08-26 00:21:15
2024-08-26 00:21:15 Usage: oxigraph <COMMAND>
2024-08-26 00:21:15
2024-08-26 00:21:15 For more information, try '--help'.

It seems --union-default-graph is not allowed for serve-secondary. I imagine why but wanted to make sure it is intended

@ch-sander Hey! I was not aware you were using serve-secondary (or of any user of it). I dropped this command from the 0.4.0-rc.1 because of all the bugs I encountered with it and RocksDB 9. Distributions have migrated to RocksDB 9 and I did not wanted to ship a badly broken feature. Can you use easily serve or serve-read-only or do you badly need it?

What is great is that a new store is target for queries immediately, so no restart of service needed. That's the main reason, I use it. But that might also be the thing to cause trouble.
It's also used by the app I run within my service:
https://github.com/epoz/shmarql/blob/8811fddb8f7f4b104e504437564616cd2f290776/src/app/main.py#L73-L84
Maybe there's a work-around for both cases? I guess the shmarql exception handling could also just fall back to read_only @epoz ?

@ch-sander If I understand your code correctly, you are loading some data into Oxigraph when starting the script and then only do read-only access. If yes, I see two approaches:

if you only have a few triples (less than a million) I would just load the data into memory each time you start the script, maybe with a on-disk cache for the data you load from the web.
if you have more triples what you can do is that the first process open the store as read/write, load the file and then create a file with a well known name. The other processes would just wait with a sleep loop for this file to exist before opening the store as read only. Idea:

try:
    GRAPH = px.Store(STORE_PATH)
    # Do loading ....
   with open(MY_WELL_KNOWN_FILE, "wt") as fp:
       fp.write(" ") # Create the file
except OSError:
   while not os.path.exists(MY_WELL_KNOWN_FILE):
      sleep(1)
  GRAPH = px.store.read_only(STORE_PATH)

I hope it helps and that I have understood your use-case well

Thanks, but the code is @epoz 's -- my use case is much simpler: I load triples into the store with pyoxigraph (similar to shamrql) but with oxigraph server, running on its own, and having set the location to this store fed by pyoxigraph, I want to have this data ready for a query without restarting oxigraph server. You suggested the serve-secondary solution, I guess, here: https://github.com/oxigraph/oxigraph/issues/948#issuecomment-2262205513
Can the server be triggered to realod the store from location without restart and http only?

@ch-sander Thank you for the context. I missed it. Sadly a reload from location cannot be triggered without a restart (this kind of reload without secondary system would be in fact more or less a restart). If you don't have too many data, the easiest way is maybe to send the extra data to the HTTP server as RDF files or SPARQL updates.
To add graph data to the default graph: curl -X POST -H "content-type: text/turtle" http://localhost:7878/store?default
To add dataset data: curl -X POST -H "content-type: application/trig" http://localhost:7878/store
To add graph data to a named graph: curl -X POST -H "content-type: text-turtle" http://localhost:7878/store?graph=http://example.com
Add ?no_transaction&lenient if you want faster loading to disable transactional updates and most data validations.

I will have to find a way. The files are/will be c. 500mb in ttl. I think I remember /store can also load from remote. And I understand uploads via /store will work also if the server is run serve-read-only, right? Or would I need to serve and have a nginx (or other proxy) config to virtually disallow access to store?

The files are/will be c. 500mb in ttl.

It should be fine via /store. If you set the no_transaction option, parsing and loading will be streamed so memory consumption should be ok.

I think I remember /store can also load from remote.

You can indeed run SPARQL UPDATE LOAD command.

And I understand uploads via /store will work also if the server is run serve-read-only, right?

Sadly not. You need a read/write server via the serve option and a proxy.
A quick and dirty approach might be to still do the loading via pyoxigraph or something similar and restart the read-only server when needed. The restart operation should be fast (less than a second).

Thanks, will do so. The updates will occur quite regularly, the restart time is not the issue, but it safely needs to be triggered from remote via http. I need to find a good solution.
Previously the pyoxigraph was part of fastapi app behind http authentication on a VM with a store directory mounted to another VM with Oxigraph server served secondary from the mount.

Quick thought: to avoid to have two Oxigraph processes, you might write in fastapi an implementation of the [SPARQL HTTP protocol](http://www.w3.org/TR/sparql11-protocol/ to serve SPARQL queries from the same app. Implementing it only for queries should not be very hard.

It's wonderful to have you reflecting on my use case, especially as I'm a beginner.
The shmarql app (fastapi) that runs beneath my own app to ingest RDF files into the /store via http has already an oxigraph-based SPARQL endpoint. I could well integrate this as endpoint for ResearchSpace, but I thought the "actual" oxigraph server is better maintained and more stable for production. E.g., shmarql does not support the flags for union-default or graph-uri (can be done easily, I know).
But with all these options, I will find a solution that fits and this without oxigraph having a buggy feature such as serve-secondary. If you ever resurrect it, maybe send me a note (and I will check the CHANGELOG).

Thank you for the nice reply!
The SPARQL protocol is quite stable and fastapi is very well maintained and stable so I tend to think it might be as good as Oxigraph http server on the stability side.
I will ping you if I resurect serve-secondary!


README.md page redesign

Our repository https://github.com/deveshvaidyaofficial/PatternsinC.git has a mimalistic README.md page...
I invite contributions for redesign of the README.md page which describes the idea and goal of our repository.
It should also include a mention about contributing to open source and its benefits.
Looking forward to work and collaborate with all of you...

kindly assign me this issue ,I will like to work on this issue.

Multiple contributors have share created pull requests for this issue..
The code will be merged once the conflict between the code is resolved


add skeletal PPP and update AboutUs.md.

addresses #49
addresses #35

other than the picture, LGTM.

Um so i kinda messed up the git part a bit, so will be making a new PR.


Start new version; get pyright passing

Just bumps to a new (dev) version and fixes some newly reported pyright issues

Reviewed with @schloerke in person


Restore link to api manifest.yml on rack repo

This is the way is way before; pointing to the site/api/manifest.yml was a temporary measure.
Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 Move manifest.yml back to Rack repo


JFXDatePicker colors

This's a follow up for issue #484
Hello again,
Thanks for the effort for fixing the issue, but i've just noticed that the same problem happens with the (today / selected date / year) numbers when default color is white as shown below:
(Today is the 4th of nov, selected date is 3rd of nov)

Also the date icon in the new release gets this weird white/silver background color when focused which didn't use to happen with the previous version i was using (1.7.0):
(focused)

(unfocused)

Best regards and thanks for the effort,

Hello,
well changing the default color changes many nodes in date picker content.
It would be better solution to change the icon color instead of default color, however this can't be done due to some binding. Will remove the icon binding so it can be changed through css.
Regarding the silver background issue, it's already fixed however was not included in 1.10.0.
you can download the latest version of JFoenix from the website.
Regards,

Hello,
I pushed the fix github, it will be pushed to maven central in the next release. meanwhile you can get it by downloading jfoenix jar from the website.
you can now change the icon color using:
.jfx-date-picker > .arrow-button > .jfx-svg-glyph{
    -fx-background-color: WHITE;
}

instead of changing the default color property
Regards,