Logan

Can confirm, I spent quite some time trying to figure this out because following the getting started guide leads to this error and causes a lot of confusion

Having this issue too, has anyone found a fix?

I tried running this code, but it's behaving very strange. This is using the pkg file from the latest release from lightbug_http.http import HTTPRequest from lightbug_http.uri import URI from lightbug_http.sys.client...

> @Logan9312 hmm I see, cannot reproduce this one on my Mac M1 using [this latest package](https://github.com/saviorand/lightbug_http/releases/download/latest-build/lightbug_http.mojopkg). Will try on a Linux machine later today. Using the package you linked...

I got that version when running `modular install mojo` so I assumed it was the latest stable. When I run `modular install nightly/mojo` I get version `mojo 2024.5.2514 (f472b8ac)`

@saviorand Sorry for late response, but I tried that package and still get the following errors: ```py /Users/logan/Documents/MojoTesting/lightbug_http.mojopkg:0:0: error: expected M::KGEN::LIT::DocStringAttr, but got: #kgen.symbol.constant : !kgen.signature owned_in_mem, |) -> !kgen.none>>...

Putting it here since you closed the other issue, > #246 Could you give list of mods which are copied to the standard mods folder? I assume it's not all...

I mean before the latest update, they would add to the automodpack folder and add into my game. Sodium was the only one that wouldn't add itself in game. Now...

Working much better on beta 8. Only sodium and Kotlin for forge get added to the main mods folder with the rest going into the automodpack folder as intended

The issue is this is an empty server with no mods, so maybe it's just an issue with 1.21 forge itself? It's also happening on NeoForged if that helps