Menu
▾
▴
dotnetrdf-develop — Developer Discussion and Feature Request
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(11) |
Mar
(17) |
Apr
(12) |
May
(2) |
Jun
(20) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(5) |
| 2011 |
Jan
(4) |
Feb
(1) |
Mar
(2) |
Apr
(2) |
May
(5) |
Jun
|
Jul
(12) |
Aug
(4) |
Sep
(5) |
Oct
(1) |
Nov
(38) |
Dec
(27) |
| 2012 |
Jan
(46) |
Feb
(182) |
Mar
(83) |
Apr
(22) |
May
(68) |
Jun
(47) |
Jul
(135) |
Aug
(84) |
Sep
(57) |
Oct
(45) |
Nov
(27) |
Dec
(61) |
| 2013 |
Jan
(59) |
Feb
(78) |
Mar
(66) |
Apr
(107) |
May
(27) |
Jun
(56) |
Jul
(53) |
Aug
(3) |
Sep
(19) |
Oct
(41) |
Nov
(44) |
Dec
(54) |
| 2014 |
Jan
(49) |
Feb
(72) |
Mar
(22) |
Apr
(41) |
May
(63) |
Jun
(27) |
Jul
(45) |
Aug
(12) |
Sep
(3) |
Oct
(8) |
Nov
(27) |
Dec
(16) |
| 2015 |
Jan
(3) |
Feb
(20) |
Mar
(6) |
Apr
(4) |
May
(15) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
(16) |
May
(9) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <tr...@do...> - 2013-04-15 21:26:10
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Add Silverlight assembly caching support</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>Unassigned</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Build, Release and Testing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Low</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A user requested via a blog comment that we support Silverlight Assembly caching to improve performance of Silverlight applications that use dotNetRDF - see <a href="http://msdn.microsoft.com/en-us/library/dd833069(v=vs.95).aspx">http://msdn.microsoft.com/en-us/library/dd833069(v=vs.95).aspx</a> for relevant MSDN documentation</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=348" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=348</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Tomasz P. <tom...@gm...> - 2013-04-15 21:15:26
|
I have got it ready really and it will take you quite some time. Please have a look at CORE-347 branch. I will write more tomorrow about the TeamCity progress Tom On Mon, Apr 15, 2013 at 11:08 PM, Rob Vesse <rv...@do...> wrote: > I will do this anyway so don't worry too much on back porting if you > prefer to concentrate on experimenting with the NUnit migration > > Rob > > On 4/15/13 1:46 PM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Actually I have already done that in my fork of the library. >> >>It may be a bit tangled with other stuff I was trying to get TeamCity >>to play along so I will patch those changes over to the main >>repository. >> >>On Mon, Apr 15, 2013 at 10:40 PM, Rob Vesse <rv...@do...> wrote: >>> I think right now the only usage of #if DEBUG is around the HTTP >>>debugging >>> feature >>> >>> I was actually going to remove the use of #if DEBUG entirely and make >>>that >>> an always available feature because it is useful outside of debug builds >>> which reminds me that I still need to do this as part of finalizing >>>1.0.0 >>> >>> Rob >>> >>> On 4/13/13 1:36 PM, "Tomasz Pluskiewicz" <tom...@gm...> >>> wrote: >>> >>>>Hi Rob >>>> >>>>I have hit this wall before already but I don't think I ever asked about >>>>it. >>>> >>>>In the VDS.RDF.Options class there are some DEBUG conditionals, which >>>>make it impossible to build the test project under release. >>>> >>>>A cleaner solution is to use ConditionalAttribute on void methods so >>>>that they will only be executed in debug build. And there will be a >>>>fair amount less of those ugly #if DEBUG :) >>>> >>>>Thanks, >>>>Tom >>>> >>>>------------------------------------------------------------------------ >>>>-- >>>>---- >>>>Precog is a next-generation analytics platform capable of advanced >>>>analytics on semi-structured data. The platform includes APIs for >>>>building >>>>apps and a phenomenal toolset for data science. Developers can use >>>>our toolset for easy data analysis & visualization. Get a free account! >>>>http://www2.precog.com/precogplatform/slashdotnewsletter >>>>_______________________________________________ >>>>dotNetRDF-develop mailing list >>>>dot...@li... >>>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >>> >>> >>> >>> >>> >>> >>>------------------------------------------------------------------------- >>>----- >>> Precog is a next-generation analytics platform capable of advanced >>> analytics on semi-structured data. The platform includes APIs for >>>building >>> apps and a phenomenal toolset for data science. Developers can use >>> our toolset for easy data analysis & visualization. Get a free account! >>> http://www2.precog.com/precogplatform/slashdotnewsletter >>> _______________________________________________ >>> dotNetRDF-develop mailing list >>> dot...@li... >>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >>-------------------------------------------------------------------------- >>---- >>Precog is a next-generation analytics platform capable of advanced >>analytics on semi-structured data. The platform includes APIs for building >>apps and a phenomenal toolset for data science. Developers can use >>our toolset for easy data analysis & visualization. Get a free account! >>http://www2.precog.com/precogplatform/slashdotnewsletter >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-04-15 21:08:56
|
I will do this anyway so don't worry too much on back porting if you prefer to concentrate on experimenting with the NUnit migration Rob On 4/15/13 1:46 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Actually I have already done that in my fork of the library. > >It may be a bit tangled with other stuff I was trying to get TeamCity >to play along so I will patch those changes over to the main >repository. > >On Mon, Apr 15, 2013 at 10:40 PM, Rob Vesse <rv...@do...> wrote: >> I think right now the only usage of #if DEBUG is around the HTTP >>debugging >> feature >> >> I was actually going to remove the use of #if DEBUG entirely and make >>that >> an always available feature because it is useful outside of debug builds >> which reminds me that I still need to do this as part of finalizing >>1.0.0 >> >> Rob >> >> On 4/13/13 1:36 PM, "Tomasz Pluskiewicz" <tom...@gm...> >> wrote: >> >>>Hi Rob >>> >>>I have hit this wall before already but I don't think I ever asked about >>>it. >>> >>>In the VDS.RDF.Options class there are some DEBUG conditionals, which >>>make it impossible to build the test project under release. >>> >>>A cleaner solution is to use ConditionalAttribute on void methods so >>>that they will only be executed in debug build. And there will be a >>>fair amount less of those ugly #if DEBUG :) >>> >>>Thanks, >>>Tom >>> >>>------------------------------------------------------------------------ >>>-- >>>---- >>>Precog is a next-generation analytics platform capable of advanced >>>analytics on semi-structured data. The platform includes APIs for >>>building >>>apps and a phenomenal toolset for data science. Developers can use >>>our toolset for easy data analysis & visualization. Get a free account! >>>http://www2.precog.com/precogplatform/slashdotnewsletter >>>_______________________________________________ >>>dotNetRDF-develop mailing list >>>dot...@li... >>>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop >> >> >> >> >> >> >>------------------------------------------------------------------------- >>----- >> Precog is a next-generation analytics platform capable of advanced >> analytics on semi-structured data. The platform includes APIs for >>building >> apps and a phenomenal toolset for data science. Developers can use >> our toolset for easy data analysis & visualization. Get a free account! >> http://www2.precog.com/precogplatform/slashdotnewsletter >> _______________________________________________ >> dotNetRDF-develop mailing list >> dot...@li... >> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > >-------------------------------------------------------------------------- >---- >Precog is a next-generation analytics platform capable of advanced >analytics on semi-structured data. The platform includes APIs for building >apps and a phenomenal toolset for data science. Developers can use >our toolset for easy data analysis & visualization. Get a free account! >http://www2.precog.com/precogplatform/slashdotnewsletter >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-04-15 21:08:29
|
Hey All This email is part information sharing on how I currently package and upload dotNetRDF for NuGet but also to start a discussion on the possibility of making unstable builds available via NuGet which would make it easier for users to consume and verify bug fixes. Packaging Currently packaging is done via pre-build NuSpec files and NAnt targets. Under Build/nuget/ in the repo you will find a sub-directory for each package we produce. In a clean repo this will contain only a .nuspec file and possibly a readme.txt if the package requires one. To generate the NuGet packages use NAnt and one of the following targets: * dist-libs-nuget Builds all the NuGet packages * dist-libs-nuget-core Build the core library package * dist-libs-nuget-data-virtuoso Build the Data.Virtuoso package * dist-libs-nuget-query-fulltext Builds the Query.FullText package These targets rely on various other targets so will compile things as necessary. Uploading Uploading the releases is done via NAnt, the equivalent NAnt targets for the aforementioned targets simply replace dist with upload in the target name. Publishing Nightly Builds Tom has suggested that as part of getting our CI infrastructure properly spun up we should push out nightly builds to NuGet automatically. Currently the only means we have for distributing nighties is via the binaries-nightly repo we maintain at SourceForge which relies on a developer manually uploading a new build. The main barrier to this with NuGet as I understand it is that unlike Java/Maven where you can specify SNAPSHOT on the end of your version and have the server generate unique version numbers for you with NuGet you have to specify a unique version number each time. So we need some mechanism to inject version numbers into the nuspec files, NuGet does appear to support placeholders but we would need to test to make sure these work as described. We would also need to make sure that if we take this approach that we are using * in the build field of our AssemblyVersion attributes so that we get an incrementing version number. The other issue is where to publish these, we can either publish to a separate package ID which is explicitly described as Nightly/Unstable or we can publish unstable releases directly to the main feeds using the NuGet pre-release functionality (http://docs.nuget.org/docs/reference/versioning#Prerelease_Versions) There are arguments for both approaches: * Separate package separates more cleanly from stable releases BUT introduces noise into NuGet search results unless we only publish pre-release builds to the unstable channel (pre-release builds are hidden by default from search results) * Separate package allows us to have a package with more owners so any developer can publish to it, same package means expanding owner list * Publishing pre-release versions avoids having to have separate packages for every package we have (currently 3) * Publishing pre-release versions makes it easier for NuGet users to switch their dependency to the nightly build without changing their package dependencies. Thoughts and suggestions in this area are welcome, Rob |
|
From: Tomasz P. <tom...@gm...> - 2013-04-15 20:46:54
|
Actually I have already done that in my fork of the library. It may be a bit tangled with other stuff I was trying to get TeamCity to play along so I will patch those changes over to the main repository. On Mon, Apr 15, 2013 at 10:40 PM, Rob Vesse <rv...@do...> wrote: > I think right now the only usage of #if DEBUG is around the HTTP debugging > feature > > I was actually going to remove the use of #if DEBUG entirely and make that > an always available feature because it is useful outside of debug builds > which reminds me that I still need to do this as part of finalizing 1.0.0 > > Rob > > On 4/13/13 1:36 PM, "Tomasz Pluskiewicz" <tom...@gm...> > wrote: > >>Hi Rob >> >>I have hit this wall before already but I don't think I ever asked about >>it. >> >>In the VDS.RDF.Options class there are some DEBUG conditionals, which >>make it impossible to build the test project under release. >> >>A cleaner solution is to use ConditionalAttribute on void methods so >>that they will only be executed in debug build. And there will be a >>fair amount less of those ugly #if DEBUG :) >> >>Thanks, >>Tom >> >>-------------------------------------------------------------------------- >>---- >>Precog is a next-generation analytics platform capable of advanced >>analytics on semi-structured data. The platform includes APIs for building >>apps and a phenomenal toolset for data science. Developers can use >>our toolset for easy data analysis & visualization. Get a free account! >>http://www2.precog.com/precogplatform/slashdotnewsletter >>_______________________________________________ >>dotNetRDF-develop mailing list >>dot...@li... >>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop > > > > > > ------------------------------------------------------------------------------ > Precog is a next-generation analytics platform capable of advanced > analytics on semi-structured data. The platform includes APIs for building > apps and a phenomenal toolset for data science. Developers can use > our toolset for easy data analysis & visualization. Get a free account! > http://www2.precog.com/precogplatform/slashdotnewsletter > _______________________________________________ > dotNetRDF-develop mailing list > dot...@li... > https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: <tr...@do...> - 2013-04-15 20:44:07
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Remove all usage of #if DEBUG associated with HTTP Debugging functionality</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Refactor</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
HTTP Debugging is a useful feature but is currently conditionally compiled out of release builds, since it can be very useful in production code and outside of a pure debug environment it makes sense to not conditionally compile this out and instead include it in all builds.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=347" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=347</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: Rob V. <rv...@do...> - 2013-04-15 20:41:56
|
I think right now the only usage of #if DEBUG is around the HTTP debugging feature I was actually going to remove the use of #if DEBUG entirely and make that an always available feature because it is useful outside of debug builds which reminds me that I still need to do this as part of finalizing 1.0.0 Rob On 4/13/13 1:36 PM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >I have hit this wall before already but I don't think I ever asked about >it. > >In the VDS.RDF.Options class there are some DEBUG conditionals, which >make it impossible to build the test project under release. > >A cleaner solution is to use ConditionalAttribute on void methods so >that they will only be executed in debug build. And there will be a >fair amount less of those ugly #if DEBUG :) > >Thanks, >Tom > >-------------------------------------------------------------------------- >---- >Precog is a next-generation analytics platform capable of advanced >analytics on semi-structured data. The platform includes APIs for building >apps and a phenomenal toolset for data science. Developers can use >our toolset for easy data analysis & visualization. Get a free account! >http://www2.precog.com/precogplatform/slashdotnewsletter >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-04-15 20:38:07
|
Tom The style of test naming was chosen originally because when sorting tests by name it nicely groups tests so that you can run all the tests that pertain to some area. I would like to preserve this at least because I personally find it very useful on a daily basis, we could try and migrate towards a compromise style e.g Mime - ParsingTurtleW3CBaseTurtleStyle1 Yours - ShouldSuccessfullyParseValidW3CBaseTurtleStyle Compromise - ParsingTurtleW3CAcceptsValidTurtleStyleBaseDeclaration (This is not a great example because the test name already calls out a bunch of stuff but you get the idea) So this fulfills my usage of being able to group tests easily by name and your aim of having more descriptive naming for diagnosing what failed, what do you think? Rob On 4/13/13 9:08 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi again Rob > >There is one more thing about unit tests. I have noticed that you >commonly use a same name for multiple tests and just append a number. >It would be much more helpful if they had meaningful names so that >when one fails it is instantly obvious why. For example >ParsingTurtleW3CBaseTurtleStyle1 would become >ShouldSuccessfullyParseValidW3CBaseTurtleStyle. Similarily >ParsingTurtleW3CBaseTurtleStyle2 would become >ShouldThrowWhenBaseDirectiveIsMissingDot and so on. > >Would you be okay with me gradually renaming any tests I think can >have a better name? > >Thanks, >Tom > >On Sat, Apr 13, 2013 at 12:23 PM, Tomasz Pluskiewicz ><tom...@gm...> wrote: >> Hi Rob >> >> Some time we discussed setting up continous integration for dotNetRDF. >> I am upgrading my VPS to a more powerful machine and I have already >> set up TeamCity. It will also be possible to install some triplestores >> for integration testing. >> >> However I'm hitting a wall with unit tests because you use MSTest. >> Would you be fine with me converting to NUnit? That way TeamCity will >> run without installing Visual Studio and VS Express users will also be >> able to build the whole solution. Also I think we could ask JetBrains >> for ReSharper licence for our project (in case you would ask about >> running the test suite from within VS). Oh and by the way, with the >> introduction of NUnit there can be a lot less code for similar tests, >> which can be parametrized. I assume you know the TestCase attribute. >> >> When TeamCity builds are running I think we should also automate NuGet >> publishing. For that some changes will be needed to have automatic >> version numbering. Also you would have to explain how you nuget pack >> dotNetRDF. In a separate email maybe. >> >> Also I thought that maybe there could be two flavors of those >> packages. One as usual for stable builds and a new one, which would >> publish automatically for each successful build. What do you think? >> >> A thing to consider here is moving to a dedicated branch for release >> development and leaving default only for bugfixes. >> >> Any thoughs? >> >> Thanks >> Tom > >-------------------------------------------------------------------------- >---- >Precog is a next-generation analytics platform capable of advanced >analytics on semi-structured data. The platform includes APIs for building >apps and a phenomenal toolset for data science. Developers can use >our toolset for easy data analysis & visualization. Get a free account! >http://www2.precog.com/precogplatform/slashdotnewsletter >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Rob V. <rv...@do...> - 2013-04-15 20:31:54
|
Hey Tom Yes we've gone around on this a couple of times before and I have never had the free time to look into it further. If you have the capacity to set up TeamCity to run builds and testing that would be great. If you want to explore moving to NUnit that is fine provided you do it in a separate branch/fork for the time being. Now the remaining blocker bug you had open (graph equality) is solved I want to go ahead and run regressions and then hopefully push out 1.0.0 towards the end of the week (unless you have any objections?) so anything that interferes with that is bad for me right now! For me the deal breaker is being able to Debug tests inside of Visual Studio without having to jump through additional hoops (i.e. Debug > Attach to Process) as NUnit straight out the box seems to require. To be honest even if JetBrains won't give us an open source ReSharper license I can easily afford to buy a personal license since I imagine it is primarily me who spends a lot of time running tests in Debug mode. I'll start a separate thread on NuGet publishing Rob On 4/13/13 3:23 AM, "Tomasz Pluskiewicz" <tom...@gm...> wrote: >Hi Rob > >Some time we discussed setting up continous integration for dotNetRDF. >I am upgrading my VPS to a more powerful machine and I have already >set up TeamCity. It will also be possible to install some triplestores >for integration testing. > >However I'm hitting a wall with unit tests because you use MSTest. >Would you be fine with me converting to NUnit? That way TeamCity will >run without installing Visual Studio and VS Express users will also be >able to build the whole solution. Also I think we could ask JetBrains >for ReSharper licence for our project (in case you would ask about >running the test suite from within VS). Oh and by the way, with the >introduction of NUnit there can be a lot less code for similar tests, >which can be parametrized. I assume you know the TestCase attribute. > >When TeamCity builds are running I think we should also automate NuGet >publishing. For that some changes will be needed to have automatic >version numbering. Also you would have to explain how you nuget pack >dotNetRDF. In a separate email maybe. > >Also I thought that maybe there could be two flavors of those >packages. One as usual for stable builds and a new one, which would >publish automatically for each successful build. What do you think? > >A thing to consider here is moving to a dedicated branch for release >development and leaving default only for bugfixes. > >Any thoughs? > >Thanks >Tom > >-------------------------------------------------------------------------- >---- >Precog is a next-generation analytics platform capable of advanced >analytics on semi-structured data. The platform includes APIs for building >apps and a phenomenal toolset for data science. Developers can use >our toolset for easy data analysis & visualization. Get a free account! >http://www2.precog.com/precogplatform/slashdotnewsletter >_______________________________________________ >dotNetRDF-develop mailing list >dot...@li... >https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop |
|
From: Tomasz P. <tom...@gm...> - 2013-04-13 20:37:43
|
Hi Rob I have hit this wall before already but I don't think I ever asked about it. In the VDS.RDF.Options class there are some DEBUG conditionals, which make it impossible to build the test project under release. A cleaner solution is to use ConditionalAttribute on void methods so that they will only be executed in debug build. And there will be a fair amount less of those ugly #if DEBUG :) Thanks, Tom |
|
From: Tomasz P. <tom...@gm...> - 2013-04-13 16:08:50
|
Hi again Rob There is one more thing about unit tests. I have noticed that you commonly use a same name for multiple tests and just append a number. It would be much more helpful if they had meaningful names so that when one fails it is instantly obvious why. For example ParsingTurtleW3CBaseTurtleStyle1 would become ShouldSuccessfullyParseValidW3CBaseTurtleStyle. Similarily ParsingTurtleW3CBaseTurtleStyle2 would become ShouldThrowWhenBaseDirectiveIsMissingDot and so on. Would you be okay with me gradually renaming any tests I think can have a better name? Thanks, Tom On Sat, Apr 13, 2013 at 12:23 PM, Tomasz Pluskiewicz <tom...@gm...> wrote: > Hi Rob > > Some time we discussed setting up continous integration for dotNetRDF. > I am upgrading my VPS to a more powerful machine and I have already > set up TeamCity. It will also be possible to install some triplestores > for integration testing. > > However I'm hitting a wall with unit tests because you use MSTest. > Would you be fine with me converting to NUnit? That way TeamCity will > run without installing Visual Studio and VS Express users will also be > able to build the whole solution. Also I think we could ask JetBrains > for ReSharper licence for our project (in case you would ask about > running the test suite from within VS). Oh and by the way, with the > introduction of NUnit there can be a lot less code for similar tests, > which can be parametrized. I assume you know the TestCase attribute. > > When TeamCity builds are running I think we should also automate NuGet > publishing. For that some changes will be needed to have automatic > version numbering. Also you would have to explain how you nuget pack > dotNetRDF. In a separate email maybe. > > Also I thought that maybe there could be two flavors of those > packages. One as usual for stable builds and a new one, which would > publish automatically for each successful build. What do you think? > > A thing to consider here is moving to a dedicated branch for release > development and leaving default only for bugfixes. > > Any thoughs? > > Thanks > Tom |
|
From: Tomasz P. <tom...@gm...> - 2013-04-13 10:24:32
|
Hi Rob Some time we discussed setting up continous integration for dotNetRDF. I am upgrading my VPS to a more powerful machine and I have already set up TeamCity. It will also be possible to install some triplestores for integration testing. However I'm hitting a wall with unit tests because you use MSTest. Would you be fine with me converting to NUnit? That way TeamCity will run without installing Visual Studio and VS Express users will also be able to build the whole solution. Also I think we could ask JetBrains for ReSharper licence for our project (in case you would ask about running the test suite from within VS). Oh and by the way, with the introduction of NUnit there can be a lot less code for similar tests, which can be parametrized. I assume you know the TestCase attribute. When TeamCity builds are running I think we should also automate NuGet publishing. For that some changes will be needed to have automatic version numbering. Also you would have to explain how you nuget pack dotNetRDF. In a separate email maybe. Also I thought that maybe there could be two flavors of those packages. One as usual for stable builds and a new one, which would publish automatically for each successful build. What do you think? A thing to consider here is moving to a dedicated branch for release development and leaving default only for bugfixes. Any thoughs? Thanks Tom |
|
From: <dot...@li...> - 2013-04-12 22:21:33
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: rvesse: Close the CORE-345 branch now the bug is fixed (Bitbucket) 2. commit/dotnetrdf: rvesse: Tweak to code in GraphMatcher that was causing unecessary recursion (CORE-345) (Bitbucket) 3. commit/dotnetrdf: tpluscode: additional test cases for CORE-345 (Bitbucket) 4. commit/dotnetrdf: 4 new changesets (Bitbucket) 5. commit/dotnetrdf: 3 new changesets (Bitbucket) 6. commit/dotnetrdf: rvesse: Tests and minor fix for GraphMatcher treatment of nulls (CORE-345) (Bitbucket) 7. commit/dotnetrdf: rvesse: Move and update graph equality documentation to GraphMatcher, make GraphMatcher public (CORE-345) (Bitbucket) 8. commit/dotnetrdf: rvesse: Minor doc correction (Bitbucket) 9. commit/dotnetrdf: 2 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Fri, 12 Apr 2013 18:16:01 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Close the CORE-345 branch now the bug is fixed To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5e26e9813958/ Changeset: 5e26e9813958 Branch: CORE-345 User: rvesse Date: 2013-04-12 20:15:41 Summary: Close the CORE-345 branch now the bug is fixed Affected #: 0 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Fri, 12 Apr 2013 18:28:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Tweak to code in GraphMatcher that was causing unecessary recursion (CORE-345) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3c08cefebb3f/ Changeset: 3c08cefebb3f User: rvesse Date: 2013-04-12 20:27:49 Summary: Tweak to code in GraphMatcher that was causing unecessary recursion (CORE-345) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Fri, 12 Apr 2013 18:57:36 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: additional test cases for CORE-345 To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/13e3e29590d6/ Changeset: 13e3e29590d6 User: tpluscode Date: 2013-04-12 20:54:32 Summary: additional test cases for CORE-345 Affected #: 16 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Fri, 12 Apr 2013 21:14:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a6a563b7fd73/ Changeset: a6a563b7fd73 User: rvesse Date: 2013-04-12 21:20:04 Summary: Improve debug info in GraphMatcher even further to try and isolate Tom's remaining failing test (CORE-345) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/bcad0408ab16/ Changeset: bcad0408ab16 User: rvesse Date: 2013-04-12 21:26:14 Summary: Have test cases dump differences for failing tests (CORE-345) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1f0819849b33/ Changeset: 1f0819849b33 User: rvesse Date: 2013-04-12 22:54:52 Summary: Tweak to debug print info Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fca49a94ab78/ Changeset: fca49a94ab78 User: rvesse Date: 2013-04-12 23:11:23 Summary: Add additional rules based mapping step which vastly improves accurracy of rules based mapping and fixes remaining failing test case (CORE-345) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Fri, 12 Apr 2013 21:48:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6f610ce27e7d/ Changeset: 6f610ce27e7d User: rvesse Date: 2013-04-12 23:19:40 Summary: Simplify method signature of GenerateMappings() and make a public static method (CORE-345) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d3e9849f0eac/ Changeset: d3e9849f0eac User: rvesse Date: 2013-04-12 23:42:20 Summary: Rewrite GenerateMappings() yet again and add unit tests to check that it does indeed brute force the complete solution space (CORE-345) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e7c003648d07/ Changeset: e7c003648d07 User: rvesse Date: 2013-04-12 23:46:32 Summary: Further logic fixes and tests to GenerateMappings() (CORE-345) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Fri, 12 Apr 2013 21:55:52 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Tests and minor fix for GraphMatcher treatment of nulls (CORE-345) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dfb6d0603c0c/ Changeset: dfb6d0603c0c User: rvesse Date: 2013-04-12 23:55:40 Summary: Tests and minor fix for GraphMatcher treatment of nulls (CORE-345) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Fri, 12 Apr 2013 22:16:18 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Move and update graph equality documentation to GraphMatcher, make GraphMatcher public (CORE-345) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/943d811c9813/ Changeset: 943d811c9813 User: rvesse Date: 2013-04-13 00:16:05 Summary: Move and update graph equality documentation to GraphMatcher, make GraphMatcher public (CORE-345) Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 12 Apr 2013 22:16:55 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Minor doc correction To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4d987e60b66a/ Changeset: 4d987e60b66a User: rvesse Date: 2013-04-13 00:16:45 Summary: Minor doc correction Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Fri, 12 Apr 2013 22:21:24 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4a736e4905dc/ Changeset: 4a736e4905dc Branch: 1.9 User: rvesse Date: 2013-04-13 00:19:13 Summary: Merge latest fixes from default Affected #: 32 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a3a1c327964b/ Changeset: a3a1c327964b Branch: 1.9 User: rvesse Date: 2013-04-13 00:20:59 Summary: Minor fix up after merge Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 7, Issue 2 *********************************************** |
|
From: <tr...@do...> - 2013-04-12 18:34:07
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Generating Graph diff report causes memory usage explosion for isomorphic graphs with lots of blank nodes</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Progress changed from "0 %" to "95 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-12 18:33:47
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Generating Graph diff report causes memory usage explosion for isomorphic graphs with lots of blank nodes</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-04-12 07:32 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
I believe the issue should now be resolved, I identified and fixed two things.</p>
<ol>
<li>
The code for GenerateMappings() was flawed and would get stuck spinning and eating memory indefinitely. I rewrote from scratch so that I could use yield return which makes the code much faster and should now be correct (though I am not 100% certain on this)</li>
<li>
I also added an intermediate mapping step between rules based and brute force mappings which takes a divide and conquer approach. It splits the unmapped blank nodes into their isolated sub-graphs and then attempts to map each one independently, this makes the possible solution space much smaller and results in a much more efficient, accurate and effective mapping algorithm.</li>
</ol>
<p>
Leaving at 95% as Tom has additional test cases to add</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2013-04-12 18:14:45
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 2 new changesets (Bitbucket) 2. commit/dotnetrdf: 3 new changesets (Bitbucket) 3. commit/dotnetrdf: tpluscode: added test case for memory leak (Bitbucket) 4. commit/dotnetrdf: 6 new changesets (Bitbucket) 5. commit/dotnetrdf: tpluscode: final fixes of culture-invariant comparison (Bitbucket) 6. commit/dotnetrdf: 3 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: More debug info in GraphMatcher (CORE-345) (Bitbucket) 8. commit/dotnetrdf: 2 new changesets (Bitbucket) 9. commit/dotnetrdf: 4 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Tue, 02 Apr 2013 00:22:35 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/632a9c0ce6b6/ Changeset: 632a9c0ce6b6 User: rvesse Date: 2013-04-02 02:20:03 Summary: Add unit test to try and reproduce a bug report, not reproducible Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2c532a4f9df5/ Changeset: 2c532a4f9df5 User: rvesse Date: 2013-04-02 02:20:51 Summary: Variant on same test, still not reproducible Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Wed, 03 Apr 2013 20:40:04 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e383279c02d1/ Changeset: e383279c02d1 Branch: CORE-344 User: tpluscode Date: 2013-04-03 22:22:26 Summary: changed the AggregateTests to reproduce bug Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cf309a34aed6/ Changeset: cf309a34aed6 Branch: CORE-344 User: tpluscode Date: 2013-04-03 22:26:09 Summary: added code changes to fix aggregate bug Affected #: 5 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4eb63d7e8bc7/ Changeset: 4eb63d7e8bc7 Branch: CORE-344 User: tpluscode Date: 2013-04-03 22:39:43 Summary: use resource file instead for test Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Sun, 07 Apr 2013 18:19:25 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: added test case for memory leak To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ce20a9b8e361/ Changeset: ce20a9b8e361 Branch: CORE-345 User: tpluscode Date: 2013-04-07 20:17:28 Summary: added test case for memory leak Affected #: 4 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Sun, 07 Apr 2013 19:41:08 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c660106a061d/ Changeset: c660106a061d Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:21:56 Summary: added decimal comparison to ComparisonHelper and use ordinal string comparison Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fbafbd1152f5/ Changeset: fbafbd1152f5 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:23:41 Summary: added failing tests for ILiteralNode comparison Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6256d90937d4/ Changeset: 6256d90937d4 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:34:10 Summary: added failing tests for SPARQL cast operators Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/56c75eecb162/ Changeset: 56c75eecb162 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:36:31 Summary: moved TestedCultureInfos to BaseTest Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2363ea027244/ Changeset: 2363ea027244 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:37:02 Summary: missing headers Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a4122a55e611/ Changeset: a4122a55e611 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:37:27 Summary: Merge with previously fixed code Affected #: 6 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Sun, 07 Apr 2013 19:41:18 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: final fixes of culture-invariant comparison To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/94fdf6940b22/ Changeset: 94fdf6940b22 Branch: CORE-344 User: tpluscode Date: 2013-04-07 21:40:54 Summary: final fixes of culture-invariant comparison Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Tue, 09 Apr 2013 17:24:40 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/70ddb5328c91/ Changeset: 70ddb5328c91 Branch: CORE-345 User: rvesse Date: 2013-04-09 18:40:00 Summary: Another unit test to try and repro a bug, turned out to be user error in prefix definitions Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/81e68409e0bc/ Changeset: 81e68409e0bc Branch: CORE-345 User: rvesse Date: 2013-04-09 19:10:36 Summary: Start adding Debug info to GraphMatcher to help debug CORE-345 Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c914b99395dc/ Changeset: c914b99395dc Branch: CORE-345 User: rvesse Date: 2013-04-09 19:24:26 Summary: More debug info in GraphMatcher (CORE-345) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Tue, 09 Apr 2013 17:26:45 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: More debug info in GraphMatcher (CORE-345) To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4efe5ea85a11/ Changeset: 4efe5ea85a11 Branch: CORE-345 User: rvesse Date: 2013-04-09 19:26:32 Summary: More debug info in GraphMatcher (CORE-345) Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 12 Apr 2013 17:20:58 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e8519395019a/ Changeset: e8519395019a Branch: CORE-345 User: rvesse Date: 2013-04-12 18:46:37 Summary: Test to try and repo a bug around MIME type selection, not reproducible Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8de2f23845e0/ Changeset: 8de2f23845e0 Branch: CORE-345 User: rvesse Date: 2013-04-12 19:20:46 Summary: Fix logic in GraphMatcher to not spin forever trying brute forcing, test now fails within timeout so logic is still not entirely correct Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Fri, 12 Apr 2013 18:14:36 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3e01b47287ac/ Changeset: 3e01b47287ac Branch: CORE-345 User: rvesse Date: 2013-04-12 19:26:03 Summary: More debug statements in GraphMatcher (CORE-345) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/330c2920193d/ Changeset: 330c2920193d Branch: CORE-345 User: rvesse Date: 2013-04-12 20:12:12 Summary: Add divide and conquer approach as fall back prior to brute force, unit tests now pass (CORE-345) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/49b55b01fe34/ Changeset: 49b55b01fe34 Branch: CORE-345 User: rvesse Date: 2013-04-12 20:13:13 Summary: Note fix for CORE-345 in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/23c4cd05b4cb/ Changeset: 23c4cd05b4cb User: rvesse Date: 2013-04-12 20:14:16 Summary: Merge fixes for CORE-345, GraphMatcher could fail to determine equality/inequality and OOM on relatively small but blank node heavy graphs Affected #: 11 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 7, Issue 1 *********************************************** |
|
From: <tr...@do...> - 2013-04-09 17:41:30
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Generating Graph diff report causes memory usage explosion for isomorphic graphs with lots of blank nodes</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Title changed from "Generating Graph diff report causes memory leak for isomorphic graphs with lots of blank nodes" to "Generating Graph diff report causes memory usage explosion for isomorphic graphs with lots of blank nodes"
</li>
<li>Status changed from "Confirmed" to "In Progress"
</li>
<li>Assigned to changed from "Unassigned" to "Rob Vesse"
</li>
<li>Estimation changed from "0.00" to "10"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-09 16:48:59
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Number parsing is affected by CultureInfo</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "50 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=344" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=344</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-09 16:45:02
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Support a ReadWrite variant of SparqlConnector that uses SPARQL Update for write operations</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.1</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Storage</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Normal</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Currently the SparqlConnector is read-only, using SPARQL Update it should be possible to make it read/write though this won't be perfect when blank nodes are involved.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=346" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=346</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-07 18:15:44
|
<p>The following issue has been updated by Tomasz Pluskiewicz:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Generating Graph diff report causes memory leak for isomorphic graphs with lots of blank nodes</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Attachment changed from "GraphComparisonB.ttl" to "Added"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-07 18:15:06
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Generating Graph diff report causes memory leak for isomorphic graphs with lots of blank nodes</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Tomasz Pluskiewicz</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Core API</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>Critical</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
There is a problem with graph comparison (presumably within GraphMatcher), which causes a memory leak when equal graphs are compared.</p>
<p>
Example graphs attached.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=345</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-04-03 20:16:43
|
<p>The following issue has been added to a project that you are monitoring.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Number parsing is affected by CultureInfo</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Tomasz Pluskiewicz</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.0.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</td>
</tr>
<tr>
<td><b>Priority:</b></td>
<td>High</td>
</tr>
<tr>
<td><b>Type:</b></td>
<td>Bug</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Valued nodes when parsed should ignore the culture setting in Thread#CurrentCulture.</p>
<p>
Currently parsing of decimal numbers would fail in cultures which use different decimal point than a dot.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=344" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=344</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <dot...@li...> - 2013-03-29 23:42:30
|
Send dotNetRDF-commits mailing list submissions to dot...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits or, via email, send a message with subject or body 'help' to dot...@li... You can reach the person managing the list at dot...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of dotNetRDF-commits digest..." Today's Topics: 1. commit/dotnetrdf: 6 new changesets (Bitbucket) 2. commit/dotnetrdf: 2 new changesets (Bitbucket) 3. commit/dotnetrdf: tpluscode: add test for invalid type loaded (Bitbucket) 4. commit/dotnetrdf: 3 new changesets (Bitbucket) 5. commit/dotnetrdf: 5 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: 2 new changesets (Bitbucket) 8. commit/dotnetrdf: 3 new changesets (Bitbucket) 9. commit/dotnetrdf: 2 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Mar 2013 19:19:53 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c9b04ee4e852/ Changeset: c9b04ee4e852 User: tpluscode Date: 2013-03-20 22:56:39 Summary: dot settings Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f47a7004371b/ Changeset: f47a7004371b Branch: CORE-337 User: tpluscode Date: 2013-03-20 23:00:22 Summary: added new constructors and made ConfigurationLoader non-static Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/96a002005589/ Changeset: 96a002005589 Branch: CORE-337 User: tpluscode Date: 2013-03-20 23:10:50 Summary: loading object using blank node identifier Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0a46617b7e8f/ Changeset: 0a46617b7e8f Branch: CORE-337 User: tpluscode Date: 2013-03-21 19:31:22 Summary: loading object using URI Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/08cd7047dbcc/ Changeset: 08cd7047dbcc Branch: CORE-337 User: tpluscode Date: 2013-03-21 20:17:13 Summary: add constructor for file and URI Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dfe4ccb90bc6/ Changeset: dfe4ccb90bc6 Branch: CORE-337 User: tpluscode Date: 2013-03-21 20:18:47 Summary: cleanup test class and added header Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 2 Date: Sun, 24 Mar 2013 18:23:09 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/9dc68de9d5e1/ Changeset: 9dc68de9d5e1 Branch: CORE-337 User: tpluscode Date: 2013-03-24 19:08:43 Summary: move test graph to constant field Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/67a81b6979f0/ Changeset: 67a81b6979f0 Branch: CORE-337 User: tpluscode Date: 2013-03-24 19:22:10 Summary: added tests for invalid configuration node Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 3 Date: Sun, 24 Mar 2013 18:26:25 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: tpluscode: add test for invalid type loaded To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6d7df2338674/ Changeset: 6d7df2338674 Branch: CORE-337 User: tpluscode Date: 2013-03-24 19:26:17 Summary: add test for invalid type loaded Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 4 Date: Mon, 25 Mar 2013 19:12:48 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f5a7856c968b/ Changeset: f5a7856c968b User: rvesse Date: 2013-03-25 19:57:26 Summary: Note Tom's changes for CORE-337 in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/05eec513b127/ Changeset: 05eec513b127 User: rvesse Date: 2013-03-25 20:11:48 Summary: Changes to fix CORE-341 a bug where the Turtle parser could accept invalid input and generate incorrect URIs for that input caused by shared helper code between Turtle and N3 where the input would be valid Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/03721ca7b7ce/ Changeset: 03721ca7b7ce User: rvesse Date: 2013-03-25 20:12:34 Summary: Note fix for CORE-341 in Change Log Affected #: 1 file Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 5 Date: Wed, 27 Mar 2013 23:39:05 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 5 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 5 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/728657493894/ Changeset: 728657493894 User: rvesse Date: 2013-03-27 21:33:37 Summary: Remove new ConfigurationLoader methods which are not supported under Silverlight (CORE-337) Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e62631983051/ Changeset: e62631983051 User: rvesse Date: 2013-03-27 22:32:17 Summary: Add some more unit tests to try and nail down a possible bug with SPARQL joins Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/509e5d294eeb/ Changeset: 509e5d294eeb User: rvesse Date: 2013-03-28 00:24:13 Summary: Unit test that demonstrates the root cause of CORE-343 which is a bug in SetDistinctnessComparer Affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c4a18c2fe92d/ Changeset: c4a18c2fe92d User: rvesse Date: 2013-03-28 00:29:55 Summary: Add failing unit test to demonstrate the issue that prompted reporting of CORE-343 as a regression and sanity test for after the set distinctness problem is resolved Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6f2e80e2b7f7/ Changeset: 6f2e80e2b7f7 User: rvesse Date: 2013-03-28 00:38:33 Summary: Additional unit tests and fix for CORE-343 Affected #: 5 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 6 Date: Thu, 28 Mar 2013 00:18:44 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/008c37ab6f78/ Changeset: 008c37ab6f78 User: rvesse Date: 2013-03-28 00:55:05 Summary: Note fix for CORE-343 in Change Log Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d13b309c2cba/ Changeset: d13b309c2cba User: rvesse Date: 2013-03-28 01:18:31 Summary: Some work towards preserving the ordering of variables in SparqlResult objects (CORE-342) Affected #: 3 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 7 Date: Thu, 28 Mar 2013 23:59:59 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/615908f8e0eb/ Changeset: 615908f8e0eb User: rvesse Date: 2013-03-28 17:45:52 Summary: Additional unit test for CORE-343 that shows how the bug can interact with property paths Affected #: 9 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5492a0f7cfb4/ Changeset: 5492a0f7cfb4 User: rvesse Date: 2013-03-29 00:59:46 Summary: Add/fix license headers Affected #: 4 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 8 Date: Fri, 29 Mar 2013 23:32:39 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/8c1b9683029d/ Changeset: 8c1b9683029d User: rvesse Date: 2013-03-29 18:39:13 Summary: Test to try and reproduce a alledged memory leak, not reproducible with information provided so far Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/51a010762727/ Changeset: 51a010762727 User: rvesse Date: 2013-03-30 00:14:54 Summary: Ensure that wherever possible the order of variables in the SELECT clause is respected and preserved (CORE-342) Affected #: 13 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a6174b925e81/ Changeset: a6174b925e81 User: rvesse Date: 2013-03-30 00:32:16 Summary: Note fixes for CORE-342, CORE-338 and CORE-341 in Change Log Affected #: 3 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ Message: 9 Date: Fri, 29 Mar 2013 23:42:17 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@bi...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d94b56ea24f6/ Changeset: d94b56ea24f6 Branch: 1.9 User: rvesse Date: 2013-03-30 00:40:00 Summary: Merge latest changes from default Affected #: 77 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/adb58da8cca7/ Changeset: adb58da8cca7 Branch: 1.9 User: rvesse Date: 2013-03-30 00:42:07 Summary: Minor fix up after merge from default Affected #: 2 files Repository URL: https://bitbucket.org/dotnetrdf/dotnetrdf/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. ------------------------------ ------------------------------------------------------------------------------ Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 6, Issue 4 *********************************************** |
|
From: <tr...@do...> - 2013-03-29 23:35:48
|
<p>The following issue has been updated by Rob Vesse:</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Order of variables in the SELECT list is not respected in returned results</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "In Progress" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "30 %" to "100 %"
</li>
</ul>
</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=342" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=342</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
|
From: <tr...@do...> - 2013-03-29 23:35:41
|
<p>A new comment has been added to the following issue.</p>
<table border="0">
<tr>
<td width="90px" valign="top"><b>Title:</b></td>
<td>Order of variables in the SELECT list is not respected in returned results</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Core Library (dotNetRDF.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-03-29 11:34 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
As far as possible the code will now try to preserve the order of variables from the SELECT clause, for SELECT * the order will depend on how the query is evaluated. For results parsed from XML, JSON, TSV and CSV order will be preserved.</p></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=342" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=342</a></p>
<p style="text-align:center;font-size:8pt;padding:5px;">
If you no longer wish to receive notifications, please visit <a href="http://www.dotnetrdf.org/tracker/Account/UserProfile.aspx" target="_blank">your profile</a> and change your notifications options.
</p>
|
48 messages has been excluded from this view by a project administrator.
