stream-js | Browser Client - Build Activity Feeds | Notification library

I am trying to stream responses to my client using a NodeJS Express server hosted using Azure App Service. However, I noticed that it is not really streaming but tries to send the response as a whole. When the response size is huge (>50MB), the client gets an Internal Server Error, but the server does not throw an error.

Further, when I run the server inside a Docker (Node Image: 10.22.0-alpine3.9), I see that the client gets the response as a stream even for huge responses. (This is the behavior I actually need)

My web.config file is as follows.

I often find myself reading a large JSON file (usually an array of objects) then manipulating each object and writing back to a new file.

To achieve this in Node (at least the reading the data portion) I usually do something like this using the stream-json module.

Hi I'm new to GetStream and still learning. Here is a condensed version of what I'm using.

I have a python backend where I create user tokens:

Versions:

• node: v12.14.0
• getstream: 4.3.0

I am experimenting with user creation as described in the documentation. However, creating a user client.user(userId).create({type: 'normal'}) always fails with 500. Similar to the Github issue 232.

Error message: {"detail":"","status_code":500,"code":-1,"exception":"InternalServerException","duration":"0.51ms"} with HTTP status code 500

Anyone an idea what may be going wrong?

Fyi:

• I am able to create and fetch feed/activities. So, the client works.
• right now I simply experimenting with some scripts.
• the userId is a string, not very long (<30 chars), alphanumeric

Update:

Same error occurs after these attempts:

• Using latest version 4.4.0
• Using REST-API/curl as documented. Example command: curl -i -X POST -d '{"id":"bob","data":{"extra":"fields","flag":false}}' -H "Content-Type: application/json" -H "Stream-Auth-Type: jwt" -H "Authorization: JWT-TOKEN" "https://tokyo-api.stream-io-api.com/api/v1.0/user/?api_key=API-KEY"
  The command in the documentation is generated using key/token, but it also changes the URL endpoint to tokyo-api.stream-io-api.com. I also tested this with the domain api.stream-io-api.com, and the opposite, using tokyo-api.stream-io-api.com in the library (overwritten manually) without success.

I tried to read HTTP response with axios and parse JSON in stream mode with stream-json` so I can fully fit my database on demand. It works well but if I try to close database connection everything will be crashed because the connection will be closed too soon. The problem is: await doesn't wait for the extract_coins function to complete (even if it's returning the promise) and close database connection in a final scope.

I am sending data to GetStream but there is an error being returned which I have no idea where it's referring to, considering I am not sending user_id anywhere in my code.

It's when I run this which the error comes up: client.trackEngagement(engagement);. The connection to GetStream seems correct in this case as I am getting a message from them, but the data being sent is somehow wrong?

GetStream JS package - https://github.com/getstream/stream-js.
GetStream Analytics Docs - https://getstream.io/docs/analytics_engagements/?language=js

Another example setup from GetStream - https://github.com/GetStream/stream-analytics-js/blob/master/examples/index.html

Error:

As a test, this is the code I run when the page is loaded.

Code:

I currently have a 700M file and always end up with a Memory Limit when I try to read it (purpose: import data to FireStore using firestore nodejs sdk).

I tried the following libraries:

• json-stream (https://github.com/uhop/stream-json)
• JSONStream (https://github.com/dominictarr/JSONStream)

I've got a Lambda function that is triggered by a write to an S3 bucket. It reads the JSON file that is written to the bucket, parses out the individual records, and writes them to a database.

Problem is; I'm not sure what I'm doing wrong, because the stream ends and the Lambda exits before all the data is written.

I'm in "flowing mode" on my readable stream, and I'm pausing/resuming during the db write. According to the docs, this should do the trick, but it's not working as expected.

Lambda handler:

In Node.js I'm using stream-chain and stream-json to request streaming feeds from local and remote resources. Below works for local resources, but how to modify it, to allow also for external resources? Do I need to download the file first or?