Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 08:40
    Aschen labeled #1496
  • 07:27
    codecov[bot] commented #1496
  • 07:27
    codecov[bot] commented #1496
  • 07:24
    codecov[bot] commented #1496
  • 07:24
    Aschen synchronize #1496
  • 07:24

    Aschen on cli-documentation

    Update references to embedded C… (compare)

  • 07:20
    Aschen assigned #1496
  • 07:20
    Aschen labeled #1496
  • 07:20
    Aschen opened #1496
  • 07:20
    Aschen labeled #1496
  • 07:11

    Aschen on cli-documentation

    Update CLI documentation (compare)

  • 06:56
    codecov[bot] commented #1495
  • 06:56
    codecov[bot] commented #1495
  • 06:49
    codecov[bot] commented #1495
  • 06:45
    codecov[bot] commented #1495
  • 06:45
    codecov[bot] commented #1495
  • 06:45
    Aschen synchronize #1495
  • 06:45

    Aschen on v2-check-request-volatile-for-sdk-version-compatibility

    Apply @scottinet comments (compare)

  • 03:47

    Aschen on fix-socketio-version-for-node6

    (compare)

  • 03:47

    Aschen on 1-dev

    Fix socketio version for node6 … (compare)

smets boris
@smetsboris_gitlab
@shawub have you tried it? I did with postman and it was working, the test took me 2 minutes approximately.
shawub
@shawub
@smetsboris_gitlab It works with queries over http but errors if I add _source to a subscription filter
Sébastien Cottinet
@scottinet

Hi @shawub > Koncorde is about matching things, it doesn't filter out the content of responses. To do that, you'll have to write a plugin, with pipes plugged on events containing the payloads you want to filter.

If you're mentioning Koncorde then I assume you want to filter notifications, and in that case, you might want to take a look at the notify:document event.

Sébastien Cottinet
@scottinet

@smetsboris_gitlab > I'm afraid Kuzzle's API doesn't allow the creation of analyzers, or the change of analyzers used on an index. Many ES administration methods are missing from Kuzzle because on of our purposes is to expose only parts of Elasticsearch through a secure API, and in a (very) controlled manner. Our policy is that most administrative tasks are outside the scope of Kuzzle and must be done on ES directly, by administrators.

Now there is a grey area when it comes to kuzzle's internal index administration, since we're asking admins to configure kuzzle stored objects in ES directly.
We're still wondering if that is a good thing or not, so this might change in the future (or not).

