Observation: unrecognized value "on;" for "ON_ERROR_STOP": Boolean expected

[dancesWithCycles]

Hi folks,
Have you ever noticed the unrecognized value "on;" for "ON_ERROR_STOP": Boolean expected feedback when calling npm run build? Here is a larger snippet.

...
ALTER TABLE
COPY 53855
COMMIT
+++ realpath ./build.sh
++ dirname /home/pacs/sib00/users/gtfsr_srv_vbb/git/berlin-gtfs-rt-server/build.sh
+ lib=/home/pacs/sib00/users/gtfsr_srv_vbb/git/berlin-gtfs-rt-server/lib
+ sponge
+ psql -b
+ NODE_ENV=production
+ node_modules/.bin/build-gtfs-match-index /home/pacs/sib00/users/gtfsr_srv_vbb/git/berlin-gtfs-rt-server/lib/hafas-info.js /home/pacs/sib00/users/gtfsr_srv_vbb/git/berlin-gtfs-rt-server/lib/gtfs-info.js
stops
routes
trip headsigns
unrecognized value "on;" for "ON_ERROR_STOP": Boolean expected
BEGIN
CREATE TABLE

COPY 579515
CREATE INDEX
...

Cheers!

[derhuerst]

Have you ever noticed the unrecognized value "on;" for "ON_ERROR_STOP": Boolean expected feedback […]?

Yes, I have! I assume it is caused by this line in gtfs-via-postgres (a dependency of this project):

https://github.com/public-transport/gtfs-via-postgres/blob/4.9.0/index.js#L156

I'd be happy to get it to disappear, especially since the message seems to indicate that the ON_ERROR_STOP setting is not getting activated. 🤔

But I can't reproduce it locally using psql from the Homebrew PostgreSQL v14 package.