From 8d1f6ecc49c8f93f24f4609e05a1236f41dc2451 Mon Sep 17 00:00:00 2001
From: Arjan <44190435+vingerha@users.noreply.github.com>
Date: Fri, 24 Nov 2023 18:20:42 +0100
Subject: [PATCH] Update README.md

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 45643e8..54db8ea 100644
--- a/README.md
+++ b/README.md
@@ -29,9 +29,9 @@ Core GTFS uses start + stop, it then determines every option between them and pr
 
 20231104: initial version
 
-## ToDo's / In Development
-- Issue when updating the source db, it throws a db locked error. This when an existing entity for the same db starts polling it at the same time
-- (DONE) Icon for the integration (brands)
+## ToDo's / In Development / Known Issues
+- Issue when updating the source db, it throws a db locked error OR pygtfs. This when an existing entity for the same db starts polling it at the same time
+- Issue when updating the source db: pygtfs error: at the moment unclear as errors fluctuate, posisbly a lack of resources (mem/cpu)
 - bypass setup control for routes that have no trips 'today'. The configuration does a spot-check if start/end actually return data with the idea to validate the setup. However, this only checks for 'today' so if your route actually has no transport running at the day of setup (say Sunday or Holiday) then it will reject it.
 
 ## Installation via HACS :