Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance toolkit exits before running any scenarios #21106

Closed
sshymko opened this issue Feb 10, 2019 · 29 comments
Closed

Performance toolkit exits before running any scenarios #21106

sshymko opened this issue Feb 10, 2019 · 29 comments
Labels
Component: Setup Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: done Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. stale issue Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@sshymko
Copy link

sshymko commented Feb 10, 2019

The Magento Performance Toolkit is unable to run against a vanilla Magento 2 instance installed from scratch with the required fixture data. It successfully completes the preliminary preparation steps, but never gets to execute any frontend scenarios. JMeter exits without any errors.

Preconditions (*)

  1. Magento 2.2.7 w/ Redis session storage
mysql -e "CREATE DATABASE magento2"

git clone https://github.com/magento/magento2.git
cd magento2/
git checkout -b v2.2.7 2.2.7

composer install --no-dev
chmod -R ug+rwX app/etc/ var/ pub/media/
php bin/magento setup:install \
    --base-url="http://127.0.0.1/" \
    --backend-frontname="admin" \
    --use-rewrites=1 \
    --db-host="localhost" --db-name="magento2" \
    --admin-user="admin" --admin-password="123123q" \
    --admin-firstname="Admin" --admin-lastname="Admin" --admin-email="admin@example.com" \
    --language=en_US --currency=USD --timezone=America/Los_Angeles \
    --session-save=redis --session-save-redis-host=/var/run/redis.sock --session-save-redis-port=0 \
    --session-save-redis-db=0 --session-save-redis-disable-locking=1 --session-save-redis-log-level=3

php bin/magento config:set dev/static/sign 1
php bin/magento config:set dev/css/minify_files 1
php bin/magento config:set dev/js/minify_files 1
php bin/magento config:set dev/js/enable_js_bundling 1
php bin/magento config:set admin/security/admin_account_sharing 1
php bin/magento config:set admin/security/use_form_key 0

php bin/magento deploy:mode:set production
composer dump-autoload --no-dev --optimize

php bin/magento indexer:set-mode schedule
php bin/magento indexer:reindex

php bin/magento cache:flush
  1. JMeter 3.1 w/ JSON plugin
sudo yum install java -y

curl -L -O https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-3.1.tgz
tar -xzf apache-jmeter-3.1.tgz

curl -L -O https://jmeter-plugins.org/files/packages/jpgc-json-2.5.zip
unzip jpgc-json-2.5.zip -d ./apache-jmeter-3.1/

Steps to reproduce (*)

  1. Generate fixture data
php bin/magento setup:performance:generate-fixtures setup/performance-toolkit/profiles/ce/small.xml
  1. Run JMeter test plan
jmeter -n \
    -t magento2/setup/performance-toolkit/benchmark.jmx \
    -j jmeter.log \
    -l jmeter-results.jtl \
    -Jhost=127.0.0.1 \
    -Jbase_path=/ \
    -Jadmin_path=admin \
    -Jadmin_user=admin \
    -Jadmin_password=123123q \
    -Jfiles_folder=magento2/setup/performance-toolkit/files/ \
    -Jloops=1 \
    -JfrontendPoolUsers=1 \
    -JadminPoolUsers=0 \
    -JcsrPoolUsers=0 \
    -JothersPoolUsers=0

Expected result (*)

  1. JMeter successfully runs all frontend scenarios

Actual result (*)

  1. JMeter successfully completes the preparation (log in to admin, load products, categories, customers, etc.)
  2. JMeter exits before executing any frontend scenarios
Writing log file to: /home/ec2-user/jmeter.log
Creating summariser <summary>
Created the tree successfully using /home/ec2-user/magento2/setup/performance-toolkit/benchmark.jmx
Starting the test @ Sun Feb 10 05:51:07 UTC 2019 (1549777867357)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
summary =    224 in 00:00:05 =   45.0/s Avg:    15 Min:     0 Max:   676 Err:     0 (0.00%)
Tidying up ...    @ Sun Feb 10 05:51:12 UTC 2019 (1549777872774)
... end of run
  1. Nginx access logs shows only preparation requests
