Consenter error when calling peer channel fetch

Bug
The org1.cello.com organization has a peer node and an orderer node, forming the containers order.cello.com and peer.org1.cello.com
When I call "peer channel fetch",  the Orderer is unable to service the Peer's request, and a SERVICE_UNAVAILABLE error is reported.
Logs
Orderer Container
It shows that "Rejecting deliver request for ... because of consenter error".
2024-11-08 19:43:58 Store data in HLF_NODE_MSP to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/config.yaml
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/keystore/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/admincerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/tlscacerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/cacerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/signcerts/
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/keystore/priv_sk
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/tlscacerts/tlsca.cello.com-cert.pem
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/cacerts/ca.cello.com-cert.pem
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/signcerts/orderer.cello.com-cert.pem
2024-11-08 19:43:58 msp
2024-11-08 19:43:58 Store data in HLF_NODE_TLS to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/server.key
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/ca.crt
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/server.crt
2024-11-08 19:43:58 msp  tls
2024-11-08 19:43:58 Store data in HLF_NODE_PEER_CONFIG to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/orderer.yaml
2024-11-08 19:43:58 msp  orderer.yaml  tls
2024-11-08 19:43:58 Store data in HLF_NODE_ORDERER_CONFIG to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/orderer.yaml
2024-11-08 19:43:58 msp  orderer.yaml  tls
2024-11-08 19:43:58 Run orderer
2024-11-08 19:43:58 2024-11-09 03:43:58.874 UTC 0001 INFO [localconfig] completeInitialization -> Kafka.Version unset, setting to <IP_ADDRESS>
2024-11-08 19:43:58 2024-11-09 03:43:58.874 UTC 0002 INFO [orderer.common.server] prettyPrintStruct -> Orderer config values:
2024-11-08 19:43:58 General.ListenAddress = "<IP_ADDRESS>"
2024-11-08 19:43:58 General.ListenPort = 7050
2024-11-08 19:43:58 General.TLS.Enabled = true
2024-11-08 19:43:58 General.TLS.PrivateKey = "/etc/hyperledger/fabric/tls/server.key"
2024-11-08 19:43:58 General.TLS.Certificate = "/etc/hyperledger/fabric/tls/server.crt"
2024-11-08 19:43:58 General.TLS.RootCAs = [/etc/hyperledger/fabric/tls/ca.crt]
2024-11-08 19:43:58 General.TLS.ClientAuthRequired = false
2024-11-08 19:43:58 General.TLS.ClientRootCAs = []
2024-11-08 19:43:58 General.TLS.TLSHandshakeTimeShift = 0s
2024-11-08 19:43:58 General.Cluster.ListenAddress = ""
2024-11-08 19:43:58 General.Cluster.ListenPort = 0
2024-11-08 19:43:58 General.Cluster.ServerCertificate = ""
2024-11-08 19:43:58 General.Cluster.ServerPrivateKey = ""
2024-11-08 19:43:58 General.Cluster.ClientCertificate = "/etc/hyperledger/fabric/tls/server.crt"
2024-11-08 19:43:58 General.Cluster.ClientPrivateKey = "/etc/hyperledger/fabric/tls/server.key"
2024-11-08 19:43:58 General.Cluster.RootCAs = [/etc/hyperledger/fabric/tls/ca.crt]
2024-11-08 19:43:58 General.Cluster.DialTimeout = 5s
2024-11-08 19:43:58 General.Cluster.RPCTimeout = 7s
2024-11-08 19:43:58 General.Cluster.ReplicationBufferSize = 20971520
2024-11-08 19:43:58 General.Cluster.ReplicationPullTimeout = 5s
2024-11-08 19:43:58 General.Cluster.ReplicationRetryTimeout = 5s
2024-11-08 19:43:58 General.Cluster.ReplicationBackgroundRefreshInterval = 5m0s
2024-11-08 19:43:58 General.Cluster.ReplicationMaxRetries = 12
2024-11-08 19:43:58 General.Cluster.SendBufferSize = 100
2024-11-08 19:43:58 General.Cluster.CertExpirationWarningThreshold = 168h0m0s
2024-11-08 19:43:58 General.Cluster.TLSHandshakeTimeShift = 0s
2024-11-08 19:43:58 General.Keepalive.ServerMinInterval = 1m0s
2024-11-08 19:43:58 General.Keepalive.ServerInterval = 2h0m0s
2024-11-08 19:43:58 General.Keepalive.ServerTimeout = 20s
2024-11-08 19:43:58 General.ConnectionTimeout = 0s
2024-11-08 19:43:58 General.GenesisMethod = ""
2024-11-08 19:43:58 General.GenesisFile = ""
2024-11-08 19:43:58 General.BootstrapMethod = "none"
2024-11-08 19:43:58 General.BootstrapFile = "/etc/hyperledger/fabric/genesisblock"
2024-11-08 19:43:58 General.Profile.Enabled = false
2024-11-08 19:43:58 General.Profile.Address = "<IP_ADDRESS>:6060"
2024-11-08 19:43:58 General.LocalMSPDir = "/etc/hyperledger/fabric/msp"
2024-11-08 19:43:58 General.LocalMSPID = "OrdererMSP"
2024-11-08 19:43:58 General.BCCSP.Default = "SW"
2024-11-08 19:43:58 General.BCCSP.SW.Security = 256
2024-11-08 19:43:58 General.BCCSP.SW.Hash = "SHA2"
2024-11-08 19:43:58 General.BCCSP.SW.FileKeystore.KeyStorePath = ""
2024-11-08 19:43:58 General.Authentication.TimeWindow = 15m0s
2024-11-08 19:43:58 General.Authentication.NoExpirationChecks = false
2024-11-08 19:43:58 General.MaxRecvMsgSize = 104857600
2024-11-08 19:43:58 General.MaxSendMsgSize = 104857600
2024-11-08 19:43:58 FileLedger.Location = "/var/hyperledger/production/orderer"
2024-11-08 19:43:58 FileLedger.Prefix = ""
2024-11-08 19:43:58 Kafka.Retry.ShortInterval = 5s
2024-11-08 19:43:58 Kafka.Retry.ShortTotal = 10m0s
2024-11-08 19:43:58 Kafka.Retry.LongInterval = 5m0s
2024-11-08 19:43:58 Kafka.Retry.LongTotal = 12h0m0s
2024-11-08 19:43:58 Kafka.Retry.NetworkTimeouts.DialTimeout = 10s
2024-11-08 19:43:58 Kafka.Retry.NetworkTimeouts.ReadTimeout = 10s
2024-11-08 19:43:58 Kafka.Retry.NetworkTimeouts.WriteTimeout = 10s
2024-11-08 19:43:58 Kafka.Retry.Metadata.RetryMax = 3
2024-11-08 19:43:58 Kafka.Retry.Metadata.RetryBackoff = 250ms
2024-11-08 19:43:58 Kafka.Retry.Producer.RetryMax = 3
2024-11-08 19:43:58 Kafka.Retry.Producer.RetryBackoff = 100ms
2024-11-08 19:43:58 Kafka.Retry.Consumer.RetryBackoff = 2s
2024-11-08 19:43:58 Kafka.Verbose = false
2024-11-08 19:43:58 Kafka.Version = <IP_ADDRESS>
2024-11-08 19:43:58 Kafka.TLS.Enabled = false
2024-11-08 19:43:58 Kafka.TLS.PrivateKey = ""
2024-11-08 19:43:58 Kafka.TLS.Certificate = ""
2024-11-08 19:43:58 Kafka.TLS.RootCAs = []
2024-11-08 19:43:58 Kafka.TLS.ClientAuthRequired = false
2024-11-08 19:43:58 Kafka.TLS.ClientRootCAs = []
2024-11-08 19:43:58 Kafka.TLS.TLSHandshakeTimeShift = 0s
2024-11-08 19:43:58 Kafka.SASLPlain.Enabled = false
2024-11-08 19:43:58 Kafka.SASLPlain.User = ""
2024-11-08 19:43:58 Kafka.SASLPlain.Password = ""
2024-11-08 19:43:58 Kafka.Topic.ReplicationFactor = 3
2024-11-08 19:43:58 Debug.BroadcastTraceDir = ""
2024-11-08 19:43:58 Debug.DeliverTraceDir = ""
2024-11-08 19:43:58 Consensus = map[SnapDir:/var/hyperledger/production/orderer/etcdraft/snapshot WALDir:/var/hyperledger/production/orderer/etcdraft/wal]
2024-11-08 19:43:58 Operations.ListenAddress = "orderer.cello.com:9443"
2024-11-08 19:43:58 Operations.TLS.Enabled = false
2024-11-08 19:43:58 Operations.TLS.PrivateKey = ""
2024-11-08 19:43:58 Operations.TLS.Certificate = ""
2024-11-08 19:43:58 Operations.TLS.RootCAs = []
2024-11-08 19:43:58 Operations.TLS.ClientAuthRequired = false
2024-11-08 19:43:58 Operations.TLS.ClientRootCAs = []
2024-11-08 19:43:58 Operations.TLS.TLSHandshakeTimeShift = 0s
2024-11-08 19:43:58 Metrics.Provider = "prometheus"
2024-11-08 19:43:58 Metrics.Statsd.Network = "udp"
2024-11-08 19:43:58 Metrics.Statsd.Address = "<IP_ADDRESS>:8125"
2024-11-08 19:43:58 Metrics.Statsd.WriteInterval = 30s
2024-11-08 19:43:58 Metrics.Statsd.Prefix = ""
2024-11-08 19:43:58 ChannelParticipation.Enabled = true
2024-11-08 19:43:58 ChannelParticipation.MaxRequestBodySize = 1048576
2024-11-08 19:43:58 Admin.ListenAddress = "<IP_ADDRESS>:7053"
2024-11-08 19:43:58 Admin.TLS.Enabled = true
2024-11-08 19:43:58 Admin.TLS.PrivateKey = "/etc/hyperledger/fabric/tls/server.key"
2024-11-08 19:43:58 Admin.TLS.Certificate = "/etc/hyperledger/fabric/tls/server.crt"
2024-11-08 19:43:58 Admin.TLS.RootCAs = [/etc/hyperledger/fabric/tls/ca.crt]
2024-11-08 19:43:58 Admin.TLS.ClientAuthRequired = true
2024-11-08 19:43:58 Admin.TLS.ClientRootCAs = [/etc/hyperledger/fabric/tls/ca.crt]
2024-11-08 19:43:58 Admin.TLS.TLSHandshakeTimeShift = 0s
2024-11-08 19:43:58 2024-11-09 03:43:58.883 UTC 0003 INFO [orderer.common.server] initializeServerConfig -> Starting orderer with TLS enabled
2024-11-08 19:43:58 2024-11-09 03:43:58.894 UTC 0004 INFO [blkstorage] NewProvider -> Creating new file ledger directory at /var/hyperledger/production/orderer/chains
2024-11-08 19:43:58 2024-11-09 03:43:58.897 UTC 0005 INFO [orderer.commmon.multichannel] InitJoinBlockFileRepo -> Channel Participation API enabled, registrar initializing with file repo /var/hyperledger/production/orderer/pendingops
2024-11-08 19:43:58 2024-11-09 03:43:58.901 UTC 0006 INFO [orderer.common.server] Main -> Starting without a system channel
2024-11-08 19:43:58 2024-11-09 03:43:58.901 UTC 0007 INFO [orderer.common.server] Main -> Setting up cluster
2024-11-08 19:43:58 2024-11-09 03:43:58.902 UTC 0008 INFO [orderer.common.server] reuseListener -> Cluster listener is not configured, defaulting to use the general listener on port 7050
2024-11-08 19:43:58 2024-11-09 03:43:58.903 UTC 0009 INFO [certmonitor] trackCertExpiration -> The enrollment certificate will expire on 2034-11-07 03:39:00 +0000 UTC
2024-11-08 19:43:58 2024-11-09 03:43:58.903 UTC 000a INFO [certmonitor] trackCertExpiration -> The server TLS certificate will expire on 2034-11-07 03:39:00 +0000 UTC
2024-11-08 19:43:58 2024-11-09 03:43:58.903 UTC 000b INFO [certmonitor] trackCertExpiration -> The client TLS certificate will expire on 2034-11-07 03:39:00 +0000 UTC
2024-11-08 19:43:58 2024-11-09 03:43:58.903 UTC 000c INFO [orderer.commmon.multichannel] InitJoinBlockFileRepo -> Channel Participation API enabled, registrar initializing with file repo /var/hyperledger/production/orderer/pendingops
2024-11-08 19:43:58 2024-11-09 03:43:58.906 UTC 000d INFO [orderer.commmon.multichannel] startChannels -> Registrar initializing without a system channel, number of application channels: 0, with 0 consensus.Chain(s) and 0 follower.Chain(s)
2024-11-08 19:43:58 2024-11-09 03:43:58.909 UTC 000e INFO [orderer.common.server] Main -> Starting orderer:
2024-11-08 19:43:58  Version: 2.5.10
2024-11-08 19:43:58  Commit SHA: development build
2024-11-08 19:43:58  Go version: go1.23.1
2024-11-08 19:43:58  OS/Arch: linux/arm64
2024-11-08 19:43:58 2024-11-09 03:43:58.909 UTC 000f INFO [orderer.common.server] Main -> Beginning to serve requests
2024-11-08 19:44:21 2024-11-09 03:44:21.763 UTC 0010 INFO [blkstorage] newBlockfileMgr -> Getting block information from block storage
2024-11-08 19:44:21 2024-11-09 03:44:21.767 UTC 0011 INFO [orderer.consensus.etcdraft] HandleChain -> EvictionSuspicion not set, defaulting to 10m0s
2024-11-08 19:44:21 2024-11-09 03:44:21.768 UTC 0012 INFO [orderer.consensus.etcdraft] HandleChain -> Without system channel: after eviction Registrar.SwitchToFollower will be called
2024-11-08 19:44:21 2024-11-09 03:44:21.768 UTC 0013 INFO [orderer.consensus.etcdraft] createOrReadWAL -> No WAL data found, creating new WAL at path '/var/hyperledger/production/orderer/etcdraft/wal/channel' channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.796 UTC 0014 INFO [orderer.commmon.multichannel] createAsMember -> Joining channel: {channel  consenter active 1}
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 0015 INFO [orderer.consensus.etcdraft] Start -> Starting Raft node channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 0016 INFO [orderer.common.cluster] Configure -> Entering, channel: channel, nodes: []
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 0017 INFO [orderer.common.cluster] Configure -> Exiting
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 0018 INFO [orderer.consensus.etcdraft] start -> Starting raft node as part of a new channel channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 0019 INFO [orderer.consensus.etcdraft] switchToConfig -> 1 switched to configuration voters=() channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 001a INFO [orderer.consensus.etcdraft] becomeFollower -> 1 became follower at term 0 channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 001b INFO [orderer.consensus.etcdraft] newRaft -> newRaft 1 [peers: [], term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0] channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 001c INFO [orderer.consensus.etcdraft] becomeFollower -> 1 became follower at term 1 channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.804 UTC 001d INFO [orderer.consensus.etcdraft] switchToConfig -> 1 switched to configuration voters=(1) channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.805 UTC 001e INFO [orderer.consensus.etcdraft] run -> This node is picked to start campaign channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.813 UTC 001f INFO [orderer.consensus.etcdraft] switchToConfig -> 1 switched to configuration voters=(1) channel=channel node=1
2024-11-08 19:44:21 2024-11-09 03:44:21.813 UTC 0020 INFO [orderer.consensus.etcdraft] apply -> Applied config change to add node 1, current nodes in channel: [1] channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.145 UTC 0021 WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:53066 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.146 UTC 0022 INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:53066 grpc.code=OK grpc.call_duration=549.291µs
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0023 WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:53080 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0024 INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:53080 grpc.code=OK grpc.call_duration=169.375µs
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 0025 WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:53096 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 0026 INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:53096 grpc.code=OK grpc.call_duration=121.334µs
2024-11-08 19:44:22 2024-11-09 03:44:22.407 UTC 0027 WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:39968 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.407 UTC 0028 INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:39968 grpc.code=OK grpc.call_duration=3.103625ms
2024-11-08 19:44:22 2024-11-09 03:44:22.521 UTC 0029 WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:53098 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.521 UTC 002a INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:53098 grpc.code=OK grpc.call_duration=182.25µs
2024-11-08 19:44:22 2024-11-09 03:44:22.702 UTC 002b WARN [common.deliver] deliverBlocks -> [channel: channel] Rejecting deliver request for <IP_ADDRESS>:53110 because of consenter error
2024-11-08 19:44:22 2024-11-09 03:44:22.702 UTC 002c INFO [comm.grpc.server] 1 -> streaming call completed grpc.service=orderer.AtomicBroadcast grpc.method=Deliver grpc.peer_address=<IP_ADDRESS>:53110 grpc.code=OK grpc.call_duration=452.375µs
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 002d INFO [orderer.consensus.etcdraft] hup -> 1 is starting a new election at term 1 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 002e INFO [orderer.consensus.etcdraft] becomePreCandidate -> 1 became pre-candidate at term 1 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 002f INFO [orderer.consensus.etcdraft] poll -> 1 received MsgPreVoteResp from 1 at term 1 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 0030 INFO [orderer.consensus.etcdraft] becomeCandidate -> 1 became candidate at term 2 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 0031 INFO [orderer.consensus.etcdraft] poll -> 1 received MsgVoteResp from 1 at term 2 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 0032 INFO [orderer.consensus.etcdraft] becomeLeader -> 1 became leader at term 2 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.807 UTC 0033 INFO [orderer.consensus.etcdraft] run -> raft.node: 1 elected leader 1 at term 2 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.809 UTC 0034 INFO [orderer.consensus.etcdraft] run -> Leader 1 is present, quit campaign channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.809 UTC 0035 INFO [orderer.consensus.etcdraft] run -> Raft leader changed: 0 -> 1 channel=channel node=1
2024-11-08 19:44:22 2024-11-09 03:44:22.809 UTC 0036 INFO [orderer.consensus.etcdraft] run -> Start accepting requests as Raft leader at block [0] channel=channel node=1

