zlib compressor error

Hi again,
I have a vti file generated by ParaView 5.11. If I choose no compressor when saving data from ParaView, then the generated file and the corresponding point data can be read by ReadVTK.jl; however, if I choose the zlib compressor, then I get the error:
julia> vtk = VTKFile("test2.vti")
VTKFile("test2.vti", <XMLDocument>, "ImageData", "2.2.0", "LittleEndian", "vtkZLibDataCompressor", <appended_data>, 8000, 6859)

julia> point_data = get_point_data(vtk)
VTKData()

julia> B = get_data(point_data["B"])
ERROR: zlib error: incorrect header check (code: -3)
Stacktrace:
 [1] unsafe_transcode!(output::TranscodingStreams.Buffer, codec::CodecZlib.ZlibDecompressor, input::TranscodingStreams.Buffer)
   @ TranscodingStreams C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:183
 [2] transcode!
   @ C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:127 [inlined]
 [3] transcode(codec::CodecZlib.ZlibDecompressor, input::TranscodingStreams.Buffer, output::Nothing)
   @ TranscodingStreams C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:109
 [4] transcode
   @ C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:108 [inlined]
 [5] transcode
   @ C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:189 [inlined]
 [6] transcode(#unused#::Type{CodecZlib.ZlibDecompressor}, args::Vector{UInt8})
   @ TranscodingStreams C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:37
 [7] get_data(data_array::VTKDataArray{Float64, 3, ReadVTK.FormatAppended})
   @ ReadVTK D:\Computer\ReadVTK.jl\src\ReadVTK.jl:740
 [8] top-level scope
   @ REPL[5]:1

This generated compressed vti file can be read by ParaView. Does it indicate that there are different types of compression zlib format?
A link to the test file is here.

Hi @henry2004y. Unfortunately, I cannot make anything of it. The issue seems related to the decoding of the compressed data stored in the VTI file. Unfortunately, zlib only gives somewhat nondescript error messages, which makes it hard for us non-experts to infer what's going on.
It would be great if you could try to dig in a little deeper. A good start would maybe to create the absolute minimum working example of a file that causes this error - e.g., a simple mesh with just one cell and one data variable (or even without data variables). Then we could try to figure what's what.
My feeling is that this might be related to #44, i.e., that ParaView uses a different encoding strategy of the header information in the compressed data than what is written in the docs.

Here is a MWE. First, a vti file can be generated in ParaView:
from paraview.simple import *
#### disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()

# create a new 'Fast Uniform Grid'
fastUniformGrid1 = FastUniformGrid(registrationName='FastUniformGrid1')

# save data
SaveData('test.vti', proxy=fastUniformGrid1, ChooseArraysToWrite=1,
    PointDataArrays=['DistanceSquared'],
    CompressorType='ZLib')

By default Paraview sets the compressor level for zlib to 6. Then with ReadVTK,
julia> using ReadVTK

julia> vtk = VTKFile("test.vti")
VTKFile("test.vti", <XMLDocument>, "ImageData", "1.0.0", "LittleEndian", "vtkZLibDataCompressor", <appended_data>, 1331, 1000)

julia> point_data = get_point_data(vtk)
VTKData()

julia> data = get_data(point_data["DistanceSquared"])
ERROR: zlib error: incorrect header check (code: -3)
Stacktrace:
 [1] unsafe_transcode!(output::TranscodingStreams.Buffer, codec::CodecZlib.ZlibDecompressor, input::TranscodingStreams.Buffer)
   @ TranscodingStreams C:\Users\hyzho\.julia\packages\TranscodingStreams\2McN2\src\transcode.jl:183
 [2] transcode!


Non-standard spelling customization

There's a documented workflow provided by Microsoft for applying a custom dictionary for style analysis. Could that workflow for adding custom dictionaries be supported as well?

It seems to me, that the workflow for extending the dictionary with custom spelling rules is different than the one that is described by Microsoft. More specifically: custom dictionaries are identified by their Build action (technically being part of the CodeAnalysisDictionary item group); as opposed to being part of an AdditionalFiles item group with a predefined name. Is there a reason for not supporting Microsoft's way of extending the dictionary?

That's a good question.  That's how it was implemented when I first worked on it so I'm not sure if there was a good reason for it. Perhaps @gregr-ni or @ccifra  knows?

Probably more of a question for @pakdev. I could envision a situation where MS re-introduces a checker and our usage of their value results in both systems being active. Using a separate approach might avoid that. Not sure if that was the intent or not.

That custom dictionary page applies to FxCop (legacy analysis):

Prior to Visual Studio 2019 16.5 release, when you select Analyze > Run Code Analysis, it executes legacy analysis. Starting Visual Studio 2019 16.5, Run Code Analysis menu option executes Roslyn-based analyzers for the selected project or solution. If you have installed .NET analyzers, they would also be executed. For more information, see How to: Run Code Analysis Manually for Managed Code.

There was an issue to port the spelling analyzer to Roslyn, which I fulfilled earlier this year with most of the code in this repo. Thus, the procedure to add custom dictionaries did not change, and Microsoft accepted it.
The documentation you linked is slightly out of date. Instead of matching only CodeAnalysisDictionary.xml, it will consider any additional file whose name matches (?:dictionary|custom).*?\.(?:xml|dic)$.
While it correctly states that the file must also be an "additional file", you can mirror the old method by using the Passing a Group of Files mechanism e.g.
<PropertyGroup>
  <AdditionalFileItemNames>$(AdditionalFileItemNames);CodeAnalysisDictionary</AdditionalFileItemNames>
</PropertyGroup>

That essentially states any file whose build action is set to CodeAnalysisDictionary will be added as an "additional file". ASW does that in NI.Pre.targets.

Proposed corrections to docs in #70


Undoing a muscle path change from visualizer does not restore original path

Steps to reproduce

Open arm26
Move a muscle point through the visualizer
Click on Navigator and then hit Undo

Expected result
Path goes back to original
Actual result
Path changes but does not restore to the original path
Environment and GUI version
W10 OpenSim 910a930d-2018-08-01

For the record, that's what the unorthodox "Restore" button on the dialog is supposed to do but I agree an undo fits better in the application 👍


custom azurerm backend for v0.12.0-rc.1

Hello,
Excited with latest development of custom backends, I was trying to get azurerm backend working without a success.
I have latest flux and tf-controller installed on the cluster.
Here is my Terraform:
apiVersion: infra.contrib.fluxcd.io/v1alpha1
kind: Terraform
metadata:
  name: tf-app
  namespace: flux-system
spec:
  approvePlan: "auto"
  backendConfig:
    customConfiguration: |
      backend "azurerm" {
        resource_group_name  = "{rg}"
        storage_account_name = "{sa_name}"
        container_name       = "tfstate"
        key                  = "{key}"
        use_msi              = true
        subscription_id      = "{sub_id}"
        tenant_id            = "{tenant_id}"
      }
  path: {path_to_tf-app}
  interval: 10m
  sourceRef:
    kind: GitRepository
    name: flux-system
    namespace: flux-system
  disableDriftDetection: true
  alwaysCleanupRunnerPod: true
  runnerTerminationGracePeriodSeconds: 30

I am using AKS pod identity, hence the backend has use_msi  = true as it would normally have.
Once this is deployed, in logs tf-controller complains that:
Error loading state: the secret name tfstate-default- is invalid, a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
This is a requirement for Kubernetes secret names.
The workspace name and key must adhere to Kubernetes naming conventions.

When setting .spec.backendConfig.secretSuffix it happily creates kubernetes backend tfstate secret, and of course no state file is stored in Storage Account.
What did I miss?

Thank you for reporting this @mjazwiecki

What did I miss?

Nop, I think it's definitely a bug.

@mjazwiecki did you just happen to upgrade from the previous version, and you got the old CRD inside the cluster?

I first tried with old version of Flux and only then I upgraded it. In both cases the error was the same.

On 18 Aug 2022, at 16:33, Chanwit Kaewkasi @.***> wrote:

@mjazwiecki did you just happen to upgrade from the previous version, and you got the old CRD inside the cluster?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

Sorry for not being clear. I meant the old version of the TF-controller and its chart.

With helm.sh/chart=tf-controller-0.5.0 the error is still there.

could you kubectl describe the object and paste the result here, please?

> k describe crd terraforms.infra.contrib.fluxcd.io
Name:         terraforms.infra.contrib.fluxcd.io
Namespace:
Labels:       app.kubernetes.io/instance=tf-controller
              app.kubernetes.io/managed-by=Helm
              app.kubernetes.io/name=tf-controller
              app.kubernetes.io/version=v0.12.0-rc.1
              control-plane=controller
              helm.sh/chart=tf-controller-0.5.0
              helm.toolkit.fluxcd.io/name=tf-controller
              helm.toolkit.fluxcd.io/namespace=flux-system
Annotations:  controller-gen.kubebuilder.io/version: v0.7.0
              meta.helm.sh/release-name: tf-controller
              meta.helm.sh/release-namespace: flux-system
API Version:  apiextensions.k8s.io/v1
Kind:         CustomResourceDefinition
Metadata:
  Creation Timestamp:  2022-08-19T07:29:14Z
  Generation:          1
  Managed Fields:
    API Version:  apiextensions.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:controller-gen.kubebuilder.io/version:
          f:meta.helm.sh/release-name:
          f:meta.helm.sh/release-namespace:
        f:labels:
          .:
          f:app.kubernetes.io/instance:
          f:app.kubernetes.io/managed-by:
          f:app.kubernetes.io/name:
          f:app.kubernetes.io/version:
          f:control-plane:
          f:helm.sh/chart:
          f:helm.toolkit.fluxcd.io/name:
          f:helm.toolkit.fluxcd.io/namespace:
      f:spec:
        f:conversion:
          .:
          f:strategy:
        f:group:
        f:names:
          f:kind:
          f:listKind:
          f:plural:
          f:shortNames:
          f:singular:
        f:scope:
        f:versions:
    Manager:      helm-controller
    Operation:    Update
    Time:         2022-08-19T07:29:14Z
    API Version:  apiextensions.k8s.io/v1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        f:acceptedNames:
          f:kind:
          f:listKind:
          f:plural:
          f:shortNames:
          f:singular:
        f:conditions:
          k:{"type":"Established"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
          k:{"type":"NamesAccepted"}:
            .:
            f:lastTransitionTime:
            f:message:
            f:reason:
            f:status:
            f:type:
    Manager:         kube-apiserver
    Operation:       Update
    Subresource:     status
    Time:            2022-08-19T07:29:14Z
  Resource Version:  5005167
  UID:               9464e3ec-e0a1-49a9-9ee8-99942f4f7360
Spec:
  Conversion:
    Strategy:  None
  Group:       infra.contrib.fluxcd.io
  Names:
    Kind:       Terraform
    List Kind:  TerraformList
    Plural:     terraforms
    Short Names:
      tf
    Singular:  terraform
  Scope:       Namespaced
  Versions:
    Additional Printer Columns:
      Json Path:  .status.conditions[?(@.type=="Ready")].status
      Name:       Ready
      Type:       string
      Json Path:  .status.conditions[?(@.type=="Ready")].message
      Name:       Status
      Type:       string
      Json Path:  .metadata.creationTimestamp
      Name:       Age
      Type:       date
    Name:         v1alpha1
    Schema:
      openAPIV3Schema:
        Description:  Terraform is the Schema for the terraforms API
        Properties:
          API Version:
            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.  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:  TerraformSpec defines the desired state of Terraform
            Properties:
              Always Cleanup Runner Pod:
                Default:      true
                Description:  Clean the runner pod up after each reconciliation cycle
                Type:         boolean
              Approve Plan:
                Description:  ApprovePlan specifies name of a plan wanted to approve. If its value is "auto", the controller will automatically approve every plan.
                Type:         string
              Backend Config:
                Description:  BackendConfigSpec is for specifying configuration for Terraform's Kubernetes backend
                Properties:
                  Config Path:
                    Type:  string
                  Custom Configuration:
                    Type:  string
                  Disable:
                    Description:  Disable is to completely disable the backend configuration.
                    Type:         boolean
                  In Cluster Config:
                    Type:  boolean
                  Labels:
                    Additional Properties:
                      Type:  string
                    Type:    object
                  Secret Suffix:
                    Type:  string
                Type:      object
              Backend Configs From:
                Items:
                  Properties:
                    Keys:
                      Description:  Keys is the data key where a specific value can be found at. Defaults to all keys.
                      Items:
                        Type:  string
                      Type:    array
                    Kind:
                      Description:  Kind of the values referent, valid values are ('Secret', 'ConfigMap').
                      Enum:
                        Secret
                        ConfigMap
                      Type:  string
                    Name:
                      Description:  Name of the configs referent. Should reside in the same namespace as the referring resource.
                      Max Length:   253
                      Min Length:   1
                      Type:         string
                    Optional:
                      Description:  Optional marks this BackendConfigsReference as optional. When set, a not found error for the values reference is ignored, but any Key or transient error will still result in a reconciliation failure.
                      Type:         boolean
                  Required:
                    kind
                    name
                  Type:  object
                Type:    array
              Cli Config Secret Ref:
                Description:  SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace
                Properties:
                  Name:
                    Description:  name is unique within a namespace to reference a secret resource.
                    Type:         string
                  Namespace:
                    Description:  namespace defines the space within which the secret name must be unique.
                    Type:         string
                Type:             object
              Destroy:
                Description:  Destroy produces a destroy plan.
                 Defaults to false.
                Type:         boolean
              Disable Drift Detection:
                Default:      false
                Description:  Disable automatic drift detection. Drift detection may be resource intensive in the context of a large cluster or complex Terraform statefile. Defaults to false.
                Type:         boolean
              Enable Inventory:
                Description:  EnableInventory enables the object to store resource entries as the inventory for external use.
                Type:         boolean
              Force:
                Default:      false
                Description:  Force instructs the controller to unconditionally re-plan and re-apply TF resources. Defaults to false.
                Type:         boolean
              Health Checks:
                Description:  List of health checks to be performed.
                Items:
                  Description:  HealthCheck contains configuration needed to perform a health check after terraform is applied.
                  Properties:
                    Address:
                      Description:  Address to perform tcp health check on. Required when tcp type is specified. Go template can be used to reference values from the terraform output (e.g. <IP_ADDRESS>:8080, :).
                      Type:         string
                    Name:
                      Description:  Name of the health check.
                      Max Length:   253
                      Min Length:   1
                      Type:         string
                    Timeout:
                      Default:      20s
                      Description:  The timeout period at which the connection should timeout if unable to complete the request. When not specified, default 20s timeout is used.
                      Type:         string
                    Type:
                      Description:  Type of the health check, valid values are ('tcp', 'http'). If tcp is specified, address is required. If http is specified, url is required.
                      Enum:
                        tcp
                        http
                      Type:  string
                    URL:
                      Description:  URL to perform http health check on. Required when http type is specified. Go template can be used to reference values from the terraform output (e.g. https://example.org, ).
                      Type:         string
                  Required:
                    name
                    type
                  Type:  object
                Type:    array
              Interval:
                Description:  The interval at which to reconcile the Terraform.
                Type:         string
              Path:
                Description:  Path to the directory containing Terraform (.tf) files. Defaults to 'None', which translates to the root path of the SourceRef.
                Type:         string
              Refresh Before Apply:
                Default:      false
                Description:  RefreshBeforeApply forces refreshing of the state before the apply step.
                Type:         boolean
              Retry Interval:
                Description:  The interval at which to retry a previously failed reconciliation. When not specified, the controller uses the TerraformSpec.Interval value to retry failures.
                Type:         string
              Runner Pod Template:
                Properties:
                  Metadata:
                    Properties:
                      Annotations:
                        Additional Properties:
                          Type:       string
                        Description:  Annotations to add to the runner pod
                        Type:         object
                      Labels:
                        Additional Properties:
                          Type:       string
                        Description:  Labels to add to the runner pod
                        Type:         object
                    Type:             object
                  Spec:
                    Properties:
                      Env:
                        Description:  List of environment variables to set in the container. Cannot be updated.
                        Items:
                          Description:  EnvVar represents an environment variable present in a Container.
                          Properties:
                            Name:
                              Description:  Name of the environment variable. Must be a C_IDENTIFIER.
                              Type:         string
                            Value:
                              Description:  Variable references $(VAR_NAME) are expanded using the previously defined environment variables in the container and any service environment variables. If a variable cannot be resolved, the reference in the input string will be unchanged. Double $$ are reduced to a single $, which allows for escaping the $(VAR_NAME) syntax: i.e. "$$(VAR_NAME)" will produce the string literal "$(VAR_NAME)". Escaped references will never be expanded, regardless of whether the variable exists or not. Defaults to "".
                              Type:         string
                            Value From:
                              Description:  Source for the environment variable's value. Cannot be used if value is not empty.
                              Properties:
                                Config Map Key Ref:
                                  Description:  Selects a key of a ConfigMap.
                                  Properties:
                                    Key:
                                      Description:  The key to select.
                                      Type:         string
                                    Name:
                                      Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                                      Type:         string
                                    Optional:
                                      Description:  Specify whether the ConfigMap or its key must be defined
                                      Type:         boolean
                                  Required:
                                    key
                                  Type:  object
                                Field Ref:
                                  Description:  Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.
                                  Properties:
                                    API Version:
                                      Description:  Version of the schema the FieldPath is written in terms of, defaults to "v1".
                                      Type:         string
                                    Field Path:
                                      Description:  Path of the field to select in the specified API version.
                                      Type:         string
                                  Required:
                                    fieldPath
                                  Type:  object
                                Resource Field Ref:
                                  Description:  Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
                                  Properties:
                                    Container Name:
                                      Description:  Container name: required for volumes, optional for env vars
                                      Type:         string
                                    Divisor:
                                      Any Of:
                                        Type:                              integer
                                        Type:                              string
                                      Description:                         Specifies the output format of the exposed resources, defaults to "1"
                                      Pattern:                             ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                                      X - Kubernetes - Int - Or - String:  true
                                    Resource:
                                      Description:  Required: resource to select
                                      Type:         string
                                  Required:
                                    resource
                                  Type:  object
                                Secret Key Ref:
                                  Description:  Selects a key of a secret in the pod's namespace
                                  Properties:
                                    Key:
                                      Description:  The key of the secret to select from.  Must be a valid secret key.
                                      Type:         string
                                    Name:
                                      Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                                      Type:         string
                                    Optional:
                                      Description:  Specify whether the Secret or its key must be defined
                                      Type:         boolean
                                  Required:
                                    key
                                  Type:  object
                              Type:      object
                          Required:
                            name
                          Type:  object
                        Type:    array
                      Env From:
                        Description:  List of sources to populate environment variables in the container. The keys defined within a source must be a C_IDENTIFIER. All invalid keys will be reported as an event when the container is starting. When a key exists in multiple sources, the value associated with the last source will take precedence. Values defined by an Env with a duplicate key will take precedence. Cannot be updated.
                        Items:
                          Description:  EnvFromSource represents the source of a set of ConfigMaps
                          Properties:
                            Config Map Ref:
                              Description:  The ConfigMap to select from
                              Properties:
                                Name:
                                  Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                                  Type:         string
                                Optional:
                                  Description:  Specify whether the ConfigMap must be defined
                                  Type:         boolean
                              Type:             object
                            Prefix:
                              Description:  An optional identifier to prepend to each key in the ConfigMap. Must be a C_IDENTIFIER.
                              Type:         string
                            Secret Ref:
                              Description:  The Secret to select from
                              Properties:
                                Name:
                                  Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                                  Type:         string
                                Optional:
                                  Description:  Specify whether the Secret must be defined
                                  Type:         boolean
                              Type:             object
                          Type:                 object
                        Type:                   array
                      Image:
                        Description:  Runner pod image to use other than default
                        Type:         string
                    Type:             object
                Type:                 object
              Runner Termination Grace Period Seconds:
                Default:      30
                Description:  Configure the termination grace period for the runner pod. Use this parameter to allow the Terraform process to gracefully shutdown. Consider increasing for large, complex or slow-moving Terraform managed resources.
                Format:       int64
                Type:         integer
              Service Account Name:
                Default:      tf-runner
                Description:  Name of a ServiceAccount for the runner Pod to provision Terraform resources. Default to tf-runner.
                Type:         string
              Source Ref:
                Description:  SourceRef is the reference of the source where the Terraform files are stored.
                Properties:
                  API Version:
                    Description:  API version of the referent.
                    Type:         string
                  Kind:
                    Description:  Kind of the referent.
                    Enum:
                      GitRepository
                      Bucket
                      OCIRepository
                    Type:  string
                  Name:
                    Description:  Name of the referent.
                    Type:         string
                  Namespace:
                    Description:  Namespace of the referent, defaults to the namespace of the Kubernetes resource object that contains the reference.
                    Type:         string
                Required:
                  kind
                  name
                Type:  object
              Suspend:
                Description:  Suspend is to tell the controller to suspend subsequent TF executions, it does not apply to already started executions. Defaults to false.
                Type:         boolean
              Vars:
                Description:  List of input variables to set for the Terraform program.
                Items:
                  Properties:
                    Name:
                      Description:  Name is the name of the variable
                      Type:         string
                    Value:
                      X - Kubernetes - Preserve - Unknown - Fields:  true
                    Value From:
                      Description:  EnvVarSource represents a source for the value of an EnvVar.
                      Properties:
                        Config Map Key Ref:
                          Description:  Selects a key of a ConfigMap.
                          Properties:
                            Key:
                              Description:  The key to select.
                              Type:         string
                            Name:
                              Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                              Type:         string
                            Optional:
                              Description:  Specify whether the ConfigMap or its key must be defined
                              Type:         boolean
                          Required:
                            key
                          Type:  object
                        Field Ref:
                          Description:  Selects a field of the pod: supports metadata.name, metadata.namespace, `metadata.labels['<KEY>']`, `metadata.annotations['<KEY>']`, spec.nodeName, spec.serviceAccountName, status.hostIP, status.podIP, status.podIPs.
                          Properties:
                            API Version:
                              Description:  Version of the schema the FieldPath is written in terms of, defaults to "v1".
                              Type:         string
                            Field Path:
                              Description:  Path of the field to select in the specified API version.
                              Type:         string
                          Required:
                            fieldPath
                          Type:  object
                        Resource Field Ref:
                          Description:  Selects a resource of the container: only resources limits and requests (limits.cpu, limits.memory, limits.ephemeral-storage, requests.cpu, requests.memory and requests.ephemeral-storage) are currently supported.
                          Properties:
                            Container Name:
                              Description:  Container name: required for volumes, optional for env vars
                              Type:         string
                            Divisor:
                              Any Of:
                                Type:                              integer
                                Type:                              string
                              Description:                         Specifies the output format of the exposed resources, defaults to "1"
                              Pattern:                             ^(\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))(([KMGTPE]i)|[numkMGTPE]|([eE](\+|-)?(([0-9]+(\.[0-9]*)?)|(\.[0-9]+))))?$
                              X - Kubernetes - Int - Or - String:  true
                            Resource:
                              Description:  Required: resource to select
                              Type:         string
                          Required:
                            resource
                          Type:  object
                        Secret Key Ref:
                          Description:  Selects a key of a secret in the pod's namespace
                          Properties:
                            Key:
                              Description:  The key of the secret to select from.  Must be a valid secret key.
                              Type:         string
                            Name:
                              Description:  Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names TODO: Add other useful fields. apiVersion, kind, uid?
                              Type:         string
                            Optional:
                              Description:  Specify whether the Secret or its key must be defined
                              Type:         boolean
                          Required:
                            key
                          Type:  object
                      Type:      object
                  Required:
                    name
                  Type:  object
                Type:    array
              Vars From:
                Description:  List of references to a Secret or a ConfigMap to generate variables for Terraform resources based on its data, selectively by varsKey. Values of the later Secret / ConfigMap with the samek keys will override those of the former.
                Items:
                  Description:  VarsReference contain a reference of a Secret or a ConfigMap to generate variables for Terraform resources based on its data, selectively by varsKey.
                  Properties:
                    Kind:
                      Description:  Kind of the values referent, valid values are ('Secret', 'ConfigMap').
                      Enum:
                        Secret
                        ConfigMap
                      Type:  string
                    Name:
                      Description:  Name of the values referent. Should reside in the same namespace as the referring resource.
                      Max Length:   253
                      Min Length:   1
                      Type:         string
                    Optional:
                      Description:  Optional marks this VarsReference as optional. When set, a not found error for the values reference is ignored, but any VarsKey or transient error will still result in a reconciliation failure.
                      Type:         boolean
                    Vars Keys:
                      Description:  VarsKeys is the data key where the values.yaml or a specific value can be found at. Defaults to all keys.
                      Items:
                        Type:  string
                      Type:    array
                  Required:
                    kind
                    name
                  Type:  object
                Type:    array
              Write Outputs To Secret:
                Description:  A list of target secrets for the outputs to be written as.
                Properties:
                  Name:
                    Description:  Name is the name of the Secret to be written
                    Type:         string
                  Outputs:
                    Description:  Outputs contain the selected names of outputs to be written to the secret. Empty array means writing all outputs, which is default.
                    Items:
                      Type:  string
                    Type:    array
                Required:
                  name
                Type:  object
            Required:
              interval
              sourceRef
            Type:  object
          Status:
            Description:  TerraformStatus defines the observed state of Terraform
            Properties:
              Available Outputs:
                Items:
                  Type:  string
                Type:    array
              Conditions:
                Items:
                  Description:  Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions.  For example, type FooStatus struct{     // Represents the observations of a foo's current state.     // Known .status.conditions.type are: "Available", "Progressing", and "Degraded"     // +patchMergeKey=type     // +patchStrategy=merge     // +listType=map     // +listMapKey=type     Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
     // other fields }
                  Properties:
                    Last Transition Time:
                      Description:  lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed.  If that is not known, then using the time when the API field changed is acceptable.
                      Format:       date-time
                      Type:         string
                    Message:
                      Description:  message is a human readable message indicating details about the transition. This may be an empty string.
                      Max Length:   32768
                      Type:         string
                    Observed Generation:
                      Description:  observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.
                      Format:       int64
                      Minimum:      0
                      Type:         integer
                    Reason:
                      Description:  reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.
                      Max Length:   1024
                      Min Length:   1
                      Pattern:      ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
                      Type:         string
                    Status:
                      Description:  status of the condition, one of True, False, Unknown.
                      Enum:
                        True
                        False
                        Unknown
                      Type:  string
                    Type:
                      Description:  type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
                      Max Length:   316
                      Pattern:      ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
                      Type:         string
                  Required:
                    lastTransitionTime
                    message
                    reason
                    status
                    type
                  Type:  object
                Type:    array
              Inventory:
                Description:  Inventory contains the list of Terraform resource object references that have been successfully applied.
                Properties:
                  Entries:
                    Description:  Entries of Kubernetes resource object references.
                    Items:
                      Description:  ResourceRef contains the information necessary to locate a resource within a cluster.
                      Properties:
                        Id:
                          Description:  ID is the resource identifier. This is cloud-specific. For example, ARN is an ID on AWS.
                          Type:         string
                        N:
                          Description:  Terraform resource's name.
                          Type:         string
                        T:
                          Description:  Type is Terraform resource's type
                          Type:         string
                      Required:
                        id
                        n
                        t
                      Type:  object
                    Type:    array
                Required:
                  entries
                Type:  object
              Last Applied By Drift Detection At:
                Description:  LastAppliedByDriftDetectionAt is the time when the last drift was detected and terraform apply was performed as a result
                Format:       date-time
                Type:         string
              Last Applied Revision:
                Description:  The last successfully applied revision. The revision format for Git sources is <branch|tag>/<commit-sha>.
                Type:         string
              Last Attempted Revision:
                Description:  LastAttemptedRevision is the revision of the last reconciliation attempt.
                Type:         string
              Last Drift Detected At:
                Description:  LastDriftDetectedAt is the time when the last drift was detected
                Format:       date-time
                Type:         string
              Last Handled Reconcile At:
                Description:  LastHandledReconcileAt holds the value of the most recent reconcile request value, so a change of the annotation value can be detected.
                Type:         string
              Last Planned Revision:
                Description:  LastPlannedRevision is the revision used by the last planning process. The result could be either no plan change or a new plan generated.
                Type:         string
              Observed Generation:
                Description:  ObservedGeneration is the last reconciled generation.
                Format:       int64
                Type:         integer
              Plan:
                Properties:
                  Is Destroy Plan:
                    Type:  boolean
                  Is Drift Detection Plan:
                    Type:  boolean
                  Last Applied:
                    Type:  string
                  Pending:
                    Type:  string
                Type:      object
            Type:          object
        Type:              object
    Served:                true
    Storage:               true
    Subresources:
      Status:
Status:
  Accepted Names:
    Kind:       Terraform
    List Kind:  TerraformList
    Plural:     terraforms
    Short Names:
      tf
    Singular:  terraform
  Conditions:
    Last Transition Time:  2022-08-19T07:29:14Z
    Message:               no conflicts found
    Reason:                NoConflicts
    Status:                True
    Type:                  NamesAccepted
    Last Transition Time:  2022-08-19T07:29:14Z
    Message:               the initial names have been accepted
    Reason:                InitialNamesAccepted
    Status:                True
    Type:                  Established
  Stored Versions:
    v1alpha1
Events:  <none>

Thank you @mjazwiecki
I'll investigate more into this issue on an Azure cluster.

I am not sure about MSI but I am able to get it to work with a service principal. Following the azurerm documentation, I am using ARM_CLIENT_ID and ARM_CLIENT_SECRET env vars.
The terraform CR looks like this:
apiVersion: infra.contrib.fluxcd.io/v1alpha1
kind: Terraform
metadata:
  name: example
  namespace: tf-controller
spec:
  interval: 5m
  approvePlan: "auto"
  destroyResourcesOnDeletion: true
  path: ./
  backendConfig:
    customConfiguration: |
      backend "azurerm" {
        storage_account_name = "abc"
        container_name       = "tfstate"
        key                  = "terraform.tfstate"
        resource_group_name  = "abc"
        subscription_id      = "xxx"
        tenant_id            = "xxx"
      }
  sourceRef:
    kind: GitRepository
    name: XXX
    namespace: XXX
  runnerPodTemplate:
    spec:
      env:
      - name: ARM_CLIENT_ID
        valueFrom:
          secretKeyRef:
              name: client_id
              key: value
      - name: ARM_CLIENT_SECRET
        valueFrom:
          secretKeyRef:
              name: client_secret
              key: value

Thank you @tomhuang12
As now it's possible to supply ARM_* via environment variables of the runnerPodTemplate, I shall close this issue.
@mjazwiecki please feel free to re-open it if the problem still persists in your setup


add Document Information Extraction API client (continued)

This PR adds the DoxApiClient class to access the SAP Document Information Extraction REST API.
(It is a continuation of this pull request.)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Pagination: future feature

Currently, the nested Select component has 10/20/30 fixed values, which are used for setting the per-page option.
Consider the possibility of using an algorithm for automatically determining the per-page option values.

There is multiple use-cases for this improved pagination-component within multiple of our internal applications, which would make this a big improvement.
I think giving the developer the freedom to pass in n-amount of numbers would be a much greater benefit than replacing it with a automatic system.
To give further feedback - best suited would be to:

pass an array of n-amount of elements as a property e.g. [10, 20, 50, 100, ...]
have a property to include a "all"-option within the select


[Bug Report] "el-time-select" does not emit "change" when attribute "editable" is true and time is manually entered

Element UI version
2.5.4
OS/Browsers version
Ubuntu 18.04 LTS/ Chrome 72
Vue version
2.6.6
Reproduction Link
https://jsfiddle.net/ruL2qaxn/
Steps to reproduce
Manually enter a value for the first time picker and then tab to the second time picker.
In the console, notice that no "change" was emitted.
The second time picker has a "minTime" set to value1.
The drop down for the second time picker does not have the minTime set from the first time picker.
What is Expected?
Make sure the Chrome Console is open.
When the attribute "editable" is true (default) that when a user types in a value that matches one of the selectable values and tabs, then that value will automatically be selected and a "change" emits occurs. You would be able to verify this happens in the console with the console.log() output.
Also, if the user types in a value that doesn't match one of the selectable parameters, when they tab, it would clear the editable area as leaving it there is misleading. (for example the user types "03" instead of "00" and then tabs, the bad value stays i.e 00)
What is actually happening?
No "change" signal is emitted when a user manually enters a value when the "editable" value is set to true.

I can't reproduce this bug, can you update the "steps to reproduce" section, please?

同样问题，无法编辑时，不显示时间


Can't drop Pineapple

While thieving the fruit stalls, some fruit are eaten or dropped, but the Pineapple can't be either dropped or eaten, it just keeps the ''use''.

New version will be doing this.


fix wine offers, permanent values for miracles and population delegation

Bug solution

@charlizzin I tested the commit 8d4ef87 and unfortunately it doesn't work. Didn't test the other commut regarding the accountStatus

@charlizzin @coecharlin It would be better to have one pull request per feature. I have the impression that you're inadvertently pushing changes to the same branch.

@charlizzin @coecharlin I appreciate the willingness to correct bugs, but it would be better to have one pull request per feature. I have the impression that you're inadvertently pushing changes to the same branch. Since your branch is called newBranch, I think you must be messing with git. I advise you to create a branch for each feature. Then create a pull request as soon as you're happy with the changes. Once you've made the pull request. Leave the branch as is until the pull request is accepted.

Just to clarify, I've tested all 3 commits and they work. There are issue/request topics for all three commits as well

Sorry, guys. I got carried away with the corrections, and since I don't have experience with GitHub, I didn't present the solutions in the ideal places.

@coecharlin @johnvittu @charlizzin I've taken the liberty of making a few changes. I think the PR is ready to be merged now. Let me know if that's ok with you

@coecharlin @johnvittu @charlizzin I've taken the liberty of making a few changes. I think the PR is ready to be merged now. Let me know if that's ok with you

Green light from me, no issues. I've been waiting for this quite some time. :P


Release 4.2.1, Nuget package wrong targetFramework

In your latest release, the Forti.dll is compiled against .NET 4.5.2 instead of 4.5 as expected in the net45 folder.
Please rectify if Fortis can support 4.5, if not remove the folder all together.

the Nuget package has been updated to put the binary into the net452 folder. As MS support has dropped for 4.5 and 4.5.1 we will not be adding binaries compiled against those versions.


CONTRIBUTING.md: Use build --stage 1 instead of build --stage 2

It seems to work fine with --stage 1 and it should be faster.
Cc #1610
Cc @jyn514

It seems to work fine with --stage 1 and it should be faster.

It should be barely any faster, both build rustc exactly twice... the only extra work that --stage 1 compiler/rustc does is some uplifting I think.
So I doubt this actually makes things much faster.

I tested this, and indeed (to my great surprise) after doing --stage 1 compiler/rustc, using the stage 1 compiler with Miri actually works. Maybe proc-macros are more decoupled from rustc now than they used to be, or maybe I never tested this particular combination of things... not sure.
However, after --stage 1 compiler/rustc is complete, doing --stage 2 compiler/rustc takes <5s. It just copies some things around:
$ nice ./x.py -j4 build --stage 2 compiler/rustc
    Finished dev [unoptimized + debuginfo] target(s) in 0.76s
Building stage0 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
    Finished release [optimized + debuginfo] target(s) in 0.31s
Copying stage0 std from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
    Finished release [optimized + debuginfo] target(s) in 0.68s
Copying stage0 rustc from stage0 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Assembling stage1 compiler (x86_64-unknown-linux-gnu)
Building stage1 std artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
    Finished release [optimized + debuginfo] target(s) in 0.15s
Copying stage1 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage1 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
    Finished release [optimized + debuginfo] target(s) in 0.33s
Copying stage1 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Assembling stage2 compiler (x86_64-unknown-linux-gnu)
Uplifting stage1 std (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
Copying stage2 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Uplifting stage1 rustc (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Build completed successfully in 0:00:04

So this does not actually save any time. But it seems conceptually simpler, so recommending stage 1 still seems like a good idea.

@camelid what are your plans for this PR? It is currently also blocking https://github.com/rust-lang/miri/pull/1615, so it'd be rgeat if you could take care of the remaining concern. :)

@RalfJung I think I must have thought there was something else to do, but it seems not. Ready to be merged!

Thanks! @bors r+

:pushpin: Commit 6a475c3ddf8ee0868f0723683aa2720e8f87d44a has been approved by RalfJung

:hourglass: Testing commit 6a475c3ddf8ee0868f0723683aa2720e8f87d44a with merge 85a9a43bef0d69eb63c62f9d0d8304f6f226e7e3...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 85a9a43bef0d69eb63c62f9d0d8304f6f226e7e3 to master...


Display two extra invalid folders after uploading the "dist" folder to a Local Emulator blob container

OS: All
Build Version: 20201011.1
Repro Steps:

Expand the Local Emulator -> Blob Containers -> Right click the blob container -> Select "Upload Folder..." -> Select the "dist" folder to upload.
Check the result.

Expect:
There is no extra invalid folder.
Actual:
There are multiple "Load More..." -> Click the "Load More..." -> Display two extra invalid folders.

More Info:
This issue doesn't reproduces after uploading the "dist" folder to a storage account blob container.

Which version of Azurite did you encounter this with?

Storage Extension Version : 20201014.1
Azurite Version : 3.9.0
This issue also reproduces for now.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


Update react and webpack versions

Make the react and webpack versions up to date.
Update if any other packages if necessary.

Updated all the packages possible.


Adding examples to QHub jupyterlab

Closes #1175
Effort was put into making these examples as small as possible. Totally agree that down the road we need to put more effort into these examples.
Also switched to using fileset in the config maps so that we do not have to explicitely include each file. fileset will grab all the files.

I have tested manually that all these dashboards work along with the dask gateway example.


youtrack: 2024.2.37269 -> 2024.2.40106

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for youtrack is: Issue tracking and project management tool for developers
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.2.38971 with grep in /nix/store/z1k54kvwihbzggxd14crs6m5idci0i5b-youtrack-2024.2.38971
found 2024.2.38971 in filename of file in /nix/store/z1k54kvwihbzggxd14crs6m5idci0i5b-youtrack-2024.2.38971

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

youtrack

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z1k54kvwihbzggxd14crs6m5idci0i5b-youtrack-2024.2.38971 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A youtrack https://github.com/r-ryantm/nixpkgs/archive/a6d8741ae7e56b0958c35e1e9a82a872a2ddebfc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a6d8741ae7e56b0958c35e1e9a82a872a2ddebfc#youtrack

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z1k54kvwihbzggxd14crs6m5idci0i5b-youtrack-2024.2.38971
ls -la /nix/store/z1k54kvwihbzggxd14crs6m5idci0i5b-youtrack-2024.2.38971/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

youtrack

Maintainer pings
cc @balsoft @leona-ya for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for youtrack is: Issue tracking and project management tool for developers
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.2.40106 with grep in /nix/store/dnd7wscq48dfkhgnqpszrzcls17pq785-youtrack-2024.2.40106
found 2024.2.40106 in filename of file in /nix/store/dnd7wscq48dfkhgnqpszrzcls17pq785-youtrack-2024.2.40106

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

youtrack

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/dnd7wscq48dfkhgnqpszrzcls17pq785-youtrack-2024.2.40106 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A youtrack https://github.com/r-ryantm/nixpkgs/archive/9d628e393320be48553be8177aeab75024a4ac5b.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9d628e393320be48553be8177aeab75024a4ac5b#youtrack

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/dnd7wscq48dfkhgnqpszrzcls17pq785-youtrack-2024.2.40106
ls -la /nix/store/dnd7wscq48dfkhgnqpszrzcls17pq785-youtrack-2024.2.40106/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

youtrack

Maintainer pings
cc @balsoft @leona-ya for testing.

Add a :+1: reaction to pull requests you find important.


Upgrade oauth2-proxy chart

Is your feature request related to a problem? Please describe.
From:
chartVersion: v7.1.3
appVersion: 2.4.1

To:
chartVersion: 7.4.0
appVersion: 6.12.0

See: https://artifacthub.io/packages/helm/oauth2-proxy/oauth2-proxy
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features
you've considered.
Additional context Add any other context or screenshots about the feature request here.

Updated oauth2-proxy chart to version 3.7.4. AppVersion = 7.4.0.
As part of the major update to version 3.*, the redis subchart is now added to the oauth2-proxy chart. As such I'm disabling the current redis and using adapting the go template for the new redis subchart.
Updating in place turned out to be quite problematic so I updated the upgrade script to delete the oauth2-proxy and oauth2-proxy-redis releases before upgrading to the new version. Created PR

Tested upgrade path from v0.22.1 on k8s v1.24 and v1.25:  Success


Concider making Replica and DependencyMap traits

As some DBMSs (like SurrealDB) might be able to represent for example dependencies straight from the DB it might be a good idea to abstract the Replica and DependencyMap to traits so that they can be given other Solutions than the way Rust implementation handles calculating dependencies, it might be a good idea to make Traits for these.
In some cases this might help as Well with bindings to other languages/platforms

There are some constraints on the data format that might make such usage difficult:

tasks have dep_... properties to represent dependencies, as part of the public API for tasks
changes to tasks are modeled as operations, adding or removing key/value pairs

That said, I'm interested in what you have in mind. A concrete case for storing task data in a different backend would help to clarify where these interfaces need to be changed.
Note also #372 is going to happen soon, and will modify the TC API pretty substantially.

I'll try to Create an example, it might take some time though

I will try to implement most of the system straight into SurrealDB to showcase the possibilities. Of course it might sometimes be better to use dedicated code for this but i think creating as much funtionality as possible, straight in the db shows the ideas better.
Also was thinking of trying out using BerkleyDB or rocksDB etc for the storage layer just to see if there is difference in the perfornabce

Sounds good!

It might make more sense to create a struct that implements the Storage (and StorageTxn) traits, instead of a replica.
The set of methods provided in StorageTxn probably deserves some scrutiny: lots of very common things, such as determining whether a task is BLOCKED or BLOCKING, currently require scanning all pending tasks, which is pretty expensive.
Let's see if this bug branches in either of those directions: creating a new storage backend using SurrealDB; or modifying the StorageTxn methods to improve performance.

There's some discussion in https://github.com/GothenburgBitFactory/taskchampion/discussions/472 of making it possible to express filter expressions in a way that the storage backend could, optionally, interpret for the caller. I think that covers part of what is proposed here, but dependency maps are not mentioned. I'll add a note about that, and close this issue in favor of that discussion.


HTTP request sent, awaiting response... 404 Not Found When downloading rt.cx/ee

root@mail:~# wget -O ee rt.cx/ee
--2016-11-04 10:23:58--  http://rt.cx/ee
Resolving rt.cx (rt.cx)... <IP_ADDRESS>
Connecting to rt.cx (rt.cx)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://raw.githubusercontent.com/EasyEngine/easyengine/master/install [following]
--2016-11-04 10:23:58--  https://raw.githubusercontent.com/EasyEngine/easyengine/master/install
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-11-04 10:24:04 ERROR 404: Not Found.
Please attach the output of following command when open a new support request.

[x] lsb_release -a
root@mail:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 8.6 (jessie)
Release:	8.6
Codename:	jessie

Please try below command for Installation
wget -qO ee rt.cx/ee && sudo bash ee


forever.js is masking errors, not helping

If something is wrong with the underlying mongod, forever will just spin in an eternal loop, adding load to the host system and not successfully starting up:
5 Feb 19:15:10 - info: process id:7401
25 Feb 19:15:11 - info: Starting locker with build info:{ "build" : "604", "gitrev" : "53718d9" }
25 Feb 19:15:11 - info: [mongo] note: noprealloc may hurt performance in many applications
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] MongoDB starting : pid=7404 port=27018 dbpath=/home/Me/mongodata 64-bit host=locker_d+singly_at_waferbaby_com
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] db version v2.0.2, pdfile version 4.5
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] git version: 514b122d308928517f5841888ceaa4246a7f18e3
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] build info: Linux bs-linux64.10gen.cc <IP_ADDRESS>-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] options: { dbpath: "/home/Me/mongodata", nohttpinterface: true, nojournal: true, noprealloc: true, port: 27018 }
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] exception in initAndListen: 10310 Unable to acquire lock for lockfilepath: /home/Me/mongodata/mongod.lock, terminating
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 dbexit:
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] shutdown: going to close listening sockets...
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] shutdown: going to flush diaglog...
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] shutdown: going to close sockets...
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] shutdown: waiting for fs preallocator...
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] shutdown: closing all files...
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 [initandlisten] closeAllFiles() finished
25 Feb 19:15:11 - info: [mongo] Sat Feb 25 19:15:11 dbexit: really exiting now
25 Feb 19:15:11 - error: mongod exited unexpectedly with code 100, signal null
warn: Forever detected script exited with code: 0
warn: Forever restarting script for 1041 time
The "sys" module is now called "util". It should have a similar interface.
25 Feb 19:15:43 - info: process id:7408
25 Feb 19:15:46 - info: Starting locker with build info:{ "build" : "604", "gitrev" : "53718d9" }

25 Feb 19:15:46 - info: [mongo] note: noprealloc may hurt performance in many applications
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] MongoDB starting : pid=7411 port=27018 dbpath=/home/Me/mongodata 64-bit host=locker_d+singly_at_waferbaby_com
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] db version v2.0.2, pdfile version 4.5
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] git version: 514b122d308928517f5841888ceaa4246a7f18e3
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] build info: Linux bs-linux64.10gen.cc <IP_ADDRESS>-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] options: { dbpath: "/home/Me/mongodata", nohttpinterface: true, nojournal: true, noprealloc: true, port: 27018 }
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] exception in initAndListen: 10310 Unable to acquire lock for lockfilepath: /home/Me/mongodata/mongod.lock, terminating
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 dbexit:
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] shutdown: going to close listening sockets...
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] shutdown: going to flush diaglog...
25 Feb 19:15:46 - error: mongod exited unexpectedly with code 100, signal null
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] shutdown: going to close sockets...
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] shutdown: waiting for fs preallocator...
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] shutdown: closing all files...
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 [initandlisten] closeAllFiles() finished
25 Feb 19:15:46 - info: [mongo] Sat Feb 25 19:15:46 dbexit: really exiting now
warn: Forever detected script exited with code: 0
warn: Forever restarting script for 1042 time

