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

Error Message "Could not reach the server" on mounting to FastAPI #1330

Closed
sajsax10 opened this issue Sep 10, 2024 · 7 comments
Closed

Error Message "Could not reach the server" on mounting to FastAPI #1330

sajsax10 opened this issue Sep 10, 2024 · 7 comments

Comments

@sajsax10
Copy link

Describe the bug
When trying to run Chainlit mounted on FastAPI , the Chainlit app seems to be failing on the path "/chainlit" with the error message:

Could Not Reach the Server

Accompanied by this in the terminal:

Translated markdown file for en-US not found. Defaulting to chainlit.md.

The Chainlit app runs perfectly fine when run separately.

To Reproduce
Error observed for Chainlit v1.1.404, normal behavior for v1.1.400

Mounting chainlit on FastAPI app
mount_chainlit(app=app, target="chatbot/chatbot.py", path="/chainlit")

Run FastAPI app:

uvicorn main:app --host 0.0.0.0 --reload

Expected behavior
App should be served as expected unless I'm doing something wrong

Desktop (please complete the following information):

  • OS: Windows10
  • Browser: Chrome
  • Version 128.0.6613.120
@stephenrs
Copy link

stephenrs commented Sep 11, 2024

@sajsax10 Since you are specifying a path, this is likely related to #1313, #1262, and #1317

As far as I'm aware, the last release that didn't have this critical bug was 1.1.402, but unfortunately the Chainlit company doesn't seem to be taking it very seriously :(

@dokterbob
Copy link
Collaborator

@stephenrs We are. Please refrain from attacking us, it's unpleasant and unproductive. We appreciate your support but please be aware that we are doing are very best with the bandwidth we have.

@sajsax10 @stephenrs Could you please try and validate whether #1337 resolves your issue?

@stephenrs
Copy link

stephenrs commented Sep 13, 2024

@dokterbob I'm not attacking you, in fact, I wasn't even talking to you. I'm pointing out my observations, and I'm glad to see you're finally showing some indications that you're paying attention to critical issues like this one. I reported this issue more than 3 weeks ago, and there have been several other issues related to the same problem, and today is the first time you've had anything to say about it.

So, I'd say my observation was objective and an accurate reflection of the truth...it didn't seem like you were taking it seriously until now.

I would recommend that you get your emotions under control, and stop whining and being so defensive. None of this is personal. Focus on the work, focus on the goal, and smile about it :)

@stephenrs
Copy link

stephenrs commented Sep 13, 2024

@dokterbob Just a quick follow-up. You seem to spend a considerable amount of time thinking about and talking about how you feel. So, I think it would be helpful for you to devote some time to thinking about how people in this community feel as a result of your actions, inactions, or lack of communication.

People who encountered this particular problem were completely blocked on their entire project if they didn't know they could downgrade to 1.1.402. This is likely an actual crisis for some people. So, I'm thinking about them and how they feel and doing my best to make sure they are informed about where your priorities appear to be so they don't get stuck in a crisis situation - because that feels terrible.

Also, if you guys make it to the point of having paying customers, what people are going to be saying here is quite likely going to be much more emotionally triggering than anything you'll hear from me - and they won't be focused on helping anyone except themselves.

Clearly, my interest is in helping you and the community. So, it might best serve your interests to start thinking about us as customers - because that's who we are. Our happiness is more important than yours, such is the nature of the real world of business. And, whining and being defensive whenever someone speaks a truth that you don't like is unpleasant and unproductive and serves the interests of no one.

...and it's important to confront the reality that you don't get to control how people express themselves to suit your narrow personal sensibilities. The world doesn't work like that. The onus is on you to stay focused on what we're all gathered here to accomplish and to be adaptable.

It might also be helpful to keep in mind that not everyone feels "attacked" when they hear a truth that they don't like. Some people might even apologize for letting such a serious, potentially widely impacting issue go unaddressed for so long.

Think of the pain you caused by letting this major issue sit for almost a month without giving a single indication that you were taking it seriously. We also don't need to hear you every day whine about how busy you are. We're all busy Mathijs, not just you. So why are you the only person who is continually whining about it? It just wastes more of our collective bandwidth.

So, if you do feel attacked when hearing the simple truth, maybe some self-reflection would be a more constructive use of your time than whining about it. The truth is just the truth, right?

Not as "quick" as I thought it would be :) but hopefully it's useful in some way.

@dokterbob
Copy link
Collaborator

@dokterbob I'm not attacking you, in fact, I wasn't even talking to you. I'm pointing out my observations, and I'm glad to see you're finally showing some indications that you're paying attention to critical issues like this one. I reported this issue more than 3 weeks ago, and there have been several other issues related to the same problem, and today is the first time you've had anything to say about it.

So, I'd say my observation was objective and an accurate reflection of the truth...it didn't seem like you were taking it seriously until now.

I would recommend that you get your emotions under control, and stop whining and being so defensive. None of this is personal. Focus on the work, focus on the goal, and smile about it :)

Cool. Note there's 355 issues that YOU can see. There's a bunch you can't see.

Sending long write ups don't help there, it detracts from limited bandwidth we have.

@dokterbob
Copy link
Collaborator

Closing this as the case as the reproduction seems to fully match the example https://docs.chainlit.io/integrations/fastapi which was tested to be resolved by #1337. Very l33t, much wow.

We're doing a release today.

@stephenrs
Copy link

stephenrs commented Sep 16, 2024

Cool. Note there's 355 issues that YOU can see. There's a bunch you can't see.

Not sure how this is relevant...and maybe if you communicated your priorities or didn't ignore questions about them it wouldn't matter at all which issues are public and which are not.

I thought you didn't approve of SCREAMING(?) It's only acceptable when you do it, like everything else you whine about day after day?

Sending long write ups don't help there, it detracts from limited bandwidth we have.

More whining. Wow. You really don't get it do you?

But hopefully you're learning that when you publish lies about the status of a product, which is illegal in the EU, your "limited bandwidth" is of no concern to the public you lied to and they don't owe you anything. The debt is entirely yours to deliver what you have promised or face worse consequences than people who "annoy" you.

Glad to see some energy and some focus on helping the people of this community get their work done, however.

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

No branches or pull requests

3 participants