Chomper never unblocks, requires reboot

[alienbogart]

• Do you want to request a feature or report a bug?

Report a bug.

• What is the current behavior?

I ran chomper 60 to block me for an hour. Maybe because it was close to midnight, when it came to "release" time chomper told me it would unblock things at 23:59 of today. sudo make reset gave me this message, so I had to reboot:

sudo env PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/sbin /home/mrbig/.local/share/virtualenvs/chomper-tBlCykeL/bin/python3.6m /home/mrbig/chomper/chomper/reset.py
env: ‘/home/mrbig/.local/share/virtualenvs/chomper-tBlCykeL/bin/python3.6m’: No such file or directory
Makefile:23: recipe for target 'reset' failed
make: *** [reset] Error 127

• What is the expected behavior?

Block me for 1 hour.

Runtime Environment

• Chomper Release or Commit: e.g. 0.2.0
• Browser: Google Chrome 71.0.3578.98
• Operating System: MX Linux 17
• My dotfiles

Update

Just tried again. Ran chomper coding 3 At 00:21. It's 00:28 and both Chrome and Firefox are giving me the following message:

Website blocked by Chomper! The coding rule is in effect until 2019-01-05 23:59:00.

Now I have to reboot again to send you this update :P

Incidentally, chomper did not create a hidden directory like in the docs, but a ~/chomper. Maybe that's relevant.

Update 2

Tested again with a blocklist (so I don't need to reboot every single time!) and the results were the same. I created the rule:

testing:
  - block_type:
      - blacklist
  - addresses:
      - lifehacker.com

And ran chomper testing 2. 10 minutes after the deadline, the domain remains inaccessible:

Website blocked by Chomper! The testing rule is in effect until 2019-01-06 00:59:00.

[respatialized]

I had this issue as well. I compared the directories created by the virtualenv installer script and the dir specified in the makefile. The virtualenv installer creates the path ~/.local/share/virtualenvs/chomper-V35YB4cc/python3.6 and the makefile (through the $INTERPRETER variable) refers to /.local/share/virtualenvs/chomperV35YB4cc/python3.6m.

Removing "m" from {$INTERPRETER}python3.6 allowed the reset to work properly. I'm not sure if this is the desired behavior, though - should the "m" be affixed to that path?

[alienbogart]

At this point, I must respectfully ask if this project is being actively maintained. The last commit was on Apr 25, 2018, the newest answer by @aniketpanjwani was on May 13, 2018 and the support message I posted on Gitter on Jan 06 found no response. It seems like a useful tool, but I cannot use it in its current state. Maybe @aniketpanjwani should put a notice on the readme about that.

@respatialized thank you for the tip, but I have exhausted the allotted time in my schedule for making this program work. I'll just wait for an "official" solution.