3.81.150.213 - - [10/Feb/2019:07:33:39 +0000] "GET /admin HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:39 +0000] "GET /admin/admin/ HTTP/1.1" 200 2358 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:39 +0000] "POST /admin/admin/dashboard/ HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "GET /admin/admin/dashboard/ HTTP/1.1" 200 9246 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "GET /rest/V1/categories/list?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=path&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=1%2F2%2F%25&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5BconditionType%5D=like&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=level&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=2&searchCriteria%5BpageSize%5D=100 HTTP/1.1" 200 536 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "GET /rest/default/V1/categories/list?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=children_count&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=0&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=level&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=2&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B0%5D%5BconditionType%5D=gt&searchCriteria%5BpageSize%5D=0 HTTP/1.1" 200 892 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:40 +0000] "GET /rest/V1/products?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=type_id&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=configurable&searchCriteria%5BpageSize%5D=15 HTTP/1.1" 200 8107 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "GET /rest/V1/products?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=type_id&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=configurable&searchCriteria%5BpageSize%5D=15&searchCriteria%5BcurrentPage%5D=2 HTTP/1.1" 200 1271 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "GET /rest/V1/products?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=type_id&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=simple&searchCriteria%5BpageSize%5D=30&searchCriteria%5BcurrentPage%5D=1&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B1%5D%5Bfield%5D=attribute_set_id&searchCriteria%5BfilterGroups%5D%5B1%5D%5Bfilters%5D%5B1%5D%5Bvalue%5D=4 HTTP/1.1" 200 5550 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "POST /rest/V1/integration/admin/token HTTP/1.1" 200 65 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "GET /rest/V1/products?searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bfield%5D=type_id&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B0%5D%5Bvalue%5D=simple&searchCriteria%5BpageSize%5D=30&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B1%5D%5Bfield%5D!=attribute_set_id&searchCriteria%5BfilterGroups%5D%5B0%5D%5Bfilters%5D%5B1%5D%5Bvalue%5D=4 HTTP/1.1" 200 5528 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:41 +0000] "POST /admin/admin/user/roleGrid/limit/200/?ajax=true&isAjax=true HTTP/1.1" 200 3209 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:42 +0000] "GET /admin/customer/index/ HTTP/1.1" 200 7914 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:42 +0000] "GET /admin/mui/index/render/?namespace=customer_listing&sorting%5Bfield%5D=entity_id&sorting%5Bdirection%5D=asc&isAjax=true&filters%5Bplaceholder%5D=customer_since%5Blocale%5D%3Den_US&filters%5Bgroup_id%5D=1&filters%5Bwebsite_id%5D=1&paging%5BpageSize%5D=100&paging%5Bcurrent%5D=1&sorting%5Bfield%5D=entity_id&sorting%5Bdirection%5D=asc&isAjax=true HTTP/1.1" 200 1932 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:42 +0000] "GET /admin/directory/json/countryRegion/?parent=US HTTP/1.1" 200 969 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:43 +0000] "POST /checkout/cart/add HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:43 +0000] "GET / HTTP/1.1" 200 7050 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
3.81.150.213 - - [10/Feb/2019:07:33:43 +0000] "GET /page_cache/block/render/?blocks=[\x22customer_form_login\x22]&handles=[\x22default\x22,\x22customer_account_login\x22]&originalRequest={\x22route\x22:\x22customer\x22,\x22controller\x22:\x22account\x22,\x22action\x22:\x22login\x22,\x22uri\x22:\x22/customer/account/login/\x22}&ajax=true&isAjax=true HTTP/1.1" 200 754 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0" "-"
  1. JMeter log shows no errors
    jmeter.log
    jmeter-results.jtl
@magento-engcom-team
Copy link
Contributor

Hi @sshymko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@sshymko do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

  • yes
  • no

Sorry, something went wrong.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Feb 10, 2019
@sshymko
Copy link
Author

sshymko commented Feb 10, 2019

@magento-engcom-team yes

@sshymko
Copy link
Author

sshymko commented Feb 10, 2019

@kandy
This is the issue with the performance toolkit I've been facing.
Any idea what could be wrong?

@pmouawad
Copy link

@sshymko can you attach the jmx file you use ? thanks

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@pmouawad
This is an unmodified JMX file that comes with the performance toolkit:
https://github.com/magento/magento2/blob/2.2.7/setup/performance-toolkit/benchmark.jmx

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@pmouawad
I see you're part of the JMeter team :)
Please note that the old version of JMeter 3.1 is used for testing.
More up-to-date versions 4 and 5 are unfortunately not supported.
I would really appreciate any clues of what could be wrong.

@pmouawad
Copy link

Thanks, any way to provide to me an access to your instance or a docker image or any other alternative ? thanks

@ghost ghost self-assigned this Feb 11, 2019
@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.3-develop branch

    Details- Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Verify that the issue is reproducible on 2.2-develop branch.

    Details- Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

  • Next steps are available in case you are a member of Community Maintainers.

  • 6. Add label Issue: Confirmed once verification is complete.

  • 7. Make sure that automatic system confirms that report has been added to the backlog.

