[（live．free™！）] Atlético Madrid vs Las Palmas Live Streams Free LA LIGA ON TV Channel 3 NOV 2024

How To Watch Atletico Madrid vs Las Palmas La Liga 2024-25 Free Live Streaming Online? Get Live Telecast Details of Spanish League Football Match With Time in IST
CLICK HERE TO WATCH LIVE STREAM

CLICK HERE TO WATCH LIVE STREAM

CLICK HERE TO WATCH LIVE STREAM

How to watch La Liga match between Atletico Madrid and Las Palmas, as well as kick-off time and team news.
Atletico Madrid will aim to bounce back from a shock away defeat in the Spanish top-flight when they resume their La Liga campaign with a clash against Las Palmas on Sunday.
Diego Simeone took full accountability for the hosts' lacklustre showing after their unbeaten streak in La Liga came to an end with a narrow 1-0 defeat to Real Betis over the weekend.
Atleti couldn't recover from an early setback, as an own goal by Jose Maria Gimenez in the fourth minute put them behind. They struggled to capitalize on the few opportunities they managed to create, with mistakes throughout the match.
Currently, Atleti hold fourth place in the La Liga standings, trailing Barcelona by ten points, while relegation-threatened Real Betis sit in 18th place with nine points from their first 11 games of the 2024-25 season despite a 1-0 victory last Saturday.
Here, GOAL brings you everything you need to know about how to watch, including TV channel, streaming details and more.
How to watch Atletico Madrid vs Las Palmas online - TV channels & live streams
Premier Sports 2	Watch here
LaLigaTV	Watch here
In the UK, the La Liga match between Valencia and Real Madrid will be available to watch and stream online live through Premier Sports and La Liga TV.
Check out GOAL's Live Match Centre for updates.
How to watch anywhere with VPN
If you are abroad, you may need to use a virtual private network (VPN) in order to watch games using your usual streaming service. A VPN, such as NordVPN, allows you to establish a secure connection online when streaming. If you are not sure which VPN to use, check out GOAL's guide to the best VPNs for streaming sport.
logo
Stream live anywhere in the world with Nord VPN
Get NordVPN
Atletico Madrid vs Las Palmas kick-off time
Date:	Sunday, November 3, 2024
Kick-off time:	1:00 pm BST
Venue:	Riyadh Air Metropolitano
The La Liga match between Atletico Madrid and Las Palmas will be played at Riyadh Air Metropolitano in Riyadh Air Metropolitano, Spain.
It will kick off at 1:00 am BST on Sunday, November 3, 2024, in the UK.
Team news & squads
Atletico Madrid team news
New Las Palmas boss Diego Martinez couldn't have asked for a stronger debut, as his team snapped a winless La Liga streak stretching back to February, ending a 23-game drought. This crucial victory not only moved them past Valencia but also lifted them off the foot of the table.
Marvin Park is still sidelined with a hamstring injury, while Sandro Ramirez nears the end of his recovery from a muscle strain and could be available for selection this weekend.
Martinez may opt to field the same lineup that started against Valencia, featuring Fabio Silva—on loan from Wolverhampton Wanderers and Oli McBurnie—in attack, along with left-back Alex Munoz, who netted the decisive goal in their previous outing.
Atletico Madrid possible XI: Oblak; Molina, Witsel, Gimenez, Lino; Koke, De Paul, Gallagher; Griezmann; Alvarez, Sorloth
Position	Players
Goalkeepers:	Oblak, Musso
Defenders:	Gimenez, Lenglet, Molina, Witsel, Galan, Mandava, Le Normand
Midfielders:	Gallagher, De Paul, Koke, Lino, Llorente, Riquelme
Forwards:	Griezmann, Sorloth, Correa, Alvarez, Simeone
Las Palmas team news
For Atletico Madrid, Clement Lenglet, Pablo Barrios, Marcos Llorente, Robin Le Normand, and Cesar Azpilicueta are set to miss this weekend’s action.
Manager Diego Simeone is likely to stick with his usual lineup despite the loss to Betis. In the attack, Antoine Griezmann, Alvaro Morata, and Alexander Sorloth are expected to feature again, with Simeone hoping the trio will begin to find their rhythm in the coming weeks.


Media HueBot on Service Fabric (SF) cluster environment?

I have switch my local Service Fabrics to work in 5-node mode, change Local.5node.xml config file to have HueBot_TargetReplicaSetSize=2 and tried to launch HueBot sample app. Obviously it failed with exception "There is already a listener on IP endpoint <IP_ADDRESS>:8445. This could happen..." while initializing media platform.

It is clear that our second Bot instance tried to use the same port for media platform, but how it should correctly behave in SF cluster? Does SF have out of the box load balancer for such use cases or we need our own?
How can I make it work on cluster with more than 1 active replica?
And in general do we have an option to run more than 1 instance of media bot on 1 physical machine/VM?
Thanks in advance!

In the SF cluster there is 1 partition per node, so each node can have the port 8445 reserved.  This does not work locally because you have 5 partitions per node (your local machine).  The HueBot sample does not support 5 node local runs.
It is important that the media platform is configured to have 1 process per VM (1 partition per node).  Internally it does thread optimization which does not work well with multiple media platforms running.  This also means that the media platform does not support replicas.  If you look at the sample  you'll notice that the partition count == node count, this is not by accident.
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/15b8070a5b65ee0829823bbd7d0fa5d527ba8879/Samples/V1.0Samples/LocalMediaSamples/HueBot/HueBotSF/ApplicationParameters/Cloud.xml#L4-L6
Even if the media platform did support replicas, there is no way today to revive a media session.  The recommended way of recovering a dead call is to do a dial out, or rejoin (using the ChatInfo and MeetingInfo provided in the call)

@ssulzer can add more detail why only a single instance of the MP should run on a given VM.

Great, thanks!
So if I will create SF cluster that consists of 5 nodes (separate VMs that have public ips), media Huebot will be able to launch its instances on all of them. But still it is not clear how it will work during the call? If I understand correctly in this case we should have load balancer with own custom logic that would route new call notifications to free nodes and established call notifications to same nodes. Please correct me if I am wrong.
Any recommendations in this area?
Thanks!

SF comes with a software LB when addressing the cluster.  That is only required for the initial call setup.

Also, while having a public IP for each VM is recommended, it is possible to do this with only one public IP.  You can specify an external port and an internal port.  The SF reverse proxy is able to map to the right instance/port.  The downside of this is that you introduce an extra hop, which is not ideal for media flow.

After the call has been set up you configure a callback URI and an MP host/port

do you mean this part of sample?
builder.SetNotificationUrl(options.BotBaseUrl.ReplacePort(options.BotBaseUrl.Port +   serviceContext.NodeInstance()));
builder.SetMediaPlatformSettings(this.MediaInit(options, serviceContext));

Yes, that's right. In MediaInit you'll see configuration of public and internal ports:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/15b8070a5b65ee0829823bbd7d0fa5d527ba8879/Samples/V1.0Samples/LocalMediaSamples/HueBot/HueBot/Bot/Bot.cs#L337-L344
Internal port is always 8445, and public port will be 8445 + instance number
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/e7755438737274c00d0081e9b1d8a3c8fc5eb42b/Samples/V1.0Samples/LocalMediaSamples/HueBot/HueBot/appsettings.json#L14

Do we need to make any manipulations to enable stickiness on SF balancer? By the way do you know how does it work? Does it work by sender ip,  X-Microsoft-Skype-Chain-Id header, etc?
Also does SF balancer have possibility to route new calls to nodes that have lower load than others? If no, do you know how such scenario can be supported?
Many thanks!

No manipulations needed.  It works by port.  If the cluster port is specified, it will direct to the cluster.  If a partition port is specified it will direct to the partition.  The ARM deployment script configures the NAT pools:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/15b8070a5b65ee0829823bbd7d0fa5d527ba8879/Samples/V1.0Samples/LocalMediaSamples/HueBot/HueBot/ARM_Deployment/AzureDeploy.json#L206-L208
I believe you can configure the SF LB, but I am not sure how.  BTW, it is dangerous to route new calls to nodes with lower load.  Consider a faulty node, where all calls routed to it are terminated immediately.  It will have low load, which will result in disproportionate % of calls being sent there and killed.  Round robin is safer.  If you really want to go advanced you can have partition groups, and an LB that directs traffic to the partition group with lowest load.  I don't know how you could achieve such a configuration in SF.

No manipulations needed. It works by port.

Not sure I understand how it works. In the Azure portal we are setting signalling web hook for calls. In our case it is going to be cluster alias.

And AFAIU media platform will use it for sending notifications. How we will achieve stickiness by port in this case? Does media platform differentiate node from which it get the response?
Thanks!

Running locally is different than running in Azure.  Local runs only have 1 instance, so all you need to do is redirect the signaling http traffic to your open signaling port (9441 I think?)  and media tcp traffic to your open media port (8445).  Ngrok does this for you.  Because local runs are only 1 instance, the global URI can be the same as the instance specific URI, and the global media port is the same as the instance specific port.
In azure, there global callback URI is your cluster URI, and when hit it will distribute the request to one of your partitions.  After that all traffic must be sticky to that partition for the remainder of the call.  Each partition knows it's own media and signaling ports, and specifies them in the ICommunicationsClientBuilder.SetNotificationUrl and the MediaPlatformSettings.  These new settings get used to notify the bot of any changes for that call, and allow the media to flow.

Thanks a lot, Kamil, for your answers!


CI-ONLY: builds of cardano-sl-0.6-staging branch

Don't merge this branch.

@georgeee why was this merged?


Create initial Spotter

Spotter is the famous moldable interface to search all sorts of things. We need it in the new world.

The current state of the Spotter:

We close this one and open more specific issues when needed.


rtk::Reg1DExtractShroudSignalImageFilter is not wrapped

There is currently a nowrap file but more work than renaming is probably required to have it wrapped.

Hello,
I am trying to extract the breathing signal from a shroud image in python, which would need the function rtk.Reg1DExtractShroudSignalImageFilter. Is this issue easily solvable or should I instead look at implementing a solution outside of the ITK/RTK framework ?
Best,
Valentin

It is a bit hard to anticipate but you can give it a try. Are you able to wrap ITK with RTK on your computer? If yes, then rename nowrap to wrap and check what is the issue. We can help to address it... Maybe @arobert01 knows what is the issue with 1D images in ITK wrapping.

To be honest, I don't know how to do that... I have just installed the itk-rtk python package with pip, but I can try to do it if I have some instructions.

You need to check ITK's software guide on how to compile. In the cmake compilation options, activate python and the RTK module.  I instead added DITK_WRAP_IMAGE_DIMS:STRING="1;2;3;4" in the hope it would help with this issue).
But when I try to build the project in Visual Studio, I am getting a lot of errors (see text file).
build.txt


protoc-gen-dhall

On finish, add it to https://github.com/protocolbuffers/protobuf/blob/master/docs/third_party.md.
Resources:

plugin.h - Protocol Buffers documentation

https://github.com/awakesecurity/proto3-suite might make this unnecessary. Would need to work out the entire flow.


[General] Cleanup array position based operations

Some logic depends on the position of a string in an array.

Mostly in validation service. Wherever we are doing string splits.
Maybe you can identify lines where this happens and mention them here before going on to resolve them.


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.6 to before v5.10.96",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d380dcde9a07ca5de4805dee11f58a98ec0ad6ff",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d71b06aa995007eafd247626d0669b9364c42ad7"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d380dcde9a07ca5de4805dee11f58a98ec0ad6ff",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "d71b06aa995007eafd247626d0669b9364c42ad7",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "tracing/histogram: Fix a potential memory leak for kstrdup()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.96 by commit d71b06aa995007eafd247626d0669b9364c42ad7, it was introduced in version v5.6 by commit d380dcde9a07ca5de4805dee11f58a98ec0ad6ff. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000185


Update scalafmt-core to 2.6.4

Updates org.scalameta:scalafmt-core from 2.6.3 to 2.6.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master      #64   +/-   ##
=======================================
  Coverage   79.24%   79.24%
=======================================
  Files           6        6
  Lines         106      106
=======================================
  Hits           84       84
  Misses         22       22

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 19510fa...f112b87. Read the comment docs.


Reduce the number of segments to wait for convergence when rebalancing

Instructions:

The PR has to be tagged with at least one of the following labels (*):

feature
bugfix
performance
ui
backward-incompat
release-notes (**)

Remove these instructions before publishing the PR.

(*) Other labels to consider:

testing
dependencies
docker
kubernetes
observability
security
code-style
extension-point
refactor
cleanup

(**) Use release-notes label for scenarios like:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

Codecov Report

Merging #10028 (d9d3a4e) into master (880a5c7) will decrease coverage by 39.20%.
The diff coverage is 72.72%.

:exclamation: Current head d9d3a4e differs from pull request most recent head f7db876. Consider uploading reports for the commit f7db876 to get more accurate results

@@              Coverage Diff              @@
##             master   #10028       +/-   ##
=============================================
- Coverage     64.28%   25.07%   -39.21%
+ Complexity     5669       44     -5625
=============================================
  Files          1939     1982       +43
  Lines        105033   107136     +2103
  Branches      16041    16295      +254
=============================================
- Hits          67518    26868    -40650
- Misses        32631    77553    +44922
+ Partials       4884     2715     -2169

Flag
Coverage Δ

integration1
25.07% <72.72%> (?)

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ntroller/helix/core/rebalance/TableRebalancer.java
54.17% <61.53%> (-19.87%)
:arrow_down:

...ore/assignment/segment/SegmentAssignmentUtils.java
42.02% <88.88%> (-55.45%)
:arrow_down:

...ain/java/org/apache/pinot/spi/utils/LoopUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...in/java/org/apache/pinot/spi/utils/BytesUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/BaseRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/NoOpRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/table/FSTType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/user/RoleType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/stream/StreamMessage.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1603 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Collect objects from third_party/libdrm

The third_party/libdrm is build and used by some code of content module, but the linker could build electron without it since electron is not using related code. However the linker of mips64el is not so advanced to optimize the dependency out and we have to ship it as part of libcc.

I have tested this build with Electron and both Debug and Release builds were working.


Technical Test Related Pull Requests

First things first: Update Django to latest release in 1.7 series (1.7.11)
Whilst this version is still unsupported and we will still need
to move to a newer version this will fix a few security issues.
Update tox config from django171 to django1711
For more information on django 1.7 security releases please see:
https://docs.djangoproject.com/en/1.7/releases/security/
All work was performed on a feature branch and then merged to develop. It would usually have gone through a review process by the time this happened. I could have pushed the feature-branch to enable this.
Summary of actions:
- The feature branch 'feature/django-security-update' was merged into 'develop'
- Feature branch 'feature/django-security-update' has been removed
- You are now on branch 'develop'

Thanks @hairychris - going to close the PR so it's not hanging around, and will review and get back to you.

@hugorodgerbrown thanks, please don't review yet I've still got to merge a feature branch. I'll post here when that's done. =)

I have merged the feature branch and pushed, it's not showing here as the pull request is closed. Feel free to check it out on my profile though.

:thumbsup:
On 11 April 2017 at 11:18, Chris Franklin<EMAIL_ADDRESS>wrote:

I have merged the feature branch and pushed, it's not showing here as the
pull request is closed. Feel free to check it out on my profile though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yunojuno/django-test/pull/8#issuecomment-293214897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMQ8PtbL_FHjFQvqpUVqiXfiSFkzB-Dks5ru1N-gaJpZM4M5Csc
.


[FEATURE REQ] ContinuablePageFlux::byPage(C continuationToken, int pageSize)

When paginating query results, the notion of continuation token and page-size specify the page boundaries. So we need support for configuring both page-size and continuation token in the ContinuablePageFlux::byPage(.)
please add the following method:
ContinuablePageFlux::byPage(C continuationToken, int pageSize)
This is an ask by CosmosDB SDK and we discussed with Jonathan and Anu offline.

This is being worked on in PR #6465

Closing this issue as the mentioned PR (#6465) has been merged and released.


[Question] Detect Plugin is Host Assembly.

We have a subsystem that uses plugins. In a use case where we are building Integration Tests (using NUnit) the plugin interfaces form the interfaces to that subsystem.
Effectively that NUint assembly has classes that also implement the plugin interfaces each as a mock of sorts. The subsystem tries to load the Unit Assembly to get to those plugin interfaces on the basis that I need to be able to get to those interfaces from the Unit test assembly to invoke the specifics of the tests.
The plan was to use a static class to manage the integration.
When one uses the PluginLoader.CreateFromAssemblyFile it of course loads another instance of the assembly. This instance appears to have a different static scope so the NUnit Test classes can't get to the same instance of the static class as the plugin do.
I'm trying to minimize impact of custom code to make the tests work, so do you have any recommendations on if its possible to short circuit and create a PluignLoader class directly by otherwise detecting that the assembly is already loaded and attach a PluginLoader to it?
If I understand this correctly, if this is possible that it will use the same instance of the assembly and the static classes data will be shareable?
Id assume to disable both EnableHotReload, and IsUnloadable

FYI. this is what I did and its seems to work:
 var fullAssemblyPath = Path.GetFullPath(pluginConfiguration.FullPath(PluginRootPath));
 var assemblies = AppDomain.CurrentDomain.GetAssemblies().Where(p => !p.IsDynamic);;
 var loadedAssembly = assemblies.FirstOrDefault(assembly1 =>assembly1.Location == fullAssemblyPath);
 var (pluginLoader, assembly) = loadedAssembly is not null
     ? (CreateLoader(fullAssemblyPath), loadedAssembly)
     : LoadAssembly(fullAssemblyPath);


Dev with hkr base

Tracked by: LRS-839

I'm seeing:
3 compilation warnings found; 1 expected
In the Windows build. Can you check, please?

I see
third-party/json.hpp
This file addition, looks like a mistake as now it is cloned during cmake


Validate PushConstants annotation and type

Check that PushConstant OpVariable is identified by Block decoration and type is struct or array of structs.

Addresses #2005

PTAL

Filed https://github.com/KhronosGroup/glslang/issues/1609 for the invalid glslang test this check exposes.


Updates the version + adds no_proxy

Multiple issues being encountered when running cert-manager.
We also haven't updated the version in a while since a new version of
k8s and kubeadm has already gone out.
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

@kairen :)

@cdrage Just so you know, I will join Red Hat Taiwan in next month! :)


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:40: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:40: missing_license_family: The recipe is missing the about/license_family key.
WARNING: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
ERROR: /tmp/abs_feb6scolzk/clone/recipe/meta.yaml:40: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:14: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
ERROR: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:40: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:40: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_12_tn2frpi/clone/recipe/meta.yaml:40: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


Listener(load balancer) is losing - has not ready endpoints (addresses) after emqx pod restart

Description of the bug:
After upgrade of emqx operator and emqx image to newest version (from apiVersion apps.emqx.io/v2alpha1 to apps.emqx.io/v2beta1) we are facing with the issue that sometimes pods are not any more binded to loadbalancer service. It happens if emqx pod is restarted by some reason after deployment.  Emqx pod is up and running after restart but StatefulSets has pending status for that pod. Listeners (LoadBalancer) service does not have endpoint for that pod any more after restart.
To Reproduce
This can be easy reproduced also on minikube on emqx-operator version: 2.2.x (tested on 2.2.4 - 2.2.10) and emqx version: 5.3.2 or later, if you e.g. manually delete emqx pod or if you descale/scale Statefulset. Pod is ready up and running, but stateful set has pending status for that pod forever.
This is not the case in previous versions (apiVersion: apps.emqx.io/v2alpha1) - pods are binded to loadbalancer without any issue if you e.g. delete manually one of the emqx pods or descale/scale Statefulset (operator version 2.1.2, emqx version 5.0.24).  Listener/LoadBalancer service is binded with the pod correctly.
The only way to fix that issue is destroying/recreating emqx pods.
Environment details::

Kubernetes version: v1.26.6
Cloud-provider/provisioner: azure (reproduced on minikube)
emqx-operator version: 2.2.x (tested on 2.2.4 - 2.2.10)
emqx version: 5.3.2 +
Install method: terraform (helm_release for operator, kubernetes_manifest for emqx)

Thank you for your response,
Anže.

 Pod is ready up and running, but stateful set has pending status for that pod forever.", and you also side "The only way to fix that issue is destroying/recreating emqx pods."  This sounds contradictory.
I'm deploy EMQX CR in my minikube cluster, and I'm manually delete some one pod, and wait it recreate, looks good.
PS: I don't recommend scale statefulset directly. It will be tuned back by emqx operator. You should modify EMQX CR.

Yes, after deletion emqx pod is successfully recreated in both cases - in versions 2.1.2 and also in version e.g. 2.2.5).
I have example with 2 replicas. In version 2.1.2 both pods are bind with endpoints to load balancer correctly if I deleted one of them.
But if you try reproduce it in never version of operator (v2beta1 - 2.2.x) after deleting one pod, statefulsets has only 1/2 pods ready. And if you look at listener (LoadBalancer) service, only endpoint from ready pod is associated (recreated pod's endpoint is not exposed any more).

in EMQX pods, I set the ReadinessGates, and EMQX operator controller will check if this pods is already in EMQX cluster, if they already joined, they will be ready. So if pods can not ready, I think there are two possibilities:

EMQX operator is not work, so pods can not be ready.
the EMQX in the pod is not join the EMQX cluster, you can running emqx ctl cluster status in this pod to check it.

I run it from one of pods:
emqx@test-emqx-core-57bcb74d8d-1:/opt/emqx$ emqx ctl cluster status
Cluster status: #{running_nodes =>
<EMAIL_ADDRESS><EMAIL_ADDRESS>stopped_nodes => []}
but "kubectl get statefulsets" says:
NAME                                          READY   AGE
test-emqx-core-57bcb74d8d   1/2         98m
And there is only one endpoint visible from:
kubectl describe service test-emqx-listeners
Name:                     test-emqx-listeners
Namespace:                default
Labels:                   apps.emqx.io/instance=test-emqx
apps.emqx.io/managed-by=emqx-operator
Annotations:              apps.emqx.io/last-applied:
UEsDBBQACAAIAAAAAAAAAAAAAAAAAAAAAAAIAAAAb3JpZ2luYWykVFtv8zYM/S98tjzLyb6ketsVGLBLtmXF0GYPskwHQmTJleSubeD/PtCXxMnSYfj6JpM0eXh4yCPIRt+jD9pZEP...
service.beta.kubernetes.io/azure-load-balancer-resource-group: anze-test
Selector:                 apps.emqx.io/db-role=core,apps.emqx.io/instance=test-emqx,apps.emqx.io/managed-by=emqx-operator
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
IP:                       <IP_ADDRESS>
LoadBalancer Ingress:     <IP_ADDRESS>
Port:                     tcp-mqtt  1883/TCP
TargetPort:               1883/TCP
NodePort:                 tcp-mqtt  32472/TCP
Endpoints:                <IP_ADDRESS>:1883
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
Br, Anze.

Is the EMQX operator is running ? and could you please show those two EMQX pod status

