-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Expressions Editor truncates expressions with too many segments #5001
Comments
@prononext I've tried these two workflows, and I'm unfortunately unable to reproduce. Regarding a stable release: we are working on building a new development and release flow that would allow us to have stable and LTS releases. It'll hopefully be ready in the next month. Workflow 1: Posting JSON Directly
Workflow 2: Downloading a large JSON and posting it to another URL
|
Here is how to reproduce the bug: 1. Paste this into a HTTP Request Node Body
|
I finally manage to find the issue. It's not related to the HTTP node or in general to any of the nodes. There seems to be a bug in the expressions editor, that's truncating really long expressions in the frontend. |
yes I guess that is related. I just tested on 0.209.1 and the bug is still there. |
Update: the issue is not related to generally long expressions, but expressions with too many tokens. It's possibly an issue with codemirror on the way iterate over segments in codemirror, that's truncating these expressions. |
@netroy do you know at which of the latest versions it was still working? |
perhaps |
Fix got released with |
I am using 0.209.0. and also tested on 0.208.1, both in queue mode setup.
In all of my HTTP-Request nodes which I have imported, there are body parameters and query parameters cut off.
I used to have 100 lines of body parameters and now there are only 62 lines, which means that I get a "invalid JSON Body Parameter" Error.
Also the expression window in the HTTP-Request node has display problems when scrolling down and shows just a white area.
Sometimes content loads when clicking into the white space. This happens on all latest Chrome, Firefox and Edge Browsers.
On 0.196.0 where I was last, all was fine.
I am am very frustrated as n8n has gotten more and more bugs and is not fit for production use anymore in the the latest versions. Seeing the "30 second scrolldown" on the github branches with no clear "stable" or "development" branch maybe one of the problems why versions just get released on https://docs.n8n.io/reference/release-notes/ and users get notified about a update like it is stable in their n8n user interface. Sorry for the harsh words but I was promoting n8n quite strong and based big projects on it but now it begins to put everything at risk.
It would be really nice to see some change and see n8n production ready to scale.
General Versions used to confirm this bug:
TRAEFIK_VERSION_TAG=v2.9.6
POSTGRESQL_VERSION_TAG=12.13 / and 11
REDIS_VERSION_TAG=alpine
N8N_VERSION_TAG=0.209.0 / and 0.208.1
No further logs error logs were thrown by n8n or the other containers (db, redis etc. )
The text was updated successfully, but these errors were encountered: