aelgasser

Check the pull request I just submitted https://github.com/GoogleChromeLabs/comlink/pull/487 it'll allow to simply do : ```js myProxy.terminate(); ```

After @surma 's review of my first attempt, I've built this one on comlink-loader https://github.com/GoogleChromeLabs/comlink-loader/pull/27. Still waiting for it to be approved or rejected though

@seedy That's what I've used in my first attempt as well, but actually `worker[Comlink.releaseProxy]();` doesn't terminate the thread, it only removes the message port/proxy being used to communicate between the...

@developit Not sure I understand your question, but in my case, threads related to the workers are not released and stay showing up in the source tab of Chrome and...

I just pushed a WIP branch with the changes to terminate the worker (I was in the middle of refactoring when I realized that the workers were not killed, hence...

How would I reuse the worker created/returned by comlink and comlink-loader to perform multiple tasks (ie. multiple validators in my case)? The only solution I see would to 'bundle' all...

@DHaussermann, @levb, @mickmister, @manland we were experimenting with the plugin at my workplace and encountered this issue as well. After digging into the code and dependencies (more precisely `go-gitlab`), I...

Hi @mickmister the issue has just been fixed in go-gitlab in their 0.97.0 release (https://github.com/xanzy/go-gitlab/pull/1744#issuecomment-1925326400, https://github.com/xanzy/go-gitlab/releases/tag/v0.97.0)

Thank you @mickmister Do you have an approximate timeline for the next release? I know it's been about 4 years for other people waiting in this discussion and only about...

Hi @mickmister, I see you released version 1.8.1 with the fix thank you! Although we don't see it on the Mattermost plugin marketplace (https://mattermost.com/marketplace/gitlab-plugin/) or at least when we try...