text:
意见反馈及常见问题整理 3

前两期 #39 #54
第二期的有时间再整理，发现讨论的偏多，所有就不像第一期那样在提问者那里整理了

现在是没有心跳了吗 貌似没有加经验啊 还是全民老爷不加经验 - -

我还真没注意这个问题，一会儿看看

有点尴尬，系统广播没开通总督的房间号

50583，没错啊，就是154

这个是房间消息，系统消息是这个
{
  "cmd": "GUARD_MSG",
  "msg": "用户 :?EricOuO:? 在主播 七七见奈波丶 的直播间开通了总督",
  "buy_type": 1,
  "_roomid": 23058
}

系统消息的data吗，还是所有，不止看data看看，

所有就是这样了，没有roomid

采用正则匹配啊

逻辑如图

那只能搜索“在主播”和“的”之前的主播名字了

@Dawnnnnnn 没有roomid就很不想做这个东西，哪天msg改了还得重写
而且之前还有这种格式
{
  "cmd": "GUARD_MSG",
  "msg": "欢迎 :?总督 Tikiあいしてる:? 登船",
  "roomid": 237328,
  "_roomid": 237328
}

emmmm，这就很难办了，要匹配的话还要先判断是哪个格式的@lzghzr

@lzghzr 大佬有没有修复应援团编译好的版本呀

手动改一下网址就行了

我太懒了，每天勋章亲密度都懒得手动刷然后我就把user.js里的if (giftData.expireat > 0 && giftData.expireat < 24 * 60 * 60)改成了if (giftData.expireat > 0)场面非常壮观

全送了。。。。

听说是判断用户是否真的在线来关小黑屋的。userinfo

倒是有个统计在线的API，我试试

朋友的。。。

妈的 狗脸~我要找他要红包

另外发现个小问题，server酱只会提醒抽奖XXXX获得1个小电视大奖，不会显示是谁。
没加上this._user.nickname

恩，忘写了，最新提交已经优化了
WangMuDu notifications@github.com 于 2018年4月1日周日 02:13写道：

另外发现个小问题，server酱只会提醒抽奖XXXX获得1个小电视大奖，不会显示是谁。
没加上this._user.nickname
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-377712436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0hjXUMiFF4vSN5gMsY8KbILQ3rblks5tj8dVgaJpZM4TATlN
.

大佬，请问实物抽奖开放了吗？

请问下各位大佬，之前还好好的最近这几天就只监听不自动抽奖了，是怎么了？
Apr 02 2018 22:17:26 : 房间 386293 开启了第 27968 轮抽奖
Apr 02 2018 22:17:26 : 房间 386293 开启了第 27968 轮客户端抽奖
Apr 02 2018 22:17:30 : 房间 771423 开启了第 27969 轮抽奖
Apr 02 2018 22:17:30 : 房间 771423 开启了第 27969 轮客户端抽奖
Apr 02 2018 22:19:23 : 房间 1517910 开启了第 27970 轮抽奖
Apr 02 2018 22:19:23 : 房间 1517910 开启了第 27970 轮客户端抽奖
Apr 02 2018 22:19:35 : 房间 521429 开启了第 27971 轮抽奖
Apr 02 2018 22:19:35 : 房间 521429 开启了第 27971 轮客户端抽奖
Apr 02 2018 22:19:36 : 房间 521429 开启了第 27972 轮抽奖
Apr 02 2018 22:19:36 : 房间 521429 开启了第 27972 轮客户端抽奖

LS你怕是进了小黑屋...

这是啥报错....

网络错误，一般不用管
Dawnspace notifications@github.com 于 2018年4月3日周二 13:47写道：

[image: image]
https://user-images.githubusercontent.com/24506421/38231527-839b4562-3745-11e8-8ed1-81fab3611b0b.png
这是啥报错....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-378135406,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0h_R4baI96kBa2ndQ3gX1XUnLVSIks5tkwzsgaJpZM4TATlN
.

现在 除了没在线 一个礼拜了还没进黑屋

想体验一下server酱的服务  可一直也没被封过_(:3」∠)_

server不是被封提示，你把开关关上就可以体验了
xin notifications@github.com 于 2018年4月3日周二 16:17写道：

想体验一下server酱的服务 可一直也没被封过_(:3」∠)_
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-378167727,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0n6MJy1Z1WL55IvkdAWsIswfUmXbks5tkzAugaJpZM4TATlN
.

呆住.jpg   更新后关过好几次，看来没设置好，我去看看。谢提醒

@l136297 你那儿可以用了不？我前两天也这样，折腾半天没解决，今天忽然就可以用了

@kkocdko 之前还以为进小黑屋了，后来换了新版本直接就好了，一直挂机都没问题

昨天双端的客户端没有完成，开关一遍之后能够完成，当然领取还是手动领的。今天正常

我知道被封以后无法完成宝箱，双端还真不清楚

宝箱可以领取，双端没有

问一哈 代理是自动使用的嘛

@lovezm 你是指IP？那个我在#61说过

重装后无法保存账号。

https://api.live.bilibili.com/lottery/v1/award/award_list今天抓了或将中心的包 朋友PHP版本的一查卧槽 几十个中奖的  但是都没领...笑哭。。心疼。。

@Haclankid   不需要   git pull   拉一下 重新npm i     npm  run build就行

关于银瓜子兑换硬币的问题，默认可以兑换两次，一次700，一次1400，是否可以设置只兑换700的那个，因为硬币是用来每月老爷时兑换1000银瓜子的=.=

目前没有这个打算，因为银瓜子实在太廉价了，趁着没金硬币的时候多换点吧

re:@yanjun0501  重装了一下可以了

Releases里打包了一份win64版本，正常来说双击cmd就可以用了

建议各位停一下，B站又开始了
另外
@lzghzr  我想问一下自己抓的包的功能加在哪里可以让他每天执行一次 - -

加在user.ts里，nextday是一天执行一次，daily是一天执行三次

....今天双端又完成不了，大号的电脑完成了手机没有，小号两个都没完成。

新版本编译显示以下错误
（Windows 8.1 x64, Node.js v8.11.1）
C:\Users\admin\Downloads\bilive_client>npm install
npm notice created a lockfile as package-lock.json. You should commit this file.

npm WARN bilive_client@1.3.8 No repository field.

added 75 packages in 16.103s

C:\Users\admin\Downloads\bilive_client>npm run build

> bilive_client@1.3.8 build C:\Users\admin\Downloads\bilive_client
> npm run build:tsc && npm-run-posix-or-windows build:copy

> bilive_client@1.3.8 build:tsc C:\Users\admin\Downloads\bilive_client
> tsc --locale zh-cn -p tsconfig.json || exit 0

bilive/listener.ts(136,17): error TS6133: 已声明“_LotteryCheck”，但从未读取其
值。
bilive/listener.ts(218,10): error TS2339: 类型“Listener”上不存在属性“_RoomLis
tener”。
bilive/listener.ts(220,43): error TS2339: 类型“Listener”上不存在属性“_RoomLis
tener”。
bilive/listener.ts(221,15): error TS2339: 类型“Listener”上不存在属性“_RoomLis
tener”。

> bilive_client@1.3.8 build:copy:windows C:\Users\admin\Downloads\bilive_client
> copy .\bilive\options.default.json .\build\bilive\ /Y

已复制         1 个文件。

(node:97049) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'AddRoom' of undefined
at Listener._RaffleHandler (/root/bilive_client/build/bilive/listener.js:137:28)
at raffleCheck.body.data.forEach.data (/root/bilive_client/build/bilive/listener.js:60:22)
at Array.forEach ()
at Listener._RaffleCheck (/root/bilive_client/build/bilive/listener.js:53:35)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:97049) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 9)
(node:97049) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'AddRoom' of undefined
at Listener._RaffleHandler (/root/bilive_client/build/bilive/listener.js:137:28)
at roomInfo.body.data.event_corner.forEach.event (/root/bilive_client/build/bilive/listener.js:102:22)
at Array.forEach ()
at Listener._AppLightenCheck (/root/bilive_client/build/bilive/listener.js:92:45)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:97049) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 10)
Apr 13 2018 15:46:44 : 1 抽奖 33708 获得 2 个辣条
(node:97049) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'AddRoom' of undefined
at Listener._RaffleHandler (/root/bilive_client/build/bilive/listener.js:137:28)
at raffleCheck.body.data.forEach.data (/root/bilive_client/build/bilive/listener.js:60:22)
at Array.forEach ()
at Listener._RaffleCheck (/root/bilive_client/build/bilive/listener.js:53:35)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:97049) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)

@zreo147 不能指定时间
多用户可以使用一个单独的protocol对用户进行区分，在现在的基础上新加一个protocol项就行，虽然改动有点多，但是实现起来应该不难，日志也可以依此分隔开

不送的话会自动送上万的辣条，哈哈，还有人一直留着没送的吗

一次送这么多，会被限制吗。。。

辣条现在不会触发频道广播了，所以还是挺安全的
B站每天那么多礼物，不会管的吧，我自己养勋章的号都被送到20级了

没有留意自动送礼，把礼物全送完了QAQ
20级真大佬

昨天20瞬间23级了....我擦...害怕B站搞我....

小电视接口可能改了？14:39开始 就没有动静了

感觉被好站给弄了   不光小电视 @lovezm

破站不至于吧 活动结束就这样搞

不过又感觉是根本没礼物 反正只看到有一个监听到抽奖但是没加入   守了半天也没人送小电视

改了？我觉得没有吧，哪位大佬做个系统消息的log看看呗

咦？又凉了吗

6点多又有了(〜￣△￣)〜

async jx() {
    if (!this.userData.jx)
        return;

const jxweb = {
    method: 'POST',
    uri: `${index_1.apiLiveOrigin}/activity/v1/MatchDraw/draw`,
    body: `name=jx3&${app_client_1.default.signQueryBase(this.tokenQuery)}`,
    json: true,
    headers: this.headers
};
tools_1.default.Log(this.nickname, '剑侠3活动抽奖', `参与剑侠情缘抽奖成功`);
const jx = await tools_1.default.XHR(jxweb);
await tools_1.default.Sleep(3000);
const jxweb2 = {
    method: 'POST',
    uri: `${index_1.apiLiveOrigin}/activity/v1/MatchDraw/draw`,
    body: `name=jx3&${app_client_1.default.signQueryBase(this.tokenQuery)}`,
    json: true,
    headers: this.headers
};
const jx2 = await tools_1.default.XHR(jxweb2);

}

加到user里面就行了。
这是剑侠三活动的 每天抽一次  关注房间的话每天可以抽两次 nodejs其实我不懂，这还是勉强对着才能写下来的，测试了功能实现了，我希望l大能优化一下我的垃圾代码。。
另外我想问一下l大，如何能让他加进去 不用再web设置 添加账号保存启用后   默认就执行？
我现在是搞个按钮，并且加到daily里面才能让他执行 nextDay就不行了 脑阔疼
活动链接是https://live.bilibili.com/blackboard/activity-jx3master3.html

nextday是固定每天00：30执行，无法手动除触发（更改系统时间除外
以及，这活动好低调

额 让了吧 看规则貌似只有比赛日才可以抽奖。。23333

我这代码 直接加到nextday也可以执行的吗。
if (!this.userData.jx)
return;
我看有的是
if (this._eventRoom || !this.userData.eventRoom)
return;
这样的
第二个的意思是在nextday或者daily里面都可以吗？

你直接不加if return就好了，默认开启

server酱都没提醒过我（（我这挂了十几个号不该一个多月了啥都没中吧（

好的 感谢~
@Naexen 不中奖不是很正常嘛  我挂100个小号不也不中奖 不过都是主站被封的。2333

@lovezm 如果你在option.json和default里写了对应的boolean值就可以做成管理页面里面那种打勾启用功能的形式了 if (this._eventRoom || !this.userData.eventRoom) return里面的!this.userData.eventRoom就是指当你在管理页面没打勾就直接return，完全可以换成自己写的功能2333
话说 server酱怎么玩儿 有大佬说说嘛

刚发现的问题，重启还是这样