Peer Container
It shows that " Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE".
2024-11-08 19:43:58 Store data in HLF_NODE_MSP to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/config.yaml
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/keystore/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/admincerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/tlscacerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/cacerts/
2024-11-08 19:43:58    creating: /etc/hyperledger/fabric/msp/signcerts/
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/keystore/priv_sk
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/tlscacerts/tlsca.org1.cello.com-cert.pem
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/cacerts/ca.org1.cello.com-cert.pem
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/msp/signcerts/peer.org1.cello.com-cert.pem
2024-11-08 19:43:58 msp
2024-11-08 19:43:58 Store data in HLF_NODE_TLS to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/server.key
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/ca.crt
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/tls/server.crt
2024-11-08 19:43:58 msp  tls
2024-11-08 19:43:58 Store data in HLF_NODE_PEER_CONFIG to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/core.yaml
2024-11-08 19:43:58 core.yaml  msptls
2024-11-08 19:43:58 Store data in HLF_NODE_ORDERER_CONFIG to /etc/hyperledger/fabric
2024-11-08 19:43:58 Archive:  /tmp/1.zip
2024-11-08 19:43:58  extracting: /etc/hyperledger/fabric/core.yaml
2024-11-08 19:43:58 core.yaml  msptls
2024-11-08 19:43:58 Run peer node start
2024-11-08 19:43:58 2024-11-09 03:43:58.886 UTC 0001 INFO [nodeCmd] serve -> Starting peer:
2024-11-08 19:43:58  Version: 2.5.10
2024-11-08 19:43:58  Commit SHA: development build
2024-11-08 19:43:58  Go version: go1.23.1
2024-11-08 19:43:58  OS/Arch: linux/arm64
2024-11-08 19:43:58  Chaincode:
2024-11-08 19:43:58   Base Docker Label: org.hyperledger.fabric
2024-11-08 19:43:58   Docker Namespace: hyperledger
2024-11-08 19:43:58 2024-11-09 03:43:58.887 UTC 0002 INFO [nodeCmd] serve -> Peer config with combined core.yaml settings and environment variable overrides:
2024-11-08 19:43:58 chaincode:
2024-11-08 19:43:58   builder: $(DOCKER_NS)/fabric-ccenv:$(TWO_DIGIT_VERSION)
2024-11-08 19:43:58   executetimeout: 30s
2024-11-08 19:43:58   externalbuilders:
2024-11-08 19:43:58   - name: ccaas_builder
2024-11-08 19:43:58     path: /opt/hyperledger/ccaas_builder
2024-11-08 19:43:58     propagateEnvironment:
2024-11-08 19:43:58     - CHAINCODE_AS_A_SERVICE_BUILDER_CONFIG
2024-11-08 19:43:58   golang:
2024-11-08 19:43:58     dynamiclink: false
2024-11-08 19:43:58     runtime: $(DOCKER_NS)/fabric-baseos:$(TWO_DIGIT_VERSION)
2024-11-08 19:43:58   installtimeout: 300s
2024-11-08 19:43:58   java:
2024-11-08 19:43:58     runtime: $(DOCKER_NS)/fabric-javaenv:$(TWO_DIGIT_VERSION)
2024-11-08 19:43:58   keepalive: 0
2024-11-08 19:43:58   logging:
2024-11-08 19:43:58     format: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc}
2024-11-08 19:43:58       -> %{level:.4s} %{id:03x}%{color:reset} %{message}'
2024-11-08 19:43:58     level: info
2024-11-08 19:43:58     shim: warning
2024-11-08 19:43:58   mode: net
2024-11-08 19:43:58   node:
2024-11-08 19:43:58     runtime: $(DOCKER_NS)/fabric-nodeenv:$(TWO_DIGIT_VERSION)
2024-11-08 19:43:58   pull: false
2024-11-08 19:43:58   startuptimeout: 300s
2024-11-08 19:43:58   system:
2024-11-08 19:43:58     _lifecycle: enable
2024-11-08 19:43:58     cscc: enable
2024-11-08 19:43:58     lscc: enable
2024-11-08 19:43:58     qscc: enable
2024-11-08 19:43:58 ledger:
2024-11-08 19:43:58   history:
2024-11-08 19:43:58     enablehistorydatabase: true
2024-11-08 19:43:58   pvtdatastore:
2024-11-08 19:43:58     collelgprocdbbatchesinterval: 1000
2024-11-08 19:43:58     collelgprocmaxdbbatchsize: 5000
2024-11-08 19:43:58     deprioritizeddatareconcilerinterval: 60m
2024-11-08 19:43:58     purgedkeyauditlogging: true
2024-11-08 19:43:58     purgeinterval: 100
2024-11-08 19:43:58   snapshots:
2024-11-08 19:43:58     rootdir: /var/hyperledger/production/snapshots
2024-11-08 19:43:58   state:
2024-11-08 19:43:58     couchdbconfig:
2024-11-08 19:43:58       cachesize: 64
2024-11-08 19:43:58       couchdbaddress: <IP_ADDRESS>:5984
2024-11-08 19:43:58       createglobalchangesdb: false
2024-11-08 19:43:58       internalquerylimit: 1000
2024-11-08 19:43:58       maxbatchupdatesize: 1000
2024-11-08 19:43:58       maxretries: 3
2024-11-08 19:43:58       maxretriesonstartup: 10
2024-11-08 19:43:58       requesttimeout: 35s
2024-11-08 19:43:58     statedatabase: goleveldb
2024-11-08 19:43:58     totalquerylimit: 100000
2024-11-08 19:43:58 logging_level: ""
2024-11-08 19:43:58 metrics:
2024-11-08 19:43:58   provider: prometheus
2024-11-08 19:43:58   statsd:
2024-11-08 19:43:58     address: <IP_ADDRESS>:8125
2024-11-08 19:43:58     network: udp
2024-11-08 19:43:58     writeinterval: 10s
2024-11-08 19:43:58 operations:
2024-11-08 19:43:58   listenaddress: peer.org1.cello.com:9444
2024-11-08 19:43:58   tls:
2024-11-08 19:43:58     clientauthrequired: false
2024-11-08 19:43:58     clientrootcas:
2024-11-08 19:43:58       files: []
2024-11-08 19:43:58     enabled: false
2024-11-08 19:43:58 peer:
2024-11-08 19:43:58   address: peer.org1.cello.com:7051
2024-11-08 19:43:58   addressautodetect: false
2024-11-08 19:43:58   authentication:
2024-11-08 19:43:58     timewindow: 15m
2024-11-08 19:43:58   bccsp:
2024-11-08 19:43:58     default: SW
2024-11-08 19:43:58     sw:
2024-11-08 19:43:58       hash: SHA2
2024-11-08 19:43:58       security: 256
2024-11-08 19:43:58   client:
2024-11-08 19:43:58     conntimeout: 3s
2024-11-08 19:43:58   deliveryclient:
2024-11-08 19:43:58     blockgossipenabled: true
2024-11-08 19:43:58     conntimeout: 3s
2024-11-08 19:43:58     reconnectbackoffthreshold: 3600s
2024-11-08 19:43:58     reconnecttotaltimethreshold: 3600s
2024-11-08 19:43:58   discovery:
2024-11-08 19:43:58     authcacheenabled: true
2024-11-08 19:43:58     authcachemaxsize: 1000
2024-11-08 19:43:58     authcachepurgeretentionratio: 0.75
2024-11-08 19:43:58     enabled: true
2024-11-08 19:43:58     orgmembersallowedaccess: false
2024-11-08 19:43:58   filesystempath: /var/hyperledger/production
2024-11-08 19:43:58   gateway:
2024-11-08 19:43:58     broadcasttimeout: 30s
2024-11-08 19:43:58     dialtimeout: 2m
2024-11-08 19:43:58     enabled: true
2024-11-08 19:43:58     endorsementtimeout: 30s
2024-11-08 19:43:58   gossip:
2024-11-08 19:43:58     aliveexpirationtimeout: 25s
2024-11-08 19:43:58     alivetimeinterval: 5s
2024-11-08 19:43:58     bootstrap: peer.org1.cello.com:7051
2024-11-08 19:43:58     conntimeout: 2s
2024-11-08 19:43:58     dialtimeout: 3s
2024-11-08 19:43:58     digestwaittime: 1s
2024-11-08 19:43:58     election:
2024-11-08 19:43:58       leaderalivethreshold: 10s
2024-11-08 19:43:58       leaderelectionduration: 5s
2024-11-08 19:43:58       membershipsampleinterval: 1s
2024-11-08 19:43:58       startupgraceperiod: 15s
2024-11-08 19:43:58     externalendpoint: peer.org1.cello.com:7051
2024-11-08 19:43:58     maxblockcounttostore: 10
2024-11-08 19:43:58     maxconnectionattempts: 120
2024-11-08 19:43:58     maxpropagationburstlatency: 10ms
2024-11-08 19:43:58     maxpropagationburstsize: 10
2024-11-08 19:43:58     membershiptrackerinterval: 5s
2024-11-08 19:43:58     msgexpirationfactor: 20
2024-11-08 19:43:58     orgleader: true
2024-11-08 19:43:58     propagateiterations: 1
2024-11-08 19:43:58     propagatepeernum: 3
2024-11-08 19:43:58     publishcertperiod: 10s
2024-11-08 19:43:58     publishstateinfointerval: 4s
2024-11-08 19:43:58     pullinterval: 4s
2024-11-08 19:43:58     pullpeernum: 3
2024-11-08 19:43:58     pvtdata:
2024-11-08 19:43:58       btlpullmargin: 10
2024-11-08 19:43:58       implicitcollectiondisseminationpolicy:
2024-11-08 19:43:58         maxpeercount: 1
2024-11-08 19:43:58         requiredpeercount: 0
2024-11-08 19:43:58       pullretrythreshold: 60s
2024-11-08 19:43:58       pushacktimeout: 3s
2024-11-08 19:43:58       reconcilebatchsize: 10
2024-11-08 19:43:58       reconcilesleepinterval: 1m
2024-11-08 19:43:58       reconciliationenabled: true
2024-11-08 19:43:58       skippullinginvalidtransactionsduringcommit: false
2024-11-08 19:43:58       transientstoremaxblockretention: 1000
2024-11-08 19:43:58     reconnectinterval: 25s
2024-11-08 19:43:58     recvbuffsize: 20
2024-11-08 19:43:58     requeststateinfointerval: 4s
2024-11-08 19:43:58     requestwaittime: 1500ms
2024-11-08 19:43:58     responsewaittime: 2s
2024-11-08 19:43:58     sendbuffsize: 200
2024-11-08 19:43:58     skipblockverification: false
2024-11-08 19:43:58     state:
2024-11-08 19:43:58       batchsize: 10
2024-11-08 19:43:58       blockbuffersize: 20
2024-11-08 19:43:58       checkinterval: 10s
2024-11-08 19:43:58       enabled: false
2024-11-08 19:43:58       maxretries: 3
2024-11-08 19:43:58       responsetimeout: 3s
2024-11-08 19:43:58     useleaderelection: false
2024-11-08 19:43:58   handlers:
2024-11-08 19:43:58     authfilters:
2024-11-08 19:43:58     - name: DefaultAuth
2024-11-08 19:43:58     - name: ExpirationCheck
2024-11-08 19:43:58     decorators:
2024-11-08 19:43:58     - name: DefaultDecorator
2024-11-08 19:43:58     endorsers:
2024-11-08 19:43:58       escc:
2024-11-08 19:43:58         name: DefaultEndorsement
2024-11-08 19:43:58     validators:
2024-11-08 19:43:58       vscc:
2024-11-08 19:43:58         name: DefaultValidation
2024-11-08 19:43:58   id: peer.org1.cello.com
2024-11-08 19:43:58   keepalive:
2024-11-08 19:43:58     client:
2024-11-08 19:43:58       interval: 60s
2024-11-08 19:43:58       timeout: 20s
2024-11-08 19:43:58     deliveryclient:
2024-11-08 19:43:58       interval: 60s
2024-11-08 19:43:58       timeout: 20s
2024-11-08 19:43:58     interval: 7200s
2024-11-08 19:43:58     mininterval: 60s
2024-11-08 19:43:58     timeout: 20s
2024-11-08 19:43:58   limits:
2024-11-08 19:43:58     concurrency:
2024-11-08 19:43:58       deliverservice: 2500
2024-11-08 19:43:58       endorserservice: 2500
2024-11-08 19:43:58       gatewayservice: 500
2024-11-08 19:43:58   listenaddress: <IP_ADDRESS>:7051
2024-11-08 19:43:58   localmspid: Org1MSP
2024-11-08 19:43:58   localmsptype: bccsp
2024-11-08 19:43:58   maxrecvmsgsize: 104857600
2024-11-08 19:43:58   maxsendmsgsize: 104857600
2024-11-08 19:43:58   mspconfigpath: /etc/hyperledger/fabric/msp
2024-11-08 19:43:58   networkid: dev
2024-11-08 19:43:58   profile:
2024-11-08 19:43:58     enabled: "false"
2024-11-08 19:43:58     listenaddress: <IP_ADDRESS>:6060
2024-11-08 19:43:58   tls:
2024-11-08 19:43:58     cert:
2024-11-08 19:43:58       file: /etc/hyperledger/fabric/tls/server.crt
2024-11-08 19:43:58     clientauthrequired: false
2024-11-08 19:43:58     clientrootcas:
2024-11-08 19:43:58       files:
2024-11-08 19:43:58       - tls/ca.crt
2024-11-08 19:43:58     enabled: "true"
2024-11-08 19:43:58     key:
2024-11-08 19:43:58       file: /etc/hyperledger/fabric/tls/server.key
2024-11-08 19:43:58     rootcert:
2024-11-08 19:43:58       file: /etc/hyperledger/fabric/tls/ca.crt
2024-11-08 19:43:58 vm:
2024-11-08 19:43:58   docker:
2024-11-08 19:43:58     attachstdout: false
2024-11-08 19:43:58     hostconfig:
2024-11-08 19:43:58       logconfig:
2024-11-08 19:43:58         config:
2024-11-08 19:43:58           max-file: "5"
2024-11-08 19:43:58           max-size: 50m
2024-11-08 19:43:58         type: json-file
2024-11-08 19:43:58       memory:<PHONE_NUMBER>
2024-11-08 19:43:58       networkmode: cello-net
2024-11-08 19:43:58     tls:
2024-11-08 19:43:58       ca:
2024-11-08 19:43:58         file: docker/ca.crt
2024-11-08 19:43:58       cert:
2024-11-08 19:43:58         file: docker/tls.crt
2024-11-08 19:43:58       enabled: false
2024-11-08 19:43:58       key:
2024-11-08 19:43:58         file: docker/tls.key
2024-11-08 19:43:58   endpoint: unix:///host/var/run/docker.sock
2024-11-08 19:43:58 2024-11-09 03:43:58.887 UTC 0003 INFO [peer] getLocalAddress -> Auto-detected peer address: <IP_ADDRESS>:7051
2024-11-08 19:43:58 2024-11-09 03:43:58.887 UTC 0004 INFO [peer] getLocalAddress -> Returning peer.org1.cello.com:7051
2024-11-08 19:43:58 2024-11-09 03:43:58.891 UTC 0005 INFO [nodeCmd] initGrpcSemaphores -> concurrency limit for endorser service is 2500
2024-11-08 19:43:58 2024-11-09 03:43:58.891 UTC 0006 INFO [nodeCmd] initGrpcSemaphores -> concurrency limit for deliver service is 2500
2024-11-08 19:43:58 2024-11-09 03:43:58.891 UTC 0007 INFO [nodeCmd] initGrpcSemaphores -> concurrency limit for gateway service is 500
2024-11-08 19:43:58 2024-11-09 03:43:58.891 UTC 0008 INFO [nodeCmd] serve -> Starting peer with TLS enabled
2024-11-08 19:43:58 2024-11-09 03:43:58.907 UTC 0009 INFO [certmonitor] trackCertExpiration -> The enrollment certificate will expire on 2034-11-07 03:39:00 +0000 UTC
2024-11-08 19:43:58 2024-11-09 03:43:58.907 UTC 000a INFO [certmonitor] trackCertExpiration -> The server TLS certificate will expire on 2034-11-07 03:39:00 +0000 UTC
2024-11-08 19:43:58 2024-11-09 03:43:58.909 UTC 000b INFO [ledgermgmt] NewLedgerMgr -> Initializing LedgerMgr
2024-11-08 19:43:58 2024-11-09 03:43:58.932 UTC 000c INFO [leveldbhelper] openDBAndCheckFormat -> DB is empty Setting db format as 2.0
2024-11-08 19:43:58 2024-11-09 03:43:58.933 UTC 000d INFO [blkstorage] NewProvider -> Creating new file ledger directory at /var/hyperledger/production/ledgersData/chains/chains
2024-11-08 19:43:58 2024-11-09 03:43:58.953 UTC 000e INFO [leveldbhelper] openDBAndCheckFormat -> DB is empty Setting db format as 2.5
2024-11-08 19:43:58 2024-11-09 03:43:58.962 UTC 000f INFO [leveldbhelper] openDBAndCheckFormat -> DB is empty Setting db format as 2.0
2024-11-08 19:43:58 2024-11-09 03:43:58.981 UTC 0010 INFO [leveldbhelper] openDBAndCheckFormat -> DB is empty Setting db format as 2.0
2024-11-08 19:43:58 2024-11-09 03:43:58.983 UTC 0011 INFO [ledgermgmt] NewLedgerMgr -> Initialized LedgerMgr
2024-11-08 19:43:58 2024-11-09 03:43:58.984 UTC 0012 INFO [gossip.service] New -> Initialize gossip with endpoint peer.org1.cello.com:7051
2024-11-08 19:43:58 2024-11-09 03:43:58.986 UTC 0013 INFO [gossip.gossip] New -> Creating gossip service with self membership of Endpoint: peer.org1.cello.com:7051, InternalEndpoint: peer.org1.cello.com:7051, PKI-ID: e8c1c840d73ee1fb8e3aace8dcf19831db615d17d713401c904c7df149dc96e9, Metadata:
2024-11-08 19:43:58 2024-11-09 03:43:58.986 UTC 0014 INFO [lifecycle] InitializeLocalChaincodes -> Initialized lifecycle cache with 0 already installed chaincodes
2024-11-08 19:43:58 2024-11-09 03:43:58.987 UTC 0015 INFO [nodeCmd] computeChaincodeEndpoint -> Entering computeChaincodeEndpoint with peerHostname: peer.org1.cello.com
2024-11-08 19:43:58 2024-11-09 03:43:58.987 UTC 0016 INFO [nodeCmd] computeChaincodeEndpoint -> Exit with ccEndpoint: peer.org1.cello.com:7052
2024-11-08 19:43:58 2024-11-09 03:43:58.987 UTC 0017 INFO [gossip.gossip] start -> Gossip instance peer.org1.cello.com:7051 started
2024-11-08 19:43:58 2024-11-09 03:43:58.989 UTC 0018 INFO [sccapi] DeploySysCC -> deploying system chaincode 'lscc'
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 0019 INFO [sccapi] DeploySysCC -> deploying system chaincode 'cscc'
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001a INFO [sccapi] DeploySysCC -> deploying system chaincode 'qscc'
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001b INFO [sccapi] DeploySysCC -> deploying system chaincode '_lifecycle'
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001c INFO [nodeCmd] serve -> Deployed system chaincodes
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001d INFO [discovery] NewService -> Created with config TLS: true, authCacheMaxSize: 1000, authCachePurgeRatio: 0.750000
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001e INFO [nodeCmd] serve -> Discovery service activated
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 001f INFO [nodeCmd] serve -> Starting peer with Gateway enabled
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 0020 INFO [nodeCmd] serve -> Starting peer with ID=[peer.org1.cello.com], network ID=[dev], address=[peer.org1.cello.com:7051]
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 0021 INFO [nodeCmd] serve -> Started peer with ID=[peer.org1.cello.com], network ID=[dev], address=[peer.org1.cello.com:7051]
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 0022 INFO [kvledger] LoadPreResetHeight -> Loading prereset height from path [/var/hyperledger/production/ledgersData/chains]
2024-11-08 19:43:58 2024-11-09 03:43:58.990 UTC 0023 INFO [blkstorage] preResetHtFiles -> No active channels passed
2024-11-08 19:44:22 2024-11-09 03:44:22.130 UTC 0024 INFO [ledgermgmt] CreateLedger -> Creating ledger [channel] with genesis block
2024-11-08 19:44:22 2024-11-09 03:44:22.131 UTC 0025 INFO [blkstorage] newBlockfileMgr -> Getting block information from block storage
2024-11-08 19:44:22 2024-11-09 03:44:22.135 UTC 0026 INFO [kvledger] commit -> [channel] Committed block [0] with 1 transaction(s) in 2ms (state_validation=0ms block_and_pvtdata_commit=0ms state_commit=0ms) commitHash=[]
2024-11-08 19:44:22 2024-11-09 03:44:22.135 UTC 0027 INFO [kvledger] updateLedgerStatus -> Updating ledger [channel] status to [ACTIVE]
2024-11-08 19:44:22 2024-11-09 03:44:22.135 UTC 0028 INFO [ledgermgmt] CreateLedger -> Created ledger [channel] with genesis block
2024-11-08 19:44:22 2024-11-09 03:44:22.139 UTC 0029 WARN [peer.orderers] Update -> Config defines both orderer org specific endpoints and global endpoints, global endpoints will be ignored channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.139 UTC 002a INFO [gossip.gossip] JoinChan -> Joining gossip network of channel channel with 1 organizations
2024-11-08 19:44:22 2024-11-09 03:44:22.139 UTC 002b INFO [gossip.gossip] learnAnchorPeers -> No configured anchor peers of Org1MSP for channel channel to learn about
2024-11-08 19:44:22 2024-11-09 03:44:22.139 UTC 002c INFO [gateway] configUpdate -> Updating orderer config channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.140 UTC 002d INFO [gossip.state] NewGossipStateProvider -> Updating metadata information for channel channel, current ledger sequence is at = 0, next expected block is = 1
2024-11-08 19:44:22 2024-11-09 03:44:22.140 UTC 002e INFO [deliveryClient] StartDeliverForChannel -> This peer will retrieve blocks from ordering service and disseminate to other peers in the organization channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.141 UTC 002f INFO [endorser] callChaincode -> finished chaincode: cscc duration: 16ms channel= txID=03eed81d
2024-11-08 19:44:22 2024-11-09 03:44:22.141 UTC 0030 INFO [comm.grpc.server] 1 -> unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=<IP_ADDRESS>:58104 grpc.code=OK grpc.call_duration=26.309792ms
2024-11-08 19:44:22 2024-11-09 03:44:22.145 UTC 0031 INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1
2024-11-08 19:44:22 2024-11-09 03:44:22.146 UTC 0032 WARN [peer.blocksprovider] func1 -> Encountered an error reading from deliver stream: EOF channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.146 UTC 0033 WARN [peer.blocksprovider] DeliverBlocks -> Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE from orderer channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.146 UTC 0034 WARN [peer.blocksprovider] DeliverBlocks -> Disconnected from ordering service. Attempt to re-connect in 100ms channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0035 INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0036 WARN [peer.blocksprovider] func1 -> Encountered an error reading from deliver stream: EOF channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0037 WARN [peer.blocksprovider] DeliverBlocks -> Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE from orderer channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.250 UTC 0038 WARN [peer.blocksprovider] DeliverBlocks -> Disconnected from ordering service. Attempt to re-connect in 120ms channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 0039 INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 003a WARN [peer.blocksprovider] func1 -> Encountered an error reading from deliver stream: EOF channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 003b WARN [peer.blocksprovider] DeliverBlocks -> Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE from orderer channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.373 UTC 003c WARN [peer.blocksprovider] DeliverBlocks -> Disconnected from ordering service. Attempt to re-connect in 144ms channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.521 UTC 003d INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1
2024-11-08 19:44:22 2024-11-09 03:44:22.521 UTC 003e WARN [peer.blocksprovider] func1 -> Encountered an error reading from deliver stream: EOF channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.522 UTC 003f WARN [peer.blocksprovider] DeliverBlocks -> Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE from orderer channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.522 UTC 0040 WARN [peer.blocksprovider] DeliverBlocks -> Disconnected from ordering service. Attempt to re-connect in 172ms channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.701 UTC 0041 INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1
2024-11-08 19:44:22 2024-11-09 03:44:22.702 UTC 0042 WARN [peer.blocksprovider] DeliverBlocks -> Got error while attempting to receive blocks: received bad status SERVICE_UNAVAILABLE from orderer channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.702 UTC 0043 WARN [peer.blocksprovider] func1 -> Encountered an error reading from deliver stream: EOF channel=channel orderer-address=orderer.cello.com:7050
2024-11-08 19:44:22 2024-11-09 03:44:22.702 UTC 0044 WARN [peer.blocksprovider] DeliverBlocks -> Disconnected from ordering service. Attempt to re-connect in 207ms channel=channel
2024-11-08 19:44:22 2024-11-09 03:44:22.925 UTC 0045 INFO [peer.blocksprovider] DeliverBlocks -> Pulling next blocks from ordering service channel=channel orderer-address=orderer.cello.com:7050 nextBlock=1

cello-api-engine
When peer channel fetch, it shows that "can't read the block: &{SERVICE_UNAVAILABLE}".
2024-11-08 19:43:08 Generating the settings.py for api_engine
2024-11-08 19:43:11 Migrations for 'api':
2024-11-08 19:43:11   api/migrations/0001_initial.py
2024-11-08 19:43:11     - Create model UserProfile
2024-11-08 19:43:11     - Create model Agent
2024-11-08 19:43:11     - Create model ChainCode
2024-11-08 19:43:11     - Create model FabricCA
2024-11-08 19:43:11     - Create model FabricPeer
2024-11-08 19:43:11     - Create model Govern
2024-11-08 19:43:11     - Create model Network
2024-11-08 19:43:11     - Create model Node
2024-11-08 19:43:11     - Create model NodeUser
2024-11-08 19:43:11     - Create model Organization
2024-11-08 19:43:11     - Create model PeerCa
2024-11-08 19:43:11     - Create model User
2024-11-08 19:43:11     - Create model Port
2024-11-08 19:43:11     - Create model PeerCaUser
2024-11-08 19:43:11     - Add field organization to node
2024-11-08 19:43:11     - Add field user to node
2024-11-08 19:43:11     - Create model KubernetesConfig
2024-11-08 19:43:11     - Create model File
2024-11-08 19:43:11     - Create model Channel
2024-11-08 19:43:11     - Add field organization to agent
2024-11-08 19:43:11     - Add field organization to userprofile
2024-11-08 19:43:11     - Add field user_permissions to userprofile
2024-11-08 19:43:12 Operations to perform:
2024-11-08 19:43:12   Apply all migrations: account, api, auth, authtoken, contenttypes, sessions, sites, socialaccount
2024-11-08 19:43:12 Running migrations:
2024-11-08 19:43:12   Applying contenttypes.0001_initial... OK
2024-11-08 19:43:12   Applying contenttypes.0002_remove_content_type_name... OK
2024-11-08 19:43:12   Applying auth.0001_initial... OK
2024-11-08 19:43:12   Applying auth.0002_alter_permission_name_max_length... OK
2024-11-08 19:43:12   Applying auth.0003_alter_user_email_max_length... OK
2024-11-08 19:43:12   Applying auth.0004_alter_user_username_opts... OK
2024-11-08 19:43:12   Applying auth.0005_alter_user_last_login_null... OK
2024-11-08 19:43:12   Applying auth.0006_require_contenttypes_0002... OK
2024-11-08 19:43:12   Applying auth.0007_alter_validators_add_error_messages... OK
2024-11-08 19:43:12   Applying auth.0008_alter_user_username_max_length... OK
2024-11-08 19:43:12   Applying auth.0009_alter_user_last_name_max_length... OK
2024-11-08 19:43:12   Applying auth.0010_alter_group_name_max_length... OK
2024-11-08 19:43:12   Applying auth.0011_update_proxy_permissions... OK
2024-11-08 19:43:12   Applying auth.0012_alter_user_first_name_max_length... OK
2024-11-08 19:43:13   Applying api.0001_initial... OK
2024-11-08 19:43:13   Applying account.0001_initial... OK
2024-11-08 19:43:13   Applying account.0002_email_max_length... OK
2024-11-08 19:43:13   Applying account.0003_alter_emailaddress_create_unique_verified_email... OK
2024-11-08 19:43:13   Applying account.0004_alter_emailaddress_drop_unique_email... OK
2024-11-08 19:43:13   Applying authtoken.0001_initial... OK
2024-11-08 19:43:13   Applying authtoken.0002_auto_20160226_1747... OK
2024-11-08 19:43:13   Applying authtoken.0003_tokenproxy... OK
2024-11-08 19:43:13   Applying authtoken.0004_alter_tokenproxy_options... OK
2024-11-08 19:43:13   Applying sessions.0001_initial... OK
2024-11-08 19:43:13   Applying sites.0001_initial... OK
2024-11-08 19:43:13   Applying sites.0002_alter_domain_unique... OK
2024-11-08 19:43:13   Applying socialaccount.0001_initial... OK
2024-11-08 19:43:13   Applying socialaccount.0002_token_max_lengths... OK
2024-11-08 19:43:13   Applying socialaccount.0003_extra_data_default_dict... OK
2024-11-08 19:43:13   Applying socialaccount.0004_app_provider_id_settings... OK
2024-11-08 19:43:14 Create user successfully 0e13ce7d-244e-4e9c-b07f-4c3e27db2f8e
2024-11-08 19:43:54 org1.cello.com
2024-11-08 19:44:21 Status: 201
2024-11-08 19:44:21 {
2024-11-08 19:44:21 "name": "channel",
2024-11-08 19:44:21 "url": "/participation/v1/channels/channel",
2024-11-08 19:44:21 "consensusRelation": "consenter",
2024-11-08 19:44:21 "status": "active",
2024-11-08 19:44:21 "height": 1
2024-11-08 19:44:21 }
2024-11-08 19:44:21
2024-11-08 19:43:54 INFO Running command: /opt/bin/cryptogen generate --output=/opt/cello/org1.cello.com/crypto-config --config=/opt/cello/org1.cello.com/crypto-config.yaml
2024-11-08 19:43:55 INFO Running command: /opt/bin/cryptogen extend --input=/opt/cello/org1.cello.com/crypto-config --config=/opt/cello/org1.cello.com/crypto-config.yaml
2024-11-08 19:43:55 INFO Running command: /opt/bin/cryptogen extend --input=/opt/cello/org1.cello.com/crypto-config --config=/opt/cello/org1.cello.com/crypto-config.yaml
2024-11-08 19:44:21 INFO Running command: /opt/bin/configtxgen -configPath /opt/cello/net/ -profile channel -outputBlock /opt/cello/net/channel.block -channelID channel
2024-11-08 19:44:21 2024-11-09 03:44:21.544 UTC 0001 INFO [common.tools.configtxgen] main -> Loading configuration
2024-11-08 19:44:21 2024-11-09 03:44:21.570 UTC 0002 INFO [common.tools.configtxgen.localconfig] completeInitialization -> orderer type: etcdraft
2024-11-08 19:44:21 2024-11-09 03:44:21.570 UTC 0003 INFO [common.tools.configtxgen.localconfig] Load -> Loaded configuration: /opt/cello/net/configtx.yaml
2024-11-08 19:44:21 2024-11-09 03:44:21.587 UTC 0004 INFO [common.tools.configtxgen] doOutputBlock -> Generating genesis block
2024-11-08 19:44:21 2024-11-09 03:44:21.587 UTC 0005 INFO [common.tools.configtxgen] doOutputBlock -> Creating application channel genesis block
2024-11-08 19:44:21 2024-11-09 03:44:21.591 UTC 0006 INFO [common.tools.configtxgen] doOutputBlock -> Writing genesis block
2024-11-08 19:44:21 INFO /opt/bin/osnadmin channel join --channelID channel --config-block /opt/cello/net/channel.block -o orderer.cello.com:7053 --ca-file /opt/cello/org1.cello.com/crypto-config/ordererOrganizations/cello.com/orderers/orderer.cello.com/msp/tlscacerts/tlsca.cello.com-cert.pem --client-cert /opt/cello/org1.cello.com/crypto-config/ordererOrganizations/cello.com/orderers/orderer.cello.com/tls/server.crt --client-key /opt/cello/org1.cello.com/crypto-config/ordererOrganizations/cello.com/orderers/orderer.cello.com/tls/server.key
2024-11-08 19:44:21 INFO /opt/bin/peer channel join -b /opt/cello/net/channel.block
2024-11-08 19:44:22 2024-11-09 03:44:22.106 UTC 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized
2024-11-08 19:44:22 2024-11-09 03:44:22.145 UTC 0002 INFO [channelCmd] executeJoin -> Successfully submitted proposal to join channel
2024-11-08 19:44:22 INFO /opt/bin/peer channel fetch config /opt/cello/net/config_block.pb -o orderer.cello.com:7050 --ordererTLSHostnameOverride orderer.cello.com -c channel --tls --cafile /opt/cello/org1.cello.com/crypto-config/ordererOrganizations/cello.com/orderers/orderer.cello.com/msp/tlscacerts/tlsca.cello.com-cert.pem
2024-11-08 19:44:22 2024-11-09 03:44:22.403 UTC 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized
2024-11-08 19:44:22 2024-11-09 03:44:22.411 UTC 0002 INFO [cli.common] readBlock -> Expect block, but got status: &{SERVICE_UNAVAILABLE}
2024-11-08 19:44:22 Error: can't read the block: &{SERVICE_UNAVAILABLE}