kubectl get pods
NAME                                                     READY   STATUS    RESTARTS   AGE
emqx5-emqx-operator-controller-manager-94b888f65-ppxrr   1/1     Running   0          158m
test-emqx-core-57bcb74d8d-0                              1/1     Running   0          155m
test-emqx-core-57bcb74d8d-1                              1/1     Running   0          153m
POD0:
kubectl describe pod test-emqx-core-57bcb74d8d-0
Name:         test-emqx-core-57bcb74d8d-0
Namespace:    default
Priority:     0
Node:         minikube/<IP_ADDRESS>
Start Time:   Tue, 09 Jan 2024 12:42:12 +0100
Labels:       apps.emqx.io/db-role=core
apps.emqx.io/instance=test-emqx
apps.emqx.io/managed-by=emqx-operator
apps.emqx.io/pod-template-hash=57bcb74d8d
controller-revision-hash=test-emqx-core-57bcb74d8d-86f944c4f
statefulset.kubernetes.io/pod-name=test-emqx-core-57bcb74d8d-0
Annotations:
Status:       Running
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  StatefulSet/test-emqx-core-57bcb74d8d
Containers:
emqx:
Container ID:   docker://fb861131f9c84be7670a8613ee05f6490d0f6fd9279276eb1757172c51191324
Image:          emqx/emqx:5.3.2
Image ID:       docker-pullable://emqx/emqx@sha256:858305e7b0b33b28abbc29bb0063b193e9b127224ffc284a36584f910cf699d0
Port:           18083/TCP
Host Port:      0/TCP
State:          Running
Started:      Tue, 09 Jan 2024 12:42:13 +0100
Ready:          True
Restart Count:  0
Liveness:       http-get http://:dashboard/status delay=60s timeout=1s period=30s #success=1 #failure=3
Readiness:      http-get http://:dashboard/status delay=10s timeout=1s period=5s #success=1 #failure=12
Environment:
EMQX_DASHBOARD__LISTENERS__HTTP__BIND:                         18083
POD_NAME:                                                      test-emqx-core-57bcb74d8d-0 (v1:metadata.name)
EMQX_CLUSTER__DISCOVERY_STRATEGY:                              dns
EMQX_CLUSTER__DNS__RECORD_TYPE:                                srv
EMQX_CLUSTER__DNS__NAME:                                       test-emqx-headless.default.svc.cluster.local
EMQX_HOST:                                                     $(POD_NAME).$(EMQX_CLUSTER__DNS__NAME)
EMQX_NODE__DATA_DIR:                                           data
EMQX_NODE__ROLE:                                               core
EMQX_NODE__COOKIE:                                             <set to the key 'node_cookie' in secret 'test-emqx-node-cookie'>  Optional: false
EMQX_API_KEY__BOOTSTRAP_FILE:                                  "/opt/emqx/data/bootstrap_api_key"
EMQX_DASHBOARD__DEFAULT_USERNAME:                              test
EMQX_DASHBOARD__DEFAULT_PASSWORD:                              test
EMQX_LISTENERS__WS__DEFAULT__ENABLE:                           false
EMQX_LISTENERS__WSS__DEFAULT__ENABLE:                          false
EMQX_AUTHENTICATION__1__MECHANISM:                             password_based
EMQX_AUTHENTICATION__1__BACKEND:                               built_in_database
EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__NAME:         bcrypt
EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__SALT_ROUNDS:  12
EMQX_AUTHENTICATION__2__MECHANISM:                             jwt
EMQX_AUTHENTICATION__2__USE_JWKS:                              false
EMQX_AUTHENTICATION__2__ALGORITHM:                             hmac-based
EMQX_AUTHENTICATION__2__SECRET:                                test
EMQX_TELEMETRY__ENABLE:                                        false
EMQX_AUTHENTICATION__2__VERIFY_CLAIMS:                         {edge_node_id: "${username}"}
EMQX_CLUSTER__DISCOVERY_STRATEGY:                              dns
EMQX_CLUSTER__DNS__RECORD_TYPE:                                srv
EMQX_SYSMON__VM__LONG_SCHEDULE:                                disabled
EMQX_LISTENERS__TCP__DEFAULT__ENABLE:                          false
EMQX_LISTENERS__SSL__DEFAULT__ENABLE:                          false
EMQX_LISTENERS__TCP__MQTT__BIND:                               "<IP_ADDRESS>:1883"
Mounts:
/opt/emqx/data from test-emqx-core-data (rw)
/opt/emqx/data/bootstrap_api_key from bootstrap-api-key (ro,path="bootstrap_api_key")
/opt/emqx/etc/emqx.conf from bootstrap-config (ro,path="emqx.conf")
/opt/emqx/log from test-emqx-core-log (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-nbg86 (ro)
Readiness Gates:
Type                      Status
apps.emqx.io/on-serving   True
Conditions:
Type                      Status
apps.emqx.io/on-serving   True
Initialized               True
Ready                     True
ContainersReady           True
PodScheduled              True
Volumes:
test-emqx-core-data:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  test-emqx-core-data-test-emqx-core-57bcb74d8d-0
ReadOnly:   false
bootstrap-api-key:
Type:        Secret (a volume populated by a Secret)
SecretName:  test-emqx-bootstrap-api-key
Optional:    false
bootstrap-config:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      test-emqx-configs
Optional:  false
test-emqx-core-log:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
kube-api-access-nbg86:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
POD1:
kubectl describe pod test-emqx-core-57bcb74d8d-1
Name:         test-emqx-core-57bcb74d8d-1
Namespace:    default
Priority:     0
Node:         minikube/<IP_ADDRESS>
Start Time:   Tue, 09 Jan 2024 12:44:01 +0100
Labels:       apps.emqx.io/db-role=core
apps.emqx.io/instance=test-emqx
apps.emqx.io/managed-by=emqx-operator
apps.emqx.io/pod-template-hash=57bcb74d8d
controller-revision-hash=test-emqx-core-57bcb74d8d-86f944c4f
statefulset.kubernetes.io/pod-name=test-emqx-core-57bcb74d8d-1
Annotations:
Status:       Running
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  StatefulSet/test-emqx-core-57bcb74d8d
Containers:
emqx:
Container ID:   docker://eb10e152c397795ee95b4b4e8292b9ae3ee190561e6a5e2b166904790d125f34
Image:          emqx/emqx:5.3.2
Image ID:       docker-pullable://emqx/emqx@sha256:858305e7b0b33b28abbc29bb0063b193e9b127224ffc284a36584f910cf699d0
Port:           18083/TCP
Host Port:      0/TCP
State:          Running
Started:      Tue, 09 Jan 2024 12:44:02 +0100
Ready:          True
Restart Count:  0
Liveness:       http-get http://:dashboard/status delay=60s timeout=1s period=30s #success=1 #failure=3
Readiness:      http-get http://:dashboard/status delay=10s timeout=1s period=5s #success=1 #failure=12
Environment:
EMQX_DASHBOARD__LISTENERS__HTTP__BIND:                         18083
POD_NAME:                                                      test-emqx-core-57bcb74d8d-1 (v1:metadata.name)
EMQX_CLUSTER__DISCOVERY_STRATEGY:                              dns
EMQX_CLUSTER__DNS__RECORD_TYPE:                                srv
EMQX_CLUSTER__DNS__NAME:                                       test-emqx-headless.default.svc.cluster.local
EMQX_HOST:                                                     $(POD_NAME).$(EMQX_CLUSTER__DNS__NAME)
EMQX_NODE__DATA_DIR:                                           data
EMQX_NODE__ROLE:                                               core
EMQX_NODE__COOKIE:                                             <set to the key 'node_cookie' in secret 'test-emqx-node-cookie'>  Optional: false
EMQX_API_KEY__BOOTSTRAP_FILE:                                  "/opt/emqx/data/bootstrap_api_key"
EMQX_DASHBOARD__DEFAULT_USERNAME:                              test
EMQX_DASHBOARD__DEFAULT_PASSWORD:                              test
EMQX_LISTENERS__WS__DEFAULT__ENABLE:                           false
EMQX_LISTENERS__WSS__DEFAULT__ENABLE:                          false
EMQX_AUTHENTICATION__1__MECHANISM:                             password_based
EMQX_AUTHENTICATION__1__BACKEND:                               built_in_database
EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__NAME:         bcrypt
EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__SALT_ROUNDS:  12
EMQX_AUTHENTICATION__2__MECHANISM:                             jwt
EMQX_AUTHENTICATION__2__USE_JWKS:                              false
EMQX_AUTHENTICATION__2__ALGORITHM:                             hmac-based
EMQX_AUTHENTICATION__2__SECRET:                                test
EMQX_TELEMETRY__ENABLE:                                        false
EMQX_AUTHENTICATION__2__VERIFY_CLAIMS:                         {edge_node_id: "${username}"}
EMQX_CLUSTER__DISCOVERY_STRATEGY:                              dns
EMQX_CLUSTER__DNS__RECORD_TYPE:                                srv
EMQX_SYSMON__VM__LONG_SCHEDULE:                                disabled
EMQX_LISTENERS__TCP__DEFAULT__ENABLE:                          false
EMQX_LISTENERS__SSL__DEFAULT__ENABLE:                          false
EMQX_LISTENERS__TCP__MQTT__BIND:                               "<IP_ADDRESS>:1883"
Mounts:
/opt/emqx/data from test-emqx-core-data (rw)
/opt/emqx/data/bootstrap_api_key from bootstrap-api-key (ro,path="bootstrap_api_key")
/opt/emqx/etc/emqx.conf from bootstrap-config (ro,path="emqx.conf")
/opt/emqx/log from test-emqx-core-log (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hlgvr (ro)
Readiness Gates:
Type                      Status
apps.emqx.io/on-serving   False
Conditions:
Type                      Status
apps.emqx.io/on-serving   False
Initialized               True
Ready                     False
ContainersReady           True
PodScheduled              True
Volumes:
test-emqx-core-data:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  test-emqx-core-data-test-emqx-core-57bcb74d8d-1
ReadOnly:   false
bootstrap-api-key:
Type:        Secret (a volume populated by a Secret)
SecretName:  test-emqx-bootstrap-api-key
Optional:    false
bootstrap-config:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      test-emqx-configs
Optional:  false
test-emqx-core-log:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
kube-api-access-hlgvr:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:

OK, please share the EMQX operator log and the EMQX customer resource status. And you can use Markdown to format you context

Hi,
please find logs attached. It seems there was restart during the night so I can reproduce it once more and send logs.
Thank you,
Anže
emqx-1.log
emqx-0.log
emqx-operator-controller-manager.log

I found this message in EMQX operator log: etcdserver: request timed out, maybe that is the reason of why the EMQX operator is not work normal

Hi,
I reproduced it. Please find attached logs. That error you mention is probably not related to it (my pc went to sleep mode before that log...).
kubectl get statefulsets
NAME                        READY   AGE
test-emqx-core-57bcb74d8d   1/2     140m

operator-manager.log
emqx0.log
emqx1.log

Could you please enable debug log for EMQX operator, and retry it, and show the debug log of EMQX operator.
You can set development = true in Helm chart value to enable debug log.
And when this issue is happen, please show EMQX customer resource, you can running kubectl get emqx $name -o json

Hi,
thx for response. Please find attached logs (I do not see any new log inside operator after recreation of the pod).
kubectl get emqx $name -o json

{
    "apiVersion": "v1",
    "items": [
        {
            "apiVersion": "apps.emqx.io/v2beta1",
            "kind": "EMQX",
            "metadata": {
                "annotations": {
                    "apps.emqx.io/last-emqx-configuration": ""
                },
                "creationTimestamp": "2024-01-10T14:29:29Z",
                "generation": 2,
                "name": "test-emqx",
                "namespace": "default",
                "resourceVersion": "905163",
                "uid": "90bfdbd3-3450-48d9-b845-193e37e8ccfd"
            },
            "spec": {
                "clusterDomain": "cluster.local",
                "config": {
                    "mode": "Merge"
                },
                "coreTemplate": {
                    "metadata": {},
                    "spec": {
                        "containerSecurityContext": {
                            "runAsGroup": 1000,
                            "runAsNonRoot": true,
                            "runAsUser": 1000
                        },
                        "env": [
                            {
                                "name": "EMQX_DASHBOARD__DEFAULT_USERNAME",
                                "value": "test"
                            },
                            {
                                "name": "EMQX_DASHBOARD__DEFAULT_PASSWORD",
                                "value": "test"
                            },
                            {
                                "name": "EMQX_LISTENERS__WS__DEFAULT__ENABLE",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_LISTENERS__WSS__DEFAULT__ENABLE",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__1__MECHANISM",
                                "value": "password_based"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__1__BACKEND",
                                "value": "built_in_database"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__NAME",
                                "value": "bcrypt"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__1__PASSWORD_HASH_ALGORITHM__SALT_ROUNDS",
                                "value": "12"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__2__MECHANISM",
                                "value": "jwt"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__2__USE_JWKS",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__2__ALGORITHM",
                                "value": "hmac-based"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__2__SECRET",
                                "value": "test"
                            },
                            {
                                "name": "EMQX_TELEMETRY__ENABLE",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_AUTHENTICATION__2__VERIFY_CLAIMS",
                                "value": "{edge_node_id: \"${username}\"}"
                            },
                            {
                                "name": "EMQX_CLUSTER__DISCOVERY_STRATEGY",
                                "value": "dns"
                            },
                            {
                                "name": "EMQX_CLUSTER__DNS__RECORD_TYPE",
                                "value": "srv"
                            },
                            {
                                "name": "EMQX_SYSMON__VM__LONG_SCHEDULE",
                                "value": "disabled"
                            },
                            {
                                "name": "EMQX_LISTENERS__TCP__DEFAULT__ENABLE",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_LISTENERS__SSL__DEFAULT__ENABLE",
                                "value": "false"
                            },
                            {
                                "name": "EMQX_LISTENERS__TCP__MQTT__BIND",
                                "value": "\"<IP_ADDRESS>:1883\""
                            }
                        ],
                        "livenessProbe": {
                            "failureThreshold": 3,
                            "httpGet": {
                                "path": "/status",
                                "port": "dashboard"
                            },
                            "initialDelaySeconds": 60,
                            "periodSeconds": 30
                        },
                        "podSecurityContext": {
                            "fsGroup": 1000,
                            "fsGroupChangePolicy": "Always",
                            "runAsGroup": 1000,
                            "runAsUser": 1000,
                            "supplementalGroups": [
                                1000
                            ]
                        },
                        "readinessProbe": {
                            "failureThreshold": 12,
                            "httpGet": {
                                "path": "/status",
                                "port": "dashboard"
                            },
                            "initialDelaySeconds": 10,
                            "periodSeconds": 5
                        },
                        "replicas": 2,
                        "resources": {},
                        "volumeClaimTemplates": {
                            "accessModes": [
                                "ReadWriteOnce"
                            ],
                            "resources": {
                                "requests": {
                                    "storage": "20Mi"
                                }
                            }
                        }
                    }
                },
                "image": "emqx/emqx:5.3.2",
                "listenersServiceTemplate": {
                    "enabled": true,
                    "metadata": {
                        "annotations": {
                            "service.beta.kubernetes.io/azure-load-balancer-resource-group": "anze-test"
                        }
                    },
                    "spec": {
                        "loadBalancerIP": "<IP_ADDRESS>",
                        "ports": [
                            {
                                "name": "tcp-mqtt",
                                "port": 1883,
                                "protocol": "TCP",
                                "targetPort": 1883
                            }
                        ],
                        "type": "LoadBalancer"
                    }
                },
                "replicantTemplate": {
                    "metadata": {},
                    "spec": {
                        "containerSecurityContext": {
                            "runAsGroup": 1000,
                            "runAsNonRoot": true,
                            "runAsUser": 1000
                        },
                        "livenessProbe": {
                            "failureThreshold": 3,
                            "httpGet": {
                                "path": "/status",
                                "port": "dashboard"
                            },
                            "initialDelaySeconds": 60,
                            "periodSeconds": 30
                        },
                        "podSecurityContext": {
                            "fsGroup": 1000,
                            "fsGroupChangePolicy": "Always",
                            "runAsGroup": 1000,
                            "runAsUser": 1000,
                            "supplementalGroups": [
                                1000
                            ]
                        },
                        "readinessProbe": {
                            "failureThreshold": 12,
                            "httpGet": {
                                "path": "/status",
                                "port": "dashboard"
                            },
                            "initialDelaySeconds": 10,
                            "periodSeconds": 5
                        },
                        "replicas": 0,
                        "resources": {}
                    }
                },
                "revisionHistoryLimit": 3,
                "updateStrategy": {
                    "evacuationStrategy": {
                        "connEvictRate": 1000,
                        "sessEvictRate": 1000,
                        "waitTakeover": 10
                    },
                    "initialDelaySeconds": 10,
                    "type": "Recreate"
                }
            },
            "status": {
                "conditions": [
                    {
                        "lastTransitionTime": "2024-01-10T14:30:10Z",
                        "message": "Create new replicaSet",
                        "reason": "CreateNewReplicaSet",
                        "status": "True",
                        "type": "ReplicantNodesProgressing"
                    },
                    {
                        "lastTransitionTime": "2024-01-10T14:30:10Z",
                        "message": "Core nodes is ready",
                        "reason": "CoreNodesReady",
                        "status": "True",
                        "type": "CoreNodesReady"
                    },
                    {
                        "lastTransitionTime": "2024-01-10T14:29:31Z",
                        "message": "Create new statefulSet",
                        "reason": "CreateNewStatefulSet",
                        "status": "True",
                        "type": "CoreNodesProgressing"
                    }
                ],
                "coreNodes": [
                    {
                        "controllerUID": "c9dc9bf5-f46b-4cee-b563-a2a1f2b48c93",
                        "edition": "Opensource",
                        "node"<EMAIL_ADDRESS>                        "node_status": "running",
                        "otp_release": "25.3.2-2/13.2.2",
                        "podUID": "b4c79037-c5e7-4d0b-9110-6ad48d57e7ac",
                        "role": "core",
                        "uptime": 19904,
                        "version": "5.3.2"
                    },
                    {
                        "controllerUID": "c9dc9bf5-f46b-4cee-b563-a2a1f2b48c93",
                        "edition": "Opensource",
                        "node"<EMAIL_ADDRESS>                        "node_status": "running",
                        "otp_release": "25.3.2-2/13.2.2",
                        "podUID": "d3e3fb8e-1dc0-4cd8-a3b8-194cb0aeb1aa",
                        "role": "core",
                        "uptime": 19906,
                        "version": "5.3.2"
                    }
                ],
                "coreNodesStatus": {
                    "currentReplicas": 2,
                    "currentRevision": "57bcb74d8d",
                    "readyReplicas": 2,
                    "replicas": 2,
                    "updateReplicas": 2,
                    "updateRevision": "57bcb74d8d"
                },
                "replicantNodesStatus": {
                    "currentRevision": "5d7b4558d5",
                    "updateRevision": "5d7b4558d5"
                }
            }
        }
    ],
    "kind": "List",
    "metadata": {
        "resourceVersion": "",
        "selfLink": ""
    }
}

operator-controller-manager.log
emqx1-recreated.log
emqx0.log
Maybe this also helps:
kubectl get events -o custom-columns=TS:.firstTimestamp,Count:.count,From:.source.component,Type:.type,Reason:.reason,Message:.message --sort-by='.firstTimestamp'
TS                     Count   From                                                                                Type      Reason                    Message
2024-01-10T14:29:31Z   1       statefulset-controller                                                                         Normal    SuccessfulCreate          create Claim test-emqx-core-data-test-emqx-core-57bcb74d8d-0 Pod test-emqx-core-57bcb74d8d-0 in StatefulSet test-emqx-core-57bcb74d8d success
2024-01-10T14:29:31Z   1       persistentvolume-controller                                                                    Normal    ExternalProvisioning      waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
2024-01-10T14:29:31Z   1       k8s.io/minikube-hostpath_minikube_4072228a-9bbc-4220-a8cc-258ba512cb4d                         Normal    ProvisioningSucceeded     Successfully provisioned volume pvc-40fe2dda-287e-457d-82b1-99431d404065
2024-01-10T14:29:31Z   1       k8s.io/minikube-hostpath_minikube_4072228a-9bbc-4220-a8cc-258ba512cb4d                         Normal    Provisioning              External provisioner is provisioning volume for claim "default/test-emqx-core-data-test-emqx-core-57bcb74d8d-1"
2024-01-10T14:29:31Z   1       k8s.io/minikube-hostpath_minikube_4072228a-9bbc-4220-a8cc-258ba512cb4d                         Normal    ProvisioningSucceeded     Successfully provisioned volume pvc-dee67a1f-6536-4efa-9034-70bb1803fd04
2024-01-10T14:29:31Z   1       default-scheduler                                                                              Warning   FailedScheduling          0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
2024-01-10T14:29:31Z   1       k8s.io/minikube-hostpath_minikube_4072228a-9bbc-4220-a8cc-258ba512cb4d                         Normal    Provisioning              External provisioner is provisioning volume for claim "default/test-emqx-core-data-test-emqx-core-57bcb74d8d-0"
2024-01-10T14:29:31Z   2       persistentvolume-controller                                                                    Normal    ExternalProvisioning      waiting for a volume to be created, either by external provisioner "k8s.io/minikube-hostpath" or manually created by system administrator
2024-01-10T14:29:31Z   1       default-scheduler                                                                              Warning   FailedScheduling          0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
2024-01-10T14:29:31Z   1       statefulset-controller                                                                         Normal    SuccessfulCreate          create Claim test-emqx-core-data-test-emqx-core-57bcb74d8d-1 Pod test-emqx-core-57bcb74d8d-1 in StatefulSet test-emqx-core-57bcb74d8d success
2024-01-10T14:29:31Z   1       statefulset-controller                                                                         Normal    SuccessfulCreate          create Pod test-emqx-core-57bcb74d8d-0 in StatefulSet test-emqx-core-57bcb74d8d successful
2024-01-10T14:29:31Z   2       statefulset-controller                                                                         Normal    SuccessfulCreate          create Pod test-emqx-core-57bcb74d8d-1 in StatefulSet test-emqx-core-57bcb74d8d successful
2024-01-10T14:29:32Z   1       default-scheduler                                                                              Normal    Scheduled                 Successfully assigned default/test-emqx-core-57bcb74d8d-0 to minikube
2024-01-10T14:29:32Z   1       default-scheduler                                                                              Normal    Scheduled                 Successfully assigned default/test-emqx-core-57bcb74d8d-1 to minikube
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Started                   Started container emqx
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Pulled                    Container image "emqx/emqx:5.3.2" already present on machine
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Created                   Created container emqx
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Started                   Started container emqx
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Pulled                    Container image "emqx/emqx:5.3.2" already present on machine
2024-01-10T14:29:34Z   1       kubelet                                                                                Normal    Created                   Created container emqx
2024-01-10T14:29:35Z   25      emqx-controller                                                                                Warning   FailedToGetNodeStatuses   failed to get node statues by API: failed to get API http://<IP_ADDRESS>:18083/api/v5/nodes: failed to request API: Get "http://<IP_ADDRESS>:18083/api/v5/nodes": dial tcp <IP_ADDRESS>:18083: connect: connection refused
2024-01-10T14:29:44Z   4       kubelet                                                                                Warning   Unhealthy                 Readiness probe failed: Get "http://<IP_ADDRESS>:18083/status": dial tcp <IP_ADDRESS>:18083: connect: connection refused
2024-01-10T14:29:48Z   4       kubelet                                                                                Warning   Unhealthy                 Readiness probe failed: Get "http://<IP_ADDRESS>:18083/status": dial tcp <IP_ADDRESS>:18083: connect: connection refused
2024-01-10T14:30:04Z   1       kubelet                                                                                Warning   Unhealthy                 Readiness probe failed: Get "http://<IP_ADDRESS>:18083/status": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
2024-01-10T14:31:07Z   1       kubelet                                                                                Normal    Killing                   Stopping container emqx
2024-01-10T14:31:07Z   1       endpoint-controller                                                                            Warning   FailedToUpdateEndpoint    Failed to update endpoint default/test-emqx-dashboard: Operation cannot be fulfilled on endpoints "test-emqx-dashboard": the object has been modified; please apply your changes to the latest version and try again
2024-01-10T14:31:07Z   1       endpoint-controller                                                                            Warning   FailedToUpdateEndpoint    Failed to update endpoint default/test-emqx-listeners: Operation cannot be fulfilled on endpoints "test-emqx-listeners": the object has been modified; please apply your changes to the latest version and try again
2024-01-10T14:31:09Z   1       default-scheduler                                                                              Normal    Scheduled                 Successfully assigned default/test-emqx-core-57bcb74d8d-1 to minikube
2024-01-10T14:31:10Z   1       kubelet                                                                                Normal    Created                   Created container emqx
2024-01-10T14:31:10Z   1       kubelet                                                                                Normal    Pulled                    Container image "emqx/emqx:5.3.2" already present on machine
2024-01-10T14:31:10Z   1       kubelet                                                                                Normal    Started                   Started container emqx

OK, check the conditions and the replicantTemplate.replicas = 0 in EMQX, I think this issue is likes to https://github.com/emqx/emqx-operator/issues/1002, could you please deploy EMQX operator 2.2.12 and retry ?

Hi,
thank you very much @Rory-Z, it works now without problem in v2.2.12! I have only one more question... I noticed that from operator version > 2.2.5,  besides the enabled port all other default ports are visible/avaliable to listener (load balancer) service, although they are disabled and not specified?
kubectl describe service test-emqx-listeners
Name:                     test-emqx-listeners
Namespace:                default
Labels:                   apps.emqx.io/instance=test-emqx
                          apps.emqx.io/managed-by=emqx-operator
Annotations:              apps.emqx.io/last-applied:
                            UEsDBBQACAAIAAAAAAAAAAAAAAAAAAAAAAAIAAAAb3JpZ2luYWykVduO3DYM/Rc+W64vs41Hb70CBXqZttNFkUwfZJleCCtLjiRvshn43wv6MvY4k26RvMkkfXhIHkpnEK26R+eVNc...
                          service.beta.kubernetes.io/azure-load-balancer-resource-group: anze-test
Selector:                 apps.emqx.io/db-role=core,apps.emqx.io/instance=test-emqx,apps.emqx.io/managed-by=emqx-operator
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
IP:                       <IP_ADDRESS>
LoadBalancer Ingress:     <IP_ADDRESS>
Port:                     tcp-mqtt  1883/TCP
TargetPort:               1883/TCP
NodePort:                 tcp-mqtt  32623/TCP
Endpoints:                <IP_ADDRESS>:1883,<IP_ADDRESS>:1883
Port:                     ssl-default  8883/TCP
TargetPort:               8883/TCP
NodePort:                 ssl-default  30891/TCP
Endpoints:                <IP_ADDRESS>:8883,<IP_ADDRESS>:8883
Port:                     ws-default  8083/TCP
TargetPort:               8083/TCP
NodePort:                 ws-default  31260/TCP
Endpoints:                <IP_ADDRESS>:8083,<IP_ADDRESS>:8083
Port:                     wss-default  8084/TCP
TargetPort:               8084/TCP
NodePort:                 wss-default  31657/TCP
Endpoints:                <IP_ADDRESS>:8084,<IP_ADDRESS>:8084
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

Thx,
Anže.

besides the enabled port all other default ports are visible/avaliable to listener (load balancer) service, although they are disabled and not specified

Yes, because they are default enable in EMQX, if you want disable it, you can set listeners.tcp.default.bind = 0 in .spec.config.data

Thx. I have it disabled in coreTemplate.spec.env (you can see it in one of previous post). Should I move this spec to.spec.config.data then?

Thx. I have it disabled in coreTemplate.spec.env (you can see it in one of previous post). Should I move this spec to.spec.config.data then?

Yes, the .spec.config.data is better

Ok thx. It was confusing because also log from emqx says:
Listener ssl:default is NOT started due to: disabled.
Listener tcp:default is NOT started due to: disabled.
Listener tcp:mqtt on <IP_ADDRESS>:1883 started.
Listener ws:default is NOT started due to: disabled.
Listener wss:default is NOT started due to: disabled.
Listener http:dashboard on :18083 started.

EMQX operator load the EMQX config in .spec.config.data, and watch this config. When the EMQX operator find the some listeners is disabled, they will disable that port in service, but EMQX operator can not load EMQX config  in pod env.
I recommend you to use .spec.config.data more, if you want update EMQX config, just change .spec.config.data is right. If you use the env in pod, you only can restart pod to update EMQX config


ask_result stores no value

Even when I run the simplest code:
ask Package ID:
echo 'ask_result'
In the cmd menu 'ask_result' gets returned. No matter what I type in the google prompt box.

Hi @RidaShahidMalik, variables are accessed using backticks, not quotes. Please try the following
echo `ask_result`


Text, images, code for inheritance tutorial

Text, images, code for inheritance tutorial
Summary
A tutorial on inheritance that addresses basic concepts, implicit inheritance, inheritance for code reuse, and abstract base classes.
Fixes #265
Suggested Reviewers
@BillWagner @mairaw @stevehoag

@BillWagner Thanks for all of the comments and reviewing the code so carefully. I've made all of your suggested changes, as well as added interpolated strings, so I think that the code is much more "modern".

@rpetrusha I read this again this morning. It looks great.
There's one typo left, and one paragraph that still states that private and internal methods aren't inherited. Once those two are fixed, LGTM.


got error when compiling

Pathoschild.Stardew.ModBuildConfig.targets(73,5): error : The mod build package can't find your game folder. You can specify where to find it; see https://smapi.io/package/custom-game-path.
1>Done building project "StardewGPT.csproj" -- FAILED.

Have you already tried setting a custom game path like the link suggests?


Show more info on VS extension activation failure.

See https://github.com/microsoft/cadl/issues/358#issuecomment-1078476294
We should dump the stack trace of the exception and ask the user to file a bug on this repo, just like we do for internal compiler errors.

@milopezc I'm having trouble getting this to work. I return a context with failure message, but nothing happens when I click on the generic message. I don't know how to find the message I returned. Also, I do still see a yellow bar with link to the very verbose activity log afterwards in VS 2022.

Ah, so if I click on the exclamation mark bottom left afterwards, then I can click through and get the details in the output window, but not if I click on the original bubble, it seems.

Ah, so if I click on the exclamation mark bottom left afterwards, then I can click through and get the details in the output window, but not if I click on the original bubble, it seems.

Correct, sorry for not clarifying before.

@milopezc Thanks for confirming. Consider it small feedback that it would be nice if you could click on the original bubble too. I suspect the current way things are will lead to confusing conversations while trying to get that FailureMessage when users hit problems.


[Request] Formatting text on a per word/per character basis [$100]

I don't know how feasible this is, but it would be great to be able to format parts of a text, e.g. coloring specific words.
For one-liners, it's feasible by adding a text in color A, adding another one in color B at an x offset based on the width of the first one, and then yet another text at an x offset based on the previous two texts again in color A. But it's really cumbersome. And in long text where the target word could be anywhere, it becomes really impractical.
In terms of API, maybe it could take the form of a setFormattedText() method, corresponding to the usual setText() but which instead would accept format markers in the text, like BBcode or something. E.g. myText.setFormattedText("Lorem [color=#ff00aa]ipsum[/color] dolor sit amet");.
(Not sure of a more practical way to target specific words/characters.)
And if it would have too much impact on the other methods and complicate too much the overall API  of the text objects, then maybe a new FormattedText game object, that may be less flexible and offer less possibilities in exchange for that particular one?

There is a $100 open bounty on this issue. Add to the bounty at Bountysource.

This feels related to #3428 which was requesting the colored text support be added back in again.
If we added it, it would work like BitmapText, where you have a Static one and a Dynamic one which has extra features like this. The bigger problem is I just can't think of a clean way to provide this. It's literally not possible in the Canvas API, which makes it a complete hack however you approach it. For colors it's a bit easier, but for things like bold text it's a complete nightmare!

Maybe make a TextObject that supports HTML and just render the HTML itself?

Yeah we could have an HTMLElement object, but then you lose the ability to layer these within your scene - you could never have a sprite above it for example. They won't respond to cameras, scrolling, etc without some serious DOM-fu going on. Might be worth exploring anyway though. It feels like colored text could maybe be handled by the current Text object though, then we get to retain all the features of a real Game Object.

https://www.w3schools.com/tags/canvas_font.asp
Wouldn't the above be applicable in this situation?  At least for basic support - aka paragraph formatting.
Perhaps we could add a class that encapsulates multiple text objects like a wrapper.  Almost like a zone for text.  Then you add an array of text objects as children that each have their own formatting, the wrapper would simply control the positioning/word wrapping of the objects.

`const textZone = new Phaser.GameObjects.TextZone([
{
text: "Lorem ipsum",
fontFace: "Arial",
fontSize: "12px",
fontWeight: "bold"
},
{
text: " dummy text",
fontFace: "Arial",
fontSize: "14px",
fontWeight: "normal"
}
]);
textZone.maxWidth = 150;`
Something syntactically like the above example.

😘

If it could be WebGL only, perhaps a signed distance field approach could work well. Colors, outlines, scaling, all basically free and easy.

I'm willing to throw an extra 100$ on top of the 50$ from last week if we can make each character in a colored text behave as an independent game object (aka, destroy random letters, or maybe just hide them and make them non-collideable).
If this is technically possible, of course.

That all would be possible with the example wrapper I provided above. But
it is a relatively large component. It would ultimately be up to Rich as to
whether it’s worth implementing directly into Phaser or just implementing
as an external plug-in.(which I feel is probably the best)
On Mon, Apr 23, 2018 at 7:34 AM Alexander Nestorov<EMAIL_ADDRESS>wrote:

I'm willing to throw an extra 100$ on top of the 50$ from last week if we
can make each character in a colored text behave as an independent game
object (aka, destroy random letters, or maybe just hide them and make them
non-collideable).
If this is technically possible, of course.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/photonstorm/phaser/issues/3390#issuecomment-383544325,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJeqInSN6vKcfMK4Io2w4wr2CywrV5qkks5trbxDgaJpZM4SqfD9
.

--
My regards,
Travis Oneal

@photonstorm What do you think about the proposed API design from @wtravO ?
Also, should that live inside the core or just as a plugin?

I think it needs adding as a Dynamic Text object. Like we have Dynamic and Static BitmapText, the current Text is 'static', but we could add a Dynamic variant which offered features like this without impacting the speed of the original.

Here is an unofficial solution.

@photonstorm what do you think about @rexrainbow 's solution? Can it get merged in master (and let him get the bounty)?

It needs to be a PR against the main repo to be able to be merged (and therefore claim the bounty) - although as I mentioned above, it will need to be a new game object, as I'm not willing to merge this into Static Text (it will need to be Dynamic Text)

@alexandernst
I prefer not merging my bbcode text object into official phaser 3 codebase, because that my coding style is incompatible with phaser 3.
My bbcode text object could be installed by plugin system of phaser 3. BTW, I had made text typing, text paging behavior for official text object, or my bbcode text object. Feel free to grab them,

I'll keep this open and move Dynamic Text up the list, to be started once the Scale Manager is in.

@photonstorm I recall reading about Scale Manager being worked on (completed?) in the last 2 weekly dev logs. Did it get implemented? Are there any docs about how to use scale manager?
Also, if scale manager is ready, does it mean that you'll be working on this?

I added an extra 50$ for this one, but for some reason BountySource is not reflecting the change 🤔

Yeah it's changed on the BountySource site, just not here, so I edited the issue.

@photonstorm Hi! Any news on this? :)

@photonstorm I added an extra 50$ to the bounty. Could you update the title of the issue, please? :pray:

@photonstorm ping?

I lost interest in this issue and I withdrawed the bounty. @photonstorm can you reflect that in the title/tags, please?

Done. BountySource is honestly more of a pain than a benefit!

Closing this as it's not going to be a feature in v3 and if you need it, you can use the BBCode Text plugin: https://rexrainbow.github.io/phaser3-rex-notes/docs/site/bbcodetext/


DRILL-5919:  Add non-numeric support for JSON processing

Added two session options store.json.reader.non_numeric_numbers and store.json.reader.non_numeric_numbers that allow to read/write NaN and Infinity as numbers. By default these options are set to false.
Extended signature of convert_toJSON and convert_fromJSON functions by adding second optional parameter  that enables read/write NaN and Infinity.. For example:
select convert_fromJSON('{"key": NaN}') from (values(1)); will result with JsonParseException, but
select convert_fromJSON('{"key": NaN}', true) from (values(1)); will parse NaN as a number.

@arina-ielchiieva made code changes according to your comments.

Thanks, +1, LGTM.

Further, is the extra option to convertFromJSON really needed? Can't we just accept NaN and Infinity by default?
Consider. If the option is off by default, users without NaN or Infinity data will see no difference. But, users will this data will get an error and have to hunt down the option to make their data work.
If the option is on by default, users without NaN or Infinity data will see no difference. But, users will this data will also have their queries work by default.
So, seems no harm in making the NaN and Infinity support turned on by default.

what do you think about having two functions instead: convertFromJSON and convertFromJSON+some suffix. Second will be able to convert  NaN, Infinity

On the two functions... Maybe just have one function that handles the Nan/Infinity case. As noted earlier, no matter what we do, JSON without these symbols will work. So, we need only consider JSON with the symbols. Either:

The NaN/Infinity cases always work, or
The NaN/Infinity cases work sometimes, fail others, depending on some option or argument.

I would vote for the first case: it is simpler. I just can't see how anyone would use Drill to valid JSON and would want a query to fail if it contains NaN or Infinity. Can you suggest a case where failing the query would be of help to the user?

@paul-rogers Made changes, please review.

@vladimirtkach thanks for adding tests for math functions. New changes look good to me.
@paul-rogers please take a look.


[RFC] PHP should be compiled with ZTS or not ?

Hi,
I'm opening this RFC hoping to gather comments from the Apache and PHP maintainers.
We know that there are two ways to compile the PHP interpreter (yeah there are many others but in this thread, only those flags are relevant):

NTS: Non-Thread Safe
ZTS: Zend-Thread Safe

Me, as a PHP developer, I remember these rules:

When PHP is meant to be used with mod_php in Apache -> it's better to use ZTS
When PHP is meant to used with CGI/FASTCGI/Nginx/CommandLine -> It's better NTS

The default PHP in Nixos is built with ZTS and I think it should be NTS. NTS is also the default in many other distributions.
What's your point of view about that?
Relevant links:

https://externals.io/message/65332
https://github.com/oerdnj/deb.sury.org/issues/1419
https://github.com/fossar/nix-phps/issues/63

CC:

Apache maintainers: @lovek323
PHP maintainers: @aanderse @etu @globin @ma27 @talyz

Even if we change this line to false:
https://github.com/NixOS/nixpkgs/blob/b2737d4980a17cc2b7d600d7d0b32fd7333aca88/pkgs/development/interpreters/php/generic.nix#L53
PHP will still be built with ZTS due to
https://github.com/php/php-src/blob/5b01c4863fe9e4bc2702b2bbf66d292d23001a18/sapi/apache2handler/config.m4#L119
$ nix shell -f . apacheHttpd.dev -c sh -c '$(apxs -q SBINDIR)/$(apxs -q TARGET) -V' | grep threaded
  threaded:     yes (fixed thread count)

Yeah, I guess the question is if we should disable apxs2 by default and maybe provide a separate package with it enabled.

Yeah, I guess the question is if we should disable apxs2 by default and maybe provide a separate package with it enabled.

Could be an idea yeah !

Do you have something to say here @lovek323 ?

Like you say, it would be great to be able to have the CLI php binary using NTS by default, if apxs is the only thing that's blocking this, a separate package for that sounds good to me.

@lovek323 Thanks for your input !
@jtojnar how about making 2 packages:

php: This would be the default PHP package, without apxs2support and NTS
php-apache:  This would be the PHP package, with apxs2support and ZTS

WDYT?

I'll mention that it is 2022 and people really shouldn't be using mod_php anymore... we have php-fpm which is almost always a better solution. @drupol I think your proposed solution is reasonable :+1:
https://cwiki.apache.org/confluence/display/httpd/PHP

I'll mention that it is 2022 and people really shouldn't be using mod_php anymore... we have php-fpm which is almost always a better solution. @drupol I think your proposed solution is reasonable :+1:
https://cwiki.apache.org/confluence/display/httpd/PHP

I definitely agree and this is why I opened this rfc.

Well, the changes is merged now :slightly_smiling_face: :tada:

Excellent :)


