otomi cli improvements

Improvements:

We can get rid of the active env vars CLUSTER & CLOUD by getting them from kubeconf current context:

see if it matches regex $customer-$cloud-$cluster, then extract

Implications:

otomi template and otomi values might not have a cluster yet, so they still should bork and ask to provide CLOUD & CLUSTER

I actually like this idea a lot, it would improve the new user experience. Why was it closed?

I actually like this idea a lot, it would improve the new user experience. Why was it closed?

It is already part of the new PR by @Dunky13. Where are those requirements found for otomi configure? We wrote them up somewhere but I see no more PR.

It is already part of the new PR by @Dunky13. Where are those requirements found for otomi configure? We wrote them up somewhere but I see no more PR.

There's no PR for it yet.
It's related to #274 but put the development of otocomplete on hold. I spent 3 full days on about 20 lines of code and wasn't making any progress. autocomplete for zsh is tricky when moving into several levels. The otomi configure that @Morriz mentioned is scripted there as well, but as dev is on hold for now, it hasn't been pulled into otomi.

There's no PR for it yet.
It's related to #274 but put the development of otocomplete on hold. I spent 3 full days on about 20 lines of code and wasn't making any progress. autocomplete for zsh is tricky when moving into several levels. The otomi configure that @Morriz mentioned is scripted there as well, but as dev is on hold for now, it hasn't been pulled into otomi.


FAILED asdf/_tests/test_yaml.py::test_implicit_conversion_warning

Hi,
While refreshing the package for Guix one unit test has failed.
Description of the problem

=================================== FAILURES ===================================
_______________________ test_implicit_conversion_warning _______________________
[gw4] linux -- Python 3.10.7 /gnu/store/jh59fh48mcffyz5wmsjj0p96xkkflbz0-python-wrapper-3.10.7/bin/python

    def test_implicit_conversion_warning():
        nt = namedtuple("TestTupleWarning", ("one", "two", "three"))

        tree = {"val": nt(1, 2, np.ones(3))}

>       with (
            pytest.warns(AsdfWarning, match=r"Failed to serialize instance"),
            pytest.warns(AsdfDeprecationWarning, match=r"implicit conversion is deprecated"),
            asdf.AsdfFile(tree),
        ):
E       Failed: DID NOT WARN. No warnings of type (<class 'asdf.exceptions.AsdfWarning'>,) were emitted. The list of emitted warnings is: [].

/tmp/guix-build-python-asdf-3.3.0.drv-0/asdf-3.3.0/asdf/_tests/test_yaml.py:203: Failed
=========================== short test summary info ============================
SKIPPED [3] ../../../gnu/store/glrxjwic379h2gmyxc2sfchvnw5g1aai-python-pytest-7.1.3/lib/python3.10/site-packages/_pytest/doctest.py:452: all tests skipped by +SKIP option
SKIPPED [9] ../../../gnu/store/7q3d3n6wjhvp4wfbm742yf90wi7yipc4-python-pytest-remotedata-0.4.1/lib/python3.10/site-packages/pytest_remotedata/plugin.py:81: need --remote-data option to run
SKIPPED [1] asdf/_tests/test_reference_files.py:55: got empty parameter set ['reference_file'], function test_reference_file at /tmp/guix-build-python-asdf-3.3.0.drv-0/asdf-3.3.0/asdf/_tests/test_reference_files.py:54
XFAIL asdf/_tests/test_yaml.py::test_python_tuple_key
  pyyaml has a bug and does not support tuple keys
XFAIL asdf/_tests/_regtests/test_1539.py::test_invalid_seek_and_read_from_closed_memoryio
  Fix will require more major changes to generic_io
FAILED asdf/_tests/test_yaml.py::test_implicit_conversion_warning - Failed: D...
============ 1 failed, 1834 passed, 13 skipped, 2 xfailed in 12.29s ============

Example of the problem

/bin/pytest -vv -n auto -p "no:legacypath"

System information

Python :: 3.10.7
Guix :: local checkout
<EMAIL_ADDRESS>
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Thanks for opening an issue.
I believe this is due to using pytest<8 (pytest 8 changed how warnings are captured). I was able to replicate this by installing pytest 7.3.
If possible would you try with a more recent version of pytest (version 8 or greater). I'll add a lower pin for pytest in the requirements for this package but it's unlikely we'll make a release with this pin anytime soon.

Hi @braingram
Thanks for suggestion. I've refreshed pytest to 8.2.2 and formally all tests passed and I've got this trace:
================================== XFAILURES ===================================
_______________ test_invalid_seek_and_read_from_closed_memoryio ________________

    @pytest.mark.xfail(reason="Fix will require more major changes to generic_io")
    def test_invalid_seek_and_read_from_closed_memoryio():
        """
        Seek and read from closed MemoryIO

        https://github.com/asdf-format/asdf/issues/1539
        """
        b = io.BytesIO()
        b.write(b"\0" * 10)
        b.seek(0)
        f = asdf.generic_io.get_file(b)
        f.close()
>       with pytest.raises(IOError, match="I/O operation on closed file."):
E       Failed: DID NOT RAISE <class 'OSError'>