Apr 17 2018 09:54:31: http://api.live.bilibili.com/activity/v1/task/receive_award{ Error: connect ETIMEDOUT120.92.174.135 :80
at 0bject._errnoException (uti1.js: 1024: 11)at_exceptionWfithHostPort (uti1.js: 1046:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js: 1182: 14)code:' ETIMEDOUT',errno:' ETIMEDOUT'
syscall:' connect'
address:' 120.92.174.135',
port: 80 ,
Apr 17 2018 09:54:32: http://api.live.bilibili.com/activity/v1/task/receive_award{ Error: connect ETIMEDOUT120.92.218.109: 80
at 0bject._errnoException (uti1.js: 1024: 11)at_exceptionWithHostPort (uti1.js :1046: 20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js :1182: 14)code:' ETIMEDOUT'errno:' ETIMEDOUT'syscall:' connect'
address:' 120.92.218.109' ,
port: 80 }[  I

不用管这个

脚本直接在这卡住了呀，没有监听也没有抽奖

@lovezm 估计你已经被重点观察了，我同时挂了3个号都没问题

我觉得吧，凌晨关闭抽奖应该是设置开关，默认关闭的，也要照顾一下头铁的账户，我这挂了150+账号封号率小于等于1%

隔壁群说，好像是看ip检测的。

破站真的黑。白嫖都不让活

不是有代理IP的吗

Apr 18 2018 00:53:29 : 正在测试可用ip
Apr 18 2018 00:53:33 : 可用ip数量为 2
Apr 18 2018 00:53:44 : 已监听 :10080
之后就再也没有反应了。。不知道有没有办法解决

@Naexen 考虑网络问题，可能网络环境不是很好

我尝试着做了一下每日视频分享(APP) 不知道sign= 这个参数是哪个 ...

@lovezm
https://github.com/lzghzr/bilive_client/blob/c687e9059f1811bdc841c2fd4b56cb5a40dab92e/bilive/lib/app_client.ts#L90-L104

body :app_client_1.default.signQueryBase(access_key=${this.accessToken}&actionKey=appkey&aid=17931759&appkey=${this.appKey}&build=${this.build}&device=phone&mobi_app=${this.mobiApp}&platform=${this.platform}&sign=${paramsHash}&ts=${this.TS}),``
我是这样的。。好像哪里不对的样子

signQuestBase前面会自带基本参数，如果你需要自己给参数用signQuest

抓包的时候有一个callback 的请求，可能是那里的问题 @lovezm

试了一下还真不行哎，不会是微信后台给B站传数据吧

可以转发到动态或者消息吧，这样就不用过微信了

@zxc110123 看 #68

最近的辣条数少了好多啊，是因为延迟抽奖还是因为送小电视的少了啊（哭）

新活动没白嫖党的份了 辣条肯定少

抽奖暂停的时间支持跨天，比如22,2, 23,3，但是不要尝试输入奇奇怪怪的数字

抽奖暂停的时间写0就是不暂停对吧

对，写0,0也行

毕竟我是代挂的，不能停

实际上默认的3,9小电视数量一般小于5

延迟是ms为单位，那就是需要设置8000ms左右喽？

恩，一般我是设置为8000的

多谢大佬更新新功能

默认三点到九点是不抽奖的，不是你弄错了？

@lzghzr 我知道，我就挂到3点就不挂了，早上起来再开就发现都进去了，因为挂了半天只有抽奖提示，但是不抽奖，再试一下才发现都被封了，我昏了，记不清了是半夜还是起来的时候。

昨天我也被封了一天，第一次。过了0点就恢复了

最近没更新版本，想问下大佬有做领总督亲密吗？

@sxinxins 没有

大佬明明做了lotterycheck和lotteryjoin 咋不把监听跟上（滑稽）

一整台服务器的小号全部阵亡...包括我的大号...要是这个IP被封了就凉了。、。。。

昨晚B站咋了？为啥中了一堆小电视

昨晚的大奖都是小抱枕吗，大奖一次也没中过

是不是开始抓小号了 我单独挂一个号好久没封了

你们被封是不是因为  537.36 BiliApp/5240000这个User-Agent的锅(雾

昨晚房间273022出现了很多bug似的抽奖，不知道是不是官方有意为之

凉了呀。。。。

描述一下我昨晚看到的吧， 0：10分到0：40分之间房间273022开启了至少7个十分诡异的小电视抽奖，所有中奖几乎都是大奖，最低1个b克拉起步。中间还有2个小电视编号没有监听到，可能是弹幕遗漏或者是其它房间有相似的情况在发生，从行为表现看这几轮抽奖的特征是

抽奖只有房间内消息没有广播
抽奖时房间人气很低
抽奖不触发抽奖弹幕
中奖消息上有送小电视的人但是送礼榜上没有

此外该房间还有其它怪异的地方比如

主播看上去是个小号但是直播等级很高，直播房间名test，直播画面一直是摄像头拍地面固定画面
没有达到开通粉丝勋章权限但是有粉丝勋章，而且粉丝勋章名字无意义，长度超出官方限制
粉丝榜基本都是批量注册小号

房间有个提督看上去倒是比较像真的，但是礼物榜却又不太对。
除此之外该房间直播时没有隐藏、加密等异常状态，普通人也可以进入这个房间。
比较郁闷的是正当我准备把消息记录下来时刚连进去直播就被切断了
{
	"cmd": "CUT_OFF",
	"msg": "分区错误，未露脸直播",
	"roomid": 273022,
	"_roomid": 273022,
	"_date": "2018-05-03T16:39:10.776Z"
}

此后该房间再没有任何消息，结果什么都没记录到。
所以这要么是个赤果果的官方钓鱼房，要么是有人黑了b站的服务器拿来试水的，总而言之是不太妙的，目前看参与抽奖的帐号没有什么特殊异常情况，从结果看似乎更可能是后面一种情况，这次诡异抽奖哪怕是挂机大多数人也是不会参与到的，看情况这件事可能比较敏感，b站的也可能有人在视奸github，如果不太适合公开的话看完帮我删了吧，回复不用@ 我我会看的

那我就先删掉好了，点了watch的应该都会收到邮件，我在考虑要不要弄个tg群

@lzghzr 必须的，表示用TG比QQ还要频繁，而且能过掉很多脾气不好的人（雾

@FQrabbit 表示QQ比VX还要频繁，TG很少开。。。。
不过由于这个项目的内容，可能是TG更加合适。。。。

B站的封禁规则很迷，有时候会突然增强，例如前几天五一，，，
或许实际是B站对这种挂机行为睁一只眼闭一只眼，
然后到了感觉流量可能会很多那天就直接突然增强？

还是弄个tg群吧。

才发现tg建群要有联系人，可怜的我一个好友都没有

可怜的我甚至没有注册tg账号

@lzghzr 发个链接我加你

你加我 然后拉我进群吧https://t.me/caidog

大概能猜到ID吧 lztgzr

刚建了一个tg群

b站好像多了个小电视飞船？还是一直都有的？

小电视飞船就是以前的小电视，换个花样而已。

大佬们，我已经被关小黑屋第五天了，还没有解禁，我是不是凉了呀

摩天大楼也可以抽 端口和高能的一样 raffleid和pc的不一样 等一个加入？

问个很小白的问题，win64版本背景和字体默认颜色在文件夹哪个文件里能设置吗？
手动换了颜色，重新打开的时候还是这种蓝底红字，有点难受

右键边框点击属性里的颜色修改

发件人: xin notifications@github.com
发送时间: Tuesday, May 15, 2018 10:03:33 PM
收件人: lzghzr/bilive_client
抄送: root; Manual
主题: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
问个很小白的问题，win64版本背景和字体默认颜色在文件夹哪个文件里能设置吗？
手动换了颜色，重新打开的时候还是这种蓝底红字，有点难受
[image]https://user-images.githubusercontent.com/30524883/40061429-80bc7a84-588b-11e8-88ce-bb3ae8c8c1b7.png
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-389178571, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AaI4JQ43EAymcft8eU2kRjoSqwEkOmSIks5tyuA1gaJpZM4TATlN.

变回来应该是你没管理员权限启动

发件人: xin notifications@github.com
发送时间: Tuesday, May 15, 2018 10:03:33 PM
收件人: lzghzr/bilive_client
抄送: root; Manual
主题: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
问个很小白的问题，win64版本背景和字体默认颜色在文件夹哪个文件里能设置吗？
手动换了颜色，重新打开的时候还是这种蓝底红字，有点难受
[image]https://user-images.githubusercontent.com/30524883/40061429-80bc7a84-588b-11e8-88ce-bb3ae8c8c1b7.png
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-389178571, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AaI4JQ43EAymcft8eU2kRjoSqwEkOmSIks5tyuA1gaJpZM4TATlN.

最近B站可能要改版，但是我一直在加班，所以不是太能跟上进度，所以要感谢其他开发者贡献的代码。
这种情况到六月份会好一些

B站开始ban账号了，手动点击抽奖全部提示错误，改密码也无效。大家注意安全，我已经哭晕在考场途中 废了废了 工头招手叫我搬砖呢。

B站应该加强了脚本的检测，我基本上一打开脚本就会被封号，只能签到，瓜子抽奖都不能领。而且封号时间很长，似乎是只要开着脚本就不会解禁

PC端我记得昨天下午就改版了，如果你没有可能是分批更新的，等一段时间就好
脚本可以参与摩天大楼，如果你自己编译的话应该是可以区分道具的，参与不了可能是被封禁，想知道是不是被封禁，手动去直播间点一下看能不能参与就行了
node版本过低，nodejs官网的8.x和10.x都可以运行，我不太清楚deepin用的什么包管理，直接下载二进制文件也行

@l136297 用nvm

话说现在大楼不能抽么 ？
还是要怎么设置才能抽的？

問問現在手動按节奏风暴是按秒數倒數那裡嗎?(:3」∠)我按了沒反映...
我摩天大楼還能抽  應該不是被小黑屋吧...(:3」∠)

web端点不了图标+1，换浏览器也点不了。不会弹出验证码页面。

包长度异常

1.3.11的自动送礼好像挂了...重启也没用，而且也没显示直接就继续开始抽奖了...但是可以把options扔回1.3.10就可以送了

话说这是被关小黑屋了还是b站锁端口了？？
一直提示房间礼物信息就是没抽奖
今天挂了两个号，大号一直没动静，小号偶尔抽一下

根据观察总结，凌晨到清晨早操时间锁号概率大增(可能是固定时段假性抽奖陷阱检测)
请大家注意错开时段!乌拉!!!

现在封号不固定时间了吗？ 刚放出来又进去了

话说 老爷挂着有没有经验啊？

我解封了 现在开始都慎重点吧   封了半个月了我  才好  我是不敢无脑挂了

27号封了10天刚出来，开了85%的丢弃和15000的延迟，然后今天又进去了

b站到底是根据什么来封人的

@LuckyStar0026    感觉是不定期钓鱼  因为 我这两天疯狂挂 也没封号   反正  慎重点就行了  别哪天永久封就gg了

@yanjun0501 我和上面那位差不多，都是很谨慎地抽奖，但是每次抽个2天就被关10天，很烦

@LuckyStar0026   就是随机钓鱼的  这个现在没有稳定封号规律了 貌似

@LuckyStar0026 好像是只要氪金了就不容易进去，我大号年费老爷+俩月船，这半年就没进去过，还有俩小号一个年费老爷一个零氪，年费那个进去两次一次一天一次三天，零氪的挂了半个月整了1w金瓜子然后就出来了...硬盒花钱消灾，上船的我丢弃开1%啥事没有...绝了

@amuisipvr1355 你估计是人品好，我大号氪了3年大会员，小号零冲，只要一挂机都是一天一封，一封一天，我现在大小号只能轮流挂，一个号封一个号抽

@l136297 是不是因为大会员不属于直播那边的……

@Baninn 可以说是的23333

我开了2个号抽奖，不知道为啥现在每天都是2个号轮流抽奖，今天1号明天就是2号，后天就是1号，持续2个星期。。喜感。。。还有就是开了氪金貌似是真的不会封

年费老爷的我瑟瑟发抖，进去半个月了
codeisjobs notifications@github.com 于 2018年8月1日周三 17:17写道：

我开了2个号抽奖，不知道为啥现在每天都是2个号轮流抽奖，今天1号明天就是2号，后天就是1号，持续2个星期。。喜感。。。还有就是开了氪金貌似是真的不会封
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-409509577,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0jOvtNSmmW1rVoBxs5YBaTDGj1Iiks5uMXIhgaJpZM4TATlN
.

@lzghzr
继续氪，舰长什么的等着你

@lzghzr 继续氪吧，上个船啥的...而且你不是奶你小号的勋章嘛，还能回点本...´_>`

@amuisipvr1355 表示除了之前玩风暴玩过火被v3 api封了一星期之外就没进过小黑屋，这个真的有点玄乎啊

@Vector000 3410你算运气好吧...而且你自己改的不是还有模拟app抽吗...只不过这东西确实有点玄学，我60个用来玩的那几个前10个就GG了，但是同时砸东西的剩下的50个啥事没有...前几天我又去皮，也没事...绝了...话说你封之后氪过金嘛...反正我是氪金救援....emm

如果上面说的“开了85%的丢弃、0到10点停止抽奖和15000的延迟”还被封的话，有点好奇b站是怎么判定是不是脚本的，这样也完全可以是一个整天盯着电脑手动抽奖的人的行为模式

手段很多啊，因为手动抽奖会触发一系列的东西，比如进房间，连接弹幕服务器，获取房间信息，抽奖信息，访问统计等等，脚本只是过去抽奖
Lucky Star notifications@github.com 于 2018年8月1日周三 23:40写道：

如果上面说的“开了85%的丢弃、0到10点停止抽奖和15000的延迟”还被封的话，有点好奇b站是怎么判定是不是脚本的，这样也完全可以是一个整天盯着电脑手动抽奖的人的行为模式
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-409619849,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0nR1DANxlRrOVWE011KlivzjB1Nbks5uMcwAgaJpZM4TATlN
.

请问设置不参加抽奖时间的时候，0.5能代表0时30分吗 @lzghzr

我暂停了一下脚本，更新一下然后就登陆不上 了

抽奖暂停我设 1,18 但是 16 点的时候有获得辣条... 暂停不了?(:3」∠)

@l136297  我现在也是只监听不抢 你是怎么解决的啊

我遇到一个很奇怪的问题,我明明被封了但还是可以抽到零星几个辣条,去那几个直播间也没发现有什么特别的,真是神奇,还有按说被封不能领取宝箱的瓜子,但是今天我领到了第一轮第一个宝箱,其他的领不了,真是神奇...

抽奖暂停我设的是0到9,0点以后就没抽了，但是宝箱领到第三轮的最后一个的时候被封了，难道领宝箱也会出问题吗？

不太清楚，有人说被封也会领到宝箱，不过领不完
On Wed, Aug 15, 2018, 11:27 JerryRich notifications@github.com wrote:

抽奖暂停我设的是0到9,0点以后就没抽了，但是宝箱领到第三轮的最后一个的时候被封了，难道领宝箱也会出问题吗？
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-413083388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0kTtD279TLc7dEfc-_nIgtXVGaBnks5uQ5UPgaJpZM4TATlN
.

@lzghzr 可是我0点之后也没有抽奖，0点前也没被封

b站是不是更新了api，感觉今天4点多之后无法自动抽奖，只能手动点，没有log记录抽奖提示也没抽奖？

@Jovy310 已更新

话说封了一个小时突然放出来20分钟然后又进去了是什么操作，这log看的我一脸懵逼

B站改封禁策略了？

@10lumiya10  话说我昨天也是 放出来一会又进去了 抽了两辣条

问下各位再用的大佬们和作者大大。这个有双端心跳的功能吗？还有那个server酱的SCKEY是什么意思呢？看不懂说明。望各位告知~谢谢 @lzghzr

还有，服务端如果想用的话应该怎么做呢？

@zhouxiaoxiao6

「Server酱」，英文名「ServerChan」，是一款「程序员」和「服务器」之间的通信软件。
服务端可以参考通用配置。

@reloader91 B站想查很简单，看进房间的历史记录就够了，正常情况下不可能不进房间就抽奖的吧

@Baninn 进入房间的模拟早已实现了吧

没有进房模拟，太浪费资源了
On Mon, Aug 20, 2018, 14:01 reloader91 notifications@github.com wrote:

@Baninn https://github.com/Baninn 进入房间的模拟早已实现了吧
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-414205603,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0huL1glDX5Mz3VQoTWXwhKKHQvvSks5uSlCrgaJpZM4TATlN
.

soga....那我就不继续丢人了_(:3」∠)_

@ol416 知道了 我已经配置了 「Server酱」 谢谢

大佬，出了新礼物，小金人，不知道需不需要升级脚本啊

@ShmilyChen 今天又重新部署了一遍，我这边能抽小金人了(^▽^)

@Baninn TamperMokey脚本的有进房模拟，但是我照样被ban，我想可能是和挂的太久有关。

大佬，又出新的领取亲密度的一个东西，在安卓最新版里面可以看到，总督可以领取20点亲密度，提督5点，舰长1点亲密度！

这个在 #103 有讨论，除非重启bilive_server项目，否则是不会加这个功能的（每个分区监听的那几个房间可以）
On Tue, Aug 28, 2018, 16:01 zhouxiaoxiao6 notifications@github.com wrote:

大佬，又出新的领取亲密度的一个东西，在安卓最新版里面可以看到，总督可以领取20点亲密度，提督5点，舰长1点亲密度！
[image: qezdezsy qjuuzvodaa7ck]
https://user-images.githubusercontent.com/39050345/44709193-90480980-aadb-11e8-885b-4bc9c5820d33.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-416488900,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0mtIQ00gdlNZYBGoiC0-ByzGrI1uks5uVPjGgaJpZM4TATlN
.

感觉进小黑屋完全是碰运气，我停了半个月没挂，昨天挂了4小时就又被封了

Aug 30 2018 21:28:01 : https://data.bilibili.com/gv/ { Error: getaddrinfo EAI_AG
AIN data.bilibili.com data.bilibili.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'data.bilibili.com',
host: 'data.bilibili.com',
port: 443 }
Aug 30 2018 21:28:13 : https://app.bilibili.com/x/v2/display/id?actionKey=appkey
&appkey=&build=&mobi_app=android&platform=android&ts=&sign= { Error: getaddrinfo EAI_AGAIN app.
bilibili.com app.bilibili.com:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'app.bilibili.com',
host: 'app.bilibili.com',
port: 443 }
这是什么报错（部分打码了）

@chenyitian2004 看起来是域名解析出了问题

请问各种抽奖中奖是怎么算的，是第一个点击抽奖的人中嘛。。。
还有请问大佬可以把这个软件搬运到吾爱破解论坛吗（52pojie.cn）

我用我的小米6手机和安卓模拟器用sever酱安卓客户端接受礼物统计消息的时候sever酱安卓客户端都会卡死，请问是什么原因。。。

了解

只会推送小电视大奖，其他的例如银瓜子，扭蛋都没有
On Thu, Sep 6, 2018, 13:25 cris3980 notifications@github.com wrote:

sever酱不推送获奖通知了？好几条中奖信息没推送，小电视、大楼、金人的都没有推送，只推每天定时的统计....
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lzghzr/bilive_client/issues/69#issuecomment-418968649,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMxV0njdNG2L0qDNF58r7my0FzZTHpneks5uYLHBgaJpZM4TATlN
.

宝箱无法全部领取了
Sep 10 2018 19:41:08 : https://api.live.bilibili.com/mobile/userOnlineHeart?access_key=27675e87e0b8c
af90662fa7779224ee5&actionKey=appkey&appkey=1d8b6e7d45233436&build=5291001&mobi_app=android&platform
=android&ts=1536579667&sign=a89626147ef8490cff29b30f4aab43cd { Error: read ECONNRESET
at TLSWrap.onread (net.js:660:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
Sep 10 2018 19:41:08 : https://api.live.bilibili.com/mobile/userOnlineHeart?access_key=c21826a05ee5b
18ce398a8c938c88a82&actionKey=appkey&appkey=1d8b6e7d45233436&build=5291001&mobi_app=android&platform
=android&ts=1536579667&sign=883954b3aba75e814c2454970b7e7e80 { Error: read ECONNRESET
at TLSWrap.onread (net.js:660:25) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }

了解
From: cris3980
Sent: Thursday, September 20, 15:25
Subject: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
To: lzghzr/bilive_client
Cc: lzzr, Mention
今天B站更新了，总督有广播了
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-423070642, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMxV0u7I3Y504opwdGMK4wu3-FyO_pHNks5uc0L9gaJpZM4TATlN.

npm install时出现了这个问题:npm WARN bilive_client@1.3.13 No repository field.怎么解决啊

我想知道这里设置的时间是服务器时间还是+8区的时间？

+8区

From: Evan notifications@github.com
Sent: Wednesday, October 17, 2018 12:09:46 PM
To: lzghzr/bilive_client
Cc: lzzr; Mention
Subject: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
我想知道这里设置的时间是服务器时间还是+8区的时间？
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-430482985, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMxV0nJ_Ng4jX5N5upiS93uUX-eY93EBks5ulq2KgaJpZM4TATlN.

@lzghzr那个npm install 失败怎么办啊npm WARN bilive_client@1.3.13 No repository field.npm start 也失败了

目录没搞错吗？

From: 1830562824 notifications@github.com
Sent: Wednesday, October 17, 2018 1:07:02 PM
To: lzghzr/bilive_client
Cc: lzzr; Mention
Subject: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
@lzghzrhttps://github.com/lzghzr那个npm install 失败怎么办啊npm WARN bilive_client@1.3.13 No repository field.npm start 也失败了
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-430491028, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMxV0tgjazhabgn5JcuZQQ2Dr5jaapByks5ulrr2gaJpZM4TATlN.

貌似登录挂了...

恩，好像是挂了

From: cris3980 notifications@github.com
Sent: Thursday, October 25, 2018 2:12:25 PM
To: lzghzr/bilive_client
Cc: lzzr; Mention
Subject: Re: [lzghzr/bilive_client] 意见反馈及常见问题整理 3 (#69)
貌似登录挂了...
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lzghzr/bilive_client/issues/69#issuecomment-432927097, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMxV0vjlVuwaT3VvoonOvdq-LS7J_Nm9ks5uoVZJgaJpZM4TATlN.


text:
PSReadLine Missing on Windows 10

I have a version of Windows 10 that was updated from the Tech Preview to the RTM version, and it appears that whatever version I got did not have PSReadline included and now even though I'm on the RTM I don't have it.
Is there anyway for me to easily get the 1.1 version of PSReadLine manually?  Installing a version from PSGet still gives me an earlier version which has issues with Win 10.
Also, is there every going to be any updated documentation indicating that PSReadLine is included with Win10?  Could be worth mentioning ANYWHERE on the page.  The only mention in the changenotes for 1.1 is a namespace rename.

That's really weird.  I'm guessing that you could find a WIndows 10 system with 1.1 on it, copy the contents of the folder C:\Program Files\WindowsPowerShell\Modules\PSReadline\1.1\ to the same location on your Win 10 machine.

Based on that comment, it seems like building whatever is currently checked in won't produce the same thing as is included in Windows.  Is that true?
I should be able to find another Win10 machine I can grab the binaries from.  Feel free to close the bug.

Building the current master should be very close, if not the same, as what shipped in Win10.  You wouldn't get the same binaries though.  That should be fine in most cases.

source: gharchive/issue

authors: lzybkr rkeithhill veleek

repo: lzybkr/PSReadLine

license_type: permissive

license_source: github-api


text:
found an issue in VS code integrated terminal

PS D:\DevEnv\jsWS\AngularJS_1.x\dtep-browser-client-with-gulp-setup>
lp-setup> ^B
Oops, something went wrong.  Please report this bug with th
e details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issu
es/new

Last 57 Keys:
g u l p Spacebar i n j e c t Enter
g u l p Spacebar c l e a n Enter
g Backspace Backspace UpArrow UpArrow Enter
UpArrow Enter
UpArrow UpArrow UpArrow Enter
UpArrow UpArrow Enter
UpArrow UpArrow Enter
UpArrow UpArrow Enter
UpArrow UpArrow Enter
UpArrow UpArrow UpArrow Enter
UpArrow UpArrow UpArrow Enter
Ctrl+b Backspace
Exception:
System.ArgumentException: Destination array was not long en
ough. Check destIndex and length, and the array's lower bou
nds.
at System.Array.Copy(Array sourceArray, Int32 sourceInde
x, Array destinationArray, Int32 destinationIndex, Int32 le
ngth, Boolean reliable)
at System.Array.Copy(Array sourceArray, Array destinatio
nArray, Int32 length)
at Microsoft.PowerShell.PSConsoleReadLine.ReallyRender()
at Microsoft.PowerShell.PSConsoleReadLine.BackwardDelete
Char(Nullable1 key, Object arg)    at Microsoft.PowerShell.PSConsoleReadLine.ProcessOneKey( ConsoleKeyInfo key, Dictionary2 dispatchTable, Boolean ign
oreIfNoAction, Object arg)
at Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrins
ics)
PS D:\DevE
PS D:\DevE
PS D:\DevEnv\jsWS\AngularJS_1.x\dtep-browser-client-with-gulp-setup>

Dupe of many like #491.


text:
Problem

It doesn't work for me in Fluency builder
I do exercises, and add some minutes but it shows nothing
pls help

u have to finish all the lesson (thats how it worked for me)

How to remove hours

license: MIT


text:
Bug reported at pseudoimport-html

This is a very important bug

Close per #41

license: isc

license_source: bigquery


text:
Specify which environments are supported

According to this comment using ESP-IDF directly is not supported: https://github.com/m5stack/M5Unified/issues/36#issuecomment-1207193364

Do you have a comment for my, why hit was closed? I see value in declaring which IDE/environments are support and at which point you are going off-roads.

When using M5Unified with ESP-IDF, do not use ArduinoESP32 as a component.

source: gharchive/pull-request


text:
Added my own blog - sheep.horse

Feel free to ignore if you don't think it meets your criteria.

what a nice blog subscribed, thanks!


text:
Occasional "PasswordVault The system cannot find the path specified." error when storing data

The Windows implementation gives occasional errors with full error description of:

ERROR SAVE PasswordVault The system cannot find the path specified.

The error "The system cannot find the path specified" indicates that the PasswordVault file might be somehow missing or alternatively it is locked by another operation.
Both c++ and c# implementations initialize a new PasswordVault instance upon reading or writing data. My theory is, that upon writing data the PasswordVault file is locked and if you end up invoking two write operations simultaneously, you'll get the error.
Packages installed
"react-native-sensitive-info": "^6.0.0-alpha.9"
"react-native": "0.65.1"
"react-native-windows": "0.65.4"

It seems that we have solution for that issue.
We create one instance of const Windows::Security::Credentials::PasswordVault PasswordVault = Windows::Security::Credentials::PasswordVault(); PasswordVault object and use that same instance on all methods.
We will send PR later for this.

authors: juhasuni tero-paananen

repo: mCodex/react-native-sensitive-info

license: mit


text:
j2cl-locale 0fcefc0fa020ac7f3bd0bfbac2aba1ea1b0ff978 20200525

https://github.com/mP1/j2cl-locale/pull/86
TimeZoneOffsetAndDaylightSavings.useDaylightTime

Closes #67


text:
midea-discover -a YOUR_ACCOUNT  YOUR_ACCOUNT不能手机号，提示this account does not exist'

midea-discover -a YOUR_ACCOUNT -p YOUR_PASSWORD
YOUR_ACCOUNT 是手机号，会提示
\msmart\cloud.py", line 220, in throw
raise ValueError(error_code, message)
ValueError: (3102, 'this account does not exist')

账号当然不存在，登录的是海外美的APP
你需要注册个账号即可，不需要添加设备，在README中给出链接了

authors: iChenlife mac-zhou

repo: mac-zhou/midea-ac-py


text:
Fix: import gdnative prelude in lib.rs template

The default lib.rs template has a compiler error with newer versions of the gdnative library. Importing the Variant type is now required to run the godot_init macro. I decided to include the prelude instead of just importing Variant to hopefully prevent these API changes from breaking things in future versions.
Test Plan:
ftw new test
cd test
ftw build

Error Output:
error[E0433]: failed to resolve: use of undeclared type `Variant`
  --> rust\src\lib.rs:13:1
   |
13 | godot_init!(init);
   | ^^^^^^^^^^^^^^^^^ not found in this scope
   |
   = note: this error originates in the macro `$crate::godot_nativescript_init` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
   |
4  | use gdnative::core_types::Variant;
   |

For more information about this error, try `rustc --explain E0433`.
error: could not compile `example` due to 2 previous errors
 ERROR: The system cannot find the file specified. (os error 2)
Error: ()

lib.rs
mod game;
mod spinning_cube;

use gdnative::prelude::{godot_init, InitHandle};

// Function that registers all exposed classes to Godot
fn init(handle: InitHandle) {
    handle.add_class::<game::Game>();
    handle.add_class::<spinning_cube::SpinningCube>();
}

// macros that create the entry-points of the dynamic library.
godot_init!(init);

Hi @aclave1,
Thank you for filing this issue, may I know what target, rust version, ftw version and the operating system you are running ftw on? Based on my initial test, I seem to don't get the error that you are getting. Please see screenshot below.

I'm on NixOS, x86_64-unknown-linux-gnu target, rust v1.64.0 and ftw v0.10.0
Mike

I'm on windows 11, target is x86_64-pc-windows-msvc, rust 1.63.0, ftw 0.10.0. One thing I see from your logs is the usage of gdnative v0.11.0. The version of gdnative that mine is using is 0.10.1. This is a project generated by ftw new.  Maybe my local copy of godot-rust-template is cached?

repo: macalimlim/ftw


text:
'generator.bigfive.world' is down

How may I get the results to generate and display with 'generator.bigfive.world' down? I tried running the generator micro api on my local machine and then routing the config/index.js file to the port I had it up on but had no success.

Hello @brianbaso!
Sorry for the late answer. I'm currently (slow-) working on a total refactor, see https://github.com/Alheimsins/bigfive-web for code.
@zrrrzzt also have some working code at https://github.com/zrrrzzt/b5-web

@brianbaso You can see the b5-web in action at https://b5.allthethings.win
This is an attempt to make everything run from a static site.

Ok great, thanks for the insights 👍

http://bigfive-test.com is btw up and working now, the code is still a mess though.
Feel free to test and bring me issues :)

authors: brianbaso maccyber zrrrzzt

repo: maccyber/bigfive-web


text:
Setup new staging and prod environments

Opening this issue to document the setup of new staging and prod environments.
We'd like to roll out some changes to the label bot frontend (see kubeflow/code-intelligence#90).
Trying to figure out how to roll things safely is revealing some areas for improvement in the way
our staging and prod clusters are setup.

We recently created a new GitHub App kf-label-bot-dev (see kubeflow/code-intelligence#84) to correspond to the dev/staging instance of the label bot

We also cleaned up the deployment of the backend (See kubeflow/code-intelligence#70) so we have separate namespaces for dev vs. prod

We'd like a similar setup for the label bot frontend with a dev instance using the dev label bot and the prod instance using the prod instance.

It looks like the prod instance is currently running in

project: github-probots
cluster: kf-ci-ml
namespace:  mlapp

It looks like there are two separate ingresses in this namespace
kubectl get ingress
NAME        HOSTS               ADDRESS         PORTS     AGE
ml-gh-app   predict.mlbot.net   35.190.23.225   80, 443   264d
mlbot-net   mlbot.net           34.95.77.230    80        264d

The predict.mlbot.net endpoint is handling the webhook for the issue-label-bot GitHub App
mlbot.net is handling the web app
They are both pointing at the same flask app/ K8s service

Looks like there are two ingresses just to allow provisioning two SSL certificates corresponding to two domains

Here's my plan

Create namespace label-bot-dev with a dev instance of the label bot
Configure the domain label-bot-dev.mlbot.net to use this server
Configure namespace label-bot-prod with a prod instance
Configure the domain label-bot-prod.mlbot.net to use this server
Update the label bot webhook to use label-bot-prod.mlbot.net
Update mlbot.net to point to the service in label-bot-prod namespace

Created static IP resources in github-probots named

label-bot-dev
label-bot-prod

I created CNAME records corresponding to those addresses as well.

https://label-bot-dev.mlbot.net/ is now up.

For the dev instance the webhooks are failing with 405's method not allowed.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>405 Method Not Allowed</title>

Method Not Allowed

The method is not allowed for the requested URL.

Maybe I have the wrong URL for the webhook; maybe there's a missing path?

Going to delete the old mlapp namespace. Here's a list of the things currently running in that namespace.
NAME                    TYPE       CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
service/ml-github-app   NodePort   10.7.248.83   <none>        3000:31195/TCP   392d

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ml-github-app   3/9     9            3           392d

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/ml-github-app-549bd9d59c   0         0         0       253d
replicaset.apps/ml-github-app-59456b86f9   0         0         0       380d
replicaset.apps/ml-github-app-67fb558bd7   0         0         0       240d
replicaset.apps/ml-github-app-68c85996c7   0         0         0       358d
replicaset.apps/ml-github-app-6b8458fdf8   9         9         3       236d
replicaset.apps/ml-github-app-74d65cb87f   0         0         0       240d
replicaset.apps/ml-github-app-75994457bb   0         0         0       382d
replicaset.apps/ml-github-app-78cbfb4cb9   0         0         0       383d
replicaset.apps/ml-github-app-dc6cc8c7b    0         0         0       358d
replicaset.apps/ml-github-app-ff776479d    0         0         0       253d
replicaset.apps/ml-github-app-ffb596777    0         0         0       236d

namespace deleted.

repo: machine-learning-apps/Issue-Label-Bot


text:
Training a model should progressively log its progress

I'm submitting a ...
[/] feature request

Summary
I'm thinking we can expose something like

const clusters = kmean.fit({
   X: [[1, 2], [1, 4], [1, 0], [4, 2], [4, 4], [4, 0]],
   log: function(msg) {
     // msg contains the details about the training progress
   }
 });

Considerations:

Enable it optionally

Question: is this feature allready implemented or under delvelopment?

repo: machinelearnjs/machinelearnjs


text:
Exceptions for all methods

create Exceptions for all methods
CreateExeption has already done.

Created all Exceptions for methods.
Need to implement them to methods correctly.

All exceptions have done.


text:
Problems with special characters

Command:
$ hyhyhy new
Then filling the basic information, the bash throws an error with encoding special characters (like ñ a spanish character):
"error: "\xC3" on US-ASCII. Use --trace to view backtrace"

s/special/non-ASCII/g

Try now. Check that it is still a mistake.
https://github.com/maciejczyzewski/hyhyhy/commit/2f6a0601d870dfeb21c9b4e3799df1981049716a

Should I reinstall hyhyhy from the gem?
Description passes, not author (My name uses the ñcharacter)
Same for $ hyyhy build throws same error: error: "\xC3" on US-ASCII. Use --trace to view backtrace

Yes. Try to reinstall.

Sorry @maciejczyzewski , uninstalled and reinstalled gem. Same error.

Finally, now it should work! Check, pls.

Awesome @maciejczyzewski , now building perfectly. Closing issue, thanks a lot. Let's try hyhyhy in deep.

authors: juanbrujo maciejczyzewski pluma

repo: maciejczyzewski/hyhyhy


text:
Add more metrics

precision@k
recall@k
AUC

As per https://github.com/maciejkula/spotlight/issues/55

@mkarakaya,
You should contribute your idea! Here are my thoughts having helped out in the past on spotlight evaluation metrics:

Yes prec-recall is fine
Of course
I asked the same question, and @maciejkula's response was as you guess -- an array. Personally, I would not be opposed to a single result however, in the case that integrating tons of AUCs were slow and could be sped up somehow by aggregating first.
Sure

Also, have you considered a confusion matrix or at least F1-score?
Good luck!

authors: maciejkula nikisix

repo: maciejkula/spotlight


text:
Add a guide to get started

How to install a lightning wallet in order to sign up and  login

Added "Getting Started" under Help menu

which opens the guide in the wiki:
https://github.com/macterra/artx-market/wiki/Getting-Started

repo: macterra/artx-market


text:
Screenshots from running VM

I think it will be handy to allow to capture screenshots of the running VM. However, right now curie executes the VM synchronously — curie run .. blocks until you quit. Which is a good feature I think, but it disallows us to implement curie make-screenshot command - this command will run in a separate process.
I'm thinking of allowing curie to expose a (local unix?) socket, over which the request to make screenshot can be sent. Running curie process with a VM would receive such request and perform an action, taking screenshot storing it into file. Also, it may send back the reply, indicating that request has been processed.
What are the alternatives?

to process something like SIGUSR1, but that is not scalable and flexible, e.g. if we wanted to allow processing more events, SIGUSR1 won't let us do that.
web socket — too broad I think, everyone would then be able to make screenshots over the network
any other ideas?

Probably good to address https://github.com/macvmio/curie/issues/57 first.

authors: beefon marciniwanicki

repo: macvmio/curie


text:
thread failed with: fread() failed

already got 20 plots with madmax.. suddenly stopped at phase 2-3.. I've got this error message
terminated called after throwing an instance of 'std::runtime_error'
what():   thread failed with: fread() failed
Aborted (core dumped)
please help 🙏🏿
thank you

disk failure?

I have the same issue but it does not even allow for the start of the plotting to begin using Ram as the second temporary directory. I have about 32 GB of Ram and created a 10 GB Ram mnt/ramdisk drive and have AMD® Ryzen 7 5800x 8-core processor × 16 (16 threads available and used 10 for the madmax plotter). P.S. Thank you for your contributions

disk failure?
something else is going on......
i've had it on a couple of long runs when i tried to restart the plotter.
a restart fixes it..

yes.. it's disk failure, i try to trim it and it run again nicely
thank you

@eze21r how did you try to trim it?
Im getting that error,, do you run the trim command manually or what?

@vvavepacket yeah, manually with this command
sudo fstrim -v /

I keep getting this and yet the whole system checks out.
ram is ECC
ssd is raid & showing zero errors.
but a reboot fixes it every time.

I keep getting this and yet the whole system checks out.
ram is ECC
ssd is raid & showing zero errors.
but a reboot fixes it every time.

same

Been getting it for weeks, and i keep saying there is a "leak".
only solution i found was a reboot.

I had the similar issue with my RAID 0 disk. One disk failed.
Removed the failed disk and made new RAID array, everything working fine now.


text:
Error when Tradfri GU10 is offline

Hey
I have a Raspberry Pi B+ with Homebridge and this Plugin installed.
There are 11 Tradfri GU10 (LED1837R5) connected. When a lamp is switched off (Offline, no power), then I get the following errors. These errors block the plugin completely.  The Home app no longer works for any Zigbee device.
System Information:
Raspbian GNU/Linux Buster (10)
Homebridge: v1.1.7
Node.js Version: v14.15.4
Npm Version: v6.14.11
Homebridge Zigbee Nt: v2.0.5
CC2531 Adapter
[09/02/2021, 13:07:29] [ZigBee] Reading 'brightness' to '0x14b457fffe450781' failed: 'Error: Read 0x14b457fffe450781/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:07:29] [ZigBee] Reading 'state' to '0x680ae2fffe39c853' failed: 'Error: Read 0x680ae2fffe39c853/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:07:49] [ZigBee] Reading 'brightness' to '0x680ae2fffe31a29e' failed: 'Error: Read 0x680ae2fffe31a29e/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:07:49] [ZigBee] Reading 'state' to '0x680ae2fffe34e82a' failed: 'Error: Read 0x680ae2fffe34e82a/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:08:09] [ZigBee] Reading 'state' to '0x680ae2fffe31a29e' failed: 'Error: Read 0x680ae2fffe31a29e/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:08:09] [ZigBee] Reading 'brightness' to '0x680ae2fffe34e82a' failed: 'Error: Read 0x680ae2fffe34e82a/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:08:29] [ZigBee] Reading 'state' to '0x680ae2fffe3b1503' failed: 'Error: Read 0x680ae2fffe3b1503/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:08:30] [ZigBee] Reading 'state' to '0x680ae2fffe37c77b' failed: 'Error: Read 0x680ae2fffe37c77b/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:08:50] [ZigBee] Reading 'brightness' to '0x680ae2fffe3b1503' failed: 'Error: Read 0x680ae2fffe3b1503/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:08:50] [ZigBee] Reading 'brightness' to '0x680ae2fffe37c77b' failed: 'Error: Read 0x680ae2fffe37c77b/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:09:10] [ZigBee] Reading 'state' to '0x680ae2fffe39c853' failed: 'Error: Read 0x680ae2fffe39c853/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:09:10] [ZigBee] Reading 'state' to '0x14b457fffe450781' failed: 'Error: Read 0x14b457fffe450781/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:09:30] [ZigBee] Reading 'state' to '0x680ae2fffe31a29e' failed: 'Error: Read 0x680ae2fffe31a29e/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))' [09/02/2021, 13:09:30] [ZigBee] Reading 'state' to '0x680ae2fffe3b1503' failed: 'Error: Read 0x680ae2fffe3b1503/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:09:50] [ZigBee] Reading 'state' to '0x680ae2fffe37c77b' failed: 'Error: Read 0x680ae2fffe37c77b/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))' [09/02/2021, 13:09:50] [ZigBee] Reading 'state' to '0x680ae2fffe34e82a' failed: 'Error: Read 0x680ae2fffe34e82a/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Thanks for your help
Chris

This will be addressed in the next release. Thanks for reporting

Thank you for your fast answer.
Now I have this error... is this a hardware problem or I have to open a new issue? Restart was not successful
[09/02/2021, 18:42:33] [ZigBee] Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)     at ZStackAdapter.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:99:27)     at Generator.throw (<anonymous>)     at rejected (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65) [09/02/2021, 18:42:33] [ZigBee] Retrying connect to hardware [09/02/2021, 18:42:38] [ZigBee] Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'     at Znp.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)     at Generator.next (<anonymous>)     at /usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:27:71     at new Promise (<anonymous>)     at __awaiter (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:23:12)     at SerialPort.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:144:65)     at SerialPort._error (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:198:14)     at /usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/node_modules/@serialport/stream/lib/index.js:242:12

This is an error of communication with the dongle. You should try to restart your raspberry

@Chrigigi Could you try the unstable version and tell me how it goes? Install it using this command:
npm i homebridge-zigbee-nt@unstable -g --unsafe-perm

@madchicken i have try to install the plugin

uninstalled plugin
clean devices Cache
install plugin with your command

The plugin did not installed
See install log below:
`pi@homebridge:/var/lib/homebridge $ npm i homebridge-zigbee-nt@unstable -g --unsafe-perm
npm WARN deprecated http2@3.3.7: Use the built-in module in node 9.0.0 or newer, instead
npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm WARN notsup Unsupported engine for http2@3.3.7: wanted: {"node":">=0.12.0 <9.0.0"} (current: {"node":"14.15.4","npm":"6.14.11"})
npm WARN notsup Not compatible with your version of node/npm: http2@3.3.7
npm WARN evergreen-ui@5.1.2 requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN evergreen-ui@5.1.2 requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-scrollbar-size@2.1.0 requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-tiny-virtual-list@2.2.0 requires a peer of react@15.x || 16.x but none is installed. You must install peer dependencies yourself.
npm WARN ui-box@4.1.0 requires a peer of react@^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-event-listener@0.5.10 requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN react-textarea-autosize@6.1.0 requires a peer of react@>=0.14.0 <17.0.0 but none is installed. You must install peer dependencies yourself.
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/local/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!  [Error: EACCES: permission denied, access '/usr/local/lib/node_modules'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/local/lib/node_modules'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2021-02-11T18_38_52_384Z-debug.log
pi@homebridge:/var/lib/homebridge $ `

I have do a clean install from my Homebridge and install your version with the command:
sudo npm i homebridge-zigbee-nt@unstable -g --unsafe-perm
I have try to add new devices, but i don't see the device in HomeKit or in the Homebridge UI:
[12/02/2021, 08:31:46] [ZigBee] Zigbee: allowing new devices to join.
[12/02/2021, 08:32:05] [ZigBee] Accepting joining whitelisted device '0xbc33acfffea940cb'
[12/02/2021, 08:32:05] [ZigBee] Device joined, Adding 0xbc33acfffea940cb (undefined - undefined)
[12/02/2021, 08:32:05] [ZigBee] Interview progress started for device 0xbc33acfffea940cb
[12/02/2021, 08:32:05] [ZigBee] Accepting joining whitelisted device '0xbc33acfffea940cb'
[12/02/2021, 08:32:07] [ZigBee] Initializing ZigBee device: 0xbc33acfffea940cb - undefined - undefined
[12/02/2021, 08:32:07] [ZigBee] Unsupported ZigBee device: 0xbc33acfffea940cb - undefined - undefined
[12/02/2021, 08:32:09] [ZigBee] Accepting joining whitelisted device '0xbc33acfffea940cb'
[12/02/2021, 08:32:09] [ZigBee] Accepting joining whitelisted device '0xbc33acfffea940cb'
[12/02/2021, 08:32:09] [ZigBee] Device announce: 0xbc33acfffea940cb (undefined - undefined)
[12/02/2021, 08:32:09] [ZigBee] Not initializing device 0xbc33acfffea940cb: interview process still not completed
[12/02/2021, 08:32:20] [ZigBee] Successfully interviewed device: IKEA of Sweden - TRADFRI bulb GU10 WW 400lm
[12/02/2021, 08:32:21] [ZigBee] Initializing ZigBee device: 0xbc33acfffea940cb - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:32:21] [ZigBee] Unsupported ZigBee device: 0xbc33acfffea940cb - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:33:08] [ZigBee] No device found from message {
  type: 'commandQueryNextImageRequest',
  device: Device {
    ID: 7,
    _type: 'Router',
    _ieeeAddr: '0xbc33acfffea940cb',
    _networkAddress: 30884,
    _manufacturerID: 4476,
    _endpoints: [ [Endpoint], [Endpoint] ],
    _manufacturerName: 'IKEA of Sweden',
    _powerSource: 'Mains (single phase)',
    _modelID: 'TRADFRI bulb GU10 WW 400lm',
    _applicationVersion: 33,
    _stackVersion: 99,
    _zclVersion: 3,
    _hardwareVersion: 2,
    _dateCode: '20181203',
    _softwareBuildID: '2.1.022',
    _interviewCompleted: true,
    _interviewing: false,
    _skipDefaultResponse: false,
    meta: {},
    _lastSeen: 1613115188438,
    _linkquality: 26
  },
  endpoint: Endpoint {
    ID: 1,
    profileID: 260,
    deviceID: 257,
    inputClusters: [
      0, 3,    4, 5,
      6, 8, 4096
    ],
    outputClusters: [ 5, 25, 32, 4096 ],
    deviceNetworkAddress: 30884,
    deviceIeeeAddress: '0xbc33acfffea940cb',
    clusters: { genBasic: [Object] },
    _binds: [],
    _configuredReportings: [],
    meta: {}
  },
  data: {
    fieldControl: 1,
    manufacturerCode: 4476,
    imageType: 16643,
    fileVersion: 553788977
  },
  linkquality: 26,
  groupID: 0,
  cluster: 'genOta',
  meta: {
    zclTransactionSequenceNumber: 0,
    manufacturerCode: null,
    frameControl: {
      frameType: 1,
      manufacturerSpecific: false,
      direction: 0,
      disableDefaultResponse: false,
      reservedBits: 0
    }
  }
}

After restart the Homebridge
[12/02/2021, 08:35:11] [ZigBee] Successfully started ZigBee service
[12/02/2021, 08:35:11] [ZigBee] ZigBee platform initialized @ 0x00124b001ccdf5aa
[12/02/2021, 08:35:11] [ZigBee] Reuse accessory from cache with uuid 6895c160-ba25-497f-b805-38071c751c56 and name zigbee:permit-join
[12/02/2021, 08:35:11] [ZigBee] Zigbee: disabling joining new devices.
[12/02/2021, 08:35:11] [ZigBee] PermitJoin accessory successfully registered
[12/02/2021, 08:35:11] [ZigBee] Reuse accessory from cache with uuid 4994893c-ea77-4292-a4ad-09e1f36f7099 and name zigbee:touchlink
[12/02/2021, 08:35:11] [ZigBee] TouchLink accessory successfully registered
[12/02/2021, 08:35:11] [ZigBee] Initializing ZigBee device: 0x5c0272fffe6afeca - TRADFRI on/off switch - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Reuse accessory from cache with uuid 359b8237-d2ec-458a-a561-35e2cca3a264 and name 0x5c0272fffe6afeca
[12/02/2021, 08:35:11] [ZigBee] Registered device: 0x5c0272fffe6afeca IKEA of Sweden TRADFRI on/off switch
[12/02/2021, 08:35:11] [ZigBee] Mounting device 0x5c0272fffe6afeca...
[12/02/2021, 08:35:11] [ZigBee] Initializing ZigBee device: 0x680ae2fffe2f6fd8 - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Unsupported ZigBee device: 0x680ae2fffe2f6fd8 - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Initializing ZigBee device: 0x680ae2fffe31abbf - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Unsupported ZigBee device: 0x680ae2fffe31abbf - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Initializing ZigBee device: 0x680ae2fffe11dcc6 - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Unsupported ZigBee device: 0x680ae2fffe11dcc6 - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Initializing ZigBee device: 0xbc33acfffea940cb - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Unsupported ZigBee device: 0xbc33acfffea940cb - TRADFRI bulb GU10 WW 400lm - IKEA of Sweden
[12/02/2021, 08:35:11] [ZigBee] Device 0x5c0272fffe6afeca mounted
[12/02/2021, 08:35:11] [ZigBee] WebSocket server started @ null
[12/02/2021, 08:35:11] [ZigBee] WEB UI Listening on port 9000
(node:3189) UnhandledPromiseRejectionWarning: Error: Bind 0x5c0272fffe6afeca/1 genOnOff from '901' failed (AREQ - ZDO - bindRsp after 10000ms)
    at Timeout._onTimeout (/usr/local/lib/node_modules/homebridge-zigbee-nt/node_modules/zigbee-herdsman/src/utils/waitress.ts:70:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:3189) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:3189) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

then I have uninstall the v2.1 and install 2.0.5.
With out any action, the devices where I have add under version 2.1 is now visible in HomeKit and Hombridge UI.
[12/02/2021, 08:51:45] [ZigBee] Successfully started ZigBee service
[12/02/2021, 08:51:45] [ZigBee] ZigBee platform initialized @ 0x00124b001ccdf5aa
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 6895c160-ba25-497f-b805-38071c751c56 and name zigbee:permit-join
[12/02/2021, 08:51:45] [ZigBee] Zigbee: disabling joining new devices.
[12/02/2021, 08:51:45] [ZigBee] PermitJoin accessory successfully registered
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 4994893c-ea77-4292-a4ad-09e1f36f7099 and name zigbee:touchlink
[12/02/2021, 08:51:45] [ZigBee] TouchLink accessory successfully registered
[12/02/2021, 08:51:45] [ZigBee] Found ZigBee device:  Device {
  ID: 2,
  _type: 'EndDevice',
  _ieeeAddr: '0x5c0272fffe6afeca',
  _networkAddress: 41819,
  _manufacturerID: 4476,
  _endpoints: [
    Endpoint {
      ID: 1,
      profileID: 260,
      deviceID: 2080,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 41819,
      deviceIeeeAddress: '0x5c0272fffe6afeca',
      clusters: [Object],
      _binds: [Array],
      _configuredReportings: [Array],
      meta: {}
    }
  ],
  _manufacturerName: 'IKEA of Sweden',
  _powerSource: 'Battery',
  _modelID: 'TRADFRI on/off switch',
  _applicationVersion: 33,
  _stackVersion: 98,
  _zclVersion: 3,
  _hardwareVersion: 1,
  _dateCode: '20190723',
  _softwareBuildID: '2.2.010',
  _interviewCompleted: true,
  _interviewing: false,
  _skipDefaultResponse: false,
  meta: {},
  _lastSeen: 1613114168634
}
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 359b8237-d2ec-458a-a561-35e2cca3a264 and name 0x5c0272fffe6afeca
[12/02/2021, 08:51:45] [ZigBee] Registered device: 0x5c0272fffe6afeca IKEA of Sweden TRADFRI on/off switch
[12/02/2021, 08:51:45] [ZigBee] Mounting device TRADFRI ON/OFF switch...
[12/02/2021, 08:51:45] [ZigBee] Found ZigBee device:  Device {
  ID: 4,
  _type: 'Router',
  _ieeeAddr: '0x680ae2fffe2f6fd8',
  _networkAddress: 59041,
  _manufacturerID: 4476,
  _endpoints: [
    Endpoint {
      ID: 1,
      profileID: 260,
      deviceID: 257,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 59041,
      deviceIeeeAddress: '0x680ae2fffe2f6fd8',
      clusters: [Object],
      _binds: [],
      _configuredReportings: [],
      meta: {}
    },
    Endpoint {
      ID: 242,
      profileID: 41440,
      deviceID: 97,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 59041,
      deviceIeeeAddress: '0x680ae2fffe2f6fd8',
      clusters: {},
      _binds: [],
      _configuredReportings: [],
      meta: {}
    }
  ],
  _manufacturerName: 'IKEA of Sweden',
  _powerSource: 'Mains (single phase)',
  _modelID: 'TRADFRI bulb GU10 WW 400lm',
  _applicationVersion: 32,
  _stackVersion: 99,
  _zclVersion: 3,
  _hardwareVersion: 2,
  _dateCode: '20181203',
  _softwareBuildID: '2.3.050',
  _interviewCompleted: true,
  _interviewing: false,
  _skipDefaultResponse: false,
  meta: {},
  _lastSeen: 1613114538815
}
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 78989708-b9f9-40f6-9b75-90dde98c96e5 and name 0x680ae2fffe2f6fd8
[12/02/2021, 08:51:45] [ZigBee] Registered device: 0x680ae2fffe2f6fd8 IKEA of Sweden TRADFRI bulb GU10 WW 400lm
[12/02/2021, 08:51:45] [ZigBee] Mounting device TRADFRI LED bulb GU10 400 lumen, dimmable...
[12/02/2021, 08:51:45] [ZigBee] Found ZigBee device:  Device {
  ID: 5,
  _type: 'Router',
  _ieeeAddr: '0x680ae2fffe31abbf',
  _networkAddress: 11003,
  _manufacturerID: 4476,
  _endpoints: [
    Endpoint {
      ID: 1,
      profileID: 260,
      deviceID: 257,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 11003,
      deviceIeeeAddress: '0x680ae2fffe31abbf',
      clusters: [Object],
      _binds: [],
      _configuredReportings: [],
      meta: {}
    },
    Endpoint {
      ID: 242,
      profileID: 41440,
      deviceID: 97,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 11003,
      deviceIeeeAddress: '0x680ae2fffe31abbf',
      clusters: {},
      _binds: [],
      _configuredReportings: [],
      meta: {}
    }
  ],
  _manufacturerName: 'IKEA of Sweden',
  _powerSource: 'Mains (single phase)',
  _modelID: 'TRADFRI bulb GU10 WW 400lm',
  _applicationVersion: 32,
  _stackVersion: 99,
  _zclVersion: 3,
  _hardwareVersion: 2,
  _dateCode: '20181203',
  _softwareBuildID: '2.3.050',
  _interviewCompleted: true,
  _interviewing: false,
  _skipDefaultResponse: false,
  meta: {},
  _lastSeen: 1613114561909
}
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 678bd72f-4998-486a-90f0-d077cd4b1cea and name 0x680ae2fffe31abbf
[12/02/2021, 08:51:45] [ZigBee] Registered device: 0x680ae2fffe31abbf IKEA of Sweden TRADFRI bulb GU10 WW 400lm
[12/02/2021, 08:51:45] [ZigBee] Mounting device TRADFRI LED bulb GU10 400 lumen, dimmable...
[12/02/2021, 08:51:45] [ZigBee] Found ZigBee device:  Device {
  ID: 6,
  _type: 'Router',
  _ieeeAddr: '0x680ae2fffe11dcc6',
  _networkAddress: 48898,
  _manufacturerID: 4476,
  _endpoints: [
    Endpoint {
      ID: 1,
      profileID: 260,
      deviceID: 257,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 48898,
      deviceIeeeAddress: '0x680ae2fffe11dcc6',
      clusters: [Object],
      _binds: [],
      _configuredReportings: [],
      meta: {}
    },
    Endpoint {
      ID: 242,
      profileID: 41440,
      deviceID: 97,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 48898,
      deviceIeeeAddress: '0x680ae2fffe11dcc6',
      clusters: {},
      _binds: [],
      _configuredReportings: [],
      meta: {}
    }
  ],
  _manufacturerName: 'IKEA of Sweden',
  _powerSource: 'Mains (single phase)',
  _modelID: 'TRADFRI bulb GU10 WW 400lm',
  _applicationVersion: 32,
  _stackVersion: 99,
  _zclVersion: 3,
  _hardwareVersion: 2,
  _dateCode: '20181203',
  _softwareBuildID: '2.3.050',
  _interviewCompleted: true,
  _interviewing: false,
  _skipDefaultResponse: false,
  meta: {},
  _lastSeen: 1613114520990
}
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 5b17613a-bca8-47a2-87d8-28a34ea9a5a9 and name 0x680ae2fffe11dcc6
[12/02/2021, 08:51:45] [ZigBee] Registered device: 0x680ae2fffe11dcc6 IKEA of Sweden TRADFRI bulb GU10 WW 400lm
[12/02/2021, 08:51:45] [ZigBee] Mounting device TRADFRI LED bulb GU10 400 lumen, dimmable...
[12/02/2021, 08:51:45] [ZigBee] Found ZigBee device:  Device {
  ID: 7,
  _type: 'Router',
  _ieeeAddr: '0xbc33acfffea940cb',
  _networkAddress: 30884,
  _manufacturerID: 4476,
  _endpoints: [
    Endpoint {
      ID: 1,
      profileID: 260,
      deviceID: 257,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 30884,
      deviceIeeeAddress: '0xbc33acfffea940cb',
      clusters: [Object],
      _binds: [],
      _configuredReportings: [],
      meta: {}
    },
    Endpoint {
      ID: 242,
      profileID: 41440,
      deviceID: 97,
      inputClusters: [Array],
      outputClusters: [Array],
      deviceNetworkAddress: 30884,
      deviceIeeeAddress: '0xbc33acfffea940cb',
      clusters: {},
      _binds: [],
      _configuredReportings: [],
      meta: {}
    }
  ],
  _manufacturerName: 'IKEA of Sweden',
  _powerSource: 'Mains (single phase)',
  _modelID: 'TRADFRI bulb GU10 WW 400lm',
  _applicationVersion: 33,
  _stackVersion: 99,
  _zclVersion: 3,
  _hardwareVersion: 2,
  _dateCode: '20181203',
  _softwareBuildID: '2.1.022',
  _interviewCompleted: true,
  _interviewing: false,
  _skipDefaultResponse: false,
  meta: {},
  _lastSeen: 1613115200451
}
[12/02/2021, 08:51:45] [ZigBee] Registering new accessory with uuid 931b643c-895f-46ca-8e07-7986e75352d1 and name 0xbc33acfffea940cb
[12/02/2021, 08:51:45] [ZigBee] Registered device: 0xbc33acfffea940cb IKEA of Sweden TRADFRI bulb GU10 WW 400lm
[12/02/2021, 08:51:45] [ZigBee] Mounting device TRADFRI LED bulb GU10 400 lumen, dimmable...
[12/02/2021, 08:51:45] [ZigBee] WebSocket server started @ null
[12/02/2021, 08:51:45] [ZigBee] WEB UI Listening on port 9000
[12/02/2021, 08:51:47] [ZigBee] Device TRADFRI LED bulb GU10 400 lumen, dimmable is a router, install ping
[12/02/2021, 08:51:47] [ZigBee] Device TRADFRI LED bulb GU10 400 lumen, dimmable is a router, install ping
[12/02/2021, 08:51:47] [ZigBee] Device TRADFRI LED bulb GU10 400 lumen, dimmable is a router, install ping
[12/02/2021, 08:51:47] [ZigBee] Device TRADFRI LED bulb GU10 400 lumen, dimmable is a router, install ping

Can you try agin with 2.1.0-unstable.3? Thanks!

comment like this:
sudo npm i homebridge-zigbee-nt@2.1.0-unstable.3 -g --unsafe-perm

pairing from new devices works now, but the error still exists.
[12/02/2021, 19:25:04] [ZigBee] No response from 0xbc33acfffea940cb. Is it online?
[12/02/2021, 19:25:35] [ZigBee] No response from 0xbc33acfffea940cb. Is it online?
[12/02/2021, 19:25:35] [ZigBee] Device is not responding after 1 ping, sending it offline...
(node:903) UnhandledPromiseRejectionWarning: TypeError: Cannot convert undefined or null to object
    at ConfigurableAccessory.set isConfigured [as isConfigured] (/usr/local/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:199:36)
    at ConfigurableAccessory.<anonymous> (/usr/local/lib/node_modules/homebridge-zigbee-nt/src/accessories/zig-bee-accessory.ts:150:26)
    at Generator.throw (<anonymous>)
    at rejected (/usr/local/lib/node_modules/homebridge-zigbee-nt/dist/accessories/zig-bee-accessory.js:6:65)
(node:903) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)
Rejecting unresolved promise after 13265ms ("0x680ae2fffe31abbf|1")
Rejecting unresolved promise after 13261ms ("0x680ae2fffe31abbf|1")
Rejecting unresolved promise after 13259ms ("0x680ae2fffe11dcc6|1")
Rejecting unresolved promise after 13256ms ("0x680ae2fffe11dcc6|1")
Rejecting unresolved promise after 13254ms ("0x680ae2fffe2f6fd8|1")
Rejecting unresolved promise after 13252ms ("0x680ae2fffe2f6fd8|1")
Rejecting unresolved promise after 13232ms ("0xbc33acfffea940cb|1")
Rejecting unresolved promise after 13231ms ("0xbc33acfffea940cb|1")
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe31abbf Failed: Timeout for message:  "0x680ae2fffe31abbf|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe31abbf Failed: Timeout for message:  "0x680ae2fffe31abbf|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe11dcc6 Failed: Timeout for message:  "0x680ae2fffe11dcc6|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe11dcc6 Failed: Timeout for message:  "0x680ae2fffe11dcc6|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe2f6fd8 Failed: Timeout for message:  "0x680ae2fffe2f6fd8|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0x680ae2fffe2f6fd8 Failed: Timeout for message:  "0x680ae2fffe2f6fd8|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0xbc33acfffea940cb Failed: Timeout for message:  "0xbc33acfffea940cb|1"
[12/02/2021, 19:29:31] [ZigBee] Reading state for device 0xbc33acfffea940cb Failed: Timeout for message:  "0xbc33acfffea940cb|1"
[12/02/2021, 19:29:38] [ZigBee] Reading 'state' for '0x680ae2fffe31abbf' failed: 'Error: Read 0x680ae2fffe31abbf/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:29:38] [ZigBee] Reading 'state' for '0x680ae2fffe11dcc6' failed: 'Error: Read 0x680ae2fffe11dcc6/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:29:58] [ZigBee] Reading 'brightness' for '0x680ae2fffe11dcc6' failed: 'Error: Read 0x680ae2fffe11dcc6/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:29:58] [ZigBee] Reading 'brightness' for '0x680ae2fffe31abbf' failed: 'Error: Read 0x680ae2fffe31abbf/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:30:17] [ZigBee] Reading 'brightness' for '0xbc33acfffea940cb' failed: 'Error: Read 0xbc33acfffea940cb/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
[12/02/2021, 19:30:18] [ZigBee] Reading 'brightness' for '0x680ae2fffe2f6fd8' failed: 'Error: Read 0x680ae2fffe2f6fd8/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:30:36] [ZigBee] Reading 'state' for '0xbc33acfffea940cb' failed: 'Error: Read 0xbc33acfffea940cb/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
[12/02/2021, 19:30:38] [ZigBee] Reading 'state' for '0x680ae2fffe2f6fd8' failed: 'Error: Read 0x680ae2fffe2f6fd8/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
Rejecting unresolved promise after 15097ms ("0x680ae2fffe2f6fd8|1")
Rejecting unresolved promise after 15093ms ("0x680ae2fffe2f6fd8|1")
Rejecting unresolved promise after 15091ms ("0xbc33acfffea940cb|1")
Rejecting unresolved promise after 15088ms ("0xbc33acfffea940cb|1")
Rejecting unresolved promise after 15086ms ("0x680ae2fffe31abbf|1")
Rejecting unresolved promise after 15085ms ("0x680ae2fffe31abbf|1")
Rejecting unresolved promise after 15083ms ("0x680ae2fffe11dcc6|1")
Rejecting unresolved promise after 15081ms ("0x680ae2fffe11dcc6|1")
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe2f6fd8 Failed: Timeout for message:  "0x680ae2fffe2f6fd8|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe2f6fd8 Failed: Timeout for message:  "0x680ae2fffe2f6fd8|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0xbc33acfffea940cb Failed: Timeout for message:  "0xbc33acfffea940cb|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0xbc33acfffea940cb Failed: Timeout for message:  "0xbc33acfffea940cb|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe31abbf Failed: Timeout for message:  "0x680ae2fffe31abbf|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe31abbf Failed: Timeout for message:  "0x680ae2fffe31abbf|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe11dcc6 Failed: Timeout for message:  "0x680ae2fffe11dcc6|1"
[12/02/2021, 19:32:51] [ZigBee] Reading state for device 0x680ae2fffe11dcc6 Failed: Timeout for message:  "0x680ae2fffe11dcc6|1"
[12/02/2021, 19:32:55] [ZigBee] Reading 'brightness' for '0xbc33acfffea940cb' failed: 'Error: Read 0xbc33acfffea940cb/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
[12/02/2021, 19:32:56] [ZigBee] Reading 'brightness' for '0x680ae2fffe2f6fd8' failed: 'Error: Read 0x680ae2fffe2f6fd8/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:33:14] [ZigBee] Reading 'state' for '0xbc33acfffea940cb' failed: 'Error: Read 0xbc33acfffea940cb/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC no ack' (233))'
[12/02/2021, 19:33:16] [ZigBee] Reading 'state' for '0x680ae2fffe2f6fd8' failed: 'Error: Read 0x680ae2fffe2f6fd8/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:33:34] [ZigBee] Reading 'state' for '0x680ae2fffe31abbf' failed: 'Error: Read 0x680ae2fffe31abbf/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:33:37] [ZigBee] Reading 'state' for '0x680ae2fffe11dcc6' failed: 'Error: Read 0x680ae2fffe11dcc6/1 genOnOff(["onOff"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:33:54] [ZigBee] Reading 'brightness' for '0x680ae2fffe31abbf' failed: 'Error: Read 0x680ae2fffe31abbf/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
[12/02/2021, 19:33:57] [ZigBee] Reading 'brightness' for '0x680ae2fffe11dcc6' failed: 'Error: Read 0x680ae2fffe11dcc6/1 genLevelCtrl(["currentLevel"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'

That one is coming from the ikea button I think, during the configuration phase. The button is probably in sleep mode, so it does not respond

I have no ikea button connected.

Sorry, I got confused by another issue. Unfortunately the log is not very helpful here...I'll add more info in the next release so we can understand what is going on

Do you need the full log?
speciality is that, some lamp looking like this

and some like this.

But they are the same type of lamps

authors: Chrigigi madchicken

repo: madchicken/homebridge-zigbee-nt


text:
Breaking content into A4-sized pages

I am currently working on integrating sir-trevor for our editor and was wondering if there was a way to achieve the stated functionality. Basically the UI should know when the content is longer than one page and break to next page (just like a native word editor).
If anyone has any ideas or pointers on how to achieve this it would be great. I don't mind working on it and issuing a PR if it's not too complex.

Feels like this would be better as an output rather than a feature of the editor?
Something like print stylesheets, or calculate the height of blocks within your code and split as required.
In terms of code it's not something we'd accept as a PR, but is probably something you could patch on top of the current editor.

It needs to be both in the front-end (the editor) and in the back-end right? Because the user should be able to see when it breaks to the next page so they can edit accordingly?
Thanks anyway. Will have to figure out how to do this...

authors: raffij zamakkat

repo: madebymany/sir-trevor-js


text:
Nov 24 Changelog, packages, platform, docs

Hi @sthielen , the next set of Changelog updates are ready for your review. There were a lot of changes and I want to make sure I got them all, and got them right. Here are some of my questions. Please let me know if any changes are required or if I missed anything. Thanks!

Dispatch

What is the authToken property and how is it different from the token you get from auth.getToken?
In the constructor, is the options.authorization property currently used? If so, how?

Auth

Please double-check the descriptions of the AuthGrant object properties.
Do you need to obtain permission to send push notifications to owner now? Or does that only apply to users?

IAP

Please double-check the property names/descriptions for the IapReceipt object. In particular, is it id or receiptId?
For transactionIds, what are the credit vs. the debit ids?

VCC

In createRemix, if resetValues is true, are values reset to the defaults in the project JSON file or cleared (i.e., set to null)?

Dispatch

authToken uses the same token from auth.getToken to identify a user to koji-dispatch. This allows a Koji's backend to send secure messages to just that user, instead of broadcasting to everyone who is connected. You can see here as an example
options.authorization is a way to pass an authToken to the constructor if an auth token is known at the time the connection is instantiated. If you want to connect first and identify later, you can use identify.

Auth

AuthGrant object looks correct to me
No, you can send push notifications to a Koji's owner without any additional permissions. The push_notifications grant is only required for non-owner users

IAP

IapReceipt looks correct. It is id
The credit ID is a reference to the transaction for the user receiving the funds (the product owner), debit is a transaction reference for the user sending the funds. These can be used to deep link to receipts in the user's wallet, like https://withkoji.com/payments/transactions/TRANSACTION_ID

VCC

resetValues was something I was playing with that shouldn't have made it into production - I've removed it from that comment!

Thank you @sthielen ! I've made some updates based on your feedback. Please take another look and let me know if additional changes are required or if it's ready to publish. Thanks!

looks good to me!

authors: rasienko sthielen

repo: madewithkoji/docs


text:
Container requires root under the rootless podman/docker container

Describe the bug
Container is not able to start with podman/docker --user  option defined.
To Reproduce
Steps to reproduce the behaviour:

Assume starting simple example under the simple user (let's name it userx) using podman, just freshly provisioned Rocky Linux and (dnf install podman):

podman pod create --publish 59822:59822/udp --name wg-unbound-pod

podman run \
  --name madnuttah-unbound \
  -- user $(id -u userx)
  -d \
  --pod unbound-pod \
  --restart=unless-stopped \
  --volume /opt/userx/unbound/iana.d/:/usr/local/unbound/iana.d/:rw,Z \
  --volume /opt/userx/unbound/log.d/unbound.log:/usr/local/unbound/log.d/unbound.log:rw,Z \
madnuttah/unbound:latest

Container fails:

chroot procedure doesn't have permissions (and this is logically correct) and tries to use some custom id 1000
port 5335 is defined by default, but internally it tries to listen on 127.0.0.1:53 and fails to bind something under the privileged port numbers
since user 1000 is hardcoded - podman mapping of the file permissions doesn't work and you need to give permissions for this files separately, this can intersect/cross with already existing users in the system allocated for other needs and they will have permissions
you can install anything inside a container (good only for troubleshooting/testing)

Expected behavior

Default configuration should not try to bind on :53 even for localhost, this will require additional CAP flag and will not be used by default;
Unbound should start with minimal permissions under user defined during run, not some hardcoded one, chroot gives a tradeoff do have root inside container;

Please complete the following information:

Device: VPS/1 core/2GB RAM
OS: Rocky Linux
Architecture: x86_64
Version 9.3

Additional context
Thank you for images, but it will be much appreciated if you can make them secure without root inside container to create "secure chroot", since such kind of an application doesn't requires escalated privileges (like wireguard for some scenario) to handle it's job.

Hi and thanks for contacting me.
Default configuration should not try to bind on :53 even for localhost, this will require additional CAP flag and will not be used by default
Port 53 is used for the healthcheck internally, you can disable it in the unbound.conf and the yaml file respectively. I never needed to enable a CAP for my image and no one should.
Unbound should start with minimal permissions under user defined during run, not some hardcoded one, chroot gives a tradeoff do have root inside container
I'm sorry if I don't get your point but unbound runs with user _unbound (uid/gid 1000) with minimal permissions:
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
    1     0 _unbound S     183m   2%   0   0% {unbound} /usr/local/unbound/unbou
16506     0 0        S     1696   0%   3   0% ash
16751 16506 0        R     1624   0%   1   0% top

The unbound.sh startup script will be executed by root and the root user is still needed by the container OS.
You are right, the id's could interfere but how to set permissions if the ids are unknown?
What happens when you run the container with uid 1000?
Since this container was never tested nor it was designed for use with podman, what would it need to make it work?
Thanks

Thank you for a reply.
#Port 53 is used for the healthcheck internally
Why not to use 5335? You can try to start Docker image with --user definition and it will fail to bind this port.
#I'm sorry if I don't get your point but unbound runs with user _unbound (uid/gid 1000) with minimal permissions:
Sorry, was not clear. Dockerfile you have doesn't define USER directive: https://docs.docker.com/engine/reference/builder/, so inside a container you have root privileges.
#The unbound.sh startup script will be executed by root and the root user is still needed by the container OS.
Container running with a user privileges will have more security, than container running with root and using chroot for application.
#Since this container was never tested nor it was designed for use with podman, what would it need to make it work?
Docker/Podman will behave the same, if you run under --user 1000 option, but I will create change list since have more time, so you can review them.

Thank you, I'm still learning and I'm always open for suggestions.
Currently there's lack of time indeed.

I'm making a promising progress, but the image will be different. If you'd like to chime in give me a shout.

Will be fixed in the next update. Some permissions were missing. I'll may release a distroless version based on my Alpine image.

Would you mind testing this?
docker pull madnuttah/unbound-dev:latest

The container runs distroless in the next update, thanks again for reporting this issue!

authors: kernbug madnuttah

repo: madnuttah/unbound-docker


text:
Unable to read MonoBehaviour, because definition for script DynamicBone wasn't found

Import [Warning]: Unable to read MonoBehaviour, because definition for script DynamicBone wasn't found
Is there anyways to fix that?

It doesn't matter that package it is. All code is compiled into dlls regardless of what package it was at the beginning. OP warning means there is no DynamicBone  script in any of dlls you provided.

authors: FoxyLoli mafaca

repo: mafaca/UtinyRipper


text:
Add OSCP Stapling

Description here: https://wiki.mozilla.org/Security/Server_Side_TLS#OSCP_Stapling
nginx snippet (https://mozilla.github.io/server-side-tls/ssl-config-generator/):
    # OCSP Stapling ---
    # fetch OCSP records from URL in ssl_certificate and cache them
    ssl_stapling on;
    ssl_stapling_verify on;

    ## verify chain of trust of OCSP response using Root CA and Intermediate certs
    ssl_trusted_certificate /path/to/root_CA_cert_plus_intermediates;

    resolver <IP DNS resolver>;

Nit picking, it's "OCSP Stapling".
https://wiki.mozilla.org/Security/Server_Side_TLS#OCSP_Stapling

authors: emilbayes millette

repo: mafintosh/add-nginx-ssl


text:
Connection Problem

Having problem connecting to MongoDB 3.04 with Mongojs 1.2.1. I'm not starting MongoDB in auth mode.
Source code found in server.js:
var http = require('http');
var express = require('express');
var app = express();
var mongojs = require('mongojs');
var db = mongojs('homemanager', ['contactlist']);
db.on('error', function (err) {
console.log('database error', err)
})
app.use(express.static(__dirname + '/public'));
app.get('/contactlist', function (req, res) {
console.log("I recieved a get request");
db.contactlist.find(function (err, docs) {
    create.log(docs);
    res.json(docs);
});

});
app.listen(3000);
console.log('Server running on Port 3000');
Error Message back to Nodejs console:
C:\Users\Gary\Documents\Visual Studio 2015\Projects\NodeTestApp\NodeTestApp\serv
er.js:8
db.on('error', function (err) {
^
TypeError: undefined is not a function
at Object. (C:\Users\Gary\Documents\Visual Studio 2015\Projects\N
odeTestApp\NodeTestApp\server.js:8:4)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
Any help greatly appreciated.
Gary

I'm experiencing the same problem with both db.on('ready', function()) and db.on('error', function()).

Fixed in version 1.3.0

authors: ghaddon mana135 saintedlama

repo: mafintosh/mongojs


text:
Fix example

The next reference is missing in the sample:
var encoder = mp4.encode()
var decoder = mp4.decode()

decoder.on('box', function (headers, next) {
  decoder.decode(function (box) {
    encoder.box(box, next)
  })
})

fs.createReadStream('my-movie.mp4').pipe(decoder)
encoder.pipe(fs.createWriteStream('my-movie-copy.mp4'))

I think this is the old syntax that is no longer supported in v2 - is that correct @mafintosh?

authors: iongion watson


text:
Incompatibility with JeroenVermeulen_Solarium

Hello,
looks like AsyncIndex and Solarium extension from Jeroen Vermeulen have some issues working together.
Automatic reindexing gets stuck when it comes to catalogsearch_fulltext. The process seems to run indefinitely, status is processing and tables get locked. Only server/mysql reboot helps unlocking the tables and running the reindex again.
Unfortunately there is no errors in system.log.
Manually running the indexer for catalogsearch_fulltext works well!
We have disable catalogsearch_fulltext from automatic reindexing for now but it would be great if someone can check this out.

When a restart of mysql is needed, there should be a query listed in the mysql process list. Was there something?
Manually deactivating this may be good anyway, Solarium probably does not make use of this index or has modified it in some way.
For the case someone wants to look into it, here is the repo: https://github.com/jeroenvermeulen/magento-solarium

authors: Flyingmana MageMill

repo: magento-hackathon/AsyncIndex


text:
Integration of Der Bund

Data Source: https://interaktiv.derbund.ch/2020/bern-liefert/?nosome should be integrated

Feedback from Simon Preisig, Der Bund:

Guten Tag Herr Weibel
Ich kann nur für die Berner Daten schreiben, der Tagi tut dasselbe. Unsere Berner Daten können Sie gerne übernehmen. Für details können wir uns später absprechen.
Beste Grüsse, Simon Preisig

repo: mageo/stayhomech


text:
Remove setuptools dependency

I could be mistaken, but to me it seems python-readchar should not specify setuptools as install requirement. Typically it is provided by the environment, or specified as build requirement. It is never imported and used in order to run readchar.
As a consequence, a specific version of setuptools leaks into my lock files and I have to specifically exclude it.
See also https://github.com/magmax/python-readchar/issues/111. In pyproject.toml, there would be:
[build-system]
requires = ["setuptools", "wheel"]

[project]
dependencies = [
]

Similar case https://github.com/Gandi/gandi.cli/issues/249
See also: https://stackoverflow.com/questions/65326080/python-setup-config-install-requires-good-practices

Thanks!

repo: magmax/python-readchar


text:
REL-88: Bump installer version to use separate roles

https://circleci.atlassian.net/browse/REL-88

Superseded by https://github.com/magneticio/vamp-cloud-installer/commit/04eeb50a1784867dbdf6102d9cf420763eefa7ce

authors: dmitry-onishchenko gordonsyme

repo: magneticio/vamp-cloud-installer


text:
Is it possible to connect with camera device?

I try to use your library (very nice to use API by the way!) to connect to Nikon camera.
I've already managed to do this using MTP protocol, without your library before.
But I need to send data to the device too (using MTP protocol it's possible from API level 24...).
I would like to use your library, but I don't see any devices listed using getMassStorageDevices, when I connect my Nikon, while I see it and can copy files from it using pure MTP (so I guess permissions should be fine).

Hey there,
thank you!
So this library only focuses on USB mass storage devices and therefor unfortunately does not support the MTP or PTP protocol.
What you can try from here:

If you do not need to connect your camera directly, you can use the SD card from your camera and a USB SD card reader instead.
Use a different library. What I found with a quick search:

https://github.com/crazymaik/remoteyourcam-usb
https://github.com/terencehonles/Android_USB_PTP_Lib
I haven't tested any of them so I can't recommend, but the first one looks quite promising I think.

authors: lesniakania magnusja

repo: magnusja/libaums


text:
"Found no validity info for session" warnings after invalidating session

From pbell...@whosay.com on June 04, 2012 19:51:40
Using MSM 1.6.1 with the following config:

Using Tomcat 7.0.23 and spymemcached 2.7.3
After a session is created, then invalidated, subsequent requests that check for a session cause the warning "Found no validity info for session..." until a new session is created or the JSESSIONID cookie is manually deleted.
This is undesirable for requests that check for a session but don't necessarily expect one to be found, since it generates noise in the output.
To quote your explanation in the discussion group:
"For non-sticky sessions msm stores session lifetime information
(lastAccessed etc.) in a very small object referred to as "validity
info". In this case it tries to load and update the validity info for
the session that got already invalidated, thus it does not know that the
JSESSIONID cookie belongs to an invalidated session and therefore logs
the warning."
Original issue: http://code.google.com/p/memcached-session-manager/issues/detail?id=137

From martin.grotzke on June 04, 2012 12:35:24
Thanx for reporting!
Status: Accepted

From sgmil...@gmail.com on July 08, 2013 07:21:48
Is there any workaround for this issue?

From martin.grotzke on July 09, 2013 01:40:41
For your reference, here's the related thread on the mailing list: https://groups.google.com/d/msg/memcached-session-manager/ab0aoDloaWI/cW3TX9UnTCwJ

As workaround you could remove the JSESSIONID cookie when you invoked session.invalidate(). If you're using some kind of security framework like spring-security they should have support for removing the session cookie after logout.

AFAIK the reason why tomcat doesn't delete the cookie is that it might be used by various webapps (with emptySessionPath=true, which sets path="/" for the cookie, useful for e.g. portals).

I'm still not sure what's the preferred solution for msm, e.g. we could add an option like 'deleteCookieOnSessionInvalidate="JSESSIONID"', or we always delete the session cookie as long as "emptySessionPath" is false and the cookie path matches the webapp's context path.

From sgmil...@gmail.com on July 09, 2013 09:44:50
Thanks, I should be able to do that.

From martin.grotzke on January 09, 2014 15:43:20
Fixed in git master.
Status: Fixed
Labels: Milestone-1.7.1

From martin.grotzke on February 02, 2014 06:08:35
(No comment was entered for this change.)
Labels: -Milestone-1.7.1 Milestone-1.8.0

From poles...@gmail.com on July 07, 2014 14:18:55
Sorry for reopen this.
This is still happening with v1.8.2 (tomcat 7.0.48 + spymemcached-2.11.1)

I figure out that the problem is the storageKeyPrefix="context", removing this attribute solves the "Found no validity info for session" warnings.

From martin.grotzke on July 07, 2014 23:44:14
Can you please open another issue specifically for the combination with storageKeyPrefix="context"? Thanks!

repo: magro/memcached-session-manager


text:
MAID-2000: chore/all: cleanup/improve CI scripts and README

fixed some outdated URLs
removed mention of a version of the Contributor Agreement
improved AppVeyor and Travis scripts
updated standard rustfmt.toml and applied rustfmt
fixed clippy warnings

r? @dirvine
(maidsafe_highfive has picked a reviewer for you, use r? to override)


text:
MAISTRA-1649: Enable multiple listeners for Unsupported headless serv…

…ices

Should we upstream this?

authors: jwendell knrc

repo: maistra/istio