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 [Ping timeout: 246 seconds]
gkellogg has quit [Quit: gkellogg]
bendiken has joined #ruby-rdf
gkellogg has joined #ruby-rdf
bendiken has quit []
terrellt has joined #ruby-rdf
<terrellt> gkellogg: Any changes in how fragment URIs are handled in 1.1.17? I'm getting stack traces in ActiveFedora when I'm using them
<gkellogg> This was a performance update, with no real functional changes. the schema.org vocabulary was updated, but no changes to URI.
<gkellogg> You guys might want to test against the develop branch, so you have a heads-up for pending changes. The performance updates have been in for a week or so.
<terrellt> In this case it wouldn't have come up, I'm only now adding a feature that uses them.
<gkellogg> The specs are a good place to look for expected behavior; there are extensive tests for fragment identifiers.
<terrellt> gkellogg: So I don't know if it's ActiveTriples, or some weird combination of factors, and I'm not sure what input is causing this, but it's this change: https://github.com/ruby-rdf/rdf/pull/213/files#diff-d8b3d406cfa5a91c317a8513a0c9fa0dR341
<terrellt> If I switch that back, no more stack trace. I should clarify too - it's a C-level stack trace
<terrellt> Give me a sec and I'll get the trace, but it's pretty gnarly
<gkellogg> Have you tried a different version of Ruby? Might be running into a Ruby bug, if it’s a C-level stack trace
<gkellogg> Those changes are all performance improvements suggested by https://github.com/JuanitoFatas/fast-ruby
<gkellogg> using the fasterer gem to identify.
<gkellogg> Does it just crash on 2.2? Is it also a 2.1 or 2.0 issue? Can you narrow it down to a specific use of yield vs block.call?
<terrellt> I'm not sure if I'll be able to narrow it down
<terrellt> I'm a few layers above RDF.rb at the moment
<gkellogg> I’ll make some changes on a branch for you to test with. Let you know soon.
<terrellt> It's 2.2 where it's crashing
<terrellt> I'll install some other versions
<gkellogg> Try the support/issue-216-yield-vs-block branch. I made just a single change, which may be the culprit. If not, there are more changes I can roll back, but I’d rather keep as much of this as we can.
<gkellogg> AFK for a while.
<terrellt> gkellogg: Confirmed fixed in 2.3.0-dev
<terrellt> I'll try that
<terrellt> gkellogg: Ah, yeah, that's what I had done locally. That also fixes it.
gkellogg has quit [Quit: gkellogg]
gkellogg has joined #ruby-rdf
<gkellogg> terrelit: Released in 1.1.17.1.