tzengshinfu
tzengshinfu
Hello, verhovsky: I encountered **node-gyp execution errors** when installing tree-sitter-java (`npm i tree-sitter-java`), so I turned to the solution based on [WebAssembly](https://github.com/tree-sitter/tree-sitter/blob/master/lib/binding_web/README.md). The steps are as follows: 1. Install Web...
谢谢回复，今天再改用v4.3.7还是一样无法正常启动， 后来我把两个版本的映像档撷取出application.properties作比对， 发现v4.3.7增加了`oms.storage.dfs.mysql_series.*`的属性，  所以在compose档的环境变量也增加就能正常启动了。 ``` powerjob: container_name: powerjob image: powerjob/powerjob-server:latest ............................................................................... environment: PARAMS: "--oms.mongodb.enable=false --spring.datasource.core.jdbc-url=jdbc:mysql://powerjob-mysql:3306/powerjob-daily?useUnicode=true&characterEncoding=UTF-8&serverTimezone=Asia/Taipei --oms.storage.dfs.mysql_series.url=jdbc:mysql://powerjob-mysql:3306/powerjob-daily?useUnicode=true&characterEncoding=UTF-8&serverTimezone=Asia/Taipei" ............................................................................... ```
Hi, 我观察到在v4.3.7版新增的oms.storage.dfs.mysql_series.url属性的默认值是 _jdbc:mysql://**localhost**:3306/powerjob-daily?useUnicode=true&characterEncoding=UTF-8&serverTimezone=Asia/Shanghai_ 而docker网络设定默认是容器相互隔离所以才会连不到mysql容器。 (如果一开始**localhost**就是**powerjob-mysql**，我就不会查觉这个状况了。) 不过还是建议在文档里写明需在环境变量去增加这个属性覆盖掉默认值。 (因为使用者的容器名称或时区可能也会修改。)
Thanks for sharing. The results of my testing indicate that after signing out and attempting to log in with a different account, the error shown in the following image appears....
I found that if I sign out the session of GreenLight V3 in the KeyCloak Administration Console, I also need to manually sign out in GreenLight; otherwise, it stays logged...
> You can disable cookie login for keycloak: > > 1. Login Keycloak greenlight realm as admin > 2. Open your greenlight realm's authentication page (/keycloak/admin/master/console/#/greenlight/authentication/) > 3. Select "Browser...
您好，谢谢回覆， 尝试将“请求报时”和“查询超时”都改为9999秒， 并重启DataEase容器，   但还是发生超时异常，而且09：09：03->09：09：51不到1分钟。 `2024-08-15 09:09:03.619 INFO --- [nio-8100-exec-5] i.d.dataset.manage.DatasetSQLManage : calcite origin sql: ...... 2024-08-15 09:09:03.620 INFO --- [nio-8100-exec-5] i.d.dataset.manage.DatasetDataManage : calcite data count sql: ...... 2024-08-15...
今天再测试， 一开始不会出现”SQL ERROR: Statement cancelled due to timeout or client request“的错误讯息， 但等了1小时画面还是停置在保存数据中的确认对话框  Chrome开发者工具可看到pending的request  再查MySQL正在执行的SQL指令（show full processlist），发现有一笔计算纪录笔数指令刚好也是执行了1小时 `SELECT COUNT(*) FROM ( SELECT `t_a_0`.`f_d02b91fd118c8474` AS `f_ax_0`, `t_a_0`.`f_43b5b3c12d896a93` AS `f_ax_1`, `t_a_0`.`f_fb29cae42a44a80f`...
Hello! I'm doing well, thank you. I'm currently using v1.19 and running it in a container.