Forever is gone as of build 609


[BUG] Fatal Exception: com.facebook.react.bridge.JSApplicationIllegalArgumentException

Bug Report
Current behavior

AgoraManager.java line 81
com.syan.agora.AgoraManager.setupLocalVideo

Steps to reproduce

I do not know how to reproduce, because it was catch at our bug tracker.

Relevant logs and/or screenshots

if anyone can reproduce it, pls provide ur step and description here, then reopen thx.


change private-net to net and rework options

Seems OK from a first pass, though obvs needs various documentation updates

/cc @eyakubovich

cc @yifan-gu as will need a patch for kubernetes after this.

@robszumski @eyakubovich @jonboulle
UX design question. what's most intuitive to pass to rkt for keeping the caller's network namespace:

--net=host could be inaccurate if the caller is not in the host netns
--net=shared could lead people on to believe it's a special container shared network mode
--net=inherit seems self-explanatory (my favourite)

If this is primarily going to be used from the host netns, it seems like we should go with --net=host for consistency with docker. If not, --net=inherit is probably best.

I like inherit too, but if we do have that near-effective parity with
docker then --host with an explanation about the inheritance would be
fine.
On Sun, Oct 4, 2015 at 12:00 PM, Rob Szumski<EMAIL_ADDRESS>wrote:

If this is primarily going to be used from the host netns, it seems like
we should go with --net=host for consistency with docker. If not,
--net=inherit is probably best.
—
Reply to this email directly or view it on GitHub
https://github.com/coreos/rkt/pull/1532#issuecomment-145375224.

Grml.. to me similarity to Docker only nice to have but I wouldn't sacrifice correctness for that sake. It's just that our own code calls it "hostNS" in many places too and I don't want to go on a rename rampage now.

PR rebased to resolve conflicts.
PTAL

I'm pretty sure that the semaphoreci fail reason rkt_fetch_test.go:217: "remote fetching from url https://github.com/coreos/etcd/releases/download/v2.1.2/etcd-v2.1.2-linux-amd64.aci" should be found is unrelated here.

Hmm, I am not sure about --net=none. There's a use case for pods with no network interfaces/access whatsoever. How can we facilitate that?

I would leave --net=none with just default-restricted interface for now. It's slightly incorrect but it does not inhibit the use of metadata service and break ACE correctness.

Code LGTM. Docs are addressed by @jonboulle
As far as --net=host vs --net=inherit, I agree that inherit is more correct but to the end-user that doesn't think about how namespaces form a hierarchy, I think "host networking" is more intuitive.

LGTM. Anyone else? This is quite a big change. @iaguis @blixtra @krnowak

