Context Variable Name does not appear to be Recognized

So the UI keeps giving me this error:
ServerError: Variable currentMappingHostValues is not defined in the context
When the context has the variable name defined...   it doesn't seem to be interpreting it correctly.
With a policy like:
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: require-unique-mapping-host-name
spec:
  background: false
  validationFailureAction: Enforce
  rules:
  - name: require-unique-mapping-host-name
    match:
      any:
      - resources:
          kinds:
          - Mapping
    context:
      - name: currentMappingHostValues
        apiCall:
          urlPath: "/apis/getambassador.io/v2/mappings"
          # Gets host values of all mappings
          jmesPath: items[].spec.{host:host,prefix:prefix}.values(@) | [*].join('',[])
    preconditions:
      all:
      - key: "{{ request.operation || 'BACKGROUND' }}"
        operator: NotEquals
        value: DELETE
    validate:
      message: "Only unique hostnames are allowed"
      deny:
        conditions:
        # this checks for any existing mapped hosts that match
          all:
          - key: "{{ request.object.spec.host }}{{ request.object.spec.prefix }}"
            operator: AnyIn
            value: "{{ currentMappingHostValues}}"

And a resource like:
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: anchore-tst
  namespace: anchore
spec:
  allow_upgrade:
  - websocket
  bypass_auth: true
  host: anchore.appz.abc.com
  merge_slashes: true
  prefix: /
  service: anchore-anchore-engine-enterprise-ui:80

And a generic ambassador mappings CRD like:
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  annotations:
    controller-gen.kubebuilder.io/version: v0.6.2
    meta.helm.sh/release-name: emissary-ingress-crds
    meta.helm.sh/release-namespace: default
  generation: 3
  labels:
    app.kubernetes.io/instance: emissary-apiext
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: emissary-apiext
    app.kubernetes.io/part-of: emissary-apiext
  name: mappings.getambassador.io