Add a changelog

It would be nice to have a changelog describing changes in each version.

Some changes can be found at https://github.com/composer/installers/releases


Some functions not rendered in docs

Given these two functions in the .bas file:

Only the Private function is in the documentation:

Looks like we try to though:
https://github.com/AutoActuary/mkdocstrings-vba/blob/2709106aee2b80371a7bbf5c48f18adc648cf7f8/mkdocstrings_handlers/vba/util.py#L139

Nothing to do with Private / Public, I'm working on MWE now

Okay, so this doesn't render:
Function dictget(d As Dictionary, key As Variant, Optional default As Variant = Empty)

End Function

But this does:
Function dictget(d As Dictionary, key As Variant)

End Function

' Variant tests:
Function Test1(d As Dictionary, key As Variant, Optional default As Variant = Empty)
    ' This doesn't render
End Function

Function Test2(d As Dictionary, key As Variant, Optional default As Variant)
    ' This renders
End Function

Function Test3(d As Dictionary, key As Variant, Optional default)
    ' This renders
End Function

' Integer tests:
Function Test4(d As Dictionary, key As Variant, Optional default As Integer = 0)
    ' This doesn't render
End Function

Function Test5(d As Dictionary, key As Variant, Optional default As Integer)
    ' This renders
End Function

Function Test6(d As Dictionary, key As Variant, Optional default)
    ' This renders
End Function

It looks like any optional argument with a default value doesn't render

Another one that doesn't render:
Public Function dict(ParamArray Args() As Variant) As Dictionary

End Function

Sorry, I just made a single commit that closes the issue, rather than a PR, since this module is still so experimental


scheduler.schedule is not a function

Bug Report
Current Behavior
Some RXjs code of mine is throwing an internal error of some kind.
scheduleArray.js:8 Uncaught TypeError: scheduler.schedule is not a function
    at Observable._subscribe (scheduleArray.js:8)
    at Observable._trySubscribe (Observable.js:43)
    at Observable.subscribe (Observable.js:29)
    at subscribeToResult (subscribeToResult.js:13)
    at MergeMapSubscriber._innerSub (mergeMap.js:74)
    at MergeMapSubscriber._tryNext (mergeMap.js:68)
    at MergeMapSubscriber._next (mergeMap.js:51)
    at MergeMapSubscriber.Subscriber.next (Subscriber.js:53)
    at MergeMapSubscriber.notifyNext (mergeMap.js:84)
    at InnerSubscriber._next (InnerSubscriber.js:15)

Putting a break point in reveals that the value of 'scheduler' is a numeric 1.
I'll admit that the code is a little on the complicated side with some streams essentially even forming a loop.
There is basically alot of rxjs code, but it is probably worth mentioning that nowhere am I making use of schedulers.
I have also been on the look out for anywhere where I might be passing in the wrong number of arguments to rxjs functions, but have not found anything yet.
Reproduction

