Andrey Frimuchkov comments

Results 11 comments of


                                            Andrey Frimuchkov

Support/make use of Async Hooks

Any updates? There are 2022, Node.js 18 and no async_hooks in sentry :(

Remove warning for exactly-once subscriptions

@feywind thanks for your answer! Yes, this warning heppening once per minute, but in logs it looks like an error... Is it possible to provide logger or just pass a...

Remove warning for exactly-once subscriptions

@feywind but I don't use exactly-once subscription with the Node client library :) Okey, I'll wait for support, this errors is not a big deal, just a little bit annoying....

Add more debug info for "invalid memory address or nil pointer dereference"

> v3.4-rc3 I'll try :)

Add more debug info for "invalid memory address or nil pointer dereference"

> @frimuchkov can you try v3.4-rc3? @sarabala1979 During rolling out 3.4.0-rc3 ```time="2022-09-03T11:38:03.035Z" level=fatal msg="error unmarshaling JSON: while decoding JSON: json: unknown field \"archiveLogs\""```

Add more debug info for "invalid memory address or nil pointer dereference"

> @frimuchkov Are you getting the above error workflow controller log? can you provide more logs and your workflow yaml? @sarabala1979 I'm getting it during rolling out new versions in...

Add more debug info for "invalid memory address or nil pointer dereference"

@sarabala1979 deployed We had `persistence.archiveLogs` in `argo-workflow-controller-configmap`...

Parent node not initialized

@sarabala1979 but I provided logs above :) We rolled back to 3.3.9 and started to see "nill pointer", then we added `--loglevel warn` and error disappeared, looks like it was...

forward in onError link doesn't send any requests

@magrinj have you solved it with chaning order of links?

Can i run the project now?

+1 Guys, you are doing an awesome stuff When it will be possible to see the backend?