Closed adrhine closed 2 years ago
what are the files you have in /events/
?
/events/
contains all of the normal .js files you would expect from source, as well as the .wh..wh..opq
file on the heroku container. I'm just using the same Dockerfile
specified in source, and locally I don't see the whiteout file present.
But the presence of the .wh..wh..opq
file throws the errors above you see in the logs and produces a fatal exception. Hopefully this makes sense - I can try to provide more info if it helps
I am running my own Heroku project, and taking the source code here + following the documentation I was able to complete a Heroku deploy pretty easily. Only, I found a single problem that was occurring whenever I would attempt to run (using a worker dyno).
The logs weren't entirely clear what was happening, so I added a little more explicit logging and this is what I found was being output during startup:
A little more research on these
.wh..wh..opq
files lead me to this: https://github.com/opencontainers/image-spec/blob/main/layer.md#whiteoutsThis appears to be a result of the layering of images that Heroku steps through, that is then causing an issue when the bot attempts to iterate through the
/events/
/commands/
directories.Locally, I was able to reproduce the same issue by creating this file (or really any random file) in the
/events/
or/commands/
dirs and then starting the app. I made some quick hacky changes locally to get past this (confirm that the files within these directories end with .js before trying to process them), but I'd rather not have to maintain a fork going forward to get around this issue.I would be happy to open a suggestion PR if you agree this is something you would like to see changed for this project, but I'm assuming that my use-case is in the minority here so I understand if you do not want to make any changes to help with this issue.