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

Following up on Issue #33 #51

Closed
chi99y opened this issue Oct 26, 2012 · 3 comments
Closed

Following up on Issue #33 #51

chi99y opened this issue Oct 26, 2012 · 3 comments

Comments

@chi99y
Copy link

chi99y commented Oct 26, 2012

Hi,

I'm a senior developer with HBO and would like to follow up on an issue that was posted by a colleague of mine a while back in issue #33.

The application can be accessed here:

http://www.hbogo.com/activate/

We're puzzled why the application works on all other browsers but the 64bit version of IE8. The error message we're getting has been reported on Issue #33 here. Do you guys have any ideas what's preventing the application from functioning properly?

Thanks.

Regards,
Chin S. Huang
Senior Developer
HBO

@briancavalier
Copy link
Member

Hi @chi99y, thanks for following up. Just want to make sure I understand correctly, since it sounded like in #33, the error message didn't actually cause a problem--i.e. it was annoying, but didn't break the application. Is that true, or is it actually causing the application to fail?

That particular error message appears to be coming from RequireJS. I know that older versions (1.x) of RequireJS used a "last ditch" timeout (the waitSeconds config option) that would cause all module loading to halt if any module exceeded the timeout.

Ok, that said, a few questions:

  1. What version of RequireJS are you using?
  2. Have you tried increasing RequireJS's waitSeconds option to see if that helps or changes the outcome in any way?
  3. Are you still seeing the error only after building your application? Or are you also seeing it in an unbuilt, development, version?
  4. If you are building, what build tool are you using? r.js? what version?
  5. I noticed a 404 error when trying to load the file activation_config.js. I figure that's not related, but just wanted to check with you.
  6. Is there any more info about the error that you can provide?

Also, pinging @unscriptable, who knows more about the AMD loading side of things.

Let us know, and we'll do our best to help you figure it out!

@chi99y
Copy link
Author

chi99y commented Oct 27, 2012

Hi Brian,

Thank you for the prompt reply. I inherited this project from my colleague
who no longer works at HBO so I'm not totally familiar with the entire
codebase. I've read through your email and will look into the points
you've made. I will also involve another member of my team in looking into
this matter on Monday. I will get get back to you regarding the questions
you've listed. Hopefully, we can get to the bottom of this issue.

Thanks again. You'll be hearing from me next week.

Regards,
Chin S. Huang

On Fri, Oct 26, 2012 at 9:34 PM, Brian Cavalier notifications@github.comwrote:

Hi @chi99y https://github.com/chi99y, thanks for following up. Just
want to make sure I understand correctly, since it sounded like in #33#33,
the error message didn't actually cause a problem--i.e. it was annoying,
but didn't break the application. Is that true, or is it actually causing
the application to fail?

That particular error message appears to be coming from RequireJS. I know
that older versions (1.x) of RequireJS used a "last ditch" timeout (the
waitSeconds config option) that would cause all module loading to halt if
any module exceeded the timeout.

Ok, that said, a few questions:

  1. What version of RequireJS are you using?
  2. Have you tried increasing RequireJS's waitSeconds option to see if
    that helps or changes the outcome in any way?
  3. Are you still seeing the error only after building your
    application? Or are you also seeing it in an unbuilt, development, version?
  4. If you are building, what build tool are you using? r.js? what
    version?
  5. I noticed a 404 error when trying to load the file
    activation_config.js. I figure that's not related, but just wanted to
    check with you.
  6. Is there any more info about the error that you can provide?

Also, pinging @unscriptable https://github.com/unscriptable, who knows
more about the AMD loading side of things.

Let us know, and we'll do our best to help you figure it out!


Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-9831518.

@briancavalier
Copy link
Member

Hi @chi99y, just a ping to see if this is still an open issue for you. If it is, please reopen the issue and let us know how we can help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants