[BUG] Tasks are not completed or canceled

Sometimes after a network problem on a part of the cluster, many tasks remain in the “_cat/tasks”.
Tasks remain hanging until nodes are reloaded.
New data is written to the indexes, no index lock occurs, the cluster state is green
I can’t specifically reproduce the problem, but now I have a live example on a running cluster.
GET _cat/tasks?v&h=action,type,running_time,node,task_id,parent_task_id&s=running_time:desc

GET /_tasks/G9gVoTdtT8Ons3Fxpisnog:98174152

{
  "completed": false,
  "task": {
    "node": "G9gVoTdtT8Ons3Fxpisnog",
    "id": 98174152,
    "type": "transport",
    "action": "indices:data/write/bulk[s]",
    "status": {
      "phase": "waiting_on_primary"
    },
    "description": "requests[1], index[security-auditlog-2023.07.23][0], refresh[IMMEDIATE]",
    "start_time_in_millis":<PHONE_NUMBER>962,
    "running_time_in_nanos":<PHONE_NUMBER>813227,
    "cancellable": false,
    "cancelled": false,
    "parent_task_id": "u9p6P23kTLqIaLls5j5GJQ:1554631381",
    "headers": {},
    "resource_stats": {
      "total": {
        "cpu_time_in_nanos": 0,
        "memory_in_bytes": 0
      }
    }
  }
}

GET /_tasks/u9p6P23kTLqIaLls5j5GJQ:1554631381

{
  "error": {
    "root_cause": [
      {
        "type": "resource_not_found_exception",
        "reason": "task [u9p6P23kTLqIaLls5j5GJQ:1554631381] isn't running and hasn't stored its results"
      }
    ],
    "type": "resource_not_found_exception",
    "reason": "task [u9p6P23kTLqIaLls5j5GJQ:1554631381] isn't running and hasn't stored its results"
  },
  "status": 404
}

I guess the problem is the missing parent task
Expected behavior
It was expected that child tasks would be executed or automatically canceled due to the missing of the parent task.
Well, or that in the absence of a parent task, it was possible to cancel tasks manually. This is currently not possible ("cancellable": false)
OpenSearch version - 2.7.0
OS - CentOS Stream release 8 [4.18.0-383.el8.x86_64]
Additional context
forum discussion

A task running for 15 days (?) is definitely a bug.

@dblock, If I understand correctly, then the task is waiting for a primary ("status":{ "phase": "waiting_on_primary"}), which does not exist.
The task will be running until I restart the service on the node
Нeap dump has a size of 3 GB, I do not have enough knowledge to understand what to look for in it :(

Although, not always parental tasks are missing.
For example, this chain:

GET /_tasks/G9gVoTdtT8Ons3Fxpisnog:98174510

{
  "completed": false,
  "task": {
    "node": "G9gVoTdtT8Ons3Fxpisnog",
    "id": 98174510,
    "type": "transport",
    "action": "indices:data/write/index",
    "status": {
      "phase": "starting"
    },
    "description": """index {[security-auditlog-2023.07.23][null], source[{"audit_trace_task_parent_id":"EWrZAyRuTnOktuuDhDtyOw:572254432","audit_cluster_name":"***","audit_transport_headers":{"_opendistro_security_initial_action_class_header":"Request","_opendistro_security_origin_header":"LOCAL","_opendistro_security_remotecn":"***"},"audit_node_name":"***-mst01","audit_trace_task_id":"G9gVoTdtT8Ons3Fxpisnog:98174487","audit_transport_request_type":"ConcreteReplicaRequest","audit_category":"MISSING_PRIVILEGES","audit_request_origin":"LOCAL","audit_node_id":"G9gVoTdtT8Ons3Fxpisnog","audit_request_layer":"TRANSPORT","@timestamp":"2023-07-23T11:19:14.644+00:00","audit_format_version":4,"audit_request_privilege":"indices:admin/seq_no/retention_lease_background_sync[r]","audit_node_host_address":"***","audit_node_host_name":"***"}]}""",
    "start_time_in_millis":<PHONE_NUMBER>693,
    "running_time_in_nanos":<PHONE_NUMBER>540595,
    "cancellable": false,
    "cancelled": false,
    "headers": {},
    "resource_stats": {
      "total": {
        "cpu_time_in_nanos": 0,
        "memory_in_bytes": 0
      }
    }
  }
}

GET /_tasks/G9gVoTdtT8Ons3Fxpisnog:98174511

{
  "completed": false,
  "task": {
    "node": "G9gVoTdtT8Ons3Fxpisnog",
    "id": 98174511,
    "type": "transport",
    "action": "indices:data/write/bulk[s]",
    "status": {
      "phase": "waiting_on_primary"
    },
    "description": "requests[1], index[security-auditlog-2023.07.23][0], refresh[IMMEDIATE]",
    "start_time_in_millis":<PHONE_NUMBER>693,
    "running_time_in_nanos":<PHONE_NUMBER>288518,
    "cancellable": false,
    "cancelled": false,
    "parent_task_id": "G9gVoTdtT8Ons3Fxpisnog:98174510",
    "headers": {},
    "resource_stats": {
      "total": {
        "cpu_time_in_nanos": 0,
        "memory_in_bytes": 0
      }
    }
  }
}

GET /_tasks/G9gVoTdtT8Ons3Fxpisnog:98174512

{
  "completed": false,
  "task": {
    "node": "G9gVoTdtT8Ons3Fxpisnog",
    "id": 98174512,
    "type": "direct",
    "action": "indices:data/write/bulk[s][p]",
    "status": {
      "phase": "primary"
    },
    "description": "requests[1], index[security-auditlog-2023.07.23][0], refresh[IMMEDIATE]",
    "start_time_in_millis":<PHONE_NUMBER>693,
    "running_time_in_nanos":<PHONE_NUMBER>567003,
    "cancellable": false,
    "cancelled": false,
    "parent_task_id": "G9gVoTdtT8Ons3Fxpisnog:98174511",
    "headers": {},
    "resource_stats": {
      "total": {
        "cpu_time_in_nanos": 0,
        "memory_in_bytes": 0
      }
    }
  }
}

Index security-auditlog-2023.07.23 has 2 shards (primary + replica) on nodes G9gVoTdtT8Ons3Fxpisnog and EWrZAyRuTnOktuuDhDtyOw
At the time when there was supposedly a problem on EWrZAyRuTnOktuuDhDtyOw in the log, I see:
[INFO ][o.o.c.c.FollowersChecker ] [***-mst02] FollowerChecker{discoveryNode={***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{****:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, failureCountSinceLastSuccess=1, [cluster.fault_detection.follower_check.retry_count]=3} failed, retrying
org.opensearch.transport.ReceiveTimeoutTransportException: [***-mst01][***:9300][internal:coordination/fault_detection/follower_check] request_id [538453465] timed out after [10006ms]
        at org.opensearch.transport.TransportService$TimeoutHandler.run(TransportService.java:1308) [opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) [opensearch-2.7.0.jar:2.7.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]

[WARN ][o.o.t.TransportService   ] [***-mst02] Received response for a request that has timed out, sent [19811ms] ago, timed out [9805ms] ago, action [internal:coordination/fault_detection/follower_check], node [{***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}], id [538453465]

[INFO ][o.o.c.c.FollowersChecker ] [***-mst02] FollowerChecker{discoveryNode={***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, failureCountSinceLastSuccess=2, [cluster.fault_detection.follower_check.retry_count]=3} failed, retrying
org.opensearch.transport.ReceiveTimeoutTransportException: [***-mst01][***:9300][internal:coordination/fault_detection/follower_check] request_id [538454273] timed out after [10005ms]
        at org.opensearch.transport.TransportService$TimeoutHandler.run(TransportService.java:1308) [opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) [opensearch-2.7.0.jar:2.7.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]

[INFO ][o.o.c.c.FollowersChecker ] [***-mst02] FollowerChecker{discoveryNode={***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, failureCountSinceLastSuccess=3, [cluster.fault_detection.follower_check.retry_count]=3} failed too many times
org.opensearch.transport.ReceiveTimeoutTransportException: [***-mst01][***:9300][internal:coordination/fault_detection/follower_check] request_id [538455143] timed out after [10005ms]
        at org.opensearch.transport.TransportService$TimeoutHandler.run(TransportService.java:1308) [opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) [opensearch-2.7.0.jar:2.7.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]

[INFO ][o.o.c.c.FollowersChecker ] [***-mst02] FollowerChecker{discoveryNode={***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, failureCountSinceLastSuccess=3, [cluster.fault_detection.follower_check.retry_count]=3} marking node as faulty

[INFO ][o.o.c.s.MasterService    ] [***-mst02] node-left[{***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true} reason: followers check retry count exceeded], term: 118, version: 56949166, delta: removed {{***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}}

[INFO ][o.o.c.s.ClusterApplierService] [***-mst02] removed {{***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}}, term: 118, version: 56949166, reason: Publication{term=118, version=56949166}
[INFO ][o.o.a.c.ADClusterEventListener] [***-mst02] Cluster node changed, node removed: true, node added: false
[INFO ][o.o.a.c.HashRing         ] [***-mst02] Node removed: [G9gVoTdtT8Ons3Fxpisnog]
[INFO ][o.o.a.c.HashRing         ] [***-mst02] Remove data node from AD version hash ring: G9gVoTdtT8Ons3Fxpisnog

After 13 seconds, the node G9gVoTdtT8Ons3Fxpisnog returned to the cluster.
The document that tried to write in the G9gVoTdtT8Ons3Fxpisnog:98174510 task is not currently in the index.

on G9gVoTdtT8Ons3Fxpisnog in log:
[INFO ][o.o.c.c.Coordinator      ] [***-mst01] cluster-manager node [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}] failed, restarting discovery
org.opensearch.OpenSearchException: node [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}] failed [3] consecutive checks
        at org.opensearch.cluster.coordination.LeaderChecker$CheckScheduler$1.handleException(LeaderChecker.java:320) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.security.transport.SecurityInterceptor$RestoringTransportResponseHandler.handleException(SecurityInterceptor.java:312) ~[?:?]
        at org.opensearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1414) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.transport.TransportService$TimeoutHandler.run(TransportService.java:1305) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) [opensearch-2.7.0.jar:2.7.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: org.opensearch.transport.ReceiveTimeoutTransportException: [***-mst02][***:9300][internal:coordination/fault_detection/leader_check] request_id [82540943] timed out after [10005ms]

[INFO ][o.o.c.s.ClusterApplierService] [***-mst01] cluster-manager node changed {previous [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}], current []}, term: 118, version: 56949165, reason: becoming candidate: onLeaderFailure

[WARN ][o.o.a.b.TransportShardBulkAction] [***-mst01] [[security-auditlog-2023.07.23][0]] failed to perform indices:data/write/bulk[s] on replica [security-auditlog-2023.07.23][0], node[EWrZAyRuTnOktuuDhDtyOw], [R], s[STARTED], a[id=2Mqj78tvQBGwZeWuiGQy-Q]
org.opensearch.transport.RemoteTransportException: [***-mst02][***:9300][indices:data/write/bulk[s][r]]
Caused by: java.lang.IllegalStateException: [security-auditlog-2023.07.23][0] operation primary term [1] is too old (current [2])
        at org.opensearch.index.shard.IndexShard.lambda$innerAcquireReplicaOperationPermit$42(IndexShard.java:3866) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.action.ActionListener$3.onResponse(ActionListener.java:130) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.action.support.ContextPreservingActionListener.onResponse(ContextPreservingActionListener.java:58) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShardOperationPermits$2.doRun(IndexShardOperationPermits.java:285) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.OpenSearchExecutors$DirectExecutorService.execute(OpenSearchExecutors.java:343) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShardOperationPermits.lambda$acquire$2(IndexShardOperationPermits.java:277) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.action.ActionListener$3.onResponse(ActionListener.java:130) ~[opensearch-2.7.0.jar:2.7.0]

[WARN ][o.o.c.a.s.ShardStateAction] [***-mst01] no cluster-manager known for action [internal:cluster/shard/failure] for shard entry [shard id [[security-auditlog-2023.07.23][0]], allocation id [2Mqj78tvQBGwZeWuiGQy-Q], primary term [1], message [failed to perform indices:data/write/bulk[s] on replica [security-auditlog-2023.07.23][0], node[EWrZAyRuTnOktuuDhDtyOw], [R], s[STARTED], a[id=2Mqj78tvQBGwZeWuiGQy-Q]], failure [RemoteTransportException[[***-mst02][***:9300][indices:data/write/bulk[s][r]]]; nested: IllegalStateException[[security-auditlog-2023.07.23][0] operation primary term [1] is too old (current [2])]; ], markAsStale [true]]

[WARN ][o.o.c.c.ClusterFormationFailureHelper] [***-mst01] cluster-manager not discovered or elected yet, an election requires at least 2 nodes with ids from [G9gVoTdtT8Ons3Fxpisnog, Cdr_6h2MTeGaPNy3zBolSg, EWrZAyRuTnOktuuDhDtyOw], have discovered [{***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{zone=***, shard_indexing_pressure_enabled=true, type=service}, {***-mst03}{Cdr_6h2MTeGaPNy3zBolSg}{mZHKmOPOQHKggJmiRcFgvQ}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}] which is a quorum; discovery will continue using [<IP_ADDRESS>:9300, <IP_ADDRESS>:9301, <IP_ADDRESS>:9302, <IP_ADDRESS>:9303, <IP_ADDRESS>:9304, <IP_ADDRESS>:9305, ***:9300, ***:9300] from hosts providers and [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, {***-mst03}{Cdr_6h2MTeGaPNy3zBolSg}{mZHKmOPOQHKggJmiRcFgvQ}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}, {***-mst01}{G9gVoTdtT8Ons3Fxpisnog}{VPG3x0ovSYyxZQ9JKYIv2A}{***}{***:9300}{dm}{zone=***, shard_indexing_pressure_enabled=true, type=service}] from last-known cluster state; node term 118, last-accepted version 56949165 in term 118

[WARN ][o.o.a.b.TransportShardBulkAction] [***-mst01] [[security-auditlog-2023.07.23][0]] failed to perform indices:data/write/bulk[s] on replica [security-auditlog-2023.07.23][0], node[EWrZAyRuTnOktuuDhDtyOw], [R], s[STARTED], a[id=2Mqj78tvQBGwZeWuiGQy-Q]
org.opensearch.transport.RemoteTransportException: [***-mst02][***:9300][indices:data/write/bulk[s][r]]
Caused by: java.lang.IllegalStateException: [security-auditlog-2023.07.23][0] operation primary term [1] is too old (current [2])
        at org.opensearch.index.shard.IndexShard.lambda$innerAcquireReplicaOperationPermit$42(IndexShard.java:3866) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.action.ActionListener$3.onResponse(ActionListener.java:130) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShardOperationPermits.acquire(IndexShardOperationPermits.java:309) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShardOperationPermits.acquire(IndexShardOperationPermits.java:254) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShard.lambda$acquireReplicaOperationPermit$40(IndexShard.java:3805) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShard.innerAcquireReplicaOperationPermit(IndexShard.java:3925) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.index.shard.IndexShard.acquireReplicaOperationPermit(IndexShard.java:3799) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.action.support.replication.TransportReplicationAction.acquireReplicaOperationPermit(TransportReplicationAction.java:1204) ~[opensearch-2.7.0.jar:2.7.0]

[INFO ][o.o.c.s.ClusterApplierService] [***-mst01] cluster-manager node changed {previous [], current [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}]}, removed {{***-ing02}{u9p6P23kTLqIaLls5j5GJQ}{T3n0iE1ASRipACeBAZKiAg}{***}{***:9300}{zone=***, shard_indexing_pressure_enabled=true},{***-ing01}{uUQV-5KZQSaiPrZJInSfnw}{0KTrT3tuRbWV-N5un0xLjQ}{***}{***:9300}{zone=***, shard_indexing_pressure_enabled=true}}, term: 118, version: 56949169, reason: ApplyCommitRequest{term=118, version=56949169, sourceNode={***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}}

[WARN ][o.o.c.a.s.ShardStateAction] [***-mst01] unexpected failure while sending request [internal:cluster/shard/failure] to [{***-mst02}{EWrZAyRuTnOktuuDhDtyOw}{4M5V6J7lSjyurzHlLlxp-w}{***}{***:9300}{dm}{type=service, zone=***, shard_indexing_pressure_enabled=true}] for shard entry [shard id [[security-auditlog-2023.07.23][0]], allocation id [2Mqj78tvQBGwZeWuiGQy-Q], primary term [1], message [failed to perform indices:data/write/bulk[s] on replica [security-auditlog-2023.07.23][0], node[EWrZAyRuTnOktuuDhDtyOw], [R], s[STARTED], a[id=2Mqj78tvQBGwZeWuiGQy-Q]], failure [RemoteTransportException[[***-mst02][***:9300][indices:data/write/bulk[s][r]]]; nested: IllegalStateException[[security-auditlog-2023.07.23][0] operation primary term [1] is too old (current [2])]; ], markAsStale [true]]
org.opensearch.transport.RemoteTransportException: [***-mst02][***:9300][internal:cluster/shard/failure]
Caused by: org.opensearch.cluster.action.shard.ShardStateAction$NoLongerPrimaryShardException: primary term [1] did not match current primary term [2]
        at org.opensearch.cluster.action.shard.ShardStateAction$ShardFailedClusterStateTaskExecutor.execute(ShardStateAction.java:485) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.MasterService.executeTasks(MasterService.java:874) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.MasterService.calculateTaskOutputs(MasterService.java:424) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.MasterService.runTasks(MasterService.java:295) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.MasterService$Batcher.run(MasterService.java:206) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:179) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:217) ~[opensearch-2.7.0.jar:2.7.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) ~[opensearch-2.7.0.jar:2.7.0]

It looks like the following happened:

node G9gVoTdtT8Ons3Fxpisnog had a primary shard with index security-auditlog-2023.07.23. Node EWrZAyRuTnOktuuDhDtyOw had replica
there was a task to add an entry to the index, the task began to be executed on the G9gVoTdtT8Ons3Fxpisnog node, it wrote the data and primed the shard and started trying to write a replica
at this moment the node G9gVoTdtT8Ons3Fxpisnog has lost connection with the cluster
node EWrZAyRuTnOktuuDhDtyOw saw that it had a replica of the security-auditlog-2023.07.23 index shard and the primary became unavailable. therefore, the replica became primary and recording began in it
when the G9gVoTdtT8Ons3Fxpisnog node returned to the cluster, it tried to continue the task, but could not complete it. And it doesn't cancel.

this is above my understanding, maybe @andrross can help?

@shwetathareja are you aware of any known bugs here? It looks like tasks can get orphaned on a node that has a network interruption but rejoins the cluster and the only way to remove the tasks is to restart the process on that node.


Remove beta references.

Remove beta references from issue template.

This is present on all ide-languages under Atom , i could create more PRs for these.

Thanks! Feel free to.


Can't find vscode version since V3

"V3 has some significant changes that will need to be accounted for in your
scripts.
We use semantic versioning now. The VS Code version will no longer be included
in the tag or the release file name. "
Some extensions are tie to particular vscode version,  so how can we find the version of vscode from the V3 releases?

