that actually comes up in the real world. We want to hear the real-world use case so the
        community can discuss and debate whether this feature is actually the *best* way to address
        the real use case, or whether or not a different abstraction might be more appropriate.


        It's okay if you can't provide complete context on a use case. We understand if you are not

    matchExpressions:
    - key: sidecar.istio.io/inject
      operator: NotIn
      values:
      - "false"
    - key: istio.io/rev
      operator: In
      values:
      - "default"

{{- /* Case 1: Namespace selector enabled, and object selector is not injected */}}
{{- include "core" (mergeOverwrite (deepCopy $whv) (dict "Prefix" "namespace.") ) }}
  namespaceSelector:
    matchExpressions:
    - key: istio-injection

    validations:
      required: true
  - type: input
    id: gradle-old-version
    attributes:
      label: Gradle version that used to work
      description: What version of Gradle gives proper result for your case?
    validations:
      required: true
  - type: input
    id: build-scan-url
    attributes:
      label: Build scan URL (optional)
      description: |

    validations:
      required: true
  - type: textarea
    id: code-to-reproduce
    attributes:
      label: Standalone code to reproduce the issue
      description: Provide a reproducible test case that is the bare minimum necessary to generate the problem. Please share a link to Colab, Jupyter, or any notebook.
      placeholder: Tell us what you see!
      value:
      render: shell
    validations:

		[size_is(count)] ShareInfo502 *array;
	} ShareInfoCtr502;

	typedef [switch_type(int)] union {
		[case(0)] ShareInfo0 *info0;
		[case(1)] ShareInfo1 *info1;
		[case(502)] ShareInfo502 *info1;
	} ShareInfo;

	typedef [switch_type(int)] union {
		[case(0)] ShareInfoCtr0 *info0;
		[case(1)] ShareInfoCtr1 *info1;
		[case(502)] ShareInfoCtr502 *info1;
	} ShareCtr;

	[op(0x0f)]

        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually
        the *best* way to address the real use case, or whether or not a different approach might be
        more appropriate.


        It's okay if you can't provide complete context on a use case. We understand if you are not

		[size_is(count)] ShareInfo502 *array;
	} ShareInfoCtr502;

	typedef [switch_type(int)] union {
		[case(0)] ShareInfo0 *info0;
		[case(1)] ShareInfo1 *info1;
		[case(502)] ShareInfo502 *info1;
	} ShareInfo;

	typedef [switch_type(int)] union {
		[case(0)] ShareInfoCtr0 *info0;
		[case(1)] ShareInfoCtr1 *info1;
		[case(502)] ShareInfoCtr502 *info1;
	} ShareCtr;

	[op(0x0f)]

            switch(domain) {
            case "intel.com":
              console.log(await script.filter({github, context, domain}));
              break;
            case "apple.com":
              console.log(await script.filter({github, context, domain}));
              break;
            case "nvidia.com":
              console.log(await script.filter({github, context, domain}));

	AMOMAXUD	X5, (X6), X7			// af3353e6
	AMOMINW		X5, (X6), X7			// af235386
	AMOMIND		X5, (X6), X7			// af335386
	AMOMINUW	X5, (X6), X7			// af2353c6
	AMOMINUD	X5, (X6), X7			// af3353c6

	// 10.1: Base Counters and Timers
	RDCYCLE		X5				// f32200c0
	RDTIME		X5				// f32210c0
	RDINSTRET	X5				// f32220c0

	// 11.5: Single-Precision Load and Store Instructions
	FLW	(X5), F0				// 07a00200

	} DfsInfo300;

	typedef struct {
		uint32_t count;
		[size_is(count)] DfsInfo300 *s;
	} DfsEnumArray300;

	typedef union {
		[case(1)] DfsEnumArray1 *info1;
		[case(3)] DfsEnumArray3 *info3;
		[case(200)] DfsEnumArray200 *info200;
		[case(300)] DfsEnumArray300 *info300;
	} DfsEnumInfo;

	typedef struct {
		uint32_t level,
		[switch_is(level)] DfsEnumInfo e;
	} DfsEnumStruct;

	[op(0x15)]