@yeasy

It seems the OSN's election is done before being pulled from the peer.
Can you pull the block manually from the OSN after the election is done?
@YoungHypo

I found the error. When "peer channel fetch” is called, "osnadmin channel join" is not completed.
So we need to add time.sleep() in django to block the process, so that the "osn join” can be fully established before running the subsequent tasks, I will submit the pr later! Thank you so much.
@yeasy

For most case, it's not a good idea to use time.sleep().
Instead, we can add more tries at peer channel fetch, till it's completed or timeout to throw error.

#659


options -P --pid does not work

-P /run/beaver.pid
--pid /run/beaver.pid
does not work
couldn't find any usage in code.

-P and --pid appear to be working in the latest release. Please re-open if you're still having problems.

Any updates here? Not working in 36.2.1:
Running with
$beaver ... -P /run/beaver.pid
but
$ cat /run/beaver.pid
cat: /run/beaver.pid: No such file or directory

@ScottBrenner please file a new issue, rather than comment on a 3+ year old issue.


build: remove obsolete config from pom.xml

PR summary
Removes some obsolete configuration from the pom.xml file.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.39.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


debug staging

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 93.75%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
116

Relevant Lines:
118

💛  - Coveralls


feat: migrate + optimize the React transform in packages/compiler

Is your feature request related to a problem? Please describe.
Currently, we have a babel-based compilation project under packages/compiler. This works at the moment, but it can result in slow compilation times, as it is unoptimized and written with babel.
Describe the solution you'd like
We should work on a new SWC-based compiler that solves this problem. We should also look into optimizing the compiler to compile very fast. This would just apply to the react transform and not the optimizing compiler.
The React transform's job is to "split" block components into two parts: the component that is rendered and the internal "block." For example this:
function Button({ initial }) {
  const [count, setCount] = useState(initial);

  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

const ButtonBlock = block(Button);

would be roughly compiled to this:
function Button({ initial }) {
  const [count, setCount] = useState(initial);

  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

function _component$({ initial }) {
  const [count, setCount] = useState(initial);
  return useBlock_component$({
    _$: () => setCount(count + 1),
    count,
  });
}

function _block$({ _$, count }) {
  return <button onClick={_$}>{count}</button>;
}

const ButtonBlock = _component$;
const useBlock_component$ = block(_block$);

The idea is to "extract" out the dynamics into a separate parent component. So here, _component$ acts as a "controller" component for the useBlock_component$ block component
Describe alternatives you've considered
We could continue optimizing the compiler, but because we have several contributors that know how to use Rust, getting performance benefits from a rewrite would be best.

How's this going folks? :smiley:

Andrew is getting started on friday

Andrew is getting started on friday

Ok, awesome!

How's this going folks? I hope y'all are doing well by the way?


Infinite loading after shade pairing.

Hi!
After updating to the latest release (V2.2.0), I've noticed that the interface would start loading indefinitely after hitting "shade paired" on the shade prog menu.

Thanks, I'll have a look.  I suspect that this is a script error and a page reload will make it go away.

If you use the Github update function and install Main this issue has been fixed.  It was not sending the linked remotes after pair.

I am closing this for now as v2.2.1 was just released that contains the fixes for this error.


add support for identifiers containing _

Hi, is it possible to add the support for identifiers with _ ? I just started using fireman and figured this limitation will limit my ability to query many collections in my database. It would be really helpful to add this support.
Thanks

Hey @lizbrownwood thanks for your proposal! Actually you can already use identifiers containing _, you just need to wrap them in single or double quotes:
foor/'bar_baz'


Error in alertmanager-relation-changed deploying in AWS

I'm deploying charmcraft-prometheus to AWS.
Charm version  in charmhub.io:
Stable: 2
This is probably for the VM charm, but the link points to this repo.
unit-prometheus-1: 10:22:33 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook
unit-prometheus-1: 10:22:34 ERROR unit.prometheus/1.juju-log alertmanager:4: Uncaught exception while in charm code:
Traceback (most recent call last):
File "./src/charm.py", line 352, in
main(PrometheusCharm)
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/main.py", line 402, in main
_emit_charm_event(charm, dispatcher.event_name)
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/main.py", line 140, in _emit_charm_event
event_to_emit.emit(*args, **kwargs)
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/framework.py", line 278, in emit
framework._emit(event)
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/framework.py", line 722, in _emit
self._reemit(event_path)
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/framework.py", line 767, in _reemit
custom_handler(event)
File "./src/charm.py", line 62, in _on_alertmanager_changed
addrs = json.loads(event.relation.data[event.app].get('addrs', '[]'))
File "/var/lib/juju/agents/unit-prometheus-1/charm/venv/ops/model.py", line 699, in getitem
return self._data[key]
KeyError: <ops.model.Application alertmanager>
unit-prometheus-1: 10:22:34 ERROR juju.worker.uniter.operation hook "alertmanager-relation-changed" (via hook dispatching script: dispatch) failed: exit status 1
unit-prometheus-1: 10:22:34 INFO juju.worker.uniter awaiting error resolution for "relation-changed" hook

Hi,
Unfortunately the same applies here. charmcraft-prometheus is not the charm built from this repository (which is https://charmhub.io/prometheus-k8s).
Sorry again for the confusion.
Best,
Simme


macos requires zeromq

ocaml install Jupyter produces errors, finishing with:
The packages you requested declare the following system dependencies. Please make sure they are installed before retrying:
zeromq
caml 4.08.1
macOS 0.15.3 Beta
home-brew 2.2.3

fixed by brew install zeromq before Ocaml install Jupiter
Rather obvious fix, then it works fine.
Thanks - great project!

Well, for me it was not that easy to solve because opam install jupyter throwed a compilation error for onf-zmq ("No file 'zmq.h' found") but no message about the missing dependency, making me despair before eventually understanding what was going on.
I think it would be better to warn about the dependency.

Sorry for late reply. opam depext jupyter shows dependencies in major OS or distribution. If you need an error message in the build phase, I think you should open an issue about conf-zmq in https://github.com/ocaml/opam-repository. I will write dependencies in README, but exhaustive explanation is impossible because the names of packages are different every OS.


Reduce code duplication in suggestion methods

The existing suggest_recipe and suggest_variable methods have a decent chunk of duplicate code. This commit factors that out into a separate method.

I changed it to use the min_by_key method on iterators to avoid collecting into a vec. I'm also kind of a comment hater, unless it's on "thar be dragons" type code, so I removed it.


Expose alternate graph return value on ingest

This maintains compatibility with the one-click API. Additionally, it allows the caller to get the graph object itself so they can do grf.compute() and grf.wait() on it, and then directly obtain resultst from the computation.
The alternative is dag.server_logs and tasks.fetch_result, which are cumbersome at best for users who have synchronous needs.
This pattern will be user in the collection-mapper logic, which absolutely must provide a usable synchronous entrypoint.

[sc-37815]

@thetorpedodog ping 🙏

Thanks @thetorpedodog !


HISTORY problem with lat,lon coordinates in diagnostics of multi-node simulations

Hi everyone,
A GCHPctm user (@joeylamcy) has reported an issue in the output of his multi-node simulations (https://github.com/geoschem/GCHPctm/issues/37). Specifically, the lat and lon coordinates are erroneous, but the rest of the diagnostic's data is okay. For single node simulations, lat and lon are okay, but for multinode simulations there are big blocks of lat and lon that are close to zero.
The user reported the issue in GCHPctm version 13.0.0-alpha.9 which uses MAPL @ fca3b33. He is using ifort 19.0.4, intel MPI, netcdf-c 4.7.1 and netcdf-fortran 4.5.2.
To try and gather more information on the problem, he reran the following simulation on 1 node, 2 nodes, 3 nodes, and 4 nodes. The configuration of this simulation was

1 hour simulation, normal GCHPctm configuration
6 cores per node, 100 GB memory per node
The following HISTORY.rc:  TestCollectionNative.template:   '%y4%m2%d2_%h2%n2z.nc4',
  TestCollectionNative.format:     'CFIO',
  TestCollectionNative.frequency:  010000
  TestCollectionNative.duration:   010000
  TestCollectionNative.mode:       'time-averaged'
  TestCollectionNative.fields:     'SpeciesConc_O3', 'GCHPchem',
::

No errors or warnings were raised in the simulations log files.
Results
Note: The narrow blank bands between faces, like in the figure directly below, are because of my plotting routine.
When the simulation ran on 1 node

When the simulation ran on 2 nodes

When the simulation ran on 3 nodes

When the simulation ran on 4 nodes

Other results
Adding TestCollectionNative.conservative: 1 for the 4-node simulation produced a different result:

Changing the position of TestCollectionNative.conservative: 1 line in the collection also produced a different result:

The diagnostic's data is okay though
Interestingly, it is only the lat and lon coordinates that are problematic. The diagnostic's data variables (i.e. SpeciesConc_O3) are okay. For example, if I calculate the coordinates offline, and then replot the diagnostic output, the figures look okay.

Has anyone seen this before? Do you have any thoughts or ideas? Thanks in advance!
-Liam

I don't think we've seen this before and since we routinely produce lat-lon output while using multiple nodes, there must be another factor that is triggering this.

Several of the intermediate plots suggest that the problem is correlated with the metadata being wrong for entire faces of the cubed sphere.   But subsequent examples are more complicated than that.

So the bottom line is, you run on different core counts and based on how many nodes that represents you get different cubed-sphere output, with the only difference being in the lats and lons? Does it look like the lats and lons in the bad cases were written with something, just bad data, or are they true missing values. I will look at the code but I'm having a hard time figuring out how all the other variables could be written correctly.

Yeah this is strange. We've been running lots of multinode simulations too, and we've never seen anything like this before.

So the bottom line is, you run on different core counts and based on how many nodes that represents you get different cubed-sphere output, with the only difference being in the lats and lons?

Yes. On one node lat and lon look okay, but on multiple nodes they go bad.

Does it look like the lats and lons in the bad cases were written with something, just bad data, or are they true missing values. I will look at the code but I'm having a hard time figuring out how all the other variables could be written correctly.

I just took a closer look. For some reason, it appears lat and lon have similar values to the data field at the surface (i.e., SpeciesConc_O3 at lev=0). This truely puzzles me.
Below are some images (2d plots) of lat and lon for face 4 for the 4 node simulation (a face with "problematic" coordinates).
Image of lons:

Image of lats:

Image of SpeciesConc_O3:

Note that lats and lons are not equal to each other or SpeciesConc_O3, but they are similar (e.g. within ~5%). The plots above show that lats and lons are being written with data that's similar to the fields data.
Here is what SpeciesConc_O3 looks like at level 30. This plot confirms that lons is similar to the data at the surface.

And here is what lons looks like for a face 4 when the coordinate is written correctly. This plot shows what an image of lons should look like.

I'm thoroughly stumped.

Not sure if this is helpful, but here is the NetCDF file:
GCHP.TestCollectionNative.20160701_0030z.zip
And here is the same file for the 1-node simulation:
GCHP.TestCollectionNative.20160701_0030z.zip

I'm going to close this issue. We aren't able to reproduce the issue, and there's a easy work around we recommended to the user. I'll reopen if we get any more reports of this.
Thanks for everyone's time in looking into this!


[Warcraft III] Getting 7 (terribly low) FPS since the new W3 2.0 update

The title.
Also, I want to point out that I did play that game recently (couple of weeks ago) and it was fine. Not sure if it's dxvk related. I'm just starting here...
Software information
Warcraft 3. Settings were at lowest preset.
System information

GPU: AMD Radeon RX 5700XT
Driver: mesa 24.2.7
Wine version: wine-ge-8-26-x86_64
DXVK version: v2.4.1 (I also tried v2.5)

Apitrace file(s)
https://mega.nz/file/6uInDZ6J#_r420DwzC2T8AX-6-QhRn-9t8N42zLj8NaGuQwlvpzs
When I tried to disable DXVK for making the API trace, it crashed, so I left it.
Log files
wine.log

I have noticed the two following threads on Blizzard's forum:
https://eu.forums.blizzard.com/en/warcraft3/t/fps-drops-back/1035/2
https://us.forums.blizzard.com/en/warcraft3/t/the-frame-rate-still-has-a-significant-drop/33206
Both are speaking of FPS drop since 2.0, it seems. The timing seems consistant. Although, they are talking about getting from 240 FPS to 100 or 60 FPS while I'm getting at 7-12 FPS. Not sure if the difference is only due to hardware ?
So, it could be possible that the issue is from on blizzard's side, but I feel like what i'm experiencing is way more terrible than what these reports are talking about.

Also, I want to point out that I did play that game recently (couple of weeks ago) and it was fine. Not sure if it's dxvk related. I'm just starting here...

Terrible or not, it definitely sounds like a game induced issue then, which is out of our scope to address. Since this is about a game that is under active development, I'd recommend waiting until the problem is addressed and the game performs as expected on native/Windows. Should you still get iffy performance with dxvk in the game at that point, do let us know.

Performance on Windows is acceptable though while it's not on Linux whether there's a bug or not. Shouldn't linux be able to offer a performance close to what is reported by others on Windows?
The lowest reported in the forums was 60FPS and I'm here with 7FPS with a more than capable graphic card. I just think that even if there is a bug in the game, it still seems to me there is performance to gain on the linux side. I'm wondering if that linux gap sits in DXVK or not.
You can look at this streamer having 100FPS ingame:
https://www.youtube.com/@FollowGrubby/videos
Why wouldn't Linux/DXVK give something closer ? Again, my graphic card is more than capable.
I do have a Windows partition. I might just try to make room on it and try to install it on Windows to compare and I'll report back in order to eliminate the hardware difference hypothesis.

What is VRAM usage looking like? Post a screenshot with DXVK_HUD=full

Something is wrong:

GPU is 1% and CPU is 8% usage....
VRAM:

How does it behave when ran without fsync and esync?

How does it behave when ran without fsync and esync?

Nope.

Does running with DXVK_CONFIG="d3d11.cachedDynamicResources = a" help?
If not then try running it with dxvk 2.3.1 along with DXVK_CONFIG="dxgi.useMonitorFallback = True"

@Blisto91 NICE.
Using
DXVK_CONFIG="d3d11.cachedDynamicResources = a"

made all the difference!
![image](https://github.com/user-attachments/assets/3f3e5c37-187c-407b-8255-d9d8405e4355

Can you explain what's going on? Is it a common option that I should have expected to be on, but is not for some reason? Is it bad config, or a particular case? Do you expect this to be enabled in my other games where I get OK performance?

The comment in the example dxvk.conf explains it already quite well https://github.com/doitsujin/dxvk/blob/master/dxvk.conf#L279

I am not reproducing any uplift myself so we are probably not going to make it a builtin config i imagine.
Besides some a rare few games where it can give a uplift to everyone it can also sometimes help specifically on systems that have issues with rebar performance. I imagine the latter is going on here.

I have enabled resizable bar as per the explanations here:
https://wiki.archlinux.org/title/Improving_performance#Enabling_PCI_resizable_BAR
So, you suspect that this is what is causing my issues?

Try to disable ReBAR and also don't set the cachedDynamicResources and see how it performs then.

Bad rebar performance is my best guess yes.

So I tried disabling both the option and resizable bar and it did fix the major issue. Although, I got around 100FPS this way instead of the 144FPS with resizable bar AND the option you suggested. Or could it be a bad reading in the latter case? I'm wondering because the FPS was steady at 144FPS never changing. Even if I did remove the FPS cap to 144, it didn't move up or down. So, is the performance actually the same, but just badly read when resizable bar and d3d11.cachedDynamicResources = a is configured?

Also, does d3d11.cachedDynamicResources = a actually makes it like resizable bar is disabled? My question is if it's gonna prevent resizable bar optimizations to be enabled?

Setting that option prevents DXVK from using BAR memory, but the Vulkan driver may still use it internally for some things.

Alright. Since the mystery is resolved, I'll close this. I understand that the best might be to stick with resizable bar and pay attention to that parameter if issues happen. Thanks for support!


[rebase on main] Fix a crash caused by wrongly used mutex

We used to have an only mutex in TimeGraph and we splitted into two when
we create TrackManager. In this PR, we moved the problematic functions
(GetNumTimers and GetTracksMinMaxTimestamps) to TrackManager to mutex
them properly.
Solve http://b/179467994.

Could you link the original PR in the description?

Could you link the original PR in the description?

Done!


add an info command to ease troubleshooting

add an info command (gatsby info is a great example) that gathers necessary context for troubleshooting such as OS, dependency versions, etc., without requiring the issue author to hop back and forth to their terminal to paste various info.
In short, the output would be very similar to the output of:
npx envinfo --system --binaries --npmPackages "@aws-amplify/backend,typescript,aws-cdk,aws-cdk-lib,aws-amplify" --showNotFound

Command signature:
amplify info [--clipboard]

Example usage:
> amplify info

  System:
    OS: macOS 13.5.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 3.6.1 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.9.0 - ~/Library/Caches/fnm_multishells/77574_1680319338649/bin/node
    Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/77574_1680319338649/bin/yarn
    npm: 10.2.1 - ~/Library/Caches/fnm_multishells/77574_1680319338649/bin/npm
    pnpm: 8.9.2 - ~/Library/Caches/fnm_multishells/77574_1680319338649/bin/pnpm
  npmPackages:
    @aws-amplify/backend: ^0.2.0-alpha.10 => 0.2.0-alpha.10
    aws-amplify: ^6.0.1-api-v6-models.c1977f8.0 => 6.0.1-api-v6-models.c1977f8.0+c1977f8
    aws-cdk: Not Found
    aws-cdk-lib: Not Found
    typescript: ^5.2.2 => 5.2.2

Example usage:
> amplify info --clipboard
Copied info to clipboard!

Regarding --clipboard, this can be removed in favor of manually copying and pasting or piping to utilities such as pbcopy:
> amplify info | pbcopy

ref https://nextjs.org/docs/app/api-reference/next-cli#next-info

Closing as this has been implemented


chore: setup esbuild for bundling typescript

use the bundling extensions documentation as a guide for setting up
esbuild. unfortunately, esbuild is necessary since bun does not support
the "cjs" output format yet, which is required for vscode extensions.
see: https://code.visualstudio.com/api/working-with-extensions/bundling-extension#using-esbuild

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#17
#16  👈
#15
#14
#13
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lewxdev and the rest of your teammates on  Graphite


fix(updateScreenshot): set default empty object

The sooner CI gets figured out the better... this fixes an issue introduced with my last commit 😬

Perfect, will publish shortly 👍


Reverted

@ssorenso
This PR reverts the containerized testrunner.

Can one of the admins verify this patch?

Hah...
The tests are running!


[bot] Update to version 3.0.1

Auto-update version number to 3.0.1

@conda-forge-admin please rerender


Run tests via actions

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@19d1d43). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage        ?   76.74%
=======================================
  Files           ?       52
  Lines           ?     1853
  Branches        ?        0
=======================================
  Hits            ?     1422
  Misses          ?      359
  Partials        ?       72

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 19d1d43...e2b69e1. Read the comment docs.


Changing isFlaky var to boolean

@Jnegrier
i have that fix on my branch as well, but feel free to merge, thanks!

closing this one, as it was fixed in https://github.com/delta-reporter/delta-frontend/pull/54

closing this one, as it was fixed in #54


Layout and Code Refactoring for Questions and Answers

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Client: I added multiple integration tests (Jest) related to the features
[x] Client: I added authorities to all new routes and check the course groups for displaying navigation elements (links, buttons)
[x] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I added multiple screenshots/screencasts of my UI changes
[x] Client: I translated all the newly inserted strings into German and English

Motivation and Context

Code is hard to read with a lot of duplication.
Questions and Answers are too small for longer texts.
Description

Refactored the code to include less methods and to be more readable.
Extracted the question-answer and question component.
Changed the design of the UI.
Added the functionality to collapse the questions and answers.
Added the functionality to resize the questions and answers by dragging.
Adapted the layout on smaller screens: Questions and Answers are shown below the detail information
Steps for Testing

Log in to Artemis
(1a. If not already, enable questions and answers for the course)
Navigate to an exercise or a lecture detail page
Play around with questions and answers (especially with the new drag and collapse feature)

Screenshots

New design of Question and Answers

Collapsed Questions and Answers

@HanyaElhashemy @sascha11110 Thanks for the feedback! I implemented it now.
And another student can edit/ delete questions and answers if he is at least a tutor in that course.

I don't really like the ? I would prefer if we still write Question at the top,
Same for the lightbulb, I would prefer that we write Answers

I don't really like the ? I would prefer if we still write Question at the top,
Same for the lightbulb, I would prefer that we write Answers

@krusche I removed the icons. Now it says question or answer

Can you update the screenshots in the PR? I would also suggest to move this to 4.0.3 then we have a bit more time for testing

I tested it again and also all options in the markdown editor. Unfortunately, the coloring option does not work for me.
Apart from that, everything works perfectly!

@sascha11110 I had a look into this and it seems to be a problem with the htmlformarkdown pipe. I will fix this in another PR refactoring the whole Markdown Editor, since it isn't directly related to the questions and answers

Good work :) I still have some comments: I would like to see some harder visual break between questions, because I find it hard to see where one stopes and the next one begins, but that might be just my opinion ( to make it clear: it's not something I request - it would be nice ImO but its up to you). Maybe a horizontal break, see screnshot:

@TobiasPr I now added a very light background to each question (group). It should be easier now to tell them apart.

I requested changes, because I found a small bug: When I edit a question or answer and click on cancel, the change is still shown -> when I refresh it is gone, because the data did not change, but it might be confusing. Steps to reproduce:

Create question
Click on edit button
Change question
Click on Cancel
Change is shown, but not applied

@TobiasPr good catch! Now the text is always reset to the initial text if not saved when closing the editor

I tested it again and also all options in the markdown editor. Unfortunately, the coloring option does not work for me.
Apart from that, everything works perfectly!

@sascha11110 I found the reason for this. I now added the 'markdown-preview' class and it should work now

Thanks for fixing the issues with the markdown editor! Looks good to me! :-)
A little suggestion (for a follow-up): would be nice if the focus is set to the corresponding textarea after clicking Add answer or Add question so that you can start typing right away.

Good idea! I'll definitely add that in a later PR

Thank you so much for addressing my previous suggestion. I still have smaller notes: could you please adapt the changes from #1381 here? The quote command does not seem to be working properly in the markdown editor.
Also when I switch to preview tab the size of the tab shrinks, is it possible to adjust this as well?

@HanyaElhashemy I included the fix and the editor should always take up the whole width now
closes https://github.com/ls1intum/Artemis/issues/1057 now, too, I guess


[BUG] ProbabilisticActor for discreate action used with parallel env creates wrong action dim

Bug
def make_env():
    base_env = GymEnv('CartPole-v1', device=device)

    # Create a transformed environment with observation normalization, float conversion, and step counter
    transformed_env = TransformedEnv(
        base_env,
        Compose(
            #ObservationNorm(in_keys=["observation"]),  # Normalize observations
            #DoubleToFloat(),  # Ensure observations are float32
            StepCounter()  # Track steps in the environment
        )
    )

    # Initialize stats specifically for ObservationNorm (transform[0])
    #transformed_env.transform[0].init_stats(1024)  # Collect stats from 1024 frames for normalization

    return transformed_env

parallel_env = ParallelEnv(num_workers= 7, create_env_fn = lambda : make_env())
check_env_specs(parallel_env)

    # Get observation and action dimensions from the environment specs
    observation_dim = parallel_env.observation_spec["observation"].shape[-1]
    action_dim = parallel_env.action_spec.shape[-1]
# Define the actor network using nn.Sequential (outputs logits for a categorical distribution)
    class ActorNet(nn.Module):
        def __init__(self, observation_dim, action_dim):
            super(ActorNet, self).__init__()
            self.net = nn.Sequential(
                nn.Linear(observation_dim, 64),
                nn.ReLU(),
                nn.Linear(64, 64),
                nn.ReLU(),
                nn.Linear(64, action_dim)  # Outputs logits for each action in the discrete space
            )

        def forward(self, x):
            print("actor net input shape  ",x.shape)

            temp=  self.net(x)
            print("actor net output shape  ",temp.shape)

            return temp

    # Instantiate the actor network
    actor_net = ActorNet(observation_dim, action_dim).to(device)

# Wrap actor network in TensorDictModule to work with TorchRL's TensorDict system
    tensordict_module = TensorDictModule(actor_net, in_keys=["observation"], out_keys=["logits"])
    actor_module = ProbabilisticActor(
        module=tensordict_module,
        spec=parallel_env.action_spec,
        in_keys=["logits"],
        out_keys=["action"],
        distribution_class=Categorical,
        return_log_prob=True  # Return log probability of sampled actions (required for PPO loss)
    )

# error on rollout
parallel_env.rollout(1000,actor_module)

Issue is  created tensordict['action'] has shape torch.size[7]
should have been tensordict['action'] has shape torch.size[7,1]
Fix
    # Use ProbabilisticActor to sample actions probabilistically from Categorical distribution based on logits
    class CustomProbabilisticActor(ProbabilisticActor):
        def forward(self, tensordict):
            # Call the parent class's forward method to get actions and log probabilities
            tensordict = super().forward(tensordict)

            # Reshape the action tensor to have shape [batch_size, 1]
            tensordict.set("action", tensordict.get("action").unsqueeze(-1))

            return tensordict

    # Use ProbabilisticActor to sample actions probabilistically from Categorical distribution based on logits
    actor_module = CustomProbabilisticActor(
        module=tensordict_module,
        spec=parallel_env.action_spec,
        in_keys=["logits"],
        out_keys=["action"],
        distribution_class=Categorical,
        return_log_prob=True  # Return log probability of sampled actions (required for PPO loss)
    )

# rollout  works now
parallel_env.rollout(1000,actor_module)

Version:
torch                     2.5.0                    pypi_0    pypi
torchrl                   0.5.0                    pypi_0    pypi
tensordict                0.5.0                    pypi_0    pypi

Hello
I think there is some confusion here: your action spec is a one-hot encoding, whereas you are using a Categorical distribution.
from tensordict.nn import TensorDictModule
from torch.distributions import Categorical
from torchrl.envs import ParallelEnv, TransformedEnv, GymEnv, Compose, StepCounter, check_env_specs
from torchrl.modules import ProbabilisticActor
from torch import nn

device = "cpu"

def make_env():
    # We must tell the env that we want a categorical action
    base_env = GymEnv('CartPole-v1', device=device, categorical_action_encoding=True)

    # Create a transformed environment with observation normalization, float conversion, and step counter
    transformed_env = TransformedEnv(
        base_env,
        Compose(
            # ObservationNorm(in_keys=["observation"]),  # Normalize observations
            # DoubleToFloat(),  # Ensure observations are float32
            StepCounter()  # Track steps in the environment
        )
    )

    # Initialize stats specifically for ObservationNorm (transform[0])
    # transformed_env.transform[0].init_stats(1024)  # Collect stats from 1024 frames for normalization

    return transformed_env

if __name__ == "__main__":
    check_env_specs(make_env())
    parallel_env = ParallelEnv(num_workers=7, create_env_fn=lambda: make_env())
    check_env_specs(parallel_env)

    # Get observation and action dimensions from the environment specs
    observation_dim = parallel_env.observation_spec["observation"].shape[-1]

    # do NOT use shape[-1] here but space.n
    # action_dim = parallel_env.action_spec.shape[-1]
    action_dim = parallel_env.action_spec.space.n

    # Define the actor network using nn.Sequential (outputs logits for a categorical distribution)
    class ActorNet(nn.Module):
        def __init__(self, observation_dim, action_dim):
            super(ActorNet, self).__init__()
            self.net = nn.Sequential(
                nn.Linear(observation_dim, 64),
                nn.ReLU(),
                nn.Linear(64, 64),
                nn.ReLU(),
                nn.Linear(64, action_dim)  # Outputs logits for each action in the discrete space
            )

        def forward(self, x):
            print("actor net input shape  ", x.shape)

            temp = self.net(x)
            print("actor net output shape  ", temp.shape)

            return temp

    # Instantiate the actor network
    actor_net = ActorNet(observation_dim, action_dim).to(device)

    # Wrap actor network in TensorDictModule to work with TorchRL's TensorDict system
    tensordict_module = TensorDictModule(actor_net, in_keys=["observation"], out_keys=["logits"])
    actor_module = ProbabilisticActor(
        module=tensordict_module,
        spec=parallel_env.single_action_spec,
        in_keys=["logits"],
        out_keys=["action"],
        distribution_class=Categorical,
        return_log_prob=True  # Return log probability of sampled actions (required for PPO loss)
    )

    # error on rollout
    parallel_env.rollout(1000, actor_module)

Hope that helps

Thank you for the help can you help me understand what is going wrong in the  as I am trying to take and env step.
`import torch
from torchrl.envs import GymEnv
from torchrl.envs.transforms import ActionDiscretizer
from tensordict import TensorDict
Step 1: Create the HalfCheetah-v4 environment using GymEnv
env = GymEnv("MountainCarContinuous-v0", device="cpu")
Step 2: Define how many intervals we want to discretize each action dimension into
action_dis_bins = torch.tensor([5])  # Discretizing into 5 intervals for each action dimension
Step 3: Apply ActionDiscretizer transform to discretize the action space
action_discretizer = ActionDiscretizer(
num_intervals=action_dis_bins,
categorical=True,
sampling=ActionDiscretizer.SamplingStrategy.MEDIAN,
out_action_key="action_discrete"  # Discretized actions will be stored under this key
)
Step 4: Append the discretizer to the environment
env = env.append_transform(action_discretizer)
Step 5: Reset the environment to get initial observations in a TensorDict
tensordict = env.rollout(1)
print(tensordict, tensordict['action'], tensordict['action_discrete'])
Create a new tensordict with the same batch size and device as the environment
new_tensordict = TensorDict(
{
"observation": tensordict["observation"],
"action": tensordict["action"],
"action_discrete": tensordict["action_discrete"],
},
# batch_size=torch.Size[1],
device=tensordict.device
)
Step 7: Take an environment step using this tensordict with discretized actions
print("tensordict is : ",new_tensordict)
next_tensordict = env.step(new_tensordict)
Step 8: Print out next state information
print(next_tensordict)`
#######################OUTPUT#################
TensorDict(
fields={
action: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.float32, is_shared=False),
action_discrete: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.int64, is_shared=False),
done: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False),
next: TensorDict(
fields={
done: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False),
observation: Tensor(shape=torch.Size([1, 2]), device=cpu, dtype=torch.float32, is_shared=False),
reward: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.float32, is_shared=False),
terminated: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False),
truncated: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False)},
batch_size=torch.Size([1]),
device=cpu,
is_shared=False),
observation: Tensor(shape=torch.Size([1, 2]), device=cpu, dtype=torch.float32, is_shared=False),
terminated: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False),
truncated: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.bool, is_shared=False)},
batch_size=torch.Size([1]),
device=cpu,
is_shared=False) tensor([[0.8000]]) tensor([[4]])
tensordict is :  TensorDict(
fields={
action: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.float32, is_shared=False),
action_discrete: Tensor(shape=torch.Size([1, 1]), device=cpu, dtype=torch.int64, is_shared=False),
observation: Tensor(shape=torch.Size([1, 2]), device=cpu, dtype=torch.float32, is_shared=False)},
batch_size=torch.Size([]),
device=cpu,
is_shared=False)
############ERROR happens on the  "env.step" line
Error log:

`RuntimeError                              Traceback (most recent call last)
Cell In[19], line 41
39 # Step 7: Take an environment step using this tensordict with discretized actions
40 print("tensordict is : ",new_tensordict)
---> 41 next_tensordict = env.step(new_tensordict)
43 # Step 8: Print out next state information
44 print(next_tensordict)
File ~/scratch_softlink/transferRL/metaworld/lib/python3.9/site-packages/torchrl/envs/common.py:1483, in EnvBase.step(self, tensordict)
1480 self._assert_tensordict_shape(tensordict)
1481 next_preset = tensordict.get("next", None)
-> 1483 next_tensordict = self._step(tensordict)
1484 next_tensordict = self._step_proc_data(next_tensordict)
1485 if next_preset is not None:
1486     # tensordict could already have a "next" key
1487     # this could be done more efficiently by not excluding but just passing
1488     # the necessary keys
File ~/scratch_softlink/transferRL/metaworld/lib/python3.9/site-packages/torchrl/envs/transforms/transforms.py:778, in TransformedEnv._step(self, tensordict)
774 def _step(self, tensordict: TensorDictBase) -> TensorDictBase:
775     # No need to clone here because inv does it already
776     # tensordict = tensordict.clone(False)
777     next_preset = tensordict.get("next", None)
--> 778     tensordict_in = self.transform.inv(tensordict)
779     next_tensordict = self.base_env._step(tensordict_in)
780     if next_preset is not None:
781         # tensordict could already have a "next" key
782         # this could be done more efficiently by not excluding but just passing
783         # the necessary keys
File ~/scratch_softlink/transferRL/metaworld/lib/python3.9/site-packages/torchrl/envs/transforms/transforms.py:8592, in ActionDiscretizer.inv(self, tensordict)
8590     return super().inv(tensordict)
8591 # We re-write this because we don't want to clone the TD here
-> 8592 return self._inv_call(tensordict)
File ~/scratch_softlink/transferRL/metaworld/lib/python3.9/site-packages/torchrl/envs/transforms/transforms.py:8607, in ActionDiscretizer._inv_call(self, tensordict)
8604         action = intervals.gather(index=action, dim=-1).squeeze(-1)
8605     else:
8606         action = torch.stack(
-> 8607             [
8608                 interval.gather(index=action, dim=-1).squeeze(-1)
8609                 for interval, action in zip(intervals, action.unbind(-2))
8610             ],
8611             -1,
8612         )
8613 else:
8614     nvec = self.nvec.tolist()
File ~/scratch_softlink/transferRL/metaworld/lib/python3.9/site-packages/torchrl/envs/transforms/transforms.py:8608, in (.0)
8604         action = intervals.gather(index=action, dim=-1).squeeze(-1)
8605     else:
8606         action = torch.stack(
8607             [
-> 8608                 interval.gather(index=action, dim=-1).squeeze(-1)
8609                 for interval, action in zip(intervals, action.unbind(-2))
8610             ],
8611             -1,
8612         )
8613 else:
8614     nvec = self.nvec.tolist()
RuntimeError: Index tensor must have the same number of dimensions as input tensor
3`


client-gen tag format has changed.

Here is a failing log:
failed to run client-gen for unversioned APIs panic: +genclient=[true] is invalid, use //+genclient if you want to generate client or omit it when you want to disable generation

It looks +genclient=[true] should be replaced with +genclient instead now.

How did you get this error?

It is reported by the latest client-gen: https://github.com/kubernetes/code-generator/tree/master/cmd
when running apiserver-boot build generated for one apiserver-boot generated project.

What is the version you downloaded?  The client-gen is vendored.  Are you currently experiencing this, or is it just to track needing to do this when we update the vendored code?

Ah, I didn't notice the tools are built-in in this project.

btw, I downloaded apiserver-builder-v0.1-alpha.15-linux-amd64.tar.gz from releases, but always get the error apiserver-boot: cannot execute binary file: Exec format error. I doubt the binary files are not correct.
apiserver-builder-v0.1-alpha.14-linux-amd64.tar.gz is ok.

@yaxinlx Thanks for noticing, it looks like there is an issue with the release script cross compiling.
#153 Will look into this over the weekend.


Security support

User should assume a role with the authentication to make all the AWS calls

More details about this topic: https://docs.aws.amazon.com/AmazonS3/latest/dev/AuthUsingTempSessionTokenJava.html


Duplicate compilation of f2j

But right despite many attempts I haven't found a way to avoid that because I suspect a Cabal bug prevents linking an executable involving deriving (...,Data,Typeable). But that deriving clause is required for using Neil Mitchell's CmdArgs library, which we use to implement the command-line interface.
This significance of this issue is that it slows down development cycle. It has caused ~3x time in building our project (the library x 1, f2j x 1, and f2ji x 1). Ideally, f2j and f2ji will depend on the library and hence in comparison building time will be just 1x.
Attached is the output of the last few lines when you try make. Can be duplicated on Weixin's machine (OS X?).
Loading package fcore-0.1.0 ... <command line>: can't load .so/.DLL for: /home/george/Code/fcore/dist/build/libHSfcore-0.1.0-ghc7.8.3.so (/home/george/Code/fcore/dist/build/libHSfcore-0.1.0-ghc7.8.3.so: undefined symbol: fcorezm0zi1zi0_Src_Bool_con_info)

Solved entirely since commit 211595effa964c0e9f273b54cdc628e9d8ddeec0.


Origin, Destination, Line, ETA, Mapbox, and Website

Is it possible to put this map on my personal website (github pages)? If so, how would I integrate it? (for example, I would like a full page on my personal website that I could go to that shows my live flight. When not connected, it's just an empty page that says "next flight on ")
Is it possible to add a line showing the path from the origin airport to the destination airport?
Can there be data somewhere on the screen that shows the ETA?
If I add my mapbox token, what can I do with that and how would I do it? Could you provide an example(s)?

thanks for making this. I like it.

Thank you very much for your message.

I actually thought about something similar but didn't proceed with it due to the lack of time. But I totally agree, it would be nice to integrate a map on one's personal website and show the live flight. I will definitely add this to my reasearch list since I'm also very interested in this.

Yes, I think it would be possible to add a line from the origin airport to the destination airport. (I already have "display flight path" on my list...)

It's also possible to add the "enroute time estimate" (GPS ETE) and "enroute time actual" (GPS ETA). Maybe there is also an option to add an "Estimated time of Arrival". Great idea!

If you add your own Mapbox token, you don't have to share the built-in token with other users. Which means that you are less likely to run into a situation where your Mapbox usage will be limited. (I have no clue how many people are using this program with Mapbox, though).

The built-in token is using the free tier, so the requests per day are limited (https://www.mapbox.com/pricing/).
Example:
http://localhost:8888/?mapbox_token=Y0UrSuP3Rs3cR3Tm4pB0Xt0k3n

I will add your requests to my todo list. Point 2) and 3) can be done pretty quickly. Regarding 1) I cannot promise anything at the moment, since it will take some time for me to evaluate this point. (Sorry about that!)
Nonetheless, thank you for using GoPilot, I really appreciate it!
If you have more ideas for features, improvements or whatsoever, please let me know.
Best,
Sascha

