lhenkelm

> I'm trying to figure out or remind myself if this was removed to allow for a custom `v1.0.0` to be loaded by the user and override the default `defs.json`...

> For your tests, the easiest way is to monkeypatch any part of the necessary call to `requests` or `urllib` under the hood and force it to return an exception...

@matthewfeickert having thought some more about @kratsg's concern about users overriding the default schema using the default version and id, I would like to add a bit of code to...

@matthewfeickert from my side this is ready to review. @kratsg `socket_disabled` works like a charm, thanks! If I drop the line pre-filling the cache, the test still catches the regression:...

> EDIT: a naive solution would be to add the full URI for `defs.json` in the store, in addition to the local path, and have them both point to the...

Re: backwards compatibilty, I imagine the easiest (to maintain going forward) is to bump the major version of the schema. Workspace specs know which schema version they want to be...

furthermore, it seems no matter what value I pass, the driver ignores it anyaways? I tried -1, 0, and 1, and in every case jobs were sent to the grid...

Hi, to answer the use case question: I was trying to play around with some of the other options, in particular --optGridOutputSampleName, to get an idea of how they work,...

Hi Giordon, are you sure? I have never used the ELG_prun.py script you linked above, so I don't know, but it looks like they actually use the "--noSubmit" option internally...