Sorry, something went wrong.

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@pmouawad
Here's a test instance for you: http://3.85.65.228/
Feel free to play with it for the next ~10 hours; it will be terminated after that.
The JMeter command provided in the ticket description has all credentials embedded.
Thank you so much for looking into this issue, it's greatly appreciated.

@pmouawad
Copy link

It would be better if you let it live until 23h30 Paris Timezone, it’s 9am now. I am working for a customer, not sure I can dedicate time today before 20h30

@kandy
Copy link
Contributor

kandy commented Feb 11, 2019

@sshymko Looks like there is an issue of our Jmeter configuration. If loops count < 2 it will not run any scenario.
So current workaround will be to increase number of loops.

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@kandy
Thank you so much! I'll try running with loops > 1 and let you know how it goes.

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@kandy
I can confirm that the workaround of -Jloops=2 does work!

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@kandy
I'm just curious, how did you figure out that the issue was loops=1?
The usage of the loops parameter in the JMX is pretty straightforward and looks correct to me.
Is there a loops=loops-1 logic hiding somewhere in the BinShell scripts?

@kandy
Copy link
Contributor

kandy commented Feb 11, 2019

@sshymko Looks like it's strange behavior in case Thread Group with Throughput Controler and throughput less than 100% work. The scenario with 100 throughput work with 1 loop too.

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

@kandy
Perhaps it's finally the time to upgrade to the latest JMeter that hopefully has no issues like that ;)

@pmouawad
Copy link

Hello,
The problem is that with a loop of 1, and none of the ThroughputController having 100%, you can end up executing nothing.
In the long run (more loops) the percentage will be matched.

This is expected behavior.
If you want a guarantee of running use one of those 2 approaches:

@kandy , if I can help on the test plan let me know where to make a kind of review.

I had reported following issue but AFAICU ,nothing was taken into account:

#723

@pmouawad
Copy link

I see a potential issue in:
"SetUp - BeanShell Sampler: Collect simple product for edit"

on second iteration, editProductList is null
if (1 == Integer.parseInt(vars.get("simple_products_counter_for_edit"))) { editProductList = new ArrayList(); props.put("simple_products_list_for_edit", editProductList); } else { productList = props.get("simple_products_counter_for_edit"); }

Should it be ?

`
if (1 == Integer.parseInt(vars.get("simple_products_counter_for_edit"))) {
editProductList = new ArrayList();
props.put("simple_products_list_for_edit", editProductList);
} else {
editProductList = props.get("simple_products_list_for_edit");
}

`

@pmouawad
Copy link

Also be aware that with upgrade of Beanshell version, it became more strict and you need to declare variables.

Anyway I suggest you move out of Beanshell, javascript which break scalability of JMeter

@sshymko
Copy link
Author

sshymko commented Feb 11, 2019

All right, I'm shutting down the test instance 3.85.65.228.
I'll proceed with the workaround to unblock my testing.
Thanks everybody for the assistance!

@ghost
Copy link

ghost commented Feb 18, 2019

HI @sshymko thank you for you report, i' closing this on comment -> #21106 (comment)

@ghost ghost closed this as completed Feb 18, 2019
@sshymko
Copy link
Author

sshymko commented Feb 18, 2019

@engcom-backlog-nazar
Why was the ticket closed?
The issue with the loops=1 is reproducible on vanilla Magento of any version.
Yes, there's a workaround to use loops=2, but the bug report is still valid.
Please reopen the ticket.

@ghost
Copy link

ghost commented Feb 19, 2019

@sshymko so how we can fix this in magento ? if problem not in magento codebase ?

@pmouawad
Copy link

@engcom-backlog-nazar, maybe you should open another issue to fix issues in test plan.

See #21106 (comment) and other performance issues.

Thanks

@ghost ghost reopened this Feb 19, 2019
@ghost ghost added Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Component: Setup labels Feb 19, 2019
@ghost ghost removed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Oct 20, 2020
@sdzhepa sdzhepa added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Nov 6, 2020
@magento-engcom-team magento-engcom-team added Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. labels Nov 30, 2020
@stale
Copy link

stale bot commented Feb 15, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

@magento-engcom-team
Copy link
Contributor

Hi @sshymko.

Thank you for your report and collaboration!

The related internal Jira ticket MC-24354 was closed as Fixed.

The fix will be available with the upcoming 2.4.3 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Setup Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: done Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S4 Affects aesthetics, professional look and feel, “quality” or “usability”. stale issue Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Development

No branches or pull requests

5 participants