-
As a regression test for #1646
-
Roger noticed that in the generated SWIG code, most converters return NULL, even if other args required cleanup. This can be fixed but \(a\) it relies on args being initialized and \(b\) it may cause…
ghost updated
7 months ago
-
# Feature Request: Default Values for Tool Arguments in GPTScript
## Summary
Add the ability to define default values for tool arguments in GPTScript. This feature will enhance the flexibility and…
-
### Preliminary checklist
- [x] I am using the latest stable version of DDEV (see [upgrade guide](https://ddev.readthedocs.io/en/stable/users/install/ddev-upgrade/))
- [x] I have searched [existing i…
-
### Android application type
.NET Android (net7.0-android, net8.0-android, etc.)
### Affected platform version
.NET 8.0.0
### Description
We have a customer using the Sentry SDK in thei…
-
Support for enum values specifying by user.
-
When I have
```justfile
run *args:
echo "$1, $2,..."
do *args: (run args)
```
How can I forward arguments properly such that $2 is `b` in `just do a b c`?
gabyx updated
3 months ago
-
### Summary
ECS should support the `--oom-kill-disable` docker flag
### Description
We have an application that uses up as much memory as it can as performance is proportional to memory…
-
**Description**
`ARG` variables of the same name as an environment variable set in a base image do not overwrite the value of the variable during build time. Is it intentional for the primary e…
-
If the command line arguments have a * (e.g. //ARGS 6 * 7), it needs to be escaped so that it isn't shell-expanded. Should one quote all arguments? What if they are quotes?