Dont know how to reproduce it yet, still trying to figure out that myself.  It's a large and private codebase.  When I start breaking things and shifting things around a bit, the error seems to occur at different times/locations, making it hard to pin point what's causing it.

Environment

Runtime: Chrome v79.0.3945.88
RxJS version: 6

Dont know how to reproduce it yet.

Not much can be done without a repro.


feat: support encrypted ID tokens and Userinfo responses

Please go the the Preview tab and select the appropriate sub-template:

🐞 Bug Fix
⚙ Improvement
🎉 New Feature

Pull Request Test Coverage Report for Build 43

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 93.081%

Totals

Change from base Build 9:
-0.4%

Covered Lines:
982

Relevant Lines:
1055

💛  - Coveralls


Benchmark regression in complex_layout_scroll_perf_ios__timeline_summary

There was a worst frame rasterizer time regression in the complex layout benchmark on iOS (Impeller).
https://flutter-flutter-perf.skia.org/e/?keys=Xb32df78351d0d4eca428a1f6cf024fde&selected=commit%3D40502%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DiPhone_11%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Dworst_frame_rasterizer_time_millis%252Ctest%253Dcomplex_layout_scroll_perf_ios__timeline_summary%252C&xbaroffset=40502

The reason this regressed is that I removed the additional shader bootstrap. While we weren't actually using those shaders, as a side effect we no longer block until shaders are fully available in context creation, meaning that on the first frame we have to wait.

The reason this regressed is that I removed the additional shader bootstrap. While we weren't actually using those shaders, as a side effect we no longer block until shaders are fully available in context creation, meaning that on the first frame we have to wait.

If I'm reading this correctly, the reason it is impacting these benchmarks is that (?):
We used to not even start rasterizing frames until the shaders were loaded and the first frame had no waits between its begin/end because it didn't even try to start its work until everything was ready?
And now since it is asynchronous we might start that first frame earlier, but we can't finish it until the shaders are ready - time that used to be ignored as part of "app startup" but now appears in the first frame time?
This was the only benchmark impacted, though, so I'm curious why some of the more simple benchmarks didn't have a regression like that...