Also will obviously need rebasing, probably once #1569 lands.

There are still some --private-net mentions left (e.g. https://github.com/steveeJ/rkt/blob/private-network-default/rkt/prepare.go#L53 or https://github.com/steveeJ/rkt/blob/private-network-default/Documentation/subcommands/run.md#private-networking)

LGTM


Formatting fix for example of ZWED0021I message

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[X] If the changes in this PR is part of the next future release, make this pull request against the docs-staging branch which will be published at the next release boundary. If the changes in this PR are part of the current release, use the default base branch, master. For more information about branches, see https://github.com/zowe/docs-site/tree/master#understanding-the-doc-branches.

[ ] If this PR relates to GitHub issues in docs-site or other repositories, please list in Description, prefixed with close, fix or resolve keywords.

Description (including links to related git issues)
Fix of formatting problem in https://docs.zowe.org/stable/troubleshoot/troubleshoot-zos.html#check-the-startup-of-zowe-desktop where the error message can't be viewed in the docs

:heart:Thank you!

@Joe-Winchester Hi Joe, this PR also includes two new files  docs/developer-guide/dev-building-zowe.md and docs/developer-guide/dev-pipeline-zowe.md. Do you intend to merge them as well? If it's only for the message formatting fix, you might want to move the fix to a new branch and re-create a PR.

@Joe-Winchester Hi Joe, this PR also includes two new files docs/developer-guide/dev-building-zowe.md and docs/developer-guide/dev-pipeline-zowe.md. Do you intend to merge them as well? If it's only for the message formatting fix, you might want to move the fix to a new branch and re-create a PR.

Thank you @nannanli for picking up on this.  I've removed the other two files which are on an unrelated doc issue I was working on.


Error trying to "npm start" ui_ng (after adding empty proxy.config.json) - Cannot find module '../aot/src/app/app.module.ngfactory'

OS: Windows 10 enterprise
Node v8.9.4
NPM v5.6.0
If you are reporting a problem, please make sure the following information are provided:
1)Version of docker engine and docker-compose.
n/a
2)Config files of harbor, you can get them by packaging "harbor.cfg" and files in the same directory, including subdirectory.
n/a
3)Log files, you can get them by package the /var/log/harbor/ .
PS C:\Users\rothandr\repos\mrp\harbor\src\ui_ng> npm start

><EMAIL_ADDRESS>start C:\Users\rothandr\repos\mrp\harbor\src\ui_ng
> ng serve --ssl 1 --ssl-key ssl/server.key --ssl-cert ssl/server.crt --host <IP_ADDRESS> --proxy-config proxy.config.json

** NG Live Development Server is listening on <IP_ADDRESS>:4200, open your browser on https://localhost:4200/ **
 10% building modules 2/2 modules 0 activeGenerating SSL Certificate                                                                                Date: 2018-03-08T20:52:03.692ZHash: 72df71a13fdc907fbf9e
Time: 31963ms
chunk {inline} inline.bundle.js (inline) 3.85 kB [entry] [rendered]
chunk {main} main.bundle.js (main) 1.81 MB [initial] [rendered]
chunk {scripts} scripts.bundle.js (scripts) 675 kB [initial] [rendered]
chunk {styles} styles.bundle.js (styles) 1.13 MB [initial] [rendered]
chunk {vendor} vendor.bundle.js (vendor) 16.4 MB [initial] [rendered]

ERROR in C:/Users/rothandr/repos/mrp/harbor/src/ui_ng/src/main-aot.ts (6,36): Cannot find module '../aot/src/app/app.module.ngfactory'.

webpack: Failed to compile.

Hi @RothAndrew , can you clarify this issue?
Are your try to run or build harbor on windows? If so, harbor has not support windows yet.

