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

Notify Users about Invalid Forward Headers #1329

Closed
1 of 2 tasks
Jjx003 opened this issue Oct 31, 2023 · 2 comments · Fixed by #1392
Closed
1 of 2 tasks

Notify Users about Invalid Forward Headers #1329

Jjx003 opened this issue Oct 31, 2023 · 2 comments · Fixed by #1392
Assignees
Milestone

Comments

@Jjx003
Copy link

Jjx003 commented Oct 31, 2023

Search before asking

  • I have searched the EvaDB issues and found no similar feature requests.

Description

As many issues have pointed out earlier (#1315, #1217, #1206, #1150), the forward header causes a lot of issues for users.
In this particular request, I am asking for a mechanism to detect faulty forward headers so that users can fix the problems quickly and not have to dig into all the wrong areas of code.

I think some ideas for requirements should be:

  1. Notify users if the signature is missing. Right now, the error says "Cannot infer io signature from the decorator..."
  2. Notify users if the signature is malformed (e.g. missing column names, types, or shapes)

Use case

No response

Are you willing to submit a PR?

  • Yes I'd like to help by submitting a PR!
Copy link
Contributor

👋 Hello @Jjx003, thanks for your interest in EVA DB 🙏 Please visit our 🔮 Tutorials to get started, where you can find quickstart guides for simple tasks like Image Classification all the way to more interesting tasks like Emotion Analysis.

If this is a 🐞 Bug Report, please provide a minimum reproducible example to help us debug it.

If this is a ❓ Question, please provide as much information as possible, including dataset examples and query results.

@hershd23 hershd23 self-assigned this Nov 10, 2023
@hershd23
Copy link
Contributor

Taking this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants