Error from `symphony/console`: An argument with name "suite" already exists

[cliffordp]

Anyone else ever get this error?

An argument with name "suite" already exists.

Best I can tell, it came from here: https://github.com/symfony/console/blob/7.3/Input/InputDefinition.php#L100

Might be related to lucatume/wp-browser#779 but I didn't change anything, just haven't used Slic in a while.

I deleted all Docker Images with 'slic' in them, re-init, restart, re-installed all of slic, etc. and keep getting this error.

[lucatume]

The slic project itself does not use any Symfony components, so the error is not likely coming from it.
The linked wp-browser issue does not seem to be related.

What uses Symfony components are codeception and wp-browser. What might be happening is that there are either multiple versions os Symfony components loading (e.g. from the plugin or site under test).

Can you provide more information about the project under test, the command that you're running and the output of the codeception command using the --debug flag?

[cliffordp]

tyvm.

I don't run Codeception or WP Browser outside of Slic, and I guess Slic doesn't pass debug messages...

The project is a private plugin that I've had for years. This is most of my composer.json:

[cliffordp]

if I switch to PHP 8, I get a different error about the database even though I ran slic restart

[cliffordp]

and same db error on PHP 8.2 after changing wp-browser to v4

[cliffordp]

I ran the slic command with --verbose and got more:

And I ran it via Github Actions and got the same:

[lucatume]

Thank you for the screenshots.

The first thing I've noticed is you're running this command:

c tests/wpunit/TK_Closing_Costs/Calc/DemoJsonArrayTest. php --debug

The c alias is for vendor/bin/codecept; in the following screens you're then running the cr command, that is an alias of vendor/bin/codecept run. The reported error about the "argument with name suite already exists" is likely due to the use of the c alias in place of the cr one.

Once you run the cr alias, you run into a database connection error. This is likely due to a suite configuration issue: please check that your suite is configured correctly and that the database credentials, host and port are correct.
In a typical slic configuration the db is called test, the host is db, the port is 3306 and the password is password.
You can check the slic container configuration using the slic config command.

To further debug the databse connection issues you can open a shell in the slic container and try to connect to the database using mysql:

slic shell
> mysql -uroot -ppassword -hdb -P3306 test

[cliffordp]

tyvm!

idk why it shows c tests/... because I always only run cr tests/... ¯_(ツ)_/¯ sorry

---

yup, db is there but no tables:

---

It says WP is up to date, but the same DB error:

---

but then db is there with tables:

---

but still db error:

[lucatume]

@cliffordp thank you for providing more information. I think the issue might be the suite is configured to hit the wrong database host or the wrong database name.
If, from the slic shell command, you run the test suite, or a test method, with the --debug flags, you should see output like this one:

  [Core bootstrap] Installing...
  [Core bootstrap] Running as single site... To run multisite, use -c tests/phpunit/multisite.xml
  Activating plugins: the-events-calendar/the-events-calendar.php and switching theme(s): 
  WordPress status: {
      "rootDir": "/var/www/html/",
      "version": {
          "wpVersion": "6.7.1",
          "wpDbVersion": "58975",
          "tinymceVersion": "49110-20201110",
          "requiredPhpVersion": "7.2.24",
          "requiredMySqlVersion": "5.5.5"
      },
      "constants": {
          "DB_NAME": "test",
          "DB_USER": "root",
          "DB_PASSWORD": "password",
          "DB_HOST": "db",
          "DB_CHARSET": "utf8",
          "DB_COLLATE": "",
          "AUTH_KEY": "97115c4108730ee226ef66cd637ce9f9d91232c9",
          "SECURE_AUTH_KEY": "ed4bb96d959ec78847e79e6f6a9cebf509aebcc1",
          "LOGGED_IN_KEY": "1ca405574980460a0ccfdf08505a86849c283bcb",
          "NONCE_KEY": "1c7b3e43ad212a0c1e3ba0300ad6733eb300d6fa",
          "AUTH_SALT": "4049e7804ba1acb8a0ceb09fd0a721695804dd5d",
          "SECURE_AUTH_SALT": "62d6bbbf10b1e9223b18e3bbb20eefe6825ae143",
          "LOGGED_IN_SALT": "37c14fad0ce53174b5ddc522b00d75daa6c7e20e",
          "NONCE_SALT": "e1d95406180b054a241bf51899439591f8df357f",
          "WP_DEBUG": false,
          "WP_CACHE": true,
          "ABSPATH": "/var/www/html/"
      },
      "globals": {
          "table_prefix": "wp_",
          "configExtra": ""
      }
  }

That should tell you what database host and database name the test suite is trying to connect to. Are those correct?

[cliffordp]

I can't get that far because it doesn't connect to the db. Again, running the mysql command works even when slic is PHP 8.3. However, if I change slic from using PHP 8.3 to 7.4, I no longer get that db connection error when running a slic test.

Could it be an error within slic, wp-browser, or the docker image? Can you set Slic to use 8.3 and get it to run any test?

This works (can run tests):

	"require-dev": {
		"php": "^7.",
		"lucatume/wp-browser": "^3."
	},

This is with PHP 7.4, but my plugin requires PHP 8.3:

tk-calc-closing-costs|1.4.7⚡ ⇒ slic shell       
slic version 1.9.2 - StellarWP local testing and development tool

Using tk-calc-closing-costs

PHP 7.4.33 (cli) (built: Nov 15 2022 03:39:38) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
  c    = codecept
  cr   = codecept run
  p    = playwright
  xon  = turn xdebug on
  xoff = turn xdebug off

[slic@slic] /var/www/html/wp-content/plugins/tk-calc-closing-costs
 > cr tests/wpunit/TK_Closing_Costs/Calc/DemoJsonArrayTest.php --debug
Codeception PHP Testing Framework v4.2.2 https://helpukrainewin.org
Powered by PHPUnit 9.6.23 by Sebastian Bergmann and contributors.

  [Core bootstrap] Installing...
  [Core bootstrap] Running as single site... To run multisite, use -c tests/phpunit/multisite.xml
  Activating plugins: gravityforms/gravityforms.php, types/wpcf.php, tk-calc-closing-costs/tk-calc-closing-costs.php and switching theme(s): 
  WordPress status: {
      "rootDir": "/var/www/html/",
      "version": {
          "wpVersion": "6.8.1",
          "wpDbVersion": "58975",
          "tinymceVersion": "49110-20201110",
          "requiredPhpVersion": "7.2.24",
          "requiredMySqlVersion": "5.5.5"
      },
      "constants": {
          "DB_NAME": "test",
          "DB_USER": "root",
          "DB_PASSWORD": "password",
          "DB_HOST": "db",
          "DB_CHARSET": "utf8",
          "DB_COLLATE": "",
          "AUTH_KEY": "fcb0bd18f0f3dffb40ed57e5537a087e4f4f53d6",
          "SECURE_AUTH_KEY": "2cdb8cb8b0de028628aef4c43ddc885d081a5076",
          "LOGGED_IN_KEY": "f87ad384be08f17812dcf2ae9be6caba5d1cca5c",
          "NONCE_KEY": "0370046f17867995e3b82e9a086b92b40bcd899d",
          "AUTH_SALT": "e5d0e603e23d82e78b76fe22f49cf34c8d0bd48e",
          "SECURE_AUTH_SALT": "d32c0366626c472397ad4ec3067604115fa95fd8",
          "LOGGED_IN_SALT": "c6cf3ff26e5d1a450e3c6d8e0ab2260dbd8565a5",
          "NONCE_SALT": "7305f874cddf28ea6b8f261f8cb026e718b1d205",
          "WP_DEBUG": false,
          "ABSPATH": "/var/www/html/"
      },
      "globals": {
          "table_prefix": "wp_",
          "configExtra": ""
      }
  }
  Rebuilding WpunitTester...

TK_Ccc_Tests_Support.wpunit Tests (32) ------------------------------------------------------------------------------------------------------------
Modules: \lucatume\WPBrowser\Module\WPLoader, \TK_Ccc_Tests_Support\Helper\Wpunit

This does not work (the db connection error from prior comments):

	"require-dev": {
		"php": "^8.3",
		"lucatume/wp-browser": "^4."
	},

Here's 15min of me trying to get things working on slic PHP 8.3: https://share.zight.com/mXu4kmv6

Along the way of my testing, I noticed these issues, which might warrant their own separate tickets if you can reproduce (if you choose to try, but with all my back-and-forth testing maybe it was something I did):

1. setting SLIC_GIT_HANDLE doesn't work

2. .env.slic.local is not incorporated at all

3. does not run composer or npm install when requested as part of init
   

4. SLIC_PHP_VERSION in an env file does not take even upon slic restart but slic php-version set X.X does work

[cliffordp]

@lucatume Possibly related to #215
but I changed my composer.json's lucatume/wp-browser from ^3.* to ^4.* and no longer get this error:

An argument with name "suite" already exists.