Roger Peppe

> To make explicit an important point touched on in the previous two comments: > > ``` > a: { > // some structure > } > b: a >...

The syntax is extremely simple. One way of describing it formally is with a regular expression. This, for example: ``` ^(.*\n)*?.*?(\n-- .+ --(\n.*)*?)*\n?$ ``` Alternatively, one could just say that...

Thanks for the report! The issue with the metaschema URL `http://json-schema.org/schema#` in particular is that its meaning changes over time, according to which version is redirected to. Currently the `jsonschema.Extract`...

> When a scheme isn't versioned would that not mean it maps to something akin to "latest"? The problem is that we can only tell that by doing an HTTP...

> @rogpeppe - I don't seem to be having the same reported issue when using cue `v0.11.0`. I know this release contained a lot of updates related to json schema....

> [@rogpeppe](https://github.com/rogpeppe) please can you confirm/summarise what the action points are here? I've created an [upstream PR](https://github.com/argoproj/argo-workflows/pull/14092) to fix the Argo schema. My hope is that they and other upstreams...

As the upstream PR has now landed, I'm presuming that this is now not an issue that needs to be solved, so closing.

I might be missing something here, but the spec does _seem_ to have [some wording](https://json-schema.org/draft/2020-12/json-schema-core#section-9.1.2-4) already on this matter: > When multiple schemas try to identify as the same URI,...

I just came across this issue in a slightly different form, with a somewhat simpler reproducer: ``` exec go mod tidy exec go run main.go ! stderr PANIC -- go.mod...

What happens if you do `exec ./anydb -f test.db set foo bar` ? That is, does it still fail if you make the current directory explicit?