iamolegga
Repos
30
Followers
95
Following
29

A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications on top of TypeScript & JavaScript (ES6, ES7, ES8) 🚀

52479
6146

The Cloud Native Application Proxy

40555
4259

🌲 super fast, all natural json logger

10482
725

React Native module for CodePush

C
8278
1258

An overview of Go syntax and features.

7147
915

Redis session store for Connect

2689
329

Events

issue comment
Build(deps): Bump minimatch from 3.0.4 to 3.1.2 in /examples/redis-store

Coverage report

Total coverage

| Status | Category | Percentage | Covered / Total | | :----: | :--------- | :--------- | :-------------: | | 🟢 | Statements | 100% | 26/26 | | 🟢 | Branches | 100% | 6/6 | | 🟢 | Functions | 100% | 6/6 | | 🟢 | Lines | 100% | 35/35 |

Status of coverage: 🟢 - ok, 🟡 - slightly more than threshold, 🔴 - under the threshold

Created at 4 days ago
issue comment
Run "Terraform plan" getting error "Failed to request discovery document"

@danieldreier any chance this will be fixed soon? Sorry for bothering, but there are no any comments from the maintainers for 2.5 years

Created at 5 days ago
Created at 6 days ago
Created at 1 week ago
issue comment
Run "Terraform plan" getting error "Failed to request discovery document"

This issue still actual on macos with the latest terraform release:

╷
│ Error: Error getting client
│
│   with provider["registry.terraform.io/hashicorp/tfe"],
│   on providers.tf line 7, in provider "tfe":
│    7: provider "tfe" {}
│
│ Error getting client: Failed to request discovery document: Get "https://app.terraform.io/.well-known/terraform.json": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
╵
Releasing state lock. This may take a few moments...
λ  terraform version
Terraform v1.4.0-alpha20221109

@Vivalldi mentioned certificates and here it's mentioned too as a bug of golang.

But it's solved in https://github.com/golang/go/commit/feb024f4153395e5bbb2a51bb3d1ddc4f5b0d2dc which is included in next releases: go1.19.3 go1.19.2 go1.19.1 go1.19 go1.19rc2 go1.19rc1 go1.19beta1 go1.18.8 go1.18.7 go1.18.6 go1.18.5 go1.18.4 go1.18.3 go1.18.2 go1.18.1 go1.18 go1.18rc1 go1.18beta2 go1.18beta1

terraform is using go1.18 since v1.4.0-alpha20221109 v1.3.5 v1.3.4 v1.3.3 v1.3.2 v1.3.1 v1.3.0 v1.3.0-rc1 v1.3.0-beta1 v1.3.0-alpha20220817 v1.3.0-alpha20220803 v1.3.0-alpha20220706 v1.3.0-alpha20220622

So since v1.3.0-alpha20220622 this is surely not a bug of golang.

Maybe someone from the team could provide more info on this and when this annoying bug will be fixed. The only alternative I can see now is move from terraform cloud to another backend

Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
Created at 1 week ago
started
Created at 1 week ago
Created at 1 week ago
closed issue
e.VIper.ReadInConfig run as part of Unmarshal clears merged in fields

Hi,

due to e.Viper.ReadInConfig() that is invoked as part of Enviper#Unmarshal any additional fields added via Viper#MergeConfigMap method are cleared. That prevents usage like that:

        e := enviper.New(viper.New())
	if err := e.ReadInConfig(); err != nil {
		panic(err.Error())
	}
	if err := e.MergeConfigMap(defaults.AllSettings()); err != nil {
		panic(err.Error())
	}
	if err := e.Unmarshal(&cfg); err != nil {
		panic(err.Error())
	}

Is there a reason why Unmarshal makes a call to ReadInConfig? Afaik, viper itself expects users to call ReadInConfig explicitly before Unmarshal is used

Created at 2 weeks ago
closed issue
[FEATURE REQUEST] Context outside of requests

Is your feature request related to a problem? Please describe.

Currently, nestjs-pino can't add context to Nest.js microservices, CRON calls etc.

Describe the solution you'd like

Ability to somehow set context (by decorator or some function) of non-request calls.

Describe alternatives you've considered

Theoretically, it's possible to access library internals, access AsyncLocalStorage in storage and manually set it for current async context.

Created at 2 weeks ago
issue comment
[FEATURE REQUEST] Context outside of requests

duplicate #803

Created at 2 weeks ago
Created at 2 weeks ago
Created at 2 weeks ago
issue comment
e.VIper.ReadInConfig run as part of Unmarshal clears merged in fields

This was in original solution. I actually don't remember why is this required. You could fork this repo, drop that line and run tests and see if it will work for you

Created at 2 weeks ago
issue comment
build(deps-dev): bump ts-jest from 27.1.3 to 27.1.4

@dependabot rebase

Created at 3 weeks ago
Created at 3 weeks ago
Created at 3 weeks ago
Remove gradle javadoc task

published in 3.1.2

Created at 3 weeks ago
iamolegga create tag v3.1.2
Created at 3 weeks ago

Removes gradle javadoc task

There's not much use to the javadocs here, as the native sources don't contain additional docs and users of the package will interact with the JavaScript API only

Created at 3 weeks ago
After upgrading from 0.67.4 to 0.69.1 and everything is working on IOS I'm getting this error on android

"react-native-launch-arguments": "^3.1.0" that's the version I'm using

That's the error I'm getting:

A problem occurred configuring project ':react-native-launch-arguments'.

Could not resolve all files for configuration ':react-native-launch-arguments:implementation'. Could not resolve com.facebook.react:react-native:+. Required by: project :react-native-launch-arguments

Created at 3 weeks ago
Remove gradle javadoc task

There's not much use to the javadocs here, as the native sources don't contain additional docs and users of the package will interact with the JavaScript API only.

Resolves #38

Thanks for maintaining the package 🙌

Created at 3 weeks ago
issue comment
[BUG] System logs skipped on startup

Logs in local development were in json format though

Created at 3 weeks ago
issue comment
[BUG] System logs skipped on startup

Faced with the same issue today on production (in k8s too), logs were in the same format as here. After upgrading to the latest versions of nestjs-pino and pino-http it was solved

Created at 3 weeks ago