An error occurred while creating the application. What should I do to fix it?

[chenxumin1]

An error occurred while creating the application. What should I do to fix it?

[dosubot[bot]]

Hello @chenxumin1! I'm Dosu, a bot here to help you solve bugs, answer questions, and support you in becoming a contributor. I'm ready to assist while you wait for a human maintainer. How can I help you today?

To resolve the "Oops, something went wrong. No schema found" error when creating a new application, follow these steps:

1. Check the URI: Ensure that the URI used to fetch the OpenAPI schema is correct. This URI should point to a valid endpoint that can return the schema.

2. Verify Endpoint Accessibility: Make sure the endpoint specified is accessible and properly configured to return the OpenAPI schema.

3. Debug the Fetch Function: Investigate the fetchOpenApiSchemaJson function to ensure it is correctly implemented and capable of fetching the schema from the given URI.

4. Logging and Debugging: Add additional logging or debugging to understand why the schema is not being returned. This can help identify if there are network issues or incorrect configurations.

If these steps do not resolve the issue, further investigation into the specific implementation of the schema fetching logic and the configuration of the service providing the schema may be necessary ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[chenxumin1]

您好 ！我是 Dosu，一个帮助您解决错误、回答问题并支持您成为贡献者的机器人。我已准备好在您等待人工维护者时提供帮助。今天我能帮你什么忙呢？

要解决“糟糕，出了点问题。No schema found“错误，请执行以下步骤：

1. 检查 URI：确保用于获取 OpenAPI 架构的 URI 正确无误。此 URI 应指向可返回架构的有效终端节点。
2. 验证端点可访问性：确保指定的端点可访问并正确配置为返回 OpenAPI 架构。
3. 调试 Fetch 函数：调查该函数以确保它已正确实现并能够从给定 URI 获取架构。fetchOpenApiSchemaJson
4. 日志记录和调试：添加其他日志记录或调试以了解未返回架构的原因。这有助于确定是否存在网络问题或配置不正确。

如果这些步骤无法解决问题，则可能需要进一步调查架构获取逻辑的具体实现和提供架构的服务的配置[1].

要继续与 Dosu 交谈，请提及 。

帮助 Dosu 学习！给它反馈：伟大的回应 |无关紧要的答案 |不正确的来源 |太冗长 |幻觉 |Bug 报告 |其他

The Alembic container failed to start. How can I fix this?

[chenxumin1]

Agenta returned 502 - Unexpected status code [agenta.sdk.middleware.auth]

[mmabrouk]

Hello @chenxumin1 ,

Can you please share the:

• network tab from the browser with the request that is failing
• The api docker container logs
• The web docker container logs

Can you please also check whether you can create test sets?

[mmabrouk]

You have mentioned that The Alembic container failed to start.

The alembic container is supposed is to start and shutdown at start. If it has failed (not shut down normally), please share the logs there too

[chenxumin1]

[chenxumin1]

SUPERTOKENS_API_KEY=replace-me AGENTA_CRYPT_KEY=replace-me .env.oss.gh，What should I change these configurations in it to?

[mmabrouk]

SUPERTOKENS_API_KEY=replace-me AGENTA_CRYPT_KEY=replace-me .env.oss.gh，What should I change these configurations in it to?

You do not need to change these to get Agenta to work, they are only thought for security.

• Can you please check whether you can create a test set?
• It looks like the chat service cannot reach the api service. There is an issue in networking. Are you running Agenta in localhost? Do you have some firewall, network rule that makes the chat container reaching the backend container though localhost impossible?

One thing to do is to open a shell inside the chat container and try to curl http://docker.internal.host/api/health and see whether it is reachable