ERROR: Enter a valid date/time

Hi,

I woke up this morning to BabyBuddy being down, checked github and noticed there was an issue with the latest release, so while the fix was being worked on I decided to move BabyBuddy from being a docker run command to a docker-compose file.

docker-compose file:

version: "2.1"
services:
  app:
    image: lscr.io/linuxserver/babybuddy:amd64-latest
    environment:
      - TZ=Pacific/Auckland
    volumes:
      - config:/config
    ports:
      - 8000:8000
    restart: unless-stopped
    networks:
      default:
        ipv4_address: 10.10.11.211
    dns:
      - 10.10.11.1
      
networks:
  default:
    external:
      name: public
      
volumes:
  config:

I have now pulled the latest image 1.9.1-ls16, and I am having an issue with date/time when adding entries. See example below.

I have tried different TZ variables but it doesn’t seem to change the outcome.

When I go to a running timer, and say, add it as a sleep timer, the time and date values appear then disappear.

I believe I was running version 1.8, I can roll back to a backup from last night to check.

Anyone have any suggestions?

[cdubz]

Ok all, I think I have this resolved on master – would appreciate if someone here is able to test and confirm but regardless I’ll create a new release in the next 24 hours or so. Big thanks to @kdrobnyh for the sleuthing that led me to be able to reproduce and fix this.

[kdrobnyh]

I have some updates about the issue: we have 2 BabyBuddy users. Today I switched to Docker and updated BabyBuddy to 1.9.2. I checked from my phone - everything seemed to work as usual. However, when my wife tried to add a new entry, she encountered this error (Enter a valid date/time.). POST messages were identical from both users, but one received error, the other did not. I checked the database - for one user the language was “en-US” (no errors), for another one is “en” (the error mentioned above). In GUI settings (on the website), both users have chosen language “English (US)”. I believe that caused the issue, since when I changed the language, everything started to work again. That also supports @lelandbay 's comment above.