close it as no activity.


Streaming (WIP)

Rollout requirements (WIP):

[ ] Get stream_results to work with non-streamed
[ ] Consider adding tags
[ ] Add halt_before to streaming

OK, basic POC is working. To get this to production, we need:

[ ] Docs

[ ] Overview of streaming
[ ] Reference API

[ ] Demo

[ ] Add gpt-streaming

[ ] Features

[ ] Get halt_before to work -- this has the same behavior

[ ] StreamingResultContainer.is_empty -- this allows halt_before

[ ] Get the stream call to work with non-streaming results

[ ] Polish

[ ] Break into commits
[ ] Add docstrings for all new methods
[ ]  Change StreamingResultContainer to StreamOutput - feels cleaner/less stuffy
[ ] Implement this for consistency: https://github.com/DAGWorks-Inc/burr/issues/63

[ ] Testing

[ ] Add another E2E test for halt_before/halt_after
[ ] Test it out with streamlit

[ ] Async generators

[ ] Implement
[ ] Test


peerDependencies are missing in the next releases

I'd like to test the next releases but the peerDependencies defined in master are missing.

I think this should be fixed in next.41. I wanted to make the imports optional instead of being peerDependencies because they're not required for usage in all platforms. I think it's correct now. Please let me know if it's still not right :)

Nope, I get the same errors as before, react isn't installed. Optional provides no guarantee from what I can tell, so I guess pnpm doesn't install/create the symlinks in a pnpm workspace setup?

I'm also seeing this weird error now:

Oh it's react that's the issue? Do you have react installed and it's not resolving it? Or are you using it without react?
I haven't used pnpm so I'm not sure how it works. In npm/yarn/bun I believe it resolves dependencies correctly if they're installed even if not specified in the package. Does pnpm require the package to list its dependences?
I don't want to make react a required dependency because the core should be usable without react, and I'd like to expand to other frameworks.
Do you (or anyone) know how to fix this correctly? One solution could be to make the react features a completely separate package that has react as a dependency, but I'm hoping there's an easier way?

No need to make React a required dependency. It should be just like it was before a peer dependency.
From https://classic.yarnpkg.com/lang/en/docs/dependency-types/#toc-peerdependencies
Peer dependencies are a special type of dependency that would only ever come up if you were publishing your own package.
Having a peer dependency means that your package needs a dependency that is the same exact dependency as the person installing your package. This is useful for packages like react that need to have a single copy of react-dom that is also used by the person installing it.


Pin coverage < 4.4 to prevent spurious CI failures

Pending a fix here: https://bitbucket.org/ned/coveragepy/issues/581/44b1-44-breaking-in-ci

Coverage remained the same at 94.541% when pulling 11b2051f4b8eece662c728a1d6393ebcc2508a68 on fix-coverage into 19e2ce69e49f78c8675821d6d5f5fabc3c0ab474 on master.


When Displaying a MessageBox this can happen !

Unhandled Application Exception
System.NullReferenceException: Object reference not set to an instance of an object.
at ComponentFactory.Krypton.Toolkit.KryptonMessageBox.UpdateMessageSizing(IWin32Window showOwner)
at ComponentFactory.Krypton.Toolkit.KryptonMessageBox.UpdateSizing(IWin32Window showOwner)
at ComponentFactory.Krypton.Toolkit.KryptonMessageBox.InternalShow(IWin32Window owner, String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon, MessageBoxDefaultButton defaultButton, MessageBoxOptions options, HelpInfo helpInfo)
at ComponentFactory.Krypton.Toolkit.KryptonMessageBox.Show(String text, String caption, MessageBoxButtons buttons, MessageBoxIcon icon)
atProgramBase.Start()
OK

I suspect it has something to do with the this being passed in for the owner being null But I am unsure.

May need a try/catch statement in the KryptonMessageBox code to prevent nullable failovers. Is this happening since I've restructured the source folder?

Ok, by the way, I've redone the Palette Upgrade Tool that was present in the commercial version before Phil Wright made it open source. It is not currently in the original repo. Might be useful for the extended toolkit project.

Tested - Now fixed :-)


⚠ Bofrost.at has degraded performance

In 496806f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1893 ms

Resolved: Bofrost.at performance has improved in 0cc2bf2 after 6 minutes.


Write hosted intermediary

Write a Java server using spring boot that gets the MQTT message and use IOTT SDK for integration in that direction.
DoD:

[ ] Receives messages from matterHub via MQTT
[ ] Forwards messages to IOTT cloud
[ ] Receives messages from IOTT cloud
[ ] Forwards messages to matterHub via MQTT

https://search.maven.org/search?q=g:org.eclipse.paho AND a:org.eclipse.paho.client.mqttv3


test: issue 5868

Redmine ticket:
https://redmine.openinfosecfoundation.org/issues/5868

Suricata PR is https://github.com/OISF/suricata/pull/8954

Merged in https://github.com/OISF/suricata-verify/pull/1316 right ?


How to grant permission access data don't need confirm on web interface when run on server command?

@jfschmakeit  When I run my application on Window OS I will can interact with UI to grant permission but I want run it on server only have command. Do you have way to by pass it ?
Thanks!

The Google Photos Library API requires user OAuth credentials. Service accounts or other non-interactive credenials are not supported. You can find more details on the Authentication and Authorization page in the developer documentation.
The only way to obtain these credentials is to prompt the user via a URL to authorize access.


Multi-agent control scenarios

Hi, thanks for the work.
Just one small question regarding multi-agent control scenarios. When controlling a group of vehicles rather than one, it is usually desired that the initial positions of controled vehicles are close to each other, like a swarm of fleet.
So, just wondering if it is possible to config initial positions of controlled vehicles?
And also, crash = True when controlled vehicles collide with each other.
Thanks very much!

Hi @sunningshore
You may have a look at https://github.com/eleurent/highway-env/issues/260 which was a related question about initial speed.
TLDR: there is unfortunately no easy way to do that for now, as the initial scene is environment dependent and I find it a bit difficult to make it fully configurable. Possible solutions are:

you clone the project and edit the _create_vehicles() method of your favorite environment to place the vehicles wherever you like.
you manually set the position of each vehicle right after calling env.reset(), something like:

env.reset()
for vehicle in env.controlled_vehicles:
    vehicle.position = np.array([<desired x, desired y>])

But you need to to it everytime you reset the environment, and make sure you don't place a the vehicles near an obstacle, so I'd recommend solution 1.

And also, crash = True when controlled vehicles collide with each other.

Ooops, is this not the case already? I'll look into that.

