Why is this script doing anything asynchronously in the first place? Were you suggesting that this behavior is unavoidable in node? (WTF?) On Thu, May 25, 2017 at 11:57 AM Jake <jake(a)spaz.org> wrote: > > there is a bad bug in the script we use to add keycards to the access > control > system, called grant_access_to_last_attempt.js > > that script should make the filesystem read-write before attempting to add > the > record, but since it's written in node, there is no sequentiality to it at > all > and the dinosaurs coexist with the humans like in The Flintstones and > nothing > gets done. > > I asked Corey for help and he made some changes to the script but it > didn't > work. If anyone wants to fix this it would be a good idea. > > Presently, when someone tries to use this script to add someone to the > access > system, it asks all the questions and lets you fill them in and then it > fails. > You have to run rwroot to make the filesystem writeable and try again, > typing > in everything again. > > and then it leaves the filesystem in a writeable state, because people > ignore > the warning on the prompt saying to run roroot to put it back, and > eventually > it will ruin the disk on the front door computer. > > here is the github pull request, that didn't work. > > https://github.com/sudoroom/doorjam/pull/7 > _______________________________________________ > access mailing list > access(a)lists.sudoroom.org > https://sudoroom.org/lists/listinfo/access