arladmin

@muhsin-k So far, the issue seems to be with one particular account (the primary one). Why could that be? And how to resolve it?

@muhsin-k @vishnu-narayanan > Why could that be? > And how to resolve it? ?

I keep experiencing this, on both, Chatwoot cloud app as well Self-hosted one.

@pranavrajs @muhsin-k Is there any fix/workaround for this, so far? Without a fix, it actually doesn't make much sense to continue using Chatwoot for various types of inboxes, eg. Whatsapp,...

@luke- > @ArchBlood Currently, we have no plans on our roadmap. Curious, why? Webhooks are pretty crucial as well as ubiquitous these days.

@Nitwel Hi. Is there any immediate workaround for this issue, until a permanent solution gets deployed? This seems to be a major bug (permissions not being respected) which is blocking...

@Nitwel We are using the Directus Studio as our Frontend itself, where all the users work. Hence, this issue's impact has exacerbated so much.

Hi @br41nslug Another example: This is the behaviour when i upload the same file to a different Directus instance (hosted on a 4GB, 2vCPU DigitalOcean droplet, with standard docker-compose setup):...

Update: the remaining 'excess' memory usage disappeared in exactly 10 mins. time since the start of the upload process (Note: the upload process lasted only for 3 mins.) : ...

@br41nslug > Looks like the AWS SDK may still be loading in the whole file into memory as it tries to concurrently do a multipart upload (tuned for max upload...