The two ways I can think of are:

Use the "about" menu from VS Code.
Run code server with code-server --version --json which prints some extra version information in JSON format. It should look something like this (except the commit will be a hash):

  { codeServer: '3.0.2', commit: 'development', vscode: '1.43.2' }

Both of these require you to have already downloaded code-server though. If you're trying to figure out the version before downloading I think the only way is to click the tag from the release then go to lib/vscode/package.json and check the version listed there.
I think it might not be a bad idea for us to list the VS Code version in the release notes as well.

Please list the vscode version directly in the release notes


Opened dask, distributed, scipy dependencies

I updated the dependencies for dask, distributed, and scipy to be open for future releases.
I successfully tested the build on a distributed cluster using dask 2.9.0, distributed 2.9.0, and scipy 1.3.3

Thank you! There is no reason to force an specific package version.


Add Pinata Integration

usecase
We can use the uploadFileToIPFS() function to upload any file (images, gifs, videos) into the Pinata IPFS.
requirements

Pinata key
Pinata Secret

@Ankush263 Hey, thank you so much for the PR. Can you please add some description on how one can use this?

Hi @Ankush263, thanks for the PR; as @viral-sangani mentioned, please add more description.
I think Celo Examples could interest you in this particular case.
Closing PR in the meantime.

@nestorbonilla  @viral-sangani  I add some descriptions as you mention. Let me know if anything else is required..

Hi @Ankush263, thanks for the update. This suggestion fits better under celo-examples as a complete example, given that there are many IPFS pining services, and Pinata is just one of them.
Would you like to create an example on celo-examples?

sure, should I make a PR in celo-composer-react-example repo ...??? @nestorbonilla


Pass minHeight as a integer to Redactor

minHeight wasn't working because it was passed as a string

Hah thanks, this was driving me nuts


chore: Context changes

Fixes #93
Updated the security context in values file

@evegufy : I did the rebase


Fix isInvalid equality check

=== comparisons only works when Zod is installed once in a monorepo setup with multiple packages using Zod.
This PR changes it to use structural type checking rather than referential equality checking.
The test reproduces the issue (i.e. fails before applying the change).
Closes #556

@krivachy Nice work sleuthing this. I'll double-check the benchmarks to ensure it's not a big regression, but I imagine it shouldn't be a noticeable increase in checking object reference equality vs checking an object's property boolean state. I'll comment here when I get some benchmarking results back.

Thanks :+1: Looking forward to have this PR in for the next release :)

I didn't notice any performance regressions on the benchmarks, so I think this is good to go!

@scotttrinh This isn't super urgent for me, but just wondering why you haven't merged the PR yet? Does someone else also need to review this PR and merge it?

@krivachy I was hoping someone else would do the actual merge since I haven't done it since becoming a collaborator, but I'm not sure why I'm hesitant! I'll merge it now, thanks for the ping.

Thanks!


BUG: ray 1.13 breaks CI, including test_binary and test_pickle, with circular import

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS Monterey 12.2.1
Modin version (modin.__version__): ba2b6ea47d81575e41af6c92ba4c2c3f8bcf54e2
Python version: 3.9.12
Code we can use to reproduce:

With ray 1.13, run
pytest modin/pandas/test/dataframe/test_pickle.py
and
pytest modin/pandas/test/dataframe/test_binary.py
and maybe more.
Sample CI failure: https://github.com/modin-project/modin/runs/6819134820?check_suite_focus=true
Describe the problem
I can't tell what's going wrong. The ray tasks raise a RaySystemError with stack trace ending in ImportError: cannot import name 'DataFrame' from partially initialized module 'pandas.core.frame' (most likely due to a circular import), e.g. for  modin/pandas/test/dataframe/test_pickle.py::test_column_pickle[True]:

