PubNub EON not rendering History - charts

Unable to figure out why the EON spline chart is not loading history upon load (Yes, the Storage and Playback features are enabled) . The chart will render data properly as data comes in and no errors are visible in the console. Any clues as to what may be going on?
eon.chart({
channel: channel,
history: true,
flow: true,
pubnub: pubnub,
debug: true,
generate: {
bindto: '#chart',
data: {
type: 'spline',
labels: false
}
},
transform: function(m) {
return { eon: {
'temp': m.temp
}}
}
});
And here is the output from the console:
EON-CHART: PubNub: Subscribed to runtimewareiotchannel
eon.js:7657 EON-CHART: Status: Restoring from history
eon.js:7657 EON-CHART: History: Retrieving messages from undefined
eon.js:7657 EON-CHART: Status: Chart Animation Enabled
eon.js:7657 EON-CHART: History: 10 messages found
eon.js:7657 EON-CHART: History: Complete... Rendering
eon.js:7657 EON-CHART: History: Retrieving messages from 14689036992721526
eon.js:7657 EON-CHART: History: 1 messages found
eon.js:7657 EON-CHART: History: Complete... Rendering
The data posted to PubNub is as follows - very simple:
{
"temp": 76.662498
}
Thanks!
Derek

This was a temporary issue today and should be resolved. See this example:
http://pubnub.github.io/eon-chart/examples/history.html

Related

Invalid parameters error on createConversation in #google-cloud/contact-center-insights SDK

I'm trying to call createConversation function of CCAI insights SDK #google-cloud/contact-center-insights but getting below error
ERROR ==> Error: 3 INVALID_ARGUMENT: Request contains an invalid argument.
What would be the correct request payload? I'm not able to find sample request payload for this function.
I'm using below code:
const [conversation] = await client.createConversation({
parent: client.locationPath(projectId, 'us-central1'),
conversation: {
medium: 'CHAT',
name: 'TestModel',
transcript: {
transcriptSegments: [{
segmentParticipant: {
role: 'HUMAN_AGENT',
userId: '1234'
},
text: 'Thank you for calling IBC, how can I help you today?',
confidence: 0.90,
sentiment: {
magnitude: 0.2,
score: 0.9
},
}]
}
}
});
console.info(`Created `, conversation.name);
Note: It's working for below github code but I need to send the payload in transcript format.
ccai-insight-github code
And even if we store the conversation in Storage bucket, what would be the format?
Thanks

Rocket.Chat Live Chat room subscription problem

I'm trying to build my own chat frontend for the Rocket.Chat Live Chat.
But currently I have the problem, that I can't subscribe to a live chat room for listening.
1) RealtimeAPI: I connect to the the rocket.chat webservice
2) RealtimeAPI: I register the guest user with "livechat:registerGuest"
3) Rest API: I create a room with "/api/v1/livechat/room?token="
I get this as answer:
{ room:
{ _id: '43TJpc3q9eRjqhFXW',
msgs: 1,
usersCount: 2,
lm: '2020-05-26T13:29:21.965Z',
fname: 'jxkyZ72fFneYCMNnM',
t: 'l',
ts: '2020-05-26T13:29:21.965Z',
departmentId: '2DKbAHmjxHtEL8g3n',
v:
{ _id: 'D6B7wJ7kcFb2QmR2u',
username: 'guest-83',
token: 'jxkyZ72fFneYCMNnM',
status: 'online' },
cl: false,
open: true,
waitingResponse: true,
_updatedAt: '2020-05-26T13:29:22.047Z',
servedBy:
{ _id: 'irByyRx98ii4wjGmj',
username: 'Admin',
ts: '2020-05-26T13:29:22.019Z' } },
newRoom: true,
success: true }
I use this _id: '43TJpc3q9eRjqhFXW' value for the subscription room name, all others cause "invalid event"
4) I try to subscribe to "stream-room-messages" and to "stream-livechat-room", but for both I receive only {"msg":"nosub","id":"3"} and not something like this
{
"msg":"ready",
"subs":[
"43TJpc3q9eRjqhFXW"
]
}
And I receive no messages from the live chat room.
Can someone tell me what I'm doing wrong or what is missing?
Thanks in advance
Frank
Ok, I found my own answer, after a lot of testings.
To subscribe for live chat message events the object has to look like this:
(Correct Object)
{
"msg":"sub",
"id":"3",
"name":"stream-room-messages",
"params":[
roomname,
{
"useCollection":false,
"args":[{"visitorToken":token}]
}
]
}
It must be "visitorToken" instead of "token".
the official documentation is wrong here, it says:
(Wrong Object)
{
"msg":"sub",
"id":"6NctZomXL3ZdtKNsn",
"name":"stream-livechat-room",
"params":[
"KTZqPAR9DQGxKcxzf",
{
"useCollection":false,
"args":[
{
"token":"jkGaw6duhiuh45"
}
]
}
]
};
Now it works to subscribe the live channel and to receive messages from the Live Agent.

