[BUG]-Dledger ： logic queue order maybe wrong

一.基本信息
版本: 4.5.1
部署模式: Dledger
部署状况: 1个broker，broker包含3个rocketmq节点
配置文件:
1. 节点1配置文件
   fileReservedTime=72
   autoCreateTopicEnable=false
   autoCreateSubscriptionGroup=false
   flushDiskType=SYNC_FLUSH
   brokerRole=SYNC_MASTER
   brokerClusterName = c1
   brokerName=c1b1
   listenPort=30911
   storePathRootDir=/home/rocketmq/store/node00
   storePathCommitLog=/home/rocketmq/store/node00/commitlog
   enableDLegerCommitLog=true
   dLegerGroup=RaftNode01
   dLegerPeers=n0-<IP_ADDRESS>:40911;n1-<IP_ADDRESS>:40911;n2-<IP_ADDRESS>:40911
   dLegerSelfId=n0
   sendMessageThreadPoolNums=64
   queryMessageThreadPoolNums=16
   pullMessageThreadPoolNums=64
   useEpollNativeSelector=true
   useReentrantLockWhenPutMessage=true

2. 节点2配置文件
    fileReservedTime=72
    autoCreateTopicEnable=false
    autoCreateSubscriptionGroup=false
    flushDiskType=SYNC_FLUSH
    brokerRole=SYNC_MASTER
    brokerClusterName = c1
    brokerName=c1b1
    listenPort=30911
    storePathRootDir=/home/rocketmq/store/node00
    storePathCommitLog=/home/rocketmq/store/node00/commitlog
    enableDLegerCommitLog=true
    dLegerGroup=RaftNode01
    dLegerPeers=n0-<IP_ADDRESS>:40911;n1-<IP_ADDRESS>:40911;n2-<IP_ADDRESS>:40911
    dLegerSelfId=n1
    sendMessageThreadPoolNums=64
    queryMessageThreadPoolNums=16
    pullMessageThreadPoolNums=64
    useEpollNativeSelector=true
    useReentrantLockWhenPutMessage=true

3. 节点3配置文件
fileReservedTime=72
    autoCreateTopicEnable=false
    autoCreateSubscriptionGroup=false
    flushDiskType=SYNC_FLUSH
    brokerRole=SYNC_MASTER
    brokerClusterName = c1
    brokerName=c1b1
    listenPort=30911
    storePathRootDir=/home/rocketmq/store/node00
    storePathCommitLog=/home/rocketmq/store/node00/commitlog
    enableDLegerCommitLog=true
    dLegerGroup=RaftNode01
    dLegerPeers=n0-<IP_ADDRESS>:40911;n1-<IP_ADDRESS>:40911;n2-<IP_ADDRESS>:40911
    dLegerSelfId=n2
    sendMessageThreadPoolNums=64
    queryMessageThreadPoolNums=16
    pullMessageThreadPoolNums=64
    useEpollNativeSelector=true
    useReentrantLockWhenPutMessage=true

二.异常情况
1.异常说明:
异常发生在n1节点上，异常日志位于storeerror.log:
[2019-08-16 15:13:59.817] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 247183480 currentLogicOffset: 247183460 Topic: DD_SYNC_SUB QID: 11 Diff: 20
[2019-08-16 15:13:59.818] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 247183500 currentLogicOffset: 247183480 Topic: DD_SYNC_SUB QID: 11 Diff: 20
[2019-08-16 15:13:59.820] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 247183520 currentLogicOffset: 247183500 Topic: DD_SYNC_SUB QID: 11 Diff: 20
[2019-08-16 15:13:59.860] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 244686580 currentLogicOffset: 244686560 Topic: LY_SUB QID: 1 Diff: 20
[2019-08-16 15:13:59.871] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 247181980 currentLogicOffset: 247181960 Topic: DD_SYNC_SUB QID: 0 Diff: 20
[2019-08-16 15:13:59.874] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 247183060 currentLogicOffset: 247183040 Topic: DD_SYNC_SUB QID: 3 Diff: 20
[2019-08-16 15:13:59.888] WARN ReputMessageService - [BUG]logic queue order maybe wrong, expectLogicOffset: 244686600 currentLogicOffset: 244686580 Topic: LY_SUB QID: 1 Diff: 20

2.可能的原因:
n1节点的机器发生过宕机,宕机时间段为 2019-8-03 16:16:40 ~  2019-8-03 17:08:00 。由于是16日发现的异常，发现时间较晚，8月3日的日志已清除了。无法追溯当时恢复时的状况。
3.尝试解决的方法:
(1) 对n1节点进行重启，发现启动恢复过程后，日常日志仍存在。下面为启动过程中数据恢复日志:
[2019-08-18 21:14:54.429] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/%RETRY%DD_SYNC_CG/0/00000000000024000000 0 0 0
[2019-08-18 21:14:54.430] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/%RETRY%DD_SYNC_CG/0/00000000000024000000 28271400
[2019-08-18 21:14:54.434] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/2/00000000000000000000 0 0 0
[2019-08-18 21:14:54.434] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/2/00000000000000000000 4406240
[2019-08-18 21:14:54.435] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/3/00000000000000000000 0 0 0
[2019-08-18 21:14:54.435] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/3/00000000000000000000 838700
[2019-08-18 21:14:54.437] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/4/00000000000000000000 0 0 0
[2019-08-18 21:14:54.437] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/4/00000000000000000000 798960
[2019-08-18 21:14:54.438] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/5/00000000000000000000 0 0 0
[2019-08-18 21:14:54.438] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/5/00000000000000000000 818040
[2019-08-18 21:14:54.439] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/6/00000000000000000000 0 0 0
[2019-08-18 21:14:54.439] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/6/00000000000000000000 854180
[2019-08-18 21:14:54.440] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/7/00000000000000000000 0 0 0
[2019-08-18 21:14:54.440] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/7/00000000000000000000 919960
[2019-08-18 21:14:54.442] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/8/00000000000000000000 0 0 0
[2019-08-18 21:14:54.442] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/8/00000000000000000000 1429200
[2019-08-18 21:14:54.444] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/9/00000000000000000000 0 0 0
[2019-08-18 21:14:54.444] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/9/00000000000000000000 1496860
[2019-08-18 21:14:54.446] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/10/00000000000000000000 0 0 0
[2019-08-18 21:14:54.446] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/10/00000000000000000000 1585000
[2019-08-18 21:14:54.448] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/11/00000000000000000000 0 0 0
[2019-08-18 21:14:54.448] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/11/00000000000000000000 1682000
[2019-08-18 21:14:54.450] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/12/00000000000000000000 0 0 0
[2019-08-18 21:14:54.451] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/12/00000000000000000000 1791980
[2019-08-18 21:14:54.453] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/13/00000000000000000000 0 0 0
[2019-08-18 21:14:54.453] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/13/00000000000000000000 1920000
[2019-08-18 21:14:54.456] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/14/00000000000000000000 0 0 0
[2019-08-18 21:14:54.456] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/14/00000000000000000000 1978020
[2019-08-18 21:14:54.458] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/15/00000000000000000000 0 0 0
[2019-08-18 21:14:54.458] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/15/00000000000000000000 2032680
[2019-08-18 21:14:54.459] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/16/00000000000000000000 0 0 0
[2019-08-18 21:14:54.459] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/16/00000000000000000000 2081820
[2019-08-18 21:14:54.460] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/17/00000000000000000000 0 0 0
[2019-08-18 21:14:54.460] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/SCHEDULE_TOPIC_XXXX/17/00000000000000000000 4304240
[2019-08-18 21:14:54.462] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/0/00000000000252000000
[2019-08-18 21:14:54.479] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/0/00000000000258000000
[2019-08-18 21:14:54.498] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/0/00000000000258000000 0 0 0
[2019-08-18 21:14:54.498] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/0/00000000000258000000 262186580
[2019-08-18 21:14:54.524] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/1/00000000000252000000
[2019-08-18 21:14:54.526] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/1/00000000000258000000
[2019-08-18 21:14:54.528] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/1/00000000000258000000 0 0 0
[2019-08-18 21:14:54.528] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/1/00000000000258000000 262187460
[2019-08-18 21:14:54.529] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/2/00000000000252000000
[2019-08-18 21:14:54.531] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/2/00000000000258000000
[2019-08-18 21:14:54.532] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/2/00000000000258000000 0 0 0
[2019-08-18 21:14:54.532] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/2/00000000000258000000 262186940
[2019-08-18 21:14:54.534] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/3/00000000000252000000
[2019-08-18 21:14:54.536] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/3/00000000000258000000
[2019-08-18 21:14:54.537] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/3/00000000000258000000 0 0 0
[2019-08-18 21:14:54.537] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/3/00000000000258000000 262187080
[2019-08-18 21:14:54.539] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/4/00000000000252000000
[2019-08-18 21:14:54.540] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/4/00000000000258000000
[2019-08-18 21:14:54.542] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/4/00000000000258000000 0 0 0
[2019-08-18 21:14:54.542] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/4/00000000000258000000 262185960
[2019-08-18 21:14:54.544] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/5/00000000000252000000
[2019-08-18 21:14:54.545] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/5/00000000000258000000
[2019-08-18 21:14:54.547] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/5/00000000000258000000 0 0 0
[2019-08-18 21:14:54.547] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/5/00000000000258000000 262187740
[2019-08-18 21:14:54.548] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/6/00000000000252000000
[2019-08-18 21:14:54.550] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/6/00000000000258000000
[2019-08-18 21:14:54.551] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/6/00000000000258000000 0 0 0
[2019-08-18 21:14:54.551] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/6/00000000000258000000 262189360
[2019-08-18 21:14:54.553] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/7/00000000000252000000
[2019-08-18 21:14:54.555] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/7/00000000000258000000
[2019-08-18 21:14:54.556] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/7/00000000000258000000 0 0 0
[2019-08-18 21:14:54.556] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/7/00000000000258000000 262187220
[2019-08-18 21:14:54.558] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/8/00000000000252000000
[2019-08-18 21:14:54.560] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/8/00000000000258000000
[2019-08-18 21:14:54.561] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/8/00000000000258000000 0 0 0
[2019-08-18 21:14:54.561] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/8/00000000000258000000 262187680
[2019-08-18 21:14:54.563] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/9/00000000000252000000
[2019-08-18 21:14:54.564] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/9/00000000000258000000
[2019-08-18 21:14:54.566] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/9/00000000000258000000 0 0 0
[2019-08-18 21:14:54.566] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/9/00000000000258000000 262188560
[2019-08-18 21:14:54.567] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/10/00000000000252000000
[2019-08-18 21:14:54.569] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/10/00000000000258000000
[2019-08-18 21:14:54.570] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/10/00000000000258000000 0 0 0
[2019-08-18 21:14:54.570] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/10/00000000000258000000 262187460
[2019-08-18 21:14:54.572] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/11/00000000000252000000
[2019-08-18 21:14:54.574] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/11/00000000000258000000
[2019-08-18 21:14:54.575] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/11/00000000000258000000 0 0 0
[2019-08-18 21:14:54.575] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/11/00000000000258000000 262187520
[2019-08-18 21:14:54.577] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/12/00000000000252000000
[2019-08-18 21:14:54.578] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/12/00000000000258000000
[2019-08-18 21:14:54.580] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/12/00000000000258000000 0 0 0
[2019-08-18 21:14:54.580] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/12/00000000000258000000 262187060
[2019-08-18 21:14:54.582] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/13/00000000000252000000
[2019-08-18 21:14:54.583] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/13/00000000000258000000
[2019-08-18 21:14:54.584] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/13/00000000000258000000 0 0 0
[2019-08-18 21:14:54.585] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/13/00000000000258000000 262186460
[2019-08-18 21:14:54.586] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/14/00000000000252000000
[2019-08-18 21:14:54.588] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/14/00000000000258000000
[2019-08-18 21:14:54.589] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/14/00000000000258000000 0 0 0
[2019-08-18 21:14:54.589] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/14/00000000000258000000 262185940
[2019-08-18 21:14:54.591] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/15/00000000000252000000
[2019-08-18 21:14:54.593] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/15/00000000000258000000
[2019-08-18 21:14:54.594] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/15/00000000000258000000 0 0 0
[2019-08-18 21:14:54.594] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/DD_SYNC_SUB/15/00000000000258000000 262184560
[2019-08-18 21:14:54.595] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/%RETRY%LY_SUB_CG/0/00000000000000000000 0 0 0
[2019-08-18 21:14:54.595] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/%RETRY%LY_SUB_CG/0/00000000000000000000 1693640
[2019-08-18 21:14:54.596] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/0/00000000000252000000
[2019-08-18 21:14:54.598] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/0/00000000000258000000
[2019-08-18 21:14:54.599] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/0/00000000000258000000 0 0 0
[2019-08-18 21:14:54.599] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/0/00000000000258000000 259639420
[2019-08-18 21:14:54.600] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/1/00000000000252000000
[2019-08-18 21:14:54.602] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/1/00000000000258000000
[2019-08-18 21:14:54.602] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/1/00000000000258000000 0 0 0
[2019-08-18 21:14:54.602] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/1/00000000000258000000 259639020
[2019-08-18 21:14:54.604] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/2/00000000000252000000
[2019-08-18 21:14:54.606] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/2/00000000000258000000
[2019-08-18 21:14:54.606] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/2/00000000000258000000 0 0 0
[2019-08-18 21:14:54.606] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/2/00000000000258000000 259639660
[2019-08-18 21:14:54.608] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/3/00000000000252000000
[2019-08-18 21:14:54.610] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/3/00000000000258000000
[2019-08-18 21:14:54.610] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/3/00000000000258000000 0 0 0
[2019-08-18 21:14:54.610] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/3/00000000000258000000 259639200
[2019-08-18 21:14:54.612] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/4/00000000000252000000
[2019-08-18 21:14:54.614] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/4/00000000000258000000
[2019-08-18 21:14:54.614] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/4/00000000000258000000 0 0 0
[2019-08-18 21:14:54.614] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/4/00000000000258000000 259638580
[2019-08-18 21:14:54.616] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/5/00000000000252000000
[2019-08-18 21:14:54.618] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/5/00000000000258000000
[2019-08-18 21:14:54.618] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/5/00000000000258000000 0 0 0
[2019-08-18 21:14:54.618] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/5/00000000000258000000 259638100
[2019-08-18 21:14:54.620] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/6/00000000000252000000
[2019-08-18 21:14:54.622] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/6/00000000000258000000
[2019-08-18 21:14:54.622] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/6/00000000000258000000 0 0 0
[2019-08-18 21:14:54.622] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/6/00000000000258000000 259638300
[2019-08-18 21:14:54.624] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/7/00000000000252000000
[2019-08-18 21:14:54.626] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/7/00000000000258000000
[2019-08-18 21:14:54.626] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/7/00000000000258000000 0 0 0
[2019-08-18 21:14:54.626] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/7/00000000000258000000 259639180
[2019-08-18 21:14:54.628] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/8/00000000000252000000
[2019-08-18 21:14:54.630] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/8/00000000000258000000
[2019-08-18 21:14:54.630] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/8/00000000000258000000 0 0 0
[2019-08-18 21:14:54.630] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/8/00000000000258000000 259638680
[2019-08-18 21:14:54.632] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/9/00000000000252000000
[2019-08-18 21:14:54.633] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/9/00000000000258000000
[2019-08-18 21:14:54.634] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/9/00000000000258000000 0 0 0
[2019-08-18 21:14:54.634] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/9/00000000000258000000 259638660
[2019-08-18 21:14:54.636] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/10/00000000000252000000
[2019-08-18 21:14:54.637] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/10/00000000000258000000
[2019-08-18 21:14:54.638] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/10/00000000000258000000 0 0 0
[2019-08-18 21:14:54.638] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/10/00000000000258000000 259640000
[2019-08-18 21:14:54.640] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/11/00000000000252000000
[2019-08-18 21:14:54.641] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/11/00000000000258000000
[2019-08-18 21:14:54.642] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/11/00000000000258000000 0 0 0
[2019-08-18 21:14:54.642] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/11/00000000000258000000 259639400
[2019-08-18 21:14:54.644] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/12/00000000000252000000
[2019-08-18 21:14:54.645] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/12/00000000000258000000
[2019-08-18 21:14:54.646] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/12/00000000000258000000 0 0 0
[2019-08-18 21:14:54.646] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/12/00000000000258000000 259638200
[2019-08-18 21:14:54.648] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/13/00000000000252000000
[2019-08-18 21:14:54.649] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/13/00000000000258000000
[2019-08-18 21:14:54.650] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/13/00000000000258000000 0 0 0
[2019-08-18 21:14:54.650] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/13/00000000000258000000 259638920
[2019-08-18 21:14:54.651] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/14/00000000000252000000
[2019-08-18 21:14:54.653] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/14/00000000000258000000
[2019-08-18 21:14:54.654] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/14/00000000000258000000 0 0 0
[2019-08-18 21:14:54.654] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/14/00000000000258000000 259638720
[2019-08-18 21:14:54.655] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/15/00000000000252000000
[2019-08-18 21:14:54.657] INFO main - recover next consume queue file, /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/15/00000000000258000000
[2019-08-18 21:14:54.658] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/15/00000000000258000000 0 0 0
[2019-08-18 21:14:54.658] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/EH_GM_LY_SUB/15/00000000000258000000 259638980
[2019-08-18 21:14:54.659] INFO main - recover current consume queue file over,  /home/rocketmq/store/node00/consumequeue/%DLQ%DD_SYNC_CG/0/00000000000000000000 0 0 0
[2019-08-18 21:14:54.659] INFO main - recover current consume queue queue over /home/rocketmq/store/node00/consumequeue/%DLQ%DD_SYNC_CG/0/00000000000000000000 2228340
[2019-08-18 21:14:54.660] INFO main - load /home/rocketmq/store/node00/commitlog/00000000442381631488 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000443455373312 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000444529115136 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000445602856960 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000446676598784 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000447750340608 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000448824082432 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000449897824256 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000450971566080 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000452045307904 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000453119049728 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000454192791552 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000455266533376 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000456340275200 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000457414017024 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000458487758848 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000459561500672 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000460635242496 OK
[2019-08-18 21:14:54.661] INFO main - load /home/rocketmq/store/node00/commitlog/00000000461708984320 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000462782726144 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000463856467968 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000464930209792 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000466003951616 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000467077693440 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000468151435264 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000469225177088 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000470298918912 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000471372660736 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000472446402560 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000473520144384 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000474593886208 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000475667628032 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000476741369856 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000477815111680 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000478888853504 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000479962595328 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000481036337152 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000482110078976 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000483183820800 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000484257562624 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000485331304448 OK
[2019-08-18 21:14:54.662] INFO main - load /home/rocketmq/store/node00/commitlog/00000000486405046272 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000487478788096 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000488552529920 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000489626271744 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000490700013568 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000491773755392 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/commitlog/00000000492847497216 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012079595520 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012247367680 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012415139840 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012582912000 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012750684160 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000012918456320 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000013086228480 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000013254000640 OK
[2019-08-18 21:14:54.663] INFO main - load /home/rocketmq/store/node00/dledger-n1/index/00000000013421772800 OK
[2019-08-18 21:14:54.665] INFO main - Begin to recover data from entryIndex=418595783 fileIndex=45 fileSize=48 fileName=/home/rocketmq/store/node00/commitlog/00000000490700013568
[2019-08-18 21:14:55.416] INFO main - Trying to recover data file /home/rocketmq/store/node00/commitlog/00000000491773755392
[2019-08-18 21:14:57.167] INFO main - Trying to recover data file /home/rocketmq/store/node00/commitlog/00000000492847497216
[2019-08-18 21:14:58.515] INFO main - Recover data file to the end of /home/rocketmq/store/node00/commitlog/00000000492847497216
io.openmessaging.storage.dledger.exception.DLedgerException: [code=414,name=DISK_ERROR,desc=] pos 0 !=<PHONE_NUMBER>54
	at io.openmessaging.storage.dledger.utils.PreConditions.check(PreConditions.java:41) ~[dledger-0.1.jar:na]
	at io.openmessaging.storage.dledger.store.file.DLedgerMmapFileStore.recover(DLedgerMmapFileStore.java:216) ~[dledger-0.1.jar:na]
	at org.apache.rocketmq.store.dledger.DLedgerCommitLog.recover(DLedgerCommitLog.java:266) [rocketmq-store-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.store.dledger.DLedgerCommitLog.recoverAbnormally(DLedgerCommitLog.java:323) [rocketmq-store-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.store.DefaultMessageStore.recover(DefaultMessageStore.java:1334) [rocketmq-store-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.store.DefaultMessageStore.load(DefaultMessageStore.java:197) [rocketmq-store-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.broker.BrokerController.initialize(BrokerController.java:256) [rocketmq-broker-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.broker.BrokerStartup.createBrokerController(BrokerStartup.java:218) [rocketmq-broker-4.5.1.jar:4.5.1]
	at org.apache.rocketmq.broker.BrokerStartup.main(BrokerStartup.java:58) [rocketmq-broker-4.5.1.jar:4.5.1]
[2019-08-18 21:14:58.516] INFO main - Recover data to the end entryIndex=420517397 processOffset=492973339454 lastFileOffset=492847497216 cha=125842238
[2019-08-18 21:14:58.523] INFO main - Recover to get committed index=420517340 from checkpoint
[2019-08-18 21:14:58.535] INFO main - Compute logical min offset: 1400522, topic: %RETRY%DD_SYNC_CG, queueId: 0
[2019-08-18 21:14:58.538] INFO main - Compute logical min offset: 209837, topic: SCHEDULE_TOPIC_XXXX, queueId: 2
[2019-08-18 21:14:58.539] INFO main - Compute logical min offset: 41820, topic: SCHEDULE_TOPIC_XXXX, queueId: 3
[2019-08-18 21:14:58.540] INFO main - Compute logical min offset: 39851, topic: SCHEDULE_TOPIC_XXXX, queueId: 4
[2019-08-18 21:14:58.541] INFO main - Compute logical min offset: 40806, topic: SCHEDULE_TOPIC_XXXX, queueId: 5
[2019-08-18 21:14:58.542] INFO main - Compute logical min offset: 42613, topic: SCHEDULE_TOPIC_XXXX, queueId: 6
[2019-08-18 21:14:58.543] INFO main - Compute logical min offset: 45902, topic: SCHEDULE_TOPIC_XXXX, queueId: 7
[2019-08-18 21:14:58.545] INFO main - Compute logical min offset: 71268, topic: SCHEDULE_TOPIC_XXXX, queueId: 8
[2019-08-18 21:14:58.546] INFO main - Compute logical min offset: 74651, topic: SCHEDULE_TOPIC_XXXX, queueId: 9
[2019-08-18 21:14:58.548] INFO main - Compute logical min offset: 79058, topic: SCHEDULE_TOPIC_XXXX, queueId: 10
[2019-08-18 21:14:58.550] INFO main - Compute logical min offset: 83908, topic: SCHEDULE_TOPIC_XXXX, queueId: 11
[2019-08-18 21:14:58.552] INFO main - Compute logical min offset: 89407, topic: SCHEDULE_TOPIC_XXXX, queueId: 12
[2019-08-18 21:14:58.554] INFO main - Compute logical min offset: 95780, topic: SCHEDULE_TOPIC_XXXX, queueId: 13
[2019-08-18 21:14:58.554] INFO main - Compute logical min offset: 98681, topic: SCHEDULE_TOPIC_XXXX, queueId: 14
[2019-08-18 21:14:58.554] INFO main - Compute logical min offset: 101414, topic: SCHEDULE_TOPIC_XXXX, queueId: 15
[2019-08-18 21:14:58.555] INFO main - Compute logical min offset: 103873, topic: SCHEDULE_TOPIC_XXXX, queueId: 16
[2019-08-18 21:14:58.555] INFO main - Compute logical min offset: 214774, topic: SCHEDULE_TOPIC_XXXX, queueId: 17
[2019-08-18 21:14:58.647] INFO main - Compute logical min offset: 11789593, topic: DD_SYNC_SUB, queueId: 0
[2019-08-18 21:14:58.719] INFO main - Compute logical min offset: 11789640, topic: DD_SYNC_SUB, queueId: 1
[2019-08-18 21:14:58.846] INFO main - Compute logical min offset: 11789624, topic: DD_SYNC_SUB, queueId: 2
[2019-08-18 21:14:58.966] INFO main - Compute logical min offset: 11789643, topic: DD_SYNC_SUB, queueId: 3
[2019-08-18 21:14:59.104] INFO main - Compute logical min offset: 11789608, topic: DD_SYNC_SUB, queueId: 4
[2019-08-18 21:14:59.244] INFO main - Compute logical min offset: 11789691, topic: DD_SYNC_SUB, queueId: 5
[2019-08-18 21:14:59.370] INFO main - Compute logical min offset: 11789762, topic: DD_SYNC_SUB, queueId: 6
[2019-08-18 21:14:59.462] INFO main - Compute logical min offset: 11789645, topic: DD_SYNC_SUB, queueId: 7
[2019-08-18 21:14:59.565] INFO main - Compute logical min offset: 11789658, topic: DD_SYNC_SUB, queueId: 8
[2019-08-18 21:14:59.660] INFO main - Compute logical min offset: 11789690, topic: DD_SYNC_SUB, queueId: 9
[2019-08-18 21:14:59.776] INFO main - Compute logical min offset: 11789668, topic: DD_SYNC_SUB, queueId: 10
[2019-08-18 21:14:59.896] INFO main - Compute logical min offset: 11789674, topic: DD_SYNC_SUB, queueId: 11
[2019-08-18 21:14:59.993] INFO main - Compute logical min offset: 11789626, topic: DD_SYNC_SUB, queueId: 12
[2019-08-18 21:15:00.087] INFO main - Compute logical min offset: 11789597, topic: DD_SYNC_SUB, queueId: 13
[2019-08-18 21:15:00.155] INFO main - Compute logical min offset: 11789558, topic: DD_SYNC_SUB, queueId: 14
[2019-08-18 21:15:00.230] INFO main - Compute logical min offset: 11789488, topic: DD_SYNC_SUB, queueId: 15
[2019-08-18 21:15:00.231] INFO main - Compute logical min offset: 84575, topic: %RETRY%LY_SUB_CG, queueId: 0
[2019-08-18 21:15:00.477] INFO main - Compute logical min offset: 11674531, topic: EH_GM_LY_SUB, queueId: 0
[2019-08-18 21:15:00.743] INFO main - Compute logical min offset: 11674503, topic: EH_GM_LY_SUB, queueId: 1
[2019-08-18 21:15:01.029] INFO main - Compute logical min offset: 11674550, topic: EH_GM_LY_SUB, queueId: 2
[2019-08-18 21:15:01.270] INFO main - Compute logical min offset: 11674512, topic: EH_GM_LY_SUB, queueId: 3
[2019-08-18 21:15:01.530] INFO main - Compute logical min offset: 11674499, topic: EH_GM_LY_SUB, queueId: 4
[2019-08-18 21:15:01.853] INFO main - Compute logical min offset: 11674490, topic: EH_GM_LY_SUB, queueId: 5
[2019-08-18 21:15:02.180] INFO main - Compute logical min offset: 11674525, topic: EH_GM_LY_SUB, queueId: 6
[2019-08-18 21:15:02.452] INFO main - Compute logical min offset: 11674546, topic: EH_GM_LY_SUB, queueId: 7
[2019-08-18 21:15:02.691] INFO main - Compute logical min offset: 11674510, topic: EH_GM_LY_SUB, queueId: 8
[2019-08-18 21:15:02.958] INFO main - Compute logical min offset: 11674506, topic: EH_GM_LY_SUB, queueId: 9
[2019-08-18 21:15:03.227] INFO main - Compute logical min offset: 11674583, topic: EH_GM_LY_SUB, queueId: 10
[2019-08-18 21:15:03.478] INFO main - Compute logical min offset: 11674585, topic: EH_GM_LY_SUB, queueId: 11
[2019-08-18 21:15:03.728] INFO main - Compute logical min offset: 11674522, topic: EH_GM_LY_SUB, queueId: 12
[2019-08-18 21:15:03.985] INFO main - Compute logical min offset: 11674560, topic: EH_GM_LY_SUB, queueId: 13
[2019-08-18 21:15:04.193] INFO main - Compute logical min offset: 11674503, topic: EH_GM_LY_SUB, queueId: 14
[2019-08-18 21:15:04.459] INFO main - Compute logical min offset: 11674504, topic: EH_GM_LY_SUB, queueId: 15
[2019-08-18 21:15:04.459] INFO main - Compute logical min offset: 111201, topic: %DLQ%DD_SYNC_CG, queueId: 0
[2019-08-18 21:15:04.459] INFO main - load over, and the max phy offset =<PHONE_NUMBER>34
[2019-08-18 21:15:04.473] INFO main - Server is running in TLS permissive mode
[2019-08-18 21:15:04.473] INFO main - Tls config file doesn't exist, skip it
[2019-08-18 21:15:04.473] INFO main - Log the final used tls related configuration
[2019-08-18 21:15:04.473] INFO main - tls.test.mode.enable = true
[2019-08-18 21:15:04.473] INFO main - tls.server.need.client.auth = none
[2019-08-18 21:15:04.473] INFO main - tls.server.keyPath = null
[2019-08-18 21:15:04.473] INFO main - tls.server.keyPassword = null
[2019-08-18 21:15:04.473] INFO main - tls.server.certPath = null
[2019-08-18 21:15:04.474] INFO main - tls.server.authClient = false
[2019-08-18 21:15:04.474] INFO main - tls.server.trustCertPath = null
[2019-08-18 21:15:04.474] INFO main - tls.client.keyPath = null
[2019-08-18 21:15:04.474] INFO main - tls.client.keyPassword = null
[2019-08-18 21:15:04.474] INFO main - tls.client.certPath = null
[2019-08-18 21:15:04.474] INFO main - tls.client.authServer = false
[2019-08-18 21:15:04.474] INFO main - tls.client.trustCertPath = null
[2019-08-18 21:15:04.474] INFO main - Using OpenSSL provider
[2019-08-18 21:15:04.496] INFO main - SSLContext created for server
[2019-08-18 21:15:04.497] INFO main - Server is running in TLS permissive mode
[2019-08-18 21:15:04.497] INFO main - Tls config file doesn't exist, skip it
[2019-08-18 21:15:04.497] INFO main - Log the final used tls related configuration
[2019-08-18 21:15:04.497] INFO main - tls.test.mode.enable = true
[2019-08-18 21:15:04.497] INFO main - tls.server.need.client.auth = none
[2019-08-18 21:15:04.497] INFO main - tls.server.keyPath = null
[2019-08-18 21:15:04.497] INFO main - tls.server.keyPassword = null
[2019-08-18 21:15:04.497] INFO main - tls.server.certPath = null
[2019-08-18 21:15:04.497] INFO main - tls.server.authClient = false
[2019-08-18 21:15:04.497] INFO main - tls.server.trustCertPath = null
[2019-08-18 21:15:04.497] INFO main - tls.client.keyPath = null
[2019-08-18 21:15:04.497] INFO main - tls.client.keyPassword = null
[2019-08-18 21:15:04.497] INFO main - tls.client.certPath = null
[2019-08-18 21:15:04.497] INFO main - tls.client.authServer = false
[2019-08-18 21:15:04.497] INFO main - tls.client.trustCertPath = null
[2019-08-18 21:15:04.497] INFO main - Using OpenSSL provider
[2019-08-18 21:15:04.521] INFO main - SSLContext created for server
[2019-08-18 21:15:04.529] INFO main - name server address updated. NEW : [saas-ff8bb063-ns-0.saas-ff8bb063-ns:9876, saas-ff8bb063-ns-1.saas-ff8bb063-ns:9876] , OLD: null
[2019-08-18 21:15:04.529] INFO main - Set user specified name server address: saas-ff8bb063-ns-0.saas-ff8bb063-ns:9876;saas-ff8bb063-ns-1.saas-ff8bb063-ns:9876
[2019-08-18 21:15:04.534] WARN main - Load default transaction message hook service: TransactionalMessageServiceImpl
[2019-08-18 21:15:04.534] WARN main - Load default discard message hook service: DefaultTransactionalMessageCheckListener
[2019-08-18 21:15:04.534] INFO main - The broker dose not enable acl
[2019-08-18 21:15:04.534] INFO main - Looking for a resource file of name [META-INF/service/org.apache.rocketmq.remoting.RPCHook] ...
[2019-08-18 21:15:04.535] WARN main - No resource file with name [META-INF/service/org.apache.rocketmq.remoting.RPCHook] found.
[2019-08-18 21:15:04.540] INFO main - [SetReputOffset] maxPhysicalPosInLogicQueue=492973338650 clMinOffset=442381631488 clMaxOffset=492973278534 clConfirmedOffset=492973278534
[2019-08-18 21:15:04.540] INFO main - Try to start service thread:ReputMessageService started:false lastThread:null
[2019-08-18 21:15:04.541] INFO ReputMessageService - ReputMessageService service started
[2019-08-18 21:15:04.541] INFO main - Compute logical min offset: 1400522, topic: %RETRY%DD_SYNC_CG, queueId: 0
[2019-08-18 21:15:04.542] INFO main - Compute logical min offset: 209837, topic: SCHEDULE_TOPIC_XXXX, queueId: 2
[2019-08-18 21:15:04.542] INFO main - Compute logical min offset: 41820, topic: SCHEDULE_TOPIC_XXXX, queueId: 3
[2019-08-18 21:15:04.542] INFO main - Compute logical min offset: 39851, topic: SCHEDULE_TOPIC_XXXX, queueId: 4
[2019-08-18 21:15:04.543] INFO main - Compute logical min offset: 40806, topic: SCHEDULE_TOPIC_XXXX, queueId: 5
[2019-08-18 21:15:04.543] INFO main - Compute logical min offset: 42613, topic: SCHEDULE_TOPIC_XXXX, queueId: 6
[2019-08-18 21:15:04.543] INFO main - Compute logical min offset: 45902, topic: SCHEDULE_TOPIC_XXXX, queueId: 7
[2019-08-18 21:15:04.543] INFO main - Compute logical min offset: 71268, topic: SCHEDULE_TOPIC_XXXX, queueId: 8
[2019-08-18 21:15:04.543] INFO main - Compute logical min offset: 74651, topic: SCHEDULE_TOPIC_XXXX, queueId: 9
[2019-08-18 21:15:04.544] INFO main - Compute logical min offset: 79058, topic: SCHEDULE_TOPIC_XXXX, queueId: 10
[2019-08-18 21:15:04.544] INFO main - Compute logical min offset: 83908, topic: SCHEDULE_TOPIC_XXXX, queueId: 11
[2019-08-18 21:15:04.544] INFO main - Compute logical min offset: 89407, topic: SCHEDULE_TOPIC_XXXX, queueId: 12
[2019-08-18 21:15:04.545] INFO main - Compute logical min offset: 95780, topic: SCHEDULE_TOPIC_XXXX, queueId: 13
[2019-08-18 21:15:04.545] INFO main - Compute logical min offset: 98681, topic: SCHEDULE_TOPIC_XXXX, queueId: 14
[2019-08-18 21:15:04.545] INFO main - Compute logical min offset: 101414, topic: SCHEDULE_TOPIC_XXXX, queueId: 15
[2019-08-18 21:15:04.546] INFO main - Compute logical min offset: 103873, topic: SCHEDULE_TOPIC_XXXX, queueId: 16
[2019-08-18 21:15:04.546] INFO main - Compute logical min offset: 214774, topic: SCHEDULE_TOPIC_XXXX, queueId: 17
[2019-08-18 21:15:04.547] INFO main - Compute logical min offset: 11789593, topic: DD_SYNC_SUB, queueId: 0
[2019-08-18 21:15:04.547] INFO main - Compute logical min offset: 11789640, topic: DD_SYNC_SUB, queueId: 1
[2019-08-18 21:15:04.547] INFO main - Compute logical min offset: 11789624, topic: DD_SYNC_SUB, queueId: 2
[2019-08-18 21:15:04.547] INFO main - Compute logical min offset: 11789643, topic: DD_SYNC_SUB, queueId: 3
[2019-08-18 21:15:04.548] INFO main - Compute logical min offset: 11789608, topic: DD_SYNC_SUB, queueId: 4
[2019-08-18 21:15:04.548] INFO main - Compute logical min offset: 11789691, topic: DD_SYNC_SUB, queueId: 5
[2019-08-18 21:15:04.548] INFO main - Compute logical min offset: 11789762, topic: DD_SYNC_SUB, queueId: 6
[2019-08-18 21:15:04.549] INFO main - Compute logical min offset: 11789645, topic: DD_SYNC_SUB, queueId: 7
[2019-08-18 21:15:04.549] INFO main - Compute logical min offset: 11789658, topic: DD_SYNC_SUB, queueId: 8
[2019-08-18 21:15:04.549] INFO main - Compute logical min offset: 11789690, topic: DD_SYNC_SUB, queueId: 9
[2019-08-18 21:15:04.549] INFO main - Compute logical min offset: 11789668, topic: DD_SYNC_SUB, queueId: 10
[2019-08-18 21:15:04.550] INFO main - Compute logical min offset: 11789674, topic: DD_SYNC_SUB, queueId: 11
[2019-08-18 21:15:04.550] INFO main - Compute logical min offset: 11789626, topic: DD_SYNC_SUB, queueId: 12
[2019-08-18 21:15:04.550] INFO main - Compute logical min offset: 11789597, topic: DD_SYNC_SUB, queueId: 13
[2019-08-18 21:15:04.551] INFO main - Compute logical min offset: 11789558, topic: DD_SYNC_SUB, queueId: 14
[2019-08-18 21:15:04.551] INFO main - Compute logical min offset: 11789488, topic: DD_SYNC_SUB, queueId: 15
[2019-08-18 21:15:04.551] INFO main - Compute logical min offset: 84575, topic: %RETRY%LY_SUB_CG, queueId: 0
[2019-08-18 21:15:04.552] INFO main - Compute logical min offset: 11674531, topic: EH_GM_LY_SUB, queueId: 0
[2019-08-18 21:15:04.553] INFO main - Compute logical min offset: 11674503, topic: EH_GM_LY_SUB, queueId: 1
[2019-08-18 21:15:04.554] INFO main - Compute logical min offset: 11674550, topic: EH_GM_LY_SUB, queueId: 2
[2019-08-18 21:15:04.554] INFO main - Compute logical min offset: 11674512, topic: EH_GM_LY_SUB, queueId: 3
[2019-08-18 21:15:04.555] INFO main - Compute logical min offset: 11674499, topic: EH_GM_LY_SUB, queueId: 4
[2019-08-18 21:15:04.556] INFO main - Compute logical min offset: 11674490, topic: EH_GM_LY_SUB, queueId: 5
[2019-08-18 21:15:04.557] INFO main - Compute logical min offset: 11674525, topic: EH_GM_LY_SUB, queueId: 6
[2019-08-18 21:15:04.558] INFO main - Compute logical min offset: 11674546, topic: EH_GM_LY_SUB, queueId: 7
[2019-08-18 21:15:04.558] INFO main - Compute logical min offset: 11674510, topic: EH_GM_LY_SUB, queueId: 8
[2019-08-18 21:15:04.559] INFO main - Compute logical min offset: 11674506, topic: EH_GM_LY_SUB, queueId: 9
[2019-08-18 21:15:04.560] INFO main - Compute logical min offset: 11674583, topic: EH_GM_LY_SUB, queueId: 10
[2019-08-18 21:15:04.561] INFO main - Compute logical min offset: 11674585, topic: EH_GM_LY_SUB, queueId: 11
[2019-08-18 21:15:04.562] INFO main - Compute logical min offset: 11674522, topic: EH_GM_LY_SUB, queueId: 12
[2019-08-18 21:15:04.562] INFO main - Compute logical min offset: 11674560, topic: EH_GM_LY_SUB, queueId: 13
[2019-08-18 21:15:04.563] INFO main - Compute logical min offset: 11674503, topic: EH_GM_LY_SUB, queueId: 14
[2019-08-18 21:15:04.564] INFO main - Compute logical min offset: 11674504, topic: EH_GM_LY_SUB, queueId: 15
[2019-08-18 21:15:04.564] INFO main - Compute logical min offset: 111201, topic: %DLQ%DD_SYNC_CG, queueId: 0
[2019-08-18 21:15:04.564] INFO main - Try to start service thread:FlushConsumeQueueService started:false lastThread:null

三. 寻求
1.导致触发这个Bug的原因可能有哪些?
2.这个异常有解决方法吗?

从恢复日志中看出，在执行org.apache.rocketmq.store.dledger.DLedgerCommitLog#recover方法时，dLedgerFileStore.recover() 发生了异常，导致不能执行后续的 super.recoverNormally(maxPhyOffsetOfConsumeQueue)。
恢复日志中异常日志:
[2019-08-18 21:14:58.515] INFO main - Recover data file to the end of /home/rocketmq/store/node00/commitlog/00000000492847497216
io.openmessaging.storage.dledger.exception.DLedgerException: [code=414,name=DISK_ERROR,desc=] pos 0 !=<PHONE_NUMBER>54
at io.openmessaging.storage.dledger.utils.PreConditions.check(PreConditions.java:41) ~[dledger-0.1.jar:na]
at io.openmessaging.storage.dledger.store.file.DLedgerMmapFileStore.recover(DLedgerMmapFileStore.java:216) ~[dledger-0.1.jar:na]
at org.apache.rocketmq.store.dledger.DLedgerCommitLog.recover(DLedgerCommitLog.java:266) [rocketmq-store-4.5.1.jar:4.5.1]
at org.apache.rocketmq.store.dledger.DLedgerCommitLog.recoverAbnormally(DLedgerCommitLog.java:323) [rocketmq-store-4.5.1.jar:4.5.1]
at org.apache.rocketmq.store.DefaultMessageStore.recover(DefaultMessageStore.java:1334) [rocketmq-store-4.5.1.jar:4.5.1]
at org.apache.rocketmq.store.DefaultMessageStore.load(DefaultMessageStore.java:197) [rocketmq-store-4.5.1.jar:4.5.1]
at org.apache.rocketmq.broker.BrokerController.initialize(BrokerController.java:256) [rocketmq-broker-4.5.1.jar:4.5.1]
at org.apache.rocketmq.broker.BrokerStartup.createBrokerController(BrokerStartup.java:218) [rocketmq-broker-4.5.1.jar:4.5.1]
at org.apache.rocketmq.broker.BrokerStartup.main(BrokerStartup.java:58) [rocketmq-broker-4.5.1.jar:4.5.1]
[

The INFO log is OK and could be ignored. It is a code style problem.
When recovering the log file, it comes to the end.

Better to separate the normal end and abnormal end of the recovery

通过在测试环境进行测试，发现在slave节点中，删除store目录下所有文件，然后进行重启，store目录下的文件和目录可以进行恢复，并且恢复过后，经过测试后，发现服务没有任何问题。于是对该集群，这个异常节点，进行store目录下文件删除操作，然后重启该节点，服务大致有1~2分钟不可用时间（此期间offset不增长，发送消息大量失败）；服务恢复正常后，该异常节点不断从leader节点同步数据，tps非常高；数据同步完后，tps恢复到与leader一致。

@faryang-sh  请问下，你们这个异常<异常发生在n1节点上，异常日志位于storeerror.log>,是导致n1节点不能消费，不能写入，还是重复消费的问题？  我们目前也碰到这个logic queue order maybe wrong异常。   您觉的导致这个异常的原因是什么？

@chwdaavid 请问发生该异常之前是不是也有机器重启的情况？

从 v从 vv 次

@RongtongJin 对的，也发生过宕机的情况。 我们版本较旧v3.2.6。  你能提供些原因猜测么。

@chwdaavid 那就不是dledger模式启动。logic queue order maybe wrong有可能是重启恢复时commitlog和consumequeue没有对齐导致的。

@chwdaavid 这个问题实际上不影响消息的写入以及消费，建议从3.2.6升级到最新版，试下dledger模式

@RongtongJin    @duhenglucky 那去除这种异常也是要删除store目录下文件来解决么。         我们目前影响还是蛮大的。 我们用的双主模式，一个影响是：有这个异常的broker运行几天后就会挂起，连接不上。 另一个影响是：重启后会有一定量的消息重复消费。

@chwdaavid 这种情况是不会导致broker的挂起的，可能要从其他方面来定位一下挂起的原因，比如连接数等，不过3.2.6的版本确实有点老了，建议升级到新版本观察下。


all and all-extras

This is built on top of #103 (so that needs to be finished first), but needing feedback on the design of these options.

@KotlinIsland Are you still interested in this PR? If so, please rebase it on the current main branch. Then, I'll take a closer look. Otherwise, there's now a (partial) duplicate PR (#241).
At first glance, an update of the readme and docs is missing in this PR.

@radoering If someone else is looking to take up the task I'm happy for them to do it.
I don't have much free time at the moment sorry.

Superseded by #241 and  #294


Use Flow instead of prop-types in lib/components

I'd like @shilman's approval on this before we merge this.
We need to discuss this properly before adding it to our codebase.

Thanks for pinging me @ndelangen
I've used Flow on projects and like it. However I'm skeptical of adding this to Storybook. I think it will make it harder for people to contribute to the project and possibly even scare people off, especially because  @storybook/components will be a package where we're bound to have a lot of first-time contributors.
In the interest of making Storybook as open as possible, I'd vote to hold off on adding this until Flow is a lot more popular/mature than it is now.

I support your statement @shilman
This codebase will definitely see higher numbers of 'first-time-contributions'. Some of those will be people not too familiar with react or flow or even JS (think about people changing styling).
I want to be welcoming to those contributors, and I think adding new syntax goes against this credo.
I really really appreciate you going out of your way to improve the codebase and all the stuff you do @Hypnosphi.
👍👍👍

I think it will make it harder for people to contribute to the project and possibly even scare people off, especially because @storybook/components will be a package where we're bound to have a lot of first-time contributors.

This codebase will definitely see higher numbers of 'first-time-contributions'. Some of those will be people not too familiar with react or flow or even JS (think about people changing styling).

Those are perfectly valid points! But they also apply to Glamorous, in my view. Should we maybe use CSS then? With CSS modules or BEM conventions, of course

Yeah some point apply to glamorous indeed. In that case I feel it's worth it, and it's not adding an new syntax: We're already using JS objects for styling.
I'm personally happy to do some hand-holding to help people overcome the glamorous barrier.
With FlowType I can't.
CSS-modules add considerable complexity in the webpack config department, there's quite a bit of 'magic' there.

I also have reservations about glamorous!!! But fewer concerns because the barrier to entry is much lower. 😄


Card Widgets does not support white color and rest of Colors supports

Steps to reproduce
Card widgets do not support a white color. However, they do support a variety of other colors.
Expected results
Card Widgets does not support white color and rest of Colors supports I want card also support white color
Actual results
Default Flutter color show when use white
Code sample
Code sample
 Widget _buildProfileCard() {
    return Card(
      color: Colors.white,
      shape: RoundedRectangleBorder(borderRadius: BorderRadius.circular(15)),
      child: Padding(
        padding: const EdgeInsets.all(16),
        child: Row(
          children: [
            const CircleAvatar(
              radius: 30,
              backgroundImage: AssetImage('assets/Ellipse 3067.png'),
            ),
            const SizedBox(width: 16),
            Expanded(
              child: Column(
                crossAxisAlignment: CrossAxisAlignment.start,
                children: [
                  Text(
                    'Alexander Michael',
                    style: GoogleFonts.poppins(
                      fontSize: 18.sp,
                      fontWeight: FontWeight.bold,
                    ),
                  ),
                  Text(
                    '+91<PHONE_NUMBER>',
                    style: GoogleFonts.poppins(
                      fontSize: 14.sp,
                      color: Colors.grey[600],
                    ),
                  ),
                ],
              ),
            ),
            const Icon(Icons.edit, color: Color(0xFF3F51B5)),
          ],
        ),
      ),
    );
  }

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
 fvm flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.9, on macOS 15.0 24A335 darwin-arm64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[!] Xcode - develop for iOS and macOS (Xcode 16.0)
    ! iOS 18.0 Simulator not installed; this may be necessary for iOS and macOS development.
      To download and install the platform, open Xcode, select Xcode > Settings > Platforms,
      and click the GET button for the required platform.

      For more information, please visit:
        https://developer.apple.com/documentation/xcode/installing-additional-simulator-runtimes
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.93.1)
[✓] Connected device (3 available)
    ! Error: Browsing on the local area network for Ashish’s iPhone (2). Ensure the device is unlocked and attached with a cable or associated
      with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

! Doctor found issues in 1 category.

codenia@Codenias-MacBook-Pro givzo %

Hi @ut7174, you're using an older version of flutter. Kindly upgrade to the latest version of flutter stable to see if you still experience this issue. If you do, please provide the updated output of flutter doctor -v along with a complete minimal reproducible code sample so that we can properly investigate this.
Any screenshots of the issue would also help.
Thank you

Here's a DartPad code sample that correctly displays a white card: https://dartpad.dev/?id=152b044160cb0f2c44a766cbd3d550e3
@ut7174 I recommend double-checking the "surface tint color"; it's possible that setting surfaceTintColor to white would resolve your issue.
If not, please update the comment so that the code sample can be copy-pasted & run (for example via DartPad) as @danagbemava-nc has suggested.

Thank you!


Likable and Reactionable separated in different mixins

Coverage decreased (-0.5%) to 24.693% when pulling 6b5c5d962f010869258004acf9cd1cd64690b611 on Diagon:master into 3aea588d76a3f760fdc1921b87a322371875ba1c on ramusus:master.


Backend Panels Gone after Upgrading

After upgrading our Django framework version to the latest, I noticed some panels in the backstage page are gone. Two examples I noticed are:

"Add Project Role" Panel in People page

"Add other visualization" panel in project page.

These missing panels make us unable to upload some key information, thus cannot show up new projects.

I was expecting to wake up this morning and quickly fix this, but I need more information. I'm not seeing the problems you're articulating. I don't think we ever had language that said "Add other visualization". Perhaps you mean something else?

I'm not seeing this problem. For me, Project Roles shows up fine on the add person page:
https://makeabilitylab.cs.washington.edu/admin/website/person/add/

For "Add other visualization" panel. I'm not sure what you mean.

Also, Daniel's page appears to show just fine:

Turns out the issue is caused by logging in with gradmin, instead of makeadmin. The gradmin account has less user permissions thus cannot access these panels. For later use, please avoid using this account.


didDeselectDate sometimes not called when cell is off-screen

Hey,
I'm using 7.1.5 and I have a problem with deselecting dates in my single row calendar.
calendar(_ calendar: JTAppleCalendarView, didDeselectDate date: Date, cell: JTAppleCell?, cellState: CellState) doesn't seem to get called when the deselected date is off-screen.
But this doesn't happen all the time. Only if the deselected date is close to the newly selected date. For example: selecting day 20 doesn't deselect day 21. However, selecting day 15 does deselect day 21.
You can see the problem in this gif (maybe disable looping the gif, it's more clear that way):

This is how I'm configuring the calendar:
let config = ConfigurationParameters(startDate: startDate,
    endDate: endDate,
    numberOfRows: 1,
    generateInDates: InDateCellGeneration.forFirstMonthOnly,
    generateOutDates: OutDateCellGeneration.off,
    firstDayOfWeek: .monday,
    hasStrictBoundaries: false)

Not entirely sure what I'm missing here because it all functions well for other dates that aren't close to each other. I don't know why that delegate method doesn't get called.
Thank you

have you implemented the willDisplayCell function?

Yes, and willDisplayCell function implements the same code as the cellForItemAt function (as described in the example project.

hmm. interesting. Would you mind pasting the relevant cellForItem and the willDisplayCell code?

They both implement this piece of code:
let cell: CalendarDayCollectionViewCell = calendar.dequeueReusableCell(for: indexPath)
// Setup happens in the cell:
cell.setup(calendar: currentCalendar, date: date, cellState: cellState)
// Shows the dot on dates which have an event:
handleCellEvents(cell: cell, cellState: cellState)
return cell

This is the setup func in the CalendarDayCollectionViewCell:
func setup(calendar: Calendar, date: Date, cellState: CellState) {
        dayLabel.text = cellState.text

    // todayView is the dark grey circle view
    // selectedView is the dark blue circle view
        if calendar.isDateInToday(date) {
            todayView.isHidden = false
            selectedView.isHidden = true
        } else {
            todayView.isHidden = true
            selectedView.isHidden = true
        }

        handleCellConfiguration(calendar: calendar, cellState: cellState)
    }

    // Not private because didSelectDate and didDeselectDate also call this
    func handleCellConfiguration(calendar: Calendar, cellState: CellState) {
        handleInOutDates(cellState: cellState)
        handleCellSelection(calendar: calendar, cellState: cellState)
        handleCellTextColor(cellState: cellState)
    }

    private func handleInOutDates(cellState: CellState) {
        if cellState.dateBelongsTo == .thisMonth {
            dayLabel.textColor = UIColordarkBlue
            isUserInteractionEnabled = true
            isHidden = false
        } else {
            dayLabel.textColor = UIColor.customLightGray
            isUserInteractionEnabled = false
            isHidden = true
        }
    }

    private func handleCellTextColor(cellState: CellState) {
        if cellState.isSelected {
            dayLabel.textColor = .white
        } else {
            if cellState.dateBelongsTo == .thisMonth {
                dayLabel.textColor = UIColor.darkBlue
            } else {
                dayLabel.textColor = UIColor.clear
            }
        }
    }

    private func handleCellSelection(calendar: Calendar, cellState: CellState) {
        if cellState.isSelected {
            todayView.isHidden = true
            selectedView.isHidden = false
        } else {
            if calendar.isDateInToday(cellState.date) {
                todayView.isHidden = false
                selectedView.isHidden = true
            } else {
                todayView.isHidden = true
                selectedView.isHidden = true
            }
        }
    }

This is about it I think.
Thanks

They both should not have this code.
let cell: CalendarDayCollectionViewCell = calendar.dequeueReusableCell(for: indexPath)

It is dequeued in the cellForItem function.
It is not dequeued in the willDisplayCell function.
Let me know if this fixes the issue first before in look at the other code.

That did the trick, great! Thanks for your help and thanks for this wonderful library!

glad issue is resolved.
leave a star rating if this lib is helpul to you.
have a good one.
🍻


SGD label resolution

Labels are rendered in 536d71c500000004 (Yeast Phosphate Starvation)
Examples
Individual: <http://purl.obolibrary.org/obo/#536d71c500000004%2F5595c4cb00000232>

    Annotations:
        <http://purl.org/dc/elements/1.1/date> "2015-01-05"^^xsd:string,
        <http://purl.org/dc/elements/1.1/contributor> "GOC:pt"^^xsd:string

    Types:
        <http://identifiers.org/sgd/S000005952>

Labels are not rendered in 5525a0fc00000061 (annotation consistency RB)
Example of OWL:
Individual: <http://purl.obolibrary.org/obo/#5525a0fc00000061%2F5595c4cb00000521>

    Annotations:
        <http://purl.org/dc/elements/1.1/date> "2015-05-01"^^xsd:string,
        <http://purl.org/dc/elements/1.1/contributor> "http://orcid.org/0000-0003-2468-9933"^^xsd:string

    Types:
        <http://identifiers.org/sgd/S000004529>

Note that S000004529 has been in the GAF a long time, so the hypothesis that this is a newly added gene doesn't hold

SGD     S000004529      TEM1            GO:0007096      SGD_REF:S000086185|PMID:16039591        TAS             P       GTP-binding protein of the Ras superfamily      YML064C|Ras family GTPase TEM1  gene      taxon:559292    20060314        SGD

Added a quick test for: <http://identifiers.org/sgd/S000005952>
Seems to work on the Golr query level perfectly well.

We already had a similar test case for: <http://identifiers.org/sgd/S000004529>
Seems to also work on the Golr level.

Was a cache issue, @hdietze committed an improved cacheing mechanism


[docs] Prevent toolbar tooltips overlapping demos

Since #17831 the current Tooltip placement means tooltips will cover the demos. This is especially annoying if you get the source hint when first visiting the docs but tooltips hiding content is annoying generally. The space to the bottom fits a tooltip perfectly though it can hide potential ads and the source. In the case of ads I think visible demos are more important demos. For source code we only cover the first import line which is almost always the react import.

Aside: Bonus points for consistent formatting

Mind that on https://deploy-preview-22732--material-ui.netlify.app/components/alert/, the tooltip become almost invisible.

Mind that on deploy-preview-22732--material-ui.netlify.app/components/alert, the tooltip becomes almost invisible.

Comes back to opacity of tooltips. Since you can't fully control the background these shouldn't have opacity IMO.
Maybe a white outline would help distinguishing them if the appear before a similar background?

@eps1lon IMHO, it's good enough like this. Developers can still see the tooltip pop when moving the mouse over the demo without scrolling.


Clarify AAD properties for Spring Cloud Azure

As title.
Fixes: https://github.com/Azure/azure-sdk-for-java/issues/29578

API change check
API changes are not detected in this pull request.


Click outside of data table is not observed

In React Bootstrap Table when I enable a enable to field to be editable. When I want to cancel the edition I press can ESC button it goes back earlier phase, but when a user clicks on data table or press enter its saves, but when I click outside of data table it remains in edit phase. I want the same thing to happen outside of data table.
In the below example, if I click outside of data table, the product price edit must go away, but currently, it remains there which is weird.

I can try to support a cellEdit.blurToLeave props to support this feature, thanks

Thank You

@pramodZipGo fixed on v4.0.6, please check this example, thanks


[SSH Connection Manager] Shows ProxyCommand instead of host name from ~/.ssh/config

Extension
https://www.raycast.com/dimagrossman/ssh-manager
Description
If ssh command contains ProxyCommand or Jump host like this,
Host SecureConnect secure.myhost.com
	User admin
	HostName <IP_ADDRESS>
	Port 22
	IdentityFile ~/.ssh/id_ed25519

Host LB-01
	User admin
	HostName <IP_ADDRESS>
	Port 22
	ProxyCommand ssh -W %h:%p SecureConnect

Then instead of actual host name it shows ProxyCommand.
Note:  HOST section can contain alias separated by space like both name and fqdn (host SecureConnect in above example)

Steps To Reproduce

macOS Ventura
ProxyCommand in ~/.ssh/config
Go to ssh connection

Current Behaviour
Same as above.
Expected Behaviour
It should show Proper name of the host. For multiple host aliases it can show both on the same line or separately as different ssh connection.

Summoning @yaronuliel. Can you take a look ?

Pinging  @RtiM0 @yaronuliel again, since it is stalled now ? Ssh-plugin unusuable with .ssh/config backend


Generated VDM does not contain orderable functions (e.g. 'asc' / 'desc')

Describe the bug
I updated a VDM, generated with "<EMAIL_ADDRESS>to follow and use the SAP Cloud SDK v2 by using generator 2.2.0
This was working like a charm and I generated a new package with the outcomes.
Then I installed the new package in my application and started to 'update' my requests to follow the new SDK requirements.
The first request already got me to that point, to start deep-diving the dist folders by searching for 'asc' and 'desc' functions to be able to order my request.
Unfortunately, I am not able find both functions as outcomes form "@sap-cloud-sdk/odata-common". They are defined with /order/orderable.ts, and getting exported there. But on the index.ts "orderable" isn't available for me to get imported.
To Reproduce
Steps to reproduce the behavior:

Generate a VDM and import it

Use the outcoming API and set up your requestBuilder:
     // get entries from logDataStore
     const { logDataStoreApi } = generatedVDM.dataLayerLogstoreService();
     const logEntries = await logDataStoreApi
                             .requestBuilder()
                             .getAll()
                             .filter(
                                 logDataStoreApi.schema.STATUS.equals('NEW'),
                                 logDataStoreApi.schema.TARGET.equals('LOGABC')
                             )
                             .orderBy(asc(logDataStoreApi.schema.CREATED_AT))
                             .top(top)
                             .execute(mySecretDestination);

Try to use functions "asc" or "desc" within the "orderBy" function. Both functions are not available.
Expected behavior
I can import them with
import { asc, desc } from '@sap-cloud-sdk/odata-common'
Used Versions:

node version 14.17.6
npm version 8.1.1
SAP Cloud SDK: @sap-cloud-sdk/generator: 2.2.0

Hi @drvup ,
Thank you for raising up.
I think this is a bug.
Please use the following workaround:
import { asc } from '@sap-cloud-sdk/odata-common/internal';

Also as a update we now order using asc per default: https://github.com/SAP/cloud-sdk-js/pull/2877


Palettes support for discrete scales

Allow to use palettes with discrete scales.
scale_color_discrete(palette='BuGn')
or:
scale_color_brewer(palette='Blues', discrete=True)

@IKupriyanov-HORIS I'm not sure what is this issue about.
Sequential brewer palettes are intended primarily for continuous data series but can be used with categorical data series as well:
scale_color_brewer(type='seq', palette='BuGn')
scale_color_brewer(type='seq', palette='Blues')


Logo design

It would be nice to make a logo to go with the name 'Teleportal'!

I wanted a logo that played with space, has bold colours and works in the hexagon open source sticker standard.

This is aweome, thanks so much @bvhme ! :D


Check mode breaks because path and dest undefined

Hey, firstly thanks for putting this module together its been really helpful in getting our own module in working order. I noticed that this thing breaks when you run it in check mode. I looked at the template module and annoyingly it returns something different depending on how its run and the change set. It seems like running the template module in check mode doesn't return path or dest? I tested with something silly like this:
- template:
    dest: /tmp/test
    src: test.j2
  register: test

- debug: var=test

When I run it in check mode I get:
{
    "test": {
        "changed": true,
        "diff": {
            "after": "",
            "after_header": "dynamically generated",
            "before": ""
        }
    }
}

and when I run it without check I get:
{
    "test": {
        "changed": true,
        "checksum": "da39a3ee5e6b4b0d3255bfef95601890afd80709",
        "dest": "/tmp/test",
        "diff": {
            "after": "",
            "after_header": "dynamically generated",
            "before": ""
        },
        "gid": 0,
        "group": "root",
        "md5sum": "d41d8cd98f00b204e9800998ecf8427e",
        "mode": "0644",
        "owner": "root",
        "size": 0,
        "src": "/home/ubuntu/.ansible/tmp/ansible-tmp-1471991735.19-268768173190611/source",
        "state": "file",
        "uid": 0
    }
}

or
{
    "test": {
        "changed": false,
        "diff": {
            "after": {
                "path": "/tmp/test"
            },
            "before": {
                "path": "/tmp/test"
            }
        },
        "gid": 0,
        "group": "root",
        "mode": "0644",
        "owner": "root",
        "path": "/tmp/test",
        "size": 0,
        "state": "file",
        "uid": 0
    }
}

luckily when you run run it with_items each of the items will have a invocation section like:
...
"invocation": {
                    "module_args": {
                        "dest": "/tmp/test",
                        "src": "test.j2"
                    },
                    "module_name": "template"
                },
...

Since we will always be using template maybe we can just grab this out all the time? Or just in the case that path and dest aren't defined? Im not sure what you want to do here but it would be cool to have this able to run through a check.
Anyway possible I missed something in there but just thought I would bring this up since Im not sure if anyone else was seeing this issue.
Thanks again.

Hey @CheRuisiBesares, thank you for this pull request.
I never tried the check mode with this module. Your proposal is very well thought out. I am very glad to merge this.


TypeError: visitFn.call is not a function

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

When running the generate from graphql-codegen i recieve the following error:
✖ src/generated/graphql.ts
    TypeError: visitFn.call is not a function
        at visit (/Users/danestves/seeed/blendi/app/node_modules/graphql/language/visitor.js:200:21)
        at Object.plugin (/Users/danestves/seeed/blendi/app/node_modules/graphql-codegen-plugin-type
script-swr/build/main/index.js:21:25)

This is my schema:
overwrite: true
schema: ${API_URL}/graphql
documents: 'src/**/*.graphql'
generates:
  src/generated/graphql.ts:
    plugins:
      - 'typescript'
      - 'typescript-operations'
      # Put `plugin-typescript-swr` below `typescript-graphql-request`
      - 'typescript-graphql-request'
      - 'plugin-typescript-swr'
    config:
      rawRequest: false
      autogenSWRKey: true

These are my dependency versions:
"graphql": "^16.0.1",
"graphql-request": "^3.6.1",
"swr": "^1.0.1",
"@graphql-codegen/cli": "2.2.2",
"@graphql-codegen/typescript": "2.3.1",
"@graphql-codegen/typescript-graphql-request": "^4.3.0",
"@graphql-codegen/typescript-operations": "2.2.0",
"graphql-codegen-plugin-typescript-swr": "^0.7.0",

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

I have downgrade to "graphql": "^15.7.2" and fix the problem, but also will love to use the latest version of GraphQL as soon as you can support it

+1

+1

+1

Any update on this? we are facing the same issue

+1

The maintainer has put in his bio that he is not maintaining this library because he is not using it 🙃 so I think someone needs to make a fork; I can't do it because I have a lot of OSS projects on my hands 😅

downgrading graphql to 15.7.2 solved it for me. Watching for better solution 🥲

Released v0.8.0. This release should this issue.


Chat flow: update gateway code to use new TFGateway

We need two new chatflows:
Delegate domain:
This one will ask the your for the name of the domain he wants to delegate
it will intruct the user to create a ns record in his dns and point it to tthe gateway dns_nameserver field in the gateway node
Expose my solution
Ask for the subdomain to expose this can be either a subdomain of one of his own delegated domains or a subdomain of the gateway see field (managed_domains)
Select the solution to expose
depending on the solution kind ask for which port to expose...
Ask for payment if needed...
Internally we make a reservations that: registered the subdomain, create a small container with flist https://hub.grid.tf/tf-official-apps/tcprouter:latest.flist.md in the network of the solution, configure the trc (tcprouterclient) with a secret connecting to the tcprouter server on the server pointing to the private ip/port of the solution selected

Two chatflows added

verified.


[Metrics] Change default value for the argument 'mentions' in entity_consistency

When dealing with metrics (specifically with entity_consistency), the default value of the argument 'mentions' is set to 10. With this default value, sometimes it is not possible to obtain data.
If the default value was higher (i.e. mentions=20), I think we could get rid of this problem.


Update README.md

Concisely describe what has been changed/addressed in the pull request.
Link reported as broken

Resolves issue #475

What tests have been done?

[x] No test files are required for this pull request.
Is there an input change for users to Stock Synthesis?
[x] No, there was no input change.

@e-gugliotti-NOAA   refreshing this PR


[SPARK-34339][CORE][SQL] Expose the number of total paths in Utils.buildLocationMetadata()

What changes were proposed in this pull request?
This PR proposes to expose the number of total paths in Utils.buildLocationMetadata(), with relaxing space usage a bit (around 10+ chars).
Suppose the first 2 of 5 paths are only fit to the threshold, the outputs between the twos are below:

before the change: [path1, path2]
after the change: (5 paths)[path1, path2, ...]

Why are the changes needed?
SPARK-31793 silently truncates the paths hence end users can't indicate how many paths are truncated, and even more, whether paths are truncated or not.
Does this PR introduce any user-facing change?
Yes, the location metadata will also show how many paths are truncated (not shown), instead of silently truncated.
How was this patch tested?
Modified UTs

While I've marked SPARK-34339 as improvement, I also feel this may be considered as a bug, as the new output brought by SPARK-31793 brings confusion.

cc.ing @gengliangwang @cloud-fan @HyukjinKwon @maropu who are author/reviewers of #28610

Test build #134849 has started for PR 31464 at commit f0a02fd.

Yeah, I think this is better

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39436/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39436/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39436/

Test build #134849 has finished for PR 31464 at commit f0a02fd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134849/

Test build #134853 has started for PR 31464 at commit 56abfe2.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39440/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39440/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39440/

Appreciate another round of review based on the changed output. I'll try out alternative if the output doesn't look good for us. Thanks!

Hmm... I'll need to fix the test as a lot of tests are relying on the previous format (Location: <className> []). I'd like to hear the voice on the new output format before fixing these.

Test build #134853 has finished for PR 31464 at commit 56abfe2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134853/

I was wrong about the amount of broken UTs. They were just 2 and I just fixed.

Test build #134861 has started for PR 31464 at commit e766209.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39448/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39448/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39448/

Test build #134861 has finished for PR 31464 at commit e766209.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134861/

@HyukjinKwon @cloud-fan @gengliangwang Appreciate another round of review. Thanks!

Merged to master.

Thanks all for reviewing and merging!


Make period for TOTP configurable

As an authenticating user, I want to have more than 30s to complete TOTP validation so that I can use slower forms of TOTP, for example SMS or E-mail.
### Acceptance Criteria
- [ ] Modify the API to be able to configure the period if needed

The problem
We have a lot of clients that have a lot of legacy (think like governmental agencies etc).
Today we are using a custom SMS/Email solution for 2FA. We are looking to migrate all of our auth to Zitadel and during the transition we'd need some way to keep the "old" 2FA until everyone has updated to something more modern.
Proposed solution
In the package used for TOTP it is possible to configure the period and it is set to 30s by default. If there could be a way to change the API of AddHumanOTP to receive a Period (maybe even optionally?) somehow and then pass it down to NewOTPKey it would solve our needs.
This would need to then surface this parameter up to the API:s by adding it as a field to AddMyAuthFactorOTPRequest. Another solution would be to add this as a configuration option on the organization level.
Possible implications
I don't have deep knowledge of this codebase so I'm not sure if this will break some interface or other pattern that you are using. Since the change I'm proposing is additive it should not break existing code since the default value should still be the same.
Lastly, if this is considered a good idea I'm open to try to implement it myself, I just don't want to put in the work and then have it rejected.
PS:
If you have an idea on how I could accomplish this without changes I'd be very happy to hear.

hei @karatekaneen
We have now additionaly Email land SMS second factor. Would that solve your problem as well?
I just reread you issue, and I am not sure what the problem is you are trying to solve.


kubelogin: 0.0.27 -> 0.0.28

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Azure/kubelogin/releases.
meta.description for kubelogin is: A Kubernetes credential plugin implementing Azure authentication
meta.homepage for kubelogin is: https://github.com/Azure/kubelogin
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.0.28 with grep in /nix/store/pin1w3qsxfrcpkccqh8iypkyxh11hmab-kubelogin-0.0.28
found 0.0.28 in filename of file in /nix/store/pin1w3qsxfrcpkccqh8iypkyxh11hmab-kubelogin-0.0.28

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kubelogin

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pin1w3qsxfrcpkccqh8iypkyxh11hmab-kubelogin-0.0.28 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubelogin https://github.com/r-ryantm/nixpkgs/archive/59d8017931de74ca140d067ae6f218e41dad852f.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pin1w3qsxfrcpkccqh8iypkyxh11hmab-kubelogin-0.0.28
ls -la /nix/store/pin1w3qsxfrcpkccqh8iypkyxh11hmab-kubelogin-0.0.28/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubelogin

Maintainer pings
cc @yurrriq for testing.

Result of nixpkgs-review pr 221593 run on aarch64-darwin 1

1 package built:

kubelogin


App Settings using IIS AppPool environmentVariables

Not sure if SiteManager is the right place to put this.

@duckblaster sorry, I just noticed this PR. I sthis still up to date and worth reviewing? If so, we will get to it soon!

I haven't had a chance to fully test it, but it compiles fine and I don't see any reason it wouldn't work.
It might be worth adding checks so it doesn't run on older versions of IIS, but the try catch blocks handle that.

It seems to be working fine as far as I can tell


Add tree view component : index & images

I've updated the site as request in LEXI-915.
Please, review and merge when you're finished.
Thanks!

This one looks much better. Thanks @hold-shift !

Great, thanks @victorvalle !


AccessRightField, FileUploaderToolbar: Add conditionals based on config

Closes https://github.com/zenodo/zenodo-rdm/issues/46

Enables disabling of the metadata-only option in the UI
Enables disabling of the full record visibility option in the UI

Screenshot of disabling: https://github.com/zenodo/zenodo-rdm/pull/90

Closed because we decided on a different solution with react-overridable (https://github.com/inveniosoftware/invenio-app-rdm/pull/1970)


Configure to use database v2.4.0

:construction_worker: Purpose
To enable login with email address
:rocket: Changes

Use database v2.4.0

:warning: Breaking Changes
None

Excellent, great work :muscle:


High GPU memory usage after import

Hi,
After importing the tfsim in my Jupyter Notebook it instantly creates a nameless process that consumes 9967MiB on the GPU. Hence it quickly runs OOM when trying to train something. This happens only on my JupyterHub instance and not when I test it on Google Colab for example.
OS: CentOS 7
Driver version: 510.47.03
Cuda version: 11.6
TF version: tested on 2.9.1 and 2.8.0
TFsim version: 0.16.2

Any ideas?

Thanks for catching this. I'm not sure what is causing this yet, but I can repro it on JupyterHub using Conda. I'll see if I can identify the import that is causing the issue.

We just pushed a patch that should fix this. Thanks again for catching this.


Add support for Boost 1.61.0

Boost 1.61.0 was released a few weeks ago, and it would be nice to add support for it.

I forgot it. I added.


mvn clean install failure for sdk-example

Expected Behavior
I would like to run mvn clean install successfully and run the examples successfully. Specifically, I need the dapr-sdk-examples jar file, but that is failing.
Actual Behavior
I see errors in my IDE even on the master branch:

Additionally, I see:
# from root run
$ ./mvnw clean install
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] dapr-sdk-parent 1.11.0-SNAPSHOT .................... SUCCESS [  1.419 s]
[INFO] dapr-sdk-autogen 1.11.0-SNAPSHOT ................... SUCCESS [  1.319 s]
[INFO] dapr-sdk 1.11.0-SNAPSHOT ........................... SUCCESS [ 18.422 s]
[INFO] dapr-sdk-actors 1.11.0-SNAPSHOT .................... SUCCESS [  7.121 s]
[INFO] dapr-sdk-workflows 0.11.0-SNAPSHOT ................. SUCCESS [  5.069 s]
[INFO] dapr-sdk-springboot 1.11.0-SNAPSHOT ................ SUCCESS [  2.841 s]
[INFO] dapr-sdk-springboot3 1.11.0-SNAPSHOT ............... SUCCESS [  0.438 s]
[INFO] dapr-sdk-examples 1.11.0-SNAPSHOT .................. FAILURE [  0.414 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  37.458 s
[INFO] Finished at: 2024-01-29T17:22:17-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project dapr-sdk-examples: Fatal error compiling: error: release version 17 not supported -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :dapr-sdk-examples

Steps to Reproduce the Problem
Check out master. Run ./mvnw clean install from root. See errors.

@skyao Do I need to do something to get the dapr-sdk-examples to be successful? I tried switching the version to be 11 manually in the sdk-examples pom.xml and that resulted in even worse errors. I know this PR adding jdk17 support got merged recently, but I was unaware of it resulting in failures. Thoughts?

It appears this was a local issue with the sdkman pointing to an old version of java.


from_xml (string) raises path too long for Windows

I'm using Python 3.7.5, ome-types 0.2.1, and on Windows, trying to pass my xml string in to from_xml:
File "d:\src\aics\cellbrowser-tools\cellbrowser_tools\fov_processing.py", line 295, in add_segs_to_img
self.omexml = from_xml(description)
File "C:\Users\danielt\AppData\Local\Continuum\anaconda3\envs\cellbrowser-tools\lib\site-packages\ome_types_init_.py", line 37, in from_xml
d = to_dict(xml)
File "C:\Users\danielt\AppData\Local\Continuum\anaconda3\envs\cellbrowser-tools\lib\site-packages\ome_types\schema.py", line 265, in to_dict
_xml = xml if os.path.exists(xml) else StringIO(xml)
File "C:\Users\danielt\AppData\Local\Continuum\anaconda3\envs\cellbrowser-tools\lib\genericpath.py", line 19, in exists
os.stat(path)
ValueError: stat: path too long for Windows
It seems the code is using os.path.exists on the raw xml string to see if it's a file or not?

huh, that sounds like https://github.com/tlambert03/ome-types/issues/50#issuecomment-728707062 which I tried to fix in https://github.com/tlambert03/ome-types/pull/56 ... (and yeah, it does call os.path.exists to detect if it's a raw XML string or a file).  However, I only tested locally on mac (where it works).  will try to post a fix soon.  thanks!

Thanks for the quick fix here. Looking forward to the release.  I also heartily approve of the addition of other platforms to the tests in github actions.
And thanks for the work on this cool library -- as you probably know, we are going to incorporate it into an upcoming version of aicsimageio !  In the meantime I am trying to use it as an intermediate representation in some other processing I'm doing.

No problem!  Thanks again for letting me know.  Looks like tests are passing now on all three platforms, with py3.7-3.9.  I just pushed v0.2.2 and it will likely post to pypi shortly.
I'm very glad to hear you're finding it useful at aics!  And using it as an intermediate representation was what got me going down this line in the first place :) so will be curious to hear how that works out for you.  keep me updated 👍


Registration error

I get the following error when I register a new app in Eureka:
"{
'timestamp':1508239392780,
'status':500,
'error':'Internal Server Error',
'exception':'com.thoughtworks.xstream.converters.ConversionException',
'message':'java.lang.Boolean cannot be cast to java.lang.String : java.lang.Boolean cannot be cast to java.lang.String
---- Debugging information ----
nmessage             : java.lang.Boolean cannot be cast to java.lang.String
ncause-exception     : java.lang.ClassCastException
ncause-message       : java.lang.Boolean cannot be cast to java.lang.String
nclass               : com.netflix.appinfo.InstanceInfo
nrequired-type       : com.netflix.appinfo.InstanceInfo
nconverter-type      : org.springframework.cloud.netflix.eureka.DataCenterAwareMarshallingStrategy$DataCenterAwareConverter
nline number         : -1
nversion             : 1.1.147
-------------------------------',
'path':'/eureka/apps/DOTNET-DEMO-SERVICE'
"
My config is:
"
"spring": {
"application": {
"name":  "myDotnetService"
}
},
"eureka": {
"client": {
"serviceUrl": "http://my-eureka-instance:8761/eureka/",
"shouldRegisterWithEureka":true,
"shouldFetchRegistry": false
},
"instance": {
"app": "myDotnetService",
"hostName":"my-host",
"port": "6000"
}
"
But if i change type of property "Enable" in JsonPortWrapper to String all work as need:
[JsonProperty("@enabled")]
public String Enabled { get; private set; }

I have this local fix, may i do pull requst?

@GSTQ ,

What version of Steeltoe are you using? 1.0.0 or 1.1.0?
What version of Netflix Eureka are you using or what are you using to startup the Eureka server?
Dave

I'm using Steeltoe  v 1.1.0 from nuget
I'm using docker image springcloud/eureka from docker hub.
At manifest.mf from JAR file i found this:

That docker image is very old .. and is likely using old neflix code ..
Can you try running the Eureka server as outlined here: https://github.com/SteeltoeOSS/Samples/blob/master/Discovery/src/AspDotNetCore/Fortune-Teller-Service/README.md ....
I'm sure that works with 1.1.0 as I just ran it again to verify...
or there is a "less" old docker image that we reference in our Music Store sample app that should work fine with 1.1.0.
https://hub.docker.com/r/steeltoeoss/servers
Dave

Thank you. I'm close my PR.


Fix array key in case of login errors

https://github.com/hamstar/Wikimate/blob/ecec68329821cdc5d72666f36eb5129347cc2a6f/Wikimate.php#L393 creates $error['auth'] instead of $error['login'] key. Adjusted example accordingly

Yup, done. Thanks.