Sending Statements to an LRS

[vbhayden]

Afternoon, team!

One of our external partners is reporting that the most recent codebase seems to have an issue sending statements to an LRS. I'd assumed this was just a small thing with a missing / on some LRS endpoint, but one of my engineers reported the same problem.

Did the process change for sending statements to an LRS?

Thanks,
-Trey

[FlorianTolk]

Here is the setup we are trying to use on the UI

It does not seem to even be trying to send the xAPI statements to an LRS, and is just defaulting to downloading them.

[cliffcaseyyet]

There actually was a very recent update to address an issue with LRS sends stemming from some earlier work. The issue was in the DS (server-side) repo not this UI one, can you confirm that the latest master version of client and server are running in the environment experiencing the issue?

Thanks,
Cliff

[FlorianTolk]

Just pulled all of the code (both UI and API) from GitHub and recompiled, and still seem to run into the same problem.

Statements are being generated. but despite the "send to LRS" box being checked, statements are installed instead of sent, and no errors seem to appear in the Debugger or console.

[cliffcaseyyet]

@FlorianTolk @vbhayden been trying to get to the bottom of this today. I also made clean installs and recompiles of master today to try to figure it out. First off we definitely need better error messaging when the LRS push fails because it can fail rather silently (i'm opening a ticket for that internally), but unfortunately when all my credentials and endpoints are in place I can't seem to reproduce the issue (tried with two flavors of LRS). Also the download of statements isn't an indicator either way because it does that regardless. However it does indicate, if the download has statements, that the sim was successful so we can probably rule sim params/profile out.

A couple of debug ideas:

• It doesn't expect the trailing slash, and explicitly appends '/statements' so in my case it was just "https://{host}/xapi"
• One thing that kept catching me (and MAY fail silently which as i mentioned we need to fix) is if the LRS already contains those statements from a prior run. DATASIM being deterministic, having the same params and seed in two runs would result in a conflict error from most LRS implementations.
• LRS integration auth is purely basic auth, have you tried posting the same statements via curl or postman?

Barring any of those what i might do is just make a branch to sloppily spit out whatever the LRS says in response and point you guys to it for a test so you can at least see if there's some noise from your LRS endpoint.

-Cliff

[FlorianTolk]

Good Morning Cliff,
I managed to curl those statements (once I removed the id field, a lot of these already existed in the public adl lrs) once I used the -k flag.
However, removing the trailing slash did not work. I think the fact that many of these statements have duplicate ids may be what is causing it to fail to send any statements to the LRS? I am unsure how DATASIM handles actually sending xAPI statements