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-11-11 11:18:37
|
<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>Set up CI servers</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-11-11 11:16 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Tom already set this up a while back and it is available at <a href="http://ci.dotnetrdf.org">ci.dotnetrdf.org</a></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=276" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=276</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-10-24 14:16:35
|
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: Merge in CORE-378 fix (Bitbucket) 2. commit/dotnetrdf: 6 new changesets (Bitbucket) 3. commit/dotnetrdf: 3 new changesets (Bitbucket) 4. commit/dotnetrdf: rvesse: Continue fleshing out contract tests for IGraph (Bitbucket) 5. commit/dotnetrdf: 4 new changesets (Bitbucket) 6. commit/dotnetrdf: 4 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: More progress on refactoring IO Core (Bitbucket) 8. commit/dotnetrdf: 4 new changesets (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Tue, 15 Oct 2013 11:20:44 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Merge in CORE-378 fix To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/61b45618a4b2/ Changeset: 61b45618a4b2 User: rvesse Date: 2013-10-15 13:20:24 Summary: Merge in CORE-378 fix Affected #: 10 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: Thu, 17 Oct 2013 09:46:00 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 6 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 6 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4a2400f35e9e/ Changeset: 4a2400f35e9e Branch: 1.9 User: rvesse Date: 2013-10-17 10:58:09 Summary: Merge latest changes from default Affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/b93d1774c7ad/ Changeset: b93d1774c7ad Branch: 1.9 User: rvesse Date: 2013-10-17 10:58:54 Summary: Reenable pre-build event Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a927456c5b73/ Changeset: a927456c5b73 Branch: 1.9 User: rvesse Date: 2013-10-17 11:37:20 Summary: Refactor Core API classes into more logical namespaces Affected #: 106 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/da1477a4d630/ Changeset: da1477a4d630 Branch: 1.9 User: rvesse Date: 2013-10-17 11:43:35 Summary: Upgrade to latest version of SyncProjects Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4334340c24d5/ Changeset: 4334340c24d5 Branch: 1.9 User: rvesse Date: 2013-10-17 11:44:24 Summary: Enable disk syncing for dotNetRDF.Core.Test project Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/db34093ea658/ Changeset: db34093ea658 Branch: 1.9 User: rvesse Date: 2013-10-17 11:45:41 Summary: Relocate new core tests to desired location in tree Affected #: 7 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: Thu, 17 Oct 2013 10:10:09 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 3 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 3 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c7cb2be7293f/ Changeset: c7cb2be7293f Branch: 1.9 User: rvesse Date: 2013-10-17 11:48:46 Summary: Switch to NUnit for new Core tests Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3f53a015665f/ Changeset: 3f53a015665f Branch: 1.9 User: rvesse Date: 2013-10-17 11:59:53 Summary: Add some basic tests for Find() behaviour on graphs Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c7abd45e121b/ Changeset: c7abd45e121b Branch: 1.9 User: rvesse Date: 2013-10-17 12:09:52 Summary: Simplify many methods of IGraph and IGraphStore to return void rather than bool which makes it easier to support a wider variety of backing implementations since backing storage does not need to report status of the operation other than throwing an exception in the case of failure Affected #: 8 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: Thu, 17 Oct 2013 10:22:46 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Continue fleshing out contract tests for IGraph To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/1df41530287f/ Changeset: 1df41530287f Branch: 1.9 User: rvesse Date: 2013-10-17 12:22:33 Summary: Continue fleshing out contract tests for IGraph 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: Thu, 17 Oct 2013 14:31:56 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ba05153460f6/ Changeset: ba05153460f6 Branch: 1.9 User: rvesse Date: 2013-10-17 15:14:13 Summary: Move and refactor URI resolution methods into UriFactory class Affected #: 6 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/26f446822ebf/ Changeset: 26f446822ebf Branch: 1.9 User: rvesse Date: 2013-10-17 15:37:32 Summary: Add a set of tests for URI and prefixed name resolution Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5742b445b378/ Changeset: 5742b445b378 Branch: 1.9 User: rvesse Date: 2013-10-17 16:11:11 Summary: Change URI interning to be by segment rather than by character to create a more compact interning data structure (CORE-330) Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f96080fec6bf/ Changeset: f96080fec6bf Branch: 1.9 User: rvesse Date: 2013-10-17 16:31:42 Summary: Enforce restriction that INamespaceMapper forbids null/relative namespace URIs. Start adding contract tests for INamespaceMapper implementations 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, 17 Oct 2013 15:19:42 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/57d3077da360/ Changeset: 57d3077da360 Branch: 1.9 User: rvesse Date: 2013-10-17 16:39:04 Summary: Start refactoring IO Core to align with Core changes, not yet buildable Affected #: 21 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5dde9c631599/ Changeset: 5dde9c631599 Branch: 1.9 User: rvesse Date: 2013-10-17 17:05:50 Summary: More refactoring towards getting the IO Core back into a buildable state Affected #: 95 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/28ff9bc4a1fb/ Changeset: 28ff9bc4a1fb Branch: 1.9 User: rvesse Date: 2013-10-17 17:12:00 Summary: Continuing to refactor IO Core Affected #: 21 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/0ba4205fcaab/ Changeset: 0ba4205fcaab Branch: 1.9 User: rvesse Date: 2013-10-17 17:19:30 Summary: Yet more refactoring of IO Core, still nowhere near buildable Affected #: 14 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, 18 Oct 2013 16:59:45 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: More progress on refactoring IO Core To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cfd9ab2bea32/ Changeset: cfd9ab2bea32 Branch: 1.9 User: rvesse Date: 2013-10-18 18:59:24 Summary: More progress on refactoring IO Core Affected #: 21 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: Thu, 24 Oct 2013 14:16:20 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 4 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 4 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/27b2fc9c6b0e/ Changeset: 27b2fc9c6b0e Branch: VIRT-382 User: rvesse Date: 2013-10-24 16:10:09 Summary: Unit tests and fixes for a case where Virtuoso transactions were not correctly closed (VIRT-382) Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/4048a54ae913/ Changeset: 4048a54ae913 Branch: VIRT-382 User: rvesse Date: 2013-10-24 16:12:37 Summary: Close the VIRT-382 branch Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/d5ce4120c9a6/ Changeset: d5ce4120c9a6 User: rvesse Date: 2013-10-24 16:13:03 Summary: Merge in fix for VIRT-382 Affected #: 4 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5e9e8cf59046/ Changeset: 5e9e8cf59046 User: rvesse Date: 2013-10-24 16:13:43 Summary: Note VIRT-382 fix 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. ------------------------------ ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 12, Issue 3 ************************************************ |
|
From: <tr...@do...> - 2013-10-24 14:16: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>In some cases Virtuoso transactions are not cleaned up</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
</tr>
<tr>
<td colspan="2"><b>Changes:</b></td>
</tr>
<tr>
<td colspan="2">
<ul>
<li>Status changed from "Confirmed" to "Completed"
</li>
<li>Resolution changed from "Unassigned" to "Fixed"
</li>
<li>Progress changed from "0 %" 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=382" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=382</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-10-24 14:15:57
|
<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>In some cases Virtuoso transactions are not cleaned up</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-10-24 03:15 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
A workaround for current code is to periodically call Dispose() on the VirtuosoManager instance and create a new instance</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=382" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=382</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-10-24 14:15:39
|
<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>In some cases Virtuoso transactions are not cleaned up</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Date:</b></td>
<td>2013-10-24 03:14 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Have confirmed that failure to close transactions in some cases was indeed the problem, I also identified a case where a query might be attempted against a closed database and fixed that as part of these changes.</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=382" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=382</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-10-24 13:44:17
|
<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>In some cases Virtuoso transactions are not cleaned up</td>
</tr>
<tr>
<td><b>Project:</b></td>
<td>Data.Virtuoso (dotNetRDF.Data.Virtuoso.dll)</td>
</tr>
<tr>
<td><b>Created By:</b></td>
<td>Rob Vesse</td>
</tr>
<tr>
<td><b>Milestone:</b></td>
<td>1.1.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Virtuoso Support</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">A user has reported an issue where sometimes Virtuoso transactions are left in the pending state and never get cleaned up. Having reviewed the code it looks like there are a couple of code paths where this could possibly happen around SPARQL queries and updates. The relevant code needs to be appropriately verified and if necessary modified so that transactions are always cleaned up.</td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=382" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=382</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-10-18 10:27:45
|
<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>Improve URI Interning support and memory usage</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-10-18 11:26 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The newly refactored resolution methods in UriFactory need to be updated to use the new interning mechanism and then we need to validate that memory usage is suitably lowered (which we strongly expect is the case). However doing that requires us to get the IO library into a suitable state that we can build and use the GraphBenchmarker tool to run benchmarks which we can compare with the default branch.</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=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</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-10-18 10:24:58
|
<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>Improve URI Interning support and memory usage</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"></td>
</tr>
</table>
<p>
More information on this issue can be found at
<a href="http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</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-10-18 10:24:36
|
<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>All URI resolution should happen in terms of Uri instances</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 "25 %"
</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=381" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=381</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-10-18 10:24:19
|
<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>All URI resolution should happen in terms of Uri instances</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-10-18 11:23 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
On the 1.9 branch the logic for URI resolution has been moved to UriFactory and has been rewritten to work in terms of Uri instances. The parser subsystem will still need to be refactored to use this appropriately.</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=381" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=381</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-10-18 10:23:19
|
<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>All URI resolution should happen in terms of Uri instances</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.9.0 Beta</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>Improvement</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Currently a lot of URI resolution involves creating Uri instances and converting them back and forth between strings which is inefficient and creates a lot of temporary objects which then have to be garbage collected. It would be much better if this resolution was done as much as possible directly using Uri instances.</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=381" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=381</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-10-18 10:20:12
|
<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>Consolidate IStoreReader and IRdfReader interfaces</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.9.0 Beta</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>Refactor</td>
</tr>
<tr>
<td><b>Description:</b></td>
</tr>
<tr>
<td colspan="2"><p>
As part of the data model refactoring in the 1.9 branch the ITripleStore interface is going away in favour of IGraphStore and we intend to remove the IStoreReader interface in favour of a generic IRdfReader interface. Making this consolidation requires several changes:</p>
<ul>
<li>
IRdfReader Load() methods should only take IRdfHandler instances</li>
<li>
IGraph based overloads can be provided as extension methods for backwards compatibility</li>
<li>
All IStoreReader implementations must be converted to IRdfReader and should call HandleQuad() in favour of HandleTriple() wherever appropriate</li>
<li>
Add IGraphStore based extension methods for IRdfReader</li>
<li>
GraphHandler needs to accept any quads received in the default graph as triples and discard any other quads received</li>
<li>
Replace StoreHandler with GraphStoreHandler, it should convert triples up into quads in the default graph</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=380" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=380</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-10-18 10:14:46
|
<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 configurable quality values for MimeTypeDefinition</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>Unscheduled</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</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>
Some systems don't like the broad accept header we send currently or they misinterpret it because we don't necessarily put our most favoured formats high up the list. It would be better if we associated each MIME type definition with a quality and sorted them appropriately when forming accept headers.</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=379" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=379</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-10-17 14:44:58
|
<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>Improve URI Interning support and memory usage</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-10-17 03:13 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The refactor as implemented does not use the SparseTrie, rather it instead interns URIs by segments rather than by characters which reduces the number of nodes in the tree thus reducing the memory usage an alternative way</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=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</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-10-17 14:14:15
|
<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>Improve URI Interning support and memory usage</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 "Planned" to "In Progress"
</li>
<li>Milestone changed from "Unscheduled" to "1.9.0 Beta"
</li>
<li>Progress changed from "0 %" to "80 %"
</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=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</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-10-17 14:13:06
|
<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>Improve URI Interning support and memory usage</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-10-17 03:12 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
This refactor is happening on the 1.9 branch as part of wider changes to how URIs and resolved and managed</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=330" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=330</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-10-15 11:07:00
|
<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>RDF/XML parser can OOM even in streaming mode</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-10-15 12:06 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
The main reported issue is now fixed and I can successfully read a chunk of the file in streaming mode without hitting a OOM exception. I still want to review the RDF/XML parser code some more to check there aren't other areas that might be affected by similar issues.</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=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</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-10-15 11:05:54
|
<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>RDF/XML parser can OOM even in streaming mode</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 "25 %" to "75 %"
</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=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</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-10-15 11:03:11
|
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: 8 new changesets (Bitbucket) 2. commit/dotnetrdf: rvesse: Added tag 1.0.1, 101 for changeset 880a1aab7365 (Bitbucket) 3. commit/dotnetrdf: 2 new changesets (Bitbucket) 4. commit/dotnetrdf: rvesse: Update out of date Copyright year (Bitbucket) 5. commit/dotnetrdf: 7 new changesets (Bitbucket) 6. commit/dotnetrdf: 2 new changesets (Bitbucket) 7. commit/dotnetrdf: rvesse: Comment out test on portable builds where GZip is not supported (CORE-378) (Bitbucket) 8. commit/dotnetrdf: rvesse: Exlcude .gz from license checks (Bitbucket) ---------------------------------------------------------------------- Message: 1 Date: Wed, 09 Oct 2013 16:05:06 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 8 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 8 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/ffa929ed5a05/ Changeset: ffa929ed5a05 User: rvesse Date: 2013-10-09 15:14:49 Summary: Update ChangeLog, ReadMe and ReleaseNotes in preparation for upcoming release Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/41832f1caeac/ Changeset: 41832f1caeac User: rvesse Date: 2013-10-09 15:18:13 Summary: More release preparation, set version to 1.0.1.2805 Affected #: 35 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f9615f9e32f5/ Changeset: f9615f9e32f5 Branch: stardog-2 User: rvesse Date: 2013-10-09 16:50:02 Summary: Initial incomplete work on adding support for Stardog 2.0 servers Affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/f215f29c8b83/ Changeset: f215f29c8b83 Branch: stardog-2 User: rvesse Date: 2013-10-09 16:59:18 Summary: Fix bad assumptions in some Stardog tests, verify that Stardog 2.0 is now appropriately supported Affected #: 2 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/2d8385dd1b79/ Changeset: 2d8385dd1b79 Branch: stardog-2 User: rvesse Date: 2013-10-09 17:10:02 Summary: Close Stardog 2.0 branch now Stardog 2.0 support is working Affected #: 0 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/19f9c4f6b003/ Changeset: 19f9c4f6b003 User: rvesse Date: 2013-10-09 17:10:20 Summary: Merge in Stardog 2.0 support Affected #: 10 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dae860e367c7/ Changeset: dae860e367c7 User: rvesse Date: 2013-10-09 17:11:59 Summary: Bump revision to 2809 as final release preparation Affected #: 33 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/880a1aab7365/ Changeset: 880a1aab7365 User: rvesse Date: 2013-10-09 17:55:53 Summary: Resolve a bug related to loaded Stardog connectors from RDF configuration files, fix a possible cross thread issue with StoreManager Affected #: 7 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: Wed, 09 Oct 2013 16:07:10 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Added tag 1.0.1, 101 for changeset 880a1aab7365 To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/fc2604f099a4/ Changeset: fc2604f099a4 User: rvesse Date: 2013-10-09 18:06:52 Summary: Added tag 1.0.1, 101 for changeset 880a1aab7365 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: Fri, 11 Oct 2013 09:19:56 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/5b649e05dbb8/ Changeset: 5b649e05dbb8 User: rvesse Date: 2013-10-10 12:16:01 Summary: Post release tidy up Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/02e3f9c33118/ Changeset: 02e3f9c33118 User: rvesse Date: 2013-10-11 11:19:19 Summary: Prep for next dev cycle, bump dev versions to 1.1.0 Affected #: 36 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, 11 Oct 2013 09:20:25 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Update out of date Copyright year To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/6b10dbfa3449/ Changeset: 6b10dbfa3449 User: rvesse Date: 2013-10-11 11:20:12 Summary: Update out of date Copyright year 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: Fri, 11 Oct 2013 11:11:33 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 7 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 7 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/dc48c03e72cc/ Changeset: dc48c03e72cc Branch: 1.9 User: rvesse Date: 2013-10-11 12:03:12 Summary: Finish consolidating nodes to a single interface such that core library compiles, add HasLanguage and HasDataType properties (CORE-329), consoliate hash code creation into central static method for reusability Affected #: 12 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/027cb31809b1/ Changeset: 027cb31809b1 Branch: 1.9 User: rvesse Date: 2013-10-11 12:10:51 Summary: Merge in latest changes from default Affected #: 83 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/57b32bc44f70/ Changeset: 57b32bc44f70 Branch: 1.9 User: rvesse Date: 2013-10-11 12:11:18 Summary: Update solution file Affected #: 1 file https://bitbucket.org/dotnetrdf/dotnetrdf/commits/873e10aaf92a/ Changeset: 873e10aaf92a Branch: 1.9 User: rvesse Date: 2013-10-11 12:25:25 Summary: Refactor Triple and Quad to use auto-properties, also force Quad to always have a non-null Graph field set to a constant DefaultGraphNode for the default graph Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/e27ed1105dd5/ Changeset: e27ed1105dd5 Branch: 1.9 User: rvesse Date: 2013-10-11 12:48:08 Summary: Refactor BaseGraphStore and GraphCollection to reflect the fact that Quad now uses Quad.DefaultGraphNode instead of null for representing quads in the default graph. Add a InDefaultGraph property to Quad Affected #: 7 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/3fa006f4c908/ Changeset: 3fa006f4c908 Branch: 1.9 User: rvesse Date: 2013-10-11 12:56:53 Summary: Fix an unintentional StackOverflowException introduced by node refactoring Affected #: 3 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/a39fd17699ce/ Changeset: a39fd17699ce Branch: 1.9 User: rvesse Date: 2013-10-11 13:11:19 Summary: Fix another possible StackOverflowException in LiteralNode. Simplify ThreadSafeTripleCollection code slightly and startt expanding new core API test suite 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: 6 Date: Tue, 15 Oct 2013 11:00:15 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: 2 new changesets To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 2 new commits in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/afb19268eb4c/ Changeset: afb19268eb4c Branch: CORE-378 User: rvesse Date: 2013-10-15 12:51:07 Summary: Fix for the main cause of CORE-378 plus unit test to verify Affected #: 8 files https://bitbucket.org/dotnetrdf/dotnetrdf/commits/c1c9169f07cf/ Changeset: c1c9169f07cf Branch: CORE-378 User: rvesse Date: 2013-10-15 12:56:51 Summary: Add some remarks to PagingHandler about circumstances when you may see less data than expected (CORE-378) 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, 15 Oct 2013 11:01:44 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Comment out test on portable builds where GZip is not supported (CORE-378) To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cbe61e9da6cf/ Changeset: cbe61e9da6cf Branch: CORE-378 User: rvesse Date: 2013-10-15 13:01:30 Summary: Comment out test on portable builds where GZip is not supported (CORE-378) 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: Tue, 15 Oct 2013 11:03:02 -0000 From: Bitbucket <com...@bi...> Subject: [dotNetRDF Commits] commit/dotnetrdf: rvesse: Exlcude .gz from license checks To: dot...@li... Message-ID: <201...@ap...> Content-Type: text/plain; charset="utf-8" 1 new commit in dotnetrdf: https://bitbucket.org/dotnetrdf/dotnetrdf/commits/cf4e300cd40f/ Changeset: cf4e300cd40f Branch: CORE-378 User: rvesse Date: 2013-10-15 13:02:43 Summary: Exlcude .gz from license checks 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. ------------------------------ ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk ------------------------------ _______________________________________________ dotNetRDF-commits mailing list dot...@li... https://lists.sourceforge.net/lists/listinfo/dotnetrdf-commits End of dotNetRDF-commits Digest, Vol 12, Issue 2 ************************************************ |
|
From: <tr...@do...> - 2013-10-15 10:35:52
|
<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>RDF/XML parser can OOM even in streaming mode</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 "Confirmed" to "In Progress"
</li>
<li>Progress changed from "0 %" to "25 %"
</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=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</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-10-15 10:31:36
|
<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>RDF/XML parser can OOM even in streaming mode</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-10-15 11:30 AM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
So the specific problem appears to be in the top level grammar production, it gathers all the events under the top level rdf:RDF element into a single event list and then passes it down to the next production. This has the effect of pre-caching all the data even when running in streaming mode hence the OOM when run against large files.</p>
<p>
The fix appears to be to introduce a wrapper event list which creates the illusion of being a new event list while really just wrapping the underlying event list and cutting off once the size of the underlying list drops below a given threshold. This should reduce memory usage for both the streaming and DOM parsing modes.</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=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</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-10-15 10:28:14
|
<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>RDF/XML parser can OOM even in streaming mode</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.1.0</td>
</tr>
<tr>
<td><b>Category:</b></td>
<td>Parsing</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>
A user question at <a href="http://answers.semanticweb.com/questions/24825/dotnetrdf-streaming-or-reading-in-chunks">http://answers.semanticweb.com/questions/24825/dotnetrdf-streaming-or-reading-in-chunks</a> has proven to be a bug in how the RDF/XML parser function. While the parser is intended to be streaming when used in streaming mode part of the parser logic means even though data is streamed from XML the entire document structure needs to be cached as events prior to parsing starting. While this is more memory efficient than the DOM parsing mode it does mean that the streaming mode is not truly streaming. With a large enough RDF/XML file the parser will still OOM fairly quickly.</p>
<p>
</p>
<p>
The code needs to be appropriately modified so that the streaming parser mode truly is streaming to avoid possible OOM errors.</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=378" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=378</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-10-11 11:15:06
|
<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>Add a HasLanguage and HasDataType properties to ILiteralNode</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 "Planned" to "In Progress"
</li>
<li>Progress changed from "0 %" to "80 %"
</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=329" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=329</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-10-11 11:14:54
|
<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>Add a HasLanguage and HasDataType properties to ILiteralNode</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-10-11 12:14 PM</td>
</tr>
<tr>
<td><b>Comment:</b></td>
</tr>
<tr>
<td colspan="2"><p>
Properties have been added to the revised INode interface in the 1.9 branch since all node types are now consoldiated onto a single node interface. Leaving this open since much code still needs to change to take account of these new properties. In particular the logic order often now needs to change since Language must be checked first as once we add RDF 1.1 implicit datatyping for literals all literals will have data types.</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=329" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=329</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-10-11 09:34:23
|
<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>Use null instead of RdfQueryException to propogate type errors in SPARQL Expression Evaluation</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>Milestone changed from "1.1.0" to "Unscheduled"
</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=327" target="_blank">http://www.dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=327</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.
