jade
The use case I want a trace function for personally is the case when I have a bad error message from putting e.g. a dictionary into an argument of `table()`....
FYI to anyone using awscli, you want env-vars AWS_REQUEST_CHECKSUM_CALCULATION and AWS_RESPONSE_CHECKSUM_VALIDATION both set to `when_required`: https://docs.aws.amazon.com/cli/v1/userguide/cli-configure-envvars.html#envvars-list-AWS_REQUEST_CHECKSUM_CALCULATION
Regarding third party tools in jj.toml, that ship has already sailed and i don't think that feature is removable: for example, it is possible to read config variables in templates...
well, stale bot, you know why it's not received any activity? because the maintainers are doing something else, as is their right to do, and which i do not whatsoever...
i hate stale bots i hate stale bots i hate stale bots i hate stale bots
Unfortunate to hear. I am probably not going to fix this myself, but PRs are welcome!
this fixes #1029, please add a note in the commit message :)
In principle. There was a regression in #67 due to an old Nix bug that seems to be fixed in 2.24 at least in which builtins.fetchTree is visible but throws...
I have absolutely no idea why this doesn't work for you. Does https://git.lix.systems/lix-project/flake-compat work for you?