Build from source fails when port 3030 already in use

2022-11-17 Thread LB 

Hi,

just want to inform about a minor limitation in the current build process:

Building Jena from Maven fails when you have something already running 
on port 3030 (e.g. a Fuseki on standard port) because there is now some 
YARN test happening in Fuseki UI by using the frontend-maven-plugin:


Error log:


[INFO] --- frontend-maven-plugin:1.12.1:yarn (yarn run test:e2e) @ 
jena-fuseki-ui ---
[INFO] Running 'yarn run test:e2e -- --headless --browser chrome' in 
/home/LorenzBuehmann/tools/jena/jena-fuseki2/jena-fuseki-ui

[INFO] yarn run v1.22.17
[INFO] warning From Yarn 1.0 onwards, scripts don't require "--" for 
options to be forwarded. In a future version, any explicit "--" will be 
forwarded as-is to the scripts.
[INFO] $ bash -c 'concurrently --names "SERVER,TESTS" --prefix-colors 
"yellow,blue" --success "first" --kill-others "yarn run serve:fuseki" 
"vue-cli-service test:e2e ${0}"' --headless --browser chrome
[INFO] [SERVER] $ nodemon src/services/mock/json-server.js 
src/services/mock/db.json

[INFO] [SERVER] [nodemon] 2.0.20
[INFO] [SERVER] [nodemon] to restart at any time, enter `rs`
[INFO] [SERVER] [nodemon] watching path(s): *.*
[INFO] [SERVER] [nodemon] watching extensions: js,mjs,json
[INFO] [SERVER] [nodemon] starting `node 
src/services/mock/json-server.js src/services/mock/db.json`

[INFO] [SERVER] node:events:368
[INFO] [SERVER]   throw er; // Unhandled 'error' event
[INFO] [SERVER]   ^
[INFO] [SERVER]
[INFO] [SERVER] Error: listen EADDRINUSE: address already in use :::3030
[INFO] [SERVER] at Server.setupListenHandle [as _listen2] 
(node:net:1334:16)

[INFO] [SERVER] at listenInCluster (node:net:1382:12)
[INFO] [SERVER] at Server.listen (node:net:1469:7)
[INFO] [SERVER] at Function.listen 
(/home/LorenzBuehmann/tools/jena/jena-fuseki2/jena-fuseki-ui/node_modules/express/lib/application.js:635:24)
[INFO] [SERVER] at Object. 
(/home/LorenzBuehmann/tools/jena/jena-fuseki2/jena-fuseki-ui/src/services/mock/json-server.js:281:8)
[INFO] [SERVER] at Module._compile 
(node:internal/modules/cjs/loader:1101:14)
[INFO] [SERVER] at Object.Module._extensions..js 
(node:internal/modules/cjs/loader:1153:10)

[INFO] [SERVER] at Module.load (node:internal/modules/cjs/loader:981:32)
[INFO] [SERVER] at Function.Module._load 
(node:internal/modules/cjs/loader:822:12)
[INFO] [SERVER] at Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:81:12)

[INFO] [SERVER] Emitted 'error' event on Server instance at:
[INFO] [SERVER] at emitErrorNT (node:net:1361:8)
[INFO] [SERVER] at processTicksAndRejections 
(node:internal/process/task_queues:83:21) {

[INFO] [SERVER]   code: 'EADDRINUSE',
[INFO] [SERVER]   errno: -98,
[INFO] [SERVER]   syscall: 'listen',
[INFO] [SERVER]   address: '::',
[INFO] [SERVER]   port: 3030
[INFO] [SERVER] }
[INFO] [SERVER] [nodemon] app crashed - waiting for file changes before 
starting...



At the moment I'm doing

mvn -Dskip.yarn

to skip the YARN test - might not be ideal, but for my purposes it works.

I consider my post here more like a reference for other people having 
the same issue.



Regards,

Lorenz

[GitHub] [jena-site] kinow commented on pull request #131: RDF Patch documentation

2022-11-17 Thread GitBox 


kinow commented on PR #131:
URL: https://github.com/apache/jena-site/pull/131#issuecomment-1318746965

   > @kinow Thank you very much for the review. Should all be done now.
   
   Nice @afs! RDF Patch, LATERAL JOIN. Interesting features coming to Jena! 
Thank you!!!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #131: RDF Patch documentation

2022-11-17 Thread GitBox 


afs commented on code in PR #131:
URL: https://github.com/apache/jena-site/pull/131#discussion_r1025159994


##
source/documentation/rdf-patch/__index.md:
##
@@ -0,0 +1,191 @@
+---
+title: RDF Patch
+slug: index
+---
+
+This page describes RDF Patch. An RDF Patch is a set of changes to an
+[RDF dataset](https://www.w3.org/TR/rdf11-concepts/#section-dataset).
+The change are for triples, quads and prefixes.
+
+Changes to triples involving blank nodes are handled by using their system
+identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank
+nodes are not generated afresh each time the document is parsed.
+
+## Example
+
+This example ensures certain prefixes are in the dataset and adds some
+basic triples for a new subclass of ``.
+
+```
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#; .
+PA "owl" "http://www.w3.org/2002/07/owl#; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+## Structure
+
+The text format for an RDF Patch is N-Triples-like: it is a series of
+rows, each row ends with a `.` (DOT).  The tokens on a row are keywords,
+URIs, blank nodes, writen with their label (see below) or RDF Literals,
+in N-triples syntax.  A keyword follows the same rules as
+Turtle prefix declarations without a trailing `:`.
+
+A line has an operation code, then some number of items depending on 
+the operation.
+
+| Operation |   |
+| - | - |
+| `H`  | Header |
+| `TX``TC``TA` | Change block: transactions|
+| `PA``PD` | Change: Prefix add and delete |
+| `A``D`| Change: Add and delete triples and quads |
+
+The general structure of an RDF patch is a header (possible empty), then a
+number of change blocks.
+
+Each change block is a transaction. Transactions can be explicit recorded ('TX'
+start, `TC` commit) to include multiple transaction in one patch. They are not
+required. If not present, the patch should be applied atomically to the data.
+
+```
+header
+TX
+Quad, triple or prefix changes
+TC or TA
+```
+
+Multiple transaction blocks are allowed for multiple sets of changes in one
+patch.
+
+A binary version based on [RDF Thrift](../io/rdf-binary/) is provided.
+Parsing binary compared to text for N-triples achieves a x3-x4 increase in
+throughput.
+
+### Header
+
+The header provides for basic information about patch. It is a series of
+(key, value) pairs.
+
+It is better to put complex metadata in a separate file and link to it
+from the header, but certain information is best kept with the patch. An 
example
+used by Delta is to keep the identifer of the global version id of the dataset

Review Comment:
   Revised that section.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [jena-site] afs commented on a diff in pull request #131: RDF Patch documentation

2022-11-17 Thread GitBox 


afs commented on code in PR #131:
URL: https://github.com/apache/jena-site/pull/131#discussion_r1025158734


##
source/documentation/rdf-patch/__index.md:
##
@@ -0,0 +1,191 @@
+---
+title: RDF Patch
+slug: index
+---
+
+This page describes RDF Patch. An RDF Patch is a set of changes to an
+[RDF dataset](https://www.w3.org/TR/rdf11-concepts/#section-dataset).
+The change are for triples, quads and prefixes.
+
+Changes to triples involving blank nodes are handled by using their system
+identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank
+nodes are not generated afresh each time the document is parsed.
+
+## Example
+
+This example ensures certain prefixes are in the dataset and adds some
+basic triples for a new subclass of ``.
+
+```
+TX .
+PA "rdf" "http://www.w3.org/1999/02/22-rdf-syntax-ns#; .
+PA "owl" "http://www.w3.org/2002/07/owl#; .
+PA "rdfs" "http://www.w3.org/2000/01/rdf-schema#; .
+A   
 .
+A   
 .
+A   
"SubClass" .
+TC .
+```
+
+## Structure
+
+The text format for an RDF Patch is N-Triples-like: it is a series of
+rows, each row ends with a `.` (DOT).  The tokens on a row are keywords,
+URIs, blank nodes, writen with their label (see below) or RDF Literals,
+in N-triples syntax.  A keyword follows the same rules as
+Turtle prefix declarations without a trailing `:`.
+
+A line has an operation code, then some number of items depending on 
+the operation.
+
+| Operation |   |
+| - | - |
+| `H`  | Header |
+| `TX``TC``TA` | Change block: transactions|
+| `PA``PD` | Change: Prefix add and delete |
+| `A``D`| Change: Add and delete triples and quads |
+
+The general structure of an RDF patch is a header (possible empty), then a
+number of change blocks.
+
+Each change block is a transaction. Transactions can be explicit recorded ('TX'
+start, `TC` commit) to include multiple transaction in one patch. They are not
+required. If not present, the patch should be applied atomically to the data.
+
+```
+header
+TX
+Quad, triple or prefix changes
+TC or TA
+```
+
+Multiple transaction blocks are allowed for multiple sets of changes in one
+patch.
+
+A binary version based on [RDF Thrift](../io/rdf-binary/) is provided.
+Parsing binary compared to text for N-triples achieves a x3-x4 increase in
+throughput.
+
+### Header
+
+The header provides for basic information about patch. It is a series of
+(key, value) pairs.
+
+It is better to put complex metadata in a separate file and link to it
+from the header, but certain information is best kept with the patch. An 
example
+used by Delta is to keep the identifer of the global version id of the dataset

Review Comment:
   Delta is [RDF Delta](https://afs.github.io/rdf-delta)  - the whole change 
propagation, replication and high-availability system. 
   
   There should not be any mention of it in this patch documentation.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org