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
The normal version is spring-cloud-2023.0.3+spring-boot-3.2.11+spring-cloud-alibaba-2023.0.1.2 or spring-cloud-2023.0.3+spring-boot-3.3.5+spring-cloud-alibaba-2023.0.1.2
The abnormal version is spring-cloud-2023.0.3+spring-boot-3.2.11+spring-cloud-alibaba-2023.0.1.3 or spring-cloud-2023.0.3+spring-boot-3.3.5+spring-cloud-alibaba-2023.0.1.3
The logs under normal circumstances are as follows
The logs of abnormal situations are as follows
By comparison, there are no startup logs related to nacos config in version 2023.0.1.3
The text was updated successfully, but these errors were encountered:
The log screenshot you given here is expected. The missing logs actually belong to nacos-client and has been logged to the logging files of nacos-client in the new version.
The 2023.0.1.3 version no longer supports pulling and configuring default names, which feels like there are more configurations. If each program uses the configuration center, it must configure this parameter.
Additionally, this prompt issue still needs to be resolved
The normal version is spring-cloud-2023.0.3+spring-boot-3.2.11+spring-cloud-alibaba-2023.0.1.2 or spring-cloud-2023.0.3+spring-boot-3.3.5+spring-cloud-alibaba-2023.0.1.2
The abnormal version is spring-cloud-2023.0.3+spring-boot-3.2.11+spring-cloud-alibaba-2023.0.1.3 or spring-cloud-2023.0.3+spring-boot-3.3.5+spring-cloud-alibaba-2023.0.1.3
The logs under normal circumstances are as follows

The logs of abnormal situations are as follows

By comparison, there are no startup logs related to nacos config in version 2023.0.1.3
The text was updated successfully, but these errors were encountered: