Skip to content
This repository was archived by the owner on Jan 20, 2025. It is now read-only.

Which fork to pick? #1017

Closed
rikki78 opened this issue Jul 10, 2021 · 12 comments
Closed

Which fork to pick? #1017

rikki78 opened this issue Jul 10, 2021 · 12 comments
Labels

Comments

@rikki78
Copy link

rikki78 commented Jul 10, 2021

It seems the repository isn't updated anymore and issues remain open. There are many forks, but I'm not sure which one to pick. Any recommendations anyone?

@stale
Copy link

stale bot commented Sep 19, 2021

[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 19, 2021
@stale
Copy link

stale bot commented Oct 12, 2021

[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Oct 12, 2021
@guilhermeaiolfi
Copy link

So, which fork is the best one? Anyone?

@rikki78
Copy link
Author

rikki78 commented Oct 24, 2021

I'm now using this fork and that works pretty well.
https://github.com/yubox-node-org/ESPAsyncWebServer.git#yuboxfixes-0xFEEDC0DE64-cleanup

@proddy
Copy link

proddy commented Nov 5, 2021

I'm on the same fork, and it seems solid. Although you may want to hunt around for better versions of the asynctcp library

@zekageri
Copy link

zekageri commented Nov 5, 2021

I got websocket crashes with that fork. :(

@proddy
Copy link

proddy commented Nov 5, 2021

yes I saw your post on that.

@rikki78
Copy link
Author

rikki78 commented Nov 5, 2021

So which one would you recommend?

@zekageri
Copy link

zekageri commented Nov 5, 2021

Don't know man. I'm desperately trying to find one. This was really promising. Other than this stupid socket crash this is the most reliable. With yubo fixes lib

@proddy
Copy link

proddy commented Nov 5, 2021

I got websocket crashes with that fork. :(

if you're getting crashes in asyntcp like the below (and are on ESP32)

E (36601) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (36601) task_wdt:  - async_tcp (CPU 0/1)
E (36601) task_wdt: Tasks currently running:
E (36601) task_wdt: CPU 0: IDLE0
E (36601) task_wdt: CPU 1: IDLE1
E (36601) task_wdt: Aborting.
abort() was called at PC 0x40194548 on core 0

then try me-no-dev/AsyncTCP#121
it really helped on stability

@zekageri
Copy link

zekageri commented Nov 5, 2021

Oh. I got no watchdog reset but I have problems with freeing the socket queue. I will try this one out. Thank you!

@DRSDavidSoft
Copy link
Contributor

It appears the updated version of the 0xFEEDC0DE64 fork is this one:
https://github.com/mathieucarbou/ESPAsyncWebServer

I have been using the WebSocket server on top of this fork for quite a while now (I only use textAll()) and it works smoothly.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants