Add mission timeouts

[jpanikulam]

No description provided.

[mattlangford]

I can include this in my next PR

[jpanikulam]

Perfect

[jpanikulam]

@mattlangford Did we ever land on this?

[mattlangford]

No reply from @forrestv yet. What do?

[jpanikulam]

Have you tried emailing god-president Trump?

[jpanikulam]

I couldn't find the timeout code on your fork, did you remove it? I was going to clone and try

[mattlangford]

I did remove it. I can add it back tonight.

[forrestv]

No reply from @forrestv yet. What do?

Huh? Not sure what you mean. Are you waiting on me fixing the spurious traceback that is printed in the case you emailed me? I thought it wasn't blocking any progress..?

[mattlangford]

Hmm I guess you're right. It doesn't actually break anything, no reason to fret over it.

[forrestv]

Well, I'm definitely going to look into it. I just wanted to point out that
it shouldn't prevent you from advancing.

I'm still a bit confused, though: that issue you showed me, I wonder why I
never saw it before when I was writing missions... From the script you
showed me, it didn't look like you were doing anything unusual... I have to
try to replicate it locally.

FYI, also, I'm likely going to redo the txros action API. It's a mess right
now.

On Wed, May 18, 2016 at 9:47 AM, mattlangford notifications@github.com
wrote:

Hmm I guess you're right. It doesn't actually break anything, no reason to
fret over it.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#113 (comment)

[mattlangford]

@jpanikulam, have you tried running it yet? I wonder if it's just a weird issue on my machine. I haven't ran it anywhere else.

Happy birthday by the way Forrest

[kev-the-dev]

Will be done via #320