CarbonLDP/carbonldp-js-sdk

CarbonLDP JavaScript SDK chat room

Miguel Aragón

@MiguelAraCo

Are you waiting for the promise to finish, or are you sending both of them at the same time?

AlexSerrano22

@AlexSerrano22

I'm waiting for the promise when this is resolved, I try to create the next document

Miguel Aragón

@MiguelAraCo

Could you paste your code?

AlexSerrano22

@AlexSerrano22

yeap give me some minutes

AlexSerrano22

@AlexSerrano22

I'm using vue, I write this code on the app.vue and I'm using the hot reload, any time that some change is detected the app is reloaded..

CarbonService.createDocument: function(carbon, rootPath, document, slug ){
    return carbon.documents.createChild( "/"+rootPath, document, slug );
}

let carbon = CarbonService.init();
let something = {};
let slug = "users";

CarbonService.createDocument(carbon, "/", something, slug).then(
( [ persistedProject, response ] ) => {
    console.log( something === persistedProject ); // true
    console.log( something.id ); // document's URI
}
).catch( console.error );

I run the script to create a document and I wait to see on the browser console the log of true and document URI, after that I'm going to my code again and change the slug variable to this:

CarbonService.createDocument: function(carbon, rootPath, document, slug ){
    return carbon.documents.createChild( "/"+rootPath, document, slug );
}

let carbon = CarbonService.init();
let something = {};
let slug = "roles";

CarbonService.createDocument(carbon, "/", something, slug).then(
( [ persistedProject, response ] ) => {
    console.log( something === persistedProject ); // true
    console.log( something.id ); // document's URI
}
).catch( console.error );

the app is reloaded and run the script again, and is there where I see the 409 error on the browser console.

Miguel Aragón

@MiguelAraCo

I just replicated your issue and identified the cause

There' s a bug in the SDK that is triggering this behavior

AlexSerrano22

@AlexSerrano22

cool, do you need that I post this on github?

Miguel Aragón

@MiguelAraCo

Well, the bug we found may not be causing your issue after all

In your code, the requests are being sent to //

Because of this: "/"+rootPath

AlexSerrano22

@AlexSerrano22

sorry this was my error when I sent you the code, currently, I only send the "/"

Miguel Aragón

@MiguelAraCo

:+1:

Can you open your developer tools and send us a screenshot of the requests being sent?

AlexSerrano22

@AlexSerrano22

sure, one moment

AlexSerrano22

@AlexSerrano22

ammm I thought about other things that I did yesterday, and another thing that I did was delete a document on the workbench and after that, I begin to see the error logs, and I understand that is because the parent document was "locked". probably this was the cause of the error. but how I can know if the parent document is locked, what happens if some request is sent to create a child in the same parent document? Will I re-send the request until the document can be created?

Miguel Aragón

@MiguelAraCo

Documents should only be locked while something is being done to them

So if you perform an action, that action finishes, and the document is still locked, there's an issue with the platform

Even then the lock expires after a few minutes

Right now there isn't a direct way to check if a document is locked other than trying something and receiving a 409

It is an internal mechanism after all

Normally you would program a retry mechanism with a configurable delay and a number of retries before failing

For now, you can remove any dead locks your platform may have by following these steps:

Shut down your platform: docker stop <container-name>
Delete the directory: <carbon-directory>/data/zookeeper
Start your platform again: docker start <container-name

Like I said, this shouldn't happen, so please let us know if a lock isn't being released and the steps you took to get there

AlexSerrano22

@AlexSerrano22

I think the platform works as designed because after a few minutes I was able to create a document, but thanks for clarifying me why I receive the 409 error. :)

Miguel Aragón

@MiguelAraCo

Nice :+1:

Thanks for reaching out :smile:

Miguel Aragón

@MiguelAraCo

Just published a new version v1.0.0-alpha.8 that fixes a minor bug. Please update your projects to use this version if you are using the alpha line

AlexSerrano22

@AlexSerrano22

cool, thanks

Alex Arriaga

@alex-arriaga

Hi, we are interested in migrating data from a previous Carbon LDP version; at this moment, we exported the data into JSON files and we are going to make some scripting to insert all that data in another Carbon instance…

Is that the right/shortest path?

We think the export/import process would not be compatible between legacy versions and the newest Alpha, right?

Miguel Aragón

@MiguelAraCo

Yes, the import/export mechanism we had on the previous version isn't compatible with the new one

There's no migration path yet

Manually importing/exporting it is the only approach as of now

Alex Arriaga

@alex-arriaga

Got it.

Alex Arriaga

@alex-arriaga

—> (deleted to place it in carbondlp channel instead)

Alex Arriaga

@alex-arriaga

Another question: I read somewhere Carbon LDP will provide some real time capabilities; is that still in development? Or can we use right away with the JavaScript SDK?

Miguel Aragón

@MiguelAraCo

https://carbonldp.com/documentation/v1.0.x/javascript-sdk/real-time-capabilities/

Alex Arriaga

@alex-arriaga

:ok_hand:

Miguel Aragón

@MiguelAraCo

My advise for users that have used previous versions of Carbon would be: read all the documentation again. A lot of things have changed

AlexSerrano22

@AlexSerrano22

Hi guy, I'm trying to create a project with a custom schema but I'm missing a dateTime value when the document is created on carbon, this is an example of my code:

carbonSchemas.PROJECT = {
    "forecastID": {
      "@id": "tms:forecastID",
      "@type": "string"
    },
    "name": {
      "@id": "https://schema.org/name",
      "@type": "string"
    },
    "updatedDate": {
      "@id": "tms:updatedDate",
      "@type": "dateTime"
    }
}
carbon.extendObjectSchema(`${CONTEXT_URL}#ForecastProject`, carbonSchemas.PROJECT);

let project = {
          "forecastID": "XXXXX",
          "color": "orange",
          "name": "someName",
          "updatedDate": "2018-01-17T04:14:54.150Z",
          "types": ["http://tms.base22.com/ns#ForecastProject"]
        }
carbon.documents.createChild("/projects/", project )...

you could see my document here: http://carbonldp.webtraining.zone:8083/projects/4132556623722936140/

Alex Arriaga

@alex-arriaga

Maybe the “updatedDate” needs to be an actual Date JavaScript object?

AlexSerrano22

@AlexSerrano22

ok let me try

Alex Arriaga

@alex-arriaga

let project = {
          "forecastID": "XXXXX",
          "color": "orange",
          "name": "someName",
          "updatedDate": new Date(),
          "types": ["http://tms.base22.com/ns#ForecastProject"]
        }

Rodolfo Aguirre

@roddolf

Yes, Alex Arriaga is right, the value needs to be a Date object

AlexSerrano22

@AlexSerrano22

cool, thanks @alex-arriaga and @roddolf

Alex Arriaga

@alex-arriaga

:ok_hand:

AlexSerrano22

@AlexSerrano22

Hello, I'm trying to add a type to a document but I'm receiving a 400 error code, Error: The attempt of parsing the request's body failed
this is the request response:

[{"@id":"_:node1c40v47nrx16996","@type":["https://carbonldp.com/ns/v1/platform#ErrorResponse"],"https://carbonldp.com/ns/v1/platform#error":[{"@id":"_:node1c40v47nrx16997"}],"https://carbonldp.com/ns/v1/platform#httpStatusCode":[{"@type":"http://www.w3.org/2001/XMLSchema#int","@value":"400"}],"https://carbonldp.com/ns/v1/platform#requestID":[{"@value":"32b1cdcc-5d3b-4901-9da2-e08b9eb58a60"}]},{"@id":"_:node1c40v47nrx16997","@type":["https://carbonldp.com/ns/v1/platform#Error"],"https://carbonldp.com/ns/v1/platform#errorCode":[{"@value":"0x6970"}],"https://carbonldp.com/ns/v1/platform#errorMessage":[{"@language":"es","@value":"The attempt of parsing the request's body failed"}],"https://carbonldp.com/ns/v1/platform#errorParameters":[{"@id":"_:node1c40v47nrx16998"}]},{"@id":"_:node1c40v47nrx16998","@type":["https://carbonldp.com/ns/v1/platform#Map"],"https://carbonldp.com/ns/v1/platform#entry":[{"@id":"_:node1c40v47nrx16999"},{"@id":"_:node1c40v47nrx17000"},{"@id":"_:node1c40v47nrx17001"}]},{"@id":"_:node1c40v47nrx16999","https://carbonldp.com/ns/v1/platform#key":[{"@value":"column"}],"https://carbonldp.com/ns/v1/platform#value":[{"@type":"http://www.w3.org/2001/XMLSchema#int","@value":"57"}]},{"@id":"_:node1c40v47nrx17000","https://carbonldp.com/ns/v1/platform#key":[{"@value":"parserErrorMessage"}],"https://carbonldp.com/ns/v1/platform#value":[{"@value":"Encountered \" <IRI> \"<http://tms.base22.com/ns#ForecastPerson> \"\" at line 1, column 57.\nWas expecting:\n    \":\" ...\n    "}]},{"@id":"_:node1c40v47nrx17001","https://carbonldp.com/ns/v1/platform#key":[{"@value":"line"}],"https://carbonldp.com/ns/v1/platform#value":[{"@type":"http://www.w3.org/2001/XMLSchema#int","@value":"1"}]}]

and this is my code:

carbon.documents.get("users/").then(( [ user, response ] ) => {
         user.addType("http://tms.base22.com/ns#ForecastPerson");
         return user.save();
      }).then(
        ( [ user, response ] ) => {
          console.log(user);
        }
      ).catch( console.error );

and my request payload is:
Add { <http://carbonldp.webtraining.zone:8083/users/> a <http://tms.base22.com/ns#ForecastPerson>. }.

I saw that the error is because the parser encountered <IRI>, my question is: can't I add a custom type? or which is the format for add a type with the function addType?

Where communities thrive

People

Repo info

Activity