Reading videos from mubi.com fails on Raspberry Pi with videojs errors

When I try to play movies from mubi.com on the Raspberry Pi 4, the video won't start and I see several videojs error messages in the web console of the browser. I tried two browsers, chromium and firefox, and two operating systems, Raspbian and Arch Linux. On both OS and browsers, playing videos from Youtube, dailymotion or vimeo works fine, only mubi gives issues. I tried using browser plugins h264ify and decentraleyes but I keep getting the following errors. On Linux desktop I have never had any problem playing from mubi.com with any browser. Can someone help understand what these errors mean ?
Resource URL: https://mubi.com/films/kingyo/watch
Source Map URL: manifest-0c2854bad8183a32f809.js.map
09:46:46.237 [clpp.player] Loading sources
Array [ {…} ]
Object { drmtoday: {…} }
breadcrumbs.js:58
09:46:46.267 [clpp.player.utils.video_events] Player state change: IDLE -> PREPARING breadcrumbs.js:58
09:46:46.825 [clpp.abr] creating bandwidth meter: SLIDING_PERCENTILE breadcrumbs.js:58
Successfully compiled asm.js code (total compilation time 74ms) mubi_player-3808cb2e6df5273c018b.js
Request to access cookie or storage on “<URL>?” was blocked because it came from a tracker and content blocking is enabled. 9
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. clpp.min.js:26:17357
VIDEOJS: ERROR: (CODE:0 MEDIA_ERR_CUSTOM) <empty string>
Object { code: 0, instanceof: "CLPPError", message_: "", group: {…}, name: "REQUESTED_KEY_SYSTEM_CONFIG_UNAVAILABLE", errCode: 6001, severity: "WARNING", parentError: {}, ts: 1587808013074, processed: true, … }
breadcrumbs.js:58
VIDEOJS: ERROR: (CODE:0 MEDIA_ERR_CUSTOM) <empty string>
Object { code: 0, instanceof: "CLPPError", message_: "CDN switch failed", group: {…}, name: "CDN_SWITCH_FAILED", errCode: 137, severity: "WARNING", parentError: {}, ts: 1587808013170, processed: true, … }
breadcrumbs.js:58
VIDEOJS: ERROR: (CODE:0 MEDIA_ERR_CUSTOM) <empty string>
Object { code: 0, instanceof: "CLPPError", message_: "CDN switch failed", group: {…}, name: "CDN_SWITCH_FAILED", errCode: 137, severity: "WARNING", parentError: {}, ts: 1587808013200, processed: true, … }
breadcrumbs.js:58
VIDEOJS: ERROR: (CODE:0 MEDIA_ERR_CUSTOM) <empty string>
Object { code: 0, instanceof: "CLPPError", message_: "CDN switch failed", group: {…}, name: "CDN_SWITCH_FAILED", errCode: 137, severity: "WARNING", parentError: {}, ts: 1587808013225, processed: true, … }
breadcrumbs.js:58
VIDEOJS: ERROR: (CODE:0 MEDIA_ERR_CUSTOM) <empty string>
Object { code: 0, instanceof: "CLPPError", message_: "CDN switch failed", group: {…}, name: "CDN_SWITCH_FAILED", errCode: 137, severity: "WARNING", parentError: {}, ts: 1587808013250, processed: true, … }
breadcrumbs.js:58

Can't get sails-hook-validate to work with Sails v1.0?

I am having an issue getting validation error messages to attach to the error object in sails v1.0. I am using the sails-hook-validate module.
User model:
module.exports = {
attributes: {
name: {
type: 'string',
required: true,
}
},
validationMessages: {
name: {
required: 'Name is required'
},
},
};
Running User.create in the sails console:
sails> User.create({}).exec(err => console.log(err.toJSON()));
{ error: 'E_UNKNOWN',
status: 500,
summary: 'Encountered an unexpected error',
Errors: undefined }
It appears sails-hook-validate is modifying the error object in some way, but it doesn't seem to be adding my custom error message in any way. Does anybody know how to get sails-hook-validate to work in Sails v1.0?
Sails v1 dramatically changed how validation errors are formatted and sails-hook-validate hasn't been updated to handle Sails v1 yet.
Sails-hook-validate is a third party hook and I dont think its been updated to work with Sails V1.
As #jeffery mentioned the structure of validation errors did change slightly in Sails V1 but there could be other changes that are effecting this hook.

Meteor login with facebook

I have a meteor app, with packages :
useraccounts:bootstrap;
service-configuration;
accounts-facebook;
The facebook side was configured to allow requests from localhost. When using the register/signin with facebook from the atForm, a popup appears
EDIT
The popup is actually not empty but displays a message 'login complete, click to close' but closed fast because that's how I configured it on the facebook side.
And the console logs an error:
Exception while invoking method 'login' undefined
EDIT
Here is the service conf:
ServiceConfiguration.configurations.remove({
service: 'facebook'
});
ServiceConfiguration.configurations.insert({
service: 'facebook',
appId: 'removed',
secret: 'removed'
});
EDIT
Here is the client side code :
Template.atForm.events({
'click #at-facebook': function(event) {
console.log("facebook click");
Meteor.loginWithFacebook({
requestPermissions: ['email', 'user_friends']
}, function (err) {
if (err)
Session.set('errorMessage', err.reason || 'Unknown error');
});
}
});
EDIT
When registering with facebook the user created is as follow :
{ createdAt: Thu Jan 21 2016 16:00:08 GMT+0100 (CET),
I20160121-16:00:08.108(1)? _id: 'Kgs3WswMdB9hsxMfp',
I20160121-16:00:08.108(1)? services:
I20160121-16:00:08.108(1)? { facebook:
I20160121-16:00:08.108(1)? { accessToken: 'removed',
I20160121-16:00:08.108(1)? expiresAt: 1458562023670,
I20160121-16:00:08.109(1)? id: 'removed',
I20160121-16:00:08.109(1)? email: 'removed',
I20160121-16:00:08.109(1)? name: 'Mathieu Kudla',
I20160121-16:00:08.109(1)? first_name: 'Mathieu',
I20160121-16:00:08.110(1)? last_name: 'Kudla',
I20160121-16:00:08.110(1)? link: 'https://www.facebook.com/app_scoped_user_id/removed/',
I20160121-16:00:08.110(1)? gender: 'male',
I20160121-16:00:08.110(1)? locale: 'fr_FR',
I20160121-16:00:08.110(1)? age_range: [Object] } } }
This seems to indicate that the facebook handshake was successful?
What is causing that error? Thanks :)
Ok I kinda solved it.
I digged in the log-in attempts and noticed that the oauth service was not properly paired with the user. I don't know why that is or if there is a better solve but I added the line :
if (user.services) { var service = _.pairs(user.services)[0]; }
to my onCreateUser hook and appended the user object properly before returning it. It seems to have done the trick but I don't know what I was not doing properly the first time...