Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

无法删除旧的配置 #5123

Closed
3 tasks
cjdxhjj opened this issue Apr 12, 2024 · 7 comments
Closed
3 tasks

无法删除旧的配置 #5123

cjdxhjj opened this issue Apr 12, 2024 · 7 comments
Labels

Comments

@cjdxhjj
Copy link

cjdxhjj commented Apr 12, 2024

  • I have checked the discussions
  • I have searched the issues of this repository and believe that this is not a duplicate.
  • I have checked the FAQ of this repository and believe that this is not a duplicate.

Describe the bug
A clear and concise description of what the bug is.
image
image

如图,界面上展示的是1天,然而这个最后时间过去好几个月了,依然展示,无法删除
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional Details & Logs

  • Version
  • Error logs
  • Configuration
  • Platform and Operating System
Copy link

dosubot bot commented Apr 12, 2024

To address the issue of not being able to delete an old configuration and the interface not accurately reflecting the most recent update or refresh times, you can follow these steps:

  1. Deleting an Old Configuration: Look for the delete link for each configuration item in the Apollo interface. This link triggers the removeItem function, which is responsible for removing items from the synchronization process. This function operates on createItems and updateItems, representing items to be created and updated, respectively. For more technical details, you can refer to the SyncConfigController.js file in the Apollo repository.

  2. Ensuring Accurate Reflection of Update/Refresh Times: The interface's reflection of update or refresh times might require ensuring that the AngularJS controller associated with the page updates the model and view accordingly. This involves calling backend APIs to fetch the latest configuration state and then updating the AngularJS model, which updates the view.

  3. Manual Refresh Option: If automatic updates do not reflect, consider implementing a manual refresh option. In the Apollo interface, there's a button that calls the refreshNamespace() function, which can be a starting point for implementing or troubleshooting this functionality.

Ensure that the backend and AngularJS services are correctly integrated and support the necessary functionality for deletion and fetching the latest configuration state. If issues persist, checking error messages and confirming that you have the necessary permissions to delete configurations might provide further insights.

The version of Apollo you're working with is identified as 2.3.0-SNAPSHOT in the pom.xml file, which might be relevant when looking into documentation or seeking specific help for your version.

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@nobodyiam
Copy link
Member

说明这几个实例还连着。配置获取时间是指第一次拿到这个配置的时间。

@cjdxhjj
Copy link
Author

cjdxhjj commented Apr 16, 2024

我代码里早已去除了其引用

@cjdxhjj
Copy link
Author

cjdxhjj commented Apr 16, 2024

image
通过日志发现,client会一直试图加载application 这个namespace

@nobodyiam
Copy link
Member

可以 debug 或者使用 arthas 看下是哪里引用了 application namespace

Copy link

stale bot commented May 16, 2024

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 16, 2024
Copy link

stale bot commented May 24, 2024

This issue has been automatically closed because it has not had activity in the last 7 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants