Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Support] AttributeError: 'CommandTrigger' object has no attribute 'logger' #715

Closed
twproject opened this issue Jan 12, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@twproject
Copy link

commented Jan 12, 2015

I'm using Devel version of Octoprint on a OctoPi enviroment
Version: 1.2.0-dev-386-g5a3df19 (devel branch)

On config.yaml i created following example an events trigger but it don't work and report errors:

config.yaml

events:
  enabled: true
  subscriptions:
  - event: Connected
    command:
    - M115
    - M117 printer connected!
    type: gcode

log:

2015-01-12 09:10:57,066 - octoprint.events - ERROR - Got an exception while sending event Connected (Payload: {'baudrate': 250000, 'port': u'/dev/ttyACM0'}) to <bound method CommandTrigger.eventCallback of <octoprint.events.CommandTrigger object at 0x28d35b0>>
Traceback (most recent call last):
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint-1.2.0_dev_386_g5a3df19-py2.7.egg/octoprint/events.py", line 121, in _work
    listener(event, payload)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint-1.2.0_dev_386_g5a3df19-py2.7.egg/octoprint/events.py", line 282, in eventCallback
    self.executeCommand(processedCommand, commandType)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint-1.2.0_dev_386_g5a3df19-py2.7.egg/octoprint/events.py", line 290, in executeCommand
    self._executeGcodeCommand(command)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/OctoPrint-1.2.0_dev_386_g5a3df19-py2.7.egg/octoprint/events.py", line 311, in _executeGcodeCommand
    self.logger.debug("Executing GCode commands: %r" % command)
AttributeError: 'CommandTrigger' object has no attribute 'logger'

foosel added a commit that referenced this issue Jan 12, 2015

@foosel

This comment has been minimized.

Copy link
Owner

commented Jan 12, 2015

Should be fixed in devel

@foosel foosel closed this Jan 12, 2015

@twproject

This comment has been minimized.

Copy link
Author

commented Jan 14, 2015

now it works fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.