Hi Edouard,
Thanks for your kind reply. This can certainly solve the problem.
“And also, crash = True when controlled vehicles collide with each other.
Ooops, is this not the case already? I'll look into that.”
Sorry, I have no idea. Because the 2 vehicles I created are always far from each other. But it’s good if it is already the case.
Best!
From: Edouard Leurent @.>
Sent: Sunday, January 23, 2022 5:29 AM
To: eleurent/highway-env @.>
Cc: MUXU @.>; Mention @.>
Subject: Re: [eleurent/highway-env] Multi-agent control scenarios (Issue #261)
Hi @sunningshore https://github.com/sunningshore
You may have a look at #260 https://github.com/eleurent/highway-env/issues/260  which was a related question about initial speed.
TLDR: there is unfortunately no easy way to do that for now, as the initial scene is environment dependent and I find it a bit difficult to make it fully configurable. Possible solutions are:

you clone the project and edit the _create_vehicles() method of your favorite environment to place the vehicles wherever you like.
you manually set the position of each vehicle right after calling env.reset(), something like:

env.reset()
for vehicle in env.controlled_vehicles:
vehicle.position = np.array([<desired x, desired y>])
But you need to to it everytime you reset the environment, and make sure you don't place a the vehicles near an obstacle, so I'd recommend solution 1.
And also, crash = True when controlled vehicles collide with each other.
Ooops, is this not the case already? I'll look into that.
—
Reply to this email directly, view it on GitHub https://github.com/eleurent/highway-env/issues/261#issuecomment-1019303194 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QP67FCPNR4R5AVJMZA4LUXLLLBANCNFSM5MLUABJA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AD2QP62ZAPFMGMJAXWA7PNLUXLLLBA5CNFSM5MLUABJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHTAVKGQ.gif Message ID: @.*** @.***> >

Hi Edouard,
It worked, thanks.
“And also, crash = True when controlled vehicles collide with each other.
Ooops, is this not the case already? I'll look into that.”
And it is the case already.
Thanks.
From: @.*** @.>
Sent: Sunday, January 23, 2022 12:12
To: 'eleurent/highway-env' @.>; 'eleurent/highway-env' @.>
Cc: 'Mention' @.>
Subject: RE: [eleurent/highway-env] Multi-agent control scenarios (Issue #261)
Hi Edouard,
Thanks for your kind reply. This can certainly solve the problem.
“And also, crash = True when controlled vehicles collide with each other.
Ooops, is this not the case already? I'll look into that.”
Sorry, I have no idea. Because the 2 vehicles I created are always far from each other. But it’s good if it is already the case.
Best!
From: Edouard Leurent @.*** @.> >
Sent: Sunday, January 23, 2022 5:29 AM
To: eleurent/highway-env @. @.> >
Cc: MUXU @. @.> >; Mention @. @.***> >
Subject: Re: [eleurent/highway-env] Multi-agent control scenarios (Issue #261)
Hi @sunningshore https://github.com/sunningshore
You may have a look at #260 https://github.com/eleurent/highway-env/issues/260  which was a related question about initial speed.
TLDR: there is unfortunately no easy way to do that for now, as the initial scene is environment dependent and I find it a bit difficult to make it fully configurable. Possible solutions are:

you clone the project and edit the _create_vehicles() method of your favorite environment to place the vehicles wherever you like.
you manually set the position of each vehicle right after calling env.reset(), something like:

env.reset()
for vehicle in env.controlled_vehicles:
vehicle.position = np.array([<desired x, desired y>])
But you need to to it everytime you reset the environment, and make sure you don't place a the vehicles near an obstacle, so I'd recommend solution 1.
And also, crash = True when controlled vehicles collide with each other.
Ooops, is this not the case already? I'll look into that.
—
Reply to this email directly, view it on GitHub https://github.com/eleurent/highway-env/issues/261#issuecomment-1019303194 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2QP67FCPNR4R5AVJMZA4LUXLLLBANCNFSM5MLUABJA .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AD2QP62ZAPFMGMJAXWA7PNLUXLLLBA5CNFSM5MLUABJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHTAVKGQ.gif Message ID: @.*** @.***> >

Great :) Closing this, but feel free to open another one if you have more questions


how to convert a wl_surface pointer to WlSurface

I get the wl_surface pointer from https://docs.rs/raw-window-handle/0.6.0/raw_window_handle/struct.WaylandWindowHandle.html#structfield.surface
however when I want to use wayland-client WlSurface, I didn't find a function or method to convert the wl_surface pointer to WlSurface
is there any way to do this job? can I just convert the pointer to *mut WlSurface and then convert to &mut WlSurface

I guess the generated API docs are build without the wayland-backend/client_system feature, so ObjectId::from_ptr isn't listed. You'll need that feature, then ObjectId::from_ptr, then WlSurface::from_id (from the Proxy trait).
https://github.com/rust-windowing/softbuffer/blob/5c7a2099e00a6c5e1e8eb3f65f05596a3f1c6db2/src/backends/wayland/mod.rs#L159-L167 for instance creates a WlSurface from a raw-window-handle.

thank you, it solved my problem


BigQuery Dialect - CREATE TABLE CLONE and COPY

Hi, All
just wondering if there is a support coming for these bigquery statements?
CREATE TABLE `tbl`
CLONE `src_tbl`;

CREATE TABLE `tbl`
COPY `src_tbl`

reference: https://cloud.google.com/bigquery/docs/reference/standard-sql/data-definition-language#create_table_copy
currently, I'm encountering this limitation below.
com.google.zetasql.SqlException: CREATE TABLE CLONE is not supported [at 4:7]

edit: it seems COPY is supported, only CLONE is not supported.
Thank you!

Support in the evaluator is not likely, but it is supported in the various other api calls (Analyzer.java).
You may need to modify the LanguageOptions to enable the statements you need enabled:
You can see an example here:
https://github.com/google/zetasql/blob/206e78c86a85053f2c0d75db6fa7b1998181263b/javatests/com/google/zetasql/AnalyzerTest.java#L284
AnalyzerOptions analyzerOptions = new AnalyzerOptions();
analyzerOptions
    .getLanguageOptions()
    .setSupportedStatementKinds(ImmutableSet.of(ResolvedNodeKind.RESOLVED_CREATE_TABLE_STMT));
Analyzer.analyzeStatement(sql, analyzerOptions, new SimpleCatalog(""))

Hi,
CLONE query works for me.
CREATE TABLE .<dataset_name>.<cloned_table_name>
CLONE .<dataset_name>.<original_table_name> FOR SYSTEM_TIME AS OF CURRENT_TIMESTAMP();


Sample Test Scenario

Test Scenario
Feature: Guess the word

  # The first example has two steps
  Scenario: Maker starts a game
    When the Maker starts a game
    Then the Maker waits for a Breaker to join

  # The second example has three steps
  Scenario: Breaker joins a game
    Given the Maker has started a game with the word "silky"
    When the Breaker joins the Maker's game
    Then the Breaker must guess a word with 5 characters

Additional Instructions
No response

this is so cool, can I see how guys are using it, @paulushcgcj @DerekRoberts

@mishraomp I'm useless! Let's both ask @paulushcgcj. :P

@mishraomp I'm useless! Let's both ask @paulushcgcj. :P

understood, the usage from here, https://github.com/bcgov/nr-forest-client/blob/main/.github/workflows/issue-gherkin.yml
looking to add it to my stack in Organics Info, if possible with playwright


Add jvm heap as a cfn parameter.

Issue #304
Description of changes:

Added the heap as a parameter and set it as JAVA_OPTS.
Use same workers, buffer and batch size.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/usr/bin/java
Found openjdk version  of 11.0
Unrecognized option: -xms256m
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

Appended the error to the same data-prepper.out


Create IngestRules with the where condition parameters substituted.

Codecov Report

:exclamation: No coverage uploaded for pull request base (ingestion_config@17c6f8e). Click here to learn what that means.
The diff coverage is 94.11%.

@@                 Coverage Diff                 @@
##             ingestion_config    #6190   +/-   ##
===================================================
  Coverage                    ?   83.32%
  Complexity                  ?    12698
===================================================
  Files                       ?     1469
  Lines                       ?    47931
  Branches                    ?     5877
===================================================
  Hits                        ?    39938
  Misses                      ?     5269
  Partials                    ?     2724

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/crate/sql/ExpressionFormatter.java
80.72% <100%> (ø)
6 <5> (?)

sql/src/main/java/io/crate/analyze/Analyzer.java
96.93% <100%> (ø)
5 <0> (?)

.../io/crate/analyze/CreateIngestionRuleAnalyzer.java
95% <91.66%> (ø)
4 <1> (?)

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 17c6f8e...dc3b109. Read the comment docs.