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

Studio fell in production #1138

Closed
aeworxet opened this issue Sep 17, 2024 · 7 comments · Fixed by #1139
Closed

Studio fell in production #1138

aeworxet opened this issue Sep 17, 2024 · 7 comments · Fixed by #1139
Labels
bug Something isn't working

Comments

@aeworxet
Copy link
Contributor

Describe the bug

Studio is not functional at https://studio.asyncapi.com with error in console.

How to Reproduce

Open https://studio.asyncapi.com.

image

Expected behavior

Studio is expected to work.

@aeworxet aeworxet added the bug Something isn't working label Sep 17, 2024
Copy link

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@aeworxet
Copy link
Contributor Author

The bug is caused by code from https://github.com/asyncapi/converter-js introduced in

92cfd9a0877ca2f9483d8bca0b67d8f0479aca0e

A fast solution would be to revert and then figure out what happened.

@jonaslagoni @ItshMoh

@aeworxet
Copy link
Contributor Author

Take into account #1094 (comment), just in case.

@aeworxet
Copy link
Contributor Author

Another fast solution would be to temporarily hard-lock the @asyncapi/converter version in both package.jsons:

./apps/studio/package.json
./apps/studio-next/package.json
"@asyncapi/converter": "1.5.0",

Choose which one is to your liking.

@jonaslagoni
Copy link
Member

Because the converter never had a requirement that the code must be able to run in the browser, I dont think the converter will get a rollback, unless majority wants it.

Studio needs to run the conversion logic in the backend and send it to the frontend, it's a problem because a dependency is no longer browser-compatible.

@aeworxet
Copy link
Contributor Author

Then, to get the Studio up and running right now, the only thing that is possible is to hard-lock the @asyncapi/converter on version 1.5.0 and after that start looking for a permanent solution.

@Amzani
Copy link
Collaborator

Amzani commented Sep 18, 2024

We can go with this option @aeworxet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
3 participants