kbariotis
Repos
123
Followers
232
Following
55

Virtual whiteboard for sketching hand-drawn like diagrams

33361
2669

HTTP Error collection to use in your next REST API.

272
18

The opinionated presentation app.

20
1

Declarative functional cron expression builder

14
0

My Gatsby.js powered personal homepage

66
14

A set of standard document templates.

1974
156

Events

issue comment
Terraform module

oh that looks great @marceloboeira , thank you for that.

So what I'm thinking is that I would like to automate the creation of the flag and its initial values across different environments (staging, prod, etc), but not necessarily dictate the distributions and leave those to be changed through the UI.

I guess there are multiple use cases there, one would also want to set those distributions and have them set only through the code.

what do you think?

Created at 1 week ago
Created at 1 week ago
opened issue
Terraform module

Hey everyone and thank you for this project.

This is a feature request to have a terraform module so we can keep our flags under version control. I'm not sure if this has been discussed before, please let me know if it has.

Thank you

Created at 1 week ago
started
Created at 1 week ago
Created at 1 week ago
Created at 3 weeks ago
closed issue
TypeError : Session must be a buffer

Details

I am not sure if this is a bug so I thought I would ask here.

I'm using Axios to make an external request from a Node.js service, the service is healthy, operates normally, and is on a k8s cluster.

At random times, I'm getting this error from these external requests that seem like they never hit the external service. Once they start failing, we've configured it so the process restarts and then continues normally able to reach the external service again.

TypeError: Session must be a buffer
    at TLSSocket._init (node:_tls_wrap:732:11)
    at new TLSSocket (node:_tls_wrap:531:8)
    at Object.connect (node:_tls_wrap:1625:19)
    at Agent.createConnection (node:https:143:22)
    at Agent.createSocket (node:_http_agent:340:26)
    at Agent.addRequest (node:_http_agent:291:10)
    at new ClientRequest (node:_http_client:311:16)
    at Object.request (node:https:353:10)
    at /home/node/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:54:19
    at Scope._activate (/home/node/node_modules/dd-trace/packages/dd-trace/src/scope/async_resource.js:57:14)

Any chance you may help understand what the problem is? Thank you

Node.js version

16

Example code

Simple GET request using Axios.

Operating system

docker node-alpine

Scope

run time

Module and version

https

Created at 1 month ago

Allow multiple event objects in one socket data event

In some cases the device socket responded with a data string that contained multiple objects seperated by an empty line. If this construct was passed to JSON.stringify it failed with an unhandled error as the json structure was not valid. Splitting the response by empty lines and handling each event fixes this.

In my case I received the following data string after calling powerOn method on the device:

{"id":0, "result":["ok"]}
{"method":"props","params":{"power":"off"}}

Merge pull request #1 from garthenweb/fix/multiple-event-in-one-data-response

Allow multiple event objects in one socket data event

Created at 1 month ago
pull request closed
Allow multiple event objects in one socket data event

In some cases the device socket responded with a data string that contained multiple objects seperated by an empty line. If this construct was passed to JSON.stringify it failed with an unhandled error as the json structure was not valid. Splitting the response by empty lines and handling each event fixes this.

In my case I received the following data string after calling powerOn method on the device:

{"id":0, "result":["ok"]}
{"method":"props","params":{"power":"off"}}
Created at 1 month ago
issue comment
Allow multiple event objects in one socket data event

Thanks for the reminder and then contribution @garthenweb :)

Created at 1 month ago
opened issue
Session must be a buffer

Details

I am not sure if this is a bug so I thought I would ask here.

I'm using Axios to make an external request from a Node.js service, the service is healthy, operates normally, and is on a k8s cluster.

At random times, I'm getting this error from these external requests that seem like the never hit the external service:

TypeError: Session must be a buffer
    at TLSSocket._init (node:_tls_wrap:732:11)
    at new TLSSocket (node:_tls_wrap:531:8)
    at Object.connect (node:_tls_wrap:1625:19)
    at Agent.createConnection (node:https:143:22)
    at Agent.createSocket (node:_http_agent:340:26)
    at Agent.addRequest (node:_http_agent:291:10)
    at new ClientRequest (node:_http_client:311:16)
    at Object.request (node:https:353:10)
    at /home/node/node_modules/dd-trace/packages/dd-trace/src/scope/base.js:54:19
    at Scope._activate (/home/node/node_modules/dd-trace/packages/dd-trace/src/scope/async_resource.js:57:14)

And chance you may help understand what the problem is? Thank you

Node.js version

16

Example code

No response

Operating system

docker node-alpine

Scope

run time

Module and version

https

Created at 1 month ago
Created at 1 month ago
Created at 1 month ago
issue comment
Add support for apollo gateway/federation

Thanks @rochdev and apologies for the delay. I guess as the OP stated, it would be nice to have more information of the Apollo Federation execution in regards to all the different services its reaching out to. For example, the main trace graphql.execute could state all the different services it reached out to, or have a different trace for each separate service including its response.

It would be very useful to understand the timings of each request plus their responses that ended up forming the final request/response.

Created at 2 months ago
Expected to find a manifest file in `app/assets/config/manifest.js`

I was getting this error below when was trying to start the server:

➜  adyen-rails-online-payments git:(main) ✗ bundle exec rails s

=> Booting Puma
=> Rails 7.0.3.1 application starting in development
=> Run `bin/rails server --help` for more startup options
Exiting
bundler: failed to load command: rails (/Users/konstantinosbariotis/projects/adyen-rails-online-payments/bin/rails)
/Users/konstantinosbariotis/projects/adyen-rails-online-payments/gems/sprockets-rails-3.4.2/lib/sprockets/railtie.rb:110:in `block in <class:Railtie>': Expected to find a manifest file in `app/assets/config/manifest.js` (Sprockets::Railtie::ManifestNeededError)
But did not, please create this file and use it to link any assets that need
to be rendered by your app:

Example:
  //= link_tree ../images
  //= link_directory ../javascripts .js
  //= link_directory ../stylesheets .css
and restart your server

For more information see: https://github.com/rails/sprockets/blob/070fc01947c111d35bb4c836e9bb71962a8e0595/UPGRADING.md#manifestjs
	from /Users/konstantinosbariotis/projects/adyen-rails-online-payments/gems/railties-7.0.3.1/lib/rails/initializable.rb:32:in `instance_exec'
...
...
...

and I managed to fix it by using this answer from SO

Created at 2 months ago