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

Slicing failed #1884

Closed
gyrex opened this issue Apr 25, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@gyrex
Copy link

commented Apr 25, 2017

Hi guys,

I'm having some issues with octopi slicing. It used to slice ok but now it won't slice anything, including previously sliced objects. For this particular print I was trying to slice 3DBenchy.The error I'm getting via the GUI is:

Slicing failed
Could not slice Spool_Holder_Left.STL to Spool_Holder_Left.gco: Unknown error, please consult the log file

Log file:

2017-04-25 02:50:12,690 - octoprint.plugins.cura - ERROR - Could not slice via Cura, got an unknown error
Traceback (most recent call last):
File "/home/pi/oprint/lib/python2.7/site-packages/OctoPrint-1.3.2-py2.7.egg/octoprint/plugins/cura/init.py", line 296, in do_slice
self._logger.info(u"Running %r in %s" % (" ".join(args), working_dir))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 334: ordinal not in range(128)

Any ideas? In the meantime, I'll slice in Cura on my desktop.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented Apr 25, 2017

Hi @gyrex,

It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).

If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.

Please do not abuse the bug tracker as a support forum - if you have a question or otherwise need some kind of help or support refer to the Mailinglist or the G+ Community instead of here.

Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.

I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2017-05-09 13:00 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.

foosel added a commit that referenced this issue May 2, 2017

Fix some potential encoding issues
Might be a fix for #1884, can't be confirmed though, ticket is
incomplete.
@foosel

This comment has been minimized.

Copy link
Owner

commented May 10, 2017

Might be fixed by the above commit, impossible to confirm though since you never provided all of the requested information, incl. a file with which to reproduce this.

Commit is available on the maintenance branch, soon devel and will be part of the upcoming 1.3.3 release.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented May 18, 2017

Since apparently some of the required information is still missing, I'm closing this now, sorry. Feel free to request a reopen of this or create a new issue once you can provide all required information.
This is nothing personal. Thank you for your collaboration.

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.