Stack trace
ray.exceptions.RaySystemError: System error: cannot import name 'DataFrame' from partially initialized module 'pandas.core.frame' (most likely due to a circular import) (/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/frame.py)
traceback: Traceback (most recent call last):
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/ray/serialization.py", line 340, in deserialize_objects
    obj = self._deserialize_object(data, metadata, object_ref)
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/ray/serialization.py", line 237, in _deserialize_object
    return self._deserialize_msgpack_data(data, metadata_fields)
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/ray/serialization.py", line 192, in _deserialize_msgpack_data
    python_objects = self._deserialize_pickle5_data(pickle5_data)
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/ray/serialization.py", line 180, in _deserialize_pickle5_data
    obj = pickle.loads(in_band, buffers=buffers)
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/frame.py", line 157, in <module>
    from pandas.core.generic import NDFrame
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/generic.py", line 114, in <module>
    from pandas.core import (
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/indexing.py", line 45, in <module>
    import pandas.core.common as com
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/__init__.py", line 48, in <module>
    from pandas.core.api import (
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/api.py", line 48, in <module>
    from pandas.core.groupby import (
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/groupby/__init__.py", line 1, in <module>
    from pandas.core.groupby.generic import (
  File "/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/groupby/generic.py", line 70, in <module>
    from pandas.core.frame import DataFrame
ImportError: cannot import name 'DataFrame' from partially initialized module 'pandas.core.frame' (most likely due to a circular import) (/Users/maheshvashishtha/opt/anaconda3/envs/modin-latest/lib/python3.9/site-packages/pandas/core/frame.py)

For modin/pandas/test/dataframe/test_binary.py for some reason I can't reproduce the failure on my laptop but here it is in CI: https://github.com/modin-project/modin/runs/6819134820?check_suite_focus=true

This has historically been a race condition between the import thread and the thread which starts running code. This code originally fixed that:
https://github.com/modin-project/modin/blob/ba2b6ea47d81575e41af6c92ba4c2c3f8bcf54e2/modin/core/execution/ray/common/utils.py#L226
@modin-project/modin-ray Do you know what changed with the import thread?

@devin-petersohn it seems we were getting lucky with that function, as it stopped doing what it was doing somewhere after 1.0: https://github.com/ray-project/ray/issues/12599
And they still don't have a good enough replacement based on https://github.com/ray-project/ray/issues/13908
😞

We should pin ray < 1.13.0 because I don't see an easy fix. I'll send a fix for new issue #4566.

I am also testing adding a sleep during Ray initialization: https://github.com/modin-project/modin/pull/4568

I think we might have changed some parts around function import/export recently. Can you create an issue with Ray github? I can tag a guy who touched that part of codebase.

@rkooo567 Created issue here: https://github.com/ray-project/ray/issues/25675

@devin-petersohn  we shouldn't use ray.worker.global_worker.run_function_on_all_workers(_import_pandas) since this is a private API.
Could you give more detail why it's used there?
Btw, ray also has modin tests in master which seems running good.

@iycheng we use that API because of the import thread race condition. This allowed all workers to import pandas before the execution of any tasks. The import thread race condition is the fundamental issue that we would hope to get fixed in Ray.

@devin-petersohn could you share more details about which race condition? Like in what case it'll fail if we don't do this.
Btw, we updated the function importer to do lazy things right now:

export if it doesn't exist in the global function table
import if it doesn't exist locally

so we import as need compared with before where we import everything.

The race condition has historically been very difficult to reproduce regularly. At first, we were seeing it only on large CPU machines, but now it happens regularly in our testing infrastructure.
Is there still a thread that imports libraries separately from deserialization and execution?

For run_function_on_all_workers, yes, it's still working as before.
But for normal functions, we are not doing that any more since it doesn't make sense to import the function that's not used by the current worker.

@devin-petersohn firstly, run_function_on_all_workers is not a public API and we shouldn't use this one outside of ray core.

The run_function_on_all_workers was intended to force all workers to fully import the pandas library before any execution starts.

Also this actually is incorrect, import thread is running async, it's not guaranteed and ray worker could be alive to take function before the function you want to run finished since all this happens in different thread (race condition)

@devin-petersohn I tried it locally and https://github.com/modin-project/modin/pull/4594 at least can pass my local run with
pytest modin/pandas/test/dataframe/test_pickle.py
pytest modin/pandas/test/dataframe/test_binary.py

The removal of run_function_on_all_workers is not necessary, but I just add it there (it needs to be removed for long term. all these are private APIs from ray).
I think the only thing I did is to copy setup.cfg to modin/pandas/test/dataframe/setup.cfg
I'm not quite sure about why it passes on my laptop.
I think you need to run the script with cwd as modin/pandas/test/dataframe otherwise, you'll need to put that dir into runtime env working dir.
Add main function into tests (example here) and test with python modin/pandas/test/dataframe/test_binary.py will also work since the working dir will be changed to modin/pandas/test/dataframe directly in ray.
I'm not sure about the race condition you mentioned unless you can show me some script which can reproduce this easily.

@devin-petersohn it seems the lint failed in that PR
I don't have a setup dev env for Modin. Do you mind taking this over and see whether there is any issues left? Also this might not be the idea way to fix, but I think the issues is about the working dir for the test script.

@mvashishtha are you running it with the PR I mentioned above? I didn't see any errors there. I'm running with master ray.
~/modin (fix-import) $ python test.py
UserWarning: Ray execution environment not yet initialized. Initializing...
To remove this warning, run the following python code before doing dataframe operations:

    import ray
    ray.init()

DeprecationWarning: `ray.ray_constants.MAC_DEGRADED_PERF_MMAP_SIZE_LIMIT` is a private attribute and access will be removed in a future Ray version.
UserWarning: Distributing <class 'numpy.ndarray'> object. This may take some time.

@iycheng  no, but when I run it with your PR #4594 at commit 6702bae9e70c448fc698c9d150c69b54df040c68, the script in my comment no longer shows the bug.
@devin-petersohn do we need to do any further testing for the import race condition, or will #4594 work?

I wonder if this is related to https://bugs.python.org/issue38884, as I see in the CI logs:
2022-06-09 19:25:08,443	WARNING worker.py:1404 -- Traceback (most recent call last):
  File "/usr/share/miniconda/envs/modin/lib/python3.8/site-packages/ray/_private/import_thread.py", line 193, in fetch_and_execute_function_to_run
    function({"worker": self.worker})
  File "/home/runner/work/modin/modin/modin/core/execution/ray/common/utils.py", line 94, in _import_pandas
    import pandas  # noqa F401
  File "/usr/share/miniconda/envs/modin/lib/python3.8/site-packages/pandas/__init__.py", line 48, in <module>
    from pandas.core.api import (
  File "/usr/share/miniconda/envs/modin/lib/python3.8/site-packages/pandas/core/api.py", line 48, in <module>
    from pandas.core.groupby import (
  File "/usr/share/miniconda/envs/modin/lib/python3.8/site-packages/pandas/core/groupby/__init__.py", line 1, in <module>
    from pandas.core.groupby.generic import (
  File "/usr/share/miniconda/envs/modin/lib/python3.8/site-packages/pandas/core/groupby/generic.py", line 70, in <module>
    from pandas.core.frame import DataFrame
  File "<frozen importlib._bootstrap>", line 988, in _find_and_load
  File "<frozen importlib._bootstrap>", line 149, in __enter__
  File "<frozen importlib._bootstrap>", line 94, in acquire
_frozen_importlib._DeadlockError: deadlock detected by _ModuleLock('pandas.core.frame') at<PHONE_NUMBER>89504

The more I read that Python bug the more I feel it is very likely the real root cause for what we have here...

@vnlitvinov is there a case where the race condition persists even after #4594?

@vnlitvinov  please see this comment for details.
Keep run_function_on_all_workers also should just work. Two ways to make it work:

copy setup.cfg to the test dir (not sure why, but maybe this change the working dir to the place where the script is)
run the test in the place where the script is

Btw, as I mentioned, this is private API in ray, please try not to use.
Please keep in mind we might remove this function since this is not used in ray core and it's async executed like before, which means you won't know when will this function be executed. It can be executed even after the function runs.
As the race condition mentioned in this ticket, if some reproducible scripts can be given, I'll be like to take a look.

Any estimation when will Ray 1.13 be officially supported ?

@tianlinzx the open PR #4603 linked to this issue should fix this bug. That PR is under active discussion. As soon as it's merged, you can install Modin from the latest source, or wait for a Modin release that includes that fix.

@iycheng Modin no longer uses run_function_on_all_workers (will be released in 0.16 soon™), so I guess Ray can continue deprecating this feature if we were the only library using it.

When will modin 0.16 be released ?

@tianlinzx I'm sorry for the late response. The Modin contributors are hoping to release 0.16 before the end of the next week (October 7).


Noticeable chess board effect on Sintel pre-trained checkpoints output

Hi, @daigo0927 thank you for your decent implementation of the TF version. It was fun playing with it.
However, I noticed that with your pre-trained Sintel checkpoints. It tends to produce Chess Board Effect. (TF version (top) vs. Paper Pytorch version (bottom))

Do you know where does it come from? Thanks!

Sorry for my late reply...
This is caused by the difference in the training procedure between mine and the original one. The training reported in the original paper uses FlyingChairs and FlyingThigs3D datasets (see Table1 in https://arxiv.org/abs/2003.12039) for pre-training.
I have trained the RAFT model only on MPI-Sintel or FlyginChairs, and FlyingThings3D is too large for me to train the model in my personal GCP environment 💸 ... This lack of training may cause the above checker-board effect.
I have described other notes at the bottom of the README. Thanks! 😄

Hi, thank you very much for your reply!
That is also one of my guesses. According to their source code, they trained in the order of Chairs->Things3D->Sintel.
I'll double-check on that see if this will be fixed.
Have a good day :)

Double-check sounds awesome! I'm looking forward to seeing the results 😃 .


Duplicate "Resource group" with wrong description

The description "API used to analyze text" was from a previous table.

@ggailey777 - Please review the proposed changes.  Thanks

@andresnava thanks for proposing a fix. I needed to make a more substantial fix to this topic for the issue you highlighted, which I ended-up doing in the private repo. Please continue to help us out with these fixes. #please-close


Add Node.js ReadableStream support

This adds crc[8,16,32]Stream functions as crc.stream.crc[8,16,32] that accept a Node.js ReadableStream object and a callback taking (error, crc)

Is it merged?


Rename Capacity to ClusterQueue and Assignment to Admission

What type of PR is this?
/kind cleanup
/kind api-change
What this PR does / why we need it:
Capacity not only defines usage limits for a set of tenants, but it is the level at which ordering will be done for workloads submitted to queues sharing a capacity.
"Assigning to a ClusterQueue" no longer makes sense. The correct interpretation is that the QueuedWorkload got admitted by the ClusterQueue. Thus, we group all the admission details in a struct within the QueuedWorkloadSpec.
Which issue(s) this PR fixes:
Fixes #85
Special notes for your reviewer:
I tried my best to split the 2 renames in different PRs, for reviewer convenience. But I might end up squashing them after review.
I might have missed some renames in some test variables. I think we can fix them in follow ups.

/hold
/assign @ahg-g
Good thing we have tests :D

squashed

/lgtm

/hold cancel


Server, patch thyself

This will rewrite configuration files to automatically install updates. By default, the AMIs already have unattended-upgrades installed, but it just updates package lists daily. This will also download packages and upgrade them daily, plus run autoclean weekly. (as recommended at https://help.ubuntu.com/lts/serverguide/automatic-updates.html) The default configuration will only automatically install package updates in xenial-security. I've already run the three new lines in a root shell on both currently running servers. I'm going to check back in a week or so on /var/log/unattended-upgrades/ to see if things are working.

Patch thyself!

Woo!
2016-10-23 16:42:00,216 INFO Initial blacklisted packages:
2016-10-23 16:42:00,216 INFO Initial whitelisted packages:
2016-10-23 16:42:00,216 INFO Starting unattended upgrades script
2016-10-23 16:42:00,216 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security']
2016-10-23 16:42:02,632 INFO Packages that will be upgraded: tzdata
2016-10-23 16:42:02,633 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
2016-10-23 16:42:05,515 INFO All upgrades installed

Nice!!


*: Remove deprecated StorageSpec fields

In v0.11.0 (released 2017-07-20) some StorageSpec fields have been deprecated and we want to finally drop them, as the Prometheus Operator itself doesn't even use them anymore inside it's code.
Closes #2121
/cc @brancz @squat @mxinden

Want to remove these from the v1alpha1 too?

beat me to this PR, btw :)


[Api Doc] Add icon preview

Added preview icon on API documentation

Won't this cause confusion with the other icons (i) for example? I'm afraid users will wonder why we put an "Information" symbol there.
Maybe in a tooltip?

Or show "Preview: {image}" and show the dual name in a tooltip?

Also a good solution


Made documentation for note, Changed version in setup.py,

Fixed python version for GitHub Action
Edited README.md

@nil-malh Big thanks!!!

I will pushed another pr to fix the isort test after that, you might take a look into why some other test failed i'm no expert in python initially


Make it possible to generate only given template files

Reason/Context
I'd like to use generator not only to scaffold my project when I start working on my application. I also want to use it continuously, every time I change something in AsyncAPI document.
The problem is that regeneration means basically another generation of the entire template. This leads to a process of regenerate -> carefully go through each change introduced after regenerating and ignore changes that will break your code
More context here.
Description
A partial solution for the problem, but also not very complicated would be a configuration I could pass to the library/cli where I could specify what files to include/exclude in a generation.
Let's say I use some Node.js template. I generated my app and later added some more dependencies for my business login. Later I want to regenerate, but by telling the generator to ignore package.json and package-lock.json files.
What do you think? is the use case clear? you think it makes sense?

How about we take a page from prisma migrations. We might have to change a lot of things, but what if the generator keeps track of the previous state of the asyncapi spec and only update what has changed.

I think that it's still relevant :) cc @derberg

I re-read your blog post @derberg and one thought that came to mind was, why even generate code that mixes your own implementation alongside the generated code 🤔 In my experience, I have never understood why you want to generate code alongside custom code. I have always seen it as a huge problem when you evolve your API when you mix the two (especially as we have seen with OpenAPI HTTP server code). So the opposite thought could be that you simply should not? 🤔
For example for the WebSocket server, would it not make more sense to create an interface for the generated code that you can integrate into your own application? I.e. instead of having scaffolding routes generated src/api/services/chat.js, the generated code should instead give you an interface for you to interact with. This way you will always be able to overwrite the old generated code and evolve your API without worrying about "maybe" you overwrite your code.
Example change (hope it makes sense):
const subChatMessage = undefined;
const pubChatMessage = undefined;
router.ws('/chat', async (ws, req) => {
  const path = pathParser(req.path);
  console.log(`${yellow(path)} client connected.`);
  subChatMessage(ws);
  ws.on('message', async (msg) => {
    console.log(`${yellow(path)} message was received:`);
    console.log(util.inspect(msg, { depth: null, colors: true }));
    await pubChatMessage(ws, { message: msg, path, query: req.query });
  });
});
export function setSubChatMessage(subChatMessage){
  subChatMessage = subChatMessage;
}
export function setPubChatMessage(pubChatMessage){
  pubChatMessage = pubChatMessage;
}

In this generated code you simply enable the user to interact with the generated code, and it is also here you can make sure that everything is in according to the AsyncAPI document i.e. set message types, etc.
In terms of supporting the proposed feature or a version thereof, maybe it makes sense to highlight you should try to never get yourself into such a situation, i.e. always keep generated code separated from business logic? 🤔
I am not sure if there ever is a time where such an approach simply does not make sense?

but I still need to "connect the dots" somehow, right? or?
Like I need to require/import interface of some given name from a given path, that is custom depending on the AsyncAPI file?

@jonaslagoni you can do this but not in all cases, simple example: package.json. After generation, I want to add another dependency there. Regeneration will remove that.

I was surprised to see that the generator creates a complete project including build files and not just stubs/interfaces. To me, the purpose of a schema document like asyncapi should foremost be to unify the interfaces and contracts between the clients/servers using the API. The implementation/project structure should not be of concern for the generator.

@Mettbrot for interfaces, models, classes you have https://github.com/asyncapi/modelina project
generator is aimed for something more, for full clients or apps generation, like for example you can bootstrap a microservice that gives you out of the box handlers, routers and other useful features to kick off prototyping faster

we basically need analogical functionality to existing noOverwriteGlobs option that works in the way that you say what paths should be ignored during generation. We need an option generateOnly and also support globs there, so I can say generate *.json only or something like this

Hello everyone, I'm here after seeing the title, and for the past three days, I've been encountering a similar problem. Basically, I'm working in Go, where I have some socket events, and I want to document them. To do this, I've used asyncapi/generator. In my Dockerfile, I've written commands for this procedure. However, during the application build process in the pipeline, this procedure takes too much time because it generates the entire document. Can anyone provide a proper solution to generate only the HTML file?
Here is the command I'm using in the Dockerfile:
RUN ag ${SOURCEROOT}/asyncapiDefinition.yml<EMAIL_ADDRESS>-o ${SOURCEROOT}/docs/socket --force-write

Could I be assigned this issue? Since I implemented the noOverwriteGlobs, I should be able to do this : )


Remote Storage Flicker/Loses Connection

Minecraft 1.11
Version: 1.1x-6.01
Pack: All the Mods 2
A modular storage chest with a linked remote storage module constantly flickers on and off. I'm using 2 storage modules and a remote storage block as an ender chest system to transfer items from mob farms wirelessly. The Remote Storage Module seems to flicker on and off constantly in the modular storage block, as item stacks go from 1 - 50/ 300 to 0/0 stacks.
The Remote Storage Block is constantly powered by an RFTools Powercell, and they are only separated by a couple chunks apart.
Cross dimension access is disabled,

This has been reported before but I have never been able to reproduce it. Can you give me a bit more information:

Server or single player?
Using a chunkloader?
What do you mean by 'as item stacks go from 1/50/300 to 0/0'?

When I have more than one storage module in a remote storage block, the remote module automatically swaps through them, displaying each in turn.  This occurs if only one of the modules has anything in it.  When I put some items in another module, then the swapping stops and it works normally.  It took a few seconds for the system to recover when I added a non-empty module to a block where the flickering was occurring.

Update: Some flickering still occurs but it's more manageable.  I can confirm that neither power (fed with cryotheum fluxduct) nor chunk loading (right next to block and cc chunk loader active) is responsible.  One of the slots in the remote storage is empty and the remote module in the tablet might be swapping to it on occasion, causing the flicker.

Hey all,
I was having the same issue today. I believe I've found a cause and a way to reproduce the problem consistently on my end - MC 1.12.2 w/ RFTools 1.12-7.15
So I placed down the Remote Storage and the Modular storage without modules in them. I powered up the RS and placed in a T3 storage module and linked a remote module. I then placed it in the RS which flickered on and off. I then break the RS block, with the module inside, and place it back again. The flickering is not gone, but it's now only once or twice every few minutes, opposed to every second or two.
Reproduction is easy, just break everything and place it back in the order above and the issue comes straight back. @McJty if you're unable to reproduce on your end I'm happy to record the reproduction on my end if that helps.

I have this issue in both MC 1.7.10 and 1.11. I found in 1.7.10 that the issue occurs if the storage unit and the remote storage unit are in different chunks.

It's occuring for me in Forever Stranded Lost souls RFTools 1.12-7.29
happens when I'm in the same chunk so chunk loading is not the cause. It flickers when I'm using it on a portable tablet, but it does not happen when I'm using it via a modular storage.
I tried surrounding the remote storage with capacitors  and/or fluxducts.. still happens.
I tried removing all points of access and leaving just the one on my one tablet, and it still happens.
I tried using a different battery (Thermal's flux capacitor, and Actually addition's battery)
I tried moving it away from my storage scanner's range.
...it keeps flickering, any advice?

log entry (but this looks unrelated)
[main/ERROR] [mcjty.lib.varia.Logging]: java.lang.RuntimeException: Internal error! getSideWindowBounds() called before initGui!

oooh, ignore me, Issue was probably caused by too many 'dying withers that should have actually died ages ago' (or maybe xp orbs)
if you care,
There appears to be an issue when trying to use a Compact machine as a wither farm (with Industrial forgoing wither builder/mob crusher), I gave it a small inventory of soul sand and skulls and let it run, thinking rightly it should be done within a day, and it was, but when I visited it there was some loud noise and an explosion of -something- (xp orbs?) and then whatever was making a mess fixed itself.
Question for you: Why was this affecting the tablet w/remote storage but NOT affecting the tablet w/storage scanner? food for thought :)

Hi @McJty ,
I've been still encountering this flickering bug lately. Sorry but it might be related to tps on the world. I do not encounter this on a fresh world but it keeps flickering on my Single player world. TPS on this world is already at 10 TPS on average due to the amount of automated systems.


[WIP] React Client

To get it running:

npm install -g webpack
cd materia
npm install
npm run-script watch
Browse to /materia for fun times

A few things of note:

React / Redux Architecture
Webpack for asset bundling
Switched to SASS
Vendor libs via npm (both JS and SASS)
Server decouplement (yay! electron desktop app now??)
Needs tests
Still loads to do for parity with current client

Hello. How to set default folder as materia (set reactjs instead of backbone)?


[hotfix] Remove redundant backslash in the log of GPUDriver

What is the purpose of the change
Remove redundant backslash in the log of GPUDriver
Brief change log
Remove redundant backslash in the log of GPUDriver
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.

master: ad828cb5709f5f28d32bcdb0d7aa8ff3868f476a
1.11.0: 3f43fc6bd31976a279cdce8301199249f5c38dc4


Use launchpad ppa to distribute debian package

ppa is already created.
We need to add a script that submits build when we push to stable channel

While you're at it, please consider creating an RPM as well to support Red Hat, Fedora and OpenSUSE. Maybe this should be a new issue.


Sample projects for .NET 8 Blazor webapps are 4 years old.

Please update Blazor samples for .NET 8 and Entra Security Single Org ASAP.

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

ID: b90331e5-cca5-b157-eaa1-6f8f90003b32
Version Independent ID: 4b1b803d-e30d-10b2-90a1-3f0ccd8d7d44
Content: Code samples for Microsoft identity platform authentication and authorization - Microsoft identity platform
Content Source: docs/identity-platform/sample-v2-code.md
Service: active-directory
Sub-service: develop
GitHub Login: @OwenRichards1
Microsoft Alias: owenrichards

@ggrater-touchmark
I've delegated this to @OwenRichards1, a content author, to review and share their valuable insights.


Code Refactoring

What Changed

project.inceptionYear variable added to make license generation accurate
Code refactored to remove "MyFirstClass" type variable and context names
Removed comments from .ftl files as they were breaking the plugin
Added extra logging to better explain possible errors
Added checks to ensure that global bamboo variables have been set

@whbath Is it OK for me to merge these changes?


Add lint: modifying camera code under FixedUpdate schedule

See #99 for more details.

Note that the correct schedule for camera update code is the last variable timestep before the fixed schedule for things that influence the physics, usually rotation, and Update for things that react to the physics, e.g. following the player.
Somewhat confusingly, the last variable update before the fixed schedules is not PreUpdate, but a specific ordering inside RunFixedMainLoop. See the fixed timestep example in the Bevy repo.
As for how to detect camera code: is it too X-Controversial to just look at the name of the involved components and see if they contain the word Camera?

As for how to detect camera code: is it too X-Controversial to just look at the name of the involved components and see if they contain the word Camera?

I'm punting it to Nursery, if that's the approach we choose. There's a lot of opportunity for false positives, and I wouldn't be comfortable stabilizing it without testing in the wild.


UnitTesting

Hi Armand, great job, I've been playing around with this package a bit, I found it very interesting, you have some unit test, I'm willing to work on this, but I wouldn't want to break it!

Hello friend, thank you for showing interest in the project :D you are more than welcome to send me a PR with your enhancements and am happy to create a contributors section in the readme and link back to your profile.


(PUP-10819) error handling for 3x functions.

Updates error handling when a 3x function is deferred

Superseded in https://github.com/puppetlabs/puppet/pull/8477

Superseded in https://github.com/puppetlabs/puppet/pull/8477


Firmware v3.0.1 no longer polling DS18B20 & reporting temp

REF: https://www.facebook.com/groups/konnected.io/posts/1556001921433830/
Verified with two different DS19B20 sensors & connected to two different pins. This was working with firmware 2.3.5. Once I upgraded to v3.x, the DS18B20 no longer reports temp.
Connected to the console using the web tool. In the console, I see it report the state of two pins & that it would poll for 3m (180000ms) on the pin the temp sensor is connected to, but it would never show.

So far have not been able to reproduce the problem. Two temp sensors connected on zone 1 working fine for me.

@andrewconnell can you share your complete zone configuration?

Hi @heythisisnate ... thanks for the reply. Sure... full zone setup:

two reed switches (binary sensors) connected to zones 1 & 2 & working as expected
temp sensor connected to zone 5 (also tried zone 6)

For good measure, here's my wiring setup:

that's a 4K7 resistor between the signal (yellow) and VCC (red) connectors
using the red alligator clip to power while debugging as my microUSB blocks plugging something into the 5V jumper

The only other thing that's strange is that when I configure it in HomeAssistant, I'm not seeing the polling interval change when I set it to something like 1 or 2 minutes... in the console, it's always showing 3m (180,000ms).

@h2zero could you take a look at this one and try to reproduce

FYI @heythisisnate, this has been working since v3.1 & also is working on the latest firmware. I should close it, but not sure if you want to leave it open to continue investigation..

Great. we will will close it then. I suspect it was a memory issue that has been resolved by the upgrade to the underlying firmware.


Total Task Duration (Seconds)  Empty

Hi all,
Under the instance details  page
nifi_instance_details
the panel  Total Task Duration (Seconds)
with:

Max_TotalTaskDurationSeconds
Avg_TotalTaskDurationSeconds

are always empty ...I'm wondering if I need to enable some logs or some flags in order to provide information to this panel
and my dummy question what exactly this panel calculate?
Thank you

Hi,
The data from my nifi show 0 in this field.
Run index=* sourcetype="nifi:reporting:task" query and show

thanks again for your support
TotalTaskDuration it;s in the search  as well, but on the panel is always not shown the value,  maybe because is very small value


fix(date): date and time string limited to 63 chars

Sensible upper limit of 1024 chars since anything of that length will
not be fully rendered on the bar anyways.
fixes #744

Ah crap, I thought boost was already a dependency, but I guess this was back when this was still called lemonbuddy.
I'll fix this in the next few days


fix stream option not working with to_gpu

CPU-to-GPU transfer with CUDA stream is not working.
It seems that this error was introduced in #2238.

Thanks!
LGTM


Unable to add external participant

After entering external phone number, nothing happens. I cannot see the calling.. image etc..
However we saw following issue in Twilio debugger.
Error - 82002
Error on Twilio Function response - add-conference-participant
UnhandledPromiseRejectionWarning: Unhandled promise rejection: Error: The source phone number provided, undefined, is not yet verified for your account. You may only make calls from phone numbers that you've verified or purchased from Twilio.
Why it is receiving undefined number?

Also getting error
Uncaught Flex JavaScript Exception: Details of this error is as follows:
flexUIVersion: 1.20.1
user.identity: apps7
user.roles[0]: admin
message: Error adding participant +14084441209
[TypeError: Failed to fetch]

Hi

Hi..... How did u resolve this issue @gsikhawal

hI.. How did u resolve this error @gsikhawal


Decide on a public domain name

We need to decide on which domain we should use for the marketing / demo page for this library. We could just use a Netlify subdomain, we may want to establish it as an azavea.com subdomain, or we may want to purchase a domain. This is probably more of a marketing / branding question than a technical one.
In the short term, a netlify.com subdomain will get us up and running.

react-showtime.dev


deepin.dtkwidget: <IP_ADDRESS> -> <IP_ADDRESS>

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dtkwidget/versions.
meta.description for deepin.dtkwidget is: '"Deepin graphical user interface library"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>

directory tree listing: https://gist.github.com/3fc2a6e2a57d1020842ef6adb797575c

du listing: https://gist.github.com/5313298e77f1f88d5ed998ec02aaf01e

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/639d161199269511b75b349ddbf3e9fd8c7c07c6.tar.gz -p deepin.dtkwidget
ls -la /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>

cc @romildo for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: deepin.dtkwidget
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: deepin.dtkwidget
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>
/nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>
shrinking /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>/lib/dtk2/dtk-svgc
shrinking /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>/lib/libdtkwidget.so.2.0.6
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>/lib
patching script interpreter paths in /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>
checking for references to /build in /nix/store/jr11klwv1xpnl5dwd82297ln3fz7dzr6-dtkwidget-<IP_ADDRESS>...
postPatchMkspecs
postPatchMkspecs

Success on aarch64-linux (full log)
Attempted: deepin.dtkwidget
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>
shrinking /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>/lib/dtk2/dtk-svgc
shrinking /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>/lib/libdtkwidget.so.2.0.6
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>/lib
patching script interpreter paths in /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>
checking for references to /build in /nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>...
postPatchMkspecs
postPatchMkspecs
/nix/store/kyq2kapd7rkyk9kcklj0day8q6y5zphs-dtkwidget-<IP_ADDRESS>


Current demo shows pageviews for current day twice

Should the bugfix be already deployed (the issue still is present on the current instance at app.kindmetrics.io?

@alexanderadam I am preparing this release as it is the full version. Still preparing the changes on the landing page as I am moving its hosting to the EU instead of GitHub pages. That and some small fixes on the pricing plan and such :)


Fix embarassing problems in tests

The issue with these tests is self-evident, I believe.

This is great!

wow


CNDB-6178

Does any of this make sense as OSS C* features on their own?  If not can we implement this stuff only in CNDB somehow?  There are a bunch of changes to add parameters to things that may be a pain to maintain forked?

@maxtomassi I've applied your review suggestions, please have a look when you have a moment.
@JeremiahDJordan I guess you're referring to Timer and the changes to ReplicaPlans. I think the former is a good abstraction to have and I think we should use it later to expire the response callbacks, similarly to what we do in DSE (food for another ticket). Regarding the latter, ReplicaPlans is unfortunately a wonderful class full of static methods, so there isn't much we can do other than introducing a whole new abstraction, which seems overkilling in this case. Thoughts?

@JeremiahDJordan I guess you're referring to Timer and the changes to ReplicaPlans.

Yeah the replica plan stuff.  I think the OSS feature would be to implemented the pluggable batchlog_endpoint_strategy like we have in DSE?  and then we could include this prefer local stuff as a strategy when doing that.

@JeremiahDJordan Apologies for this late reply.

I think the OSS feature would be to implemented the pluggable batchlog_endpoint_strategy like we have in DSE?

I'm fine with that but I would unblock this ticket first, and address that in a followup directly on OSS.

Sure, I'm not trying to block this ticket.  Just want to understand what is in it and how it relates to what we can OSS.


Update and Re-indent Building Adapter page for 1.2

Description & motivation

added an overview section of the different areas that need work
change indentation level
updated the "(source)" URLs of all the macros to point to their new locations
added an explanation of standardize_grants_dict() method
instead of adding the GRANTS macros to the list of "required macros" I just made a new section and linked to them

Questions for @jtcohen6 (the first is the only required question for this PR, the other two are what I've been thinking

Should the grant macros be in "Required Macros" list?
What does it mean if a macro is in the "Required Macros" list but doesn't have (required) after it? AFAIK, it means they have default__ implementations but perhaps we're strongly suggest that they make their own version? I ask because isn't so exhausted

True or False: This Building an Adapters page should have any core-versioning dynamics because we'd recommend to anyone who wants to make an adapter that they should start with the latest version of dbt-core

closing in favor of #1727


"rules_group" controller type overwrites text of individual rules

I wanted to group up mods with categories that could be collapsed but all of the text in the individual rules got overwritten in the GUI.
Here is my code:
gist
And this is what it looks like:

fixed in 1.3.3


Make preload invalid paths null instead of a compilation error

Operating system or device - Godot version:
Windows 10
Godot 2.1 stable
Issue description:
The current behavior of preload with invalid paths is give an error in editor (Can't preload resource at path) and crash at runtime.

A better approach could be instead of give an error in editor and crash at runtime, preload could return null and let the user check ingame if the preloaded var/const is null.
This could be useful for addons, for example I have an addon which has a timer created by script for delayed triggers and I wan't the trigger addon to be independant from the project, but for this project the timer could be paused with a player ability, so I need a way to attach that script for the timer in the trigger. The easiest and optimal way to achieve this could be preload const and check if the script path is null.  So with this I could use the addon  without major modifications in another project or I could put another timer script at the path for custom behaviour in a new project.
NOTE: I'm aware of load and check/load the path in ready:
const _timer_script_path = "res://resources/scripts/timer.gd"

func _ready():
	var timer = Timer.new()
	var script = load(_timer_script_path)
	if(script != null):
		timer .set_script(script)

But that method should be less optimal because is 1 load for EACH ready vs a SINGLE preload in a CONST at start of the game
Steps to reproduce:
Create a script and try to preload an invalid resource with a const and run the game:
const _script = preload("res://resources/scripts/timer.gd")

I agree a crash is not great. Your proposal should be fine if it doesn't implies a runtime cost (besides initial load).

Crash (parse error actually) is fine, this is meant to always work. It
would be worse if you mess up the name, it doesn t work and you dont
realize you made a mistake.
On Mon, Nov 14, 2016 at 5:49 PM, Marc<EMAIL_ADDRESS>wrote:

I agree a crash is not great. Your proposal should be fine if it doesn't
implies a runtime cost (besides initial load).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7118#issuecomment-260458165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z28rXhNi8w45Eh-9cs7y4uSKDqr2Lks5q-MlZgaJpZM4Kxtpp
.

If you are not sure whether it should work or not, use load() instead.
On Mon, Nov 14, 2016 at 6:29 PM, Juan Linietsky<EMAIL_ADDRESS>wrote:

Crash (parse error actually) is fine, this is meant to always work. It
would be worse if you mess up the name, it doesn t work and you dont
realize you made a mistake.
On Mon, Nov 14, 2016 at 5:49 PM, Marc<EMAIL_ADDRESS>wrote:

I agree a crash is not great. Your proposal should be fine if it doesn't
implies a runtime cost (besides initial load).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7118#issuecomment-260458165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z28rXhNi8w45Eh-9cs7y4uSKDqr2Lks5q-MlZgaJpZM4Kxtpp
.

Crash (parse error actually) is fine, this is meant to always work.

The app should still crash if the user doesn't handle the null preloaded var/const with the approach in my post.

It would be worse if you mess up the name, it doesn t work and you dont
realize you made a mistake.

With load the user could mess up the name and nobody complained about that, this is the same behavior suggested for preload in this issue. The advantage of nullable preloads is custom behaviour for preload paths not found instead of I can't compile with an invalid path.

If you are not sure whether it should work or not, use load() instead.

Well as I said in first post I'm aware of load, but that method should be less optimal because is 1 load for EACH ready vs a SINGLE preload in a CONST at start of the game.

you can run load in an initializer fine:
var someobj = load(pathtores)
On Mon, Nov 14, 2016 at 7:36 PM, Hearto<EMAIL_ADDRESS>wrote:

Crash (parse error actually) is fine, this is meant to always work.
The app should still crash if the user doesn't handle the null preloaded
var/const with the approach in my post.
It would be worse if you mess up the name, it doesn t work and you dont
realize you made a mistake.
With load the user could mess up the name and nobody complained about
that, this is the same behavior suggested for preload in this issue. The
advantage of nullable preloads is custom behaviour for preload paths not
found instead of I can't compile with an invalid path.
If you are not sure whether it should work or not, use load() instead.
Well as I said in first post I'm aware of load, but that method should be
less optimal because is 1 load for EACH ready vs a SINGLE preload in a
CONST at start of the game.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7118#issuecomment-260485937,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z20rIpdpIMFF5KFK3isQocq_Q0iuZks5q-OJcgaJpZM4Kxtpp
.

#6203 mentions some of the things I ran into with load/preload, might be worth bearing in mind?

Preload is supposed to be a static dependency, if it doesn't exist, it's
the same as a .tscn mentioning an external resource that doesn't exist.. It
should abort as if the game data is incorrect
On 14 November 2016 at 18:30, Juan Linietsky<EMAIL_ADDRESS>wrote:

If you are not sure whether it should work or not, use load() instead.
On Mon, Nov 14, 2016 at 6:29 PM, Juan Linietsky<EMAIL_ADDRESS>wrote:

Crash (parse error actually) is fine, this is meant to always work. It
would be worse if you mess up the name, it doesn t work and you dont
realize you made a mistake.
On Mon, Nov 14, 2016 at 5:49 PM, Marc<EMAIL_ADDRESS>wrote:

I agree a crash is not great. Your proposal should be fine if it doesn't
implies a runtime cost (besides initial load).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/godotengine/godot/issues/7118#
issuecomment-260458165>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF-Z28rXhNi8w45Eh-
9cs7y4uSKDqr2Lks5q-MlZgaJpZM4Kxtpp>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7118#issuecomment-260468804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVmPQfSEFpuuexYxIjcPtFkdtCTlESjks5q-NMHgaJpZM4Kxtpp
.

you can run load in an initializer fine:
var someobj = load(pathtores)

What about CONST values?
At least you can't load in a CONST obj

what does it change for you whether it s a const value or not?
the only difference it makes to gdscript is that it can do compile time
optimization.
On Mon, Nov 14, 2016 at 7:54 PM, Hearto<EMAIL_ADDRESS>wrote:

you can run load in an initializer fine:
var someobj = load(pathtores)
What about CONST values?
At least you can't load in a CONST obj
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7118#issuecomment-260490538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z27RAUX1T4KNMXqNqBN9LNlbP-KeMks5q-Oa-gaJpZM4Kxtpp
.

AFAIK resources are cached, so a second load() will grab the same resource from memory, not load from the filesystem again.

If it does, the resource doesn't have the same ID.

preload expects a const String. If that const String points to an invalid path, that's a bug from whoever wrote the string, and it's normal that the program gives an error.
You can't use preload to load resources dynamically, that's load's job, so it's definitely what you want to use in your use case. It makes no sense to have preload return a null object if passed a bogus path. It should only return a null object if it was called on a valid path but an invalid resource (i.e. it couldn't load the file because it's not a resource Godot knows how to handle), not if the programmer made a typo.

If it does, the resource doesn't have the same ID.

How is that a problem? As long as each ID points to the same allocated memory, that's AFAIK the way it's intended to be. Resources are reference-counted - the allocated memory will live until all references are freed.

Agree with Akien. Also I prefer a compile error than a successful compilation but a hidden bug.

what does it change for you whether it s a const value or not?
the only difference it makes to gdscript is that it can do compile time
optimization.

Well in theory with CONST the value should be executed 1 time for each script and with var the value should be executed for each instance of the script.
Now that sound less optimal but taking in account this reply from @vnen :

AFAIK resources are cached, so a second load() will grab the same resource from memory, not load from the filesystem again.

With that info var xxx = load() should be the same performance wise as const xxx = preload(). Of course if  the cache algorithm isn't limited (something like using a dictionary with a limit of 100 last values)
So this issue could be closed if the performance is the same in both cases.

Well in theory with CONST the value should be executed 1 time for each script and with var the value should be executed for each instance of the script.

That's true, but if it really, really matters, you can make a global singleton holding those variables and doing whatever you want with the resources just once.

@akien-mga Close this?


chore(master): release 2.8.2

:robot: I have created a release beep boop
2.8.2 (2024-10-07)
Performance Improvements

export createResponseProxy function (261606e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq/releases/tag/v2.8.2 :sunflower:


Add the --close-to-tray command line option.

New PR for #69 since the code has changed a lot since.
If the --close-to-tray command line option is set, clicking on the close button won't kill the application, it will only hide the window.

Outside of the typo in the CLI description, this looks good. Please let me know when that is corrected (be sure to squash the PR to 1 commit upon update).

@twolfson : the typo should be fixed.

This has been released in 2.9.0. Thanks for keeping the PR alive =)


Bug in mojo websocket client with big response

Mojolicious version: 7.36
Perl version: 5.22
Operating system: Linux

Steps to reproduce the behavior
If server send big message to client then client generate 1009 error and ioloop generate message.
server
#!/usr/bin/perl
use Mojo::Base -strict;
use Mojolicious::Lite;
websocket '/' => sub {
  shift->on(text => sub {
    my ($c, $text) = @_;
    $c->send({text => '1' x 1_000_000});
  });
};
app->start;

client
#!/usr/bin/perl
use Mojo::Base -strict;
use Mojo::UserAgent;

Mojo::IOLoop->timer(3 => sub {warn '!!!'});

my $ua = Mojo::UserAgent->new;
$ua->websocket('ws://<IP_ADDRESS>:3000/' => sub {
  my ($ua, $tx) = @_;
  say 'WebSocket handshake failed!' and return unless $tx->is_websocket;
  $tx->on(text => sub {
    my ($tx, $text) = @_;
    warn $text;
  });
  $tx->send({text => 'hello'});
});
Mojo::IOLoop->start;

Expected behavior
No warnings
Actual behavior
Warnings
$ perl client.pl
Use of uninitialized value $loop in hash element at /usr/local/share/perl/5.22.1/Mojo/UserAgent.pm line 200.
Mojo::Reactor::EV: I/O watcher failed: Can't call method "remove" on an undefined value at /usr/local/share/perl/5.22.1/Mojo/UserAgent.pm line 276.
!!!
$

Can confirm. Here it is in the form of a test file:
use Mojolicious::Lite;

use Test::More;
use Test::Mojo;

my $send = '1' x 1e5;

websocket '/' => sub { shift->send({text => $send}) };

my $t = Test::Mojo->new;

$t->websocket_ok('/')
  ->message_ok
  ->message_is($send)
  ->finish_ok;

done_testing;

Ah, this is just hitting the max websocket size. I was amazed that such a simple behavior could be missed. http://mojolicious.org/perldoc/Mojo/Transaction/WebSocket#max_websocket_size
@kraih is there a warning/log that I'm not seeing when this level is breached? If not perhaps there could be. Anyway, the reported issue is not a bug, so I'm closing it.

From RFC 6455.
1009 indicates that an endpoint is terminating the connection
      because it has received a message that is too big for it to
      process.

Ah yes, well then that is consistent with the HTTP behaviors. I HAD thought that there was a warning to the log but I just looked it up and indeed it is just an error to the client. https://github.com/kraih/mojo/blob/master/lib/Mojo/Message.pm#L169-L179


Update dependencies

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build was run locally and any changes were pushed
[x] Lint has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.368%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1730

Relevant Lines:
1741

💛  - Coveralls


new handPose video!

In case you want to incorporate anywhere on the site!
https://youtu.be/vfNHdVbE-l4
https://thecodingtrain.com/tracks/ml5js-beginners-guide/ml5/hand-pose
Currently A/B testing three thumbnail designs:

@shiffman Thank you for letting us know! I will add it to the website soon.

@shiffman Sorry for the delay! The tutorial has been posted on the Community page and featured on the Home page! #50


Import Wegue as a module?

Hi Wegue team,
I am interested in using this package as a module in a NuxtJs app. To do so, I need to create a plugin that imports the required components/configs from Wegue... but I am currently struggling with:

which components should I import;
how to avoid $appConfig since in my case I want a configuration per instance.

Hi @ntma, thanks for your interest in Wegue. I fear at the moment it is not possible, what you are planning to do. There is no importable component package yet. We plan to separate the components from the template application in a mid-term change set. Hereby we want to decouple the components from the application configuration. So plans are there, but not implemented yet.

Ah, awesome! I'll look forward to it!
In the meanwhile, is there a roadmap settled for the development of Wegue that can be shared?

No, there is no official roadmap so far. But we should do that, to get things more transparent. The issues give us some kind of backlog and currently the mid- and long-term things are more ideas evolving in talks between the developers.


Edge numbering

Depends on #32 for CI support
This adds support for handling edge numbers as described in Matsen et al. We do not handle edge labels. Edge numbers are necessary to handle placement information from jplace, which will come in a subsequent PR.

Okay, this should be good. There is a 20% performance degradation in parsing, however it's unclear if that impacts anything right now and is okay to table for the time being as parsing is still rather fast.

Looks good to me!

thanks!!


I think this step can work with these project types too :)

Hey @viktorbenei, thanks for contribution!

Thanks for the step! ;)


[ML category based PROJECT PROPOSAL]

Project Request
Developing a model to predict early heart disease prediction by doing a comparitive analysis of different machine learning models to predcit heart disease with highest accuracy on defined and most important attributes

Field
Description

About
Early Heart disease prediction using ML

Github
poorvika11

Email
<EMAIL_ADDRESS>

Label
Project Request

https://github.com/poorvika11

Define You

GSSOC Participant
Contributor

Early Heart Disease Prediction

Description
The project involved analysis of the heart disease patient dataset with proper data processing. Then, different models will be trained and predictions will be made with different algorithms KNN, Decision Tree, Random Forest,SVM,Logistic Regression etc. Variety of Machine Learning algorithms implemented in Python to predict the presence of heart disease in a patient. This is a classification problem, with input features as a variety of parameters, and the target variable as a binary variable, predicting whether heart disease is present or not.
Scope
Objectives:

Implement a robust and efficient heart disease prediction.
Enable high accuracy model using comparitive analysisof all machine learning models.

Deliverables

A trained model capable of predciting disease accurately.
Well-documented guidelines, including dataset preparation, training, inference,exploratory data analysis and any specific requirements.
Models predicting using different algorithms KNN, Decision Tree, Random Forest,SVM,Logistic Regression etc.

Timeline
Start Date: when assigned
End Date: 10 August

Hello, I'm a GSSoC'23 contributor. I would like to work on this project. Can you please assign me. I will implement a robust prediction and enable high accuracy.

I'm a GSSoC'23 contributor. Please, assign the issue to me.

@poorvika11  I have assigned this particular project to you under GSSOC 23.
Will you be able to manage the project alone or would you like to collaborate with other contributors
All the best contributing
if you have any doubts on the project structure feel free to contact me

Hello, I'm a GSSoC'23 contributor. I love  to work on this project. if there is any chance I can collaborate .

@adithya-s-k please label it with level label also. Highly requested to you to do this


I got a issues when build the target

When I trying to build the target, I got many warning and errors like this:

ld: warning: ignoring file /Users/Church/Caffe2-iOS/src/caffe2-ios/caffe2-ios/opencv2.framework/opencv2, file was built for unsupported file format ( 0x76 0x65 0x72 0x73 0x69 0x6F 0x6E 0x20 0x68 0x74 0x74 0x70 0x73 0x3A 0x2F 0x2F ) which is not the architecture being linked (armv7): /Users/Church/Caffe2-iOS/src/caffe2-ios/caffe2-ios/opencv2.framework/opencv2

The opencv framework was ignored, it seems two kind of architectures were not matched, but I'm not sure what the real problem is, did I do something wrong?
Thanks for your help anyway.

@Kyuuki93  I assume this is because of the new commit I did two days ago. I updated the opencv2.framework with a fresh built so that it's pure static and compatible without problem for archiving.
However, the new opencv2.framework contains a file called opencv2, which is around 130MB, way too large to fit a git commit. Therefore, I used git lfs to store big files, including all pb models. I think this waring is because of cloning did not fetch the files stored in lfs hosting.
Check the following:

You have Git lfs installed
Do a fresh clone again
If still problematic, try this

Also make sure that you are building target against an actual device instead of a simulator.
I will update the readme to include the content above.

@Kyuuki93 I update the document for GIT LFS: https://github.com/KleinYuan/Caffe2-iOS#lfs-clone
Since this is implementing issue, I will close it and feel free to reopen it if you still meet this problem.


staging mgr: support nil values

Solves #1046

This change is

Codecov Report

Merging #1062 (25ca0a9) into master (11b432d) will decrease coverage by 0.01%.
The diff coverage is 94.44%.

@@            Coverage Diff             @@
##           master    #1062      +/-   ##
==========================================
- Coverage   46.61%   46.60%   -0.02%
==========================================
  Files         158      158
  Lines       12718    12726       +8
==========================================
+ Hits         5929     5931       +2
- Misses       6036     6043       +7
+ Partials      753      752       -1

Impacted Files
Coverage Δ

graveler/graveler.go
33.17% <0.00%> (ø)

graveler/staging.go
96.55% <100.00%> (+0.32%)
:arrow_up:

graveler/staging_iterator.go
79.06% <100.00%> (+1.56%)
:arrow_up:

config/logger.go
64.28% <0.00%> (-10.72%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
81.53% <0.00%> (-3.08%)
:arrow_down:

stats/collector.go
59.09% <0.00%> (-2.28%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
66.66% <0.00%> (+7.40%)
:arrow_up:

Continue to review full report at Codecov.

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


Open links in about page release notes in external browser

Branch : Master
Steps to reproduce:

In the Mongotron menu click 'About Mongotron'
In the release notes click on a Github link

You should see that the Github page gets loaded in Electron. We should open up these types of links externally using https://github.com/atom/electron/blob/master/docs/api/shell.md#shellopenexternalurl.
Could wrap this up in Angular directive,  but for rendering Markdown in the About page we need to somehow parse links from the Markdown and convert them.

Fixed in https://github.com/officert/mongotron/commit/be6b810419a998b7e3f650eb335420046715f5aa


Small Bug? Palette hover doesn't show first  of help if comments left in place

The template node has some <-- --> comments at the top of the help section. If these are left in, the first  does not actually show up when hovering over the node in the palette.
A small thing. You could update the documentation instead of fix probably.

Thanks for spotting this. Fixed.


Support for multiple SLOs in local filesystem

In the context of running locally, storing the SLO definitions in a file it seems I currently have to create one file for each SLO that I want to define. IOW: I'd love to see support for multiple ServiceLevelObjective resources separated by --- (like the case in the Kubernetes API) for the local filesystem implementation.

I've looked into this. It seems we need to use the other YAML libs to unmarshal.
However, with that one, I couldn't make the multi stream files work yet. I'll look into it again, when time permits.

Had to do this exact thing, hacky patch I came up with involved unmarshalling and marshalling each YAML document before calling yaml.UnmarshalStrict.
func objectivesFromFile(file string) ([]v1alpha1.ServiceLevelObjective, error) {
	b, err := os.ReadFile(file)
	if err != nil {
		return nil, fmt.Errorf("failed to read file %q: %w", file, err)
	}

	var objectives []v1alpha1.ServiceLevelObjective

	dec := yaml2.NewDecoder(bytes.NewReader(b))
	dec.SetStrict(true)

	for {
		var yamlObj any
		if err := dec.Decode(&yamlObj); err != nil {
			if err == io.EOF {
				break
			}

			return nil, fmt.Errorf("failed to unmarshal objective for roundtrip %q: %w", file, err)
		}

		buf, err := yaml2.Marshal(yamlObj)
		if err != nil {
			return nil, fmt.Errorf("failed to marshal objective for roundtrip %q: %w", file, err)
		}

		var objective v1alpha1.ServiceLevelObjective
		if err := yaml.UnmarshalStrict(buf, &objective); err != nil {
			return nil, fmt.Errorf("failed to unmarshal objective %q: %w", file, err)
		}

		objectives = append(objectives, objective)
	}

	return objectives, nil
}

yaml2 is just sigs.k8s.io/yaml/goyaml.v2


Added AllowedPattern for RemoteAccessCidr parameter

Issue #, if available:
Description of changes:
Added an AllowedPattern to check the RemoteAccessCidr parameter. It's a required parameter otherwise it will cause an error in CloudFormation
Embedded stack arn:aws:cloudformation:us-east-1:816333157034:stack/vmware-tanzu-application-platform-1-2-ExistingVpcStack-7UAE0RNJB7RV/be9c4d20-0c1e-11ed-b0ef-0ebb957d5521 was not successfully created: The following resource(s) failed to create: [LinuxBastionSshIngressRule, WindowsBastionRdpIngressRule, EKSQSStack].
As remote CIDR is unique to each customer, we cannot provide a secure default without opening remote access to the world.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/do-e2e-tests

Merging per discussion with @satya-dillikar. Thanks @spagno!

Thanks, @spagno for taking care of this.  Thanks @tlindsay42 for merging and push this to AWS QS S3 buckets also.


create skbio.sequence.stats and initially populate with sequence distance metrics

This will be where we store sequence-specific statistics. Two initial functions that we'll include here will be hamming and kmer_distance.

[ ] hamming will be a wrapper around scipy.spatial.distance.hamming, which takes two skbio.Sequence objects, confirms that they are the same length as raises an informative error if not, converts them into input to scipy.spatial.distance.hamming (i.e., by accessing the sequence attribute), and returns the result. This will let us remove the metric-specific check for sequence length in skbio.Sequence.distance.

[ ] kmer_distance will take two skbio.Sequence objects, k (the kmer length), and probably a flag indicating whether the metric should be qualitative (presence/absence of kmers only) or quantitative (compares abundances of kmers), and return the fraction of unique kmers between the pair of sequences.

skbio.Sequence should then be updated to support these functions, and all metric-specific error checking should be removed from that method.

:+1:

@Kleptobismol are you interested in working on this?

Yes.

@gregcaporaso the analysis that kmer_distance performs appears to be qualitative--finding only how many unique kmers exist. Should this be the default functionality as opposed to quantitative? Also, I have no problem writing tests for this ported code, but I cant seem to find any tests in your code. Are there any? Thanks!