-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Packs tab stops rendering after some time #919
Comments
As anyone been able to verify this issue? I have 3 disparate clusters and a stand alone test server and they all have this issue. |
I have the same issue. I haven't change any global setting before it occurs. The stackstorm version is I tried the followings but it didn't help:
On firefox console, I can see the following errors:
Even in the case of those events are not related, this really looks like a frontend problem. In the network console of firefox, I can see the package configurations being retrieved through API calls. EDIT 1: after a complete re-installation, the bug is no more present. The errors in the Firefox console are still there so it is definitely not related to the bug. The stream connection error is probably related to a forced refresh (ctrl+shift+r). And the API call give the same output as before on route (on route /config_schemas and /configs?show_secrets=true) Suspicion continues to be on the fronted part. |
This is still an issue in 3.8.0 for us. |
I have the same issue, and raise it, but nobody response so far. It seems st2 need access stackstorm exchange portal to retrieve all packs information. The pack page is empty if st2 instance has no internet access. |
I'm having some weird issue where the packs tab is not rendering the list of packs.
You can see a list of the packs that is queried as a payload back to the client, but the site wont render it. I've tried this in incognito mode both in FF and Chrome and get the same issue. I have three clusters in three datacenters and they're all doing the same thing.
I do have our own index.json file for our own custom pack install list, but this has never been an issue before. Nothing in the nginx error or access logs that indicate an issue. No errors in the console.
I dont even know how to begin troubleshooting this.
The text was updated successfully, but these errors were encountered: