-
Notifications
You must be signed in to change notification settings - Fork 10
[命令行工具] 除用户添加外所有功能均无法使用 #13
Comments
学校是湖北工业职业技术学院 |
是一个插件升级带来的报错 @djkcyl |
哪有什么办法解决吗,给插件降级? |
我更新一下,发布一个新的版本,除 CLI 外其它的功能应该是完好的 |
好的 |
好了 (~ ̄▽ ̄)~ @djkcyl 请安装这个版本 |
我去试试 |
用户删除可以用了,学校设置-s和sign依然不能使用 学校设置: 签到 |
所以说用数字id就没问题了吗 |
哦好的,谢谢啦 |
@djkcyl 而且登录表单不一样,有时间我会兼容 |
你看看我 README 那个最后感谢里 wisedu-unified-login-api 项目兼不兼容,它的适配性很好 |
我去试试 |
试试这个 url,应该是可以的,我看了代码 |
@djkcyl 各个学校不一样,导致这种爬虫类的开发是很杂的,适配性很低是正常的,不要气馁,多尝试 😂 |
@djkcyl @beetcb/cea@2.1.5 支持了这种登录模式,先关掉这个 Issue (缺少回复) |
可能本地配置比较乱,建议执行一次 |
删除用户:
(node:17564) UnhandledPromiseRejectionWarning: ReferenceError: get is not defined at i.deleteUser (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:14:1985) at C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:21:234 at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:17564) 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: 2) (node:17564) [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.
配置学校:
(node:16216) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of null at c.schoolApi (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:14:3281) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async c.init (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:14:2330) at async C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:21:277 (node:16216) 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:16216) [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.
签到:
(node:10616) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'login' of undefined at module.exports (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:8:456) at t (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:12:210) at C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:12:616 at Array.map (<anonymous>) at r.e.handleCookie (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:12:561) at C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:18:220 at Object.parcelRequire.PTk1.../src/index (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:18:266) at f (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:3:468) at p (C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:3:544) at C:\Users\cyl\AppData\Roaming\npm\node_modules\@beetcb\cea\dist\cli.js:21:376 (node:10616) 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: 2) (node:10616) [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.
The text was updated successfully, but these errors were encountered: