bendiken changed the topic of #ruby-rdf to: Ruby RDF & SPARQL chat. | https://github.com/ruby-rdf/rdf | Gitter: https://gitter.im/ruby-rdf/rdf | Mailing List: https://lists.w3.org/Archives/Public/public-rdf-ruby | Twitter: @Gkellogg @bendiken @no_reply | Use http://pastebin.com for code/graph snippets. Also join #swig for general linked data and semantic web chatter. Public channel log at http://irclog.whitequark.org/ruby-rdf/
bendiken has quit []
gkellogg has quit [Quit: gkellogg]
bendiken has joined #ruby-rdf
gkellogg has joined #ruby-rdf
tjohnson has joined #ruby-rdf
<tjohnson> gkellogg: I have an odd turtle error for you: https://gist.github.com/no-reply/d8bd0d00e9543dc2a48b
<tjohnson> getting the error in that file on a """...""" style long string
<tjohnson> the turtle in parses.txt/errors.txt does what the filename says
<gkellogg> Your gists are a bit hard to make out!
<tjohnson> the only difference between the strings are the presence of the letter 'x' between two spaces
<tjohnson> gkellogg: i wanted to give you something you could copy-paste in to repeat the issue
<tjohnson> i'll post some formatted output
<gkellogg> Could you re-post fails.txt and parses.txt without the embedded newlines?
<gkellogg> I think there’s a a W3C hosted turtle parser; you might run it by there. My guess is that you’re running into an issue with the syntax, rather than a parser bug.
<tjohnson> i added formatted turtle
<gkellogg> Okay, looks like a tokenizer issue, then.
<gkellogg> Probably running into a buffer-boundary corner case. It uses a streaming string reader which needs to re-fill when it runs out of characters, and may be missing something in this case. That’s in the ebnf gem.
<tjohnson> ah...
<tjohnson> yeah, looks like it's something about the length of this particular line that's making the difference between parsing and not
<tjohnson> not the `x` or its location in the line, specifically
<tjohnson> here's where I am: https://gist.github.com/no-reply/cb2ced2cc5762964319a#file-my-life-txt-L2758 Getting ready to pop open the lexer at the point of problems.
<tjohnson> hopefully I can spot the issue
<gkellogg> It’s likely somewhere in here, or the environment that calls it https://github.com/gkellogg/ebnf/blob/master/lib/ebnf/ll1/scanner.rb#L101-L109