Failed to add edge detection with latest push #71
Labels
No labels
UserStory
bug
duplicate
enhancement
help wanted
hw task
invalid
question
refactoring
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mattzz/halloween#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I just saw this, too.
Should be fixed with latest commit
b12797209dActually my bug was a bit different:
This is fixed in commit
b12797209dHmm, I thought this came from dungeon not being in the hosts list - but it was already. Any idea? Still is the same with the recent code. Running in debug mode.
Might be related to port 11 being assigned to something else? See: https://www.raspberrypi.org/forums/viewtopic.php?t=205327
This issue does not seem to happen on nginx...
Are you using a RPi 3B+?
Yes: Pi 3 Modell B+
I'm seeing some issues like this in combination with the rpi3b+ on the interwebs.
Check out if it still happens with
sudo ./pumpkin.pyIf yes, it's related to root rights. (I think the nginx master process is running as root.)
Still odd...
Strange:
sudodoesn't make a difference.On demon it doesn't even run on deployed on nginx:
It works on nginx on dungeon but not in debug mode (also with sudo):
After reading this comment, I tried pin 37 on demon and with that change it works in nginx (not on command line still): https://www.raspberrypi.org/forums/viewtopic.php?t=205327#p1273043
Dungeon and demon are identical RPi. On dungeon it works with pin 11 (at least in nginx) while on demon it doesn't (but works with pin 37).
I found some differences in the apt packages: Demon was older. So I'm performing an apt-get update and upgrade now...
After the update it also runs on demon in nginx with pin 11.
Changed from bug to "help wanted" because this issue doesn't seem to be related with a bug in the application itself.
The fucker is back: On demon in nginx for pin 11 and 37!
After reboot it's ok in pin 37..
sudo rebootdoes the trick if it appears after a restart.