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

REXML::ParseException: #<REXML::ParseException: Missing end tag for 'meta' ﴾got "head"﴿ #318

Closed
akannur opened this issue Jan 26, 2017 · 11 comments
Assignees

Comments

@akannur
Copy link

akannur commented Jan 26, 2017

...
Missing end tag for 'meta' ﴾got "head"﴿
Line: 27
Position: 1590
Last 80 unconsumed characters:
Line: 27
Position: 1590
Last 80 unconsumed characters:
/opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/xml/rexml.rb:7:in new' /opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/xml/rexml.rb:7:in initialize'
/opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/xml.rb:55:in initialize' /opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/api/errors.rb:49:in new'
/opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/api/errors.rb:49:in xml' /opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/api/errors.rb:34:in description'
/opt/app/ums/shared/bundle/ruby/1.9.1/gems/recurly‐2.7.3/lib/recurly/api/errors.rb:19:in to_s' /opt/app/ums/releases/20161215140922/lib/tasks/batch_job_line_item.rake:39:in message'
/opt/app/ums/releases/20161215140922/lib/tasks/batch_job_line_item.rake:39:in rescue in block ﴾4 levels﴿ in <top ﴾required﴿>' /opt/app/ums/releases/20161215140922/lib/tasks/batch_job_line_item.rake:16:in block ﴾4 levels

@bhelx
Copy link
Contributor

bhelx commented Jan 26, 2017

@akannur This error is coming from the ruby client so this issue may belong in this repo: https://github.com/recurly/recurly-client-ruby

I'd need to see the code that is causing this to be sure, but it looks like it's maybe getting some kind of HTML page and expecting XML. Could you show the code which generated this error?

@bhelx bhelx self-assigned this Jan 26, 2017
@akannur
Copy link
Author

akannur commented Jan 26, 2017 via email

@bhelx
Copy link
Contributor

bhelx commented Jan 26, 2017

@akannur I'm a bit confused as to where the problem is in this code. Could you provide some code to help me reproduce the problem? Or maybe you can point out where in this code the problem is occurring.

@bhelx
Copy link
Contributor

bhelx commented Jan 26, 2017

@akannur If it's something you aren't able to reproduce, it might be a hiccup 502 error that cloudflare is giving you. I think because cloudflare is sending back html and the xml parser is exploding it is obscuring the fact that this is a 502 error.

If this turns out to be the case I will change the ruby client to have a clearer error message.

@akannur
Copy link
Author

akannur commented Jan 26, 2017 via email

@bhelx
Copy link
Contributor

bhelx commented Jan 26, 2017

@akannur I'm still not certain that it's not another problem. Were you able to reproduce it or does it seem like it was a one off thing?

@akannur
Copy link
Author

akannur commented Jan 27, 2017 via email

@bhelx
Copy link
Contributor

bhelx commented Jan 27, 2017

@akannur I'm closing this as it belongs in the ruby client's repo. You can follow along here now: recurly/recurly-client-ruby#296

@bhelx bhelx closed this as completed Jan 27, 2017
@akannur
Copy link
Author

akannur commented Jan 27, 2017 via email

@bhelx
Copy link
Contributor

bhelx commented Jan 27, 2017

@akannur I'm going to do a release today of version 2.7.6 which will include this change.

@akannur
Copy link
Author

akannur commented Jan 27, 2017 via email

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