Hi Andy, On Thu, Mar 5, 2015 at 10:54 AM, Andy Seaborne <a...@apache.org> wrote: >> Some of the currently non-working features were previously working. > > > What specifically? On the query page or elsewhere? > > There are different changes from different origins - I'm trying to pin down > which we're talking about in case it's a systematic, and single root, issue.
I think the Yasqe update complicates the UX of the query page (esp pivot tables, but there's a separate discussion on that). Yasqe also removed codemirror, which took out the validation pages, which were then removed as broken links. Some other minor things, but tbh some of those might have been lingering issues from the previous round of work. >> It also looks like backup is currently not working due to a >> transaction problem. I'll need to confirm that, will add a Jira if >> necessary. > > > I have just checked and "it works for me" except that they get placed in the > wrong directory. No UI issue. Recorded as JENA-894. Hmm. I get the following on the Fuseki console: 2015-03-05 11:14:02] Admin INFO [8] POST http://localhost:3030/$/backup/ds [2015-03-05 11:14:02] Admin INFO [8] Backup dataset /ds [2015-03-05 11:14:02] Server INFO Task : 1 : backup [2015-03-05 11:14:02] Server INFO [Task 1] starts : backup [2015-03-05 11:14:02] Admin INFO [8] 200 OK (41 ms) [2015-03-05 11:14:02] Backup INFO [8] >>>> Start backup /ds -> backups/ds_2015-03-05_11-14-02 [2015-03-05 11:14:02] Server INFO [9] GET http://localhost:3030/$/tasks/1 [2015-03-05 11:14:02] Server INFO [9] Task 1 [2015-03-05 11:14:02] Server INFO [9] 200 OK (2 ms) [2015-03-05 11:14:02] Backup INFO [8] **** Exception in backup com.hp.hpl.jena.tdb.transaction.TDBTransactionException: Not in a transaction at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:106) at com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.get(DatasetGraphTransaction.java:1) at com.hp.hpl.jena.sparql.core.DatasetGraphTrackActive.getDefaultGraph(DatasetGraphTrackActive.java:91) at org.apache.jena.riot.system.RiotLib.prefixMap(RiotLib.java:257) at org.apache.jena.riot.RDFDataMgr.write$(RDFDataMgr.java:1331) at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1205) at org.apache.jena.riot.RDFDataMgr.write(RDFDataMgr.java:1195) at org.apache.jena.fuseki.mgt.Backup.backup(Backup.java:82) at org.apache.jena.fuseki.mgt.ActionBackup$BackupTask.run(ActionBackup.java:76) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at org.apache.jena.fuseki.async.AsyncTask.call(AsyncTask.java:94) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) [2015-03-05 11:14:02] Server INFO [Task 1] finishes : backup [2015-03-05 11:14:02] Server INFO [10] GET http://localhost:3030/$/tasks/1 [2015-03-05 11:14:02] Server INFO [10] Task 1 [2015-03-05 11:14:02] Server INFO [10] 200 OK (2 ms) Any suggestions on diagnostics to probe why my setup might be different to yours? I started fuseki with --loc=/var/lib/tdb/ea/rbwd /ds >> How long do I have before we freeze the release? > > > -5 days :-) OK. /me needs to pay more attention! Ian
