the real issue is not that the user id changed, though that may cause issues. The real issue is that when the file permissions don't match (which in this case are on the travis user id 2000 and node user id 1000) then yaktor.sh#L9 copies the env in to .env and then attempts to source it at yaktor.sh#L24 where apparently the 4th import statement tries to import a key (with c++ in the name???) and fails.
The lasting fix something like filtering bad names from env or don't copy it if a .env file exists.
the real issue is not that the user id changed, though that may cause issues. The real issue is that when the file permissions don't match (which in this case are on the travis user id
2000and node user id1000) then yaktor.sh#L9 copies theenvin to.envand then attempts tosourceit at yaktor.sh#L24 where apparently the 4th import statement tries to import a key (withc++in the name???) and fails.The lasting fix something like filtering bad names from env or don't copy it if a .env file exists.
See https://travis-ci.org/SciSpike/yaktor/builds/339139267#L564