Field updating bug

[Jonas]

Please fill in the questionnaire below.

Technical Help Questionnaire

Have you read and followed the instructions at: *READ ME FIRST* Technical Help FAQs - #2 by nigel ?

Answer: Yes

Self-Hosted Installation and Setup Questions

How have you self-hosted Baserow.

Answer: Docker-compose.all-in-one.yml

What are the specs of the service or server you are using to host Baserow.

Answer: 8vCPU x 16GB RAM

Which version of Baserow are you using.

Answer: 1.28.0

How have you configured your self-hosted installation?

Answer:

version: "3.4"
services:
  baserow:
    container_name: baserow
    image: baserow/baserow:1.28.0
    environment:
      BASEROW_PUBLIC_URL: 'https://baserow.mydomain.com'
      BASEROW_CADDY_ADDRESSES: :443
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - baserow_data:/baserow/data
volumes:
  baserow_data:

What commands if any did you use to start your Baserow server?

Answer:

docker-compose up -d

Describe the problem

Describe, step by step, how to reproduce the error or problem you are encountering.

I have issue with editing values inside one table (1000+) rows. When I click backspace or delete nothing happens until I enter some characters. I recorded video with this issue. This happens not only to field Name but to any other fields with text values. For describing this problem I’ve hidden other fields and provided live log from baserow server.

Provide screenshots or include share links showing:

Recordered video in logs section.

How many rows in total do you have in your Baserow tables?

I have database with 7 tables. 6 of them have 100-200 rows. But the first one has 1100 for now and this is the table I have problems with.

Please attach full logs from all of Baserow’s services

Can’t attach files here, so I’ve uploaded video to Vimeo service
Issue + Logs

[davide]

Hi @Jonas,

I’m sorry you are experiencing this issue with Baserow.

I tried to replicate it on my end but couldn’t reproduce the same behavior. To help me understand the issue better, could you please provide a bit more detail? Here are a few questions that might clarify things:

1. Is this error happening only locally or does it happen also on our SaaS (https://baserow.io)
2. Does it happen on a specific browser or on different browsers?
3. Is this happening only for that specific table? Or maybe only for all the big tables? Or instead is for any table you have in your Baserow instance?
4. Is there anything else you might suggest to us to replicate the issue?

[Jonas]

@davide

Hi @Jonas,

I’m sorry you are experiencing this issue with Baserow.

I tried to replicate it on my end but couldn’t reproduce the same behavior. To help me understand the issue better, could you please provide a bit more detail? Here are a few questions that might clarify things:

1. Is this error happening only locally or does it happen also on our SaaS (https://baserow.io)
2. Does it happen on a specific browser or on different browsers?
3. Is this happening only for that specific table? Or maybe only for all the big tables? Or instead is for any table you have in your Baserow instance?
4. Is there anything else you might suggest to us to replicate the issue?

Hi Davide,

1. I only have self-hosted version. So I don’t know if this also happen on baserow.io
2. It happened only in chrome, I didn’t use it with other browsers
3. Yes, only this specific table with 1000+ rows. I don’t have yet another big tables
4. Actually, when I tried to test this table on other browsers, I’ve found out that issue is gone in another browser (firefox). And moreover, issue dissappeared also in Chrome when I started new session in private window. But it is persistent in main Chrome window, where session lasts for week. After I made sign out and then sign in the issue is gone for now in every window. So I suppose that the problem is with cache or something like this, because when it occured for the first time some time passed after sign in. I won’t sign out for some time to see if the problem returns and will leave here message.

[Jonas]

@davide

Hi @Jonas,

I’m sorry you are experiencing this issue with Baserow.

I tried to replicate it on my end but couldn’t reproduce the same behavior. To help me understand the issue better, could you please provide a bit more detail? Here are a few questions that might clarify things:

1. Is this error happening only locally or does it happen also on our SaaS (https://baserow.io)
2. Does it happen on a specific browser or on different browsers?
3. Is this happening only for that specific table? Or maybe only for all the big tables? Or instead is for any table you have in your Baserow instance?
4. Is there anything else you might suggest to us to replicate the issue?

Hello, @davide ,

Over the past week, I’ve been testing this case in various ways and have learned some new details:

1. This happens only locally. On your SaaS I can’t reproduce the same behaviour when I use the same tables.
2. I tested it in Chrome and Firefox. In both browsers, the same behavior appears approximately one day after signing in. If I sing out and clear cache or start new session in private windows the issues dissapears for some time.
3. I’ve downloaded some sample csv file customers-10000.csv from this site GitHub - datablist/sample-csv-files and the same issue appeared in this table too. So, I assume that the problem does not lie in the data I store in my original table. Other small tables in my database act normally.
4. In my local instance I use webhooks in every table that send webhooks to separete container (webhook-listener). This container modifies another table using baserow API. This table has no issues. And when I switch off this listener and webhooks the issue with big tables persist. So, I don’t think it can cause the issue I described before.