MaikoTan
commented
1 year ago Why does nai -r 512x512 girl not work?
if (this.ctx.database) {
if (session.subtype === 'group') {
// attach group data
const channelFields = new Set<Channel.Field>(['flag', 'assignee', 'guildId', 'locale'])
this.ctx.emit('before-attach-channel', session, channelFields)When Koishi received a command and there is a database usable, Koishi would emit a before-channel-attached and before-user-attached BEFORE calling the observeChannel and observeUser function that would write properties into session.user the Proxy object.
ctx.before('attach-channel', (session, fields) => {
session.collect('channel', session.argv, fields)
})In middleware.ts, an event listener was registered with the before-channel-attached event, it would call the session.collect function.
if (!this.resolveCommand(argv)) return const { options, args, error } = argv.command.parse(argv)In the session.collect function, Koishi would try to resolve a command's details with session.resolveCommand function, which calling the argv.command.parse function.
// apply domain callback
const transform = resolveType(type)
if (transform) {
try {
return transform(source, argv.session)
} catch (err) {So then in the parse function, following the calling chain parse -> parseValue -> transform, the transform function is exactly the faulted resolution function in this case.
As I mentioned at the first, the argv.session here has only a null user property. Considering the code history, this code should not work at first.
But why does 约稿 -r 512x512 girl work?
Just as the workflow mentioned above, the shortcut command also following it, getting into session.resolveCommand function.
But differently, the first line if (this.inferCommand(argv) was failing here (because the content was not be parsed), which making it an early return.
resolveCommand(argv) {
if (!this.inferCommand(argv)) returnSo then the calling chain return-ed with nothing, nothing, nothing...until going back to the _process function mentioned at the top.
Originally this message would be ignored cause it is not getting into the command invoke, but thanks to the session.response function assigned above in the _executeMatcher function, which makes it getting into the session once again.
session.response = async () => {
const output = await session.resolve(response, params)
return segment.normalize(output, params.map(source => source ? segment.parse(source) : ''))
} if (session.response) return session.response()
return next()Note here, the session here was already assigned with the session.user property with the observerUser function. So when the session.response was called that cycling the command again, following the steps above makes the resolution function functioning accidently.
Describe the bug
在qq或沙盒里发送
nai -r 512x512 cat，bot回复选项 resolution 输入无效，Cannot read properties of null (reading 'authority')。 不加-r参数bot回复正常。发送nai -r landscape catbot回复正常。Steps to reproduce
在qq或沙盒里发送
nai -r 512x512 catExpected behavior
bot发送一张512x512大小的图
Screenshots
Relevant log output
Launcher
Koishi CLI (koishi start)
Backend
Stable Diffusion WebUI (AUTOMATIC1111)
Versions
Additional context
已开启sqlite数据库插件