Actually I'm wrong, this is caused by the changes I made to image decoding. Maybe we've got a mutex somewhere that we're contesting? Or there is something in the metal driver that is contested now:


2024-02-23T00:15/01:15+09:00 [Webinar] UN Mappers - The Croundsourcing Community

I received the following invitation from UN Open GIS Initiative secretariat (Timur). Please join if you can!
Please assign yourself to this issue if you are interested and/or joining.

Geographic Information Systems
Politecnico di Milano, 2023-2024
Prof. Maria Antonia Brovelli
WEBINAR UN Mappers – The Crowdsourcing Community
22 February, 2024, 16:15 – 17:15
Politecnico di Milano – room 7.1.2 and
https://politecnicomilano.webex.com/meet/maria.brovelli
UN Maps is a mapping initiative that aims to assist UN peacekeeping missions in their field endeavors,
such as peace and security, navigation and logistics, by providing its peacekeepers with topographic
maps that will help them in their tactical and operational activities.
UN Mappers is a community of passionate digital volunteers supporting UN field operations by editing
OpenStreetMap or providing open geospatial data. The community is composed of more than 4000
contributors including UN personnel on the field (GIS and Information Management working groups
and uniformed personnel), academia (high schools and universities), local communities and remote
volunteers from all over the world. UN Mappers have been giving support to crises such as the
earthquake in Türkiye and Syria, development projects such as educational planning in Madagascar and
innovative applications such as Virtual Reality. Everybody can be a UN Mapper, and you can stay
updated on the community activities by following UN Mappers' social media or visiting
https://mappers.un.org
Speaker: Dr. Michael Montani – United Nations Global Service Center (UNGSC)
Michael Montani is a GIS Consultant at the United Nations Global
Service Center (UNGSC) and coordinator of the crowdsourcing activities
for UN Maps. Formerly he has been YouthMappers Research Fellow
and co-founder of the first European chapter of the network,
PoliMappers. Over the years, he trained hundreds of contributors
including UN personnel, academia and local communities worldwide
on Volunteered Geographic Information and open-source GIS. He holds
an MS in Geoinformatics Engineering at Politecnico di Milano
Webinar_Michael_Montani.pdf

参加できました！良い概論だったと思います。


fix(webClientServer): include basePath in createRequestUrl

Description
This patches the webClientServer to ensure the updateUrl is relative to the root.
This ensures the correct URL in case code-server is being served behind a
reverse proxy.
An example of this would be using Caddy to server code-server on
localhost:8082/code/
This fix ensures request urls are created against localhost:8082/code/ instead
of localhost:8082/
Screenshot
Notice the Request URL in the image. Serving code-server regularly (i.e. on 8080), the update/check is made against the root.

When serving code-server behind a reverse-proxy with Caddy, the update/check is made against the reverse-proxy root (i.e. /code/

Testing Plan
I tested against the root and the reverse-proxy.

cd vscode && git checkout jsjoeio-fix-csp-reverse-proxy
yarn link
cd code-server && yarn link code-oss-dev --modules-folder vendor/modules
create Caddyfile somewhere:

http://localhost:8082/code/* {
  uri strip_prefix /code
  reverse_proxy <IP_ADDRESS>:8080
}

caddy run
Navigate to http://localhost:8082/code/ in the browser and check Network tab. Filter for "check" and look at the Headers tab for the request.

I also did some basic testing around new URL in Codesandbox here.
This PR fixes https://github.com/cdr/code-server/issues/4476
(There is a chance this fixes other reverse proxy issues, but I will test after this is merged).

I was given some feedback on Slack.
Look at http in code-server and add a new method that does this instead. We should be able to achieve this change with relative urls.
We can't rely on referrer since that isn't guaranteed (see here).

@TeffenEllis since Asher is out today and next week, do you mind reviewing? It's very minimal


[Pulsar Scheduler] Load errors in chunks

Change the pulsar scheduler so that we load errors in chunks.  This means that we don;t try and load an unbounded number of errors from the db in a single query.

Codecov Report
Base: 46.53% // Head: 46.53% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (0d457b6) compared to base (ff35e73).
Patch coverage: 75.67% of modified lines in pull request are covered.

:exclamation: Current head 0d457b6 differs from pull request most recent head d8ed2fe. Consider uploading reports for the commit d8ed2fe to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2189      +/-   ##
==========================================
- Coverage   46.53%   46.53%   -0.01%
==========================================
  Files         223      223
  Lines       33077    33102      +25
==========================================
+ Hits        15394    15405      +11
- Misses      16446    16461      +15
+ Partials     1237     1236       -1

Flag
Coverage Δ

armada-server
46.53% <75.67%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/scheduler/database/job_repository.go
80.00% <75.67%> (-0.59%)
:arrow_down:

internal/scheduler/database/query.sql.go
28.82% <0.00%> (-2.41%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Helper modes for trying to profile noise and pointclouds

Is your frame expense, and you have a hunch it might be because you are using so much noise()? How can you figure that out?
This patch provides two new helper modes for ShadingSystem:

When the "profile" attribute is set to nonzero, it counts the number of noise calls and reports the total in the stats.

When the "no_noise" attribute is set to nonzero, all noise calls will be replaced with an inexpensive function that just returns 0 (for signed noise varieties) or 0.5 (for unsigned noises). You can then time your render in this mode versus with the regular noise calls, and the different should give you an estimate of how much time was spent doing noise math.

Updated, I decided I liked the attribute name "no_noise" better than my original choice of "nullnoise".

Updated again, added "no_pointcloud" attribute that shortcuts the pointcloud search functions, for various debug and profile purposes.

LGTM


Language chooser spike

converters are different, but can we add that in? e.g., https://www.pulumi.com/arm2pulumi/
how-to guides don't  have the update
can we copy over API docs for at least aws?


Login Failed

[ ] I've read the Readme - FAQ and Readme - Troubleshooting section.

Describe the bug
Login failed. code=1106, msg=permission deny
[12/19/2022, 8:50:43 AM] [@0x5e/homebridge-tuya-platform] Please make sure your countryCode, username, password, appSchema is correct, and app account is linked with cloud project.
Following debug area that isnt correct.
body = {
"country_code": 1,
"username"<EMAIL_ADDRESS>"password": "Not my password", is this area salted?
"schema": "tuyaSmart"
Expected behavior
Login
Screenshots
If applicable, add screenshots to help explain your problem.
Device info
If the issue is related to a device, please provide the device info list and debug logs.

Yes the password is salted. If you confirm you information is correct, please submit a ticket on https://service.console.tuya.com/

Di you submit a ticket on this? Mine is doing the exact same thing.

the API error don't have any useful information, and wrong countryCode/username/password/appSchema maybe is just one of the failure reason. I think submit the ticket by everyone is the best solution.

Support had me change the password. I had to do it twice. Had to limit the complexity and length for it to work.

Same problem on my side.
I've checked dozen of times all informations.
I use "smartlife" as appSchema because it's a smart Life app login and devices.
My user is linked to my devices with full permissions (Tuy App Account).
The country code is the right one...
No any other information in DEBUG mode.
I think there is a pb on Tuya Platform.
I've created a ticket on tuya pt.
Keep in touch

i'm getting this same error message as well
i'm not totally clear on what username and password i should be providing in the config
i've tried:

app username/password
tuya iot username/password
username/password for a user i created in the cloud project

none of them worked

i'm getting this same error message as well
i'm not totally clear on what username and password i should be providing in the config
i've tried:

app username/password

tuya iot username/password

username/password for a user i created in the cloud project

none of them worked

it's app username. if not working, need to submit a ticket let the staff to process.

The support team has just replied to test the same password with smartlife app.
Anyway this is working...
I have just a doubt about the password encryption :  "password is MD5 encrypted 32-bit lowercase letters"
So i'm trying to reproduce the login API call with postman.
The sign field is so tricky !! (multiple concat of strings)
Do you have some out of the box js function to generate it ?
Thanks!

@floperrot44 you can use https://iot.tuya.com/cloud/explorer to debug api, no need to calculate sign by your self.
Someone just update to a simple password then it's working, I'm not sure if update password works, or update a simple password works. Can you have a try?


The “go to definition” link will be abnormal when the id is with "-"

VSCode Version: 1.8.1
OS Version: Windows 10 1607

Steps to Reproduce:
1.Create a .ts file, define "vue-router" and input import * as Router from "vue-router";.
2.Move the mouse onto the "vue-router" as you press the "Ctrl".
The “go to definition” link will be abnormal, only "vue" or "router" turn blue.

Also it's abnormal when the id is with ""

When I click the blue link "vuex", the "./vuex/store" will be opened but not "vuex".

@longque Do you have any extensions installed? I don't think our builtin functionality provides links for TypeScript imports.

@mjbvz I don't think it's a problem caused by my extensions.
4 extensions installed

C/C++
C#
Python
Python for VSCode

It also appears in a .js file.

"vue-router" is defined in a .d.ts file.

@longque Thanks,  I'm able to repo this now.
After investigating, this looks like a duplicate of #10037. We need a new API on the VSCode side to define the range of a definition in the source document


Support empty string attributes

As per https://aws.amazon.com/about-aws/whats-new/2020/05/amazon-dynamodb-now-supports-empty-values-for-non-key-string-and-binary-attributes-in-dynamodb-tables/
Empty string attributes have been supported since May 18 2020. Right now they are serialised to NULL as per https://github.com/scanamo/scanamo/pull/367.
This should be a pretty easy fix, happy to open a PR to help.

Hi @danielchen2
Thanks for opening this issue. A PR would be really appreciated.

Thanks @danielchen2


Add extra logging for discovery checks in system test and output docker logs to file on failure.

Create pull request to trigger ci

Close as this is somewhat outdated.