[jira] [Created] (JENA-2055) handle properly the denied access generated by jena-permission security evaluator

[info parlepeuple (Jira)]

info parlepeuple created JENA-2055:
--

 Summary: handle properly the denied access generated by 
jena-permission security evaluator
 Key: JENA-2055
 URL: https://issues.apache.org/jira/browse/JENA-2055
 Project: Apache Jena
  Issue Type: Bug
  Components: Fuseki
Affects Versions: Jena 3.17.0
 Environment: jena-fuseki 3.17.0

openjdk version "1.8.0_275"
Reporter: info parlepeuple
 Attachments: 
0001-handle-properly-the-denied-access-generated-by-jena-.patch

When the dataset is secured with [jena 
permission|https://jena.apache.org/documentation/permissions/] , and some 
access is denied, an exception is thrown from the SecuredGraph.

This exception is not catched in SPARQLQueryProcessor, which results in a 500 
error returned to the HTTP client.

exception OperationDeniedException should return a 403, not a 500.

 

attached is the patch !

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena-site] kinow commented on pull request #42: Use main instead of master

[GitBox]

kinow commented on pull request #42:
URL: https://github.com/apache/jena-site/pull/42#issuecomment-782755073


   Fixed conflicts, merging :+1: 



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.

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

[GitHub] [jena-site] kinow merged pull request #42: Use main instead of master

[GitBox]

kinow merged pull request #42:
URL: https://github.com/apache/jena-site/pull/42


   



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.

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

[jira] [Commented] (JENA-2052) run github action maven.yml also for windows server and macos

[Andy Seaborne (Jira)]

[ 
https://issues.apache.org/jira/browse/JENA-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287696#comment-17287696
 ] 

Andy Seaborne commented on JENA-2052:
-

Seen the PR - thanks!

Just as background:

The project uses [a number of Jenkins 
jobs|https://ci-builds.apache.org/job/Jena/] including one for windows. There's 
more control (like triggering them on demand).

The use of Github actions directly by Apache projects, that is, running on the 
Apache account, is quite new and because it is one account for all projects, 
there are issues with running out of credits (the Foundation does, I believe, 
get more than the mininum per account). Its settling down as. Jena is a simple 
build, other projects are not.

The windows job passes on Jenkins - so we can deduce that the job does not run 
of a filesystem with path including an "~". Good to catch this. Raiused as 
JENA-2054.

We don't have regular macOS - the Jenkins installation no longer has mac build 
servers so it's good to see that here. (MacOS tests do get done during the 
release process.)

The macOS job looks like an environment timing issue - the timeout isn't 
happening because the query is executing. Timeout tests are hard to get stable 
- sometimes the query runs to completion before the timeout happens due to 
scheduling or clock weirdness. But setting the query execution so long to 
guarantee the timeout makes local development less nice.


> run github action maven.yml also for windows server and macos
> -
>
> Key: JENA-2052
> URL: https://issues.apache.org/jira/browse/JENA-2052
> Project: Apache Jena
>  Issue Type: New Feature
>  Components: Build
>Reporter: Øyvind Gjesdal
>Priority: Minor
>
> I've looked at the documentation for github actions 
> [https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-running-with-more-than-one-operating-system]
>  and have wanted to try out running jobs on multiple OS'es.
>  
> Incoming PR (WIP) if it is of interest :) I've not used jira/github before, 
> but I think I should check out a branch named by the Jena issue, created from 
> this request?
>  
> Both windows and macos currently report failing tests from main branch:
> (under Build with maven)
> windows: 
> [https://github.com/OyvindLGjesdal/jena/runs/1930240867?check_suite_focus=true]
> macos: 
> [https://github.com/OyvindLGjesdal/jena/runs/1930240890?check_suite_focus=true]
>  
> I've not found out yet how to continue the CI tasks in the other OS'es if one 
> of them fails, while still returning an error on completion. The second 
> commit completes green when the continue on error: true is set, however there 
> is no indication they failed, without viewing the job.
>  
> I thought maybe "if: sucess() | failure()" would work, but it seems the other 
> jobs are still canceled, when the first one fails. I'll see if I can read a 
> bit more to understand how this works and if it is possible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (JENA-2054) File IRIs with "~" in the direct path cause test failure.

[Andy Seaborne (Jira)]

 [ 
https://issues.apache.org/jira/browse/JENA-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Seaborne reassigned JENA-2054:
---

Assignee: Andy Seaborne

> File IRIs with "~" in the direct path cause test failure.
> -
>
> Key: JENA-2054
> URL: https://issues.apache.org/jira/browse/JENA-2054
> Project: Apache Jena
>  Issue Type: Improvement
>Reporter: Andy Seaborne
>Assignee: Andy Seaborne
>Priority: Major
>
> This is via the report in JENA-2052 (adding OS's to the GH action).
> It looks like the "~" isn't being handled correctly.
> {noformat}
> TestInMemDatasetAssembler
> Error:  Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.058 
> s <<< FAILURE! - in org.apache.jena.sparql.core.assembler.TS_Assembler
> Error:  
> directDataLinkForDefaultAndNamedGraphs(org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler)
>   Time elapsed: 0.004 s  <<< ERROR!
> org.apache.jena.riot.RiotException: [line: 2, col: 70] Bad IRI: 
> 
>  : 
> 
>  Code: 61/SCHEME_PATTERN_MATCH_FAILED in PATHQUERY: The scheme specific 
> syntax rules are violated.
>   at 
> org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.assemble(TestInMemDatasetAssembler.java:65)
>   at 
> org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.directDataLinkForDefaultAndNamedGraphs(TestInMemDatasetAssembler.java:99)
> Error:  
> directDataQuadsURI(org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler)
>   Time elapsed: 0.012 s  <<< ERROR!
> org.apache.jena.riot.RiotException: [line: 1, col: 70] Bad IRI: 
> 
>  : 
> 
>  Code: 61/SCHEME_PATTERN_MATCH_FAILED in PATHQUERY: The scheme specific 
> syntax rules are violated.
>   at 
> org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.assemble(TestInMemDatasetAssembler.java:65)
>   at 
> org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.directDataQuadsURI(TestInMemDatasetAssembler.java:138)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (JENA-2054) File IRIs with "~" in the direct path cause test failure.

[Andy Seaborne (Jira)]

Andy Seaborne created JENA-2054:
---

 Summary: File IRIs with "~" in the direct path cause test failure.
 Key: JENA-2054
 URL: https://issues.apache.org/jira/browse/JENA-2054
 Project: Apache Jena
  Issue Type: Improvement
Reporter: Andy Seaborne


This is via the report in JENA-2052 (adding OS's to the GH action).

It looks like the "~" isn't being handled correctly.

{noformat}
TestInMemDatasetAssembler

Error:  Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.058 s 
<<< FAILURE! - in org.apache.jena.sparql.core.assembler.TS_Assembler
Error:  
directDataLinkForDefaultAndNamedGraphs(org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler)
  Time elapsed: 0.004 s  <<< ERROR!
org.apache.jena.riot.RiotException: [line: 2, col: 70] Bad IRI: 

 : 

 Code: 61/SCHEME_PATTERN_MATCH_FAILED in PATHQUERY: The scheme specific syntax 
rules are violated.
at 
org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.assemble(TestInMemDatasetAssembler.java:65)
at 
org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.directDataLinkForDefaultAndNamedGraphs(TestInMemDatasetAssembler.java:99)

Error:  
directDataQuadsURI(org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler)
  Time elapsed: 0.012 s  <<< ERROR!
org.apache.jena.riot.RiotException: [line: 1, col: 70] Bad IRI: 

 : 

 Code: 61/SCHEME_PATTERN_MATCH_FAILED in PATHQUERY: The scheme specific syntax 
rules are violated.
at 
org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.assemble(TestInMemDatasetAssembler.java:65)
at 
org.apache.jena.sparql.core.assembler.TestInMemDatasetAssembler.directDataQuadsURI(TestInMemDatasetAssembler.java:138)
{noformat}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [jena-site] afs merged pull request #43: Note modules as "retired"

[GitBox]

afs merged pull request #43:
URL: https://github.com/apache/jena-site/pull/43


   



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.

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

[GitHub] [jena-site] afs commented on a change in pull request #42: Use main instead of master

[GitBox]

afs commented on a change in pull request #42:
URL: https://github.com/apache/jena-site/pull/42#discussion_r579658923



##
File path: build-script
##
@@ -6,7 +6,7 @@
 ## ---
 
 # Specify source and site branches
-SOURCE="master"
+SOURCE="main"

Review comment:
   Hazy memory but I think the first setup did not use the `Jenkinsfile` 
feature on Jenkins; instead it was a bash script and `build-script` is copy for 
reference.





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.

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

Re: ApacheCon 2021

[Claude Warren]

Can you run a demo?

A demo and a look ahead to V4 would be nice.

I can talk about the permissions layer or the query builder, but it would
be nice to have a presentation showing the Jena in a real world application.

@Andy Seaborne  would you be willing to talk about V4 and
the changes therein?

Perhaps we should take this discussion to the users list and see if there
is interest over there.

Thoughts?
Claude

On Fri, Feb 19, 2021 at 8:54 PM Marco Neumann 
wrote:

> I'd like to see a demo session.
>
> On Thu, Feb 18, 2021 at 6:52 PM Claude Warren  wrote:
>
> > arrrgg.  What was I thinking??  I don't know either.  I meant to ping
> this
> > topic to see if there was any interest before dropping it.  So if you are
> > interested in a Jena topic at ApacheCon this year let me know and I will
> > propose it and drive it forward as best I can.
> >
> > Claude
> >
> > On Thu, Feb 18, 2021 at 6:50 PM Claude Warren  wrote:
> >
> > > not hearing any suggestions on this topic. I will drop it.
> > >
> > > Thx
> > >
> > > On Wed, Feb 17, 2021 at 5:41 PM Marco Neumann  >
> > > wrote:
> > >
> > >> I am in touch with the Apache spatial group about the 2021 slots, and
> it
> > >> looks like I will dedicate a strand to linked data and geosparql with
> > jena
> > >> here in spatial track.
> > >>
> > >> Marco
> > >>
> > >>
> > >>
> > >> On Wed, Feb 17, 2021 at 11:43 AM Claude Warren 
> > wrote:
> > >>
> > >> > There is a call for tracks for ApacheCon 2021.  Do we want to
> propose
> > a
> > >> > track again this year?  Perhaps we could get some presentations from
> > >> users.
> > >> >
> > >> > FYI:  I gave an impromptu talk about Jena at the Apache "table"
> during
> > >> > FOSDEM at the beginning of this month.
> > >> >
> > >> > Claude
> > >> >
> > >> > --
> > >> > I like: Like Like - The likeliest place on the web
> > >> > 
> > >> > LinkedIn: http://www.linkedin.com/in/claudewarren
> > >> >
> > >>
> > >>
> > >> --
> > >>
> > >>
> > >> ---
> > >> Marco Neumann
> > >> KONA
> > >>
> > >
> > >
> > > --
> > > I like: Like Like - The likeliest place on the web
> > > 
> > > LinkedIn: http://www.linkedin.com/in/claudewarren
> > >
> >
> >
> > --
> > I like: Like Like - The likeliest place on the web
> > 
> > LinkedIn: http://www.linkedin.com/in/claudewarren
> >
>
>
> --
>
>
> ---
> Marco Neumann
> KONA
>


-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren