with latest PR #525 I always have "No route matches" as soon as I click into a conversation #572
Replies: 9 comments 7 replies
-
@variousfire dang, sorry for the trouble! I hope we didn't break things for a lot of people. I just tried my instance and it's working for me, and I also did a fresh deploy to Render and Heroku and both of those setups seem to be working. But I'm worried now that we introduced a bug for some people in a particular state (whatever state you're in). I need more information in order to debug. Where are you seeing that error, is it in the logs? Can you share the URL that is being loaded when that error appears? And is it every conversation? Are you able to start a new conversation with an assistant even though you can't view older conversations? |
Beta Was this translation helpful? Give feedback.
-
I run totally local so I am likely to miss out a lot of things. The update had always been chaotic (i git pull like very 3~4 weeks just to feel the work done so far and always run into some issues 1 way or the other although they are fixed every time). Let me try to recall from memory for now and I will extract as much log if I can when I have more time.
If there are other info I can give I will do my best. Please let me know. Thanks |
Beta Was this translation helpful? Give feedback.
-
Hmm, git pull should always be clean. I maintain a clean git history on
main with only forward commits. I wonder if that is a clue.
Have you needed to change some local files in your main? If so, do you
remember what it was? That could explain why you keep needing to do a reset
and may explain this issue.
When I’m back at my computer I can try a clean local docker setup.
|
Beta Was this translation helpful? Give feedback.
-
Error dump:
|
Beta Was this translation helpful? Give feedback.
-
Here some additional info: I did a git diff on Gemfile.lock (on a M1 MBP)
i have re-done another `docker compose build --no-cache` after completely remove the container (but keeping the volume)
`docker compose up`
I can load and just login `http://localhost:3000/` fine. but as soon as I start a conversation or load an existing one I get the errorHere is the docker log
and the web ui error
judge from the error message, |
Beta Was this translation helpful? Give feedback.
-
Same here:
|
Beta Was this translation helpful? Give feedback.
-
Dang, I think the slug-in-url feature is turning out to be more trouble than it's worth. I'm going to try to undo that change without reverting the PR. Stay tuned... |
Beta Was this translation helpful? Give feedback.
-
Sorry about that everyone; and sorry I’ve been awol over last weeks to investigate fix. |
Beta Was this translation helpful? Give feedback.
-
I just merged in #588 which I think should fix this. Can anyone who was experiencing this confirm if things are better now? |
Beta Was this translation helpful? Give feedback.
-
I updated to the latest main branch and it gives me that.
Beta Was this translation helpful? Give feedback.
All reactions