next-evolve-x

> _🤖_ > > 您好，感谢您的反馈。 > > 根据我在Apollo仓库中找到的相关问题，这个问题可能与Apollo当前的设计有关。在Apollo中，如果配置未发布，是无法撤销的。Apollo的“回滚”功能允许您恢复到之前发布的版本，但这只适用于已经发布的更改。对于未发布的更改，由于它们不是发布版本的一部分，所以无法回滚。 > > 另外，关于文本编辑模式下注释重复出现的问题，我找到了一个类似的问题[#4276](https://github.com/apolloconfig/apollo/issues/4276)，这个问题已经在[#4279](https://github.com/apolloconfig/apollo/pull/4279)的pull request中被修复了。这个修复是通过检查item.isDeleted来判断项目是否被删除。 > > 但是，我注意到您使用的Apollo版本是2.0.1，而这个修复是在2.1.0版本中才有的。因此，我建议您升级到最新的Apollo版本，看看这个问题是否还存在。 > > 如果问题仍然存在，那么可能需要更深入地研究这个问题。如果可能的话，您能提供更多关于这个问题的信息吗？例如，这个问题是否在所有环境中都会出现，还是只在特定的环境中出现？这将有助于我们更好地理解和解决这个问题。 > > 再次感谢您的反馈，期待您的回复。 > > ## Sources > * [如果不小心删除或修改了一个配置，但是还未发布，能不能增加撤销待发布的值得功能](https://github.com/apolloconfig/apollo/issues/4970) > *...

> ### Description > 运行时候提示如下信息，怎么解决，有没有源码编译部署说明 [2023-12-29 00:55:37] [FATA] need:[github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterNodeStore github.com/eolinker/apinto-dashboard/modules/notice/notice-store.notice_store.INoticeChannelStatStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IClusterVariableStore github.com/eolinker/apinto-dashboard/modules/group/group-store.group_store.ICommonGroupStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IPluginHistoryStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IApiHistoryStore github.com/eolinker/apinto-dashboard/modules/api/store.api_store.IAPIStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterCertificateStore github.com/eolinker/apinto-dashboard/modules/dynamic/dynamic-store.dynamic_store.IDynamicPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateHistoryStore github.com/eolinker/apinto-dashboard/modules/plugin_template/plugin-template-store.plugin_template_store.IPluginTemplateStore github.com/eolinker/apinto-dashboard/modules/base/quote-store.quote_store.IQuoteStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginRuntimeStore github.com/eolinker/apinto-dashboard/modules/module-plugin/store.store.IModulePluginEnableStore github.com/eolinker/apinto-dashboard/modules/plugin/plugin-store.plugin_store.IClusterPluginPublishHistoryStore github.com/eolinker/apinto-dashboard/modules/module-plugin/store.store.IPluginResources github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariableRuntimeStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariablePublishVersionStore github.com/eolinker/apinto-dashboard/modules/variable/variable-store.variable_store.IVariableHistoryStore github.com/eolinker/apinto-dashboard/modules/openapp/openapp-store.openapp_store.IExternalApplicationStore github.com/eolinker/apinto-dashboard/modules/application/application-store.application_store.IApplicationHistoryStore github.com/eolinker/apinto-dashboard/modules/cluster/cluster-store.cluster_store.IClusterStore...

> 编译的时候，需要带上tags  是的太棒了

> Okay, we have also identified this issue and expect a version to be released next week to fix it together. Thank you for your feedback. What's new or bug...

I think it's a bug here  But this only affects the returned content Again, what happens when the plug-in fails to load

配置文件，自己配置Admin的 advertise_urls:配置就好了，你不配，程序内部会自己去根据主机网络解析出： 

看代码，这里查重的方法判断都是用的input.Method，完全没有管数据库查出来的已存在的api的method 

什么时候有版本呀，或者解决方案发一下，我本地先自行处理

Is it okay to add Option to the front-end modification?

The logic of repeated detection has a bug.