added template modifications for uuid in machineconfig

Issue #, if available:
Description of changes:
Now passing uuid instead of name if provided by user to capx provider.
Also added simpleflow tests with uuid for e2e tests for all k8s versions
Testing (if applicable):

 allow-uuid-as-id ±          LOCAL_E2E_TESTS=TestNutanixKubernetes124SimpleFlowUUID  make local-e2e GO_TEST_FLAGS="-test.v 10 -vlevel=10"
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
if [ "" = "true" ]; then \
		if [[ "" =~ "aws-staging-eks-a-build" ]]; then \
			make eks-a-release-cross-platform GIT_VERSION=v0.7.0 RELEASE_MANIFEST_URL=https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml; \
			make eks-a-release GIT_VERSION=v0.0.0-dev; \
			scripts/get_bundle.sh; \
		else \
			make eks-a-cross-platform; \
			make eks-a; \
		fi \
	else \
		make eksa-components-override; \
		make eks-a; \
	fi
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
scripts/eksa_components_override.sh https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml<PHONE_NUMBER>73.dkr.ecr.us-west-2.amazonaws.com/eks-anywhere-cluster-controller:-c541b56f54e6834c774ad7f327a289afd229c728
+ set -o nounset
++ git rev-parse --show-toplevel
+ REPO_ROOT=/Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere
+ BUNDLE_MANIFEST_URL=https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml
+ CLUSTER_CONTROLLER_OVERRIDE_IMAGE=770301640873.dkr.ecr.us-west-2.amazonaws.com/eks-anywhere-cluster-controller:-c541b56f54e6834c774ad7f327a289afd229c728
+ SED=sed
++ uname -s
+ '[' Darwin = Darwin ']'
+ SED=gsed
+ yq --version
yq version 3.4.1
+ mkdir -p /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin
+ make release-manifests RELEASE_DIR=/Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin RELEASE_MANIFEST_TARGET=local-eksa-components.yaml
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
mkdir -p "_output/kustomize-bin/"
rm hack/tools/bin/kustomize
cd hack/tools/bin && curl -s "https://raw.githubusercontent.com/kubernetes-sigs/kustomize/master/hack/install_kustomize.sh" | bash -s 4.2.0
{Version:kustomize/v4.2.0 GitCommit:d53a2ad45d04b0264bcee9e19879437d851cb778 BuildDate:2021-06-30T22:49:26Z GoOs:darwin GoArch:amd64}
kustomize installed to /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/hack/tools/bin/kustomize
cp hack/tools/bin/kustomize "_output/kustomize-bin/"
/Library/Developer/CommandLineTools/usr/bin/make generate-core-manifests
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
GOBIN=/Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/hack/tools/bin go install<EMAIL_ADDRESS>hack/tools/bin/controller-gen \
		paths=./pkg/api/... \
		paths=./controllers/... \
		paths=./manager/... \
		crd:crdVersions=v1 \
		rbac:roleName=manager-role \
		output:crd:dir=./config/crd/bases \
		output:webhook:dir=./config/webhook \
		webhook
# Build core-components.
hack/tools/bin/kustomize build config/prod > /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin/local-eksa-components.yaml
cp /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin/local-eksa-components.yaml _output/manifests/cluster-controller
+ curl https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml -o /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin/local-bundle-release.yaml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  149k  100  149k    0     0   424k      0 --:--:-- --:--:-- --:--:--  440k
+ gsed -i 's,public.ecr.aws/.*/eks-anywhere-cluster-controller:.*,770301640873.dkr.ecr.us-west-2.amazonaws.com/eks-anywhere-cluster-controller:-c541b56f54e6834c774ad7f327a289afd229c728,' /Users/deepak.muley/go/src/github.com/nutanix-cloud-native/aws-eks-anywhere/bin/local-eksa-components.yaml
scripts/eksa_components_override.sh: line 39: gsed: command not found
make[1]: *** [eksa-components-override] Error 127
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
/Library/Developer/CommandLineTools/usr/bin/make eks-a-binary GIT_VERSION=v0.0.0-dev
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 /usr/local/bin/go build -tags "" -ldflags " -X github.com/aws/eks-anywhere/pkg/version.gitVersion=v0.0.0-dev -X github.com/aws/eks-anywhere/pkg/cluster.releasesManifestURL=https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml -X github.com/aws/eks-anywhere/pkg/manifests/releases.manifestURL=https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml -s -w -buildid='' -extldflags -static"  -o bin/eksctl-anywhere github.com/aws/eks-anywhere/cmd/eksctl-anywhere
GOOS=darwin GOARCH=amd64 /usr/local/bin/go build -o bin/test github.com/aws/eks-anywhere/cmd/integration_test
/Library/Developer/CommandLineTools/usr/bin/make e2e-tests-binary E2E_TAGS=e2e
Using standard BUNDLE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/bundle-release.yaml and RELEASE_MANIFEST_URL https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml
fatal: No names found, cannot describe anything.
fatal: No names found, cannot describe anything.
GOOS=darwin GOARCH=amd64 /usr/local/bin/go test ./test/e2e -c -o bin/e2e.test -tags "e2e" -ldflags "-X github.com/aws/eks-anywhere/pkg/version.gitVersion=v0.0.0-dev -X github.com/aws/eks-anywhere/pkg/cluster.releasesManifestURL=https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml -X github.com/aws/eks-anywhere/pkg/manifests/releases.manifestURL=https://dev-release-assets.eks-anywhere.model-rocket.aws.dev/eks-a-release.yaml"
./bin/e2e.test -test.v -test.run TestNutanixKubernetes124SimpleFlowUUID -test.v 10 -vlevel=10
2022-12-06T13:55:46.745-0800	V4	e2e	Logger init completed	{"vlevel": 4}
=== RUN   TestNutanixKubernetes124SimpleFlowUUID
2022-12-06T13:55:46.745-0800	V2	e2e	Pulling docker image	{"image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.7.2-eks-a-v0.0.0-dev-build.1864"}
2022-12-06T13:55:50.153-0800	V3	e2e	Initializing long running container	{"name": "eksa_1670363746745833000", "image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.7.2-eks-a-v0.0.0-dev-build.1864"}
    cluster.go:686: Running shell command [ eksctl anywhere generate clusterconfig dm-5af8e2b -p nutanix > cluster.yaml ]
    cluster.go:504: Creating cluster dm-5af8e2b
    cluster.go:686: Running shell command [ eksctl anywhere create cluster -f dm-5af8e2b/cluster.yaml -v 4 --bundles-override bin/local-bundle-release.yaml ]
