Closed yangm97 closed 6 years ago
lua: ./lua/main.lua:144: bad argument #2 to 'format' (string expected, got table)
stack traceback:
[C]: in function 'format'
./lua/main.lua:144: in function <./lua/main.lua:61>
(tail call): ?
polling.lua:47: in main chunk
[C]: ?
Fixed by #323
Maybe not. The issue with ###cb:dashboard:settings
persists.
can you provide error log? i just pull from this repo, master branch and and launch (w/o docker) but not facing issue on ###cb:dashboard:settings
Ooops, I might have forgotten to update the running bots 😅
TODO: Add CI/CD
An #error occurred.
./lua/utilities.lua:608: bad argument #1 to 'format' (string expected, got nil)
stack traceback:
[C]: in function 'format'
./lua/utilities.lua:608: in function 'getSettings'
./lua/plugins/dashboard.lua:109: in function <./lua/plugins/dashboard.lua:89>
(tail call): ?
[C]: in function 'xpcall'
./lua/main.lua:112: in function <./lua/main.lua:61>
(tail call): ?
polling.lua:47: in main chunk
[C]: ?
it_IT
###cb:dashboard:settings:
Nah, seems like I did not forget to update it after all.
it seem you forget to update after all, i just test it using italian but i didnt face this issue
It is happening on official GB and I can assure it is up to date.
An #error occurred.
./lua/utilities.lua:594: bad argument #1 to 'format' (string expected, got nil)
stack traceback:
[C]: in function 'format'
./lua/utilities.lua:594: in function 'getSettings'
./lua/plugins/dashboard.lua:109: in function <./lua/plugins/dashboard.lua:89>
(tail call): ?
[C]: in function 'xpcall'
./lua/main.lua:112: in function <./lua/main.lua:61>
(tail call): ?
polling.lua:47: in main chunk
[C]: ?
it_IT
###cb:dashboard:settings:
(Notice how lines changed because I removed some leftover code from moderators and admins, after your PR got merged)
Seems like /ban id is broken too
./lua/plugins/banhammer.lua:99: bad argument #2 to 'format' (string expected, got nil)
stack traceback:
[C]: in function 'format'
./lua/plugins/banhammer.lua:99: in function <./lua/plugins/banhammer.lua:46>
(tail call): ?
[C]: in function 'xpcall'
./lua/main.lua:112: in function <./lua/main.lua:61>
(tail call): ?
polling.lua:47: in main chunk
[C]: ?
en
/ban [numeric id]
use /ban [user id] right? i dont this error when use command /ban (userid)
Maybe users are trying /ban with invalid numeric ids?
Or rather, ids from members that are not in the chat.
i dont get any error when tried to ban member that were not in the chat
@riskey95 So I don't have any idea what it could be then. We're planning to store problematic updates somewhere in the future to help debugging this kind of issues though.
@NotAFile added an assert on getnames_complete()
and today I just saw this:
An #error occurred.
./lua/utilities.lua:787: kicked is false/nil
stack traceback:
[C]: in function 'assert'
./lua/utilities.lua:787: in function 'getnames_complete'
./lua/plugins/banhammer.lua:58: in function <./lua/plugins/banhammer.lua:46>
(tail call): ?
[C]: in function 'xpcall'
./lua/main.lua:122: in function 'on_msg_receive'
./lua/main.lua:335: in function 'parseMessageFunction'
polling.lua:47: in main chunk
[C]: ?
en
/ban [numeric id]
So there are cases where this function is returning nil/false.
Is anyone against adding a default value, like “unknown” for this function?
@yangm97 sounds great
Alright, should be fixed by fc12590 now.