ty


Evaluate openstates data as an alternative to malegislature API

https://openstates.org/ma
It scrapes data from the malegislature website's html pages rather than the api, so may provide more complete content.

Events: while there is an experimental events endpoint, it does not seem to work and not for MA.
People: government officials are maintained in a github repo and exposed by the API. it covers more people than the list of legislators from the maleg API.
Bills: only limited amounts of data are scraped for the bill, in particular the bill text is not scraped. It does track the latest activity on the bill.
Search: We can search for people and bills by text strings, and can search for people by geo coordinates. This is much better than our capabilities with firestore.

I think we should continue with our API scrapers for v2 and evaluate integrating with openstates feature-by-feature for the next iteration.


NSwagStudio & Cmd Line: Support .NET Core assemblies [on hold]

I am using core dnx web project and with dnx all references are not copied. Unfortunately studio seems to be ignroing the "Path to search for referenced assembly" I cannot load web api, because it doesn't find dependencies. If I copy core.dll into the API directory it can find it, but then it cannot find any nuget packages, so it's not an option.

Did you follow the instructions here: https://github.com/NSwag/NSwag/wiki/WebApiAssemblyToSwaggerGenerator
?

Yes, I tried it too (First). It couldn't find core.dll. I guess I moved too soon to root package directory. Because, I just tried it now (it's still doesn't find core.dll), but if I copy it into the folder  manually. Now it finds .net assemblies fine.

Yes, its a little strange for .NET Core as not everything is copied into one output directory... Is this issue solved?

well, no it's still cannot get dll from the reference path.
http://screencloud.net/v/mL96

Can you provide a sample project?

Im just trying to load a .net core project, but with rc2 it no longer works... have to investigate further

It seems that with RC2, .NET Core assemblies can no longer be loaded in a full .NET 4.6 process... I will wait until .NET Core and .NET 4.6.2 is released and try again when everything is stable...
Until then, you can install the new .NET Core middlewares in your project and serve the Swagger spec directly from your project: https://github.com/NSwag/NSwag/wiki/OwinMiddleware
After starting the web project, open NSwagStudio and load the Swagger spec via URL:

.Net core 1.0 assemblies require .net standard 1.6 and it seems that only .Net 4.6.3 will support that...

With v6.2 .NET Core support is now working in NSwagStudio and the command line tools.
Fix: https://github.com/NSwag/NSwag/commit/507f4b917d567fcf6fba9be8a48afd89d6836ced

Updated wiki: https://github.com/NSwag/NSwag/wiki/WebApiAssemblyToSwaggerGenerator#net-core

Still issues with .NET Core system NuGet packages: BadFormatException
Maybe try debug publish?

Updated wiki with a way to load .net core libs


JaegerContainer - useOtlpCollector default change proposal

Currently JaegerContainer interface defaults useOtlpCollector to false.
https://github.com/quarkus-qe/quarkus-test-framework/blob/main/quarkus-test-service-jaeger/src/main/java/io/quarkus/test/services/JaegerContainer.java#L32
Upstream moves away from direct rest point usage - OpenTelemetry Jaeger exporter moved to Quarkiverse in 2.14, OpenTracing is marked as deprecated, and the path forward is using OTLP.
I propose to change the useOtlpCollectordefault totrue`.  It should make the experience with our framework a bit better.
I've hit the trouble when enhancing OpenTelemetry coverage and it took some time to realize that I need to have @JaegerContainer(useOtlpCollector = true)
@mjurc @pjgg fyi

This should be implemented on main.


change cookie domain documentation

Change cookie domain documentation after #2722 explanation.
I didn't go over the checklist since it's only a small documentation change.

Please rebase this to 2.3.x, docs fixes should be made against the latest feature branch.

You'll need to rebase and force push to change the base, not only change the PR target.
$ git rebase --onto origin/2.3.x origin/main
$ git push -f