Releases: TarsCloud/TarsFramework
Releases · TarsCloud/TarsFramework
v3.0.17 20240202
en
- update tarscpp to v3.0.19
- fix: tarsnode ServerManager.cpp reportNode
- feat tarsnode add nodename to template
- feat: cmake add open ENABLE_ADDRESSSANITIZER
- feat: tarsregsitry EndpointF set nodeName
- optimize: doReserveDb drop table
v3.0.16 20231106
en
- fix: tarsnode start same process two times when process start is slow
- fix: tarsregistry, when mysql is down not crash
- fix: tarsnode, when tarsregistry all down, tarsnode still can start local servers
- fix: deploy dockerfile to support nodejs update
- fix: tar-server.sh do not update npm
- tarsnode auto set locator when tarsregistry locator changed
- set default value of activating-timeout: 60s
- delete some interface in tarsnotify that not used
cn
- 修复: tarsnode 会启动两个相同的进程, 当业务进程启动太慢的时候(尤其是java容易出现)
- 修复: 当mysql无法连接时,启动tarsregistry不再crash
- 修复: 当tarsregistry都死掉, tarsnode启动后, 能正常拉起所有本地的服务, 不再依赖tarsregistry
- 修复: 部署Dockerfile中, 不再主动升级npm, 避免兼容性问题
- 修复: tar-server.sh 也不在主动升级npm
- tarsnode自动设置locator, 当发现tarsregistry做了迁移locator变更后
- 修改缺省模板, 设置缺省的activating-timeout值为60s, 保证服务器启动60s不会被tarsnode杀掉
- 删除了tarsnotify中不再使用的接口和功能代码
# v3.0.15 20231007
v3.0.15 20231007
en
- fix tars-start.sh & tars-stop.sh when is slave
- fix tarsconfig, out of limit return 429
- fix tarsquerystat/tarsqueryproperty, Resolve the bug where the log cutting parameters are not working prop
- fix tarsnotify command field is empty
cn
- 修复: 备机是tars-start.sh & tars-stop.sh的问题
- 修复: tarsconfig超过频率限制时返回429
- 修复: tarsquerystat/tarsqueryproperty解析日志参数的bug
- 修复: tarsnotify写入数据库时, command字段为空的问题(影响告警)
# v3.0.14 20230415
v3.0.14 20230415
en
- feat: tarsnode linux & mac add close_all_file_descriptors
- fix: tarsnode start java server bug, add tars_start.sh.pid record tars service pid
- fix: AdminReg stopServer
- fix: the bug that ports might be used when the service was restarted
cn
- feat: tarsnode启动服务时增加关闭句柄
- fix: tarsnode 启动服务时, 记录服务的pid
- fix: AdminReg 修复stopServer的bug
- fix: 服务重启时端口可能被重用的bug
# v3.0.13 20230307
v3.0.13 20230307
en
- feat: tarsadmin support multi service
- feat: install framework default node version use v16.13.0
- Fix: the issue that tarsregistry sometimes failed to join the service's locator configuration list
cn
- feat: tarsadmin支持多副本
- feat: 安装框架时, 默认的node版本使用v16.13.0
- 修复: tarsregistry有时候没法加入到服务的模板配置中的bug
# v3.0.12 20220906
v3.0.12 20220906
en
- fix: deploy/docker.sh use tonistiigi/binfmt:latest
- fix: tarsnode start server in docker mode when tarsnode is docker
- fix: tarsnode docker pull bug when image not exists
- fix: tarsnode longconnection active status bug in tarsweb
- fix: the script process does not exit after starting tarsnode under Linux
cn
- fix: deploy/docker.sh使用tonistiigi/binfmt:latest
- fix: tarsnode是容器模式下且以容器化方式启动业务服务的bug
- fix: tarsnode以容器化启动业务服务, 拉取基础镜像的bug
- fix: tarsnode长连接模式下tarsweb显示的bug
- fix: linux下启动tarsnode后脚本进程不退出问题修复
# v3.0.11 20220823
v3.0.11 20220823
en
- fix tars_node_init.sql not init tarsAdminRegistry
cn
- fix: tars_node_init.sql 中不要初始化tarsAdminRegistry
v3.0.10 20220816
v3.0.10 20220816
en
- fix: es compatibility of tarslog
- add: tarsnode log when call system()
cn
- fix: tarslog兼容es的问题
- add: tarsnode调用system时增加日志
v2.4.17
v2.4.17 2021.12.04
en
- update dockerfile node upgrade to 16.13.0
- fix tarsnode use old config for tars framework server
cn
- 升级 dockerfile, 框架的 dockerfile 升级到 16.13.0
- 修复 tarsnode, 对于 tars 框架服务, 使用老的配置, 从而保证 local 端口不变
v3.0.3
v3.0.3 20211130
en
- remove tarsnode useless log
- fix tarsnode use old config for tars framework server
- fix tarsnode, keep tars server local port not change
- update dockerfile node upgrade to 16.13.0
cn
- 去掉 tarsnode 中不用的日志
- 修复 tarsnode 对 tars 框架服务, 使用旧配置文件
- 修复 tarsnode 保持 tars 服务的 local port 不要改变
- dockerfile 中 nodejs 版本升级到 v16.13.0