--telemetry-url <URL VERBOSITY> ,Verbosity is configured but not taking effect in v1.18.0

[ioomie]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Description of bug

I updated the image version of my chain node on the Kubernetes cluster from parity/polkadot:v1.17.2 to the latest released Docker image: parity/polkadot:v1.18.0.

After I restarted it, my chain node encountered an error:

Starting binary polkadot  
error: invalid value 'wss://telemetry-backend.w3f.community/submit' for '--telemetry-url <URL VERBOSITY>': Verbosity level missing  

For more information, try '--help'.  

After I rolled back to version v1.17.2, it recovered and no longer showed the above error. Everything is working normally again.

Below is a part of my startup configuration:

...
spec:
  containers:
  - args:
    - --base-path=/chain-data
    - --rpc-cors=all
    - --port=29252
    - --unsafe-rpc-external
    - --validator
    - --rpc-methods=Unsafe
    - --name=OnfValidator
    - --chain=kusama
    - --db-cache=512
    - --telemetry-url=wss://telemetry-backend.w3f.community/submit 1
    - --in-peers=100
    - --in-peers-light=0
...

Steps to reproduce

All issues were reproduced in the Kubernetes environment:

1. When starting, the --telemetry-url configuration was set in version v1.18.0.2
2. After waiting for the startup, an error was reported: ERROR.
3. After rolling back to v1.17.2 with the same --telemetry-url configuration, the startup proceeded normally.

[bkchr]

I'm surprised that this ever worked for you, if you change it to:

--telemetry-url=`wss://telemetry-backend.w3f.community/submit 1`

It should also work for the latest version. Maybe the library we are using for CLI changed something internally.

[ioomie]

I'm surprised that this ever worked for you, if you change it to:

--telemetry-url=`wss://telemetry-backend.w3f.community/submit 1`

It should also work for the latest version. Maybe the library we are using for CLI changed something internally.

I configured this parameter, but it seems it is still not working properly 🫠

[ioomie]

If I use version v1.17.2 and add ``, it will also report an error, but the form of the error is different. It seems that in version v1.18.0, the number after the space is not being read.