virtualization code bug #2 about pyretic

[monsanto]

I of course did verify that example before closing the last ticket, pingall worked fine just as it works fine now. I cannot reproduce your problem. Can you give me some more information? That error doesn't even make sense to me, is the function "all" suggested to be a module? Or is it the eval attribute of some predicate that is now for some reason a module?

You are using my branch of POX, correct?

[joshreich]

I completely believe you, and had been really surprised when it broke when I tried to run it after your fix (and I agree w/ you that the error dump reported in issue #6 (3) seems bizarre). I am using your version of POX (master branch freshly pulled) and to make sure nothing had been subsequently busted, did a git reset --hard e7bfae9 (the commit where you pushed the fix closing #3).

I definitely think Jen is correct and that the best way for us to figure out what is going on is to schedule a hangout to look at this together as soon as possible.
What's the next time you'd be available to chat?

-Josh

On Jan 17, 2013, at 3:27 AM, Christopher Monsanto [email protected] wrote:

I of course did verify that example, pingall worked fine just as it works fine now. I cannot reproduce your problem.

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

[monsanto]

Any time tomorrow is fine with me (but the later the better). I'm afraid I screwed up my sleep schedule last night.

[joshreich]

Would 1PM work?

On Jan 17, 2013, at 5:03 PM, Christopher Monsanto [email protected] wrote:

Any time tomorrow is fine with me (but the later the better). I'm afraid I screwed up my sleep schedule last night.

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

[monsanto]

Sure lets do that

[joshreich]

Just saw this, not sure how I missed it. Sorry for the redundancy query in my other email.

On Jan 17, 2013, at 5:14 PM, Christopher Monsanto [email protected] wrote:

Sure lets do that

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