2022-12-06T13:55:52.913-0800	V4	Logger init completed	{"vlevel": 4}
2022-12-06T13:55:52.914-0800	V0	Warning: The recommended number of control plane nodes is 3 or 5
2022-12-06T13:55:54.503-0800	V4	Reading bundles manifest	{"url": "bin/local-bundle-release.yaml"}
2022-12-06T13:55:55.047-0800	V0	Warning: The recommended number of control plane nodes is 3 or 5
2022-12-06T13:55:55.047-0800	V2	Pulling docker image	{"image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.12.2-eks-a-v0.0.0-dev-build.4911"}
2022-12-06T13:55:56.180-0800	V3	Initializing long running container	{"name": "eksa_1670363755047287000", "image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.12.2-eks-a-v0.0.0-dev-build.4911"}
2022-12-06T13:55:56.519-0800	V4	Task start	{"task_name": "setup-validate"}
2022-12-06T13:55:56.519-0800	V0	Performing setup and validations
2022-12-06T13:56:02.193-0800	V0	✅ Nutanix Provider setup is valid
2022-12-06T13:56:02.193-0800	V0	✅ Validate certificate for registry mirror
2022-12-06T13:56:02.193-0800	V0	✅ Validate authentication for git provider
2022-12-06T13:56:02.193-0800	V0	✅ Create preflight validations pass
2022-12-06T13:56:02.193-0800	V4	Task finished	{"task_name": "setup-validate", "duration": "5.674177587s"}
2022-12-06T13:56:02.193-0800	V4	----------------------------------
2022-12-06T13:56:02.193-0800	V4	Task start	{"task_name": "bootstrap-cluster-init"}
2022-12-06T13:56:02.193-0800	V0	Creating new bootstrap cluster
2022-12-06T13:56:02.195-0800	V4	Creating kind cluster	{"name": "dm-5af8e2b-eks-a-cluster", "kubeconfig": "dm-5af8e2b/generated/dm-5af8e2b.kind.kubeconfig"}
2022-12-06T13:56:36.466-0800	V0	Provider specific pre-capi-install-setup on bootstrap cluster
2022-12-06T13:56:36.466-0800	V0	Installing cluster-api providers on bootstrap cluster
2022-12-06T13:57:57.033-0800	V0	Provider specific post-setup
2022-12-06T13:57:57.033-0800	V4	Task finished	{"task_name": "bootstrap-cluster-init", "duration": "1m54.795695371s"}
2022-12-06T13:57:57.033-0800	V4	----------------------------------
2022-12-06T13:57:57.033-0800	V4	Task start	{"task_name": "workload-cluster-init"}
2022-12-06T13:57:57.033-0800	V0	Creating new workload cluster
2022-12-06T13:58:05.406-0800	V3	Waiting for control plane to be available
2022-12-06T14:01:05.810-0800	V3	Waiting for workload kubeconfig generation	{"cluster": "dm-5af8e2b"}
2022-12-06T14:01:06.461-0800	V0	Installing networking on workload cluster
2022-12-06T14:01:11.208-0800	V4	Installing machine health checks on bootstrap cluster
2022-12-06T14:01:11.806-0800	V3	Waiting for controlplane and worker machines to be ready
2022-12-06T14:01:13.446-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:13.819-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:15.377-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:16.719-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:18.103-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:19.452-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:20.790-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:22.156-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:23.503-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:24.947-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:26.283-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:27.617-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:29.220-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:30.547-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:31.912-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:33.230-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:34.552-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:35.865-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:37.190-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:38.528-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:39.913-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:41.211-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:42.540-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:43.953-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:45.274-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:46.620-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:47.964-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:49.294-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:50.631-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:51.947-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:53.286-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:54.597-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:56.104-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:57.409-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:01:58.773-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:00.193-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:01.547-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:02.864-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:04.230-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:05.728-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:07.074-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:08.450-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:09.811-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:11.139-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:12.464-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:13.852-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:15.176-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:16.492-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:17.823-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:19.187-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:20.559-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:21.942-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:23.265-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:24.631-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:26.001-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:27.356-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:28.827-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:30.206-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:31.535-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:32.854-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:34.199-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:35.571-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:36.917-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:38.227-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:39.539-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:40.877-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:42.226-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:43.694-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:45.114-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:46.610-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:47.954-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:49.362-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:50.745-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:52.063-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:53.373-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:54.771-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:56.307-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:57.685-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:02:58.994-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:00.411-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:01.757-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:03.179-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:04.531-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:05.873-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:07.216-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:08.523-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:09.866-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:11.205-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:12.524-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:13.844-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:15.185-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:16.501-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:17.802-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:19.126-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:20.497-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:21.812-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:23.126-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:24.463-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:25.865-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:27.276-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:28.669-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:29.980-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:31.341-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:32.691-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:33.995-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:35.352-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:36.683-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:38.012-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:39.367-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:40.687-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:41.997-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:43.319-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:44.649-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:45.991-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:47.337-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:48.671-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:50.065-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:51.599-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:52.891-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:54.251-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:55.598-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:57.000-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:58.327-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:03:59.647-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:00.953-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:02.293-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:03.601-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:04.919-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:06.243-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:07.581-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:08.889-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:10.207-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:11.506-0800	V4	Nodes are not ready yet	{"total": 2, "ready": 1, "cluster name": "dm-5af8e2b"}
2022-12-06T14:04:12.842-0800	V4	Nodes ready	{"total": 2}
2022-12-06T14:04:12.842-0800	V0	Creating EKS-A namespace
2022-12-06T14:04:13.663-0800	V0	Installing cluster-api providers on workload cluster
2022-12-06T14:05:37.790-0800	V0	Installing EKS-A secrets on workload cluster
2022-12-06T14:05:39.804-0800	V4	Task finished	{"task_name": "workload-cluster-init", "duration": "7m42.765341869s"}
2022-12-06T14:05:39.804-0800	V4	----------------------------------
2022-12-06T14:05:39.804-0800	V4	Task start	{"task_name": "install-resources-on-management-cluster"}
2022-12-06T14:05:39.804-0800	V0	Installing resources on management cluster
2022-12-06T14:05:39.804-0800	V4	Task finished	{"task_name": "install-resources-on-management-cluster", "duration": "7.329µs"}
2022-12-06T14:05:39.804-0800	V4	----------------------------------
2022-12-06T14:05:39.804-0800	V4	Task start	{"task_name": "capi-management-move"}
2022-12-06T14:05:39.804-0800	V0	Moving cluster management from bootstrap to workload cluster
2022-12-06T14:05:39.804-0800	V3	Waiting for management machines to be ready before move
2022-12-06T14:05:41.401-0800	V4	Nodes ready	{"total": 2}
2022-12-06T14:05:41.401-0800	V3	Waiting for all clusters to be ready before move
2022-12-06T14:05:53.735-0800	V3	Waiting for control planes to be ready after move
2022-12-06T14:05:55.372-0800	V3	Waiting for workload cluster control plane replicas to be ready after move
2022-12-06T14:05:56.147-0800	V3	Waiting for workload cluster machine deployment replicas to be ready after move
2022-12-06T14:05:56.902-0800	V3	Waiting for machines to be ready after move
2022-12-06T14:05:59.016-0800	V4	Nodes ready	{"total": 2}
2022-12-06T14:05:59.016-0800	V4	Task finished	{"task_name": "capi-management-move", "duration": "19.211372461s"}
2022-12-06T14:05:59.016-0800	V4	----------------------------------
2022-12-06T14:05:59.016-0800	V4	Task start	{"task_name": "eksa-components-install"}
2022-12-06T14:05:59.016-0800	V0	Installing EKS-A custom components (CRD and controller) on workload cluster
2022-12-06T14:06:48.903-0800	V0	Installing EKS-D components on workload cluster
2022-12-06T14:06:51.091-0800	V0	Creating EKS-A CRDs instances on workload cluster
2022-12-06T14:06:51.095-0800	V4	Applying eksa yaml resources to cluster
2022-12-06T14:06:52.343-0800	V1	Applying Bundles to cluster
2022-12-06T14:06:53.723-0800	V4	Applying eksd manifest to cluster
2022-12-06T14:06:55.937-0800	V4	Applying eksd manifest to cluster
2022-12-06T14:06:56.841-0800	V4	Applying eksd manifest to cluster
2022-12-06T14:06:57.736-0800	V4	Applying eksd manifest to cluster
2022-12-06T14:07:04.056-0800	V4	Task finished	{"task_name": "eksa-components-install", "duration": "1m5.039055045s"}
2022-12-06T14:07:04.056-0800	V4	----------------------------------
2022-12-06T14:07:04.056-0800	V4	Task start	{"task_name": "gitops-manager-install"}
2022-12-06T14:07:04.056-0800	V0	Installing GitOps Toolkit on workload cluster
2022-12-06T14:07:04.056-0800	V0	GitOps field not specified, bootstrap flux skipped
2022-12-06T14:07:04.056-0800	V4	Task finished	{"task_name": "gitops-manager-install", "duration": "36.825µs"}
2022-12-06T14:07:04.056-0800	V4	----------------------------------
2022-12-06T14:07:04.056-0800	V4	Task start	{"task_name": "write-cluster-config"}
2022-12-06T14:07:04.056-0800	V0	Writing cluster config file
2022-12-06T14:07:04.060-0800	V4	Task finished	{"task_name": "write-cluster-config", "duration": "4.452316ms"}
2022-12-06T14:07:04.060-0800	V4	----------------------------------
2022-12-06T14:07:04.060-0800	V4	Task start	{"task_name": "delete-kind-cluster"}
2022-12-06T14:07:04.061-0800	V0	Deleting bootstrap cluster
2022-12-06T14:07:05.320-0800	V4	Deleting kind cluster	{"name": "dm-5af8e2b-eks-a-cluster"}
2022-12-06T14:07:08.145-0800	V0	🎉 Cluster created!
2022-12-06T14:07:08.145-0800	V4	Task finished	{"task_name": "delete-kind-cluster", "duration": "4.084692181s"}
2022-12-06T14:07:08.145-0800	V4	----------------------------------
2022-12-06T14:07:08.145-0800	V4	Task start	{"task_name": "install-curated-packages"}
--------------------------------------------------------------------------------------
The Amazon EKS Anywhere Curated Packages are only available to customers with the
Amazon EKS Anywhere Enterprise Subscription
--------------------------------------------------------------------------------------
2022-12-06T14:07:08.145-0800	V0	Enabling curated packages on the cluster
2022-12-06T14:07:08.145-0800	V0	Installing helm chart on cluster	{"chart": "eks-anywhere-packages", "version": "0.2.21-eks-a-v0.0.0-dev-build.5058"}
secret/aws-secret created
2022-12-06T14:07:31.935-0800	V4	Task finished	{"task_name": "install-curated-packages", "duration": "23.789173401s"}
2022-12-06T14:07:31.935-0800	V4	----------------------------------
2022-12-06T14:07:31.935-0800	V4	Tasks completed	{"duration": "11m35.364772865s"}
2022-12-06T14:07:31.949-0800	V3	Cleaning up long running container	{"name": "eksa_1670363755047287000"}
    cluster.go:686: Running shell command [ eksctl anywhere delete cluster dm-5af8e2b -v 4 --bundles-override bin/local-bundle-release.yaml ]
