search

Hoektronics / BotQueue

Control your 3D printer(s) through the Internet.
https://www.botqueue.com
GNU General Public License v3.0
167 stars 41 forks source link

failed to complete job #1067 #36

Closed hoeken closed 11 years ago

hoeken commented 11 years ago

not sure what happened... need to look into. this was on job finish?

[2013-03-06 21:12:33,167] ERROR: XiaoKong: Error notifying mothership: You cannot complete this job. Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 337, in processJob raise Exception("Error notifying mothership: %s" % result['error']) Exception: Error notifying mothership: You cannot complete this job. [2013-03-06 21:12:33,170] ERROR: XiaoKong: Error mode: Error notifying mothership: You cannot complete this job. [2013-03-06 21:12:33,170] DEBUG: Calling https://www.botqueue.com/api/v1/endpoint [2013-03-06 21:12:54,111] ERROR: XiaoKong: The read operation timed out Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 62, in errorMode self.dropJob(error) File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 368, in dropJob result = self.api.dropJob(self.data['job']['id'], error) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 209, in dropJob return self.apiCall('dropjob', {'job_id' : job_id, 'error' : error}) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 76, in apiCall raise NetworkError(str(ex)) NetworkError: The read operation timed out [2013-03-06 21:12:54,115] INFO: XiaoKong: Setting bot status as error. [2013-03-06 21:12:54,115] DEBUG: Calling https://www.botqueue.com/api/v1/endpoint [2013-03-06 21:13:05,384] ERROR: XiaoKong: The read operation timed out Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 140, in run self.processJob() File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 343, in processJob self.errorMode(ex) File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 68, in errorMode result = self.api.updateBotInfo({'bot_id' : self.data['id'], 'status' : 'error', 'error_text' : error}) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 248, in updateBotInfo return self.apiCall('updatebot', data) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 76, in apiCall raise NetworkError(str(ex)) NetworkError: The read operation timed out [2013-03-06 21:13:05,385] ERROR: The read operation timed out Traceback (most recent call last): File "bumblebee.py", line 40, in loadbot worker.run(); File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 160, in run raise ex NetworkError: The read operation timed out

Jnesselr commented 11 years ago

Wait, so your bot couldn't connect to the internet, so it decided to drop the job. It then changed its error mode which was reported to the site, but that also failed for the same reason.

Wow. Definitely feeling like a bumblebee rewrite. On Mar 7, 2013 11:33 PM, "Zach Hoeken" notifications@github.com wrote:

not sure what happened... need to look into. this was on job finish?

[2013-03-06 21:12:33,167] ERROR: XiaoKong: Error notifying mothership: You cannot complete this job. Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 337, in processJob raise Exception("Error notifying mothership: %s" % result['error']) Exception: Error notifying mothership: You cannot complete this job. [2013-03-06 21:12:33,170] ERROR: XiaoKong: Error mode: Error notifying mothership: You cannot complete this job. [2013-03-06 21:12:33,170] DEBUG: Calling https://www.botqueue.com/api/v1/endpoint [2013-03-06 21:12:54,111] ERROR: XiaoKong: The read operation timed out Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 62, in errorMode self.dropJob(error) File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 368, in dropJob result = self.api.dropJob(self.data['job']['id'], error) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 209, in dropJob return self.apiCall('dropjob', {'job_id' : job_id, 'error' : error}) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 76, in apiCall raise NetworkError(str(ex)) NetworkError: The read operation timed out [2013-03-06 21:12:54,115] INFO: XiaoKong: Setting bot status as error. [2013-03-06 21:12:54,115] DEBUG: Calling https://www.botqueue.com/api/v1/endpoint [2013-03-06 21:13:05,384] ERROR: XiaoKong: The read operation timed out Traceback (most recent call last): File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 140, in run self.processJob() File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 343, in processJob self.errorMode(ex) File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 68, in errorMode result = self.api.updateBotInfo({'bot_id' : self.data['id'], 'status' : 'error', 'error_text' : error}) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 248, in updateBotInfo return self.apiCall('updatebot', data) File "/Users/hoeken/github/BotQueue/bumblebee/botqueueapi.py", line 76, in apiCall raise NetworkError(str(ex)) NetworkError: The read operation timed out [2013-03-06 21:13:05,385] ERROR: The read operation timed out Traceback (most recent call last): File "bumblebee.py", line 40, in loadbot worker.run(); File "/Users/hoeken/github/BotQueue/bumblebee/workerbee.py", line 160, in run raise ex NetworkError: The read operation timed out

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36 .

hughht5 commented 11 years ago

I got the exact same thing the whole of last night.

hoeken commented 11 years ago

its the weekend soon, so i'll find this and fix it.

just for the record - a re-write of botqueue is not on the books. thats the quickest way to kill a project. constant, incremental improvement is the name of the game and bug fixing is a major part of it.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Fri, Mar 8, 2013 at 5:45 PM, Hugh Halford-Thompson < notifications@github.com> wrote:

I got the exact same thing the whole of last night.

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611434 .

Jnesselr commented 11 years ago

Constant incremental improvement works for something that is well designed. I contend that bumblebee is not well designed. And actually, many times a rewrite will be necessary.

Also, I believe that you read bumblebee as BotQueue which isn't correct. I just want to improve bumblebee. its the weekend soon, so i'll find this and fix it.

just for the record - a re-write of botqueue is not on the books. thats the quickest way to kill a project. constant, incremental improvement is the name of the game and bug fixing is a major part of it.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Fri, Mar 8, 2013 at 5:45 PM, Hugh Halford-Thompson < notifications@github.com> wrote:

I got the exact same thing the whole of last night.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611434> .

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611509 .

hoeken commented 11 years ago

We may have a slight misunderstanding of rewrite. In my experience this means tossing out all the working code because of a bit of code that is not working and means spending months re-inventing the wheel and ending up with code that is broken in different ways.

Feel free to do it, but I'd rather just fix the parts that aren't working - which doesn't involve throwing out the majority of the code that does work.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Sun, Mar 10, 2013 at 10:38 AM, Jnesselr notifications@github.com wrote:

Constant incremental improvement works for something that is well designed. I contend that bumblebee is not well designed. And actually, many times a rewrite will be necessary.

Also, I believe that you read bumblebee as BotQueue which isn't correct. I just want to improve bumblebee. its the weekend soon, so i'll find this and fix it.

just for the record - a re-write of botqueue is not on the books. thats the quickest way to kill a project. constant, incremental improvement is the name of the game and bug fixing is a major part of it.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Fri, Mar 8, 2013 at 5:45 PM, Hugh Halford-Thompson < notifications@github.com> wrote:

I got the exact same thing the whole of last night.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611434> .

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611509> .

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14675127 .

Jnesselr commented 11 years ago

True, which is why it's important to write it correctly the first time. That way, it's highly expandable. I'll work on it in a separate branch and send a pull request when it's done. On Mar 10, 2013 10:57 PM, "Zach Hoeken" notifications@github.com wrote:

We may have a slight misunderstanding of rewrite. In my experience this means tossing out all the working code because of a bit of code that is not working and means spending months re-inventing the wheel and ending up with code that is broken in different ways.

Feel free to do it, but I'd rather just fix the parts that aren't working

which doesn't involve throwing out the majority of the code that does work.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Sun, Mar 10, 2013 at 10:38 AM, Jnesselr notifications@github.com wrote:

Constant incremental improvement works for something that is well designed. I contend that bumblebee is not well designed. And actually, many times a rewrite will be necessary.

Also, I believe that you read bumblebee as BotQueue which isn't correct. I just want to improve bumblebee. its the weekend soon, so i'll find this and fix it.

just for the record - a re-write of botqueue is not on the books. thats the quickest way to kill a project. constant, incremental improvement is the name of the game and bug fixing is a major part of it.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Fri, Mar 8, 2013 at 5:45 PM, Hugh Halford-Thompson < notifications@github.com> wrote:

I got the exact same thing the whole of last night.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611434>

.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611509>

.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14675127> .

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14695629 .

hoeken commented 11 years ago

That works for me. Thats why the API is there - nice clean separation of client and server means this sort of thing is possible. Make sure you change your client ID string please. :)

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Mon, Mar 11, 2013 at 10:59 AM, Jnesselr notifications@github.com wrote:

True, which is why it's important to write it correctly the first time. That way, it's highly expandable. I'll work on it in a separate branch and send a pull request when it's done. On Mar 10, 2013 10:57 PM, "Zach Hoeken" notifications@github.com wrote:

We may have a slight misunderstanding of rewrite. In my experience this means tossing out all the working code because of a bit of code that is not working and means spending months re-inventing the wheel and ending up with code that is broken in different ways.

Feel free to do it, but I'd rather just fix the parts that aren't

working

which doesn't involve throwing out the majority of the code that does work.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Sun, Mar 10, 2013 at 10:38 AM, Jnesselr notifications@github.com wrote:

Constant incremental improvement works for something that is well designed. I contend that bumblebee is not well designed. And actually, many times a rewrite will be necessary.

Also, I believe that you read bumblebee as BotQueue which isn't correct. I just want to improve bumblebee. its the weekend soon, so i'll find this and fix it.

just for the record - a re-write of botqueue is not on the books. thats the quickest way to kill a project. constant, incremental improvement is the name of the game and bug fixing is a major part of it.

Zach Hoeken Smith

Work: www.haxlr8r.com Blog: www.hoektronics.com Twitter: @hoeken Skype: chilldude22 QQ: 1489598623 China: +86-186-8209-7069

On Fri, Mar 8, 2013 at 5:45 PM, Hugh Halford-Thompson < notifications@github.com> wrote:

I got the exact same thing the whole of last night.

— Reply to this email directly or view it on GitHub<

https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611434>

.

— Reply to this email directly or view it on GitHub<

https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14611509>

.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14675127>

.

— Reply to this email directly or view it on GitHub< https://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14695629> .

— Reply to this email directly or view it on GitHubhttps://github.com/Hoektronics/BotQueue/issues/36#issuecomment-14695672 .

hoeken commented 11 years ago

this has been fixed now.