Scott W

using setPipeline('Light2D') on my sprites / tilemaps make them disappear

1

## Version * Phaser Version: 3.55.2 * Operating system: macOS * Browser: Tried with Chrome & Brave ## Description When using `setPipeline('Light2D')` on any of my game objects or tilemap...

I'd like to be able to disable sorting of messages. I know os.Getenv probably isn't the best way to pass this flag, so tell me how it should be done...

adds "integration testing" for our components - all components run simultaneously pointed at mock kube apiservers which impersonate clusters. supports blackbox testing of our translation pipeline all in-process of one...

because services are more useful/common in the world of routing, and they can be used to front multiple deployments, it makes sense that a user can instead give us a...

currently whenever we target a mesh with a policy (e.g. virtualmesh) we require selecting the mesh by reference. this violates the design principle of **not requiring users to directly interact...

currently our destination selectors (used by traffic policy) can only select `kube` destinations. now that our system supports more types of destinations (`virtual`, `externalService`), we should add those to the...

changing params for virtualmesh signing cert should re trigger issuedcertificate

1

**Describe the bug** verified by modifying `orgName` in self-signed certificate parameters inside vmesh `spec. **To Reproduce** apply any vmesh, e.g. ```yaml apiVersion: networking.mesh.gloo.solo.io/v1alpha2 kind: VirtualMesh metadata: labels: app: bookinfo-policies app.kubernetes.io/name:...

gloo-mesh networking errors all input resources on boot

1

**Describe the bug** currently, gloo-mesh does not wait to process/create clients for all registered clusters before it begins reconciling. therefore, the first few iterations of the reconciler will produce the...

default warning AppMesh missing crds message to "off"

1

we currently throw a repeated warning when the appmesh Mesh CRD Is not found on a cluster: https://github.com/solo-io/service-mesh-hub/blob/ece2937dcd2c4e3cd8acac5ec7c1078f7de0f2fa/pkg/mesh-discovery/reconciliation/discovery_reconciler.go#L56 this simply indicates the AppMesh Mesh CRD is not registered, which is...

seems like `meschtl cluster deregister` is sharing flags with `meschtl cluster register`, many of which are invalid / do not apply: https://docs.solo.io/service-mesh-hub/latest/reference/cli/meshctl_cluster_deregister/