2022-12-06T14:07:32.392-0800	V4	Logger init completed	{"vlevel": 4}
2022-12-06T14:07:33.645-0800	V0	Warning: The recommended number of control plane nodes is 3 or 5
2022-12-06T14:07:33.648-0800	V4	Reading bundles manifest	{"url": "bin/local-bundle-release.yaml"}
2022-12-06T14:07:33.874-0800	V0	Warning: The recommended number of control plane nodes is 3 or 5
2022-12-06T14:07:33.874-0800	V2	Pulling docker image	{"image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.12.2-eks-a-v0.0.0-dev-build.4911"}
2022-12-06T14:07:35.083-0800	V3	Initializing long running container	{"name": "eksa_1670364453874421000", "image": "public.ecr.aws/l0g8r8j6/eks-anywhere-cli-tools:v0.12.2-eks-a-v0.0.0-dev-build.4911"}
2022-12-06T14:07:35.419-0800	V4	Task start	{"task_name": "setup-and-validate"}
2022-12-06T14:07:35.419-0800	V0	Performing provider setup and validations
2022-12-06T14:07:35.419-0800	V4	Task finished	{"task_name": "setup-and-validate", "duration": "20.125µs"}
2022-12-06T14:07:35.419-0800	V4	----------------------------------
2022-12-06T14:07:35.419-0800	V4	Task start	{"task_name": "management-cluster-init"}
2022-12-06T14:07:35.419-0800	V0	Creating management cluster
2022-12-06T14:07:35.420-0800	V4	Creating kind cluster	{"name": "dm-5af8e2b-eks-a-cluster", "kubeconfig": "dm-5af8e2b/generated/dm-5af8e2b.kind.kubeconfig"}
2022-12-06T14:08:11.462-0800	V0	Provider specific pre-capi-install-setup on bootstrap cluster
2022-12-06T14:08:11.462-0800	V4	Task finished	{"task_name": "management-cluster-init", "duration": "36.042519929s"}
2022-12-06T14:08:11.462-0800	V4	----------------------------------
2022-12-06T14:08:11.462-0800	V4	Task start	{"task_name": "install-capi"}
2022-12-06T14:08:11.462-0800	V0	Installing cluster-api providers on management cluster
2022-12-06T14:09:41.453-0800	V4	Task finished	{"task_name": "install-capi", "duration": "1m29.990136536s"}
2022-12-06T14:09:41.453-0800	V4	----------------------------------
2022-12-06T14:09:41.453-0800	V4	Task start	{"task_name": "cluster-management-move"}
2022-12-06T14:09:41.453-0800	V0	Moving cluster management from workload cluster
2022-12-06T14:09:41.453-0800	V3	Waiting for management machines to be ready before move
2022-12-06T14:09:43.845-0800	V4	Nodes ready	{"total": 2}
2022-12-06T14:09:43.845-0800	V3	Waiting for all clusters to be ready before move
2022-12-06T14:10:04.592-0800	V3	Waiting for control planes to be ready after move
2022-12-06T14:10:05.944-0800	V3	Waiting for workload cluster control plane replicas to be ready after move
2022-12-06T14:10:06.615-0800	V3	Waiting for workload cluster machine deployment replicas to be ready after move
2022-12-06T14:10:07.158-0800	V3	Waiting for machines to be ready after move
2022-12-06T14:10:08.754-0800	V4	Nodes ready	{"total": 2}
2022-12-06T14:10:08.754-0800	V4	Task finished	{"task_name": "cluster-management-move", "duration": "27.300409191s"}
2022-12-06T14:10:08.754-0800	V4	----------------------------------
2022-12-06T14:10:08.754-0800	V4	Task start	{"task_name": "delete-workload-cluster"}
2022-12-06T14:10:08.754-0800	V0	Deleting workload cluster
2022-12-06T14:10:08.754-0800	V1	Deleting CAPI cluster	{"name": "dm-5af8e2b"}
2022-12-06T14:10:37.860-0800	V4	Task finished	{"task_name": "delete-workload-cluster", "duration": "29.103930372s"}
2022-12-06T14:10:37.860-0800	V4	----------------------------------
2022-12-06T14:10:37.860-0800	V4	Task start	{"task_name": "clean-up-git-repo"}
2022-12-06T14:10:37.860-0800	V0	Clean up Git Repo
2022-12-06T14:10:37.860-0800	V0	GitOps field not specified, clean up git repo skipped
2022-12-06T14:10:37.860-0800	V4	Task finished	{"task_name": "clean-up-git-repo", "duration": "33.956µs"}
2022-12-06T14:10:37.860-0800	V4	----------------------------------
2022-12-06T14:10:37.860-0800	V4	Task start	{"task_name": "package-resource-delete"}
2022-12-06T14:10:37.860-0800	V4	Task finished	{"task_name": "package-resource-delete", "duration": "1.207µs"}
2022-12-06T14:10:37.860-0800	V4	----------------------------------
2022-12-06T14:10:37.861-0800	V4	Task start	{"task_name": "kind-cluster-delete"}
2022-12-06T14:10:39.050-0800	V4	Deleting kind cluster	{"name": "dm-5af8e2b-eks-a-cluster"}
2022-12-06T14:10:41.700-0800	V4	Task finished	{"task_name": "kind-cluster-delete", "duration": "3.839777624s"}
2022-12-06T14:10:41.701-0800	V4	----------------------------------
2022-12-06T14:10:41.701-0800	V4	Tasks completed	{"duration": "3m6.279561611s"}
2022-12-06T14:10:41.709-0800	V3	Cleaning up long running container	{"name": "eksa_1670364453874421000"}
2022-12-06T14:10:42.000-0800	V3	e2e	Cleaning up long running container	{"name": "eksa_1670363746745833000"}
--- PASS: TestNutanixKubernetes124SimpleFlowUUID (895.42s)
PASS

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

/ok-to-test

/test eks-anywhere-presubmit

/test eks-anywhere-presubmit


object has no attribute '_formatter_parser'

Rasa NLU version  :"version": "0.10.1"
Used backend / pipeline spacy_sklearn,
Operating system RHEL 7
Issue:
while executing query following error is comming
{"error": "'NoneType' object has no attribute '_formatter_parser'"}
Example:
curl -XPOST localhost:5000/parse -d '{"q":"I am looking for Chinese food"}'
{"error": "'NoneType' object has no attribute '_formatter_parser'"}
Content of configuration file (if used & relevant):

Can you provide more information on how you're running Rasa: command line, python, docker, etc?
Have you already trained a model? What is in the /projects folder? Can you post the metadata.json file of the model that is being loaded.

I have the same on a brand new installation on Ubuntu from github: command line, docker, following the tutorial without modification.
{
    "entity_synonyms": "entity_synonyms.json",
    "pipeline": [
        "nlp_spacy",
        "tokenizer_spacy",
        "intent_featurizer_spacy",
        "intent_entity_featurizer_regex",
        "ner_crf",
        "ner_synonyms",
        "intent_classifier_sklearn"
    ],
    "spacy_model_name": "en",
    "language": "en",
    "intent_classifier_sklearn": "intent_classifier.pkl",
    "trained_at": "20171020-125436",
    "training_data": "training_data.json",
    "entity_extractor_crf": {
        "BILOU_flag": true,
        "model_file": "crf_model.pkl",
        "version": 1,
        "crf_features": [
            [
                "low",
                "title",
                "upper",
                "pos",
                "pos2"
            ],
            [
                "bias",
                "low",
                "word3",
                "word2",
                "upper",
                "title",
                "digit",
                "pos",
                "pos2",
                "pattern"
            ],
            [
                "low",
                "title",
                "upper",
                "pos",
                "pos2"
            ]
        ]
    },
    "rasa_nlu_version": "0.10.1",
    "regex_featurizer": "regex_featurizer.json"
}

which python version do you use?

And can you please also add the stacktrace from the console

Hi,@wrathagom,I have the same problem.
This is my metadata.json.
{     "entity_synonyms": "entity_synonyms.json",     "pipeline": [         "nlp_mitie",         "tokenizer_jieba",         "ner_mitie",         "ner_synonyms",         "intent_entity_featurizer_regex",         "intent_featurizer_mitie",         "intent_classifier_sklearn"     ],     "mitie_feature_extractor_fingerprint":<PHONE_NUMBER>478185215,     "regex_featurizer": null,     "language": "zh",     "mitie_file": "./data/total_word_feature_extractor_zh.dat",     "intent_classifier_sklearn": "intent_classifier.pkl",     "trained_at": "20171030-153135",     "training_data": "training_data.json",     "entity_extractor_mitie": "entity_extractor.dat",     "rasa_nlu_version": "0.10.1" }

@wrathagom @tmbo python version is 2.7.0

I pushed a fix/work-around (it's a log statement that doesn't have a format string), so if you get the current version of rasa_nlu you should find the visible part of this problem has gone away.

@Jonathan-Wei we also just recently cut a release, so the issue is also fixed in 0.10.4


CSS

you'll have to run npm run lint:fix

Thanks for fixing it. I thought I ran that, I ran everything related to lint and prettier and fixing multiple times lol but alas


Option to delete all entries

I don't know if there is any way to delete all the entries and import again from 0 time. Anyway, thanks for this pretty good tool!

Thanks!!!

Thanks!!!


Designer Express Mode

It would be nice to have an express mode.
E.g.: Someone doesn't want to edit all of the variables, instead they provide 5 colors, with those colors a scheme will be created. Which will be based around those colors

Material Algorythm

Put the colors which are frequently used in variables --> create an "express" input switch where those variables can be edited more quickly


update playerlist

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for betsweatwin processing.

Name
Link

🔨 Latest commit
e0e0e55743f486cbd662df0ec4548dfc5534eb1e

🔍 Latest deploy log
https://app.netlify.com/sites/betsweatwin/deploys/653955955e9fbc0008e32e7a


Nodejs Debugger skips first F11 after breakpoint on await/async function

VSCode Version: 1.20.1
OS Version: Windows 10 x64

Steps to Reproduce:

Write some async code (see example)

async function foo(num) {
    await new Promise(function (res) {
        setTimeout(res, 1000);
        console.log(num);
    })
}

(async function () {

    await foo(1); // set breakpoint here, then press F11 to step in
    await foo(2); // F11 doesn't work for a first line, but will work on next line
    await foo(3);
})()

Set breakpoint on await foo(1);
Start file with nodejs and debugger
When debugger stops on breakpoint, try to F11 into the function
F11 doesn't work, first line is skipped as if F10 was pressed
Second F11 works fine

Only async functions affected.
Help->Report issue doesn't work.

Does this issue occur when all extensions are disabled?: Yes

What version of node are you using?

Cannot reproduce.
With node 8.9.3 on Windows 10 F11 steps into some internal node module:

This can be prevented by skipping internal modules like this:
  {
            "type": "node",
            "request": "launch",
            "name": "Launch Program",
            "program": "${workspaceFolder}/test.js",
            "skipFiles": [
                "<node_internals>/**"
            ]
        }

Now the stepping works just fine:

Thanks for quick response!
I was using Nodejs v8.2.1.
I've just updated it to Nodejs v8.9.4, and it works same as on your gifs. Although it's still not a perfect behavior, it doesn't miss breakpoints now.
Thanks!

What is not "perfect" about the behaviour?

I guess, stepping to inner nodejs modules, but it doesn't do that while debugging my project, only on  example code.
And I don't know if VSCode is aimed to support older Nodejs versions, or that was a bug in Nodejs instead of VScode.

upd. Sometimes while debugging my project, it drops into nodejs internal modules too.

If it does not step into internal nodejs modules in your project, then you might have configured your launch config for this behaviour. If not please file a bug and we will investigate.
VS Code node-debug supports older version of node.js back to 0.10.x (which is really old). But since there are lots of node.js versions, and quite a few have bugs, we cannot work around all those bugs. So you might see issues like this with the v8.2.1 version.


Automatically fill message field for HTTPException, when it is present in api_docs…

Ideally, when an endpoint call abort with an HTTP error, we would like the message to be filled according to the endpoint's documentation (e.g. "Resource missing", rather than Flask's default "The requested URL was not found on the server" for a 404).
This seems like something that could be done in the abort method? I have had a look at the Blueprint class, but still unsure where it should look, to get the list of responses for that particular call…

I won't spend much time on this myself, as I don't think it is critical. But if someone comes up with a satisfying solution, I'm happy to merge it.
I'm not sure I understand the feature description correctly, but from what I graps, it could be challenging.
First, we'd need to sort of single-source the error messages. I mean at the end, they are in the docs, but before that, they must be structured somewhere in the code. This could be in several places (path description, response component definition).
Then, abort can be called from anywhere before even entering a resource. The 404 error is the best example. It does not belong to a resource. Arguably, /pets/wrong_id is a "Pet not found" issue, but /pest/pet_id just does not relate to any resource. Maybe there are other similar cases.
Let's say you get an authentication error in an auth decorator. Then abort. You're not in the resource function yet. You could get the path from the request object. Then you'd need to go all the way from the path to the function to access the error message. I does not seem straightforward.
I could be missing something.
If you're still interested in this, you may want to elaborate on a use case description. But frankly, I don't think I'll be of much help.

I'll need to go and have a look again (it's not even that fresh in my memory any more), but even if not using the Resource's doc to provide the error (although that would be even nicer), at least honouring the second arg in the abort function (currently, it gets overwritten by default HTTP error messages) would be helpful…

This should work:
abort(400, message='What a bad request')

The custom error message should appear in the response payload.
Or am I misunderstanding your point?

@zedrdave I don't think flask-rest-api can do much more than pass the message in the call to abort as shown in my comment above.
May I close this? Or do you think you can be more specific about what you're thinking about, perhaps with use case examples?

@lafrech I think abort(400, message='something') is fine. Wondering if it might be possible to make message the second positional argument without too much breakage (as I think that would increase compatibility with other versions of abort).


Removing datastore.Dataset class and its uses.

Addresses part 8 of #477.
@tseaver What do you want to do about #499? We can finish that review and I can rebase this, but it will likely be quite difficult.
I have put off doc changes (unless necessary, e.g. the RST docs which would not build without the class) and will tackle that next.
I have also not yet been able to resolve the cyclic import in Key.get() but I am leaning towards simply removing it and renaming datastore.__init__.get_entities to datastore.__init__.get (and allowing a Key or a list of Keys).

Also, I need to fix the following "extra" modules:
gcloud/datastore/demo/...
regression/populate_datastore.py
regression/clear_datastore.py

I have put it off for now since each can be done in an individual (easier to review) PR.

Coverage remained the same when pulling e998859d8dba24a97be97ead6edc759c77a22375 on dhermes:fix-477-part8 into f1760986309319d32a14164623be6a0013d8e7d6 on GoogleCloudPlatform:master.

@tseaver I am going to try to do a large docs fix-up. After your cherry-pick of #499 is in, how do you want to divvy up:
gcloud/datastore/demo/...
regression/populate_datastore.py
regression/clear_datastore.py

how about I tackle the 'demo' stuff, and you the 'regression'?

SGTM. I'm going to tackle docs first after we're done with #501 and then get to that.


Remove repo.spring.io from where-for-dinner

upgrade spring to 3.0.2
upgrade java 17
remove repo.spring.io

It looks like only the notify application is upgrading to spring boot 3.0.2. Is there a reason not to upgrade all of the applications?

It looks like only the notify application is upgrading to spring boot 3.0.2. Is there a reason not to upgrade all of the applications?

I made a comparison with the main and I found this:

where-for-dinner-(availability and search): there is problem with r2dbc-mariadb when updating to spring 3.0.2 and if you try give a version to the dependency all unit tests fail, for all the other I did a new push


Add GitKraken Client

Adds development utility client for git repository management for GitHub/GitLab/BitBucket/etc.

Updated to remove git; and point merge toward the test branch


NTR: cDNA Sequencing Assay

NTR: "cDNA Sequencing"

Editor preferred term: "cDNA Sequencing"
Alternative terms: copy DNA sequencing
Textual definition: Sequencing (either Sanger or High-throughpu - like PacBio or Oxford Nanopore) of a full, partial or tag- fragmented cDNA molecule.
Definition source for the textual definition: Common parlance
Logical definition (or parent term):
Example of usage: "The data contained herein is derived from cDNA sequencing of oligo-dT primed cDNAs"
Term editor: Carrie A Davis

Hi, Carrie.  I'd like to start helping with your term requests.  To start...
Could this be defined as a "Seq assay which takes cDNA as the input"... but ins't that the case for RNAseq?  In what case would somebody use this term in a materials and methods section?

@turbomam we have no need for this term request anymore. You are right that cDNA sequencing is basically RNAseq. Thank you for pointing out this open issue to us, but please feel free to close it.

Thanks @bonitalam


Can't navi to settings page when hide menu bar icon if only switch icon appear at the left

Describe the bug
I turn on the hide menu bar icon switch and where the switch icon appears at the left, then there is a dead lock if the only switch is active and its icon is hidden, so I can't navigate into the setting page and disable the swtich.
To Reproduce
Steps to reproduce the behavior:

Put the hide icon tag on the right of the "only switch" icon;
Go to settings page and turn on "hide menu bar icon" switch
The left icons are hidden including "only switch" icon.

Expected behavior
Never hide "only switch" icon.

Thank you for the feedback. Which OnlySwitch version are you using?

Thank you for the feedback.  Actually, there is logic in the code to avoid this situation. It doesn't happen on my side. I think I need more clue.
https://user-images.githubusercontent.com/3782279/184844089-8c79eb6d-cbc5-4609-b9c6-d0edeb1b1fd2.MOV

If you delete plist file, it still can't show the icon, please restart your laptop.

I can give a workaround to solve the current problem. delete this file /Users/xxxx/Library/Preferences/jacklandrin.OnlySwitch.plist. Actually, there is logic in the code to avoid this situation. It doesn't happen on my side. I think I need more clue.
IMG_2333.MOV

I recover the hidden icons after I deleted the Userdefaults and some relevant directories. Then I can't reproduce the bug as well. 😂

Maybe this problem is caused by cover installation. Some new userdefaults conflict with old settings.

Did you update it from 2.3.6?

Did you update it from 2.3.6?

Maybe from 2.3.4 or 2.3.5

I tried to install back 2.3.5 and uploaded it to 2.3.7. It still can't reproduce the bug. 🤣


two-fer: sync

Sync the two-fer exercise with the latest data, as defined in https://github.com/exercism/problem-specifications/tree/main/exercises/two-fer.

