Wildan Gunawan

Results 16 comments of Wildan Gunawan

Jupyter notebook workaround for this issue: ```bash !pip3 uninstall twint -y !pip3 install --user --upgrade git+https://github.com/twintproject/twint.git@origin/master#egg=twint ``` Then continue as usual ```python import twint import nest_asyncio nest_asyncio.apply() c = twint.Config()...

> Is there any specification for installing it on ubuntu? I have no problem installing it on Ubuntu 16.04 under Conda environtment. I used this command: ```bash pip install --user...

I have this issue as well. Thank to @AJRepo, I managed to launch MAVROS successfully. I'm following how PX4 launches MAVROS (only the format), you can look at [here](https://github.com/PX4/PX4-Autopilot/blob/master/launch/mavros_posix_sitl.launch#L25). @AJRepo...

Also I think it's not only that. Since they moved from Webpack+Mix to Vite, the config file also changed. ![image](https://user-images.githubusercontent.com/35158077/207558055-a71a40ea-366d-484c-9d21-41f275667754.png) from [this](https://github.com/coollabsio/coolify/blob/main/apps/api/src/lib/buildPacks/common.ts#L799) should be changed to `COPY *.json *.config.js /app/`...

Yep, that's, I suspect, because the Dockerfile didn't copy the config files (vite.config.js, postcss.config.js, and tailwind.config.js). Hence returned an error. I tried running `vite build` on local and all good...

> Simply adding `"production": "vite build"` to my `package.json` file didn't work. Still got the same error. Yeah I alr reported another issue with the Dockerfile [here](https://github.com/coollabsio/coolify/issues/788#issuecomment-1350720353) and [here](https://github.com/coollabsio/coolify/issues/788#issuecomment-1351609313) (in...

HAHAHA. Just saw this issue while also trying to zip the folder. Right now I'm copying each JSON file to my own Google Drive via Colab. Copying 110k files took...

Aaaahhh love it. Thanks Pak @cahya-wirawan :D. Probably Pak @feryandi can add the link to the Huggingface dataset on readme

Same issue using 280 Pi

I already send this concern to the tech dept (support at elephantrobotics dot com) email. Hopefully we get response soon.