Kin Fai Tse
Kin Fai Tse
@yaacovCR There are quite some discussions, and also comments suggesting nested mutation is not supported in graphql spec https://github.com/graphql/graphql-js/issues/221 https://github.com/graphql/graphql-spec/issues/252 However, as I am aware, the graphql spec only requires...
Sorry that the request in https://github.com/graphql/graphql-spec/issues/252 might have mislead you, our case consist of only erither whole operation on `query`, or whole operation on `mutation`, however, mutations containing side-effect is...
Hi @yaacovCR, thanks for your quick reply, surely schema stitching, particularly remote schema, is kind of new ideas and deserves some discussion. There are two cases below, imo in terms...
it does in our case to throw a "mutation in query error" that, we forbids resolver intended for mutation being run in query It is a way to require developers...
https://github.com/LLNL/maestrowf/blob/06fd2f2b50611310c09492e9a4497115d33c04e2/maestrowf/interfaces/script/slurmscriptadapter.py#L122-L134 https://github.com/LLNL/maestrowf/blob/06fd2f2b50611310c09492e9a4497115d33c04e2/maestrowf/interfaces/script/slurmscriptadapter.py#L154-L155 I am not sure why `procs_in_batch` only considered from `self._batch` setting but not current `step.run.procs`, it is quite unintuitive that if - `nodes` was set in step -...
The closest thing now seem to be 1. Deploy `AWS::RDS::DBCluster` with `EngineMode: provision` 2. Run `aws rds modify-db-cluster --serverless-v2-scaling-configuration '{"MinCapacity":0.5,"MaxCapacity":128}' --db-cluster-identifier `, if you have not find this config, update...
Had a discussion with support and heard this wasn't fixed yet. ``` Resources: MyResource Properties: SomeProperty: !Sub "{{resolve:ssm:${SomeParameterOrValue}}}" ``` Had a workaround, plug a random source (e.g. timestamp) into metadata...
I thought it should be a simple fix in change set creation, like when the syntax is `"{{resolve:ssm:...}}"` / `!Sub "{{resolve:ssm:...}}"` / anything evaluated to `"{{resolve:ssm:...}}"`, assume there will be...
I think this issue also deserve attention. `IS_SET` or `IS_NOT_SET` seem to make more sense in all compatibility, implementation and usability aspect, for - compatibility: in all previous version, values...
was looking for solution and found this could be done overriding the spec https://github.com/aws-cloudformation/cfn-lint/blob/main/docs/customize_specifications.md#customize-specifications Had an example making Tags mandatory. Edit: Attach another example I can constraining lambda launch condition...