Feel free to close this PR if there is another PR that also syncs this exercise.
When approved, feel free to merge this PR yourselves (you don't have to wait for me).

As this PR only updates docs and/or metadata, it won't trigger a re-run of existing solutions (see the docs).

pending https://github.com/exercism/abap/pull/304


Fix Fix auto partition cannot load data

Proposed changes
Issue Number: close #xxx
in cloud mode, run test_select_with_predicate_prune could reappear it.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

http://<IP_ADDRESS>:8111/test/-7872041104277188299?currentProjectId=Doris_DorisCloudRegression&expandTestHistoryChartSection=true
passed relative cloud test

run buildall

run buildall


PauliEvolutionGate with time-dependent Hamiltonians

What is the expected enhancement?
At the moment PauliEvolutionGate takes a time independent Hamiltonian and returns its evolution in the form of some product formula. However, general system Hamiltonians are time-dependent, so it would be nice to be able to do something along the lines:
from qiskit.circuit import Parameter
from qiskit.opflow import X, Z
from qiskit.circuit.library import PauliEvolutionGate

t_param = Parameter("t")
operator = X * t_param + Z
evo_time = 1
PauliEvolutionGate(hamiltonian, evo_time)

Below are some references for the different approaches to simulate the evolution of time-dependent Hamiltonians.
Product formula approach:

Higher Order Decompositions of Ordered Operator Exponentials
Quantum simulation of time-dependent Hamiltonians and the convenient illusion of Hilbert space

QDrift:

Time-dependent Hamiltonian simulation with L1-norm scaling

Linear Combination of Unitaries

Simulating the dynamics of time-dependent Hamiltonians with a truncated Dyson series

Variational methods (many references, not listed)

Any updates on this?

The PauliEvolutionGate only supports static Hamiltonians. Time-dependent Hamiltonians are covered in the TrotterQRTE class, which implements a full Trotterized time evolution, see


HIVE-28138: Hive metastore benchmarks jar should use log4j2CacheTransformer

What changes were proposed in this pull request?
Why are the changes needed?
java -jar hmsbench-jar-with-dependencies.jar

ERROR StatusLogger Unrecognized format specifier [d]
ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [thread]
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
ERROR StatusLogger Unrecognized format specifier [level]

https://logging.apache.org/log4j/transform/latest/
https://stackoverflow.com/questions/48033792/log4j2-error-statuslogger-unrecognized-conversion-specifier
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
local test

https://github.com/apache/hive/pull/5112 Can this PR fix your issue?


Problem with bpf_redirect_peer

From the author tutorial: "The official cilium blog says that the skb should be directly redirected from the vxlan device to the half veth of the pod in netns through bpf_redirect_peer, but when I first tried to use bpf_redirect_peer for redirection , It is observed that the traffic indeed enters the veth in the pod, and the packet capture can also capture the request on this veth, but I don’t know why, it does not return a reply, but it is ok to switch to bpf_redirect. If there is any big If you know the reason, please let me know, thank you" (I'm using Google Translate)
=> I also encounter the same problem when using bpf_redirect_peer. All the packets go to the pod dest veth but there aren't any reply messages.
=> I'm using eBPF to trace, the handler of the IP layer - ip_rcv drop all the packets with bpf_redirect_peer
=> Any ideas why this happens? I believe that every thing is fine: MAC, IP of source and dest

I was trying to use bpf_redirect_peer to redirect packets from one veth (not a VXLAN device) to another veth, and it also failed. The bpf_skb_change_type(skb, PACKET_HOST) solved my problem, too. So I think this problem has nothing to with VXLAN.


d3.forceCollideRect?

While making cartograms I'm finding that the collide function of this block works much better than just using d3.forceCollide, as it seems to be made for squares rather than circles with a certain radius.
Is there a way to emulate its behaviour with the current forces available? If not, does it make sense to have it inside d3-force in some form?

Related: https://github.com/mapbox/polylabel/pull/63

Also related: d3fc-label-layout


Add docs for OS installation workflow

most contents are from  confluence page https://hardware.corp.emc.com/display/gheonrack/Parameterize+OS+bootstrap+APIs.
@RackHD/rackhd_dev @RackHD/corecommitters @WangWinson @pengz1 @zyoung51

@zyoung51 @yyscamper Thanks for your comments. all comments mentioned are updated. any other more comments, I'll continue to update

:+1:

@pengz1 @zyoung51 Thanks again, and update again :)

+1, document looks pretty good for me and we can refine in the future with more futures and OS.

👍 with a minor question/clarification on the ssh key type, and a suggestion for future work from @pengz1.

Guys, all are good suggestions and are updated

:+1:


gitea/gitea 1.22.1

Description
Dear Gitea team,
We have found a bug with the docker gitea 1.22.1 version running git clone<EMAIL_ADDRESS>I got remote Unauthorized Authentication failed using the correct password.
Using the same user and password works properly from web browser
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Rocky Linux 8.x
How are you running Gitea?
docker container
Database
None

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Can you reproduce in demo site?

Or are there any special characters in your password.


[ISSUE #4323] Quickstart adds the default NamesrvAddr

fix : #4322
Make sure set the target branch to develop
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.007%) to 52.134% when pulling ff634acb864b9b3650d3c70998474dcbf9d006f1 on li-xiao-shuang:feature_example_1 into a28dc651dcd1b250cb50ee29f036e04e97d8c3b8 on apache:develop.

Codecov Report

Merging #4322 (ff634ac) into develop (a28dc65) will increase coverage by 0.07%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #4322      +/-   ##
=============================================
+ Coverage      48.15%   48.23%   +0.07%
- Complexity      5076     5090      +14
=============================================
  Files            642      642
  Lines          42767    42767
  Branches        5598     5598
=============================================
+ Hits           20595    20628      +33
+ Misses         19659    19631      -28
+ Partials        2513     2508       -5

Impacted Files
Coverage Δ

.../rocketmq/broker/filter/ConsumerFilterManager.java
72.19% <0.00%> (-1.80%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
71.42% <0.00%> (-1.79%)
:arrow_down:

...ain/java/org/apache/rocketmq/store/MappedFile.java
51.40% <0.00%> (+0.35%)
:arrow_up:

...nt/impl/consumer/ConsumeMessageOrderlyService.java
50.35% <0.00%> (+0.35%)
:arrow_up:

...he/rocketmq/client/trace/AsyncTraceDispatcher.java
82.92% <0.00%> (+0.48%)
:arrow_up:

...a/org/apache/rocketmq/store/StoreStatsService.java
38.09% <0.00%> (+0.56%)
:arrow_up:

...e/rocketmq/client/impl/consumer/RebalanceImpl.java
44.53% <0.00%> (+0.78%)
:arrow_up:

...he/rocketmq/client/impl/consumer/ProcessQueue.java
62.38% <0.00%> (+0.91%)
:arrow_up:

...mq/client/impl/consumer/RebalanceLitePullImpl.java
73.52% <0.00%> (+1.47%)
:arrow_up:

...va/org/apache/rocketmq/common/stats/StatsItem.java
55.00% <0.00%> (+4.16%)
:arrow_up:

... and 5 more

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 a28dc65...ff634ac. Read the comment docs.


Segfault when allocating in a loop

This pieces of code causes a segfault on julia 1.8.3 and Enzyme v0.10.12
Note: The code doesn't do anything useful, but I believe this causes the issue I see in a more complex piece of code, where I assign the allocated arrays in the inner loop to an array I define outside the loop.
Also note that pulling the allocation out of the loop (or using `for k in 1:1) causes no isses.
using Enzyme

function test(x)
    n = 1
    for k in 1:2
        y = falses(n)
    end
    return x
end
a = Enzyme.autodiff(Enzyme.Reverse, test, Active, Active(1E4))

signal (11): Segmentation fault
in expression starting at /home/chrhck/repos/NeutrinoTelescopes/scripts/repr_enzyme_crash.jl:10
_ZNK4llvm10BasicBlock10getContextEv at /home/chrhck/.julia/juliaup/julia-1.8.3+0.x64.linux.gnu/bin/../lib/julia/libLLVM-13jl.so (unknown line)```

This will be fixed by https://github.com/EnzymeAD/Enzyme/pull/957 but will require a jll bump before it is available to the Julia bindings.

If I've understood the issue correctly, then the segfault in this case has to do with the fact that the loop is essentially a noop for calculating the gradient? In this case it's probably not the cause of the issue I'm seeing with the more complex code. I'll dig further...

Yeah this is distinct from what you posted on slack -- but nevertheless a good bug to fix!
Which now should be fixed on main if you can retry.


Experiments to compare random GOLEM with MAB

Experiments to compare random GOLEM with MAB should be conducted:

On the simple task
On the graph search task

Convergence, mutations probability and population diversity must be analyzed

Results for tree graphs
convergence plots

mutation probabilities


Migrate to React 16

Migrating to latest react increases overall website performance and eases the further maintainability of the project. Also We possibly have an issue with Preact event system mock which sometimes doesn't fire onError for the image see #1924
Considering overall bundle size reductions and GZIP it doesnt make much sense to keep preact, also @bebraw dropper preact in antwar's latest versions as it wasnt working with webpack4 setup.
Dependency: #1964
As soon as #1964 is finalized and merged i can do the migration
UPDATE: It seems there is a branch already which does the migration, this is on hold until things getting clearer, see rebuild branch for more info.

@EugeneHlushko Preact works just fine. You have to tune it like this: https://github.com/antwarjs/antwar/blob/master/smoketest/antwar.config.js#L9 . See the smoketest example configuration.

But do we still need it when react's async rendering lands? 16.3 RC is already on npm so that might be too soon

@EugeneHlushko I had some troubles with Preact until I realized I have to implement that render hook. I would go with Preact for now given it's so much smaller than React. I wouldn't worry about the new async rendering semantics yet. I would optimize for bundle size.

I am not totally convinced that 32.6 kb GZ react 16.2 vs 3kb GZ preact makes difference when we include avatar based widgets on pages where each picture can be 4-32kb and the content is responsive on initial render as antwar already generated the markup during build.
As github pages does GZ by default i would still try to move out for React 16, which might also solve our current issue with  onError failures.
But i can still do alias after the migration if everyone is up for Preact in this particular website scenario

Ok. Even better, we should find a neat way to separate React and react-dom to a shared vendor bundle. I have a feeling it's quite easy to pull this off through webpack configuration (externals) though I may have to extend Antwar somehow to do this in a neat way.
If we do this, the size difference doesn't matter as the outcome is more or less the same.

Or that might be a cachingGroup in optimization.splitChunks ? I will look to it in this Issue when webpack 4 migration is merged

@EugeneHlushko That's what I mean. It's good to remember Antwar bundles twice which makes this a little tricky. The first phase generates a bundle it calls in different ways to render individual pages. During this second phase it bundles the interactive bits. Maybe cachingGroup for React and react-dom during the first phase would be enough as long as there's a way to inject a reference to the resulting bundle in the second phase.

ok thats why you mentioned externals, didnt realize at the start 👍 i will ping you when PR is up if you dont mind

@EugeneHlushko Ok. Open an issue at Antwar repo and I'll try to setup a small example to follow.

done in rebuild

@EugeneHlushko rebuild branch uses React 15.6.1

@montogeek it says ^16.2.0 for both react and react-dom on latest rebuild branch in package.json

@EugeneHlushko Correct, no idea what I read last night


[import/no-duplicates] (prefer-inline) Autofix merges imports incorrectly

Config:
'import/no-duplicates': ['error', { 'prefer-inline': true }]

Case 1:
input
import type { TypeOne, TypeTwo } from './types';
import type { TypeThree, TypeFour } from './types';

output
import type { TypeOne, TypeTwo, type TypeThree, TypeFour } from './types';

expected
import { type TypeOne, type TypeTwo, type TypeThree, type TypeFour } from './types';

Case 2:
input
import type { TypeOne, TypeTwo } from './types';
import { type TypeThree, type TypeFour } from './types';

output
import type { TypeOne, TypeTwo, type TypeThree, type TypeFour } from './types';

expected
import { type TypeOne, type TypeTwo, type TypeThree, type TypeFour } from './types';

Another broken prefer-inline autofix case, and a minor inconsistency:
Case 1: Merging type followed by non-type generates uncompilable code:
input
import type { TypeOne } from './other';
import { functionOne } from './other';

output
import type { TypeOne , functionOne } from './other';

expected
import { type TypeOne, functionOne } from './other';

Case 2: Merging non-type followed by type generates correct code but with unusual output spacing:
input
import { functionOne } from './other';
import type { TypeOne } from './other';

output
import { functionOne ,type  TypeOne } from './other'

expected
import { functionOne, type TypeOne } from './other'

Another one:
input
import type React from 'react';
import { useId, useState } from 'react';

output
import type React, { useId , useState } from 'react';

expected
import type React from 'react';
import { useId, useState } from 'react';

Another case: Merging import type and type only named import results into uncompilable code.
input
import type Highcharts from 'highcharts'
import { type SankeyNodeObject } from 'highcharts'

output
import type Highcharts, { type SankeyNodeObject } from 'highcharts';

expected
import { type default as Highcharts, type SankeyNodeObject } from 'highcharts';

Caution: Although following code looks similar to expected output, it will generate different compiled code from input when verbatimModuleSyntax is enabled in TypeScript compiler options.
import type { default as Highcharts, SankeyNodeObject } from 'highcharts';

Ran into this today. Original code:
import type { Knex } from 'knex';
import knex from 'knex';

Produces these warnings:
index.ts:3:27
✖    3:27  /project/node_modules/knex/knex.js imported multiple times.    import/no-duplicates
✖    4:18  /project/node_modules/knex/knex.js imported multiple times.    import/no-duplicates

Auto-fixes to:
import knex, type { Knex } from 'knex';

Then when running eslint again:
index.ts:3:13
✖  3:13  Parsing error: { expected.

1 error

And also produces the following TypeScript error:
index.ts:3:28 - error TS1434: Unexpected keyword or identifier.

3 import knex, type { Knex } from 'knex';

I'd +1 to @frantic1048's expectation rather than @dylang's, as per the rule name no-duplicates, though this should be configurable by a boolean option like mergeTypeDefault with the default value being true.


KodaDot V3 Redesign + Guidelines

Is your feature request related to a problem?
Hello everyone, let’s escape the Craigslist pit and turn KodaDot into a slick NFT Explorer. 👯
If you need me to respond, I am usually available Mon-Fri, and at my computer from 9am-6pm CET, whilst working 3x days per week.
Buckle up because this is a long document which aims to:

Organise all issues in a large mind map which will serve as a guide on where to place each PR/issue

eliminate double work, outdated PRs/issues and double PRs/issues

construct a way for all of us to easily communicate with each other and move rapidly forward

I have started redesigning page by page, so far I’ve finished the “Nav Bar”, “Gallery”, “Jobs” and “Checkout” designs. I would suggest either starting with the “Gallery” or waiting for me to finish further designs.
Please tag me in any new PRs/issues being opened that have any relation to UX/UI so I can keep adding these to the mind map accordingly + providing designs so that devs don’t have to bother with this, as it is my duty to sort out UX/UI so you can focus on what you do best.
Redesign file is here
Further Notes:
I would suggest holding off on any tutorials and FAQ before the redesign is complete, however, I'd assign @cryptodamsky and @onerawartist to do these once the redesign is done. In order to fast track this process I will focus on redesigning the landing page and minting user journeys next.
Mind Map Legend
Cyan color: Pages
Black: Unresolved issues with design
Orange: Resolved issues with design
Note: some blocks are duplicated due to having a pressence on multiple pages
All of your suggestions are very much appreciated, let me know how you'd like to proceed and please assign yourselves to issues/PRs you see fit.
Describe the solution you would like
Note: As I continue to research user journeys, some things are subject to change, I will update as I go.
General changes:

[ ] - Change color to E6007E
[ ] - Update background color to: 0A0A0A
[ ] - remove glow from images
[ ] - remove zoom in from images

The design will sort out the issues/PR's per page, as in the list below:
Nav Bar
#910
#1337
My proposal is to remove these from nav bar:
"Collections"(these should be easy to view in gallery, not needed in NAV at all)
"Spotlight" (I think this should be merged with "series" as a separate tab and I suggest renaming "series" to "leaderboad", as the term is confusing)
I suggest adding "credit", "transform", "admin", "settings" under a new page called "My profile" where the user will be able to edit and access multiple features; see the works/artists/collections they like/follow, what they have collected, active data on the works they purchased/created. Additionally, the page would have a "dev" dashboard where we can also track all of our Github contributions and activities(have a look at the mind map for a breakdown of the page). Thsi page will take a while to researh but I am confident we can have the redesign of the entire platform done within the next 2 weeks.
Personal account zone: My Profile

[ ] #911
[ ] #942
[ ] #1172
[ ] #1432
[ ] #1439
[ ] #1526
[ ] #361
[ ] #1516 once #744 adjusted
[ ] #1334
[ ] #1285

Tutorial would be turned into "Help" and it would consist of both tutorials + FAQ's
Landing

[ ] #90
[ ] #1115
[ ] #876
[ ] #899
[ ] #145
[ ] #1489
[ ] #145
[ ] #319
[ ] #660
[ ] #837
[ ] #899
[ ] #1445
[ ] #1564

Activity(a new page in the navigation to track activity in real time)

[ ] #1236

Leaderboard/Series
Add as tabs:

[ ] #1477
[ ] #1440

Gallery+Search Engine

[ ] #348
[ ] #802
[ ] #859
[ ] #290
[ ] #903
[ ] #1050
[ ] #285
[ ] #1023
[ ] #1088
[ ] #1191
[ ] #49
[ ] #979
[ ] #1526
[ ] #35
[ ] #1367
[ ] #1294
[ ] #42
[ ] #1174
[ ] #979
[ ] #1367
[ ] #991
[ ] #1411
[ ] #1582
[ ] #1231

Create(Minting)

[ ] #378
[ ] #460
[ ] #419
[ ] #614
[ ] #753
[ ] #401
[ ] #847
[ ] #614
[ ] #911
[ ] #575
[ ] #991
[ ] #1005
[ ] #1094
[ ] #1330
[ ] #1406
[ ] #1526
[ ] #991
[ ] #1015

Profile(this is what others view when they ladn on your profile, the "My profile" section is private)

[ ] #1285
[ ] #49
[ ] #716
[ ] #617
[ ] #678
[ ] #1190
[ ] #571
[ ] #612
[ ] #744
[ ] #880
[ ] #877
[ ] #825
[ ] #898
[ ] #903
[ ] #938
[ ] #1015
[ ] #1029

NFT + Collection view(I need to separate these accordingly as issues are bundled together at the moment)

[ ] #219
[ ] #357
[ ] #901
[ ] #957
[ ] #1118
[ ] #1330
[ ] #594
[ ] #910
[ ] #958
[ ] #1083
[ ] #1214
[ ] #1606
[ ] #612
[ ] #744
[ ] #936
[ ] #990
[ ] #1252
[ ] #1238
[ ] #14
[ ] #737
[ ] #1160
[ ] #1010
[ ] #1191
[ ] #1390
[ ] #1174
[ ] #878
[ ] #962
[ ] #1015
[ ] #1323
[ ] #1423
[ ] #1019
[ ] #1175
[ ] #1012
[ ] #1065
[ ] #1029
[ ] #979
[ ] #1456
[ ] #1483
[ ] #1115
[ ] #1111
[ ] #1122
[ ] #991
[ ] #1566
[ ] #348

Leaderboard(previously Series)

Add "spotlight" as tab

[ ] #49

[ ] #827

[ ] #1165

[ ] #1165

[ ] #1496

[ ] #1386

Help: FAQ+Tutorials

[ ] #529
[ ] #648
[ ] #401
[ ] #847
[ ] #614
[ ] #1220
[ ] #725
[ ] #1015
[ ] #648
[ ] #737
[ ] #915
[ ] #1015
[ ] #1604

Footer
Quite a few things added in the design, but only 1 linking to issues, which is #702 : jobs
Describe alternatives you have considered
I suppose there will be plenty once we start unpacking page by page, these will be added here once we encounter obstacles.
Screeenshots
Designs are on this link, if you have any questions or require exports, just respond to this thread and tag me.
https://www.figma.com/file/GeVzZKVORd9L8kAWrlKtZv/KodaDot-UX%2FUI?node-id=0%3A1

Hey!
Dope work, love the new design!
Few things:

I have a concern about accessibility color contrast: text => #E6007E on background => #1F1F1F
can we have a light theme page example?
is "checkout flow" possible feature wise?
I find search filters hard for the UX, would it be possible to rework a version less harmful? maybe create a sidebar filter
Not a fan of gradiant button. What would be hover/active state?

What are your thoughts on this?

Hey! Dope work, love the new design!

Thank you!

Few things:
* I have a concern about accessibility color contrast: text => #E6007E on background => #1F1F1F

I've changed the pink color to #FF47AC and bacground to #090909, see new design here. Ran it through a contrast checker plug in which approved it :D

* can we have a light theme page example?

Here we go

* is "checkout flow" possible feature wise?

I suppose this is a Q for @yangwao, but the suggestions was mentioned in #910

* I find search filters hard for the UX, would it be possible to rework a version less harmful? maybe create a sidebar filter
* Not a fan of gradiant button. What would be hover/active state?

Any particular reason why you dislike the gradient? I've positioned the filters at the top so that the images have more space, here's an example with the sidebar and solid buttons.
In regards to the UX of filtera, @cryptodamsky just submitted a proposal to add info to certain sections in #1637 , I think this would be a great addition if we agree on it.

I have no words for this amazing issue and effort someone goes through all of the issues and trying index them into one and whole kodadot v3! A really impressive amount of effort and thank you in the first place!

eliminate double work, outdated PRs/issues and double PRs/issues

if there are, it's bc they left of old process and some of might be reinforcement by logging twice which is good, also be aware that some issues sound similar, they are not. Definitely would chop on our backlog, but some older issues are gems which just weren't implemented fully :)

construct a way for all of us to easily communicate with each other and move rapidly forward

github made discussion boards, where information doesn't lost as in realtime chats

I would suggest holding off on any tutorials and FAQ before the redesign is complete

Rather have tutorial and onboarding material, because migration to new beta took us over 3 months tbh and can't afford loose that amount of time. Rather have outdated onboarding material and as separate process we can upgrade them and learn by doing new one.

"Collections"(these should be easy to view in gallery, not needed in NAV at all)

yes this should be merged as functionality in the gallery I guess, as collection could be enabled there, but if collection is interesting, would be nice users have dedicated entrance point to that

"Spotlight" (I think this should be merged with "series" as a separate tab and I suggest renaming "series" to "leaderboad", as the term is confusing)

Yes and no. Leaderboard is actually term I'm trying steeraway as it put artist into competition bit which is not aim of Spotlight. Rather would be good name to have Spotlight renamed to Artist Directory.

I suggest adding "credit", "transform", "admin", "settings" under a new page called "My profile"

yeah would be nice to have something like "Control Center" I guess
Re design in firma, I would strongly require to have this time some sort of atomic components, before we go for v3
Seems we had tons of issue double fixed or missing somewhere which introduced lot of incosistency across codebase and wasted pretty lot amount of time adjusting components per each instance.
Re design process I would advise starting it as mobile-first design, this seems way much as desktop only so till we will have decide on mobile it can take time.
Plus I don't see anywhere AR/VR/XR buttons tho for our XR efforst

I have no words for this amazing issue and effort someone goes through all of the issues and trying index them into one and whole kodadot v3! A really impressive amount of effort and thank you in the first place!

Thank you! Hopefully it will help us build stuff faster!

eliminate double work, outdated PRs/issues and double PRs/issues

if there are, it's bc they left of old process and some of might be reinforcement by logging twice which is good, also be aware that some issues sound similar, they are not. Definitely would chop on our backlog, but some older issues are gems which just weren't implemented fully :)

Fair enough and understandable.

construct a way for all of us to easily communicate with each other and move rapidly forward

I would suggest holding off on any tutorials and FAQ before the redesign is complete

Rather have tutorial and onboarding material, because migration to new beta took us over 3 months tbh and can't afford loose that amount of time. Rather have outdated onboarding material and as separate process we can upgrade them and learn by doing new one.

Alright, I believe @onerawartist made a tutorial for minting, so that can be added and @cryptodamsky said he is also willing to make some materials. I've updated the landing page design and created a dedicated section for newcomers. I'll keep working on the entire user journey for new useers and we can add the videos etc there.

"Collections"(these should be easy to view in gallery, not needed in NAV at all)

yes this should be merged as functionality in the gallery I guess, as collection could be enabled there, but if collection is interesting, would be nice users have dedicated entrance point to that

It could also be in a drop down from "Gallery?"

"Spotlight" (I think this should be merged with "series" as a separate tab and I suggest renaming "series" to "leaderboad", as the term is confusing)

Yes and no. Leaderboard is actually term I'm trying steeraway as it put artist into competition bit which is not aim of Spotlight. Rather would be good name to have Spotlight renamed to Artist Directory.

Understandable, but I do believe that any kind of table suggests competition, regardless, the term was suggested primarily for easier UX.

I suggest adding "credit", "transform", "admin", "settings" under a new page called "My profile"

yeah would be nice to have something like "Control Center" I guess

Cool!

Re design in firma, I would strongly require to have this time some sort of atomic components, before we go for v3 Seems we had tons of issue double fixed or missing somewhere which introduced lot of incosistency across codebase and wasted pretty lot amount of time adjusting components per each instance.

Fair enough.

Re design process I would advise starting it as mobile-first design, this seems way much as desktop only so till we will have decide on mobile it can take time.

I'll start working on a mobile version of already designed pages so we can have an idea of how it looks like.

Plus I don't see anywhere AR/VR/XR buttons tho for our XR efforst
This will be on the artist profiles and NFTs themselves+ in the filters for search.
If we have some pre-built galleries we can add this to the Nav Bar and/or emphasise in landing.


net/haproxy: add "map" support to haproxy

via IRC; https://www.haproxy.com/blog/web-application-name-to-backend-mapping-in-haproxy/
Motivation:

its a hack of a lot clicky to do ssl offloading + "ACL if host starts with X, [ACTION] then use Backend X,[BACKEND] then use server X,[SERVER] go to y.x.y.z:someport"

Should be implemented just like "Error files" and "Lua scripts": Map files should be managed through the GUI (or the API).

This will be available in os-haproxy 2.8. It will offer basic support for map files. More features will be added based on user feedback.
A simple domain-to-backend map can be created like this:
First create the map file (HAProxy->Advanced->Map Files):

Then create a rule to use this map file (HAProxy->Rules & Checks->Rules):

Finally add this rule to a (HTTP!) public service (HAProxy->Virtual Services->Public Service):

After clicking "Apply", the following is added to haproxy.conf and HAProxy is restarted:
    use_backend %[req.hdr(host),lower,map_dom(/var/etc/haproxy/mapfiles/5b67812585ba87.85158829.txt,testing_backend)]

Of course, this is also available through the API.


AVRO-2431: remove trailing whitespaces from avro C++ files

does not need testing - trivial change.

Looks good to me. Please resolve the conflict, we'll have it merged. Thank you for taking this up.

I would like to request that we only accept trivial and stylistic fixes if they are included with an automated check that will prevent the same stylistic problems being re-introduced later.

@kojiromike - I will investigate if we can add an automation for this. Let's hold off submitting this PR until then.

@aniket486 In #532 I'm attempting to add a build.sh lint command that runs each lang's appropriate linters. In this case maybe it could just be as trivial as git grep -q ' $' lang/c++?

Hello! As part of "prevent the same stylistic problems being re-introduced later", what do you think about adding the .cc and .hh to https://github.com/apache/avro/blob/master/.editorconfig (trim_trailing_whitespace)?  It's not automated, but in the same spirit.

Here are my attempt to add clang-format support for C++: https://github.com/aniket486/avro/pull/1.
It creates these changes to existing files under lang/c++: https://github.com/aniket486/avro/pull/2 - does that look reasonable?

@kojiromike @thiru-apache - what you guys think?

I left some notes on the shell script itself, but I'm not strong in C++, so I'll leave the results checking to the experts.


Capacity Unit definition update

The volume of metadata storage provided by 1 CU needs to be updated from 2GB to 10GB

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 36e52412-4d39-4566-5895-3f83c8198167
Version Independent ID: 1ed309b9-5e29-a1a9-b66c-aafbcd0d35d4
Content: Microsoft Purview governance portal product glossary - Microsoft Purview
Content Source: articles/purview/reference-microsoft-purview-glossary.md
Service: purview
GitHub Login: @evangelinew
Microsoft Alias: evwhite

@Anaig
Thanks for your feedback! We will investigate and update as appropriate.

@Anaig - I'm confirming the available storage, and I'll update as appropriate! Thank you!

@Anaig - You should see those updates by later this afternoon. Thank you!
#please-close


Best way to load a custom page in the admin panel.

Looked through the API and docs and I may have missed it.  What is the best way to add a custom page to the admin panel.  For instance if I want to add a button called Analytics.  And I want to serve a custom page inside the admin panel that has charts and graphs about the sites analytics.
Maybe even render a custom docs page inside the admin area for new users.

Here it is
https://github.com/orionjs/core/tree/master/api#adding-tabs

Will the added tab render the admin layout though ?

Meaning if I create a template for analytics.  How would I make that template render inside of the admin area instead of just routing to the page itself

That function only adds the button, you must create the route and specify the layout. Filesystem and pages uses that function, you can use them as example

Oh good point thanks man.

Perfect

@rwatts3 .... I think I need to do something similar. Can you advise how you went about doing this? I haven't explored the code much yet

Hi.  I haven't done it just yet but have an idea of how I'm going to do it.  I will follow up once I implement my feature.


SFPNOP is not issued after required instructions in certain cases.

The compiler is not issuing SFPNOP instructions at least after SFPMUL instructions in certain scenarios even when they are needed.
Example scenario :
Architecture : wormhole_b0
OS : Ubuntu 20.04.6 LTS
When the power_tile function is called it eventually calls calculate_power_iterative which gets inlined. The  function has a 2 level loop. The outer loop gets unrolled.
template <bool APPROXIMATION_MODE,int ITERATIONS = 8>
inline void calculate_power_iterative(const uint exponent)
{
    #pragma GCC unroll 8
    for (int d = 0; d < 8; d++)
    {
        vFloat in = dst_reg[0];
        vFloat result = 1.0f;
        for (uint i = 0; i < exponent; i++) {
            result *= in;
            // TTI_SFPNOP;
        }
            dst_reg[0]=result;
        dst_reg++;
    }
}

When the power_tile function is itself called within a loop, during the unrolling and inlining SFPNOP instructions are not issued after SFPMUL  instruction in the last 5 out of the total 8 unrolled instances leading to wrong result.
    7834:	00ee0863          	beq	t3, a4, 7844 <kernel_launch()+0x38c>
    7838:	18006402          	sfpmul	L0, L0, L1, L9, 0
    783c:	00170713          	addi	a4, a4, 1
    7840:	ff5ff06f          	j	7834 <kernel_launch()+0x37c>
    7844:	c8030001          	sfpstore	0, L0, 0, 3

How to reproduce:
Architecture : wormhole_b0
OS : Ubuntu 20.04.6 LTS
In the branch
https://github.com/tenstorrent/tt-metal/tree/amahmud/power_debug,
running the python test
pytest ./tests/tt_eager/python_api_testing/unit_testing/misc/test_moreh_norm.py
will compile the kernel ./ttnn/cpp/ttnn/deprecated/tt_dnn/op_library/moreh_norm/moreh_norm_h/kernels/moreh_norm_h_kernel.cpp
This kernel calls power_tile within a loop that will run only once and produces redundant values in the place of padded zeroes of the output tensor due to the mentioned issue. You can see the missing SFPNOPS by generating assembly code for the file in
/tt-metal/built/<generated-number>/kernels/moreh_norm_h_kernel/<generated-number>/trisc1/trisc1.elf
In my branch I have already generated and dumped the assembly code and elf files in the folder /tt-metal/assembly/ with appropriate names
The code in the moreh_norm_h_kernel.cpp will call power_tile within a loop, but if you comment that part and uncomment the code above which does the same thing but not being within a loop, the issue will not be encountered.
void MAIN {

    // OMITTED CODE

/*
    // **The following code produces the correct output.**

    // DPRINT_PACK( DPRINT << "EXECUTE POWER \n";)
    ACQ();
    cb_wait_front(cb_x, onetile);
    cb_reserve_back(cb_y, onetile);

    // copy
    copy_tile_init();
    copy_tile(cb_x, 0, dst0);

    // power
    power_tile_init();
    power_tile(dst0, p);

    pack_tile(dst0, cb_y);

    cb_push_back(cb_y, onetile);

    cb_pop_front(cb_x, onetile);
    REL();
*/

    **// The loop below runs only once, but unlike the code above will miss issuing SFPNOPs
    // In the correct places.**

    // DPRINT_PACK(DPRINT << "num_cols_per_core " << num_cols_per_core << "\n"; )
    // DPRINT_PACK(DPRINT << "Ht " << Ht << "\n"; )
    // This loop only runs once.
    for (uint32_t col_idx = 0; col_idx < num_cols_per_core; ++col_idx) {
        // This loop only runs once.
        for (uint32_t row_idx = 0; row_idx < Ht; ++row_idx) {
            // DPRINT_PACK( DPRINT << "EXECUTE POWER \n";)
            // The following code is identical to the above but produces incorrect output.
            ACQ();
            cb_wait_front(cb_x, onetile);
            cb_reserve_back(cb_y, onetile);

            // copy
            copy_tile_init();
            copy_tile(cb_x, 0, dst0);

            // power
            power_tile_init();
            power_tile(dst0, p);

            pack_tile(dst0, cb_y);
            cb_push_back(cb_y, onetile);

            cb_pop_front(cb_x, onetile);
            REL();
        }
    }
}  // void MAIN
}

Without loop (gives correct result and has SFPNOP after every SFPMUL)
power_no_loop_correct.txt
With loop (does not have SFPNOP after 5 instances of SFPMUL)
power_loop_bug_asm.txt
This issue has been identified from issue : https://github.com/tenstorrent/tt-metal/issues/7928

Compiler sources updated. binary PR raised  https://github.com/tenstorrent/tt-metal/pull/12061

Updated compiler merged https://github.com/tenstorrent/tt-metal/pull/12061


Downloading annotation extensions should use the standard syntax

Is the output meant to look like this?
PomBase:SPBC216.07c	serine/threonine protein kinase Tor2		GO:0004672	"{""relationship"": {""relation"": [{""id"": ""GOREL:0000752"", ""label"": ""has_direct_input""}], ""id"": ""PomBase:SPAC1B9.02c"", ""label"": ""PomBase:SPAC1B9.02c""}}"	PomBase	NCBITaxon:4896	IDA				PMID:22976295	20151027
PomBase:SPBC216.07c	serine/threonine protein kinase Tor2		GO:0004672	"{""relationship"": {""relation"": [{""id"": ""GOREL:0000752"", ""label"": ""has_direct_input""}], ""id"": ""PomBase:SPAC22E12.14c"", ""label"": ""PomBase:SPAC22E12.14c""}}"	PomBase	NCBITaxon:4896	IDA				PMID:22976295	20151027

column headers would be helpful
I'd rather see extensions formatted in the same way that we construct them...there is a lot of duplication in theis output. And too many """"":[{]

I now see this is jsn format? would people ewant this in a standard tab delimited file.
I tried a different option (annotation extesnion class labal)
This gives me:
PomBase:SPBC14F5.08	mediator complex subunit Med7		GO:0030295	PomBase	NCBITaxon:4896	IDA				PMID:10625684	20160908	regulation of transcription from RNA polymerase II promoter
PomBase:SPAC2F3.15	P-TEFb-associated cyclin-dependent protein kinase Lsk1		GO:0004693	PomBase	NCBITaxon:4896	IMP				PMID:17502918	20151109

No extension if the extension is a gene product
No extension relation

next option gives me some craziness:
PomBase:SPBC14F5.08	mediator complex subunit Med7		GO:0030295	PomBase	NCBITaxon:4896	IDA				biological regulation|biological_process|regulation of RNA biosynthetic process|regulation of nucleobase-containing compound metabolic process|regulation of macromolecule metabolic process|regulation of transcription, DNA-templated|regulation of nitrogen compound metabolic process|regulation of nucleic acid-templated transcription|regulation of biosynthetic process|regulation of transcription from RNA polymerase II promoter|regulation of cellular process|regulation of RNA metabolic process|regulation of gene expression|regulation of macromolecule biosynthetic process|regulation of metabolic process|regulation of cellular macromolecule biosynthetic process|regulation of biological process|regulation of cellular biosynthetic process|regulation of primary metabolic process|regulation of cellular metabolic process	PMID:10625684	20160908
Is there an option which gives me the annotated extension?
i.e.
has_direct_input PomBase:SPBC19F8.07,part of regulation of transcription from RNA polymerase II promoter

I'm afraid this is also an extension of the issues around #201 .

201 is about how to better query using information in the extension.
I think @ValWood just wants an extension column that is identical to the source GAF. This should be straightforward but plumbing at a few different places:

[ ] Extend association schema to include a field annotation extension (source)
[ ] Extend owltools-solr to populate this with the exact string, prior to parsing
[ ] Remove json from list of defaults

Some additional side-issues

[ ] Show column headers
[ ] Remove unused fields (e.g. geo)
[ ] General user-friendliness stuff

Spot on!  Thanks.

Dupe #94 then.
For the additional issues, one of the reason that we agreed to the "pseudo-gaf" is so we do not have to pipe the solr output through a proxy to add decorations.


Bug: user-defined max_decoding_message_size is not used in some cases (client streaming response decoding)

Bug Report

Version
tonic 0.9.1
tonic-build 0.9.1
Platform
Fedora 37 x86_64
Crates
tonic
Description
I recently updated tonic to v0.9.1, and I experienced breaking changes due to DEFAULT_MAX_RECV_MESSAGE_SIZE. It's ok, we can increase this limit with max_decoding_message_size() and max_encoding_message_size() (in both server and client !), and it did fix "message lenth too large" errors for normal requests/responses (I increased it to 60MB).
However, I still have these errors in stream responses decoding, when calling if let Some(stream_response) = request.message().await.unwrap() :
TonicStatus status: OutOfRange, message "Error, message length too large: found 6877902 bytes, the limit is: 4194304 bytes", details: [], metadata: MetadataMap { headers: {} }

In Grpc::create_response() if found that in a some cases, the codec::decode::Streaming is created without the user-defined max_decoding_message_size, when calling Streaming::new_empty(...) here :
https://github.com/hyperium/tonic/blob/9990e6ef9d00394b5662719662062cc85e6e4700/tonic/src/client/grpc.rs#L352-L364
But I do no have a complete understanding of the tonic crate, so I did not open a pull-request for this issue yet
Thank you !

Hi @checkline1052, I wrote a test to try and reproduce what you were stating above but from what I can tell everything works as intended. Please take a look at https://github.com/hyperium/tonic/pull/1363 and see if this differs from your code.

Thanks you for the integration test, I was doing something wrong !


chore(main): release 0.44.0

:robot: I have created a release beep boop
0.44.0 (2024-02-06)
Features

Pipeline: add support for dataset parameter (#545) (cd8d024)

Bug Fixes

Schema: Add a BigInt scalar (#553) (524ba2a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-frontend/releases/tag/0.44.0 :sunflower:


173 validate before save field

Q
A

Branch
master

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Fixed issues
chameleon-system/chameleon-system#173

License
MIT

Uses now validation before save: most functionality is moved to "PostSaveHook()".
Table fields are correctly created and deleted if needed.

Thanks @UlrichKu


Latest version 3.0.0-beta.4 is not published to npm

Describe the bug
The package.json's version of packages/react-virtual was bumped to 3.0.0-beta.4 but that version is not published to npm (the latest version published to npm is 3.0.0-beta.2).
Your minimal, reproducible example
https://stackblitz.com/github/TanStack/virtual/tree/beta/examples/react/fixed
Steps to reproduce

Clone a specific example
Install the dependencies
An error is raised as the version can't be found in the registry

Expected behavior
I was expecting the versions referenced in the examples to be published.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

OS: MacOS
Browser: Brave

tanstack-virtual version
3.0.0-beta.4
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

I was going nuts with the inconsistency between the DOCS and the actual versions that are published.
For other reader:
If you get

scrolltoindex is not a function

You need version 3.0.0-beta.4, which is not published as mentioned in this issue.
@tannerlinsley Are you still actively working on this repo?

For other reader:
If you get

scrolltoindex is not a function

You need version 3.0.0-beta.4, which is not published as mentioned in this issue.)

I think you are having a different issue. We use 3.0.0-beta.2 and scrollToIndex is available.

For other reader:
If you get

scrolltoindex is not a function

You need version 3.0.0-beta.4, which is not published as mentioned in this issue.)

I think you are having a different issue. We use 3.0.0-beta.2 and scrollToIndex is available.

Interesting 🤔 i will check. Thanks 🙏

bump, can we expect this to be released to NPM?

Making some new releases now. Thanks for your patience!


Save files now encrypted?

Experimental Alpha52 save files have changed. Looks like they are encrypted.

well of course they are duh!!!!!!

Guessing this is dead if there's no way to decrypt them eh?


Don't be sensitive to case when searching an identity

I guess this is not possible. It depends of @c-geek API ?

I guess this is not possible. It depends of @c-geek API ?

It is more a uCoin implementation issue then.