Alwin Arrasyid

You might want to change your code into ```v module main import vweb struct App { vweb.Context } fn main() { vweb.run(&App{}, 8083) } pub fn (mut app App) index()...

My pleasure. I think we can close this issue, no?

Yes, i got this output after running `npm ls -g --depth=0 | grep makerboard` command: ``` ├── [email protected] ```

Yes, the package is there. Here's the output that's piped to `grep makerboard`: ``` drwxr-xr-x 8 nobody dycode 4096 Jul 21 10:20 makerboard ```

Very nice! Thanks

Hi @VojtechBartoska, I had a similar issue and I have tried using V2.0.3-RC1 tag but the issue remains. I tested using PlatformIO and here is my platformio.ini configuration ``` [env:ttgo-t-watch]...

I managed to remove the compilation errors by adding the following into my `build_flags` configuration in platformio.ini ``` -DBLE_42_FEATURE_SUPPORT=TRUE -DBLE_50_FEATURE_SUPPORT=TRUE ``` Here's my complete platformio.ini ``` [env:ttgo-t-watch] platform = https://github.com/platformio/platform-espressif32.git#feature/arduino-upstream...

Our team is facing a similar issue. After this line, he added the following code, which seems to recover the error. ```c++ i2c_context[i2c_port].unlock(); ``` below this line: https://github.com/m5stack/M5GFX/blob/0.1.15/src/lgfx/v1/platforms/esp32/common.cpp#L1409 ```c++ if...

Thanks @lovyan03. Before updating the library version, my device stuck when the error occurred because we heavily used the I2C bus. I haven't observed any failure/error so far, perhaps I'm...