Use "wasmer --version --verbose" in the issue template

[Michael-F-Bryan]

Description

Now that the wasmer CLI can show more verbose version information (#3215), we should ask people to use it when creating tickets.

Before:

$ echo "`wasmer -V` | `rustc -V` | `uname -m`"
wasmer 3.0.2 | rustc 1.63.0 (4b91a6ea7 2022-08-08) | x86_64

After:

$ wasmer -vV; rustc -vV
wasmer 3.0.2 (5287c 2022-11-27)
binary: wasmer-cli
commit-hash: 5287c4f1253f66f428066d35eef0825fe827cff3
commit-date: 2022-11-27
host: x86_64-unknown-linux-gnu
compiler: singlepass,cranelift,llvm
rustc 1.63.0 (4b91a6ea7 2022-08-08)
binary: rustc
commit-hash: 4b91a6ea7258a947e59c6522cd5898e7c0a6a88f
commit-date: 2022-08-08
host: x86_64-unknown-linux-gnu
release: 1.63.0
LLVM version: 14.0.5

Fixes #3412.

[ptitSeb]

so no more uname?
a uname -a would be interesting.
(Also, side ote, this doesn't work for Windows OS., but it has never worked...)

[Michael-F-Bryan]

@ptitSeb, I removed the uname -m because it just prints x86_64, which is already covered in the host: x86_64-unknown-linux-gnu printed by rustc and wasmer.

That's a good point about platform compatibility, though. Powershell supports &&, so wasmer -Vv && rustc -Vv will work, but cmd.exe will error out with a syntax error.

[ptitSeb]

I tried on Windows.
On Powershell:

PS L:\git\wasmvm> wasmer -vV && rustc -vV
Au caractère Ligne:1 : 12
+ wasmer -vV && rustc -vV
+            ~~
Le jeton « && » n’est pas un séparateur d’instruction valide.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidEndOfLine

PS L:\git\wasmvm> wasmer -vV ; rustc -vV
wasmer 3.0.0-rc.2 (33da4 2022-11-04)
binary: wasmer-cli
commit-hash: 33da46f94ba6cc18f817428fc751ef25772cf5a5
commit-date: 2022-11-04
host: x86_64-pc-windows-msvc
compiler: singlepass,cranelift,llvm
rustc 1.64.0-nightly (27eb6d701 2022-07-04)
binary: rustc
commit-hash: 27eb6d7018e397cf98d51c205e3576951d766323
commit-date: 2022-07-04
host: x86_64-pc-windows-msvc
release: 1.64.0-nightly
LLVM version: 14.0.6

On CMD.exe

L:\git\wasmvm>wasmer -vV; rustc -vV
error: Found argument '-v' which wasn't expected, or isn't valid in this context

        If you tried to supply `-v` as a value rather than a flag, use `-- -v`

USAGE:
    wasmer [OPTIONS] <FILE> [ARGS]...

For more information try --help

L:\git\wasmvm>wasmer -vV ; rustc -vV
wasmer 3.0.0-rc.2 (33da4 2022-11-04)
binary: wasmer-cli
commit-hash: 33da46f94ba6cc18f817428fc751ef25772cf5a5
commit-date: 2022-11-04
host: x86_64-pc-windows-msvc
compiler: singlepass,cranelift,llvm

L:\git\wasmvm>wasmer -vV : rustc -vV
wasmer 3.0.0-rc.2 (33da4 2022-11-04)
binary: wasmer-cli
commit-hash: 33da46f94ba6cc18f817428fc751ef25772cf5a5
commit-date: 2022-11-04
host: x86_64-pc-windows-msvc
compiler: singlepass,cranelift,llvm

L:\git\wasmvm>wasmer -vV && rustc -vV
wasmer 3.0.0-rc.2 (33da4 2022-11-04)
binary: wasmer-cli
commit-hash: 33da46f94ba6cc18f817428fc751ef25772cf5a5
commit-date: 2022-11-04
host: x86_64-pc-windows-msvc
compiler: singlepass,cranelift,llvm
rustc 1.64.0-nightly (27eb6d701 2022-07-04)
binary: rustc
commit-hash: 27eb6d7018e397cf98d51c205e3576951d766323
commit-date: 2022-07-04
host: x86_64-pc-windows-msvc
release: 1.64.0-nightly
LLVM version: 14.0.6

I don't think there is an universal solution here :(

[Michael-F-Bryan]

@ptitSeb, this error message is very surprising:

$ wasmer -vV; rustc -vV
error: Found argument '-v' which wasn't expected, or isn't valid in this context

        If you tried to supply `-v` as a value rather than a flag, use `-- -v`

USAGE:
    wasmer [OPTIONS] <FILE> [ARGS]...

For more information try --help

It's almost like Windows does something different with command-line arguments, so wasmer doesn't recognise the -v flag as valid 🤔

[ptitSeb]

It's because of the lack of space between V and ;... Windows CMD parser is .. crude...