Bilal Bassam

@maya-bee Make sure your key uses PEM, nothing else. For example, when generating your key using ssh keygen you would do something such as: ```sh keygen -t rsa -b 4096...

Good to note, currently all of [my packages](https://lit.luvit.io/packages/Bilal2453) have the same issue. So there is a chance it is not per module, but per user. As well as the chance...

After some thinking and talking to contributors, this *might* have been caused by a bad local litdb on my end. Just when I wanted to publish one of my packages,...

I've been trying on a workaround of testing the previous theory, other than restarting the whole upstream since that's pretty problematic, and I came up with the idea of forcing...

Indeed, sounds like some missing validation, at the very least server side. I am honestly not quite sure where exactly either, I didn't dig to that point. But all I...

Oops that close was accidental

Not sure what to say, but this is not as straightforward as I thought. After publishing the problematic version, 1.1.10, I have published 1.1.11 of the mentioned package; and that...

coro-channel.lua#L126: ```lua local function wait() local thread = coroutine.running() return function (err) print("reaching assertResume") assertResume(thread, err) end end ``` coro-channel#L149: ```lua print("reaching socket:write") local success, err = socket:write(chunk, wait()) if...

```bash $ luvit Welcome to the Luvit repl! > require'coro-http'.request("POST", "https://google.com", {}, "") cannot resume running coroutine stack traceback: ``` As I assumed, it was affecting a wider range. The...

> The single file package problem is unfortunate. It indeed is, the implementation does its best to solve it but, that is as far as it is possible with Git....