You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
这是 image-bin 的日志,可以发现其中有多个地方出现 image-bin v0.11.7 ready on 8107,这是 image-bin 启动时会输出的日志(只是和 AI Studio 的错误日志时间不匹配,但是好像 AI Studio 的错误时间段内并没有 image-bin 的日志?)
2024-06-04T17:50:51: updating image bin env
2024-06-04T17:50:51: Mapping can use resources count: 0 []
2024-06-04T17:50:51: clean up expired uploads by cron
2024-06-04T17:50:52: companion: 2024-06-04T17:50:52.199Z [info] jobs.cleanup.start starting clean up job
2024-06-04T17:50:52: > image-bin v0.11.7 ready on 8107
2024-06-04T17:50:52: Fetch blocklet.js succeed: zNKoMsf9c3gJv9pAyHiiVmEieHvK5SeWYCjo/z8ia1mAXo8ZE7ytGF36L5uBf9kD2kenhqFGp9
2024-06-04T18:00:00: clean up expired uploads by cron
2024-06-04T18:11:22: Received event from component channel: user.updated. time: 1717524682785
2024-06-04T18:11:23: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T19:00:00: clean up expired uploads by cron
2024-06-04T19:39:06: Received event from component channel: user.added. time: 1717529946542
2024-06-04T19:39:08: Received event from component channel: user.updated. time: 1717529948943
2024-06-04T19:41:59: Received event from component channel: user.updated. time: 1717530119252
2024-06-04T19:42:05: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T19:43:14: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T19:58:25: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T20:00:00: clean up expired uploads by cron
2024-06-04T20:12:46: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T20:58:50: updating image bin env
2024-06-04T20:58:51: Mapping can use resources count: 0 []
2024-06-04T20:58:51: clean up expired uploads by cron
2024-06-04T20:58:51: companion: 2024-06-04T20:58:51.261Z [info] jobs.cleanup.start starting clean up job
2024-06-04T20:58:51: > image-bin v0.11.7 ready on 8107
2024-06-04T20:58:51: Fetch blocklet.js succeed: zNKoMsf9c3gJv9pAyHiiVmEieHvK5SeWYCjo/z8ia1mAXo8ZE7ytGF36L5uBf9kD2kenhqFGp9
2024-06-04T21:00:00: clean up expired uploads by cron
2024-06-04T21:46:50: updating image bin env
2024-06-04T21:46:51: Mapping can use resources count: 0 []
2024-06-04T21:46:51: clean up expired uploads by cron
2024-06-04T21:46:51: companion: 2024-06-04T21:46:51.236Z [info] jobs.cleanup.start starting clean up job
2024-06-04T21:46:51: > image-bin v0.11.7 ready on 8107
2024-06-04T21:46:51: Fetch blocklet.js succeed: zNKoMsf9c3gJv9pAyHiiVmEieHvK5SeWYCjo/z8ia1mAXo8ZE7ytGF36L5uBf9kD2kenhqFGp9
2024-06-04T22:00:00: clean up expired uploads by cron
2024-06-04T22:01:20: Received event from component channel: user.added. time: 1717538480536
2024-06-04T22:01:28: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T22:33:47: call http://127.0.0.1:8126/api/v1/sdk/status api success
2024-06-04T22:41:51: updating image bin env
2024-06-04T22:41:51: Mapping can use resources count: 0 []
2024-06-04T22:41:51: clean up expired uploads by cron
2024-06-04T22:41:52: companion: 2024-06-04T22:41:52.058Z [info] jobs.cleanup.start starting clean up job
2024-06-04T22:41:52: > image-bin v0.11.7 ready on 8107
2024-06-04T22:41:52: Fetch blocklet.js succeed: zNKoMsf9c3gJv9pAyHiiVmEieHvK5SeWYCjo/z8ia1mAXo8ZE7ytGF36L5uBf9kD2kenhqFGp9
2024-06-04T22:53:51: updating image bin env
2024-06-04T22:53:51: Mapping can use resources count: 0 []
2024-06-04T22:53:51: clean up expired uploads by cron
2024-06-04T22:53:51: companion: 2024-06-04T22:53:51.407Z [info] jobs.cleanup.start starting clean up job
2024-06-04T22:53:51: > image-bin v0.11.7 ready on 8107
复现这个 bug
截图或报错信息(可选)
异常的行为
期望的行为
可能的解决方案(可选)
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
详细描述
这是 AI Studio 的 error.log,可以发现和用户看到的错误一致。
这是 image-bin 的日志,可以发现其中有多个地方出现
image-bin v0.11.7 ready on 8107
,这是 image-bin 启动时会输出的日志(只是和 AI Studio 的错误日志时间不匹配,但是好像 AI Studio 的错误时间段内并没有 image-bin 的日志?)复现这个 bug
截图或报错信息(可选)
异常的行为
期望的行为
可能的解决方案(可选)
The text was updated successfully, but these errors were encountered: