Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 21:32
    gkellogg commented #393
  • Jan 31 10:29
    typhoon2099 commented #393
  • Jan 31 10:20
    typhoon2099 opened #393
  • Jan 29 19:14

    gkellogg on develop

    Guard against nil bindings in s… (compare)

  • Jan 29 02:10

    gkellogg on develop

    Have solution iterators also re… (compare)

  • Jan 29 00:59

    gkellogg on develop

    Fix check for variable in Patte… (compare)

  • Jan 29 00:38

    gkellogg on develop

    Add `Solutions#dup`. Add `existential` modifier to v… (compare)

  • Jan 26 23:12

    gkellogg on develop

    Dup components of a URI to avoi… Calculate pattern cost based on… (compare)

  • Jan 24 16:11
    coveralls commented #392
  • Jan 24 16:08

    gkellogg on develop

    Implement marshaling methods to… (compare)

  • Jan 24 16:08
    gkellogg closed #392
  • Jan 24 15:50
    cjcolvar opened #392
  • Jan 24 15:27
  • Jan 21 21:56

    gkellogg on develop

    Update Repository to remember s… (compare)

  • Jan 20 23:45

    gkellogg on develop

    Fix bug in NTriples::Reader.une… (compare)

  • Jan 20 00:12

    gkellogg on develop

    Change N-Triples literal output… (compare)

  • Jan 19 22:54

    gkellogg on develop

    Single quote (') was missing fr… (compare)

  • Jan 16 23:43

    gkellogg on develop

    Make query validation optional.… Better support for non-distingu… Test solutions bindings. (compare)

  • Jan 15 20:09
  • Jan 01 20:18

    gkellogg on 3.0.9

    (compare)

Thomas Johnson
@no-reply
it invalidates the MRI method cache every time Repository.new is called
Gregg Kellogg
@gkellogg
Can we just not do if self.class.equal?(RDF::Repository) && !respond_to?(Implementation)?
Or, maybe it could be done in #method_missing.
Thomas Johnson
@no-reply
the pass through could work; no idea if there are pitfalls to that, though
would want to make sure not to forget #respond_to_missing
Thomas Johnson
@no-reply
we'd also have to replace the logic in Implementation.extend_object somehow
Gregg Kellogg
@gkellogg
Looks like Rack doesn't support Ruby < 2.2 anymore (see phusion/passenger#1710). This is a development dependency for many gems. We should either lock in an earlier version, or obsolete Ruby < 2.2.
Thomas Johnson
@no-reply
i'm inclined toward obsoleting Ruby 2.2...
oh goodness. I hadn't seen that Rack 2.0 was released
i guess we probably owe some work there
is there release documentation anywhere? the latest news on the Rack website dates from early 2013
Gregg Kellogg
@gkellogg
Travis JRuby failures are pretty annoying. Looks like memory management changes are biting us (see this. Probably easiest to simply mark JRuby in the allow_failures matrix for all gems. See https://travis-ci.org/ruby-rdf/rdf-aggregate-repo/jobs/151974020, for example.
Gregg Kellogg
@gkellogg
Also https://travis-ci.org/ruby-rdf/rdf/jobs/151973839 fails with a similar out-of-memory error.
Thomas Johnson
@no-reply
yeah, ouch.
Thomas Johnson
@no-reply
@gkellogg looks like we never released rdf 2.1 D:
Gregg Kellogg
@gkellogg
Hmm, I thought I had done that. Released now.
Thomas Johnson
@no-reply
thanks!
Thomas Johnson
@no-reply
hmmmm... i think the default #query_pattern implementation is broken... gist incoming
Thomas Johnson
@no-reply
sorry the initial gist is slightly misleading
i've updated it... the issue seems to be RDF::Query::Pattern.new(nil, nil, nil, graph_name: false) === RDF::Statement.new(:s, :p, :o, graph_name: :blah)
which causes default #query_pattern to fail the tests for Queryable
Thomas Johnson
@no-reply
i have a fix at https://github.com/ruby-rdf/rdf/compare/feature/dataset, but it still needs a refactor
i'm tempted to implement a DefaultGraph singleton
Thomas Johnson
@no-reply
@gkellogg: ping
Gregg Kellogg
@gkellogg
Hi
Should we jump on Skype?
Thomas Johnson
@no-reply
yeah, probably
Gregg Kellogg
@gkellogg
Call me when you’re ready
Thomas Johnson
@no-reply
I'll probably cut a 2.0.4 release in the next few days, and continue to backport any simple bugfixes or non-breaking performance improvements for at least a few weeks, releasing when convenient
Gregg Kellogg
@gkellogg
Okay, I’m working on vocabs update for ontology for 2.1.1. Is it worth backporting too?
Thomas Johnson
@no-reply
maybe? I'm not excited by the idea of maintaining multiple branches of the vocabs, though...
i think let's punt it? if people are clamoring for it, or someone is willing to maintain a Ruby 2.1 compatible branch, then we can revisit
It's probably good practice to pin vocabs to a tiny version in production applications, anyway
Gregg Kellogg
@gkellogg
If it ports easily (which it should), no harm in including it in 2.0.4. Should know later today or tomorrow.
Thomas Johnson
@no-reply
:ok_hand:
Gregg Kellogg
@gkellogg
@no-reply: we should push out a new release soon. I have changes that are required to update other gems. Anything else to get in?
Thomas Johnson
@no-reply
@gkellogg sorry for the slow response; I've been down with the flu
I'm :+1: on a release. If we're willing to wait until friday, I'll finish up ruby-rdf/rdf#318.
Gregg Kellogg
@gkellogg
Sounds good, no rush. Do you think this should be 2.2.0? or 2.1.x?
Thomas Johnson
@no-reply
looks like we have several new features. Seems to justify 2.2.0.
Gregg Kellogg
@gkellogg
no-reply: Perhaps 2.2.0 is necessary, but if all changes are backwards-compatible, maybe not.
Thomas Johnson
@no-reply
@gkellogg can't make a call this morning, sorry. I'm transitioning to school schedule, and my calendar is odd this week. Should be able to attend at this time in future weeks for the foreseeable future.
Alex Norton
@alexnorton
hi there, is it possible to pass in a default set of prefixes when parsing and executing a SPARQL query?
(if this isn't best place to seek help feel free to point me elsewhere)
Gregg Kellogg
@gkellogg
Pushing out 3.0 versions for release later today.
Stian Soiland-Reyes
@stain
Congrats on the new release!
Gregg Kellogg
@gkellogg
stain: thanks! Even with few changes, coordinating a new major release is quite a bit of work.