profile
viewpoint

yasserf/babelbox 21

Babelbox is a small i18n library that allows users to easily create apps that support multiple languages

deepstreamIO/deepstream.io-realtime-search 3

Provides realtime lists for a collection of databases

deepstreamIO/deepstream.io-clusternode-redis 2

A redis cluster bus implementation to allow deepstream nodes to scale

deepstreamIO/deepstream.io-dummy-client 2

A very basic JS file to show the quickest way to get a client running

deepstreamIO/deepstream.io-example-plugins 2

A variety of all custom plugin examples

deepstreamIO/deepstream.io-protobuf-js 2

The JS builder / parser for deepstream.io / node and JS runtimes

deepstreamIO/deepstream.io-protobuf 1

The protobuf protocol files

deepstreamIO/deepstream.io-types 1

The deepstream enums and interfaces

yasserf/babelbox-requirejs 1

A babelbox plugin for requirejs

startedtbleckert/react-select-search

started time in 9 hours

issue commentdeepstreamIO/deepstream.io-client-js

Problem of usage in nodejs 14.5 with the lastest version of @deepstream/client@5.1.1

@jaime-ez also related to the last release 😅

geohuz

comment created time in 11 hours

issue commentdeepstreamIO/deepstream.io-client-js

C and Options are not exported from dist/bundle/ds.min.js

@jaime-ez any idea how we can get this to work? (Or if we just mention its a breaking change)

timarandras

comment created time in 11 hours

startedmoroshko/react-autosuggest

started time in a day

startedfraserxu/react-dropdown

started time in 3 days

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

Hmm. Honestly I have no idea what can be causing this. Subscribing to an event is something I used to do on a daily basis, there are a bunch of tests and it feels like something that would have been raised by other users.

If you create a small reproducible repo I can took a look into it. The code you pasted doesn't replicate the issue for me. Thanks!

davidbehler

comment created time in 5 days

issue commentdeepstreamIO/deepstream.io

Future of deepstream / Contributor Callout

@speedysera I'm 100% for accepting PRs and bugfixes as long as they align with the project goals. I'm wary of people pulling projects into completely different directions to fit their exact usecases, but as long as it improves the core awesome. The structure is 90% modular so you can pretty much swap in and out any part of the server if you do have a more specific requirement. Literally, any part other than config parsing.

The thing is I'm no longer dedicating personal time for adding new features or clients as I put in a few years already and I don't currently use it in my projects (as my current projects are more webapp heavy and barely touch backend services.

The notice is there to inform people that it isn't being actively maintained in the sense of day to week life, and if theres a bug you might need to get your hands dirty (or at least raise a PR).

@slachtar I can't put a sponsor button up due to legal issues (the company behind it still exists and I'm definitely not going to spend my time declaring german taxes). I'm also not going to coordinate any work with a paid contractor to build a client. We sunk thousands of pounds into that during deepstreamhub and the result was, well, you can see how the non JS sdks look (other than the ios wrapper by @akramhussein, the job itself was extremely ambitious and it was by far the best experience I had working with someone outside of a core team).

yasserf

comment created time in 5 days

startedaudiojs/audio-buffer-utils

started time in 5 days

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

unfortunately not no. The config in permissions: fileLoad(permissions.yml) is what matters. If changed

davidbehler

comment created time in 6 days

CommitCommentEvent

issue closeddeepstreamIO/deepstream.io-dummy-client

Health check path and ping/pong message

Is it supposed to get back pong message from server with client ping? In the code I can see there is a ping to sever by every 5 sec, but I can't see the pong message from the server? Is there any documentation about the ping/pong mechanism of deepstream?

And I saw there is a health check path in the server configuration, how does this related to ping/pong heartbeat? How we can utilize this path?

Thanks

closed time in 6 days

geohuz

issue commentdeepstreamIO/deepstream.io

Future of deepstream / Contributor Callout

hello! I mean it's been open source since it started in 2015, we just pulled out clustering and put it back in.

Depends on what you need to to contribute really. You can either add features to it for fun (not exactly recommended since it just adds more complexity) or you can look at the git issues that are tagged contribution friendly to get you started.

Generally best contribution methods are:

  1. Writing a client. It's a huge task so means you gotta be pretty committed.
  2. Writing guides. This can be any size you want and is usually the most fun.
  3. Updating documentation. This is pretty mundane but can take a few minutes.

I personally would say being vocal about using deepstream by either writing a small guide, tutorial or even an odd tweet here or there would have the biggest umph factor.

Hope that helps

yasserf

comment created time in 6 days

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

as in are you using the default valve permissions or did u modify it?

davidbehler

comment created time in 6 days

issue openedkatspaugh/wavesurfer.js

Cursor is no longer visible on master branch

Hey, thank you for testing and contributing to wavesurfer.js!

Wavesurfer.js version(s):

  • master

Browser and operating system version(s):

chrome (but this applies everywhere)

Code needed to reproduce the issue:

https://github.com/katspaugh/wavesurfer.js/commit/0fec7883e1ad59f8ff67f115d5992aac7138355c

Looks like using the clip width (while definitely a huge performance gain) has the downside of no longer showing the border-right which is the cursor.

created time in 7 days

CommitCommentEvent

push eventyasserf/wavesurfer.js

Yasser Fadl

commit sha 77c6cc3e917f1072b0b513889b6503fe899e2041

microphone plugin: change LocalMediaStream to MediaStream in docs (#1958) As documented here: https://developer.mozilla.org/en-US/docs/Web/API/LocalMediaStream

view details

Thijs Triemstra

commit sha 13cb121626ca3a355e172034a5111f0cc864aa9c

update dev dependencies

view details

Thijs Triemstra

commit sha ba3f2940ce85df43a30d9d7482ec5e0217a2c091

ci: use latest node on appveyor (#1961)

view details

Oliver Switzer

commit sha 54b27a51fedb7042aea940a974e23551d55a50fa

Add setDisabledEventEmissions to allow disabling event emissions (#1960) * Add option to seekTo method to allow diabling event emissions * Remove arrow functions and let declarations * Allow for disabling event handlers for any set of events via Observer#setDisabledEventEmissions * Forgot to remove old changes in Wavesurfer class * Add CHANGES.md entry for 4.0.0 * add version marker * add @example usage Co-authored-by: Thijs Triemstra <info@collab.nl>

view details

Maria Zuccarà

commit sha 9d64ccf2f57da62a9d328ec2112dcbee1efd26bb

Drawer: removed private methods (#1962) * changelog * drawer: removed private methods and vars * fix changelog

view details

Thijs Triemstra

commit sha b7d1a25965869acb1843323232831ad48f5780af

eslint: enable indent rule

view details

ThibG

commit sha 8b52847e32bdd378d2c1288b0b21bdd39672e64d

Fix muting behavior with the MediaElement backend (#1966) * Fix muting behavior with the MediaElement backend * Document changes

view details

Ben Osheroff

commit sha a5b488421643cc8c90c543377cd659ac7ab38155

remove no-eslintrc flag (#1967) * remove no-eslintrc flag this was breaking CI builds * fix lint errors that were re-exposed

view details

ThibG

commit sha 52e7ac7717ce998621bfcd04274c0a37dec9b30d

Fix setMute setting (incorrect isMuted) (#1968)

view details

Ben Osheroff

commit sha f96f3b313c363f6970b2101dcc8270e10990d637

MediaElement safari fixes (#1964) * rewrite mediaelement-webaudio comment * resume audiocontext for Safari + mediaelement/webaudio this was happening in the webaudio backend, but due to the odd inheritance layout of mediaelement-webaudio it wasn't happening here. * add changelog entry * hoist common code into utility function * generalize comment

view details

Thijs Triemstra

commit sha f8544deb96cc70dbd2b5a5467645f013e30810f3

Release 4.0.0 (#1974) * update dev dependencies * bump version: 4.0.0

view details

Ben Osheroff

commit sha 4e2375e20a84ab1ca15b74dc25cfddb769d03e40

guard against null _disabledEventEmissions in Observer#fireEvent (#1970) the regions plugin notably was using all the functions of Observer without calling the constructor, triggering a crash

view details

Ben Osheroff

commit sha 357112af008d8cff43da2f27c9455c312f893a91

update regions plugin example (#1978) show off playback of a region and looping.

view details

Thijs Triemstra

commit sha aaf433ecaf2f032a28a0419401ed56958f67a17e

release 4.0.1 (#1979) * add 4.0.1 changelog entry * bump version: 4.0.1 * update dev dependencies

view details

katspaugh

commit sha 594480a4baea0a8aa325a59b0bdb2368c0b027f6

Add publishConfig (#1984) Co-authored-by: katspaugh <katspaugh@gmail.com>

view details

Seweryn Zeman

commit sha a7c73440d9d4c2804ca12534dde73252c1fd11d1

regions plugin: improve loop playback logic (#1977) * Change loop playback logic Removed double playback loop logics and using this.loop now * Restore region loop logic from previous playLoop() * update changelog

view details

Ben Osheroff

commit sha 4cb1fe1da90e34e99b05e5aa42aaf5a10b8da5c7

avoid call to HTMLMediaElement#load when peaks are given (#1969) * avoid call to HTMLMediaElement#load when peaks are given calling `.load()` explicitly on a mediaelement entirely defeats the "preload" setting and makes it impossible to avoid downloading data before playback. When HTMLMediaElement#load is called, all of the major browsers make some request for the file. Chrome and FF make a range request for the entire file, but only report downloading them partially. Safari reports downloading the file in its entirety. * code review; only avoid .load call when preload == 'none' * add changelog entry * bump changelog entry to next release * add next section to changelog Co-authored-by: Thijs Triemstra <info@collab.nl>

view details

Ben Osheroff

commit sha 0fec7883e1ad59f8ff67f115d5992aac7138355c

performance: use clip-path css instead of width (#1983) * use a clip-path css mask instead of changing width this prevents browsers from continuously making layout engine passes. * code review fixes; code style, comments * add changelog entry * add PR number to changelog Co-authored-by: Thijs Triemstra <info@collab.nl>

view details

Maria Zuccarà

commit sha a50691b310493c48c31a42328891bee58d912065

regions plugin: improve regions handle elements access (#1985) - fixed regions handles style assignment - changelog

view details

Thijs Triemstra

commit sha 3a02ddf2fb810abd1bd25b591ff41d06b985a5c2

doc: add regions section in changelog

view details

push time in 8 days

created tagdeepstreamIO/deepstream.io

tagv5.1.2

deepstream.io server

created time in 8 days

push eventdeepstreamIO/deepstream.io

Yasser Fadl

commit sha e75e2cf287c514941b3bb87e7362f4f878b1a0cd

5.1.2

view details

push time in 8 days

push eventdeepstreamIO/deepstream.io

Yasser Fadl

commit sha 1b4aaed660a1af4f1e9837f8497b9696147d1d18

chore: removing mocha ops from nyc

view details

push time in 8 days

push eventdeepstreamIO/deepstream.io-client-js

Yasser Fadl

commit sha 6670e694645fa397b722ed7c537ef76d485e1145

chore: upgrading dependencies

view details

push time in 8 days

push eventdeepstreamIO/deepstream.io

Yasser Fadl

commit sha dee754922cdb2fef5b3c3ea6aa4d3c3cfd1dfc2a

chore: updating all dependencies

view details

Yasser Fadl

commit sha 4280b18d0ee516cb87408515be77eb1e98d1f510

chore: updating all dependencies

view details

Yasser Fadl

commit sha 308965fc7f3f9ff05c32a449a8fa2a974f55235d

chore: upgrading mocha

view details

push time in 8 days

issue commentdeepstreamIO/deepstream.io-dummy-client

Health check path and ping/pong message

I believe so, there has been a fix fixes around health checks in v5.1

https://github.com/deepstreamIO/deepstream.io-client-js/commit/388506e9516374760b7c8710576d66ae6e59259b

geohuz

comment created time in 8 days

pull request commentdeepstreamIO/deepstream.io-client-js

[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle

@jaime-ez you can push the tag v5.1.2 and it should auto publish btw. CI systems yay.

I don't think changing the package.json main file makes a difference in semantic versioning since noone really uses it outside of npm (that I know of, if they do it's a bit odd and we have a small enough pool of users for it to be very unlikely).

jaime-ez

comment created time in 8 days

Pull request review commentdeepstreamIO/deepstream.io-client-js

[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle

+import { Buffer } from 'buffer'

why is this needed btw? Is it not polyfilled?

jaime-ez

comment created time in 8 days

issue commentdeepstreamIO/deepstream.io

Maximum Version Number

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt

This will actually fix the issue on the server, just needs to polyfilled on Client

grydstedt

comment created time in 8 days

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

hey @davidbehler

Sorry for the delay.

Are you using custom permissions? Looks like it's a cross referencing bug

davidbehler

comment created time in 8 days

issue closeddeepstreamIO/deepstream.io

Use deepstream client in node throws error

I'm trying to programing a server side client to connect to deepstream server to manager list of task, so I'm using node with @deepstream/client,

import DeepstreamClient from '@deepstream/client'

const dss = new DeepstreamClient('xxx.xxx.xxx.xxx:6020/deepstream')
dss.login()

run the script file with node --experimental-modules taskserver.mjs And I get: TypeError: DeepstreamClient is not a constructor

Am I doing correctly?

closed time in 8 days

geohuz

pull request commentdeepstreamIO/deepstream.io-client-js

[task] implement client reset function

Interestingly in polymer tools and older (like 4 years ago) angular I didn't use singletons:

https://github.com/deepstreamIO/deepstream.io-tools-polymer/blob/master/ds-connection-behaviour.html https://github.com/deepstreamIO/ds-demo-simple-app-ng/blob/master/src/start-ng.js

But my reasoning in React and Angular2+ for some reason changed. So I can see the confusion, I myself am confused haha

jaime-ez

comment created time in 8 days

pull request commentdeepstreamIO/deepstream.io-client-js

[task] implement client reset function

Happy to hear it works well for you

I think if I was to raise a PR to allow a user to change their auth credentials without invalidating what I would do is:

.pause()
.updateAuth() // new API that replaces auth credentials and nothing else
.resume()

or


.updateAuth() // new API that replaces auth credentials and nothing else


That way you can either predict auth credentials changing (like a JWT token) without having to kill the connection or update it on a INVALID_AUTH event.

I generally like the connection being completely dead at the end at the end tbh, because it forces things to clean up if you surpass the maximum amount of invalid login events (including dumping you local storage if configured that way).

jaime-ez

comment created time in 8 days

pull request commentdeepstreamIO/deepstream.io-client-js

[task] implement client reset function

So the issue I'm seeing with the reset method that I can see is that it essentially rewrites all of the client state. So you lose all references to current subscriptions (invalidating anything you already have) and essentially just using the deepstream instance as a very shallow wrapper.

So rather than using a factory/singleton pattern (which is what I would argue is a bit more sane) your now making a single deepstream instance responsible for what is essentially replacing it's entire internal logic.

It would probably easier in the react world to use a context (to retrieve the client) or in the redux world to use a singleton pattern where you can do (deepstream().event.subscribe).

In client v2 is just recreated the socket after changing auth params (same as .resume): https://github.com/deepstreamIO/deepstream.io-client-js/blob/v2/src/message/connection.js#L82

In v4 the same thing is there but it's commented out: https://github.com/deepstreamIO/deepstream.io-client-js/blob/master/src/connection/connection.ts#L227

Seems like it was commented out a few years ago by one of the developers due and I just never commented it back in.

jaime-ez

comment created time in 8 days

pull request commentdeepstreamIO/deepstream.io-client-js

[task] implement client reset function

So there’s a pause and resume method, and reconnection logic already exists.

As such I’m not fully following. I get the issue with the Auth credentials but I think the issue your facing is more around your app design rather than deepstream tbh.

If you logout your app should be destroyed in react native (everything unmounts). If your carrying state between different users it’s sort of a security concern (worst case).

jaime-ez

comment created time in 8 days

issue commentdeepstreamIO/deepstream.io

Use deepstream client in node throws error

It’s { DeepstreamClient } since the function is not the default export.

geohuz

comment created time in 8 days

issue commentdeepstreamIO/deepstream.io

TypeScript Compile Error : An accessor cannot be declared in an ambient context

seems this is an issue with angular/typescript version

https://github.com/storybookjs/storybook/issues/9463

easiest thing is apparently adding "skipLibCheck": true

gigenthomas

comment created time in 12 days

push eventdeepstreamIO/deepstream.io-client-js

jaime-ez

commit sha 009e200d4206058f38499f0482b458b72bd868e4

[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle :100644 100644 b936458 9cc7f2f M src/deepstream.ts :100644 100644 d006dbe 0a48a7f M src/util/utils.ts

view details

jaime-ez

commit sha 198a9b6ba60e7378fd32bfea6c831f9e79ee04d0

[fix] explicit Buffer import

view details

Yasser Fadl

commit sha e8769c0bb245fc0e1699d1036552b6dae962096b

Merge pull request #531 from jaime-ez/master [task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle

view details

push time in 12 days

PR merged deepstreamIO/deepstream.io-client-js

[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle

Hi @yasserf, hope everything is ok.

I gave a second thought to the react-native issue and chose not to use the URL api, neither from the browser nor nodejs, since the use case is rather simple, and coded the url string manipulation directly. This allows to use the client in web, nodejs and react-native without adding more external dependencies. This fixes #515

Also exported the client as object in order to maintain the same api in the bundle. This fixes issue #528

Let me know what you think and I can push the package and changelog updates.

Also, should the main file in the package.json point to the bundle?

Cheers

+25 -15

2 comments

3 changed files

jaime-ez

pr closed time in 12 days

issue closeddeepstreamIO/deepstream.io-client-js

React Native 0.59+ URLSearchParams 'Error: not implemented'

Hi, i am trying to upgrade deepstream js client to v4, on React Native 0.61 but application seems to fail on this line of code: const client = new DeepstreamClient(url)

because on pareseUrl it is calling URL.host and reaches the following code that throws an exception: https://github.com/facebook/react-native/blob/e6057095adfdc77ccbbff1c97b1e86b06dae340b/Libraries/Blob/URL.js#L157-L159

Capture

Also i get this warning when removing the validation buy it might be another issue not related to this one Capture

I've tried solutions described here [0.59.x] URLSearchParams 'Error: not implemented' but nothing seems to work. Note: Client version 2.3.4 seems to work fine.

Is there any chance to support deepstream client v4+ on React Native v0.59+ ? My dependencies are:

"react": "16.9.0",
"react-native": "0.61.2",
"@deepstream/client": "^4.1.3",
"url": "^0.11.0"

closed time in 12 days

adrhub

pull request commentdeepstreamIO/deepstream.io-client-js

[task] do not depend on browser or nodejs URL api [fix] export DeepstreamClient as object property in bundle

Seems good to me. Happy to merge this in and you can commit changelog and tag directly from master. Thanks!

jaime-ez

comment created time in 12 days

push eventdeepstreamIO/deepstream.io-website

jaime-ez

commit sha fd8ad244f27e84bcb02673d40ab8ef8f59c435ef

[task] complete json endpoint description and config in server and client

view details

jaime-ez

commit sha 3f6d232636dc538ed179c659b238f7f8cfe38193

[fix] update links and code examples

view details

Yasser Fadl

commit sha 5077f9853bb403451d76f0e642ebceb228c94049

Merge pull request #45 from jaime-ez/master update json endpoint and react-native example

view details

push time in 12 days

starteddraft-js-plugins/draft-js-plugins

started time in 18 days

startedatlassian/react-beautiful-dnd

started time in 19 days

startedreact-dnd/react-dnd

started time in 19 days

issue commentdeepstreamIO/deepstream.io-benchmarks

make command error

Yeah this repo is pretty old and has not been updated in a while I’m afraid. It’s also the text protocol which is invalid after 3.0 in terms of server efficiency.

sas05

comment created time in 23 days

startedjacobbuck/react-beforeunload

started time in 23 days

fork yasserf/DefinitelyTyped

The repository for high quality TypeScript type definitions.

fork in a month

startedexpressjs/multer

started time in a month

startedrichardgirges/express-fileupload

started time in a month

startedi-like-robots/react-tags

started time in a month

startedytiurin/downscale

started time in a month

startedthibaudcolas/draftjs-conductor

started time in a month

push eventdeepstreamIO/deepstream.io-website

Ananda Umamil

commit sha 879110690e821c888c1ab1483574819eb06bc32d

Use gatsby-plugin-manifest for favicon & metadata

view details

Yasser Fadl

commit sha 9c077deb35306bfe7ceb2b14c558e39da3466379

Merge pull request #44 from zweimach/master Use gatsby-plugin-manifest for favicon & metadata

view details

push time in a month

PR merged deepstreamIO/deepstream.io-website

Use gatsby-plugin-manifest for favicon & metadata

Use official plugin from GatsbyJS instead of #33

+87 -97

0 comment

12 changed files

zweimach

pr closed time in a month

PR opened katspaugh/wavesurfer.js

doc: Changing LocalMediaStream to MediaStream

Title: Documentation Type change in Microphone Plugin

Please make sure you provide the information below:

Short description of changes:

Changing documentation LocalMediaStream to MediaStream As documented here: https://developer.mozilla.org/en-US/docs/Web/API/LocalMediaStream

+2 -2

0 comment

2 changed files

pr created time in a month

push eventyasserf/wavesurfer.js

Yasser Fadl

commit sha c16084708a84a4b7f7a50bbad0a2ca5f8696e61e

doc: Changing LocalMediaStream to MediaStream As documented here: https://developer.mozilla.org/en-US/docs/Web/API/LocalMediaStream

view details

push time in a month

fork yasserf/wavesurfer.js

Navigable waveform built on Web Audio and Canvas

https://wavesurfer-js.org

fork in a month

startedKagami/ffmpeg.js

started time in a month

startedreact-native-community/react-native-audio-toolkit

started time in a month

startedtonistiigi/audiosprite

started time in a month

startedlocalForage/localForage

started time in a month

issue commentfacebook/draft-js

Changing entity data doesn't update contentState, and changing selection state or entity data does not cause decorators to run

I managed to get it to rerender by replacing the text with itself:

contentState = Modifier.replaceText( contentState, selectionState, block.getText().substring(start, end), // start and end are the same as the selection state anchor and focus offset undefined, entityKey, )`

bcokert

comment created time in a month

issue commentdeepstreamIO/deepstream.io-client-java

java client code does not work well

I'm sorry but there aren't any active maintainers on deepstream java anymore so it's unlikely you'll get a response.

turbo-xp

comment created time in a month

issue commentdeepstreamIO/deepstream.io

RangeError [ERR_OUT_OF_RANGE]

@grydstedt to be clear, as long as you don’t need server side merging, if you stick, to using ‘set’ without paths, enable the hot path prefix on the server config to include your record pattern and ensure the client side merge resolution is accept remote for that pattern it will work by forcing the version to 1 without you needing a patch.

grydstedt

comment created time in a month

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

The comment I made contained the commit with the issue, mentioned the fact it was fixed in 5.1.1

Please not that 5.1.1 is the server and not the client.

The client cdn is actually correct, since it’s sending down the new messages in the protocol.

The reason it’s crashing is because there are some new fields in the protocol and a guard wasn’t in place to support both cases.

2.0 was years ago, but we never bundled us files into the hot release. Normally people would instead using npm and then reference ‘@deepstream/client/dist/Client.min’ or something similar.

Please confirm your on 5.1.1 on the server.

davidbehler

comment created time in a month

issue commentdeepstreamIO/deepstream.io

TypeError: Cannot read property 'add' of undefined

This seems to be that the client cdn isn’t updated, and also that your not running the latest version.

https://github.com/deepstreamIO/deepstream.io/commit/347621d0bcc1302d8b9133c2cf8a148db2b0b9e2

5.1.1 was released shortly after 5.1 and has that fix.

davidbehler

comment created time in a month

startedpshihn/rough-notation

started time in a month

startedpkalogiros/AudioMass

started time in a month

pull request commentdeepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

Welcome to the org! 🦸

jaime-ez

comment created time in a month

push eventdeepstreamIO/deepstream.io-storage-postgres

jaime-ez

commit sha a61bf10b228a02a5aed5372bf0ebec8b67f7eeae

[task] version 3.0.0

view details

jaime-ez

commit sha 82ece656c88560c7da0f984c3b5d83ea4fa10dd4

[fix] include a std logger when plugin is used in standalone mode [fix] main file in package.json

view details

jaime-ez

commit sha 71a7f300837637a1202b9990121b07111d226cea

[task] add husky script and include dist folder for easy install from branch

view details

Yasser Fadl

commit sha cac954cb4ade9ac95033dc536e52e39c38a3eddb

Merge pull request #36 from jaime-ez/ts [task] version 3.0.0

view details

push time in a month

PR merged deepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

Bump version, update changelog and clarify the defaultTable option.

it's not possible to do tags in PRs :(

+2069 -47

5 comments

37 changed files

jaime-ez

pr closed time in a month

startedchris-rudmin/opus-recorder

started time in a month

startedaikoven/typescript-fsa

started time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

btw @jaime-ez, happy to add you into the org so that u can do tags and such directly. Let me know if your interested

jaime-ez

comment created time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

Thanks again for the work @jaime-ez

jaime-ez

comment created time in 2 months

issue commentdeepstreamIO/deepstream.io

Future of deepstream / Contributor Callout

After the step down blog I have had a really friendly and interesting company reach out willing to fund me to build out SDKs for deepstream. I initially was pretty happy to start but have since turned the offer down.

The reason I turned it down is because:

  1. I got 30 responses (some duplicates) of people using deepstream in the last few months.
  2. Out of those thirty, 60% are using version 5.
  3. Out of those 60%, 6 have enabled telemetry.

Thats 6 people who have allowed telemetry across ALL users. Not just the 30 users I'm aware of.

As such, the logical conclusions are either:

  1. The userbase is tiny.
  2. The userbase is larger, but unaware that the project is in a bit of a crisis mode (which means they haven't seen the website in months).
  3. The userbase is larger and are aware but don't want feel the need to take action, which is completely fine as well.

I have decided to step down entirely entirely from this project, including all github issues and otherwise, in October. The reason I'm adding some months is incase someone raises an issue on migration or critical bug. The only way this decision will be turned around is if number 2 or 3 in the points above are true and action is taken. This has no longer become an issue of sponsorship or funding, it's literally that maintaining an opensource project of this size needs users in order to be relevant. Having 30 opensource users on a 5 year project that had hundreds of thousands of pounds sunk into is a far definition of success.

As for the current contributors who are sitting by and watching with a concerned expression, please remember this is now completely opensource, and as such you can spend some of your time writing a medium post, tweeting or whatever else comes to mind that could effect those three points above.

Thanks.

yasserf

comment created time in 2 months

startedbokuweb/react-rnd

started time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

FYI, if we release this the next deepstream release will break for postgres users. Given the project is in maintenance mode I don't want to introduce breaking changes in there. Can we change the docker file in deepstream root to install v2 of this adaptor?

jaime-ez

comment created time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

[task] version 3.0.0

FYI, if we release this the next deepstream release will break for postgres users. Given the project is in maintenance mode I don't want to introduce breaking changes in there. Can we change the docker file in deepstream root to install v2 of this adaptor?

jaime-ez

comment created time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

handle data stored as jsonb

Tests pass. If you do the changelog and package.json happy to release.

Is it possible to do tags in PRs? 😁

jaime-ez

comment created time in 2 months

pull request commentdeepstreamIO/deepstream.io-storage-postgres

handle data stored as jsonb

👍

jaime-ez

comment created time in 2 months

push eventdeepstreamIO/deepstream.io-storage-postgres

jaime-ez

commit sha 165250a50ec61496c800fa944eb7520e0f3ce606

[fix] -check if value is string before parsing JSON in order to allow using jsonb. - use a less common schema name for tests

view details

Yasser Fadl

commit sha 8910840473320b50ab7bf9d2bbf1acd58e3ac041

Merge pull request #35 from jaime-ez/ts handle data stored as jsonb

view details

push time in 2 months

PR merged deepstreamIO/deepstream.io-storage-postgres

handle data stored as jsonb

and other minor fixes, mainly to avoid unwanted schema name collisions during tests

+15 -12

0 comment

3 changed files

jaime-ez

pr closed time in 2 months

starteddmotz/oriDomi

started time in 2 months

startedguigrpa/timm

started time in 2 months

issue commentdeepstreamIO/deepstream.io

RangeError [ERR_OUT_OF_RANGE]

Easiest way to deal with this is to do rolling. If the number is 2147483647 then go back to zero. Will end up having all the clients needing to just accept remote.

Best way of doing that is probably sending out a custom message inform clients to do so via the protocol. It's aint great, but the client would break eitherways due to same error.

I'm no longer maintaining ds, happy to accept a patch if anyone raises it.

Easiest way to test would be to use setData(name, 2147483646, data) api and then updating normally.

grydstedt

comment created time in 2 months

startedRosey/markdown-draft-js

started time in 2 months

startedjpuri/draftjs-to-markdown

started time in 2 months

startedglobocom/react-native-draftjs-render

started time in 2 months

startedKagami/vmsg

started time in 2 months

startedkatspaugh/wavesurfer.js

started time in 2 months

push eventdeepstreamIO/deepstream.io-protobuf-js

Yasser Fadl

commit sha cc0b420b4c510cda8da3906dc503fb60135fccf2

1.0.4

view details

push time in 2 months

push eventdeepstreamIO/deepstream.io-protobuf-js

Yasser Fadl

commit sha d271f96708844a40605a5562ed5cd6c298844bb6

switching MIT, AGPL here completely breaks MIT in server and client

view details

push time in 2 months

push eventdeepstreamIO/deepstream.io-protobuf

Yasser Fadl

commit sha 9eb24e29c7f0d0cda61dcae6c17e6934adeb0aa1

switching MIT, AGPL here completely breaks MIT in server and client

view details

push time in 2 months

issue openedklaussinani/rels

Show more than 30 releases

Describe the bug When using --all or a number > 30 with list it only shows the last 30 releases

To Reproduce rels --repo deepstreamIO/deepstream.io --list 50 rels --repo deepstreamIO/deepstream.io --all

Expected behavior Show all releases (in the hundreds)

Technical Info (please complete the following information)

  • OS: darwin
  • Rels Version: 0.4.3
  • Node.js Version: 12.6

created time in 2 months

startedklaussinani/rels

started time in 2 months

startedbrickpop/flutter-rust-ffi

started time in 2 months

issue openedwehriam/deepstream.io-cluster

Adding to deepstream core connectors

Hello!

I was wondering if you would like to have this under the deepstream umbrella with other connectors so that it can be bundled into the binary.

Thanks again for your work on this!

created time in 2 months

issue closeddeepstreamIO/deepstream.io

Elton phone home

Given there are only 10 packages claiming to use deepstream (vs the X million for socket.io) the next feature will be bit more of a James Bond spy I’m afraid.

Before you panic, here’s how it will look like:

telemetry: type: deepstream.com (yeah it’s a plug-in! You can override it as default with other things if you want)

Yeah that’s really about it. By default it will be disabled, but will print log messages on start pleading you to enable it so that I can gather better numbers to help determine this projects future. If you want to fully disable logging as well, override the plugin with your own.

It will most likely just trigger a lambda on ds side that logs your OS, DS version, binary/node and startup time.

It may also send an update (configurable, only when something changes) stating what features you used (permissions/endpoints/events/etc). This will help figure out how if deepstream continues on so we can pivot away from some of the features, or at least prioritise them.

I really don’t care about tracking (no offence!) and would love if anyone has input into a way I can gather this data without having access to your IP, without using a third party VPN or dark web.

If there was a fatal crash it will also upload the stack trace as well at some point, but that’s an opt in feature.

This is really easy to implement and would be much more efficient than the google form I have now, I think (given I got very few responses).

Again, addressing the elephant in the room, this is opensource right? Why are you tracking stuff? Your evil right? Who you selling your data to? I don’t want people to know I’m using DS! That’s it, I’m moving to something else that cares about my privacy.

I get it, it’s not a great solution and it’s why I’m adding it in SO LATE into the project. Trust me, if I wanted decent info for the cash it would have been when deepstream had a company around it.

The reason why this is being added is because deepstream is in a delicate state right now. I personally would love to continue supporting it however I need motivation, and that motivation my friends are users and contributors👩🏽‍💻🧑🏿‍💻👨🏽‍💻. And what better way to have an idea of the number than to do this.

So, when you see that log line pleading you to enable it and you ignore it, please remember that that just commenting that line can directly affect the life and death outcome of this project.

Also the lambda code will be a public repo, although obviously I won’t be giving anyone access to AWS itself.

Thanks!

closed time in 2 months

yasserf

issue commentdeepstreamIO/deepstream.io

Elton phone home

Implemented in 5.1!

yasserf

comment created time in 2 months

more