Lukasz Gornicki

ok, it is either `@asyncapi/payload-police` or `@asyncapi/goalie` or `@asyncapi/keeper` or `@asyncapi/goalkeeper` Pick one and rename it accordingly

don't worry @Adi-204 I'm aware that in ecosystem there is no widely adopted standard for "human readable" errors. So the current error is completely fine. For initial implementation completely technical...

/rtm

@jonaslagoni not good, but yeah I get your point. So might be that they best would be to block autoupdates 🤔 @Souvikns ?

yeah, it sucks 😞 there is no best approach here 😞 loosing autoupdates sucks or we complicate too much and nobody cares about output changes 🤔 nobody complains so far...

Hey @Lancetnik, sorry for the delay, but an AsyncAPI Conference recently kept us busy. Please have a look at https://github.com/asyncapi/community/blob/master/AMBASSADOR_ORGANIZATION.md#ambassador-requirements. As far as I can see in your PR, you...

Thanks for your openness and understanding 🙏🏼 > Yeah, I knew about formal requirements to be an ambassador, but some contributions can't be measured. I created FastStream and now this...

> I'm not sure how you could make a request on your own, don't know such a process. I just reached via email my LF contact to understand who should...

Hi @Lancetnik, First of all, thank you so much for all the enthusiasm and effort you’ve invested in the AsyncAPI community, both in spreading the word and enriching our tooling...

@polyn0m sorry for not an addressing the problem earlier but we were focused on AsyncAPI v3 release. @ldynia can you please clarify if after using `--user=root` the error is still...