smets boris
@smetsboris_gitlab
@scottinet thanks for clarification, that makes sense
Gaiidenn
@Gaiidenn
Bonjour, j'avais précédemment envoyé un fichier pour votre doc. Là, avec Angular 2+, je peux vous fournir un exemple fonctionnel pour : l'adaptateur du kuzzle sdk + un service "générique" qui l'utilise + un exemple de service standard en angular qui utilise kuzzle. Est-ce que ça vous intéresse? :)
Sébastien Cottinet
@scottinet
Bonjour @Gaiidenn ,
De quel fichier s'agit-il ?
Sinon, toute contribution est bienvenue. N'hésite pas à saisir une pull request sur github :)
Gaiidenn
@Gaiidenn
@scottinet ce ne sont que des fichiers dans mon app personnelle, qui pourraient servir d'exemple pour l'utilisation du sdk kuzzle dans une application Angular
Sébastien Cottinet
@scottinet
@Gaiidenn > on a des getting started pour Node.js, browser vanilla, webpack, et on en a en cours de revue pour Vue.js et pour React. Un getting started pour Angular serait plutôt intéressant, surtout qu'on n'a pas encore prévu d'en écrire un.
Si tu te sens, tu peux t'inspirer de ce qu'on a déjà pour en écrire un, cela nous serait d'une grande aide (Getting Started: Vanilla or, currently under review, kuzzleio/sdk-javascript#436)
Gaiidenn
@Gaiidenn
oki oki @scottinet je checkerai ça si j'ai le temps du coup ^^'
M Hjorleifsson
@mhjor70
folks any good docs on using vuejs on the frontend of kuzzle?
Gaiidenn
@Gaiidenn
Petite info en passant (je viens de chercher 2h pour trouver que ça vient de là) : ne PAS mettre l'option "optimization" dans angular.json (au build d'une app angular) => le SDK Kuzzle n'aime pas ça (app crash)
Sébastien Cottinet
@scottinet
Hi @mhjor70 >
a Vue.js getting started is under review: kuzzleio/sdk-javascript#431
It should soon be available in our documentation.
M Hjorleifsson
@mhjor70
@scottinet thank you i will review.. have a 2 projects i would love to use kuzzle for , front end requirement is vue as the components are already written
Sébastien Cottinet
@scottinet
@Gaiidenn > Interesting. Can you write an issue about it, with the exact error you got and a way to reproduce the problem?
@mhjor70 > we use our SDK daily with Vue.js, so if you have specific questions, don't hesitate to ask here
M Hjorleifsson
@mhjor70
@scottinet Awesome thanks for the quick reply. BTW i tried to send a contact request for a quote on the website and the capatcha kept reporting incorrectly that it failed (using brave browser).
@scottinet one of the projects is IoT and requires the auth be available offline, trying to figure out if that is possible, was initially looking at pouch/couch as a solution for that but would prefer kuzzle as the dev time would be shorter if there is a way to sync that auth info for offline auth to control the IoT system
Sébastien Cottinet
@scottinet
About the contact form, thanks for the heads up. I've notified our communication team, and hopefully this should be fixed soon.
This message was deleted
@mhjor70 > About the auth problem, it depends of what you mean by "offline". If you mean "having a LAN system without an access to WAN", then if you have a powerful enough server, this is definitely doable, as Kuzzle can be installed anywhere.
If that's not that, then I will need more information to get an idea about your use case.
M Hjorleifsson
@mhjor70
@scottinet so the main system will be in the cloud (admin etc) but there are technicians out in the field with devices and a tablet to control the device (this talks to a little arm computer in the unit) we need to sync the auth data from the cloud to the control device every time the unit gets online so if a password has changed or a new authorized user was added its available in the field. basically a subset of the users documents/db. for that client entity for their devices
smets boris
@smetsboris_gitlab
Hello all, I have a recurrent problem within one of my plugin which is making some request ( before creating some documents (pipe: <document:beforeCreate>). I get a fatal error when the index doesnt exist (of course it should exist, and we have a problem in the client but as we are in a multitenant it s a bit difficult to be sure) : here is my code const searchRequest = new this.context.constructors.Request({ index: index, collection: collection, controller: 'document', action: 'search', body: queryObject }) return this.context.accessors.execute(searchRequest) the fatal error stop the instance of kuzzle which is a bit frightening, how could I avoid to have to restart kuzzle?
Sébastien Cottinet
@scottinet
@mhjor70 > about the captchas problem: I do use brave, so I tested it (I'm not a frontend guy, so I rarely use our own website). I hate those captchas: they never seem to work with Brave shields up, I need to deactivate them.
M Hjorleifsson
@mhjor70
ill try that now.
Sébastien Cottinet
@scottinet
@smetsboris_gitlab > this is worrying indeed: this should not stop a kuzzle instance. Does Kuzzle print logs before dying and, if so, can you send paste those here?
Also, what version of Kuzzle are you using?
M Hjorleifsson
@mhjor70
@scottinet worked with shields down, message sent :)
smets boris
@smetsboris_gitlab
smets boris
@smetsboris_gitlab
I can t say the version exact because I use the latest tag... but from an inspect my docker image has been created 2 months ago: "2019-07-15T14:44:53.870057858Z",
Sébastien Cottinet
@scottinet
ok this should be 1.8.4
@smetsboris_gitlab > is the index name an Elasticsearch alias to another index?
smets boris
@smetsboris_gitlab
@scottinet no, I don't use alias
Sébastien Cottinet
@scottinet

@smetsboris_gitlab > I tried with Kuzzle 1.10.4, 1.8.4 and 1.8.3, with a pipe plugged on the document:beforeCreate event.
I copied/pasted your code (except that I don't have the content of your "queryObject" variable), and tried the following scenarios:

  • with an existing index: the "document:create" request is replaced with the "document:search" one, since this is what is returned by the pipe
  • with a null index: correctly throws a 400 BadRequest informing that this API route needs an index (kuzzle does not crash)
  • with a non-existing index: correctly throws a 404 NotFound error (kuzzle does not crash)

There is something missing... Is your NODE_ENV environment variable set to development?

smets boris
@smetsboris_gitlab
@scottinet Ok , I got it (maybe my nodejs skills are in question..) if I dont catch the error I get fatal error , with something like :```return this.context.accessors.execute(searchRequest).then(elts => {
// do some stuff
})
  .done(() => callback(null, request))``` but If I catch it , it works like a charm, see : ```return this.context.accessors.execute(searchRequest).then(elts => {
  // do some stuff
})
  .catch(error => {
    //
  })
  .done(() => callback(null, request))```
Sébastien Cottinet
@scottinet
@smetsboris_gitlab > Yes, but only if your NODE_ENV variable is set to development. We provoke a crash on purpose to help catching unhandled promise rejections during development phases, simulating what Node.js behavior will be in the future (we don't know exactly when).
With any other value in the NODE_ENV variable, Kuzzle will ignore unhandled promise rejections, only logging them and continuing the best it can (in your case this will probably end up in a PluginImplementationError being sent to the requesting user)
Sébastien Cottinet
@scottinet

@smetsboris_gitlab > I was wondering what was that .done() method... It appears to be specific to bluebird, and what it does is act as a generic then OR catch, and then make node crash on purpose: https://devdocs.io/bluebird/api/done
Bluebird's API documentation states that this method should not be used.

So... I think that the cause of crash is there. And now I understand that Fatal word being put before the error message in the stacktrace you sent, since this is not something Kuzzle adds.

smets boris
@smetsboris_gitlab
@scottinet good point, you found the problem
thanks a lot
stefanweiser801
@stefanweiser801_twitter
Hello all. I am currently using the Android SDK. And I have two questions. I hope you can help me. 1. Everything works fine, when i use always the callbacks. Kuzzle k = new Kuzzle(...); k.login(...); Now if i want to create a collection it works fine inside the callback of the k.login. But outside the callbacks i always get a nullpointerexception. So my question is, how to stay logged in every activity?
do i have to create a new instance everywhere? 2. callbacks are always void. What is the best way to get the result of it? Thank you for the help.
Sébastien Cottinet
@scottinet
Hi @stefanweiser801_twitter > to stay logged, save the authentication token (kuzzle.jwt) somewhere. When instanciating a new kuzzle instance, put the saved value in it.
About callback results, can you provide an example where a null result is returned by the callback?
stefanweiser801
@stefanweiser801_twitter

First, thank you for the reply. So here is a short part of the code and only the important things.

Kuzzle kuzzle = new Kuzzle(HOST , options, new ResponseListener<Void>() {
                @Override
                public void onSuccess(Void response) {
                    kuzzle.login("local", credentials, 10000, new ResponseListener<JSONObject>() {
                        @Override
                        public void onSuccess(JSONObject response) {
                            Collection collection = kuzzle.collection(collection, index);
                            createDocument(content, collection);

                        }

Here everything is fine, but when i use createDocument outside the callback it gives me a null result. in create Document you find kuzzle.collection(...).createdocument(...). So it works only in the callback.

Sébastien Cottinet
@scottinet
How is createDocument initialized?
stefanweiser801
@stefanweiser801_twitter
I found out what's wrong. when i use kuzzle outside the login callback then i get the null result. I changed it and i put everything in the callback, now it works fine. Thank you for your help.
M Hjorleifsson
@mhjor70
he there i have been trying to find the vuejs getting started but i cant seem to locate it.
M Hjorleifsson
@mhjor70
just found some snippets.
but no getting started type doc
Sébastien Cottinet
@scottinet
Hi @mhjor70 > It's still under review and hasn't made its way to production yet.
You can find a preview here: https://deploy-preview-431--doc-sdk-javascript.netlify.com/getting-started/vuejs/standalone/
M Hjorleifsson
@mhjor70
thanks, at least i can do a lil testing :)
M Hjorleifsson
@mhjor70
got it thanks :)
Sébastien Cottinet
@scottinet
@mhjor70 > Hi again: the Vue.js getting started has been released: https://docs.kuzzle.io/sdk/js/6/getting-started/vuejs