-
Notifications
You must be signed in to change notification settings - Fork 0
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
As a developer, I would like to be able to see latest changes from Nachet on the deployed instance #114
Comments
Report IssueThe default value for
ConclusionEven if the value is set up in the yaml file it seems the deployment doesn't follow that value of |
…ontroller configuration deployment
issue #114: find why client_max_body_count is overriden
Still need to change the deploy branch to main (when main is ready) |
What are we waiting for before doing this ? |
Still waiting for this PR to be merged: Waiting on @RussellJimmies approval |
…to-be-able-to-see-latest-changes-from-nachet-on-the-deployed-instance fixes #114: change image to nachet-backend main branch
The deployment is currently pointing to an old branch. I would like it to point to the main like Finesse does.
Issue Description
Currently, the main branch of Nachet is not up to date with the latest deployment. The current branch
51-implementing-2-models
is pending review to able to be merged intomain
.The actual issue with the deploy version is that it is not able to classify images. The return error
413 413 Request Entity Too Large
could be either an ingress error or a backend error.This error started on Friday and was discovered by Taran around 4 pm.
Change between the moment the deployment work and the problem was reported.
We had discussion about increasing the content length for uploads 2 weeks ago.
Test for investigation
main
branch with latest changeThe text was updated successfully, but these errors were encountered: