-
Notifications
You must be signed in to change notification settings - Fork 109
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
[Bug] Pipeline editor throwing Error #1124
Comments
Hi @Safvan-tsy thank you for raising this issue, could you confirm if this bug still persists or if it has been resolved now? Thank you 🙏 |
Hey @kuroxx . Its not resolved i'm still facing the same issue |
Thanks for updating me @Safvan-tsy, let me check with our team internally and get back to you soon! |
Hi @Safvan-tsy |
A side question is, can you go to your previous created pipeline? |
Hey @donch1989 Browser: OS: |
hey @EiffelFly no i can't view editor for any pipelines |
@Safvan-tsy Did you still experience the same bug? We have implemented some fixes could you help us double check it 🙏 |
still facing this issue in my chrome browser more info from logs
I think this issue is mostly due to any of my local configurations |
I can access the pipeline editor from my firefox . @EiffelFly |
Hi @Safvan-tsy That is great. This information is valuable for us
https://api.instill.tech/v1beta/component-definitions?page=1&view=VIEW_FULL net::ERR_INTERNET_DISCONNECTED makeMethodRequest @ 6a130808-c03db8803b1ec173.js:1 get @ 6a130808-c03db8803b1ec173.js:1 listComponentDefinitions @ 6a130808-c03db8803b1ec173.js:1 listComponentDefinitions @ 6a130808-c03db8803b1ec173.js:1Understand this error layout-2a56d04df9fdce6a.js:1 error in retry TypeError: Failed to fetch About this I will take a look deeper, what about your Google Chrome now? Can you access our product with it now? (We have several fixes recently) |
Is There an Existing Issue for This?
Are you willing to own the issue?
Where did you encounter this bug?
Instill Cloud
Describe the Bug
Instill cloud >> create a pipeline or edit a pipeline >> Throwing the below exception (ss attached)
Steps to Reproduce
No response
Actual Result
No response
Expected Behavior
No response
Technical Details
No response
Anything Else?
No response
The text was updated successfully, but these errors were encountered: