-
Hi,
Following some tests with `picolibc` and `qemu` semi-hosting on Risc-v, I stumbled across a possible issue with command line arguments parsing from https://github.com/picolibc/picolibc/blob/695…
-
### Component(s)
processor/transform
### What happened?
## Description
The OTL func `Concat` complains that the output from a func `Split` is not `StringLIkeGetter`
## Steps to Reproduce
…
-
We only want one of `--remotes` or `--all-remotes`. We need to add these options to the argument parser.
jwir3 updated
6 years ago
-
**Describe the bug**
When providing a `*, keyword` argument in a command function definition, the library is *supposed* to make it a "greedy" argument, in that any content unconsumed goes into that v…
-
**Describe the bug**
If use a `Procfile` to declare a complex command, I would expect that the first token would be the command and the rest be arguments. This would allow me to define default beha…
-
We are using the [`uutils/coreutils`](https://github.com/uutils/coreutils) crates for some of our key file-system commands.
Their project has some core crates like `uucore` and then a series of cr…
-
Is there any way to allow passing options through without enabling positional options globally? Part of my program expects it to be disabled, and is built around that. However, one subcommand needs th…
-
When using functions combined with streaming completions, the ChatFunctionCallArgumentsSerializerAndDeserializer is used to deserialize arguments. This is broken because **quotes get stripped from the…
-
### I Have A Problem With:
A specific source
### What's Your Problem
With the new update, going to the GUI based source configuration, it appears to me that there is an issue with entering ar…
-
Implement such a functionality
```
file --narg1 val --narg2 val
````