spec:
  group: getambassador.io
  names:
    categories:
    - ambassador-crds
    kind: Mapping
    listKind: MappingList
    plural: mappings
    singular: mapping
  scope: Namespaced
  versions:
  - additionalPrinterColumns:
    - jsonPath: .spec.host
      name: Source Host
      type: string
    - jsonPath: .spec.prefix
      name: Source Prefix
      type: string
    - jsonPath: .spec.service
      name: Dest Service
      type: string
    - jsonPath: .status.state
      name: State
      type: string
    - jsonPath: .status.reason
      name: Reason
      type: string
    name: v2
    schema:
      openAPIV3Schema:
        description: Mapping is the Schema for the mappings API
        properties:
          apiVersion:
            description: 'APIVersion defines the versioned schema of this representation
              of an object. Servers should convert recognized schemas to the latest
              internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
            type: string
          kind:
            description: 'Kind is a string value representing the REST resource this
              object represents. Servers may infer this from the endpoint the client
              submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
            type: string
          metadata:
            type: object
          spec:
            description: MappingSpec defines the desired state of Mapping
            properties:
              add_linkerd_headers:
                type: boolean
              add_request_headers:
                type: object
                x-kubernetes-preserve-unknown-fields: true
              add_response_headers:
                type: object
                x-kubernetes-preserve-unknown-fields: true
              allow_upgrade:
                description: "A case-insensitive list of the non-HTTP protocols to
                  allow \"upgrading\" to from HTTP via the \"Connection: upgrade\"
                  mechanism[1].  After the upgrade, Ambassador does not interpret
                  the traffic, and behaves similarly to how it does for TCPMappings.
                  \n [1]: https://tools.ietf.org/html/rfc7230#section-6.7 \n For example,
                  if your upstream service supports WebSockets, you would write \n
                  \   allow_upgrade:    - websocket \n Or if your upstream service
                  supports upgrading from HTTP to SPDY (as the Kubernetes apiserver
                  does for `kubectl exec` functionality), you would write \n    allow_upgrade:
                  \   - spdy/3.1"
                items:
                  type: string
                type: array
              auth_context_extensions:
                additionalProperties:
                  type: string
                type: object
              auto_host_rewrite:
                type: boolean
              bypass_auth:
                type: boolean
              bypass_error_response_overrides:
                description: If true, bypasses any `error_response_overrides` set
                  on the Ambassador module.
                type: boolean
              case_sensitive:
                type: boolean
              circuit_breakers:
                items:
                  properties:
                    max_connections:
                      type: integer
                    max_pending_requests:
                      type: integer
                    max_requests:
                      type: integer
                    max_retries:
                      type: integer
                    priority:
                      enum:
                      - default
                      - high
                      type: string
                  type: object
                type: array
              cluster_idle_timeout_ms:
                type: integer
              cluster_max_connection_lifetime_ms:
                type: integer
              cluster_tag:
                type: string
              connect_timeout_ms:
                type: integer
              cors:
                properties:
                  credentials:
                    type: boolean
                  max_age:
                    type: string
                type: object
                x-kubernetes-preserve-unknown-fields: true
              dns_type:
                type: string
              docs:
                description: DocsInfo provides some extra information about the docs
                  for the Mapping (used by the Dev Portal)
                properties:
                  display_name:
                    type: string
                  ignored:
                    type: boolean
                  path:
                    type: string
                  timeout_ms:
                    type: integer
                  url:
                    type: string
                type: object
              enable_ipv4:
                type: boolean
              enable_ipv6:
                type: boolean
              envoy_override:
                description: UntypedDict is relatively opaque as a Go type, but it
                  preserves its contents in a roundtrippable way.
                type: object
                x-kubernetes-preserve-unknown-fields: true
              error_response_overrides:
                description: Error response overrides for this Mapping. Replaces all
                  of the `error_response_overrides` set on the Ambassador module,
                  if any.
                items:
                  description: A response rewrite for an HTTP error response
                  properties:
                    body:
                      description: The new response body
                      properties:
                        content_type:
                          description: The content type to set on the error response
                            body when using text_format or text_format_source. Defaults
                            to 'text/plain'.
                          type: string
                        json_format:
                          additionalProperties:
                            type: string
                          description: 'A JSON response with content-type: application/json.
                            The values can contain format text like in text_format.'
                          type: object
                        text_format:
                          description: A format string representing a text response
                            body. Content-Type can be set using the `content_type`
                            field below.
                          type: string
                        text_format_source:
                          description: A format string sourced from a file on the
                            Ambassador container. Useful for larger response bodies
                            that should not be placed inline in configuration.
                          properties:
                            filename:
                              description: The name of a file on the Ambassador pod
                                that contains a format text string.
                              type: string
                          type: object
                      type: object
                    on_status_code:
                      description: The status code to match on -- not a pointer because
                        it's required.
                      maximum: 599
                      minimum: 400
                      type: integer
                  required:
                  - body
                  - on_status_code
                  type: object
                minItems: 1
                type: array
              grpc:
                type: boolean
              headers:
                type: object
                x-kubernetes-preserve-unknown-fields: true
              host:
                type: string
              host_redirect:
                type: boolean
              host_regex:
                type: boolean
              host_rewrite:
                type: string
              idle_timeout_ms:
                type: integer
              keepalive:
                properties:
                  idle_time:
                    type: integer
                  interval:
                    type: integer
                  probes:
                    type: integer
                type: object
              labels:
                additionalProperties:
                  description: A MappingLabelGroupsArray is an array of MappingLabelGroups.
                    I know, complex.
                  items:
                    description: 'A MappingLabelGroup is a single element of a MappingLabelGroupsArray:
                      a second map, where the key is a human-readable name that identifies
                      the group.'
                    maxProperties: 1
                    minProperties: 1
                    type: object
                    x-kubernetes-preserve-unknown-fields: true
                  type: array
                description: A DomainMap is the overall Mapping.spec.Labels type.
                  It maps domains (kind of like namespaces for Mapping labels) to
                  arrays of label groups.
                type: object
              load_balancer:
                properties:
                  cookie:
                    properties:
                      name:
                        type: string
                      path:
                        type: string
                      ttl:
                        type: string
                    required:
                    - name
                    type: object
                  header:
                    type: string
                  policy:
                    enum:
                    - round_robin
                    - ring_hash
                    - maglev
                    - least_request
                    type: string
                  source_ip:
                    type: boolean
                required:
                - policy
                type: object
              method:
                type: string
              method_regex:
                type: boolean
              modules:
                items:
                  description: UntypedDict is relatively opaque as a Go type, but
                    it preserves its contents in a roundtrippable way.
                  type: object
                  x-kubernetes-preserve-unknown-fields: true
                type: array
              outlier_detection:
                type: string
              path_redirect:
                description: Path replacement to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                type: string
              precedence:
                type: integer
              prefix:
                type: string
              prefix_exact:
                type: boolean
              prefix_redirect:
                description: Prefix rewrite to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                type: string
              prefix_regex:
                type: boolean
              priority:
                type: string
              query_parameters:
                type: object
                x-kubernetes-preserve-unknown-fields: true
              redirect_response_code:
                description: The response code to use when generating an HTTP redirect.
                  Defaults to 301. Used with `host_redirect`.
                enum:
                - 301
                - 302
                - 303
                - 307
                - 308
                type: integer
              regex_headers:
                additionalProperties:
                  type: string
                type: object
              regex_query_parameters:
                additionalProperties:
                  type: string
                type: object
              regex_redirect:
                description: Prefix regex rewrite to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                properties:
                  pattern:
                    type: string
                  substitution:
                    type: string
                type: object
              regex_rewrite:
                properties:
                  pattern:
                    type: string
                  substitution:
                    type: string
                type: object
              resolver:
                type: string
              respect_dns_ttl:
                type: boolean
              retry_policy:
                properties:
                  num_retries:
                    type: integer
                  per_try_timeout:
                    type: string
                  retry_on:
                    enum:
                    - 5xx
                    - gateway-error
                    - connect-failure
                    - retriable-4xx
                    - refused-stream
                    - retriable-status-codes
                    type: string
                type: object
              rewrite:
                type: string
              service:
                type: string
              shadow:
                type: boolean
              timeout_ms:
                description: The timeout for requests that use this Mapping. Overrides
                  `cluster_request_timeout_ms` set on the Ambassador Module, if it
                  exists.
                type: integer
              use_websocket:
                description: 'use_websocket is deprecated, and is equivlaent to setting
                  `allow_upgrade: ["websocket"]`'
                type: boolean
              v3StatsName:
                type: string
              weight:
                type: integer
            required:
            - prefix
            - service
            type: object
            x-kubernetes-preserve-unknown-fields: true
          status:
            description: MappingStatus defines the observed state of Mapping
            properties:
              reason:
                type: string
              state:
                enum:
                - ""
                - Inactive
                - Running
                type: string
            type: object
        type: object
    served: true
    storage: true
    subresources:
      status: {}
  - additionalPrinterColumns:
    - jsonPath: .spec.host
      name: Source Host
      type: string
    - jsonPath: .spec.prefix
      name: Source Prefix
      type: string
    - jsonPath: .spec.service
      name: Dest Service
      type: string
    - jsonPath: .status.state
      name: State
      type: string
    - jsonPath: .status.reason
      name: Reason
      type: string
    name: v3alpha1
    schema:
      openAPIV3Schema:
        description: Mapping is the Schema for the mappings API
        properties:
          apiVersion:
            description: 'APIVersion defines the versioned schema of this representation
              of an object. Servers should convert recognized schemas to the latest
              internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
            type: string
          kind:
            description: 'Kind is a string value representing the REST resource this
              object represents. Servers may infer this from the endpoint the client
              submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
            type: string
          metadata:
            type: object
          spec:
            description: MappingSpec defines the desired state of Mapping
            properties:
              add_linkerd_headers:
                type: boolean
              add_request_headers:
                additionalProperties:
                  properties:
                    append:
                      type: boolean
                    v2Representation:
                      enum:
                      - ""
                      - string
                      - "null"
                      type: string
                    value:
                      type: string
                  type: object
                type: object
              add_response_headers:
                additionalProperties:
                  properties:
                    append:
                      type: boolean
                    v2Representation:
                      enum:
                      - ""
                      - string
                      - "null"
                      type: string
                    value:
                      type: string
                  type: object
                type: object
              allow_upgrade:
                description: "A case-insensitive list of the non-HTTP protocols to
                  allow \"upgrading\" to from HTTP via the \"Connection: upgrade\"
                  mechanism[1].  After the upgrade, Ambassador does not interpret
                  the traffic, and behaves similarly to how it does for TCPMappings.
                  \n [1]: https://tools.ietf.org/html/rfc7230#section-6.7 \n For example,
                  if your upstream service supports WebSockets, you would write \n
                  \   allow_upgrade:    - websocket \n Or if your upstream service
                  supports upgrading from HTTP to SPDY (as the Kubernetes apiserver
                  does for `kubectl exec` functionality), you would write \n    allow_upgrade:
                  \   - spdy/3.1"
                items:
                  type: string
                type: array
              ambassador_id:
                description: "AmbassadorID declares which Ambassador instances should
                  pay attention to this resource. If no value is provided, the default
                  is: \n    ambassador_id:    - \"default\" \n TODO(lukeshu): In v3alpha2,
                  consider renaming all of the `ambassador_id` (singular) fields to
                  `ambassador_ids` (plural)."
                items:
                  type: string
                type: array
              auth_context_extensions:
                additionalProperties:
                  type: string
                type: object
              auto_host_rewrite:
                type: boolean
              bypass_auth:
                type: boolean
              bypass_error_response_overrides:
                description: If true, bypasses any `error_response_overrides` set
                  on the Ambassador module.
                type: boolean
              case_sensitive:
                type: boolean
              circuit_breakers:
                items:
                  properties:
                    max_connections:
                      type: integer
                    max_pending_requests:
                      type: integer
                    max_requests:
                      type: integer
                    max_retries:
                      type: integer
                    priority:
                      enum:
                      - default
                      - high
                      type: string
                  type: object
                type: array
              cluster_idle_timeout_ms:
                description: 'TODO(lukeshu): In v3alpha2, change all of the `{foo}_ms`/`MillisecondDuration`
                  fields to `{foo}`/`metav1.Duration`.'
                type: integer
              cluster_max_connection_lifetime_ms:
                description: 'TODO(lukeshu): In v3alpha2, change all of the `{foo}_ms`/`MillisecondDuration`
                  fields to `{foo}`/`metav1.Duration`.'
                type: integer
              cluster_tag:
                type: string
              connect_timeout_ms:
                description: 'TODO(lukeshu): In v3alpha2, change all of the `{foo}_ms`/`MillisecondDuration`
                  fields to `{foo}`/`metav1.Duration`.'
                type: integer
              cors:
                properties:
                  credentials:
                    type: boolean
                  exposed_headers:
                    items:
                      type: string
                    type: array
                  headers:
                    items:
                      type: string
                    type: array
                  max_age:
                    type: string
                  methods:
                    items:
                      type: string
                    type: array
                  origins:
                    items:
                      type: string
                    type: array
                  v2CommaSeparatedOrigins:
                    type: boolean
                type: object
              dns_type:
                type: string
              docs:
                description: DocsInfo provides some extra information about the docs
                  for the Mapping. Docs is used by both the agent and the DevPortal.
                properties:
                  display_name:
                    type: string
                  ignored:
                    type: boolean
                  path:
                    type: string
                  timeout_ms:
                    description: 'TODO(lukeshu): In v3alpha2, change all of the `{foo}_ms`/`MillisecondDuration`
                      fields to `{foo}`/`metav1.Duration`.'
                    type: integer
                  url:
                    type: string
                type: object
              enable_ipv4:
                type: boolean
              enable_ipv6:
                type: boolean
              envoy_override:
                description: UntypedDict is relatively opaque as a Go type, but it
                  preserves its contents in a roundtrippable way.
                type: object
                x-kubernetes-preserve-unknown-fields: true
              error_response_overrides:
                description: Error response overrides for this Mapping. Replaces all
                  of the `error_response_overrides` set on the Ambassador module,
                  if any.
                items:
                  description: A response rewrite for an HTTP error response
                  properties:
                    body:
                      description: The new response body
                      properties:
                        content_type:
                          description: The content type to set on the error response
                            body when using text_format or text_format_source. Defaults
                            to 'text/plain'.
                          type: string
                        json_format:
                          additionalProperties:
                            type: string
                          description: 'A JSON response with content-type: application/json.
                            The values can contain format text like in text_format.'
                          type: object
                        text_format:
                          description: A format string representing a text response
                            body. Content-Type can be set using the `content_type`
                            field below.
                          type: string
                        text_format_source:
                          description: A format string sourced from a file on the
                            Ambassador container. Useful for larger response bodies
                            that should not be placed inline in configuration.
                          properties:
                            filename:
                              description: The name of a file on the Ambassador pod
                                that contains a format text string.
                              type: string
                          type: object
                      type: object
                    on_status_code:
                      description: The status code to match on -- not a pointer because
                        it's required.
                      maximum: 599
                      minimum: 400
                      type: integer
                  required:
                  - body
                  - on_status_code
                  type: object
                minItems: 1
                type: array
              grpc:
                type: boolean
              headers:
                additionalProperties:
                  type: string
                type: object
              host:
                description: "Exact match for the hostname of a request if HostRegex
                  is false; regex match for the hostname if HostRegex is true. \n
                  Host specifies both a match for the ':authority' header of a request,
                  as well as a match criterion for Host CRDs: a Mapping that specifies
                  Host will not associate with a Host that doesn't have a matching
                  Hostname. \n If both Host and Hostname are set, an error is logged,
                  Host is ignored, and Hostname is used. \n DEPRECATED: Host is either
                  an exact match or a regex, depending on HostRegex. Use HostName
                  instead. \n TODO(lukeshu): In v3alpha2, get rid of MappingSpec.host
                  and MappingSpec.host_regex in favor of a MappingSpec.deprecated_hostname_regex."
                type: string
              host_redirect:
                type: boolean
              host_regex:
                description: "DEPRECATED: Host is either an exact match or a regex,
                  depending on HostRegex. Use HostName instead. \n TODO(lukeshu):
                  In v3alpha2, get rid of MappingSpec.host and MappingSpec.host_regex
                  in favor of a MappingSpec.deprecated_hostname_regex."
                type: boolean
              host_rewrite:
                type: string
              hostname:
                description: "Hostname is a DNS glob specifying the hosts to which
                  this Mapping applies. \n Hostname specifies both a match for the
                  ':authority' header of a request, as well as a match criterion for
                  Host CRDs: a Mapping that specifies Hostname will not associate
                  with a Host that doesn't have a matching Hostname. \n If both Host
                  and Hostname are set, an error is logged, Host is ignored, and Hostname
                  is used."
                type: string
              idle_timeout_ms:
                description: 'TODO(lukeshu): In v3alpha2, change all of the `{foo}_ms`/`MillisecondDuration`
                  fields to `{foo}`/`metav1.Duration`.'
                type: integer
              keepalive:
                properties:
                  idle_time:
                    type: integer
                  interval:
                    type: integer
                  probes:
                    type: integer
                type: object
              labels:
                additionalProperties:
                  description: A MappingLabelGroupsArray is an array of MappingLabelGroups.
                    I know, complex.
                  items:
                    additionalProperties:
                      description: 'A MappingLabelsArray is the value in the MappingLabelGroup:
                        an array of label specifiers.'
                      items:
                        description: "A MappingLabelSpecifier (finally!) defines a
                          single label. \n This mimics envoy/config/route/v3/route_components.proto:RateLimit:Action:action_specifier."
                        maxProperties: 1
                        minProperties: 1
                        properties:
                          destination_cluster:
                            description: Sets the label "destination_cluster=«Envoy
                              destination cluster name»".
                            properties:
                              key:
                                enum:
                                - destination_cluster
                                type: string
                            required:
                            - key
                            type: object
                          generic_key:
                            description: Sets the label "«key»=«value»" (where by
                              default «key» is "generic_key").
                            properties:
                              key:
                                description: The default is "generic_key".
                                type: string
                              v2Shorthand:
                                type: boolean
                              value:
                                type: string
                            required:
                            - value
                            type: object
                          remote_address:
                            description: Sets the label "remote_address=«IP address
                              of the client»".
                            properties:
                              key:
                                enum:
                                - remote_address
                                type: string
                            required:
                            - key
                            type: object
                          request_headers:
                            description: If the «header_name» header is set, then
                              set the label "«key»=«Value of the «header_name» header»";
                              otherwise skip applying this label group.
                            properties:
                              header_name:
                                type: string
                              key:
                                type: string
                              omit_if_not_present:
                                type: boolean
                            required:
                            - header_name
                            - key
                            type: object
                          source_cluster:
                            description: Sets the label "source_cluster=«Envoy source
                              cluster name»".
                            properties:
                              key:
                                enum:
                                - source_cluster
                                type: string
                            required:
                            - key
                            type: object
                        type: object
                      type: array
                    description: 'A MappingLabelGroup is a single element of a MappingLabelGroupsArray:
                      a second map, where the key is a human-readable name that identifies
                      the group.'
                    maxProperties: 1
                    minProperties: 1
                    type: object
                  type: array
                description: A DomainMap is the overall Mapping.spec.Labels type.
                  It maps domains (kind of like namespaces for Mapping labels) to
                  arrays of label groups.
                type: object
              load_balancer:
                properties:
                  cookie:
                    properties:
                      name:
                        type: string
                      path:
                        type: string
                      ttl:
                        type: string
                    required:
                    - name
                    type: object
                  header:
                    type: string
                  policy:
                    enum:
                    - round_robin
                    - ring_hash
                    - maglev
                    - least_request
                    type: string
                  source_ip:
                    type: boolean
                required:
                - policy
                type: object
              method:
                type: string
              method_regex:
                type: boolean
              modules:
                items:
                  description: UntypedDict is relatively opaque as a Go type, but
                    it preserves its contents in a roundtrippable way.
                  type: object
                  x-kubernetes-preserve-unknown-fields: true
                type: array
              outlier_detection:
                type: string
              path_redirect:
                description: Path replacement to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                type: string
              precedence:
                type: integer
              prefix:
                type: string
              prefix_exact:
                type: boolean
              prefix_redirect:
                description: Prefix rewrite to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                type: string
              prefix_regex:
                type: boolean
              priority:
                type: string
              query_parameters:
                additionalProperties:
                  type: string
                type: object
              redirect_response_code:
                description: The response code to use when generating an HTTP redirect.
                  Defaults to 301. Used with `host_redirect`.
                enum:
                - 301
                - 302
                - 303
                - 307
                - 308
                type: integer
              regex_headers:
                additionalProperties:
                  type: string
                type: object
              regex_query_parameters:
                additionalProperties:
                  type: string
                type: object
              regex_redirect:
                description: Prefix regex rewrite to use when generating an HTTP redirect.
                  Used with `host_redirect`.
                properties:
                  pattern:
                    type: string
                  substitution:
                    type: string
                type: object
              regex_rewrite:
                properties:
                  pattern:
                    type: string
                  substitution:
                    type: string
                type: object
              remove_request_headers:
                items:
                  type: string
                type: array
              remove_response_headers:
                items:
                  type: string
                type: array
              resolver:
                type: string
              respect_dns_ttl:
                type: boolean
              retry_policy:
                properties:
                  num_retries:
                    type: integer
                  per_try_timeout:
                    type: string
                  retry_on:
                    enum:
                    - 5xx
                    - gateway-error
                    - connect-failure
                    - retriable-4xx
                    - refused-stream
                    - retriable-status-codes
                    type: string
                type: object
              rewrite:
                type: string
              service:
                type: string
              shadow:
                type: boolean
              stats_name:
                type: string
              timeout_ms:
                description: The timeout for requests that use this Mapping. Overrides
                  `cluster_request_timeout_ms` set on the Ambassador Module, if it
                  exists.
                type: integer
              tls:
                type: string
              use_websocket:
                description: "use_websocket is deprecated, and is equivlaent to setting
                  `allow_upgrade: [\"websocket\"]` \n TODO(lukeshu): In v3alpha2,
                  get rid of MappingSpec.DeprecatedUseWebsocket."
                type: boolean
              v2BoolHeaders:
                items:
                  type: string
                type: array
              v2BoolQueryParameters:
                items:
                  type: string
                type: array
              v2ExplicitTLS:
                description: V2ExplicitTLS controls some vanity/stylistic elements
                  when converting from v3alpha1 to v2.  The values in an V2ExplicitTLS
                  should not in any way affect the runtime operation of Emissary;
                  except that it may affect internal names in the Envoy config, which
                  may in turn affect stats names.  But it should not affect any end-user
                  observable behavior.
                properties:
                  serviceScheme:
                    description: "ServiceScheme specifies how to spell and capitalize
                      the scheme-part of the service URL. \n Acceptable values are
                      \"http://\" (case-insensitive), \"https://\" (case-insensitive),
                      or \"\".  The value is used if it agrees with whether or not
                      this resource enables TLS origination, or if something else
                      in the resource overrides the scheme."
                    pattern: ^([hH][tT][tT][pP][sS]?://)?$
                    type: string
                  tls:
                    description: "TLS controls whether and how to represent the \"tls\"
                      field when its value could be implied by the \"service\" field.
                      \ In v2, there were a lot of different ways to spell an \"empty\"
                      value, and this field specifies which way to spell it (and will
                      therefore only be used if the value will indeed be empty). \n
                      \ | Value        | Representation                        | Meaning
                      of representation          |  |--------------+---------------------------------------+------------------------------------|
                      \ | \"\"           | omit the field                        |
                      defer to service (no TLSContext)   |  | \"null\"       | store
                      an explicit \"null\" in the field | defer to service (no TLSContext)
                      \  |  | \"string\"     | store an empty string in the field
                      \   | defer to service (no TLSContext)   |  | \"bool:false\"
                      | store a Boolean \"false\" in the field  | defer to service
                      (no TLSContext)   |  | \"bool:true\"  | store a Boolean \"true\"
                      in the field   | originate TLS (no TLSContext)      | \n If
                      the meaning of the representation contradicts anything else
                      (if a TLSContext is to be used, or in the case of \"bool:true\"
                      if TLS is not to be originated), then this field is ignored."
                    enum:
                    - ""
                    - "null"
                    - bool:true
                    - bool:false
                    - string
                    type: string
                type: object
              weight:
                type: integer
            required:
            - prefix
            - service
            type: object
          status:
            description: MappingStatus defines the observed state of Mapping
            properties:
              reason:
                type: string
              state:
                enum:
                - ""
                - Inactive
                - Running
                type: string
            type: object
        type: object
    served: true
    storage: false
    subresources:
      status: {}
  - name: v1
    schema:
      openAPIV3Schema:
        description: Mapping is the Schema for the mappings API
        type: object
        x-kubernetes-preserve-unknown-fields: true
    served: false
    storage: false

Hey, right now its not possible to simulate API calls.
In your case you would need to "mock" the response in the context configuration under variables.
like:
variables:
  currentMappingHostValues: ['anchore.appz.abc.com/']

A working share link: Playground

Makes sense.  Thanks!


Applying a Fee Wavier in any Request State

Describe the bug in current situation
When a fee waiver needs to be applied to a request, the request must be in the On-Hold state for the value to be entered. In any state besides the On-Hold state, the fee waiver option is greyed out and no information can be entered.
Link bug to the User Story
Impact of this bug
Fee waivers can be granted at any point during a request's lifecycle. It slows the process down for the IAO analyst and client ministry to constantly move a request back into the On-Hold state to enter this information.
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requisites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Go to Any request in any state besides On-Hold
Click on the CFR tab
Scroll down to the fee waiver option
See Error

Actual/ observed behaviour/ results
The fee waiver box remains grey and the value of the fee waiver cannot be entered by the IAO analyst or ministry client.
Expected behaviour
GIVEN An IAO analyst or ministry coordinator is in a request, in any state, where a full or partial fee waiver is granted
WHEN They select the CFR tab on the request
THEN The fee waiver box will be live and editable
AND the value of the fee waiver can be entered.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

@m-prodan For review!


QT compile error

image/qjpeghandler.cpp: In function ‘bool read_jpeg_image(QImage*, QSize, QRect, QRect, int, Rgb888ToRgb32Converter, j_decompress_ptr, my_error_mgr*)’:
image/qjpeghandler.cpp:384:41: error: invalid conversion from ‘JSAMPROW {aka char*}’ to ‘uchar* {aka unsigned char*}’ [-fpermissive]
                     uchar *in = rows[0] + clip.x() * 3;
                                 ~~~~~~~~^~~~~~~~~~~~~~
image/qjpeghandler.cpp:389:41: error: invalid conversion from ‘JSAMPROW {aka char*}’ to ‘uchar* {aka unsigned char*}’ [-fpermissive]
                     uchar *in = rows[0] + clip.x() * 4;
                                 ~~~~~~~~^~~~~~~~~~~~~~
image/qjpeghandler.cpp:408:50: error: invalid conversion from ‘uchar** {aka unsigned char**}’ to ‘JSAMPARRAY {aka char**}’ [-fpermissive]
                 (void) jpeg_read_scanlines(info, &row, 1);
                                                  ^~~~
In file included from image/qjpeghandler.cpp:64:0:
/home/wheybags/.hunter/_Base/7202b63/2df0ae1/594d1c9/Install/include/jpeglib.h:1056:20: note:   initializing argument 2 of ‘JDIMENSION jpeg_read_scanlines(j_decompress_ptr, JSAMPARRAY, JDIMENSION)’
 EXTERN(JDIMENSION) jpeg_read_scanlines JPP((j_decompress_ptr cinfo,
                    ^~~~~~~~~~~~~~~~~~~
image/qjpeghandler.cpp: In function ‘bool write_jpeg_image(const QImage&, QIODevice*, int, const QString&, bool, bool)’:
image/qjpeghandler.cpp:602:26: error: invalid conversion from ‘uchar* {aka unsigned char*}’ to ‘JSAMPROW {aka char*}’ [-fpermissive]
         row_pointer[0] = new uchar[cinfo.image_width*cinfo.input_components];
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
image/qjpeghandler.cpp:605:39: error: invalid conversion from ‘JSAMPROW {aka char*}’ to ‘uchar* {aka unsigned char*}’ [-fpermissive]
             uchar *row = row_pointer[0];
                          ~~~~~~~~~~~~~^

gcc version 6.3.0

I think there are 3 errors here:

Seems that JPEG update broke some stuff. See this change (note that CI is working). Affect OpenCV already: https://github.com/ruslo/hunter/pull/986#issuecomment-326737616 @xsacha +cc

If Qt is using JPEG library installed by Hunter then there should be hunter_add_package(Jpeg) in scheme

Qt is built with own copy of JPEG (see -qt-libjpeg) so actually Qt should not use JPEG headers from Hunter (Qt bug?)

I think OpenCV, dlib and Qt allow the option of linking to an existing (i.e. hunter) image library (jpeg/png/gif) or building it from source.
In Qt, the option is -system-libjpeg vs -qt-libjpeg.
In OpenCV, the option is WITH_JPEG without BUILD_JPEG
Building it from source is troublesome as the linker will often complain that there are multiple versions of the same symbol in the situation you have both Hunter and an in-package version of the library.
Should it be enforced to use only Hunter libraries and not have the option of BUILD_JPEG, BUILD_PNG etc (i.e. in-package)?

In OpenCV, the option is WITH_JPEG without BUILD_JPEG

OpenCV is already hunterized so the only problem is JPEG headers.

Should it be enforced to use only Hunter libraries and not have the option of BUILD_JPEG, BUILD_PNG etc (i.e. in-package)?

This check can be implemented in OpenCV hunterized fork.

In Qt, the option is -system-libjpeg vs -qt-libjpeg.

I agree, we should use packages from Hunter. Such changes are quite fragile and require a lot of testing and manual checks. One by one pull requests with minimal change are welcome.

Closing inactive discussion.


(maint) Rerevert environment guard

This reverts commit 21bf78d0ed9be75a14c2f73bbdf14899bcfafe10, reversing
changes made to 53aa5b312d1f15063822b8ad2f5c545975ad47a3.

Note commit 53aa5b312d passed PE CI

jenkins please test this with servertests


[BUG]

Browser
Safari
Bug Description
VS Code extension is not generating the warp them.
Using warp version: v0.2<IP_ADDRESS>.15.stable_03
VS Code version: Version: 1.71.2
Steps to Reproduce
Install extension exit and restart warp and VS Code theme does not appear in list.
Additional Context
This one seems straight forward.

I'll look into to it as soon as possible :)

➕1 Same here.

I just published v1.0.3 to the marketplace, which should fix this issue. If not feel free to reopen this issue :)!
https://marketplace.visualstudio.com/items?itemName=haack.warp-companion

Tried again, but still no VS Code theme visible in Warp. 🤔

Warp v0.2<IP_ADDRESS>.08.stable_01
VS Code Version: 1.71.2
warp-companion: v1.0.3

Have you tried switching the theme? It should create the .yaml file, as soon as the theme is switched 🤔

🙏 Thanks for the quick response.
When I switch the theme in VS Code, it opens an empty tab labeled warp-companion-panel, but still no evidence of any vs theme in Warp:

Tried quitting & restarting both VS Code & Warp, but no luck so far.

Does the empty tab stay open or does it close immediately?

stays open

This bug finally should be fixed by now with the release of v1.0.4 :)

With v1.0.4, the empty warp-companion-panel tab is gone and I get a notification in VS Code that looks promising, but still no sign of a new theme in Warp (even after restart):

Where should I be looking for the .yaml file?

Well that's interesting 🤔 The file should be located at ~/.warp/themes/vs_code.yaml.
Might take a look at the contents, if the file exists?

File is created at ~/.warp/themes/vs_code.yaml with the following content:
background: "#292d3e"
accent: rgba(113, 124, 180, 0.31)
foreground: "#a6accd"
details: darker
terminal_colors:
  normal:
    black: "#000000"
    red: "#ff5370"
    green: "#c3e88d"
    yellow: "#ffcb6b"
    blue: "#82aaff"
    magenta: "#c792ea"
    cyan: "#89ddff"
    white: "#ffffff"
  bright:
    black: "#676e95"
    red: "#ff5370"
    green: "#c3e88d"
    yellow: "#ffcb6b"
    blue: "#82aaff"
    magenta: "#c792ea"
    cyan: "#89ddff"
    white: "#ffffff"

— but for some reason, the theme is not available in the Warp theme browser ⌃ ⌘ T.
Checked Security & Privacy > Privacy > Files and Folders to see if Warp has permission to access the home folder and saw that it only had access to Documents & Downloads.
Tried granting Full Disk Access, but Warp still doesn't see the theme file. 🤷

Than this error actually is related to #2 😬 Warp only supports hexadecimal representations of colors and not rgb/a. I'll implement a fix as soon as possible :)


Upgrade from sixtyfps to slint UI framework

The UI framework used in the KDE example was renamed from "sixtyfps" to "slint". This PR switches from the old name to the new name, as the Crates under the old name won't receive any update in the future.

As we do not have an automated test for the examples yet, I've build and tested the change locally and it works.


Do not terminate application on write exception

Is your feature request related to a problem? Please describe.
The application terminates when we receive an error while writing to the target data source.
Describe the solution you'd like
At this stage, the action to be taken when an error occurs can be defined as a function.
.SetExceptionCallbackFunction()

#54 [duplicate]


Fix typos memmory

Fix typos memmory

Codecov Report

Merging #971 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #971   +/-   ##
=======================================
  Coverage   18.64%   18.64%
=======================================
  Files         234      234
  Lines      146664   146664
  Branches    12633    12633
=======================================
  Hits        27343    27343
  Misses     118350   118350
  Partials      971      971

Flag
Coverage Δ

#2017
18.64% <ø> (ø)
:arrow_up:

#Debug
18.64% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

src/TraceEvent/Parsers/KernelTraceEventParser.cs
36.95% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3654ab3...901daef. Read the comment docs.


Mapping LDAP Groups to Roles not working

Hello,
Firstly, good work on making LDAP auth simple.
But I can't figure out how to map LDAP Groups to Roles.
I configured ldaptools-bundle this way:
ldap_tools:
    security:
        default_role: null
        roles:
            ROLE_ADMIN: "CN=group 1,OU=groups_l,OU=lorem,OU=Ipsum,DC=dolor,DC=local"
            ROLE_USER: "CN=group 2,OU=groups_l,OU=lorem,OU=Ipsum,DC=dolor,DC=local"

I manage to login successfully but can't map the good roles.
Do you have any idea what I'm doing wrong?

Are you using OpenLDAP or Active Directory?

Thanks for the quick answer.
AD

I would double check that you have the DN right for the group. If you replace it with just the simple name of the group (ie. "Group 1") does it work?
Or verify the group information via a query (should spit out the DN, Name, GUID):
$group = $this->get('ldap_tools.ldap_manager')
    ->buildLdapQuery()
    ->fromGroups()
    ->where(['name' => 'Group 1'])
    ->getLdapQuery()
    ->getArrayResult()
dump($group);

Thanks @ChadSikorra, it was the base_dn.

@ladenise can u show your base_dn please. i have the same issue.
thanks

@adelinoo please find it below even if I think it won't you very much:
base_dn: 'DC=dolor,DC=local'


Current buildstream master is failing to build freedesktop-sdk

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Sep 20, 2018, 11:44
Summary
Build of current release of freedesktop-sdk is failing whe trygin to use bst master (commit 667dd4ca), It builds fine with bst-1.2
Relevant logs and/or screenshots
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/jobs/99556677

In GitLab by [Gitlab user @jjardon] on Sep 20, 2018, 11:45
changed the description

In GitLab by [Gitlab user @jjardon] on Sep 20, 2018, 12:13
changed the description

In GitLab by [Gitlab user @toscalix] on Sep 20, 2018, 15:59
assigned to [Gitlab user @tristanvb]

In GitLab by [Gitlab user @juergbi] on Sep 21, 2018, 06:50
[Gitlab user @jmacarthur] I suspect this is a regression from the introduction of the Directory API. The flatpak_image plugin (from bst-external) creates directories using os.makedirs() (i.e., not using the new API). After that it calls Element.stage_dependency_artifacts(), which uses the new API attempting to descend into a previously created directory. However, that directory 'buildstream' is not in the FileBasedDirectory index, which results in an error: "No entry called 'buildstream' found in the directory rooted at ..."

In GitLab by [Gitlab user @toscalix] on Sep 21, 2018, 09:07
assigned to [Gitlab user @jmacarthur]

In GitLab by [Gitlab user @jmacarthur] on Sep 21, 2018, 12:42
I agree, there is a concurrent modification problem between FileBasedDirectory and the underlying file system. I think this can be fixed by forbidding the sandbox from caching virtual directory objects if get_directory is ever used, and making some more explicit instructions for the use of get_virtual_directory inside BuildStream.

In GitLab by [Gitlab user @jmacarthur] on Sep 21, 2018, 17:18
mentioned in merge request !818

In GitLab by [Gitlab user @jmacarthur] on Sep 21, 2018, 17:19
!818 may solve this - it fixes the flatpak-images/platform-vaapi-intel.bst element mentioned in attached logs. I'm running a full build of freedesktop-sdk now.

In GitLab by [Gitlab user @jmacarthur] on Sep 24, 2018, 18:04
!818 has successfully built freedesktop-sdk. I've added a change suggested by [Gitlab user @juergbi] and am re-testing freedesktop-sdk at the moment.

In GitLab by [Gitlab user @tristanvb] on Oct 1, 2018, 05:55
I admit I haven't looked intensely deep into this, but I have a thought: Why do we have different codepaths for get_directory() and get_virtual_directory() at all ? This seems error prone.
Instead, maybe we could have an internal context manager for invoking plugin methods which involve staging sources and artifacts, which could then add an interpretation layer between the plugin and any calls it might make to functions like os.makedirs, os.stat, etc, and just automatically do the right thing when the filesystem paths are found to be inside the sandbox ?

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 06:46
This doesn't sound very robust. It would essentially be like a FUSE layer but at the Python OS API level instead of the kernel. Due to this difference we couldn't guarantee that all filesystem I/O would go through this layer. Some plugins might use host tools that use the filesystem. New Python versions or Python modules might add further OS filesystem functions that would be left uncovered, at least until BuildStream could catch up.
It would also likely be quite a bit more complex than what we have now to cover everything we can cover. E.g. we would also have to handle arbitrary file modifications.
FUSE as alternative
An alternative could have been to use a real FUSE layer. However, the POSIX filesystem API isn't the best fit, e.g., copying a directory tree with many files (as we do for staging) requires a lot of syscalls. With FUSE these operations would take even longer (additional context switches), i.e., 'virtual staging' would probably be slower than the current regular staging.
With the virtual directory API some of these operations can be a lot faster. E.g., copying a whole directory tree is a simple O(1) operation if the target doesn't exist yet (i.e., if no merge is required). However, even for the directory merge case, the virtual directory API requires only a fraction of syscalls.
Another aspect is that requiring FUSE wouldn't allow Windows/WSL clients to use remote execution. On macOS it might work but it would also not have been as straight forward.

In GitLab by [Gitlab user @tristanvb] on Oct 1, 2018, 08:52
[Gitlab user @juergbi]

This doesn't sound very robust.

This is definitely true, it might make more sense to have BuildStream APIs which the plugin calls instead for filesystem operations, which BuildStream could marshal into what it wants, but we didn't do that.
At any rate, it would be good at least that if there are two ways of getting a thing done, that we deprecate the old thing in favor of the new one, while keeping support for the old one.
Do I understand that with !818, plugins which continue to use Sandbox.get_directory() will just be ineligible for remote execution ? (wont be able to build Flatpaks using a win32/osx client connected to a grid ?), if so; it might still be worth monkey patching the os and shutil calls in a context manager, and documenting the deprecation of such usage, even if fragile, rather than just not working.

In GitLab by [Gitlab user @juergbi] on Oct 1, 2018, 09:09

This is definitely true, it might make more sense to have BuildStream APIs which the plugin calls instead for filesystem operations, which BuildStream could marshal into what it wants, but we didn't do that.

That's basically what the abstract Directory API is for. BuildStream instantiates either the FileBasedDirectory or the CasBasedDirectory subclass depending on whether local or remote execution is used.

At any rate, it would be good at least that if there are two ways of getting a thing done, that we deprecate the old thing in favor of the new one, while keeping support for the old one.

Yes, that was the plan but we failed to actually declare Sandbox.get_directory() as deprecated and update the documentation accordingly. We should do this now.

Do I understand that with !818, plugins which continue to use Sandbox.get_directory() will just be ineligible for remote execution ? (wont be able to build Flatpaks using a win32/osx client connected to a grid ?), if so; it might still be worth monkey patching the os and shutil calls in a context manager, and documenting the deprecation of such usage, even if fragile, rather than just not working.

Yes, plugins that don't set BST_VIRTUAL_DIRECTORY to True won't work with remote execution. As it should be very simple to port plugins to the virtual directory API, I don't think it's worth the effort (and the potentially hard to debug issues).

In GitLab by [Gitlab user @tristanvb] on Oct 1, 2018, 10:02

Yes, plugins that don't set BST_VIRTUAL_DIRECTORY to True won't work with remote execution. As it should be very simple to port plugins to the virtual directory API, I don't think it's worth the effort (and the potentially hard to debug issues).

Agreed.
That said we should make sure to have an early error in preflight when remote execution is needed or expected, and the plugins in use do not support it.

In GitLab by [Gitlab user @valentindavid] on Oct 1, 2018, 16:48
How can we make a plugin work with remote execution and still support 1.2? I think we will need that.

In GitLab by [Gitlab user @tristanvb] on Oct 5, 2018, 07:36

How can we make a plugin work with remote execution and still support 1.2? I think we will need that.

This is an interesting question, I think in practice we don't need that.
When 1.4 is out, the plugin will either:

Not have support for remote execution
Require BuildStream >= 1.4

In GitLab by [Gitlab user @juergbi] on Oct 5, 2018, 07:45
I think it would be possible to create a plugin with conditionals, transparently supporting both BuildStream 1.2 and remote execution. It would come at the cost of increased code complexity. However, as most plugins don't contain that much code, it should be manageable.

In GitLab by [Gitlab user @tristanvb] on Oct 5, 2018, 07:50

I think it would be possible to create a plugin with conditionals, transparently supporting both BuildStream 1.2 and remote execution. It would come at the cost of increased code complexity. However, as most plugins don't contain that much code, it should be manageable.

That is probably possible indeed, however only useful for a limited time of a development cycle, you'd probably want to gut that code out after the 1.4 release and just depend on >= 1.4 from then on.

In GitLab by [Gitlab user @jmacarthur] on Oct 10, 2018, 13:58
The above discussion is very useful, but can we agree that it's not directly part of this urgent issue? I'm happy to capture this in a new issue.

In GitLab by [Gitlab user @tristanvb] on Oct 10, 2018, 14:24
[Gitlab user @jmacarthur], I don't think we need a separate issue for that conversation in BuildStream proper.
We already do have public API utils.get_bst_version() which reports a major/minor point version integer tuple - so afaics BuildStream provides an API surface already for a plugin which might want to do conditional support depending on the BuildStream version.

In GitLab by [Gitlab user @jmacarthur] on Oct 22, 2018, 11:35
Closing this as freedesktop-sdk now builds and none of the comments after that are actionable.

In GitLab by [Gitlab user @jmacarthur] on Oct 22, 2018, 11:35
closed


Added a password strength checker

Added a meter that will measure the strength of a password

Thank you for your contribution.


Package Manager page does not list Orchestrator

Describe the bug
In the Package Manager section, the Orchestrator package does not appear/
Version
Version:  1.3.1-nightly.219396.61c944a
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0
Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[x] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

I was following this step in the Orchestrator bug bash instructions:

In Package Manager, under the Browse tab, I only see two packages:

and only one installed:

Do I need to edit my feeds? Do I need to reset my feeds to default?
Expected behavior
I expected to see more packages. I'd also expect the package manager feeds to be in Composer settings, if they effect all my bots, instead of in the package manager.

I believe this is due to the feed being out of date in your composer settings.
You should see 4 packages, including orchestrator.

Is the feeds surfaced in the UI on the Composer Settings page? (I didn't see anything there.)

click edit feeds at top

@mewa1024 have you been able to rectify this issue?
if not i can jump on a chat..

no, Orchestrator still doesn't show up--but what feeds should I be using? This is what I have:

This is the old feed.
The new one is:
https://api.nuget.org/v3/index.json

That worked. Is there anywhere in the UI where the user can get the latest feeds? Like "Restore to defaults" or something? I could not find it anywhere.

Also, your list of feeds are Composer-wide, not project-specific, right?

@taicchoumsft can you comment on this one?

Changing the feed manually as Ben described above worked, so I can close this bug. Thanks!


readme so bad

Version: lastest
Platform: windows 10
Description:
import redis
>>> r = redis.Redis(host='localhost', port=6379, db=0)
>>> r.set('foo', 'bar')
True
>>> r.get('foo')
b'bar'
r.get('foo')  return b'bar' .  start with b so puzzle.

general  use redis to set text type ,not byte.
while I first use redis-py r.get  ('foo') ,I fee puzzle. why b start with result?
use redis cli or java redis client   result is normal.
I cost ten minute to think and search the question, find the solution:
https://stackoverflow.com/questions/25745053/about-char-b-prefix-in-python3-4-1-client-connect-to-redis
I do not want next user cost time again?
can the doc change like below ?
r = redis.StrictRedis(host="localhost", port=6379, charset="utf-8", decode_responses=True)

There’s actually a lot of use cases for redis-py to store bytes in Redis. Many caching frameworks serialize data at picked objects or json before writing to Redis. Both of these types work with bytes, not strings.
I believe the docs should start with the basic, no-frills options first and then describe how to add on higher level features. The 2 paragraphs immediately following the code example you highlighted talk specifically about decode_responses.
I’m all for enhancing this section but I’m happy with the way that it starts. Feel free to open a PR if you like.


CandleStickChartWithUpdatingData

code does not work in this example: "https://bl.ocks.org/rrag/555ea9d11c621a895171",
on "http://rrag.github.io/react-stockcharts/documentation.html#/updating_data" file "http://rrag.github.io/react-stockcharts/dist/react-stockcharts-documentation.js" page too big to understand the source code. What changes need to be done in the first example to the demo work?

the source in the block uses v0.3 which is no longer the current version
How did you get to that link? I had removed all references to that link from documentation, if there is still some old reference to it, please let me know so I can remove that.
http://rrag.github.io/react-stockcharts/documentation.html#/updating_data
does not have a link to that block. to avoid the confusion I deleted that block now.
Link to source is available in the above link
https://github.com/rrag/react-stockcharts/blob/master/docs/lib/charts/CandleStickChartWithUpdatingData.jsx


Empty lists are bound as nulls

Minimal working example
Consider the following Main method:
static void Main(string[] args)
{
    var c = new ConfigurationBuilder()
        .AddJsonFile("appsettings.json")
        .Build()
        .GetSection("Things")
        .Get<string[]>();
}

Case 1
With the following config, c has 2 items:
{
    "Things": [
        "Value1",
        "Value2"
    ]
}

Case 2
With the following config, c has 1 item:
{
    "Things": [
        "Value1"
    ]
}

Case 3
With the following config, c is null:
{
    "Things": [
    ]
}

Case 4
With the following config, c is null:
{
}

Notes
In Case 3, I would expect a list with 0 items. I find it surprising that an empty list is considered null. This causes trouble for settings validation, because there are legitimate use cases where an empty list is valid. Because empty lists are treated the same as nulls, it's not possible to distinguish between the configuration system correctly specifying an empty list (Case 3), and a total binding failure (Case 4) or other problem ingesting IConfiguration.
Although the minimal example above uses strings, the behavior is the same for more complex objects.

Related issue which got shut down as "Nothing to be done here" which I disagree with.


Feat: Donate Form UI and responsive

Describe the feature
Improving UI to match website theme of the page.
Adding conformation pop-up on submission of form.
Making page responsive for all screen sizes.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@huamanraj @anuragverma108 Sir,
Please assign this issue to me under GSSoC'24. Thank You!


WIP UPSTREAM : Rebase code to kfp 2.2.0

Description of your changes:
Resolves #RHOAIENG-6670
Checklist:

[ ] The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

it seems the pr is missing the code changes introduced by the rebased changes, example: https://github.com/rimolive/data-science-pipelines/blob/rebase-2.2.0/VERSION
should read 2.2 from this commit https://github.com/opendatahub-io/data-science-pipelines/pull/68/commits/dd59f48cdd0f6cd7fac40306277ef5f3dad6e263#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350


sync: interplay of ninja and --results

aur-build truncates the --results file, and with ninja there is a single aur-build command-line per pkgbase. This means that a file specified to aur sync --results would only contain an entry for the last built pkgbase, and not any preceding them.

I guess --results-append=<file> is the most immediate option.


current version of lazysizes = images sometimes stuck on 'lazyloading' in firefox

since i upgraded the version of lazysizes i am using to a more recent one, i found that images on my site are not always loading in firefox. this page (https://www.ureka.org/thoughts/view/2828/mistakenly-seeking-love-and-acceptance-from-others), for example, has one main blog image on it and it has failed to render in both windows firefox and linux firefox here. the class 'lazyloading' is set for the image, but i don't know more than that presently. the image usually loads correctly when i refresh the page.

Could you please re-check with the current alpha version. (https://afarkas.github.io/lazysizes/lazysizes.min.js) This should be fixed.

ok thanks. the github pages section is down for maintenance presently, so i couldn't access the file you linked. i have downloaded and am testing this version though and so far it looks ok: https://github.com/aFarkas/lazysizes/blob/gh-pages/lazysizes.js


Recurring drives frontend

We're truly sorry, this is the biggest feature by far. This is the front end part of the recurring drives!
Instead of all the new changes, I'm going to describe a flow for testing:

You can create recurring drives by clicking the checkbox on the regular create drive page. Please check if everything is understandable for usability.
You are taken to the new recurring drive detail page, where you can see your schedule, information and all generated drives. In addition to that, you can edit the schedule by tapping the icon on the top right.
You can see your recurring drives on the new "Recurring" tab under the Drives navigator bar entry.
The rest of the time was essentially spent on figuring out edge cases and weirdness that has to do with the complexity of situations that can arise by cancelling, changing or picking weird recurring drive schedules.

We haven't finished everything (especially tests), but please review what we have until now!

The option where you can see the next few upcomming drives as a preview is only available when the next drives are during the next 30 days. Is this right or should we show the next 2 dates even if they are a year apart?

The option where you can see the next few upcomming drives as a preview is only available when the next drives are during the next 30 days. Is this right or should we show the next 2 dates even if they are a year apart?

Yes that might be a little confusing... We can't show any other drives because they were not created yet by the cronjob. Theoretically I could of course lengthen that timeframe. But that would require cancelling many more drives when changing the recurrence rule.
I think 30 days is a good medium timelength, but we should think of some way to better visualize/document this for the end user.

when you change the language to german the "wiederkehrende" is not completely visible

the following exception occurs when i try to stop a drive.
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: PostgrestException(message: column "stopped_at" does not exist, code: 42703, details: Bad Request, hint: null) #0      PostgrestBuilder._parseResponse (package:postgrest/src/postgrest_builder.dart:323:7) #1      PostgrestBuilder._execute (package:postgrest/src/postgrest_builder.dart:198:14) <asynchronous suspension> #2      PostgrestBuilder.then (package:postgrest/src/postgrest_builder.dart:400:24) <asynchronous suspension>

when you change the language to german the "wiederkehrende" is not completely visible

You mean in the tabview? Yeah okay but what can you do 🤷♂

the following exception occurs when i try to stop a drive. [VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: PostgrestException(message: column "stopped_at" does not exist, code: 42703, details: Bad Request, hint: null) #0 PostgrestBuilder._parseResponse (package:postgrest/src/postgrest_builder.dart:323:7) #1 PostgrestBuilder._execute (package:postgrest/src/postgrest_builder.dart:198:14) <asynchronous suspension> #2 PostgrestBuilder.then (package:postgrest/src/postgrest_builder.dart:400:24) <asynchronous suspension>

Whoops. Should be fixed now?

i have an overflow error, at the elements that show on which days the drive will be.

and i can not stop the recurring drive.


Update Campsite challenge copy and labs

Also:

Updated nonprofit project total (we shipped another project)
Updated FAQ

Tested look good to me!

:+1:


Make NESTED-KVM-BASIC-VERIFICATION case available in RHEL-8 and add network checkpoints

This case is updated for adapting to RHEL-8:

Add NESTED_IMAGE_URL, NESTED_VM_USER and NESTED_VM_PASSWORD parameters into the ReplaceableTestParameters.xml, which are used in the params.
Add the downloading public file from github.com step, which was mentioned in the description but not deployed in the case. And add another checkpoint that copy file from L1 host to the nested VM
Skip RHEL-6/RHEL-7
Install epel repo before installing aria2
Change "echo" messges to "LogMsg" and some other fixes.

[LISAv2 Test Results Summary]
Test Run On           : 07/24/2020 05:09:38
Test Category         : Functional
Initial Kernel Version: 4.18.0-227.el8.x86_64
Final Kernel Version  : 4.18.0-227.el8.x86_64
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:12

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 NESTED               NESTED-KVM-BASIC-VERIFICATION                                                     PASS                  8.1
      OsVHD: https://walaautol2.blob.core.windows.net/vhds/RHEL-8.3.0-20200722.n.0.vhd, OverrideVMSize: Standard_E4s_v3, SetupType: OneVM, TestLocation: eastus2, VMGeneration: 1

It looks like there are many functions(e.g.Update_Test_State, Log_Msg) defined in nested_vm_utils that are duplicated to the functions in utils.sh. But some other NESTED cases are rely on them so I don't remove them here.


BLD: updating qiime2 build

There are some R conflicts popping up.  Let's see if these get resolved in the newest q2 release.

It looks like only the master build is being triggered.  Merging this into master for debugging.


mssql for arm64

When will mssql be available for arm64 processors?

I'm also +1 on this! It would be great to see MSSQL support for ARM64 processors.

Also interested but likely not coming anytime soon as Microsoft just removed ARM64 support from the Azure SQL Edge product (which is a smaller version of SQL Server)

With the introduction of the new snapdragon devices, there is a market for mssql on arm, maybe this help to get some attention, since right now there is no way to run mssql on these devices


Safari Support

Hello! This tool has been great so far, very straightforward to set up.
I am wondering how to enable safari support?
My capabilities & services look like this
capabilities: [
    {
      maxInstances: 5,
      browserName: "chrome",
      acceptInsecureCerts: true,
    },
    {
      maxInstances: 5,
      browserName: "firefox",
      acceptInsecureCerts: true,
    },
    {
      maxInstances: 1,
      browserName: "safari",
    },
  ],
...

services: [
    [
      launcher,
      {
        projectArn: process.env.PROJECT_ARN,
      },
    ],
    [
      "safaridriver",
      {
        outputDir: "./logs",
        logFileName: "wdio-safaridriver.log",
      },
    ],
  ],

and i receive these errors when trying to run the test
[2-0] 2022-04-13T22:26:18.017Z ERROR webdriver: invalid argument: 2 validation errors detected: Value 'safari' at 'desiredCapabilities.browserName' failed to satisfy constraint: Member must satisfy value set: [firefox, chrome, internet explorer, MicrosoftEdge]; Value 'safari' at 'capabilities.alwaysMatch.browserName' failed to satisfy constraint: Member must satisfy value set: [firefox, chrome, internet explorer, MicrosoftEdge]

[2-0] 2022-04-13T22:26:18.021Z ERROR @wdio/runner: Error: Failed to create session.
[2-0] 2 validation errors detected: Value 'safari' at 'desiredCapabilities.browserName' failed to satisfy constraint: Member must satisfy value set: [firefox, chrome, internet explorer, MicrosoftEdge]; Value 'safari' at 'capabilities.alwaysMatch.browserName' failed to satisfy constraint: Member must satisfy value set: [firefox, chrome, internet explorer, MicrosoftEdge]

at first i thought this was an error with wdio or my config, but i am able to run tests with this same config locally and things are all working with safari.

@davecusatis thanks for the feedback.
I am afraid that DeviceFarm is currently not supporting Safari hence the error message. You can find the list of currently supported browsers here: Supported Capabilities, Browsers, and Platforms in Device Farm Desktop Browser Testing.

Appreciate the response! So Safari is only available through mobile testing, is that correct? This service doesn't support that yet right?

Yes, that's correct. This WDIO service doesn't support mobile testing yet but we're open to contributions.


Unable to run tests via jest

React version (e.g., 17.0.2)
18.2.0
Package manager version (e.g., yarn 2, npm 8)
8.1.2
Node version (e.g., 16.13.2)
v16.13.1
Rest Hooks version (e.g., 6.2.0)
6.3.4
Describe the bug
I'm upgrading to react 18 and moving away from enzyme. When I try to run my tests via jest and react-testing-library I get the following error:
    Details:

    node_modules/rest-hooks/lib/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export { useCache, useControl
ler, useFetcher, useRetrieve, useResource, useSubscription, useMeta, useError, useInvalidator, useResetter, useDenormalized, useSuspense, useFetch, useDLE, // TODO: get rid of these exports once core has been out for a while
                                                                                ^^^^^^

    SyntaxError: Unexpected token 'export'

If I set transformIgnorePatterns: ["node_modules/(?!rest-hooks|@rest-hooks)"], in jest.config.js then I get a different error:
 TypeError: this.memo is not a function

at Function.memo [as endpoint] (node_modules/@rest-hooks/rest/src/SimpleResource.ts:138:17)

Is there a way to build this package without needing to convert to ECMAScript Modules?
To Reproduce
jest.config.js
"use strict";

module.exports = {
  preset: "ts-jest",
  transform: {
    "\\.tsx?$": 'ts-jest',
    "\\.jsx?$": "babel-jest",
  },
  moduleNameMapper: {
    "^.+\\.(css|scss|gif|jpg|png)$": "identity-obj-proxy",
  },
  transformIgnorePatterns: ["node_modules/(?!rest-hooks|@rest-hooks)"],
  modulePaths: ["frontend", "frontend/src", "frontend/src/app"],
  collectCoverageFrom: ["frontend/src/**/*.{js,jsx,ts,tsx}"],
  coveragePathIgnorePatterns: [
    "frontend/src/index.js",
    "frontend/src/constants/*",
    "frontend/src/pages/*",
    "frontend/src/tests/*",
  ],
  coverageReporters: ["html", "text", "text-summary", "cobertura"],
  setupFiles: ["./jest-setup.js"],
  testEnvironment: "jsdom",
  testPathIgnorePatterns: ["frontend/src/test-utils/*"],
};

jest-setup.js
import "whatwg-fetch";
import "core-js/stable";

global.$RefreshReg$ = () => {};
global.$RefreshSig$ = () => () => {};

webpack rule:
  {
    test: /\.[jt]sx?$/,
    exclude: /node_modules/,
    use: [
      {
        loader: require.resolve('babel-loader'),
        options: {
          plugins: [require.resolve('react-refresh/babel')],
        },
      },
    ],
  },

babel.config.js
"use strict";

module.exports = {
  presets: [
    "@babel/preset-env",
    "@babel/preset-typescript",
    ["@babel/preset-react", { runtime: "automatic" }],
  ],
  plugins: [["react-refresh/babel", {skipEnvCheck: true}], "@babel/transform-runtime"],
};

Thanks for the report, @ah19 ! Can you confirm that the same setup had worked with the previous version of react?

I have discovered the cause. Jest is identifying itself as a 'browser' conditional for package.json 'exports' field, rather than 'node'. This appears to be a somewhat recent change in a downstream dependency.
Will push a new version of the packages with updated exports entries.


Failed to load plug-in script: Error: Invalid entity type.

Describe the bug
Upon loading a park, OpenRCT2 outputs this error message:

Failed to load plug-in script: Error: Invalid entity type.

To reproduce

Install the latest OpenRCT2 (<IP_ADDRESS>)
Install ParkRatingInspector
Run openrct2.com
Start a new scenario
ParkRatingInspector is not loaded
See the output from openrct2.com

Expected behavior
The plugin should load and work.
Notes
I suspect this is due to changes to the "peep", "guest", and "staff" entity types.

@kendfrey You're correct that the readme does not mention it unfortunately. It is mentioned in big letters on the download page, I'm afraid I can't make them any bigger. 😁


Felipe talk at Devs conf

It's fine @plhnk
Thanks for moving this @victorvalle!

waiting for a new banner to merge this


Upgrade script and instructions

Walk a Lamassu operator through the process of upgrading from the standard https://github.com/lamassu/lamassu-machine code base to this Dash-enabled code base. This will at least require installing this code and pointing the upstart scripts toward the new installation.
As much as possible should be automated in an update script, then instructions on running the script put into a text document for operators.

Git Guild Bounty Program

Total
Dev
Sales
Reporter
Tester(s)
Maintainer
Documenter

N/A
assignee(s)
@isysd
@isysd
@isysd
@isysd
@d3brouille

$201.67
$110.00
$9.17
$9.17
$36.67
$9.17
$9.17

Replaced by more detailed task. #8


Java Error on run

Running Gradle task 'assembleDebug'...
Exception in thread "main" java.lang.NoClassDefFoundError: org/gradle/internal/jvm/UnsupportedJavaRuntimeException
	at java.base/java.lang.Class.getDeclaredMethods0(Native Method)
	at java.base/java.lang.Class.privateGetDeclaredMethods(Class.java:3166)
	at java.base/java.lang.Class.getMethodsRecursive(Class.java:3307)
	at java.base/java.lang.Class.getMethod0(Class.java:3293)
	at java.base/java.lang.Class.getMethod(Class.java:2106)
	at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:29)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Caused by: java.lang.ClassNotFoundException: org.gradle.internal.jvm.UnsupportedJavaRuntimeException
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:589)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
	... 8 more

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


output 'tensorflow/core/kernels/_objs/reduction_ops_gpu/tensorflow/core/kernels/reduction_ops_half_mean_sum.cu.pic.o' was not created

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
Python version:3.6.6
Bazel version (if compiling from source):0.11.1
GCC/Compiler version (if compiling from source):7.3.0
CUDA/cuDNN version:CUDA10.0  , cuDNN 7
GPU model and memory:GTX1050
Exact command to reproduce:

### Describe the problem
While I run the code '''' from https://github.com/VLOGroup/mri-variationalnetwork

I'm using Ubuntu18.04,
bazel 0.11.1
Cuda10.0
cuDNN7.4

I think some attributes not compile in the file " paramdefination.py"

def plt_act_function(x, phi):
my_dpi = 96.
fig = matplotlib.figure.Figure(figsize=(350/my_dpi, 250/my_dpi), dpi=my_dpi)
ax = fig.add_subplot(1, 1, 1)
images = []
for s in range(phi.shape[0]):
images_stage = []
for i in range(phi.shape[1]):
ax.clear()
ax.plot(x, phi[s, i, :])
if fig.canvas is None:
FigureCanvasAgg(fig)
fig.canvas.draw()
img_data = np.fromstring(fig.canvas.tostring_rgb(), dtype=np.uint8, sep='')
img_data = img_data.reshape(fig.canvas.get_width_height()[::-1] + (3,))
images_stage.append(img_data)
images.append(images_stage)
return np.asarray(images)

This is the following issue:

2020-02-09 14:45:41.165513: W tensorflow/core/framework/op_kernel.cc:1198] Unknown: AttributeError: 'FigureCanvasBase' object has no attribute 'tostring_rgb'
Traceback (most recent call last):
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1350, in _do_call
return fn(*args)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1329, in _run_fn
status, run_metadata)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/framework/errors_impl.py", line 473, in exit
c_api.TF_GetCode(self.status.status))
tensorflow.python.framework.errors_impl.UnknownError: AttributeError: 'FigureCanvasBase' object has no attribute 'tostring_rgb'
[[Node: activation_plot/PyFunc = PyFunc[Tin=[DT_FLOAT, DT_FLOAT], Tout=[DT_UINT8], token="pyfunc_2", _device="/job:localhost/replica:0/task:0/device:CPU:0"](activation_plot/strided_slice/_371, activation_plot/Reshape_1/_373)]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "train_mri_vn.py", line 315, in
coord.join(enqueue_threads_data)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/training/coordinator.py", line 387, in join
six.reraise(*self._exc_info_to_raise)
File "/home/vivi/.local/lib/python3.6/site-packages/six.py", line 703, in reraise
raise value
File "train_mri_vn.py", line 295, in
options=run_options, run_metadata=run_metadata)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 895, in run
run_metadata_ptr)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1128, in _run
feed_dict_tensor, options, run_metadata)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1344, in _do_run
options, run_metadata)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1363, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.UnknownError: AttributeError: 'FigureCanvasBase' object has no attribute 'tostring_rgb'
[[Node: activation_plot/PyFunc = PyFunc[Tin=[DT_FLOAT, DT_FLOAT], Tout=[DT_UINT8], token="pyfunc_2", _device="/job:localhost/replica:0/task:0/device:CPU:0"](activation_plot/strided_slice/_371, activation_plot/Reshape_1/_373)]]

Caused by op 'activation_plot/PyFunc', defined at:
File "train_mri_vn.py", line 176, in
vn.paramdefinitions.add_activation_function_params(params, reg_config['activation1'])
File "/home/vivi/mri-variationalnetwork-master/vn/paramdefinitions.py", line 70, in add_activation_function_params
phi_img = tf.py_func(plt_act_function, [x_plt_tf[:, 0], phi_plt], tf.uint8)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/ops/script_ops.py", line 300, in py_func
func=func, inp=inp, Tout=Tout, stateful=stateful, eager=False, name=name)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/ops/script_ops.py", line 209, in _internal_py_func
input=inp, token=token, Tout=Tout, name=name)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/ops/gen_script_ops.py", line 93, in _py_func
"PyFunc", input=input, token=token, Tout=Tout, name=name)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3160, in create_op
op_def=op_def)
File "/home/vivi/.local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1625, in init
self._traceback = self._graph._extract_stack() # pylint: disable=protected-access

UnknownError (see above for traceback): AttributeError: 'FigureCanvasBase' object has no attribute 'tostring_rgb'
[[Node: activation_plot/PyFunc = PyFunc[Tin=[DT_FLOAT, DT_FLOAT], Tout=[DT_UINT8], token="pyfunc_2", _device="/job:localhost/replica:0/task:0/device:CPU:0"](activation_plot/strided_slice/_371, activation_plot/Reshape_1/_373)]]

@vivien624, Please provide the complete code to replicate the reported issue and also Tensorflow version that you are using. Thanks!

@vivien624, Any update?

I think I figured it out. Thank you very much.
gadagashwini<EMAIL_ADDRESS>于2020年2月17日周一 上午5:45写道：

@vivien624 https://github.com/vivien624, Any update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/36553?email_source=notifications&email_token=AOPZSCIBVLUWBKLCLIZQW33RDJTGHA5CNFSM4KRSSXG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL55WVY#issuecomment-586931031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPZSCO2XHSODMO5GE4QCIDRDJTGHANCNFSM4KRSSXGQ
.

@vivien624, Glad that it resolved.

@vivien624, I am having the same issue. How did you resolve it? Thanks!

@vivien624, I am having the same issue. How did you resolve it? Thanks!
See this issue: https://github.com/tensorflow/tensorflow/issues/28796
and it was  resolved by https://github.com/tensorflow/tensorflow/commit/3c245f52912612ed9d8e20245ddb5de055680969

See this issue: #28796
https://github.com/tensorflow/tensorflow/issues/28796
The comment from Tayseer-bme https://github.com/Tayseer-bme gives
solution:
https://github.com/tensorflow/tensorflow/issues/28796#issuecomment-496881881
and it was resolved by 3c245f5
https://github.com/tensorflow/tensorflow/commit/3c245f52912612ed9d8e20245ddb5de055680969
cecilr14<EMAIL_ADDRESS>于2020年4月2日周四 下午12:06写道：

@vivien624 https://github.com/vivien624, I am having the same issue.
How did you resolve it? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/36553#issuecomment-607972625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPZSCO55XBVU4SEMMNLWCDRKTAXPANCNFSM4KRSSXGQ
.

@vivien624, Thanks! Sadly, the above changes do not work for me. I am using Tensorflow's r1.8 branch which already has the commit 3c245f5 and am still getting the error:
'FigureCanvasBase' object has no attribute 'tostring_rgb
in paramdefinitions.py


RSDK-8684: modules hang on shutdown

In Python 3.12.6, there is a bug that happens with the grpclib library, where log handlers are not closed correctly. The logs show that the process is killed instead of cleanly exited.
The bug also doesn't happen if the system is on earlier versions of the Python SDK (v0.23.0) or RDK (v0.27.0). Why this is is still unclear. Maybe it was because I did a brew upgrade and it upgraded other things other than the RDK, like the Python version? I doubt that it would change my Python version, but I'm confused as to how a bug introduced by a Python version is affected by the Python SDK and RDK version.
To fix this without changing the grpc library, we have to watch the awaited function wait_closed() for when to put in logging.shutdown manually.

Closing in favor of #733


Bug/57 responsive font size

Frontend design improved, namely:

.sass files with styles added
Font sizes made responsive
Homepage swipe incentive added
Desktop navigation arrows added
Slides sizing changed to fullscreen
Various design details

npm install in frontend directory is required to make styles work!

Thank you for the review.
I fixed the frontend nginx configuration, which prevented CSS from loading properly. This should make my changes work in Docker as well, thereby solving points 2 and 3 from your comment.
Ad 1 - I changed the image sizing because I think that displaying a 1:1 image on (usually) 16:9 phones looks odd, as you are wasting a big portion of the screen with a solid colour. But I can change this, of course, if you prefer the original. What does @PiechZ think?
Ad 4 - I will replace the character with a multiplatform one.

I´m more for full-screen stretch or rather this responsive behavior, it looks good on both PC and mainly mobile devices. @shippy @szymsza

@szymsza Sorry about nginx; thanks for fixing it. (I can't quite tell what you did, but everything seems to work, so yay.)
I agree that the slides look good on mobile - there's less background-image detail on the sides, so not much is lost there when it's cropped. Viewing it on my laptop, I'm noticing that a lot of the important-to-the-image detail is in the top third, which gets mercilessly cut off. What would you think about either (1) positioning the images so that they get cut off at the bottom instead of the top, or (2) restricting max-width but not height?
(I'm using /slides/2956 to test, since there's a lot of achievements there.)


add runtime-only install steps

Good start. Do you want to open an issue on the dot.net website to make sure we get runtime instructions there as well?


Clicking on a SmartScanned expense from the past date throws a Hmm error and unable smartscan from that date

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @jliexpensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722937874213389
Action Performed:

SmartScan a receipt
Click on it after few days
Throws error
SmartScan the same receipt (or equivalent one - i.e. same amount, same date)

Expected Result:
Able to smart scan
Actual Result:

Nothing happens in ND
Repeat the SmartScan
Nothing happens in ND

Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/485c6a83-a929-46ca-ac4e-bf230fe2cac9
https://github.com/user-attachments/assets/b4292d3f-29eb-4744-8d30-9b5472b12474

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I don't have an Android to test with - asking here: https://expensify.slack.com/archives/C01SKUP7QR0/p1723823768663629

Bumped the Slack thread

Just adding you here since you're helping me test @strepanier03

Checked today and I can still open the SS details so I'll check again tomorrow.

SS details are still visible on the expense. Will check again tomorrow.

checking now!


speed up watch list crossmatching

Just pinning this for the future. I think I/we can significantly increase the crossmatching speed.

I have some code I wrote for Sherlock that could help. The trick might be in matching lists against one another instead of matching one source at a time. I would need to investigate to be sure but will wait until after UI release day.