/tmp/guix-build-python-asdf-3.3.0.drv-0/asdf-3.3.0/asdf/_tests/_regtests/test_1539.py:20: Failed
____________________________ test_python_tuple_key _____________________________

    @pytest.mark.xfail(reason="pyyaml has a bug and does not support tuple keys")
    def test_python_tuple_key():
        """
        This tests whether tuple keys are round-tripped properly.

        As of this writing, this does not work in pyyaml but does work in
        ruamel.yaml.
Oleg

Thanks! Yes that looks correct, all xfails and skips but no failures. I'll close this issue and the linked PR should address the issue for future releases.


Improve required file format

I'm submitting a ...

[ ] bug report
[X] feature request
[ ] code improvement request

Expected behavior
How should it work (with the bug fixed or the feature implemented)?
The header should be seperated in two lines. The first line should represent the variable names and the second line the variable symbols. That way the header has the same number of columns as the body.
The images and text explaining the user the definition of the format must be changed too.
Screenshot
Actual behavior
How does it currently work (with the bug causing problems or without the feature)?
Screenshot

Done:


Unnecessary navbar.css in icons folder

There is an navbar.css file in the icons folder that as far as I can tell, isn't used anywhere. it is different from the actual navbar file.

I think it's an old duplicate which somehow made its way in there. Looks like it's about 2 months old. I added it around when I was moving icon code around - must have copied it temporarily while I relocated the icon code and forgot to delete it.


fork 42 and 4

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes
Related pull request(s)

Going to close this for now, I'd rather use the local chain Ids and get everything to work like that.


Make string comments of Modelica.Magnetic.QuasiStatic.FundamentalWave consistent

Reported by beutlich on 29 Feb 2016 13:42 UTC
Comment of Modelica.Magnetic.QuasiStatic.FundamentalWave.Utilities.MultiTerminalBox.m is "number of phases" which is not consistent with Modelica.UsersGuide.Conventions.ModelicaCode.Format. Please note that comment of Modelica.Magnetic.QuasiStatic.FundamentalWave.Utilities.TerminalBox.m is "Number of phases" which is as expected.
One other issue I found is with comment "frequency of the source" of Modelica.Magnetic.QuasiStatic.FundamentalWave.Sources.ConstantMagneticPotentialDifference.f and Modelica.Magnetic.QuasiStatic.FundamentalWave.Sources.ConstantFlux.f.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1933

Comment by otter on 2 Mar 2016 08:56 UTC
Fixed in 4b5febe3c177444fce0e024306b83b58f8a6f008, by changing the first letters to upper case


Better full page reload failures

If some tests accidentally do a full page refresh, karma-dots-reporter reports the error, but karma-mocha-reporter doesn't make the failure as clear.
With dots reporter:
..............................................................................
PhantomJS 1.9.8 (Windows 7 0.0.0) ERROR
  Some of your tests did a full page reload!
PhantomJS 1.9.8 (Windows 7 0.0.0): Executed 78 of 135 ERROR (0.2 secs / 0.2 secs)

With mocha reporter:
PhantomJS 1.9.8 (Windows 7 0.0.0) ERROR
  Some of your tests did a full page reload!
Finished in 0.222 secs / 0.217 secs
SUMMARY:
√ 78 tests completed

A better report would be:
PhantomJS 1.9.8 (Windows 7 0.0.0) ERROR
  Some of your tests did a full page reload!
Finished in 0.222 secs / 0.217 secs
SUMMARY:
√ 78 tests completed
× 57 test failed

Can you please provide a test case which does the full page reload so that we can reproduce the behavior. That would help us a lot.

I would think a test like this would reproduce it. However, I've so far not been able to reproduce with your demo tests.
describe('thing', function() {
    it('should do stuff', function() {
        window.location.reload();
    });
});

See this issue for more discussion of this karma error:
https://github.com/karma-runner/karma/issues/1101

I was able to reproduce with this test:
describe('thing', function() {
    it('should do stuff', function() {
        window.location.reload();
        expect(1+1).toEqual(2);
    });
});

output is this:
START:
29 12 2015 11:35:39.293:WARN [karma]: Port 9876 in use
29 12 2015 11:35:39.297:INFO [karma]: Karma v0.13.16 server started at http://localhost:9877/
29 12 2015 11:35:39.303:INFO [launcher]: Starting browser PhantomJS
29 12 2015 11:35:39.824:INFO [PhantomJS 1.9.8 (Windows 7 0.0.0)]: Connected on socket SPElEECVbW6K94
R5AAAA with id 12782191
thing
    √ should do stuff

Finished in 0.004 secs / 0.002 secs

SUMMARY:
√ 1 test completed
PhantomJS 1.9.8 (Windows 7 0.0.0) ERROR
Some of your tests did a full page reload!

Finished in 0.021 secs / 0.002 secs

SUMMARY:
√ 1 test completed
Warning: Task "karma:success" failed. Used --force, continuing.

Done, but with warnings.

Thanks for the test case. I could easily reproduce the problem. But it is a bit tricky. Interestingly the onRunComplete method is called twice in this case, so the summary is printed twice. Also the test itself is successful for karma, so it is completed successful but the message with the full page reload is also printed.
I changed the handling in the onRunComplete method and hope the output is better now. Let me know if this acceptable for you.
START:
29 12 2015 21:19:55.379:INFO [karma]: Karma v0.13.16 server started at http://localhost:9876/
29 12 2015 21:19:55.385:INFO [launcher]: Starting browser PhantomJS
29 12 2015 21:19:57.008:INFO [PhantomJS 1.9.8 (Mac OS X 0.0.0)]: Connected on socket JdUrzi4k9z9lGV5pAAAA with id 72983911
  thing
    ✔ should do stuff
    ✔ should do other stuff

Finished in 0.005 secs / 0.001 secs

SUMMARY:
✔ 2 tests completed
PhantomJS 1.9.8 (Mac OS X 0.0.0) ERROR
  Some of your tests did a full page reload!

✖ Error while running the tests! Exit code: 1

Warning: Task "karma:reload" failed. Use --force to continue.

Aborted due to warnings.

Assuming the x and Error while running the tests are in red when colored I think that'd be great!

Yes, they are.

Published as v1.1.5

Please update fix for the following issue.
PhantomJS 1.9.8 (Mac OS X 0.0.0) ERROR
Some of your tests did a full page reload

The error comes from karma. It has nothing to to with the reporter. Maybe you should update to the latest version of karma and PhantomJS.


MWPW-137200 - Password protect pdf test

Resolves: https://jira.corp.adobe.com/browse/MWPW-137200
Test ticket for Converter: https://jira.corp.adobe.com/browse/MWPW-137197
Test ticket for Eventwrapper: https://jira.corp.adobe.com/browse/MWPW-138330

Codecov Report

Merging #439 (46fba0f) into stage (f5e1192) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            stage     #439      +/-   ##
==========================================
+ Coverage   96.57%   96.61%   +0.03%
==========================================
  Files          26       26
  Lines        2865     2865
==========================================
+ Hits         2767     2768       +1
+ Misses         98       97       -1

see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


environment for reproduction

Hello, thank you for sharing your work.
Could you possibly share the environment requirement to reproduce the training results?
Thank you in advance

Hi,
The core packages in environment I used before are:
torch==1.10.0+cu113
open3d==0.14.1
opencv-python==<IP_ADDRESS>
numpy==1.21.2
The above packages with other common python tools (like pyyaml, scipy ... ) are enough.

Thank you very much!


Refactor request mixin

As we have used the request mixin more, a couple of patterns/issues have emerged:
1. Promise catching
The request mixin already knows to do certain things when it catches an error response. However, because the mixin can return an uncaught promise, almost every request promise chain in Central ends with .catch(() => {}).
The vast majority of requests in Central look like this:
this.some_request_method(...args)
  .then(({ data }) => {
    // do something with data
  })
  .catch(() => {});

Given that, perhaps it'd be alright for request methods not to return a promise. Instead, the request methods could take a callback. If the component needs something more sophisticated, it can always use this.$http directly, but a callback approach should cover the vast majority of cases.
2. Promise chain order
Right now, components react to whether a request is in progress or not (see the awaitingResponse computed property). This is a little subtle, but there may be places where we want a component to update not when a request is done, but rather when the request is done and has been fully processed by Central.
For example, we might want a component not to permit certain actions until a request has been completed and fully processed. However, right now, those actions might be permitted in the (probably quite short) period between when the request is completed and when it is fully processed.
I think the callback approach mentioned above could help in this case as well. It would ensure that awaitingResponse (or its equivalent) would not be toggled until after the callback has been run.

With #203, we now use $store.dispatch('get') for GET requests. The request mixin no longer has get() or maybeGet(), and we have removed MaybeData. With these changes, the mixin is now used exclusively for non-GET requests.

1. Promise catching
The request mixin already knows to do certain things when it catches an error response. However, because the mixin can return an uncaught promise, almost every request promise chain in Central ends with .catch(() => {}).
…
[P]erhaps it'd be alright for request methods not to return a promise. Instead, the request methods could take a callback. If the component needs something more sophisticated, it can always use this.$http directly, but a callback approach should cover the vast majority of cases.

I think I have become convinced that .catch(() => {}) is inevitable. We do use catch() and finally() with promises, and while we could replace those with corresponding callback options in the request Vuex module and the request mixin, I hesitate to add complexity in those places. We also use promises widely throughout Central (Frontend and Backend), and I'm wary of making a change that could result in callback pyramids.
Chrome shows an error in the console for any uncaught promise, so for better or for worse, I think we need to continue adding catch() even if the catch() callback does nothing. However, I think we are soon going to add a noop() function so that we use () => {} in fewer places.

2. Promise chain order
Right now, components react to whether a request is in progress or not (see the awaitingResponse computed property). This is a little subtle, but there may be places where we want a component to update not when a request is done, but rather when the request is done and has been fully processed by Central.
For example, we might want a component not to permit certain actions until a request has been completed and fully processed. However, right now, those actions might be permitted in the (probably quite short) period between when the request is completed and when it is fully processed.

I think the request Vuex module mostly solves this. When $store.dispatch('get')is called, the following happens:

The request state is set to 'loading'.
The request is sent.
Once the response is received, the following all happens in the same event loop:

The request state is set to 'success'
The response is transformed. For example, it may be wrapped in a presenter object.
$store.state.request.data is updated.
If a success callback was specified, it is run.

Vue reacts to the changes to the store state, running watchers and updating the DOM.
Any then() or catch() callback is called.

The main change here is that much more is done in (3) rather than (5): the data is transformed and set at the same time that the request state is set to 'success', before Vue reacts. then() and catch() are still used, especially for changes that only affect the DOM. However, if it's important for a callback to be run in (3) rather than (5), a success callback can be specified.
These changes have only been made to the request Vuex module, not the request mixin. If anything, moving GET requests from the mixin to the Vuex module has made the mixin that much simpler. However, so far this issue seems to be less relevant to non-GET requests. After a response is received for a non-GET request, the mixin will set awaitingResponse to false — and Vue will react to that change — before any then() or catch() callback is run. However, awaitingResponse is mostly only used in rendering the DOM, not driving order-sensitive logic, and so far this doesn't seem like an issue.


32 Compute Features

resolves #32
The feature matrix is calculated correctly for tiff/tif images and saved in a .csv file
The following changes were implemented:

the button responsible for saving the segmentation in cellpose.gui/menus.py was adapted to be disabled by default to prevent error messages in case of it being used in inadequate situations
method toggle_save_features_csv was created in cellpose/gui/gui.py to control the menu button:

button is only enabled if the image is of the type .tif or .tiff
method is called in cellpose/gui/io.py; therefore the button is also only enabled if the picture has already been segmented
if a new image is loaded, the button is disabled again in the existing function _load_image in cellpose/gui/io.py to prevent it staying active

method convert_images_to_array was created in cellpose/gui/gui.py to facilitate the extraction of information about the channels:

returns four-dimensional stacked_array, with the intensity included in the fourth dimension
this is used in cellpose/gui/io.py to transform parent.grayscale_image_stack, where the current image is stored

in the existing method _save_features_csv in cellpose/gui/io.py, the indentically named method in cellpose/io.py is now called with two additional arguments:

cellpix: This stores the masks of the cells and therefore provides an overview over the segmented cells
channels: This is the information extracted using convert_images_to_array and contains the different segmentations depending on the channels. In the fourth dimension, only the second column is used, for those contain the relevant information

existing method save_features_csv in cellpose/io.py was adapted:

the individual cells are saved in cell_ids
the number of cells found is saved in num_cells
the number of channels is saved in num_channels
a matrix called features is initialized
this matrix is filled using two for loops:

the outer loop iterates over the cell_id and creates a boolean matrix cell_mask that saves for every pixel whether it is part of the current cell
the number of pixels is saved in num_pixels
the inner loop iterates over the channels num_channels

the marker intensity for the cells is calculated by multiplying the matrix for the respective channel (channels[j]) with the one indicating the current cell (cell_mask)
this is divided by the number of pixels and entered in the feature-matrix

the rows of the final feature-matrix contain the cells, the columns the channels
finally, this matrix is saved in a .csv file

This PR combines the code from #58 and the information from the research task #64.
The functionality is currently only given for tiff/tif images, for this is the most common use case. Future extensions of this are conceivable. However, this would need a more general conversion of image arrays which is not yet given.
Information for testing
For testing, I recommend using a relatively small tif image, since bigger images can lead to a long runtime. You are welcome to try it using bigger pictures, but at least my laptop sadly can't handle the segmentation leading to the program crashing.
You can use the button in the file menu once you have segmented the picture by clicking on the run cyto3 button:

The button in the file menu should only be usable after the segmentation. Prior to that, you should not be able to click on it (depending on your system it might look grey or somewhat blurry). In my case, it looks like this, it might be more clear on Mac.

Showcase
For the example_tif_image.tif file (on the right) that was sent in the Discord server, the resulting matrix in the created file (on the left) should look like this:

(If you can't find the file I can send it to you of course.)
Interpretation
The values in the matrix should be between 0 and 255. Bigger values indicate a higher intensity.
In the example above we could therefore deduce that channel 1 and channel 5 are relatively bright for the given cells.

Great job! Your code was easy to follow and understand due to the clear documentation provided in both your code and your PR.
I tested your code as described by loading an image, segmenting it, and finally saving it. Since I used the same tiff image, a CSV file was also loaded in the same folder as the image with the same values you have in your example. The values in channel 1 and channel 5 are also higher. Additionally, the button in the file menu was only usable after segmentation (it was greyed out before that).
I have just a small note: When loading large-sized tif images, the option to save as CSV does not appear and is displayed as greyed out.
However, this might not be an issue.
Other than that, I don't have any further remarks and would approve!

Thank you for your quick and thorough review!
I believe there has been a misunderstanding. What you are describing is intended that way: If you were able to export the data right now, you would get an empty matrix, since you haven't run the segmentation yet (this is also why the buttons above are greyed out as well). If you click on the run cyto3 button (and your program doesn't crash), you should be able to use the button again :)

Thanks for the thorough explanation of the changes! I'm testing the implemented feature and came across the following:
Button is inactive before segmentation and remains so for non-tiff images ✓ However, after loading a .tif image, segmenting it and clicking on the button, I receive this error message on the terminal:  I'm still figuring out why this might be. Also, I removed an import of the PIL package that was causing trouble in my computer.

Hi Nicolas, thank you for your review!
Could you provide more information as to what kind of image you are using? This message appeared previously when using non-tiff images if I remember correctly, but this should not be possible anymore....


Need to create the github documentation

Description:
Need to create the github docs and and add sample responses for each method.

Moved to https://github.com/wso2/docs-mi/issues/788


nginx: Add CORS, HSTS, and X-Frame-Options headers to error responses

Testing Plan: Production install at https://andersk.zulipdev.org.

Merged, thanks @andersk!


Missing dependency: CompileTime

Going from version Waud 0.4.8 to 0.4.9, CompileTime became necessary.
https://github.com/adireddy/waud/commit/6d6d6fbb0c9de537da2ba031d916e760f755c65e

new version 0.5.0 without compiletime is out now.


Allow user to add multiple accounts

As a user, I want to add more than 1 account (gmail, or Microsoft)
desiggn ui to allow this

The example app will implement this. It will be on hold for UI design to be implemented in TIKI app.
Acceptance criteria:
1 - Example app allowing multiple accounts.

https://user-images.githubusercontent.com/8357343/172168285-2456701f-74b2-4938-9163-f0ef9790c58a.mov


CI: Makefile: Add more flake8 tests and lint the whole repo

Description
(Brief description on what this PR is about)
Makefile: Add more flake8 tests and lint the whole repo
Syntax errors and undefined names in test files are worth knowing about/fixing.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[x] more flake8 tests
[x] lint the whole repo (including tests)

Comments

Syntax errors and undefined names in test files are worth knowing about/fixing.

In order to view the Jenkins results I need to provide ci.mxnet.io with read and write access to the code in all my repos, all my settings, all my deployment keys?!?
Authorize ci.mxnet.io
@cclauss ci.mxnet.io by dmlc
wants to access your cclauss account
Repositories
Public repositories

This application will be able to read and write all public repository data. This includes the following:

    Code
    Issues
    Pull requests
    Wikis
    Settings
    Webhooks and services
    Deploy keys

Job PR-808/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-808/1/index.html

I meant that if I click on the "Details" buttons next to the failed tests below, I need to give that access to see the results of those tests.

@cclauss these are the ones we configured the CI for read:org,user:email,public_repo

@cclauss we actually don't need most of the settings, but rather just whether a user has admin access to a public repo. would you happen to know what the appropriate scope is?

I do not.  Sorry.

@cclauss I removed the public-repo part. could you give it another try?

That worked perfectly...  Thanks much.

Job PR-808/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-808/2/index.html

Job PR-808/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-808/3/index.html


Add sort key option for ImageViewer

Add an option for specifying the order of figures. Currently the ImageViewer would display figures in a random order. This feature can also be added to other modules such as VideoViewer
Checklist:

[x] I am familiar with the Contributing Guidelines.
[x] I agree with the terms of the Contributor Agreement.
[ ] The changes introduced by this pull request are covered by existing or newly introduced tests.
[ ] The package documentation and framework documentation in signac-docs are up to date with these changes.
[ ] I have updated the changelog and added any related issue and pull request numbers for future reference.

One consideration: should different file types be grouped together? What should the default be?
Sorting alphabetically could result in mixing of file types. Does this matter?
image_a.png
image_b.gif
image_b.png

The sort function should act on the file path relative to the job directory. The caller should be responsible for grouping the results by extension in the sort function, if that is desired.

One consideration: should different file types be grouped together? What should the default be?
Sorting alphabetically could result in mixing of file types. Does this matter?
image_a.png
image_b.gif
image_b.png

The sort function should act on the file path relative to the job directory. The caller should be responsible for grouping the results by extension in the sort function, if that is desired.

So I guess the only thing left is to add docstring?

I added the same option to VideoViewer which also deals with files.

docstring

What do you think of how I described the argument in the video_viewer module?

I added the same option to VideoViewer which also deals with files.

docstring

What do you think of how I described the argument in the video_viewer module?

I think the name of the parameter is self-explanatory, so probably don't need to mention it's passed internally to sorted. But if you want to be more specific, we could probably be more direct and just say that it is the key parameter of sorted.


feat: Simpler UpdateFields

from:
users.update(
            {
                userId: bunny.userId,
            },
            {
                op: UpdateFieldsOperator.SET,
                fields: {
                    name: "Jania McGrover",
                },
            }
        );

to
users.update(
            {
                userId: bunny.userId,
            },
            {
                    name: "Jania McGrover",
            }
        );

Codecov Report

Merging #34 (7d69c3f) into main (508168e) will increase coverage by 0.13%.
The diff coverage is 96.00%.

@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
+ Coverage   91.72%   91.85%   +0.13%
==========================================
  Files           7        7
  Lines        1377     1388      +11
  Branches      200      201       +1
==========================================
+ Hits         1263     1275      +12
  Misses        111      111
+ Partials        3        2       -1

Impacted Files
Coverage Δ

src/collection.ts
84.43% <66.66%> (ø)

src/types.ts
91.62% <100.00%> (-0.03%)
:arrow_down:

src/utility.ts
98.67% <100.00%> (+0.39%)
: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 508168e...7d69c3f. Read the comment docs.


Bugfix. Correct wrong method call from scheduleTask() to scheduleTaskForDatabase()

Bug introduced in #12766
Also revert the deprecated annotation removed by #12459
labels
bugfix

For some reason all but one of the pipeline jobs using Java 21 failed. I've just re-scheduled them

Thanks @gortiz , when I checked it was having troubles downloading Node.js dep


WORKDIR changed in Dockerfile

See WORKDIR /app.
WORKDIR was changed from "/" to "/app".
But there are no synchronous changes to the use of docker in the documentation.

The commit: https://github.com/casdoor/casdoor/commit/cd902a21ba3ad9441bf3c5f6491dced49dfa7177 caused this.
@atompi plz change the work dir back to "/" by making a new PR and keep the docs up-to-update.


Add slash command reply functions

Implemented slash command related functions in lib/SlackBotWorker/index.js.

bot.replyPublic()
bot.replyPrivate()
bot.replyPublicDelayed()
bot.replyPrivateDelayed()
raise version to 0.1.1

"Delayed" functions and the other functions are equal because botkit-mock don't distinguish timing of reply.
All four functions store reply message in bot.api.logByKey, just like replyInteractive().
(Added test files for this change in tests/slash_command/. Is that OK?)

Reviewing this and will cycle back with any comments

Thanks 😆


console error on 1.13

Info

Server version: 1.13 latest buildtools
OldCombatMechanics version: latest from spigot
Server log file: https://hastebin.com/sawetuqiho.md
OldCombatMechanics config file: untouched,default config

Problem Description

there isn't a problem that i notice ingame, just a console error.

For the sake of bookkeeping:
It sounds like a duplicate of #246 which is a duplicate of #229 which was fixed in PR #230, merged at the 5th of September.
For you:
This error was fixed in a development build a while ago.
Please try a dev build from here and report back, if this does not resolve the error for you.


Adding logging

Could you attach the logger to the connection to the local spire-agent as well: https://github.com/square/spiffe-aws-assume-role/blob/master/pkg/credentials/spiffejwt.go#L40
Would be helpful for debugging connection issues there


Investigate creating a simpler sql call to replace get-project-stats on the institution page

The get-project-stats route is too slow.  There is another issue to limit how soon this route is called.  It is causing the side effect of delaying other calls (add imagery, add member, etc).  For the institution page, we only need to know if the project has been started, or has been finished.  A simpler sql function might allow us to continue to load all the info up front.

CREATE OR REPLACE FUNCTION select_simple_project_statistics(_project_id integer)
 RETURNS TABLE(
    started       boolean,
    finished      boolean
 ) AS $$

   WITH sums AS (
        SELECT SUM(coalesce(flagged::int, 0)) as flagged,
            SUM((user_plot_uid IS NOT NULL)::int) as assigned,
            COUNT(plot_uid) as plots
        FROM projects prj
        INNER JOIN plots pl
          ON project_uid = pl.project_rid
        LEFT JOIN user_plots ps
          ON ps.plot_rid = plot_uid
	   GROUP BY project_uid, plot_uid
        HAVING project_uid = _project_id
    )

    SELECT flagged + assigned > 0 as started,
        CAST(GREATEST(0, (plots - flagged - assigned)) as int) = 0 as finished
    FROM sums

$$ LANGUAGE SQL;

This is also faster for regular stats
CREATE OR REPLACE FUNCTION select_project_statistics(_project_id integer)
 RETURNS TABLE(
    flagged_plots       integer,
    assigned_plots      integer,
    unassigned_plots    integer,
    members             integer,
    contributors        integer,
    created_date        date,
    published_date      date,
    closed_date         date,
    archived_date       date,
    user_stats          text
 ) AS $$

    WITH project_plots AS (
        SELECT project_uid,
            plot_uid,
            (CASE WHEN collection_time IS NULL OR collection_start IS NULL THEN 0
                ELSE EXTRACT(EPOCH FROM (collection_time - collection_start)) END) as seconds,
            (CASE WHEN collection_time IS NULL OR collection_start IS NULL THEN 0 ELSE 1 END) as timed,
            u.email as email
        FROM user_plots up
        INNER JOIN plots pl
            ON up.plot_rid = plot_uid
        INNER JOIN projects p
            ON pl.project_rid = project_uid
        INNER JOIN users u
            ON up.user_rid = user_uid
        WHERE project_uid = _project_id
    ), user_groups AS (
        SELECT email,
            SUM(seconds)::int as seconds,
            COUNT(plot_uid) as plots,
            SUM(timed):: int as timedPlots
        FROM project_plots
        GROUP BY email
        ORDER BY email DESC
    ), user_agg as (
        SELECT
            format('[%s]',
                   string_agg(
                       format('{"user":"%s", "seconds":%s, "plots":%s, "timedPlots":%s}'
                              , email, seconds, plots, timedPlots), ', ')) as user_stats
        FROM user_groups
    ), members AS (
        SELECT COUNT(distinct user_uid) as members
        FROM select_project_users(_project_id)
    ), plotsum AS (
        SELECT SUM(coalesce(flagged::int, 0)) as flagged,
            SUM((user_plot_uid IS NOT NULL)::int) as assigned,
            plot_uid
        FROM projects prj
        INNER JOIN plots pl
          ON project_uid = pl.project_rid
        LEFT JOIN user_plots ps
            ON ps.plot_rid = plot_uid
        GROUP BY project_uid, plot_uid
        HAVING project_uid = _project_id
    ), sums AS (
        SELECT MAX(prj.created_date) as created_date,
            MAX(prj.published_date) as published_date,
            MAX(prj.closed_date) as closed_date,
            MAX(prj.archived_date) as archived_date,
            (CASE WHEN SUM(ps.flagged::int) IS NULL THEN 0 ELSE SUM(ps.flagged::int) END) as flagged,
            (CASE WHEN SUM(ps.assigned::int) IS NULL THEN 0 ELSE SUM(ps.assigned::int) END) as assigned,
            COUNT(distinct pl.plot_uid) as plots
        FROM projects prj
        INNER JOIN plots pl
          ON project_uid = pl.project_rid
        LEFT JOIN plotsum ps
          ON ps.plot_uid = pl.plot_uid
        WHERE project_uid = _project_id
    ), users_count AS (
        SELECT COUNT (DISTINCT user_rid) as users
        FROM projects prj
        INNER JOIN plots pl
          ON project_uid = pl.project_rid
            AND project_uid = _project_id
        LEFT JOIN user_plots up
          ON up.plot_rid = plot_uid
    )

    SELECT CAST(flagged as int) as flagged_plots,
        CAST(assigned as int) assigned_plots,
        CAST(GREATEST(0, (plots-flagged-assigned)) as int) as unassigned_plots,
        CAST(members as int) as members,
        CAST(users_count.users as int) as contributors,
        created_date, published_date, closed_date, archived_date,
        user_stats
    FROM members, sums, users_count, user_agg

$$ LANGUAGE SQL;

The first function might be able to be combined with get-institution-projects now that its so much faster.


Release/v0.14.0

After merging, please think about add a git tag v0.14.0

Going to close this, as this change will be covered by your other PR (#233).
Please see my comment on the issue (#210) to explain when SetContent event is needed.


Update GAX version to 0.0.3

You missed the most important update, in build.gradle.

Done. PTAL.

LGTM.


docs(quickstart-ts): add note about ES6 shim

Adding appendix to TS quickstart regarding ES6 support and how to use a shim to get the example working on older browsers.

Thanks for adding this.


Removed extra spaces between lines.

issue : unnecessary spaces present between the lines.
ISSUE DETAILS
There is unnecessary spaces present between the lines in the section : Basics, Configuration, Stateless Applications ,Stateful Applications
To see the issue go to this link "https://kubernetes.io/docs/tutorials/"

WHY IT NEEDS TO BE CHANGED?
To maintain uniformity of documentation writing style. So to maintain this uniformity i have removed the extra spaces. You can see these links and screenshots provided below , how the sections are maintained in other pages :
Visit this link and go to section What's next : https://kubernetes.io/docs/setup/

Visit this link and go to section Services , Security: https://kubernetes.io/docs/tutorials/

/kind cleanup
/lgtm for consistency purposes.
Thanks @PranitRout07

/lgtm

@Gauravpadam lists aren't supposed to have extra lines between list items so this approach is correct

Thanks for the confirmation @shannonxtreme! :)  That was my only concern

@Gauravpadam  i have checked other markdown files where there is no space between the lines , so for this reason i removed spaces from markdown file only.

/lgtm
This will fix the consistency issues about bullets on this page.

Hey @shannonxtreme ,is there anything more to do in this pull request for approval?

I think it's fine to merge but you need an Approver (@kbhawkey was assigned to this one) to actually approve and merge it. They'll get to it in time!

ok thanks for the confirmation @shannonxtreme :)

Hey @kbhawkey , is this pull request good to go?

I would avoid tagging approvers unless your PR has been stale for a while. I've had some PRs sit for weeks - there are few approvers and very many PRs to get to in the project :P

/retitle Remove some vertical space between lines of text

/approve


Add disable_sso_sls_verify config option

Allowing for a disable_sso_sls_verify configuration option.  This was brought about when trying to integrate with Okta for single logout.  Okta insists on sending a HTTP_POST when confirming an SLO request which the underlying Onelogin Saml-PHP framework is not currently compatible with. The Sign out process doe in fact complete but our app is not able to verify the HTTP_POST response.
I am proposing that by setting this disable_sso_sls_verify to true, if we encounter an error on SLO processing, we assume the request succeeded, kill the current user session and redirect to a logout page.
I can update the wiki if accepted.

This is now more specific.  Will only bypass the error on logout when HTTP_REDIRECT binding is not used and we specify disable_sso_sls_verify in the config


isFrozen() modifier is not used in the contract

true, lets remove it. But could be useful in the future.

Addressed in  #26


[WIP] Periodogram class and asteroseismology

There are a lot of commits on this branch from me, make sure that you're working from the current KeplerGO master branch of lightkurve rather than one of my crumby old branches!

This is breaking because we need to add pandas as a dependency.

Codecov Report

Merging #177 into master will decrease coverage by 0.05%.
The diff coverage is 92.1%.

@@            Coverage Diff             @@
##           master     #177      +/-   ##
==========================================
- Coverage   93.18%   93.13%   -0.06%
==========================================
  Files          17       19       +2
  Lines        2421     2461      +40
==========================================
+ Hits         2256     2292      +36
- Misses        165      169       +4

Impacted Files
Coverage Δ

lightkurve/__init__.py
100% <100%> (ø)
:arrow_up:

lightkurve/tests/test_periodogram.py
100% <100%> (ø)

lightkurve/lightcurve.py
92.13% <100%> (-0.14%)
:arrow_down:

lightkurve/periodogram.py
89.65% <89.65%> (ø)

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 1f0fb99...92cbd1a. Read the comment docs.


[WIP] Add LSUN dataset

Work in Progress for adding the LSUN dataset for classification and segmentation, which is accessible here.

get_file may be a good way to download file for unification.


Stylus support

Could you please add stylus support??

You need to ask this on the upstream project
See #3


add check for empty note array

Added a ValueError in compute_pianorolls when passing empty note arrays.

excuse me, the change is in _make_pianoroll.


Add experience block

Add into block:

Header
Experiences
Additional info

Header - https://github.com/ticial/homepage/commit/b0179011f86a7640608701f0e2d1c810a4bb62f8

Experiences - https://github.com/ticial/homepage/commit/f6ef882798c89e4f72138038d35d472aa6281cb5

Additional info - https://github.com/ticial/homepage/commit/e2c2ddee434c05bec49c4696f3c7627b9080c73e


FIT files - incorrect product and product_name for APEX 2

The FIT files from the APEX 2 do not identify the watch like other devices.

product = 822 (same as APEX 2 Pro)
product_name = COROS Wearables (instead of COROS APEX 2)

Some other watches for reference:

804 = COROS PACE 3
822 = COROS APEX 2 Pro
831 = COROS VERTIX
832 = COROS VERTIX 2
841 = COROS APEX Pro

This is a proposed wokaround to patch the data when consuming a FIT from the APEX 2:

Field
Value
Criteria

product
821
product = 822 and product_name == "COROS Wearables"

product_name
"APEX 2"
product = 822 and product_name == "COROS Wearables"


Optimise dockerfile

Remove the ppa (afaik the packages from the ppa were not used, because their versions was lower than that in the ubuntu repositories)
Use the non -dev versions of packages

What's the reason for including the e2e Test in the image?


Port nano to OMVS

Hi!
I have tried in the past to port nano to OMVS
I hit many problems, and admittedly, I was very new to much of the technology on my previous attempts - but all failed ;) From memory I got stuck in a constant chain of porting a giant myriad of other libraries and tools.
Is there a good guide on how to get started - or a support network for when I hit a problem?

I think you have come to the right place.  A Primary purpose of this project is to help anyone who is trying to port code to z/OS, which is no small feat sometimes.  It may be best to have a working session to review the kinds of problems you have encountered so far.  If this sounds like a good idea, I could set something up.

Excellent - let me remind myself where I got to, and then we can schedule.

config.log
I run ./configure and it eventually ends with the following:
config.status: error: Something went wrong bootstrapping makefile fragments     for automatic dependency tracking.  If GNU make was not used, consider     re-running the configure script with MAKE="gmake" (or whatever is     necessary).  You can also try re-running configure with the     '--disable-dependency-tracking' option to at least be able to build     the package (albeit without support for automatic dependency tracking).
Please see the attached config.log

Note - I have progressed further than this in the past, but don't have the time to dig indepth right now - and share here in the hope of some quick solution so I can continue attempting the compile.

Do you have Rocket's port of GNU make installed? If not then you should install gmake and automake and all the other tools.
BTW, Rocket has a decent z/OS port of Vim. Are you interested in nano because of the initial Vim learning curve?


Fix x and y pos being added to width and height.

It’s relative to parent after all. Or am I missing something here?
This bug is easy to test by creating a Sprite with some graphics:

with y = 0, height will be equal to Graphics
with y = 1,  height will be 1 + Graphics height...

Issue with doc build

Do you have example code of a use-case this fixes?

I was placing objects below each other in a loop and the y-position kept growing exponentially.

Merged, I thought this was going to cause a regression in the textField.getBounds behavior, but I was wrong. Makes sense :smile:


Optimize our AWS spend by adding in reserved instances

We want to further reduce our AWS cost. Using reserved EC2 instances could help us further manage our cost.

Issue is no longer valid as we are now 3rd party hosted.


Vulnerability roundup 111: mysql-8.0.27: 69 advisories [7.1]

search, files

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

CVE details
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-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-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-unstable: 5aaed40d22f.
Cc @orivej

Fixed:

nixos-unstable: mysql-5.7.39, mysql-8.0.30


polygit server is down

polygit.org is down.
Duplicate Issues:
https://github.com/PolymerLabs/polygit/issues/7
https://github.com/PolymerLabs/polygit2/issues/13

Duplicate of https://github.com/PolymerLabs/polygit2/issues/13
Other issue closed.